1. Tadaa OKRs

Goal
An objective is what you want to accomplish. It is significant, concrete, action-oriented and inspirational. Key Results are how you will accomplish it. They are specific, time-bound, aggressive yet realistic, measurable and verifiable.

Who
Company-wide employees should help determine the company OKRs to ensure easy adoption by all teams.
‍
How (example)
O: Achieve carbon footprint neutrality
KR1: Reduce the supply chain footprint to 100% zero waste
KR2: Increase compostable material to 90%
KR3: Pay 100% carbon offset for calculated carbon dioxide emissions

Deliverables
✅ Write 2-4 OKRs using the following method:
O: I will ...
KR1: as measured by ...
KR2: as measured by ...
KR3: as measured by ...

2. Product OKRs

Goal
Product OKRs are specific objectives you want to accomplish based on the company-wide OKRs.

Who
Whole product squad: Product Lead, Product Manager, Product designer and Developers

How
1. What’s the product ambition?
2. How does it align with the company vision?

Deliverables
✅ Write 2-4 OKRs using the following method:
O: I will ...
KR1: as measured by ...
KR2: as measured by ...
KR3: as measured by ...

3. User research

Goal
Create a shared knowledge base across all clients. User interviews rely on stories to explore emotions, understand user goals, and assess needs.
‍
Who
Product Designer, Customer success and UX researcher if available
‍
How
The goal of the interview is to gain empathy for the user’s experience. Through that empathy, we can shape the design solutions to fit the use better.
1. Recruit users in advance of the sprint
2. Prepare interview questions
‍
Deliverables
‍✅ A minimum of 5 user interviews (in-person or video) focusing on user experience of the product, likes and dislikes
✅ Knowledge that elicits user stories

4. Client feedback

Goal
Gather information from the multiple platforms we collect client feedback from.
‍
Who
Product Designer, Customer success and UX researcher if available
‍
How
This could be direct (slack, intercom, chatbot on the platform) or indirect (online review on the app. store).
‍
Deliverables
✅ List of feedback,
- categorised from most recurring to least recurring
- with the names of the customer so we can then update them once the pain has been solved

5. Data analysis

Goal
Gather data points from platforms to analyse customer pains
‍
Who
Data team or Product Managers/ Engineers
‍
How
User data: demographics, behaviors, online reviews, NPS scores
Type of product data: user flow, meta data, bounce rates, abandonment rates,adoption rates, heatmaps
‍
Tools
Hotjar -> understand friction points on the platform
Google Analytics/ Heap.io -> create dashboards
‍
Deliverables
✅ Understand the entire customer journey, what works well and what doesn't

6. Problem identification

Goal
Make sure we have a deep understanding of the problems we’re looking to solve.
‍
Who
Product managers with the help of Product designers and Business stakeholders
‍
How
1. What is the problem?
(List the problems you have identified during the research phase)
2. Why do we want to solve this problem?
3. Who are we solving this problem for?
4. What are users currently using to address the need we believe we can manage better?
5. What are the use cases? Jobs-to-be-done?
When ... (situation), I want to .... (motivation), so that I can (expected outcome)
Example: When building a new feature, I want Tadaa to help me map the process so I can visualise the end-to-end product development journey.
‍
Deliverables
‍✅ User journey map with consolidated customer pains for each journey at specific stages

7. Prioritization

Goal
From all the problems we’ve listed in the Job-to-be-Done step, can we define the main use case we want to address and agree on setting other use cases aside?
‍
Who
Product Manager, Product Designer, and Engineers
‍
Deliverables
‍✅ Assess value: prioritisation score based on clear business metrics and strategy set in OKRs
✅ Estimate effort via engineering complexity
✅ Set priorities using the Effort/ value matrix: must-have/ should-have/ nice-to-have
✅ Keep must-haves (store the rest for future sprints)

8. Market research

Goal
Competitor analysis and other websites benchmarks should be made to understand how others have already treated the same subjects and detect standards and patterns.
‍
Who
Product designer
‍

How
”Good artists borrow, great artists steal.”
What are others doing well that we could steal or draw inspiration from? They can be in the same or different industries.
‍
Deliverables
‍✅ Benchmark with 3-5 precise ideas

9. Wireframe

Goal
‍Ideate on the problem identified and start creating the first sketch to identify potential solutions to solve it
‍
Who
The whole Product team gets together. This includes the Engineering team to do feasibility checks.
‍
How
Workshop session. We now have a framed idea of what we’re trying to build and for whom. We’ve drawn inspiration from other great ideas (see market research).
‍
Deliverables
✅ Crazy 8's
Fast sketching exercise where people sketch 8 distinct ideas in 8 minutes. The goal is to push beyond your first idea, frequently the least innovative, and to generate a wide variety of solutions to your challenge.

10. Test

Goal
Turn your wireframes into prototypes that can be tested. Show it to the users and learn.
‍
Who
Product Designers, Engineers and Product Managers work together to build out the frontend user experience, iterating the design from early-stage concepts to working product.
‍
How
‍1. Early-stage foundational work – nav structure, interaction model, information architecture and user flows.
2. Mid-stage interface design – working with design systems team to appropriately use pre-existing Garden patterns and components, fleshing out interactions, visual design, make sure the design works for accessibility
At each stage, usability tests are done to surface and fix points of friction for users. This reduces uncertainty and also decreases the risk of building the wrong thing.
‍
Tools
Lookback/ UserTesting -> qualitative tests
Calendly -> to organise remote and in-person user tests
Maze -> quantitative tests
‍
Deliverables
✅ Test protocol with goals, hypothesis and scenarios detailed
✅ A prototype that looks good enough to get users to test it without being put off
✅ User test conclusions, hypothesis and scenarios
What are the learnings? What works? What doesn't? What can we do better?

11. Final Design

Goal
Find a solution that’s compelling, technically feasible and one that all stakeholders are aligned with.
‍
Who
Product Designers are lead. May need to pair with Engineers to discuss any ad hoc UX decisions
‍
How
Late-stage design: discuss key interactions, behaviours or design details;
- edge cases,
- zero states,
- error states and prevention,
- creation of assets such as icons and illustrations
‍
Tools
Figma -> To sketch in high-fidelity the final solution
ZeroHeight -> Design system management
‍
Deliverable
‍✅ Final design of working product reviewed by all stakeholders (product & engineering)

12. Development

Goal
‍From specifications to live product.
‍
Who
The Product manager coordinates the product development and go-to-market activities. He is accompanied on this task with the Tech lead, the Engineers and the Product Designers to help on specific issues.
‍
Tool
Linear -> List, monitor and track development tickets, bugs and issues
‍
Deliverables
✅ Inform and communicate clearly with all stakeholders regarding progress and delays
✅ If needed, reshuffle roll-out planning
✅ If compulsory, adjust the live product’s scope

13. QA

Goal
Validate development and prepare product launch.
‍
Who
Product managers, Product Designers, Marketing team and Engineers
‍
How
1. How will we get this product to market?
Briefly describe how this new product will be launched and promoted. Including potential steps. Include t-shirt sizing effort from developers.
2. What are the implications for other teams?
List dependencies or risks for other teams.
3. What factors are critical to success?
Learning from our past experiences what do we need to pay extra attention to?
4. How will we measure success for this product?
Describe what is the expected outcome of the project. What would success be like?
‍
Deliverables
✅ Product has been tested and is fully functional. All bugs have been addressed
✅ List of questions above have been answered for next stage

14. Public Launch

Goal
This is when we "announce" the product/feature.
‍
Who
Product team, Marketing team, Customer Success
‍
How
Determine the contents and timing for the public launch.
‍
Deliverables
✅ Evaluate need for marketing campaign to promote launch
✅ Update users that requested the solution/ highlighted the pain (ask customer success team)

15. Post-launch

Goal
‍Monitor success from live product to lovable product
‍
Who
Product managers, Product Designers, Customer Success and Data team
‍
How
‍1. Talking to users and iterating on the UX
2. Working with PMs and engineers to bring in improvements
3. Partner with support team to get early customer feedback
‍
Deliverables
✅ Follow-up survey with users
✅ Data analysis with success & impact metrics
✅ Monitor customer complaints
✅ Collect list of features to improve for next sprint
✅ Record all our successes, failures and learning to enable continuous improvement, easy review and fast onboarding
✅ Close out document

Conclusion

This is the best-practice process that we've created with the feedback we got from our 200 interviews. We iteratively improve the process every sprint, to make sure we build the best products! They will grow as we expand the team and the platform.


If you have any suggestions or want to learn more, don't hesitate to DM us on slack (link below)!