Lean Inception
We were interested in the problem-solving approach in the Design Sprint and the Lean Inception.
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.
Get started with this template right now.
20/80 Process Diagram - EOS® Compatible
Works best for:
Diagramming
The 20/80 Process Diagram - EOS® Compatible template is a visual tool for mapping out processes and workflows aligned with the Entrepreneurial Operating System (EOS®) methodology. It provides a structured framework for identifying core processes and key activities that drive business outcomes. This template enables organizations to streamline operations, clarify roles and responsibilities, and enhance accountability. By promoting alignment with EOS® principles, the 20/80 Process Diagram empowers teams to achieve organizational excellence and drive sustainable growth.
Retrospective - Summer
Works best for:
Retrospectives, Agile Methodology, Meetings
The Retrospective - Summer template offers a seasonal and themed approach to retrospectives, perfect for capturing the spirit of summer. It provides elements for reflecting on achievements, experiences, and goals amidst the summer backdrop. This template enables teams to relax, recharge, and recalibrate their efforts for the upcoming season. By promoting reflection and rejuvenation, the Retrospective - Summer empowers teams to celebrate successes, learn from setbacks, and embark on new adventures with renewed energy and enthusiasm effectively.
Agile Product Roadmap
Works best for:
Roadmap, Planning, Mapping
The Agile Product Roadmap template enables teams to visualize and communicate the strategic direction of their product development in an agile environment. It allows for flexibility and adaptation to changing requirements while providing a clear overview of priorities and timelines. By incorporating feedback loops and iterative planning, teams can ensure alignment with stakeholder expectations and deliver value incrementally.
Start, Stop, Continue Template
Works best for:
Retrospectives, Meetings, Workshops
Giving and receiving feedback can be challenging and intimidating. It’s hard to look back over a quarter or even a week and parse a set of decisions into “positive” and “negative.” The Start Stop Continue framework was created to make it easier to reflect on your team’s recent experiences. The Start Stop Continue template encourages teams to look at specific actions they should start doing, stop doing, and continue doing. Together, collaborators agree on the most important steps to be more productive and successful.
Learning Loop Retro Template
Works best for:
Retros, Agile
The Learning Loop Retro template is a powerful tool designed to help teams reflect on their projects by recognizing successes and identifying areas for improvement. This template is part of Miro's Intelligent templates, which streamline workflows and keep teams engaged by integrating AI, interactive tools, and seamless integrations. One key benefit of the Learning Loop Retro template is its ability to drive continuous improvement. By regularly reflecting on their work and identifying areas for enhancement, teams can consistently elevate their performance and achieve better outcomes.
PI Planning Template
Works best for:
PI Planning, Product Management
The Miro PI Planning Template streamlines the Program Increment planning process for Agile teams. It facilitates a collaborative environment, enabling teams to efficiently align on strategies, identify dependencies, and convert decisions into actionable tasks. With features like real-time collaboration, Jira integration, and a centralized workspace, the template supports teams in enhancing efficiency, engagement, and decision-making.