Personas for Product Management

Marty Cagan argues that product management is a series of choices about which problems, customers, and features to pursue, and that personas are one of his favorite tools for making them. A persona is an archetype of an imaginary but plausible user, built from interviews and capturing behaviors, attitudes, and goals. Cagan notes that designers and marketers already use personas, but for different purposes, and that product managers should be deeply involved in creating them, early in discovery and without delegating the work. He lists benefits such as prioritization, avoiding the trap of confusing yourself with customers, and rallying the team, alongside pitfalls like refusing to pick a primary persona, relying on untested assumptions, and testing only with the primary persona. The core message is to focus each release on one primary user.

01Key takeaways

• Be actively involved in building personas and attend user interviews yourself rather than delegating the work.
• Start persona work early in discovery so it shapes decisions instead of arriving after designs are underway.
• Choose one primary persona per release, and decide explicitly who the release is not for.
• Treat initial persona hunches as theories and validate them with real users before relying on them.
• Use personas to guard against building for yourself and to align the team on decisions when details are open.
• When testing prototypes, recruit a range of reasonably possible users, not only the primary persona.

02Key sections

What personas are and why they matter

Personas capture what interviews reveal about users and represent a plausible archetype grounded in behaviors, attitudes, and goals. They help product managers make the many tradeoffs that determine product success.

How personas differ across disciplines

Designers focus on user goals and online behavior, while marketers focus on reaching customers and appealing to emotions. Product managers benefit from both perspectives but should not leave persona work to others.

The product manager's role in creating personas

Cagan argues the PM should co-create personas with designers and researchers, attend user interviews, and push for this work early in the process.

Benefits for product teams

Personas help prioritize features, expose the mistake of designing for oneself, clarify distinct user types, and align the team around a shared vision for decisions.

Pitfalls to avoid

Teams often fail by refusing to choose a primary persona, relying on stereotypes instead of real users, or testing only with the primary persona when recruiting for prototypes.

03From the post

“A partnership dedicated to teaching best practices to product teams and product leaders”

04Frameworks mentioned

Summary and takeaways written by PM Atlas; quotes are short excerpts. © the original author.