Product initiative + Strategy
Manage your product initiatives. (Product managers). Includes an initiative canvas, product launch,.
- Sessions
- 13
- Steps
- 42
- Last edited
- Oct 4, 2023
- Created by
- Nova
About this process
This workflow is an iterative process in which your team plans and works together to launch a new product or feature. It combines agile methodologies with the initiative canvas. The objective is to provide a workflow to move your product initiatives from an early stage idea all the way to prototyping. The main difference between this template and our other templates is that we use a user story mapping instead of a service design template to map out the process. We also include a template to discuss and define how you will launch a product or feature.
The process in detail
13 sessions Β· 42 stepsUser Story Mapping
5 steps- 1
Introduction to User Story Mapping.
- 2
Activities.
- 3
Steps.
- 4
Details.
- 5
MVP or next release.
Read the full text
1. Introduction to User Story Mapping.
Product-development teams can use story mapping to drive product discussion and align everyone's efforts at any stage of the process. Story maps can be used for new products after discovery work, or for existing products after usability testing. The user story map helps teams illustrates how the solutions can solve the problems research activities have uncovered.
Team norms: π©βππ©βββπ¦Έβββ
2. Activities.
Describe the high-level tasks that users aim to accomplish using the digital product, such as 'checking the account balance' or 'depositing a check'. (Usage process)
These will potentially be transform into "initiatives or epics".
3. Steps.
Steps appear under activities and are arranged sequentially. To complete the activity above, users will go through specific subtasks in the product. In the activity, Deposit a check, the steps are: Enter mobile deposit details, Sign check, Photograph check, Submit deposit, and Confirm deposit. (user tasks)
If you are a product manager, often steps can represent some of the user stories.
4. Details.
You can use details to describe the lowest-granularity interactions the team anticipates users will experience. These are often similar to product requirements like 'Enter email' ' Enter password'
5. MVP or next release.
Identifying the minimum viable product (or next release) and prioritizing it based on well-informed judgment by analyzing the User story map.
Team members can use story maps to visualize what their minimum-viable-product release could or should include, along with how and when to release end-to-end product increments with specific goals and outcomes.
- User Story Mapping
- Activities Initiatives or Epics
- Find and install the app
- Create an account if you don't have one
- Find class
- Register and pay
- View details and pricing
- Steps User stories
- Search the app store (by name or category)
- Log in
- Access account
- Details
- Sticky note
- Enter full name and email
- Enter Password
- Sticky note
- Release 1
- Priorities
- Release 2
- Future releases
Initiative Canvas
10 steps- 1
Overview.
- 2
Leadership + Stakeholders.
- 3
Justification. (Why)
- 4
Objective.
- 5
User story + Acceptance criteria
- 6
Values + Team rituals.
- 7
Metrics.
- 8
Initial Scope.
- 9
Key constraints.
- 10
Data & Analytics.
Read the full text
1. Overview.
π Describe the initiative/project or idea.
Provide a brief summary providing an overview of the epicβs goals, objectives, and desired outcomes.
2. Leadership + Stakeholders.
3. Justification. (Why)
4. Objective.
5. User story + Acceptance criteria
6. Values + Team rituals.
Team rituals.
What artifacts are created from the initiative/project that helps reinforce the project's goals? Celebrate its success? Support continual learning and growth?
7. Metrics.
8. Initial Scope.
How would the project be structured? Are they any key milestones? Are we launching a beta version?
β Must-have list
π Provide dates.
9. Key constraints.
What will influence decisions and possibilities to be closely considered in planning this initiative? Timeline, relationships, budget, governance, etc.
Add sticky notes inside the "can influence" and "beyond scope" section.
10. Data & Analytics.
What type of information will help you achieve your objectives and reach your desired outcome?
Add key highlight here and provide a list of links and resources.
- User story As a [type of user], I want to [perform some task] so that I can [achieve some goal].
- Initiative Canvas
- Justification What problem is being solved by the project/initiative/idea? For who (user)?
- Overview
- Objective What is the objective?Desired outcomes. ( Business value, expected reward, ROI, etc)
- Hypothesis, Assumptions & Risks
- As a [type of user], I want to [perform some task] so that I can [achieve some goal].
- As a [type of user], I want to [perform some task] so that I can [achieve some goal].
- As a [type of user], I want to [perform some task] so that I can [achieve some goal].
- As a [type of user], I want to [perform some task] so that I can [achieve some goal].
- Start typing...
- User persona + User needs
- Acceptance criteria Given [some context] when [some action is carried out] then [a set of observable outcomes should occur].
- Start typing...
- Start typing...
- Start typing...
- Team rituals and celebrations How do you celebrate success?When?
- Values What values will guide the teaming and decision making process?
- Metrics How do we measure success? [Success criteria] Validation Plan (What, When? How often?)
- Start typing...
- Leadership Who is leading this initiative?
- Subject matter expertise?
- Stakeholders Who are the project/initiative stakeholders? What are their priorities?
- Priority
- Estimate
- Priority
- Estimate
- Priority
- Estimate
- Priority
- Estimate
- 2 days
- Low
- Low
- Low
- 5 days
- High
- 2 days
- 4 days
- Scope Definition of the boundaries and extent of the initiative/epicβs impact, specifying the features, functionalities, or areas of the product it will affect. How will the project be structured? Are they any milestones or versions?
- Key constraints What will influence decisions and possibilities and needs to be closely considered in planning this initiative?
- Data & Analytics
- Must-Have
- Can influence
- Links to surveys, newspapers, research sessions, etc.
- Requirement
- Link to resources
- Nice-Have
- Beyond scope
- Definition of done Definition of done for Developers and Product.
- Parking Lot: Opportunities/Asides/etc [Recommendation: Keep this organized by adding 1 or 2]
- Timeline and Milestones Proposed timeline or milestones for the epicβs implementation and delivery.
- Timeline/Estimate
- Add text
- Cost of building
- Add text
- Return & Payback
- Add text
- MM YYYY
- MM YYYY
- Activity or milestone
Inspiration wall
Read the full text
- Inspiration Wall
- Examples/Inspiration/Evidence
Competitive analysis
4 steps- 1
Feature Comparison Canvas.
- 2
Competitive Advantage.
- 3
Leaders vs followers.
- 4
Add a few ideas.
Read the full text
1. Feature Comparison Canvas.
Add competitor products and features to the board.
Add competitor products as well as their core features.
Discuss and evaluate each feature:
You will use a 1 to 5 scale to evaluate each feature. Where:
2. Competitive Advantage.
Add any final thoughts on what this means for your competitive advantage and how you might move forward based on areas of low or high ratings βππ.
3. Leaders vs followers.
Where do you want to be?
Tip: Leaders spend more time leading brainstormings sessions, and testing ideas. (Update your scope/timeline)
4. Add a few ideas.
- Initiative/project Competitive analysis
- Feature Comparison Canvas Core features and ideas
- CompetitiveAdvantage the secret sausage
- YOUR PRODUCT
- [PRODUCT]
- [PRODUCT]
- [PRODUCT]
- [FEATURE]
- 1
- [FEATURE]
- 2
- 4
- [FEATURE]
- 5
- 3
- [FEATURE]
- Leaders vs followers
- [FEATURE]
- $$$ Price
- Leaders
- You
- [FEATURE]
- Your competitor
- Your competitor
- [FEATURE]
- [FEATURE]
- $
- Copycat
- Innovation
- Play-to-win What is their strategy?
- Screenshots What are they doing?
- Branding Logos, Tono of voice, Tag lines, Illustration, Website, etc
- Content: Blog, Social media & Advertising spend
- Other
Design Sprint (workshop)
Initial scoping + Must-Have
2 steps- 1
Define your goal + Must-have.
- 2
Start defining your action plan.
Read the full text
1. Define your goal + Must-have.
Define your goal. What are your goals for the coming year?π₯ Include at least two KPIs. Identify the departments or team members who are responsible and should be held accountable for reaching this goal.
2. Start defining your action plan.
Add your major steps, events, and milestones that must be taken to achieve your goal. How? Use sticky note or tasks If you are using sticky notes use a different color per department or team. (Define each team or Team member and their tasks and responsibilities by adding information inside the π«Team/people section) Task or event duration can be shown by making sticky notes longer.
- Goal
- Timeline
- Choose 3-5 KPIs:
- Goal
- Metric 1: Type here
- Month
- Month
- Month
- Month
- Month
- Month
- Metric 2: Type here
- Team name
- Metric 3: Type here
- Milestone or task
- Metric 4: Type here
- Milestone or task
- Metric 5: Type here
- Must-Have
- Nice-to-have
- Team name
- Team name
- Must-Have
- Avoid/Out of scope
- Team name
Design Sprint - Sketches 1
Execution (3W)
6 stepsDuring this session we will determine which departments and leaders will be involved during this project/product/sprint. Our goal is to create a quick summary of actions and accountabilities - the only "notes" you need to keep from a meeting of an hour or longer.
- 1
Preparation.
- 2
Who is the person accountable for this function?
- 3
Evaluation & Discussion.
- 4
The four questions.
- 5
Communication.
- 6
What?
Read the full text
1. Preparation.
Break the leadership team into groups of two or three.
Ask each group to come up with the 3 to 8 key functions processes that will need to be involved during this project or new sprint.
2. Who is the person accountable for this function?
Start by having each member of the executive team fill in the first blank column by adding the initials of the person they think is accountable for each function or business unite.
Tip:
You want to ensure you promote and hire leaders who:
3. Evaluation & Discussion.
Ensure that everyone knows who is owns each function.
4. The four questions.
Once the team has agreed on the people accountable for each function, consider following these four questions: Do you have more than one person accountable for function?** The rule is that only one person should be accountable, otherwise there will be confusion. Does someone's name show up in more boxes than someone else's?** Do you have any boxes with no names in them?** This sometimes happens when the whole team think is accountable for operations or human resources. Are you enthusiastic about the person you have in each box?** Discuss the four questions and decide where there are glaring gaps in the leadership team. Tip: The rule of accountability means one person must ultimately take ownership, however the person to whom these people report has the overall accountability.
5. Communication.
How is change managed? How is information shared? How is disagreement processed? What type of information will each stakeholder group need?
6. What?
Quick summary of actions and accountabilities.
Notes: The only notes you need to keep and update from a meeting of an hour or longer.
- Week 2: Workload
- Week 1: Workload
- MON
- TUES
- WED
- THU
- FRI
- Who?
- MON
- TUES
- WED
- THU
- FRI
- Who?
- Communication
- Scorecard
- Functions
- Person accountable
- What: (Responsibilities during this project)
- When (Optional)
- Product Manager Allocation: 30h a week
- Product Manager Allocation: 30h a week
- Name
- Days or activities
- What?
- Task
- Product Manager
- add notes...
- Task
- Marketing Allocation: 4h a day
- Marketing Allocation: 4h a day
- Name
- Days or activities
- What?
- Marketing
- Name
- Days or activities
- What?
- Back End Developer
- Name
- Days or activities
- What?
- Sales
- Name
- Days or activities
- What?
- Operations
- Name
- Days or activities
- What?
- Design
- Deadline
- Name
- Days or activities
- What?
- Controller
- Day - Month - Year
- To be done
- Done
- Other
- Blocked
- To be done
- Done
- Other
- Blocked
- Name
- Days or activities
- What?
- Front end developers
- Week 3: Workload
- Week 3: Workload
- Name
- Days or activities
- What?
- MON
- TUES
- WED
- THU
- FRI
- Who?
- MON
- TUES
- WED
- THU
- FRI
- Who?
- Human Resources
- Notes
- Product Manager Allocation: 30h a week
- Product Manager Allocation: 30h a week
- Name
- Days or activities
- What?
- Customer Advocacy
- add notes...
- Marketing Allocation: 4h a day
- Marketing Allocation: 4h a day
- Name
- Days or activities
- What?
- Others
- Name
- Days or activities
- What?
- Others
- Name
- Days or activities
- What?
- Others
- To be done
- To be done
- Done
- Other
- Done
- Blocked
- Other
- Blocked
Prototype (Red pen & green pen)
Retro
5 steps- 1
Retrospective: Reflect on the project and identify past pitfalls, and propose new ideas with this sprint retrospective template.
- 2
What went well?
- 3
What didn't go well?
- 4
What should we start doing?
- 5
Take 1-2 minutes to show some gratitude.
Read the full text
1. Retrospective: Reflect on the project and identify past pitfalls, and propose new ideas with this sprint retrospective template.
Before you start: The mood-o-meter: (Take the temperature in the "project") How is everyone feeling after this project?
- Option 1
- Option 2
- Option 3
- Option 4
- Option 5
- Option 6
2. What went well?
Each team member member writes down what they think went well. Then, discuss those wins as a team.
3. What didn't go well?
Following the same format, each team member shares anything that didnβt go as planned.
What should we π« stop doing? What should we do differently?
πAdd one suggestion per sticky note.
4. What should we start doing?
Any ideas?Once any down-falls have been identified, the team is invited to brainstorm ideas that can be taken to improve problem areas.
5. Take 1-2 minutes to show some gratitude.
Share moments of gratitude and shoutouts for individual team members.ππ
Site map
Product/Feature Launch Checklist
10 steps- 1
Intro:
- 2
Discovery.
- 3
Definition.
- 4
Validation.
- 5
Design.
- 6
Implementation & Development.
- 7
Launching strategy.
- 8
Training.
- 9
Marketing.
- 10
Validation.
Read the full text
1. Intro:
Launching a new product feature or creating a new product requires that a product manager not only prepares user stories and writes a good epic for developers, but also defines a good action plan and strategy for that initiative. This includes having a good communication plan, a way to train users to use the new feature or product, and a launching strategy. Product managers can use this tool as a checklist to think about each phase of the product, from discovery to validation.
Product phases:
2. Discovery.
Answer the following questions and define an action plan to answer them: What do you know about the market? What are your competitors doing? ππ«What do you know about your users and their pain points? πWhat job are they trying to do (Job-to-be-done)? How would they describe their pain? How often do they experience it? How likely are they to change the way they currently respond to that pain? Why should they choose your product?π
3. Definition.
Define the problem you are trying to solve. What should success look like? What is causing the problem? Can you solve the problem or are you creating a painkiller or a distraction? What would be nice-to-have? What are your current assumptions, and how risky are those assumptions?
4. Validation.
By the end of this initiative or product launch, what do you want to learn? How are you going to measure success? How should designers measure success?
5. Design.
Explore what should be simplified and focus on solving the problem first. How would the design look? Would it be good enough to validate this experiment? Provide a success criteria.
6. Implementation & Development.
π₯π₯What do developers need to implement this design? What is non-negotiable? What is the timeline?
7. Launching strategy.
Define how this product or feature should be launched. Do you need to send an email to communicate these changes to current users? Should you write a post or a press release? How will you generate excitement about this product or feature? Create a list of key activities to support your launch.
8. Training.
How will you ensure users don't have to contact your support team to use the new product or feature? Do you need to update your Q&A page? Do you need to create how-to videos? How can you ensure people can find the information they need to achieve their goals?
9. Marketing.
How will you attract new and current users to use this new product or feature? How will you increase your revenue? Think about a promotion or a lead generation campaign.
10. Validation.
Finally, go back to the validation phase and validate your learning. What have you learned? Have you validated some of your hypotheses?
What's next? Would you change something to improve the results?
ππAdd your conclusions inside the conclusion section.
- Mark the areas that don't apply to this initiative.
- Start typing...
- How will your team validate whether this solution effectively addresses the problem or enhances the current solution? Please provide specific metrics when defining this, and collaborate with your data analyst to determine the best validation approach for this solution. Additionally, consider whether the development team needs to implement changes within the platform to track specific results. It might be necessary to create an additional ticket within this epic for that purpose.