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.
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.
User Story Map Framework
Popularized by Jeff Patton in 2005, the user story mapping technique is an agile way to manage product backlogs. Whether you’re working alone or with a product team, you can leverage user story mapping to plan product releases. User story maps help teams stay focused on the business value and release features that customers care about. The framework helps to get a shared understanding for the cross-functional team of what needs to be done to satisfy customers' needs.
A project scope helps you plan and confirm your project’s goals, deliverables, features, functions, tasks, costs, and deadlines. A project manager and team should develop a project scope as early as possible, as it will directly influence both the schedule and cost of a project as it progresses. Though project scopes will vary depending on your team and objectives, they generally include goals, requirements, major deliverables, assumptions, and constraints. Aim to include the whole team when you create a project scope to ensure everyone is aligned on responsibilities and deadlines.
Keeping track of your priorities is a big challenge on big projects, especially when there are lots of deliverables. The MoSCoW method is designed to help you do it. This powerful technique is built on a matrix model divided into four segments: Must Have, Should Have, Could Have, and Won’t Have (which together give MoSCoW its name). Beyond helping you assess and track your priorities, this approach is also helpful for presenting business needs to an audience and collaborating on deliverables with a group of stakeholders.
Ready to start building an app? Don’t just imagine how it will function and how users will interact with it—let a wireframe show you. Wireframing is a technique for creating a basic layout of each screen. When you wireframe, ideally early in the process, you’ll gain an understanding of what each screen will accomplish and get buy-in from important stakeholders—all before adding the design and content, which will save you time and money. And by thinking of things in terms of a user’s journey, you’ll deliver a more compelling, successful experience.
Official 5-Day Design Sprint
The goal of a Design Sprint is to build and test a prototype in just five days. You'll take a small team, clear the schedule for a week, and rapidly progress from problem to tested solution using a proven step-by-step checklist. Steph Cruchon of Design Sprint created this template for Miro in collaboration with design sprint gurus at Google. This Design Sprint template is designed specifically for remote sprints so you can run productive and efficient sprints with colleagues around the world.