START WHERE IT’S UNCLEAR

Most people wait for a project to come into focus before they move. The unclear part is usually where the value is, and where I start.

How I work

When a space is fuzzy, the instinct is to narrow it fast. I widen it first. I read where the world is going, and the system your users actually live in, until the real shape of the problem shows up. That's where the bet is hiding: not in the obvious lane, but in the part everyone stepped around.

Then we move forward. Sketch it, test it, let the evidence talk. And I build with your team, not around them, so the thinking stays in the room after I've gone. The work has to outlast me, or it isn't finished.

How we can work together

A week, a quarter, or the longer haul. We'll size it to where you are.

Direction Sprint.
For teams and founders who need to make sense of their space and commit to a direction. We work three questions together: where the world is going, where value will be created, and how you'll play to win, and leave you with a direction you can start from.  
Best when: you're at the start, the space is fuzzy, and you need clarity.

Concept Validation Sprint.
Turn a fuzzy idea into something testable. Research, prototyping, and structured experiments give you the evidence to grow it, pivot it, or stop. before you spend a year finding out the hard way.  
Best when: you have an idea and need to know if it's real.

Experience & Service Strategy.
An embedded partnership to launch and scale. Lifecycle mapping, service design, and the product or service foundations: design system, UX strategy, core features, your team can build on for the long run.  
Best when: the direction is set and you need to make it real and repeatable.

Coaching & Mentoring.
One-to-one support for founders, designers and design leaders navigating ambiguity, growth, or a big transition. Trained in co-active coaching (CTI), I help you find your own clarity , not hand you mine.  
Best when: the thing that needs to move forward is you.

What I make

Not only slide decks. Objects you can use. They reflect the way I work, in order:

The state of the user and system.
An honest read of where your users and the systems around them actually are: emotionally, contextually, specifically. And where the openings to bet are. Built for you, your team, your moment. The from and the to, made concrete.
The vision sprint and artifact.
Not a deck about the future, a living sketch of it. Made fast, by me or with AI: specific enough to point a team the same way, loose enough to keep changing as our thinking does. A north star you can argue with, and build toward.
The experiments to prove direction.
The tests that turn a bet into evidence, sized from an indicative directional signal to something you'd stake the roadmap on.
The decision frameworks.
The principles, criteria, and maps a team needs to keep moving without me in the room. The foundations you can operate from.
The team to run with.
How your team should be shaped, and how the operations can works, so the momentum outlasts the project.

Not sure which way you're pointing yet? That's usually the right time to talk.

Not only slide decks. Objects you can use. They trace the way I work, in order:

The state of the user and system.
A named, honest read of where your users and the systems around them actually are: emotionally, contextually, specifically. And where the openings to bet are. Built for your vertical, your team, your moment. The from and the to, made concrete.
The vision sprint and artifact.
Not a deck about the future, a living sketch of it. Made fast, by me or with AI: specific enough to point a team the same way, loose enough to keep changing as the thinking does. A north star you can hold, argue with, and build toward.
The experiments to prove direction.
The tests that turn a bet into evidence, sized from an indicative directional signal to something you'd stake the roadmap on.
The decision frameworks.
The principles, criteria, and maps a team needs to keep moving without me in the room. The foundations you operate from.
The team to run with.
How your team should be shaped, and how could it works, so the momentum outlasts the project.

Not sure which way you're pointing yet? That's usually the right time to talk.

Not only slide decks. Objects you can use. They trace the way I work, in order:

The state of the user and system.
A named, honest read of where your users and the systems around them actually are: emotionally, contextually, specifically. And where the openings to bet are. Built for your vertical, your team, your moment. The from and the to, made concrete.
The vision sprint and artifact.
Not a deck about the future, a living sketch of it. Made fast, by me or with AI: specific enough to point a team the same way, loose enough to keep changing as the thinking does. A north star you can hold, argue with, and build toward.
The experiments to prove direction.
The tests that turn a bet into evidence, sized from a cheap directional signal to something you'd stake the roadmap on.
The decision frameworks.
The principles, criteria, and maps a team needs to keep moving without me in the room. The foundations you operate from.
The team to run with.
How your team should be shaped, and how could it works, so the momentum outlasts the project.

Not sure which way you're pointing yet? That's usually the right time to talk.