Feature Planning Template
Use our Feature List Template to develop a process for building your feature so you can hit the ground running. Create a clear and repeatable process now for developing new features.
About the Feature Planning template
What is Feature Planning?
Designing a feature is no small feat. At any point during the process, a variety of teams, stakeholders, timelines, and constraints may come into play. The steps are numerous: everything from prototyping to gathering feedback. And then, of course, you have to create documentation along the way.
Feature Planning allows you to develop a process for building your feature so you can hit the ground running. As you create your product or iterate on it, you can have a clear process in place that allows you to save time.
What steps should you take to engage in Feature Planning?
Step 1 - Gather resources and build a timeline. Start by ensuring you know which stakeholders are going to be involved in the project, what budget you have to work with, and whether there are any key deadlines. Get everyone in the same room to have an initial meeting, ensuring your team is on the same page. Agree on a goal for your feature, and decide on any metrics that will show whether you’ve reached your goal.
Step 2 - Map out your feature. Think about user flow and use cases. Don’t try to sketch out any designs just yet. Instead, concentrate on understanding your user, their needs, and why they might want this particular feature.
Step 3 - Prototype. Now that you have your map in place, you can start designing the actual feature. Sketch it out. Don’t be afraid to get creative.
Step 4 - Gather feedback. Give all your stakeholders enough time to review. Compile your feedback so you can come back to the table and iterate if necessary. Solicit comments on your design and UX copy.
Step 5 - Iterate!
Step 6 - Build your feature. Once you’re confident in your design, you can go ahead and build the feature itself.
How do you use the Feature Planning template?
Start with our pre-made template, making any changes you’d like to suit your particular needs. Invite team members to join your board and collaborate. Use the @mention or video chat if you need to get input from others. You can upload other file types such as documents, photos, videos, and PDFs to store all the relevant information in one place. You may also find it useful to link to or embed other boards such as the Product Roadmap or Communication Strategy.
Who should use the Feature Planning template?
Anyone who’s involved in the development, release, testing, and promotion of features can use the Feature Planning template. This is likely to include members of the product, engineering, marketing, and sales teams.
Get started with this template right now.
Canvas Playground Template
Works best for:
Templates
The canvas playground template is the ultimate way to explore all the features that make up Miro's Intelligent Canvas. This dynamic and interactive space is designed to help you get work done faster while engaging your team. From AI creation and Sidekicks to intelligent widgets, this template allows you to try it all and discover how these capabilities can streamline your workflow and enhance collaboration.
5S Template
Works best for:
Strategy and Planning, Productivity
The 5S Template offers a systematic framework based on the renowned 5S methodology: Sort, Set in order, Shine, Standardize, and Sustain. Originally derived from Japanese manufacturing practices, this template provides clear directions to help teams optimize workspaces. A standout benefit of using this template is its capacity to drastically improve efficiency. Every resource and tool is positioned for maximum productivity by guiding users through decluttering and organizing, reducing time wastage, and enhancing overall workflow.
Penny Game
Works best for:
Agile
The Penny Game is a simulation exercise that illustrates the impact of batch size and work in progress on cycle time and throughput. By tracking the flow of pennies through a production system, teams learn how to identify bottlenecks, optimize processes, and improve efficiency. This template offers a practical way to explore Lean principles and drive continuous improvement, empowering teams to streamline their workflow and deliver value more predictably.
Strategy Diamond Template
Works best for:
Leadership, Operations, Strategic Planning
To achieve key objectives, every business assembles a series of strategies. But what elements should you consider when building a strategy? A strategy diamond is a collection of elements forming a coherent business strategy. These elements include: Arenas, Differentiators, Vehicles, Staging, and Economic Logic. Most strategic plans focus on just one or two of these elements, creating gaps that might cause problems for your business later on. A strategy diamond can help you stay focused and ensure you’re fulfilling all of your business’s needs rather than one or two.
Easter Egg Retrospective
Works best for:
Agile Methodology, Retrospectives, Meetings
The Easter Egg Retrospective template offers a themed approach to retrospectives, incorporating elements of the Easter holiday. It provides elements for reflecting on past iterations, hunting for hidden insights, and brainstorming improvements. This template enables teams to have fun while addressing serious topics, fostering creativity and collaboration. By promoting a playful yet productive atmosphere, the Easter Egg Retrospective empowers teams to uncover hidden gems, drive improvement, and strengthen team cohesion effectively.
Quick Retrospective Template
Works best for:
Education, Retrospectives, Meetings
A retrospective template empowers you to run insightful meetings, take stock of your work, and iterate effectively. The term “retrospective” has gained popularity over the more common “debriefing” and “post-mortem,” since it’s more value-neutral than the other terms. Some teams refer to these meetings as “sprint retrospectives” or “iteration retrospectives,” “agile retrospectives” or “iteration retrospectives.” Whether you are a scrum team, using the agile methodology, or doing a specific type of retrospective (e.g. a mad, sad, glad retrospective), the goals are generally the same: discovering what went well, identifying the root cause of problems you had, and finding ways to do better in the next iteration.