Blog
On product, engineering, and the gap between customer feedback and shipped software.
Most product teams build from feature requests. The ones that build the right things build from problems. Here's how to tell the difference — and why it matters more than anything else in your process.
Read →Most teams assume misaligned sprints are a communication problem. They're not — they're a translation problem. Here's where the process breaks and how to fix it.
Read →Acceptance criteria can look fine when you write them. It's when someone tries to build against them that you see the problems. Here's how to fix that.
Read →There's a number buried in your team's sprint history that you've never bothered to compute. It's the amount of money spent building the wrong thing — and it's probably larger than you think.
Read →Manually writing tickets after customer calls is one of the most expensive habits in B2B SaaS. Here's what it actually takes to turn a customer call into a developer-ready Jira or Linear ticket automatically — and why transcription alone doesn't cut it.
Read →Fireflies and Otter.ai are excellent transcription tools — but neither was built to generate engineering tickets. Specc was. Here's how to choose the right tool depending on what your team actually needs after a customer call.
Read →Ambiguous requirements are the #1 cause of sprint failure in B2B SaaS. Here is a battle-tested checklist of eight questions every PM should ask before a customer call ends — and what a ticket looks like when you actually answer them.
Read →