How I think

I don’t jump to solutions.
I follow the signal.

The tools change. The thinking doesn’t.

1. 01 / DiscoverSignalWhat’s actually happening, not what’s being reported?Learnt · NibbleWatch what people do. Twenty-four students asked for a career copilot. I built the opposite.
2. 02 / DefineProblemWhose problem is this, in one sentence?Learnt · LoocatorSolve for one person first. Not “public toilets”. A washroom one woman can trust, tonight.
3. 03 / PrioritiseChoiceWhat breaks first if we ignore it?Learnt · NibbleFix drop-off before features. Mission one finishes at 47%, not 60%. That gets fixed before any new feature.
4. 04 / MeasureOutcomeWhich number moves if this works?Learnt · BiteSpeedOne number changed my career. DSO went from 50 days to 30, and that number moved me into product.
5. 05 / BuildSystemWhat’s the smallest thing that proves it?Learnt · OrqenHarsh feedback is a spec. “Looks like AI slop” became the brief. I rebuilt around one working console.
6. 06 / ShipReleaseWho uses this tomorrow?Learnt · LoocatorVerify on foot, then ship. Nineteen spots verified on foot before a single pin went live.