Product and engineering guides
Latest guides
What to Ask Your Development Team Every Week
A practical weekly agenda for a non-technical owner: the four questions that cannot be answered with a confident paragraph, and what a real answer sounds like.
"It's 90% Done" and What That Actually Means
Why "nearly finished" is the most expensive sentence on a software project, what is usually left when it is said, and how to check it without technical knowledge.
How to Tell If a Software Project Is Really Behind
The difference between a project that is hard and a project that has stopped, and the four signals that separate them without anyone having to read code.
How to Read a Sprint Report Without Being Technical
What each part of a sprint report is measuring, which parts can be gamed, and the three things worth looking at if you only have five minutes.
How to Plan an Omnichannel Customer Experience
A buyer-focused guide to an omnichannel customer experience: understanding the opportunity, managing risk, and learning how to preserve identity, intent, status, and service context across web, mobile, messaging, and staff channels.
Customer Feedback System: Channels, Workflow, and Closed Loop
A practical guide to customer feedback system covering customer journey and service operations, risk, measurement, and clear next steps.
Building the product for what comes next
We would rather deliver one product that holds up than three that have to be rebuilt. That standard is the same on every project, whatever its size.
Ali Boran GazelCEO