[Rebroadcast] Answering Your #1 Question: What's a One-Pager? (With Daphne Funston) - Build with Maggie Crowley Recap

Podcast: Build with Maggie Crowley

Published: 2021-09-10

Duration: 22 min

Guests: Daphne Funston

Summary

The episode revisits the concept of the 'one-pager', a concise document used to define and communicate product problems and goals effectively within teams at Drift.

What Happened

Maggie Crowley revisits a popular episode on the 'one-pager', a tool used at Drift to scope and define problems for product development. The one-pager serves as a well-researched document, distinct from a product requirements doc, focusing on customer problems rather than specific solutions or features. Daphne Funston joins to explain the six sections of a one-pager, emphasizing the importance of storytelling and context in framing the problem and engaging the team.

The one-pager is structured into sections: the story, background and context, goals, requirements and constraints, time box, and concepts and references. Each section serves a specific purpose, from capturing the customer problem to defining project goals and constraints. This structure ensures that all team members, including engineers and executives, have a clear understanding of the project.

Daphne highlights the 'job to be done' framework as a critical aspect of the story section, helping teams focus on the customer's ultimate goal rather than the product itself. This approach encourages broader thinking about the problem and drives innovative solutions.

The episode stresses the importance of using the one-pager as a living document, continually updated with new learnings and decisions throughout the project lifecycle. This practice not only maintains alignment across the team but also serves as a historical record of the project's development.

Maggie and Daphne share practical tips for writing effective one-pagers, such as writing for the reader, anticipating questions, and using visuals to enhance understanding. They emphasize the importance of clarity and conciseness, suggesting that a well-written one-pager should be easy to draft if the problem is well-understood.

The hosts discuss common pitfalls, like trying to fit a project into company priorities without a genuine customer problem. They advise against rushing the storytelling process, as a compelling narrative is crucial for engaging the team and stakeholders.

Finally, they underscore that while the one-pager is a valuable tool, it is not a substitute for good communication and collaboration within teams. The document should enhance conversations and ensure everyone is equipped to contribute to the solution.

Key Insights