Idea Funnel Backlog
Prioritise and focus your backlog while keeping ideas fluid.
About the Idea Funnel Backlog Template
An idea funnel backlog can help you and your team prioritize a list of features, bugs, technical work, and knowledge building. These are elements you should identify and keep updated to make your product or service more functional.
Treat your idea funnel backlog as both a roadmap and backlog. The combination of a Kanban Board and backlog helps you and your team prioritize as you approach near-term or end-of-quarter dates.
Keep reading to learn more about idea funnel backlogs.
What is an Idea Funnel Backlog
An idea funnel backlog allows product managers to convert their idea pool into a product backlog, to inform planned feature implementations or user stories.
Product backlogs typically comprise three layers:
Raw requests and ideas (sourced from customer support, product owners, or product teams)
User stories (converted from requests or ideas by a product owner, based on current product strategy or request popularity)
Planned state for user stories (these live on a Kanban Board)
An idea funnel backlog can help you pick new ideas to prioritize for your next sprint. Ideally, the funnel structure helps you turn a large number of ideas into manageable, relevant stories or features to implement.
Teams needing a framework to get out of a reactive sprint planning cycle or task-focused thinking can benefit from an idea funnel backlog. The structure helps teams focus on longer-term goals to gain predictability in tackling idea backlogs.
When to use an Idea Funnel Backlog
An idea funnel backlog can benefit product teams who need help:
Maintaining costs: queues of unvalidated ideas can often become costly, so product teams need to groom and prioritize backlogs regularly.
Focusing on high-value tasks: prioritizing your ideas leads you to work on user stories or features with potentially more significant impact — and minimizes ideas not being actioned.
Encouraging innovation: try to balance validating ideas with maintaining the potential value of anything behind the queue, and not forgetting anything going to the back of the queue.
Create your own Idea Funnel Backlog
Making your own idea funnel backlogs is easy. Miro’s whiteboard tool is the perfect canvas to create and share them. Get started by selecting the Idea Funnel Backlog Template, then take the following steps to make one of your own.
Start adding user stories or product features to your backlog. Click the “Sticky Note” icon on the toolbar or press “N” on your keyboard to enable the tool, to add more Sticky Notes. Don’t worry about prioritizing for this first step — your main goal is to add your team’s relevant ideas to the board as needed.
Give each of your ideas an age limit. For your user story or product feature backlog to stay relevant and timely, agree with your team on an expiration date (for example, three months). If an idea isn’t prioritized in the timeframe, it should disappear from your list over time.
Prioritize your “Must Do” tasks. On this default template, tasks can be organized by “Could Do,” “Should Do,” and “Must Do.” Does your team have their own way to describe and categorize user stories and features? Perhaps “Later,” “Soon,” “Next,” “Now”? Edit the text boxes with your preferred wording.
Add your most urgent or popular backlog items to the sprint area. Add your “Must Do” items to the sprint area on the board, and tackle them in order of “Next,” “Doing,” “Done.” Maybe you’re using Miro on a touch device with a stylus. In that case, you can convert your handwriting to text on Sticky Notes, or add extra notes and symbols for context that doesn’t fit on the Sticky Note square.
Continue to maintain your backlog and prioritize through rapid growth periods. This funnel is your idea management system: it keeps your team aligned and sharing a centralized place for tangible, validated customer feedback, prioritized product feature ideas, and committed product roadmap items for a development pipeline.
Assumption Grid Template
Works best for:
Leadership, Decision Making, Strategic Planning
Someone wise once said that nothing in life is certain. But the waters of the business world? It can seem especially uncertain and unclear. An Assumption Grid can help you navigate those waters and make your decisions confidently. It organizes your business ideas according to the certainty and risk of each — then your team can discuss them and make judgment calls, prioritize, mitigate risk, and overcome uncertainties. That’s why an Assumption Grid is a powerful tool for getting past the decision paralysis that every team occasionally faces.
Works best for:
Mapping, Software Development, Diagrams
Building a website is a complex task. Numerous stakeholders come together to create pages, write content, design elements, and build a website architecture that serves a target audience. A sitemap is an effective tool for simplifying the website design process. It allows you to take stock of the content and design elements you plan to include on your site. By visualizing your site, you can structure and build each component in a way that makes sense for your audience.
Technology Roadmap Template
Works best for:
Agile Methodology, Roadmaps, Agile Workflows
A technology roadmap helps teams document the rationale of when, why, how, and what tech-related solutions can help the company move forward. Also known as IT roadmaps, technology roadmaps show teams what technology is available to them, focusing on to-be-scheduled improvements. They allow you to identify gaps or overlap between phased-out tech tools, as well as software or programs soon to be installed. From a practical point of view, the roadmap should also outline what kinds of tools are best to spend money on, and the most effective way to introduce new systems and processes.
Remote Design Sprint
Works best for:
Design, Desk Research, Sprint Planning
A design sprint is an intensive process of designing, iterating, and testing a prototype over a 4 or 5 day period. Design sprints are conducted to break out of stal, work processes, find a fresh perspective, identify problems in a unique way, and rapidly develop solutions. Developed by Google, design sprints were created to enable teams to align on a specific problem, generate multiple solutions, create and test prototypes, and get feedback from users in a short period of time. This template was originally created by JustMad, a business-driven design consultancy, and has been leveraged by distributed teams worldwide.
Example Mapping Template
Works best for:
Product Management, Mapping, Diagrams
To update your product in valuable ways—to recognize problem areas, add features, and make needed improvements—you have to walk in your users’ shoes. Example mapping (or user story mapping) can give you that perspective by helping cross-functional teams identify how users behave in different situations. These user stories are ideal for helping organizations form a development plan for Sprint planning or define the minimum amount of features needed to be valuable to customers.
Product Roadmap Template
Works best for:
Product Management, Roadmaps
Product roadmaps help communicate the vision and progress of what’s coming next for your product. It’s an important asset for aligning teams and valuable stakeholders – including executives, engineering, marketing, customer success, and sales – around your strategy and priorities. Product roadmapping can inform future project management, describe new features and product goals, and spell out the lifecycle of a new product. While product roadmaps are customizable, most contain information about the products you’re building, when you’re building them, and the people involved at each stage.