Build reports
Product development, shown as an illustrative kanban board. Cards are example pieces of work, not a real client project. Filter by type of product.
Backlog ideas, ranked
Agree first releasePick the smallest set of features that tests the main hypothesis.
Web product
Web product
Choose platformsDecide between native iOS/Android or a cross-platform approach.
Mobile app
Mobile app
Define support needsWho fixes what, and how fast, once live.
Live service
Live service
Designing shape it
Design systemReusable components so screens stay consistent.
Web product
Web product
Onboarding flowFirst-run screens tested with users.
Mobile app
Mobile app
Building make it
Core journeysEngineering the key flows with automated tests.
Mobile app
Mobile app
Accessibility passKeyboard, screen reader and contrast checks.
Web product
Web product
Release pipelineRepeatable builds and deployments.
Live service
Live service
Live & learning measure it
Store submissionPreparing listings and meeting app store review rules.
Mobile app
Mobile app
Usage reviewCheck whether the hypothesis held; feed the backlog.
Web product
Web product
MonitoringErrors and performance watched after launch.
Live service
Live service
How a build runs
Work moves left to right in short cycles. At the end of each cycle we show working software, review what we learnt, and re-rank the backlog together. Nothing moves to “live” without testing, and every live feature gets checked against the hypothesis that justified it.