The process

  1. 01

    Get into the room

    Before any brief or wireframe, I try to be where the problem actually lives. With Savior, that meant months inside hospitals before touching a spec. The gap between how things are supposed to work and how they actually work is usually where the product is. You can't see that on a call.

  2. 02

    Find the actual problem

    The brief is usually a symptom. "We need a dashboard." Okay, but what decision is it serving? I spend time here before writing anything down. The real problem is almost never the stated one.

  3. 03

    Build the smallest useful thing

    Not an MVP in the buzzword sense. The smallest thing that actually does the job for one real person. Career Leap started as a WhatsApp group. KnowYourPay started as a spreadsheet I shared with a few people. If the thing doesn't work before it's a product, it won't work after.

  4. 04

    Ship early, watch what happens

    I have a bias toward shipping early over debating internally. Real users in 3 days beats a perfectly refined prototype in 3 weeks. The feedback you get from watching someone actually use something is worth more than any survey or interview.

  5. 05

    Know when to kill it

    I shut down Career Leap when the unit economics didn't work. I killed Hypersync before it launched when the third person I showed it to said "I just use Doppler." The willingness to stop is as important as the willingness to start. Sunk cost is the enemy of good judgment.

How I think

What I don't do