About — Notes by Alice

01｜Who I am

I'm Alice — sociology background, eight years at an IoT startup, from Marketing Specialist to Marketing Director.

My experience spans performance marketing, social, editorial, brand video, influencer, and B2C / B2B campaigns — alongside quotation workflows, CRM, internal reporting, and automation tooling. These may look scattered, but for me they all come back to the same thing: understanding where things are actually stuck, then building a solution that people will actually use.

A sociology background taught me to read context: how people act, how processes work, how information moves through an organization. After graduation, most of my learning came from a practical reason: keeping problems from stalling in discussion and turning them into something visible, testable, and fixable as quickly as possible.

From media buying, Figma, and design thinking to recently completing a Python course at NTU CSIE, this has helped me break requirements into executable tasks — and let teams align faster and commit resources sooner.

02｜Positioning

I work across product marketing, content strategy, and brand narrative, helping complex technology products translate technical capabilities into clear customer value.

I start by clarifying the purpose: who needs to understand this, who will use it, who will take it over? If an adjustment doesn't help with judgment, operation, or handoff, I generally don't treat it as a real solution.

When a process, message, or tool has room to improve, I start by figuring out where it's stuck: Is the customer not convinced? Is information not reaching the right person? Is the process too dependent on someone remembering? Or does the tool not fit how the work actually happens?

That lets me move between marketing insight and operational systems.

If the problem is that the message isn't landing, I pull signals from sales conversations, user reactions, and product specifics — and turn them into creative strategy, brand narrative, or pitch language.

If the problem is a workflow that keeps breaking down, I break it into roles, rules, fields, and tools — and rebuild it into something executable, trackable, and transferable.

03｜How I work

I define good work as shippable: building something that can be adopted, tracked, and handed off under real constraints.

Clarify the problem first

I start by confirming what this actually needs to achieve, then map the roles, process, and data involved. A lot of the time, what looks like a content, tool, or workflow problem is really a misaligned goal.

Build a testable v1

I'd rather get something running in real context than finish every detail on paper first. A working prototype surfaces problems that documents don't.

Converge with feedback

I refine based on metrics, real usage, and frontline feedback — documenting the rules and decisions so the result stays maintainable and handoff-ready.

AI is my accelerator. It lets me prototype tools and workflows without writing everything from scratch. But the real value is still in the decisions: what to build, why it matters, what trade-offs to make. AI speeds up execution — but what's worth building still requires a person to judge.

04｜Now

Learning podcasting — I want to document and share real management experiences from mid-level managers in SMBs.

The topic is closer to my work than it might seem: a lot of management problems aren't really about individual capability — they come from misaligned expectations, unclear roles, broken processes, and information gaps. I want to turn those rarely-articulated middle-management experiences into content that's easier to talk about.

This site will keep evolving with notes, case studies, and systems thinking.