The single biggest mistake most teams make is creating a persona that is a fictional character instead of a tool for making decisions. The document becomes a gallery of stock photos and demographic data that feels productive to create but is useless when it’s time to write copy, prioritize features, or map out a customer journey.
The most common version of this is the persona built on shallow demographics. It describes a person’s age, income, and hobbies, but not their motivations, their anxieties, or the real problem they’re trying to solve. Your team can’t do much with "is 35-45 and likes hiking." It doesn’t tell you why they would choose your product over a competitor’s. This happens because demographics are easy to get, but they don’t explain the "why" behind a purchase. The fix is to shift from what your customer is to what your customer wants to accomplish.
Another frequent mistake is creating the persona in an ivory tower. The marketing team goes off, does some research, and comes back with a polished deck. The problem is, your customer service and sales teams have a much richer, more nuanced understanding of your customers because they talk to them every day. When their real-world knowledge clashes with the official persona document, they’ll trust their own experience and ignore the document. The cost is a lack of team alignment. The fix is to make it a collaborative process from the start.
But the most critical error is creating a persona that isn’t tied to a clear action. Instead of a static description of a person, what you really need is a dynamic description of their problem. On an episode of New Frontier (AI & Ecommerce), Marcelo Calbucci explained Amazon’s best-kept corporate innovation secret for this: the PRFAQ framework. Instead of a persona, you write a Press Release for your finished product and a list of Frequently Asked Questions a customer would have. This forces your entire team to start with the customer’s perspective and define what success looks like for them. Marcelo notes that you can’t just hand this off to AI; it requires deep critical thinking about the user’s world. The PRFAQ becomes a guiding star for the whole product development process, making the customer’s needs impossible to ignore.
A great persona document is less a portrait of a person and more a shared manual for how to solve their specific problem effectively.