Articles and reports on the decisions behind a useful product: what to build, what to connect, and what to take responsibility for.
2026 Edition
How expert teams turn AI-assisted work into faster product progress.
A report on shortening the path from a difficult problem to an accepted release: clear decisions, connected systems, inspectable work and AI used with judgment.
Read the 2026 report2025 Edition
Your first useful AI feature. A product roadmap for the year ahead.
An early-2025 perspective on bringing AI into your product: choosing a first use case, proving customer value, and moving from a promising demo to a dependable feature.
Read the 2025 reportBefore we ask, ‘Can we build this?’ let’s take a moment to ask, ‘Should we?’
Read perspectiveA product partnership starts with a responsibility—not a headcount. Here is how to make that responsibility concrete.
Read perspectiveFive questions to ask before moving AI from an impressive pilot into everyday operations.
Read perspectiveA booking is not finished at the confirmation screen. Neither is the engineering.
Read perspectiveStaying with a product works best when responsibility can evolve without becoming ambiguous.
Read perspectiveOur April Fools collaboration with Formidable Care turns a familiar checkbox into a workout. An absurd product idea, with a demo you can actually try.
Read perspectiveAI-assisted implementation makes clarity about the product more valuable, not less.
Read perspectiveUseful observability starts with the question support will ask when a customer gets stuck.
Read perspectiveShared understanding matters most when it turns into inspectable work and clearer decisions.
Read perspectivePutting a person after the model does not explain how that person can make a good decision.
Read perspectiveA faster draft is useful only if the complete task becomes better.
Read perspectiveDecide which customer tasks must work before deciding which technical numbers to put on a dashboard.
Read perspectiveMoving records is not enough. The people using them must still understand and trust what they see.
Read perspectiveAccount creation is a system milestone. It may be nowhere near the moment a customer receives value.
Read perspectiveWho can see, change, and approve something is a product decision before it is an implementation detail.
Read perspectiveThe most useful technical conversation often happens before there is a specification to estimate.
Read perspectiveA sequence of features is less useful when nobody can explain what would change the sequence.
Read perspectiveStart by separating what is unfinished, what is uncertain, and what is genuinely blocked.
Read perspectiveThe recovery path often tells you more about a product than its perfect demonstration.
Read perspectiveConnecting two APIs is only the beginning. Decide what each side believes, owns, and can correct.
Read perspectiveBefore replacing a system, identify the product change the current one is preventing.
Read perspectiveA release plan should explain who can act when the first real customer needs help.
Read perspectiveThe useful question is which part of the experience your business needs to control.
Read perspectiveRepeated questions reveal the work your interface is leaving to people.
Read perspectiveBefore estimating the screens, agree on the change those screens are supposed to make.
Read perspectiveA new build, a difficult problem, or a longer-term product partner. Let’s talk about what you need.
