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.
Lean Procurement Canvas
Works best for:
Agile
The Lean Procurement Canvas is a visual tool for optimizing procurement processes by applying Lean principles. It provides a structured framework for defining customer needs, identifying waste, and streamlining procurement activities. This template enables procurement teams to visualize their processes, identify improvement opportunities, and enhance efficiency and effectiveness. By promoting transparency and collaboration, the Lean Procurement Canvas empowers organizations to deliver value through optimized procurement practices.
OKR Drafting Board
Works best for:
Agile
The OKR Drafting Board (New) is a visual tool for defining and tracking Objectives and Key Results (OKRs). It provides a structured framework for setting ambitious goals, defining measurable outcomes, and aligning teams around shared objectives. This template enables organizations to articulate their strategic priorities, track progress transparently, and foster accountability and alignment across teams. By promoting focus, alignment, and agility, the OKR Drafting Board empowers organizations to achieve breakthrough results and drive continuous improvement.
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.
Lean Coffee: Meetings without Agendas
Works best for:
Agile
Lean Coffee: Meetings without Agendas is a collaborative meeting format that fosters open dialogue and emergent topics. Participants suggest discussion topics, vote on them, and engage in time-boxed conversations. This template provides a structured framework for facilitating Lean Coffee sessions, enabling teams to prioritize topics, share insights, and make decisions collectively. By promoting inclusivity and adaptability, Lean Coffee empowers teams to address issues efficiently and drive continuous improvement.
Agile Marketing KANBAN
Works best for:
Agile, Kanban
The Agile Marketing KANBAN template adapts Kanban principles to the marketing domain, enabling teams to manage campaigns, tasks, and workflows efficiently. It provides visual boards for planning, prioritizing, and tracking marketing activities, ensuring alignment with strategic goals and timely delivery of campaigns. With customizable columns and swimlanes, this template empowers marketing teams to visualize work, limit work in progress, and optimize their processes, driving agility and effectiveness in marketing operations.
Backlog Refinement with Jira Template
Works best for:
Agile, Backlog Refinement
The Backlog Refinement with Jira template in Miro improves collaboration among team members. It provides a visual and interactive space for teams to review, prioritize, and clarify upcoming work items together in real time. This collaborative approach ensures alignment on priorities and details, leading to a more organized and efficient workflow. The seamless integration with Jira automatically syncs all changes, reducing the need for manual updates and keeping both platforms up-to-date.