What not to include in a persona

When building a persona, you might be confused about what details are essential and what can be omitted to prevent overwhelming team members. The more excessive data the persona contains, the less memorable it becomes.

The main rule is to include only relevant data that can help make design decisions and influence the final product. For example, information about a persona's favorite travel destinations has no value for a taxi app. What really matters here is if the persona values comfort and safety and has a busy schedule on average. In this case, it should be the team's goal to create an app with an intuitive interface that allows users to rate cars and order a taxi in a hurry or on the go.