Philosophy Complex products. Clear direction.
Your team can build faster than ever. Deciding what to build, and how it should all fit together, is getting harder.
Follow the threadThe cost of building
AI makes execution cheaper, which is good news: more room to explore, test and ship. But every new feature adds questions about how the product should behave and how it connects to what’s already there. The cost of building falls, while the effort of understanding the whole keeps growing.
Look closer
The work behind the screen
A screen can come together in minutes. Behind it sit different users and permissions, business rules, legal requirements and connections to other systems.
Take a simple approval button. Who can use it? What exactly are they approving? Can they change their mind? What happens to the people waiting on that decision? Building the button is the easy part.
Find what’s getting in the way
Sound familiar?
- There’s a workflow your team quietly works around.
- There’s a rule nobody is quite sure about.
- There’s a feature that matters to the business but keeps confusing customers.
- The product has grown feature by feature and no longer feels like one thing.
- You’re shipping faster than ever, but not always in the same direction.
These are the problems I like working on.
Give the work direction
How we’d work together
I start by talking with the people who use, build and run your product to understand what’s actually happening. Together we decide what needs to change, what’s worth keeping and where to start. Then I turn that direction into flows, prototypes and designs we test with real people before your team commits to building them.
Keep what matters
Not all complexity is a problem
Some of it belongs. A financial decision needs checks. A medical workflow needs care. The goal isn’t to remove those demands but to make them understandable, so that:
- Your customers know what they can do and what will happen next.
- Your team can explain why the product works the way it does, with fewer debates and less rework.
- You have a clear reason for what gets built next.
A clear next step
Let’s talk
If your product has become harder to understand than it should be, I’d like to hear about it.
See this thinking in practice