Feature Canvas Template
Analyse incoming features and ideas keeping in mind users, problems and context.
About the Feature Canvas Template
A feature canvas helps you understand why a new feature was requested.
Before you dive into solution mode and build out a feature, try filling in a feature canvas. The grid layout helps you understand if investing time in a new feature will be valuable to your customers, meet business needs, and make the most of team resources.
Your product team may want to fill in a feature canvas after completing a product canvas. After developing expertise in who your customers are and what your product’s basic functionality should be, it’s time to dig deeper.
Feature canvases allow your team to build context and value propositions for feature requests. You'll make better product decisions by learning more about the risks and opportunities of some advanced features.
Keep reading to learn more about feature canvases.
What is a feature canvas
Before you start working on a concrete solution for a new feature, you need to figure out the “why” that’s motivating it. A feature canvas helps you understand if you should commit to a new feature based on its feasibility and whether it truly solves customer pain points.
A feature canvas typically has seven segments:
An idea description: How would you describe the product feature in 2-3 sentences?
Why: How would implementing this product feature help your customers and your organization?
Contextual situations: When do people need this feature? How do internal and external factors impact how they interact with the feature?
Problems to solve: What are the customer and business problems this feature addresses?
Team capabilities: What resources are immediately available to you to help build new solutions to these problems?
Restrictions and limitations: What obstacles could stop your team from building these features right away?
By considering these different factors, you can decide what feature requests are worth building, and which ones aren’t worth following through. This is the basic version of a feature canvas, which can be adapted for any product feature idea.
When to use a feature canvas
You can use a feature canvas during planning or brainstorming sessions to sell your ideas or align your cross-functional teams on all the details. It can help you and your product team:
Spend more time defining a problem before you commit to building a new solution
Stay user-centered while analyzing new feature requests and ideas
Discard feature ideas that don’t fit current needs, user contexts, or business goals
Find blind spots to address in your user research before building new features
Align teams around the context you need to agree on before you commit to building a feature
You can also use this canvas to plan feature launch activities. These can include re-engaging dissatisfied customers, boosting customer retention and customer loyalty, and campaigns reminding your customers that your company is listening and considering feedback.
Create your own feature canvas
Making your own feature canvas is easy. Miro’s whiteboard tool is the perfect canvas to create and share it. Get started by selecting the Feature Canvas Template, then take the following steps to make one of your own.
Give your team context about why you’re using the feature canvas. This canvas aims to help your team progress from execution mode to analysis mode. Context, customer problems, capabilities, and restrictions all impact whether or how you build out features. Get your product team to fill in this feature canvas in a single session, to understand the reasons for prioritizing certain features over others.
Fill in each numbered segment with sticky notes. Stick to one idea per sticky note. After placing all the notes, nominate a group facilitator to review them to determine what ideas to prioritize, and which to set aside for the near future. Spend 10 minutes on this, then assess whether you’re ready to move onto the next step. If not, try another five minutes. You can useto manage your time during this activity.
Add other segments if needed. An extended feature canvas can have up to 14 segments, including: customer tasks, customer awareness, customer support needs, success criteria, and key activities to deliver customer and business value. You can add rows or columns and change formatting or content inside each block with.
Invite cross-functional team members to review and contribute to your canvas. You can use this feature canvas as a one-off team synchronization tool or maintain it as a living document throughout a product’s life cycle – to implementation and beyond. Revisit it as necessary to update details or add more segments as your team’s analysis and planning needs evolve.
When developing a product roadmap, it can be easy to get lost in the weeds. RICE, which stands for Reach, Impact, Confidence, and Effort, helps you evaluate and prioritize ideas. Brainstorming new ways to delight your customers can be rewarding, but it can also be overwhelming. You and your team might be tempted to dive into the most exciting ideas first, without taking into account the potential lift. The RICE framework allows your team to carefully consider each potential project and assess its feasibility.
It's tempting to measure a sprint’s success solely by whether goals and timelines were met. But there’s another important success metric: emotions. And Mad Sad Glad is a popular, effective technique for teams to explore and share their emotions after a sprint. That allows you to highlight the positive, underline the concerns, and decide how to move forward as a team. This template makes it easy to conduct a Mad Sad Glad that helps you build trust, improve team morale, and increase engagement.
Jobs to be Done
It’s all about a job done right — customers “hire” a product or service to do a “job,” and if it's not done right, the customer will find someone to do it better. Built on that simple premise, the Jobs To Be Done (JTBD) framework helps entrepreneurs, start-ups, and business managers define who their customer is and see unmet needs in the market. A standard job story lets you see things from your customers’ perspective by telling their story with a “When I…I Want To…So That I …” story structure.
Attracting new users, compelling them to try your product, and turning them into loyal customers—it all starts with understanding them. An empathy map is a tool that leads to that understanding, by giving you space to articulate everything you know about your customers, including their needs, expectations, and decision-making drivers. That way you’ll be able to challenge your assumptions and identify the gaps in your knowledge. Our template lets you easily create an empathy map divided into four key squares—what your customers Say, Think, Do, and Feel.
Happiness, Engagement, Adoption, Retention, and Task Success. Those are the pillars of user experience — which is why they serve as the key metrics in the HEART framework. Developed by the research team at Google, this framework gives larger companies an accurate way to measure user experience at scale, which you can then reference throughout the product development lifecycle. While the HEART framework uses five metrics, you might not need all five for every project — choose the ones that will be most useful for your company and project.
Amazon pioneered the working backwards approach based on one of their key principles: celebrating customer obsession. Working backwards is a framework for thinking about a product without a detailed roadmap. Your product team would work back from a mental image of the customer to launch your product in a way that truly serves them. The method requires anyone with a new product or feature idea to articulate its objective as clearly as possible.. If the idea presentation impresses leadership, the next step is to map out what the team needs in order to get to the product or feature launch.