Lean Inception
The Lean Inception method gives you a great place to start from - defining and developing an MVP.
Why use Lean Inception?
When we go into our workshops, we’re often faced with very little information and several stakeholders with different priorities and ideas about what needs to be done. It’s not possible to immediately make everyone happy, so our process helps us create a constructive dialogue between members of the same team who come into the workshop with different needs.
Through compromise and facilitated discussions, it gives us all a common goal to work towards and levels out everyone's expectations. This board is our interpretation of the Lean Inception approach and represents our learned experiences so far. We use it as a base and continue to modify it based on each workshop's needs. It helps us define the problem in the best possible way and get to a clearly defined MVP.
How is Lean Inception different from a Design Sprint?
We were interested in the problem-solving approach in the Design Sprint and the Lean Inception. The methodology was based on so much real experience from their creators that we wanted to give it a shot.
The Design Sprint method solves a different kind of issue than the Lean Inception one. The questions are different, as is the end result. As we went through them, we realized that the demands coming from our clients wouldn’t really fit either method - but a combination of both worked like a charm. Sometimes we also need to adapt the length of the workshop. We don't always have the 5 days both methodologies ask for - so we make it work in 3 days by cutting some of the activities. It's a bit more intense but works well both for our clients and us.
For example, we normally don't need to calculate the effort, time and cost - we try to go into the workshop with a ballpark figure regarding these estimates. However, this is an individual approach that works well for us, as we are in charge of both facilitating and developing the MVP in question.
The Lean Inception method gives you a great place to start from - defining and developing an MVP. This was most of what we needed to do. But in the end, it leaves you without a visual idea of what needs to be done. We feel that the visual representation of the problem being solved is like the cherry on top of a well defined MVP. That is where you can see that everyone is on the same page and you all understand the MVP properly. So we borrow the sketching part of the Design Sprint and incorporate it into our approach.
This template was created by RUBICON.
Get started with this template right now.
Retrospective in the Island of Golocans
Works best for:
Retrospectives, Meetings, Agile Methodology
The Retrospective in the Island of Golocans template offers a creative and imaginative setting for retrospectives, transporting participants to a fictional island setting. It provides elements for reflecting on past iterations, sharing insights, and brainstorming improvements. This template enables teams to step outside their usual environment and approach retrospectives with a fresh perspective. By promoting creativity and storytelling, the Retrospective in the Island of Golocans empowers teams to engage in meaningful discussions, generate new ideas, and foster a culture of innovation effectively.
SAFe PI Planning
Works best for:
Agile
SAFe PI Planning is a collaborative event for Agile Release Trains to plan and align on program increments. It provides a structured framework for setting objectives, identifying dependencies, and sequencing work. This template facilitates PI Planning sessions, enabling teams to visualize their commitments and coordinate cross-team dependencies effectively. By promoting transparency and alignment, SAFe PI Planning empowers Agile organizations to deliver value at scale with predictability and quality.
DMAIC Analysis Template
Works best for:
Agile Methodology, Design Thinking, Operations
Processes might not seem like the funnest thing to dive into and examine, but wow can it pay off—a more efficient process can lead to serious cost savings and a better product. That’s what DMAIC analysis does. Developed as part of the Six Sigma initiative, DMAIC is a data-driven quality strategy for streamlining processes and resolving issues. The technique is broken into five fundamental steps that are followed in order: Define, Measure, Analyze, Improve, and Control.
Blameless postmortem canvas
Works best for:
Agile
The Blameless Postmortem Canvas is a structured framework for conducting blameless postmortems following incidents or failures. It provides sections for documenting the timeline, impact, root causes, and actionable insights. This template promotes a blame-free culture of learning and improvement, enabling teams to analyze incidents objectively, identify systemic issues, and implement preventive measures. By fostering transparency and accountability, the Blameless Postmortem Canvas empowers organizations to learn from failures and enhance resilience, driving continuous improvement and reliability.
Start, Stop, Continue Retrospective by Laura Timmins
Works best for:
Retrospectives, Agile Methodologies
The Retrospective template offers a flexible and customizable framework for teams to reflect on past experiences and identify areas for improvement. It provides elements for sharing successes, challenges, and action items. This template enables teams to facilitate constructive discussions, generate insights, and drive continuous improvement. By promoting reflection and collaboration, the Retrospective empowers teams to optimize performance and achieve their goals effectively.
To-do List Template
Works best for:
Project Management, Education, Decision Making
A to-do list helps teams manage, organize, and prioritize their upcoming tasks. As a result, they can improve time management and streamline work operations. Using Miro’s to-do list template, teams create interactive, collaborative, and user-friendly task lists.