Teams ask:
“What should we build?”
I prefer to ask:
“What is making this harder than it needs to be?”
That small shift changes everything.
A user rarely experiences a business as a collection of technologies. They experience a checkout that takes too long, a form they have to fill twice, a dashboard they cannot understand, or a process that requires five different people to complete one simple task.
The technology is usually invisible.
The friction is not.
Build around the journey, not the software
When working on a website, ecommerce store, internal tool, or business platform, I like to map the journey first.
A customer might:
Discover → Compare → Decide → Buy → Receive → Return
A business employee might:
Receive request → Review → Approve → Process → Deliver → Follow up
Once the journey is visible, the technology becomes much easier to choose.
Sometimes the right answer is Shopify.
Sometimes it is WordPress.
Sometimes it is Odoo.
Sometimes it is a small custom application.
And sometimes the best solution is simply removing three unnecessary steps.
The interesting part is what happens between systems
Some of the best product opportunities live in the gaps.
A customer submits a form.
Someone copies the information into a spreadsheet.
Another person enters it into a CRM.
Someone sends a WhatsApp message.
Another person updates the order.
None of these steps are individually difficult.
Together, they create friction.
That is where I find the most interesting work: connecting the pieces so the user experiences one simple process instead of five disconnected ones.
A good interface hides complexity
The best interfaces don't necessarily have fewer things happening behind the scenes.
They simply make fewer things visible to the user.
A complicated business process might involve:
customers + inventory + payments + approvals + notifications + analytics
But the user might only need to see:
“Your order is ready. Confirm delivery.”
That is good product design.
The complexity still exists.
It has simply been put in the right place.
My approach
I enjoy working across different parts of a digital product rather than looking at each piece in isolation.
I like understanding the problem, exploring different ways to solve it, building the experience, and then improving it after people actually use it.
Because ultimately, the goal isn't to use the most impressive technology.
It's to build something that makes the work simpler, faster, and more useful.
A simple principle I keep coming back to:
Good technology solves problems. Great products make those problems feel like they never existed.