Product Requirements

Why do you write product requirements? We used to write long product requirement documents to communicate the solution we wanted our engineering teams to build. But over time we learned that outlining every detail of the solution upfront leads to overcommitting to solutions before we know whether or not they

It’s easy to spend the majority of your time talking about features. You track features in your backlog. You schedule features on your roadmap. Your customers request features. Your sales team complaints about missing features. Almost everyone thinks of products as features. But if you want to build better

Have you ever rolled out a major product change while one of your sales reps was demo’ing your product to a prospect? I have. It wasn’t pretty. It wasn’t a small change. It was a new home page, completely new positioning, new branding. A whole new identity.

When I work on a product, I think about it all day long. I obsess over it. I love exploring the long view. What will this product look like next year? Five years from now? Ten years from now? I love the challenge of identifying the very next step on