HEART Framework Template
Evaluate customer satisfaction and ensure that you are providing real value with the HEART Framework. Measure Happiness, Engagement, Adoption, Retention, and Task Success.
About the HEART Framework template
The HEART framework is a UX framework developed by Google. It turns the often-fuzzy idea of user experience into a set of measurable, actionable metrics, helping your product win new users and keep current active users loyal.
What is the HEART framework?
User experience teams often find it challenging to develop useful metrics for success. It’s an even greater challenge for teams at large companies. You can measure user experience at a small scale through user research, surveys, and focus groups. But as your company grows, your customer base gets too large for these methods to always be reasonable.
Google developed the HEART framework to tackle the problem of quantifying user experience. The HEART framework is a set of user-centered metrics you can use to measure user experience at any scale — then draw on those metrics repeatedly throughout the product development lifecycle.
What does HEART stand for?
HEART stands for Happiness, Engagement, Adoption, Retention, and Task Success.
Happiness is a subjective measure of attitude or satisfaction. It’s often quantified through user surveys and bolstered via case studies.
Engagement measures how much the user interacts willingly with a product. Depending on the product, it can be measured by your number of active users in a day, week, or month or your net promoter score (NPS).
Adoption is the rate of new users gained in each time period, usually monthly.
Retention measures how long each customer remains an active user before dropping off. Churn, the other side of the coin, measures how many active users go inactive each month.
Task Success is either the average time it takes a user to complete a task in your product or the percentage of tasks users successfully complete.
What are goals, signals, and metrics in HEART?
Goals, signals, and metrics are the core of the HEART process. All five areas of the HEART acronym must be connected to a goal, at least one signal, and at least one metric.
A goal is a statement of what you’d like your product to achieve in that area of HEART. It’s important for goals to be general, not defined by existing metrics. Some examples:
Happiness goal: “We want logging into our product to feel relaxing and supportive.”
Engagement goal: “We want users engaging with our app every day.”
Adoption goal: “We want our user base to grow continuously.”
Retention goal: “We want as little churn as possible.”
Task Success goal: “We want to minimize abandoned tasks across all user segments.”
Next, come up with one or more signals for each goal. Signals are signs you can look for to show you whether you’re on track to achieve your goal. Examples might be:
Happiness signals: Positive feedback from with real users, recommendations, few complaints.
Engagement signals: Large amount of user-generated content, users spending more time in the app, users logging in multiple times per day.
Adoption signals: More downloads, new features adopted quickly, paid features generating more revenue.
Retention signals: More subscription renewals, fewer users going inactive.
Task Success signals: Few abandoned tasks, few complaints about time-to-completion.
Finally, decide on metrics you can use to objectively measure each signal. For example:
Happiness metrics: Number of five-star reviews, NPS.
Engagement metrics: Daily/weekly/monthly active users.
Adoption metrics: New users per day/week/month, revenue from paid users.
Retention metrics: Retention rate, churn rate.
Task Success signals: Tasks completed per user, average completion time.
The HEART framework is not prescriptive. You’re free to come up with whatever goals, signals, and metrics make the most sense for your business and product.
How do you create a HEART model?
Start by selecting the HEART framework template. Then follow these steps:
Decide on your scope. Are you evaluating your whole product, certain features, or just one feature?
Get familiar with the template. The five areas are listed at the top of the table. Goals, signals, and metrics run down the left-hand side.
Fill out goals for each column. Brainstorm or with your team to settle on five goals.
Fill out signals. Signals can be either positive (something you want to see) or negative (something you’re on the right track if you don’t see).
Fill out metrics. Pick metrics you can use to quantify each signal.
Alternately, you might choose to come up with goals, signals, and metrics for each column before moving on to the next one. Either approach works!
Once finished, you can share your framework with your team or anyone else who would benefit from seeing the information by sending them the board link.
When should you use the HEART model?
The HEART model is generally used to measure larger scale projects, but it works for any size project or team. Use it whenever you want to ensure you’re making your customers happy and providing them with real value.
What are UX frameworks?
A UX framework is a set of assumptions and steps a team can use to build a user experience. UX frameworks such as HEART also monitor and refine user reactions to a product once it’s already out in the world.
What is a KPI in UX design?
A KPI, or key performance indicator, is a measurable variable a UX team can use to determine how their user interface is performing with customers. In the HEART framework, it’s called a metric. Examples include monthly active users and time to complete tasks.
What is UX tracking?
UX tracking is the act of using tools to follow how users interact with your product. It encompasses a wide range of technology, including website analytics, click-tracking, and A/B testing apps.
How do you use the HEART framework?
The easiest way is to use this free template. Alternatively, create a table and label one axis with Happiness, Engagement, Adoption, Retention, and Task Success. Label the other axis with Goals, Signals, and Metrics. Then, work with your UX team to fill in each cell.
Get started with this template right now.
User Interview Template
Works best for:
Desk Research, Product Management
A user interview is a UX research technique in which researchers ask the user questions about a topic. They allow your team to quickly and easily collect user data and learn more about your users. In general, organizations conduct user interviews to gather background data, to understand how people use technology, to take a snapshot of how users interact with a product, to understand user objectives and motivations, and to find users’ pain points. Use this template to record notes during an interview to ensure you’re gathering the data you need to create personas.
Midnight Sailboat Retrospective
Works best for:
Retrospectives, Meetings, Agile Methodology
The Midnight Sailboat Retrospective template offers a metaphorical journey through past experiences and future aspirations, likening the retrospective process to a midnight sailboat voyage. It provides elements for reflecting on challenges faced, lessons learned, and goals for the future. This template enables teams to navigate uncertainties, chart a course for success, and foster a culture of resilience. By promoting reflection and metaphorical thinking, the Midnight Sailboat Retrospective empowers teams to overcome obstacles, embrace change, and sail towards their goals effectively.
Meeting Notes Template
Works best for:
Business Management, Meetings
When your meeting is a success (and Miro will help make sure it is), participation will run high, brilliant ideas will be had, and decisions will be made. Make sure you don’t miss a single one — use our meeting notes template to track notes and feedback in a centralized place that the whole team can access. Just assign a notetaker before the meeting, identify the discussion topics, and let the notetaker take down the participants, important points covered, and any decisions made.
Bang for the Buck Template
Works best for:
Project Management, Strategic Planning, Prioritization
The name pretty much says it—this Agile framework is all about helping you maximize efficiency by powering collaboration between product managers and dev teams. Together you can go over each to-do on the project agenda and evaluate them in terms of costs and benefits. That way you can prioritize tasks based on how much bang for your buck they deliver. This template is great for teams and organizations that want to make a strategic plan to tackle an upcoming sprint.
Product Canvas Template
Works best for:
Desk Research, UX Design
Product canvases are a concise yet content-rich tool that conveys what your product is and how it is strategically positioned. Combining Agile and UX, a project canvas complements user stories with personas, storyboards, scenarios, design sketches, and other UX artefacts. Product canvases are useful because they help product managers define a prototype. Creating a product canvas is an important first step in deciding who potential users may be, the problem to be solved, basic product functionality, advanced functionalities worth exploring, competitive advantage, and customers’ potential gain from the product.
Block Diagram Template
Works best for:
Mapping, Software Development, Diagrams
Use this template to illustrate technical systems. Blocks represent important objects in the system, and arrows demonstrate how the objects relate to each other. Perfect for engineers, workflow managers, or anyone trying to build a better process.