03 / 07

Start from the problem, write the decisions down, and let the system enforce them.

01

Problem before backlog

Every product starts as a business problem, written down with the people who own it, then shaped into deliverables, a plan and a price.

02

Decisions in writing

Product and architecture decisions get a number, a reason and an owner. On the account companion we are past 160 of them.

03

Rules that check themselves

“Read-only” is a wish until a database role enforces it. I prefer boundaries the system checks over ones the team agrees on.

04

Ship to a link

Demos run from a public link that only changes when I deploy on purpose, so nothing shifts under a meeting.

Book and iPod in a glass sleeve

Support the arts

date an artist

liveGroove Salad

← → or swipe — rooms · Del — clear web · Click — the spider pounces. Make it miss three times…Swipe — rooms · Hold — clear web · Double-tap — the spider pounces. Make it miss three times…