DML Product Workflow
Define, map and launch your product initiative or epic following these 3 basic frameworks.
- Sessions
- 7
- Steps
- 42
- Last edited
- Sep 25, 2026
- Created by
- Nova
About this process
Define. Map. Launch. Define your product initiative or epic following 3 basic frameworks that will help you prioritize key requirements and provide product direction to your team. This workflow helps you 1) Define your epic or initiative in detail. 2) Map user requirements and activities and 3) build a launch plan. This framework includes: The Initiative/Epic canvas User story mapping Product Launch Strategy Board and 2 additional templates. Add additional sessions, whiteboards, design reviews, tasks, etc - whenever you need them.
The process in detail
7 sessions · 42 stepsDesign sprint
2 steps- 1
How Might We....
- 2
Initial ideas: Concept Sketching/Mockup
Read the full text
1. How Might We....
Considering the solution being discussed, the problem you are trying to solve, and its root cause, use the HMW (How Might We) framework to start a brainstorming session. Think of two potential questions that could unlock two different approaches to perceiving the problem and solution, and add each to a separate sticky note.
2. Initial ideas: Concept Sketching/Mockup
Evaluate the solution requirements and HMW questions to develop a potential design concept. Produce an HTML prototype and pin it to the whiteboard for further discussion.
- Design Sprint
- Next Steps
- 6
- Concept sketching
- 5
- How might we...
- 4
- Intro
- 1
- Let's get everyone in the team on the same page and understand the context of the problem. We will write HMW statements following these steps: 1) Take a sticky note and write your question starting with ' How might we....' 2) Read your HMW 3) Vote
- Process born at Google, that allows teams to align on a specific problem or challenge, generate a lot of potential solutions, and test and learn from real users. This template will help you map and sketch ideas - replacing endless meetings and guesswork with real work and tangible results.
- Start typing here...
- The team
- 2
- Add names and roles.
- Our challenge
- 3
- We are running this design sprint in order to solve [problem]. By the end of this session we will [ result]
Competitors and similar solutions
5 steps- 1
Add competitor products and features to the board
- 2
First evaluation.
- 3
Discuss and evaluate each feature
- 4
Comments and thoughts
- 5
Create a document and analyze competitor strengths, strategic priorities, value propositions, and market opportunities,
Read the full text
1. Add competitor products and features to the board
Identify the top 2–3 competitor products and their core features comparable to the product or feature you are evaluating
2. First evaluation.
Evaluate the competitors and key characteristics identified by the team, gathering online sentiment for each product. Synthesize these findings into an evaluation matrix that rates each feature on a scale from 0 to 5 (0 = missing, 1 = indirect solution, 2–5 = basic to state-of-the-art), explicitly identifying where each competitor holds an advantage.
3. Discuss and evaluate each feature
Rate each feature or characteristic chosen in the previous step on a 1–5 scale for each competitor, highlighting where each leads.
👎1 = Bad implementation and design 👍5 = Great usability, design and implementation
4. Comments and thoughts
Summarize how these insights impact your competitive advantage and outline next steps, identifying potential growth opportunities based on high and low ratings.
5. Create a document and analyze competitor strengths, strategic priorities, value propositions, and market opportunities,
Draft a one-page summary evaluating your solution against key competitors based on identified features and characteristics. Analyze competitor strengths, strategic priorities, value propositions, and market opportunities, then publish the document to the whiteboard
- [PRODUCT] COMPETITOR
- [PRODUCT]
- [PRODUCT] COMPETITOR
- [PRODUCT] COMPETITOR
- [PRODUCT] COMPETITOR
- [FEATURE] or [SERVICE]
- 2
- 3
- 3
- 3
- 2
- 3
- 2
- 1
- [FEATURE] or [SERVICE]
- 2
- 2
- 4
- 5
- 2
- 3
- 4
- 3
- [FEATURE] or [SERVICE]
- 0
- 2
- 1
- 0
- [FEATURE] or [SERVICE]
- 1
- 5
- 4
- 3
- [FEATURE] or [SERVICE]
- [FEATURE] or [SERVICE]
- [FEATURE] or [SERVICE]
- Our product helps (customer segment) who want ( job-to-be-done) by... unlike...
- Their product helps (customer segment) who want ( job-to-be-done) by... unlike...
- $$$
User story mapping
6 steps- 1
Introduction to User Story Mapping.
- 2
Activities.
- 3
Steps.
- 4
Add additional Details.
- 5
MVP or next release.
- 6
Final document
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. Outline 3 to 5 high-level user activities necessary to reach the primary objective, establishing the framework for user story mapping, such as 'checking the account balance' or 'depositing a check'. (Usage process)
These will potentially be transform into "initiatives or epics" or just represent certain user activities.
Below each one, describe the activity or problem if needed (Details).
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 and can help you define some of the requirements.
Thinks about all the steps and use cases.
4. Add additional Details.
You can add additional details by adding a sticky note (use a different color) 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.
Think about the requirements that are:
🔴 Critical: The must-have. Non-negotiable. We absolutely need this or the user will not be able to use/understand/buy our product/service/idea.
🟠Nice-to-have: The high-value features and ideas. The user will be able to reach their objective and the product/idea will still work but adding these additional features could improve their experience, users could pay more for the same product/service or increase their likelihood of converting into paying customers.
Discuss this with your team and make the final decision based on what you want to validate first. Also consider things like costs, time, etc.
Move to the next release those that are nice to have but can't be implemented for this release.
🟣Low: Small impact features and ideas. Ideas and features that aren't necessary but adding them to the product/service will have a small positive impact. Usually not adding these features or ideas will have zero negative effects. Ask yourself: what would happen if our team decides to move forward without adding this feature? If the answer is "nothing" or the negative effects are small this feature or idea belongs here or inside the "indifferent" quadrant.
🟡Indifferent: Customers don't care about it. (Avoid)
6. Final document
Synthesize the whiteboard story map into a structured document detailing all requirements in a clean tabular format
- Find and install the app
- Create an account if you don't have one
- Register and pay
- Find class
- View details and pricing
- Search the app store (by name or category)
- Log in
- Access account
- Enter full name and email
- Enter Password
- Sticky note
Initiative Canvas
11 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.
- 11
Initiative Brief
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.
11. Initiative Brief
Evaluate all notes and the lean canvas to produce an initiative brief covering the business justification, key objectives, and metrics. Include complete user stories, scope boundaries, and detailed engineering/design requirements to enable team execution.
Product Launch/Strategy
7 steps- 1
👀🤩What's changing in the product? Describe the initiative, its benefits, and who it impacts.
- 2
👉 Supporting Materials (documents, links, etc)
- 3
💫 Goals.
- 4
🤑😬🥶 Identify Obstacles, Challenges, Risks, and Budget
- 5
🔥 Describe the strategy.
- 6
🦵👣👇Now be more specific: "The Buyer Journey"
- 7
Plan Your Next 90 Days.
Read the full text
1. 👀🤩What's changing in the product? Describe the initiative, its benefits, and who it impacts.
What's changing in the product?
Describe the initiative, its benefits, and who it impacts.
2. 👉 Supporting Materials (documents, links, etc)
Include designs, graphics, business model canvas, links to videos, training sessions for the team, and any other resources that could be useful during the launch of this initiative.
3. 💫 Goals.
👉Start by defining the goal (objective) of the product initiative. 💫What do you aim to achieve within the next 12 months?
The goal should define the desired outcome and motion the problem that you are trying to solve.
Add a list of 3-10 KPIs.
4. 🤑😬🥶 Identify Obstacles, Challenges, Risks, and Budget
It's essential to recognize and address the potential roadblocks on your path to success. Define obstacles to overcome, limitations, constraints, external forces affecting your strategy, and the budget considerations. Understanding these factors is crucial for crafting a realistic plan. 🤑😬🥶
Include:
Mention any obstacles to overcome and challenges that you could have. This is more an opportunity to predict potential problems that will stop you from validating this initiative and that you may want to evaluate potential ways to mitigate those. You can think about user behavior if your new solution means that they will have to learn about how to use your product differently. If this is, for example, the case, you may discuss with the marketing team or product team to create a video. You also discuss things like fears, new trends in the market, market age and preferences, etc.
5. 🔥 Describe the strategy.
“Strategy describes how a company creates a unique and valuable position through a set of differentiating actions.” — Michael Porter’s
Strategy is more than just a plan; it encompasses your vision, partnerships, brand promise, and values. Your strategy should guide your actions and remain unwavering, even if your plan evolves.
🔥Strategy can be divided into strategic thinking and planning. But there is more to strategy than just having a good plan. In fact, the plan can change, but the vision, the partnerships, the brand promise, and the values can't change.
👉Define how you would achieve your goals in the next year by describing how your company creates a unique and valuable position through a set of differentiating actions.
Discuss and define each section. (7P's of Marketing)
🟢Product: What’s changing in the product? What’s the objective from the product perspective?
🟢Service: What’s changing from the service perspective? Are we adding, changing or removing some of our services? What’s the objective?
🟢Promotion: What are the promotional activities across all marketing channels, including advertising, direct marketing, in-store promotions, social media groups, etc that will be implemented, changed, or removed to support this initiative? What is the objective with those changes?
🟢Physical evidence: What aspects are you changing, improving, removing or adding to help prove that your brand or product exists and that helps you know when a client or user selects the solution? What are you doing to be more aware of what your user sees, hears, does and says? Is there anything that talks about your brand changing? Maybe your packaging, maybe how you are displaying the product, maybe the copy, etc.
🟢Place: Is anything changing about this? Where can users find this? Where can users get informed when they have questions? Where in the process do they get prompted with this new solution? Basically what is changing about where they can find you or learn more about you? Also think about the buying process, and the typical blockers that stop them from making a decision, or changing a behavior. Think about what you are incorporating or could change to guide them through the buying process or help them change a behavior.
🟢Process and People: Finally, discuss if there is anything changing in the process, or how people will connect or support your clients and users. What is the objective here?
Use that space as a place for discussion, and then now define the strategy.
In here is all the things mentioned above but actually thinking about what is possible to implement based on the resources and the timeline you have.
6. 🦵👣👇Now be more specific: "The Buyer Journey"
🦵👣👇How would each strategy support each phase of the customer journey - from 'Exploration all the way to Advocacy.'
If you want you can define this strategy further or skip this section.
This is extremely helpful when you are trying to move forward and grow your product. For example, if this is a new product you will probably want to put more efforts into the exploration phase, where users learn about your product and the problem they have, because they need to do that before they make a decision to choose you. You will probably will not prioritize anything related to product advocacy.
7. Plan Your Next 90 Days.
Now that you've laid the foundation, define your plan for the next 90 days. What actionable steps can you take in the next 30 to 90 days to propel you toward your goals? Prioritize your actions and start implementing them.
By following these steps, you'll be well on your way to creating a marketing plan that not only helps you win but also sets you up for long-term success.
🤫What can you do in the next 30 to 90 days to achieve your goals. Which actions would you implement first?
- Start typing here...
- Start typing here...
- Start typing here...
- Start typing here...
- Start typing here...
- Start typing here...
- Start typing here...
- Start typing here...
- Start typing here...
- Start typing here...
Engineering feedback
5 steps- 1
Hi, thank you for joining this asynchronous session.
- 2
Do you foresee any major issues, risks, or challenges during development? What considerations should we make when designing the solution, and are there any cost-effective ideas you would suggest to reduce development time and complications?
- 3
How confident are you that this will work?
- 4
How hard is this to implement? What is the effort?
- 5
Do you have any other comments, ideas, or requests?
Read the full text
1. Hi, thank you for joining this asynchronous session.
The objective of this session is to 👉 share an initial idea for [problem/challenge] and get feedback from you so we can consider cost-effective solutions, as well as your initial concerns and suggestions, before the design work moves into further detail. 🙏
This is a collaborative session, so it feels a lot like a meeting (without adding another meeting to your calendar), allowing you to participate on your own time before the due date. While I am giving you the flexibility to choose when you participate, I ask that you do so before the 📅 due date. If you don't want to forget, we'll send you a reminder, but you can also add this session to your calendar.
Let me share the proposal with you here 👇 [ ADD A LINK AND VIDEO (Loom/YouTube) ]
You can also find all the documents and information here. Document link
What do you think about the concept?
- Option 1
- Option 2
- Option 3
- Option 4
- Option 5
- Option 6
2. Do you foresee any major issues, risks, or challenges during development? What considerations should we make when designing the solution, and are there any cost-effective ideas you would suggest to reduce development time and complications?
3. How confident are you that this will work?
- Low Confidence
- Medium
- High
- Very high
4. How hard is this to implement? What is the effort?
- Extremely hard / long
- Hard
- Medium
- Easy & Fast
- Very Easy & Fast
5. Do you have any other comments, ideas, or requests?
Do you have any other comments, ideas, or requests?
💬We will review all your feedback, update our requirements and designs accordingly, and get back to you once we have also received feedback from other stakeholders.
Stakeholder feedback/discussion
6 steps- 1
Hi there! Let me share this design with you.
- 2
👩🎨👩🎤 Use Case Evaluation
- 3
📍Usability & Risk Assessment
- 4
🤑 Cost & Implementation Considerations
- 5
👍 Any additional ideas or recommendations?
- 6
Questions or Comments
Read the full text
1. Hi there! Let me share this design with you.
👉Remember that, although you can choose when to participate within the given⚡ timeframe, we do have a 📅 due date for this work. Failing to meet this deadline will result in all future deadlines being pushed back and the project being delayed. I take our goals and timelines very seriously, so please make sure to participate before the due date. Please note that you will NOT be able to participate or collaborate once the due date has passed.
Kindly add this feedback session to your calendar and allocate sufficient time to provide your feedback.🙏
Let me walk your through it 👇 Watch this video /[Read this document].
[ You can add links here like this ]
[ Add a short description about the proposal or concept ]
How do you feel about this design?👇
- Option 1
- Option 2
- Option 3
- Option 4
- Option 5
- Option 6
2. 👩🎨👩🎤 Use Case Evaluation
👉In this design, we considered [specific use case] and prioritized [specific feature]. However, our product often encounters extreme or unique use cases. 👩🎨👩🎤Can you think of any such scenarios that might not be supported by this design? 🧝♂Who are the exceptions? Would anyone need a different approach or solution? Who should not be affected by the changes?
You can skip this step if we are covering all use cases.
3. 📍Usability & Risk Assessment
👉When examining the usability of this design and the user's journey to accomplish [specific task], can you identify any potential gaps or risks?
👉Are there any other limitations, risks, or challenges you would like to share with us? 🤔 Do you foresee any risks that would require immediate intervention or mitigation? What is your main concern with this initiative, if any? What are the limitations that based on your experience exist or should be considered now?
Instructions: 👇Add one per sticky note. Please add one suggestion per sticky note, keeping it concise. If a risk or challenge isn't clear, I'll reach out to you or schedule a meeting to gain a better understanding. It's crucial that each sticky note contains only one suggestion to facilitate voting using emojis. Feel free to use the (🔥) emoji to mark suggestions as high-priority.
4. 🤑 Cost & Implementation Considerations
👉As designers, we aim to develop the best solution for our clients while also considering the cost and potential challenges during implementation. Is there anything you believe 😶should be changed or removed to reduce costs or ease the implementation and distribution phases? How can we reduce costs? If you could remove one thing, what would you exclude from the scope to cut costs?
Skip this step if you think is design can be implemented and distribute easily and you don't have any suggestions.
5. 👍 Any additional ideas or recommendations?
Please add your ideas and suggestions below.
Use one sticky note per idea and keep it concise. You will also be able to view and interact with others' suggestions and ideas, so feel free to vote or organize them using emojis. Use the thumbs up 👍 emoji to indicate your liking for an idea.
👀Help me understand your priorities.
Choose 1! ❤ Can you think of one single improvement that could really help our team, clients, increase revenue, or reduce costs? If so, please mark that sticky note with this ❤️emoji so we can see which ideas are important to you. If someone else has added an idea that seems important and you'd like to prioritize it, do the same.
6. Questions or Comments
Add your questions and comments below👇
I will go through all of your comments and answers once the session is closed and will address all of your questions and concerns a few days later. If you have a question that requires an immediate answer, you can contact me through Slack.