Feature Planning Template
Create a clear and repeatable process 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.
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.
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.
In our hectic world, it can be hard to plan out a schedule and stick to it. Whether you’re rigorous about scheduling or you struggle to keep your calendar updated, you’ll benefit from a weekly planner. A weekly planner is a schedule of your plans and activities over a week. It enables you to manage your time, track tasks, and organize your team by day. Unlike most paper planners, which are not personalizable, you can change up this weekly planner to create an agenda that fits your needs.
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.
A timeline is a visual tool that chronologically plots out projects step by step. It’s an ideal tool for your team to tell stories (such as an overview of events in your organization) and visualize your projects or processes. The Timeline Workflow template is perfect for any project that relies on visual content. You may find it beneficial to use with your team and also to share with other stakeholders or clients to keep them in the loop on your progress.
User flows are diagrams that help UX and product teams map out the logical path a user should take when interacting with a system. As a visual tool, the user flow shows the relationship between a website or app’s functionality, potential actions a user could take, and the outcome of what the user decides to do. User flows help you understand what a user does to finish a task or complete a goal through your product or experience.
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.
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.