How I Think
I start by asking what someone is trying to make easier. Where do they lose time? What is confusing? What would a useful result look like? Once I understand that, I can turn the idea into something they can try.
A good idea should make sense to the person using it.
From a question to a useful result
How I reduce complexity
I ask about the people, the information and the decisions involved.
Most problems get easier once they are broken into the right pieces.
Messy Problem
Scattered information. Repeated work.
Limits
What we have to work with
Users
Who uses it and what they need
Data
The information we can trust
Flow
The steps from question to result
How it works
Simplify. Structure. Connect.
Once the right pieces are visible, the system gets easier to shape into something workable.
Usable Outcome
Clear enough to act on
1. Start with the problem
I ask someone to walk me through a real task, including the calls, messages and workarounds. That helps me find the part a useful app could make clearer.
2. Make the steps clear
I work out what information is needed, what choices someone makes and what should happen next. The first version should help them complete that journey.
Simplicity over Complexity: I prefer simple, effective solutions over over-engineered systems. A useful solution should be easy to explain, improve and hand over to someone else.
3. Simplify what matters
A solar customer needs to see their options. A property team needs to know who is handling a buyer. A factory team needs to see what changed in the readings. I shape the solution around the decision each person needs to make.
4. Learn from people using it
I put a working version in front of someone and watch where they get stuck.
Their questions help me see what is missing, what is unnecessary and which parts deserve more work.
That feedback turns a promising idea into a more useful product.