Perspective.

I like the business side, and I like helping people manage their stuff without a headache.

I started out freelancing, wearing a lot of creative hats for businesses in many different industries. What I kept wanting was more ownership over the direction and strategy of the product, not just how it looked. Product design gave me that: working out what a business needs, making it easy for the people using it, and turning a confusing screen into something that just makes sense.

A system earns its cost by removing repeated decisions, not just enforcing consistency.

Consistency isn't the only point: a system earns its keep when teams stop re-litigating the same patterns and spend their judgment on what's actually new. If it doesn't speed people up, it's just documentation.

AI makes me faster, and I still own the direction.

It speeds up execution but doesn't replace taste, product sense or knowing what not to build, so I use it as a thought partner and to iterate quickly while I keep direction, interaction quality and scope. Without real context and an understanding of the problem, it can also produce a polished-looking result that doesn't solve anything.

Diagrams are useful, but they go stale fast.

Diagrams help stakeholders and teams understand a system, but they quickly become artifacts of the past. Skills and markdown live next to the work, stay current, and serve both a teammate and an agent, and once that foundation exists it's far easier to turn it back into a diagram, prototype or journey map than the other way around.

Over a long enough timeline, user value and business value are the same problem.

A product that's good for users but not the business dies; one that's good for the business but not users decays. The work is finding the design that serves both, and that takes the range to understand business, tech, and psychology well enough to make real trade-offs, plus the restraint to remove everything that doesn't serve the outcome.

I design for the constraint, and make sure design never becomes the bottleneck.

Some teams prioritize the experience, others the deadline, and sometimes both are right. I've learned to work with each mindset instead of against it. The skill is discernment: knowing when a quick fix is the right call and when to push for broader change, while keeping design a resource that moves the team forward.

As building gets cheaper, deciding what is worth building gets more valuable.

AI makes producing a screen fast, so the hard part moves to judgment. A UI has always been a layer between a person and a task, and as more of that work becomes automated or conversational, someone has to decide what to hand off, how to keep people's trust, how they recover when it's wrong, and where a human should stay in the loop. When anyone can generate an interface, that judgment is what's scarce, which is why designers matter more now, not less.