Bet
Independent product concept
Bet
A reasoning layer for product decisions.
Product teams remember what they shipped. Bet preserves what they believed, how confident they were, and what happened next.
Selected work
Where the questions came from
The projects below left me with questions that continued beyond the work itself: how systems shape decisions, how organisations coordinate complexity, and where structure helps or gets in the way.
The common thread
Across these cases, the work sits at the boundary between product, systems and people.
- Worked across
- Customer products · internal platforms · emerging technology
- Questions explored
- How systems shape decisions · how teams coordinate · how complexity becomes usable
- Focus
- Turning ambiguity into structures teams can build with
Derived reflections
Writing from the same questions
Reflection · Delivery
What Gets Embedded
The number that travelled upward was how many customers had moved onto the new platform. It had no opinion about what they’d actually moved into.
Read the note →Reflection · Delivery
What Counts as Done
A minimum viable product promised before anyone agreed what “viable” meant. The deadline was clear. The learning was not.
Read the note →Still unfolding
I am still interested in the gap between what people intend, what systems encourage, and what actually happens when the two meet.