Thoughts That Shape My Product Thinking
Small thoughts collected while designing, reviewing, testing ideas, using new tools, and figuring out why some decisions hold up better than others.
-
I naturally begin with the user — clarity, accessibility, behaviour and the next decision they need to make.
-
Feedback taught me to see the other side too: brand, business, growth and stakeholder expectations.
-
The job is not choosing one over another. It is finding the direction where they can work together.
A product decision rarely belongs to one perspective.
The screen stopped being the whole product.
1
-
AI can generate flows, interfaces and prototypes remarkably quickly.
-
That makes one thing easier to notice: a polished output can still be built on an assumption.
-
Research and usability testing give me the context the interface cannot provide on its own — how people behave, where they hesitate, and whether the product actually makes sense to them.
Fast execution still needs evidence behind the direction.
Speed exposed the missing thinking.
2
Wireframes earn their time back.
3
-
Going directly into polished UI may save time at the beginning.
-
But when the journey, hierarchy or interaction logic is unresolved, those questions return later as changed screens and repeated iterations.
-
For a product solving a real problem, wireframes are where I work through those decisions before visual polish makes them expensive to change.
Solve the flow while changing it is still cheap.
A good brief is already a design tool.
4
Before the interface, I want clarity around a few things:
-
Who is this for?
-
What must the product solve?
-
What matters to the brand?
-
What should success look like?
Clear answers make both manual and AI-assisted exploration more useful. The brief is not paperwork before the design. It shapes what deserves to be designed.
Better questions usually lead to better product decisions.
Craft begins after the obvious choice.
5
-
Patterns, components, libraries and generated layouts can get a product surprisingly far.
-
Craft is what happens next.
-
Hierarchy. Spacing. Typography. Accessibility. Motion. Content. Restraint.
-
The goal is not to make every interface different. It is to make each decision feel like it belongs to that product.
Craft is knowing what to refine — and what to leave out.
Tools moved closer to the product.
6
Figma Make, Agents, motion tools, AI and code-assisted workflows let me explore faster and spend less time rebuilding predictable parts.
What matters to me is what happens after generation:
-
Does the flow still make sense?
-
Does it use the system correctly?
-
Does it survive another iteration?
-
What still needs human judgement?
I value tools most when they create more room for those decisions.
Automation can shorten the work. It does not own the judgement.
I want to see what happened before “shipped.”
7
-
When something is presented as AI-built, the final screen is only the first thing I look at.
-
I want to know the workflow behind it — the brief, tools, refinements, testing, implementation and what changed along the way.
-
That is where product thinking becomes visible.
-
Not in how quickly the first version appeared, but in how deliberately it became reliable.
The result shows what was made. The process shows how it was thought through.
The questions I keep nearby.
8
01 — Who are we designing for — user and brand?
02 — What problem must this product solve really well?
03 — Which features and decisions deserve priority?
04 — Are we simplifying the next decision or adding friction?
05 — Does the experience also help the product succeed?
When a product gets complicated, the right questions bring it back into focus.
One thing stays constant.
Every interaction should earn its place.
-
Research should clarify.
-
Feedback should widen the view.
-
Craft should make the product intentional.
-
Tools should create room for better decisions.
The interface is what people eventually see.
The product thinking is what makes it worth using.