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.
Agile Transition Plan Template
Works best for:
Agile Methodology, Agile Workflows
An Agile transformation roadmap can help you, your team, and your organization transition from rigid compliance-heavy methods to the more flexible Agile way of doing things incrementally. From requirements to integrations to security, you can map out your organization's moving parts as “swim lanes” that you can then update regularly. Use your roadmap as a way to tell the story of how you see your product growing over a period of time. Get buy-in without overselling and keep your roadmap simple, viable and measurable. By using an Agile transformation roadmap, you can avoid getting bogged down in details and instead invest in big-picture strategic thinking.
Mad Sad Glad Retrospective
Works best for:
Brainstorming, Ideation
It's tempting to measure a sprint’s success solely by whether goals and timelines were met. But there’s another important success metric: emotions. And Mad Sad Glad is a popular, effective technique for teams to explore and share their emotions after a sprint. That allows you to highlight the positive, underline the concerns, and decide how to move forward as a team. This template makes it easy to conduct a Mad Sad Glad that helps you build trust, improve team morale, and increase engagement.
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.
Product Discovery Ideation Session
Works best for:
Agile
The Product Discovery Ideation Session template fosters creativity and innovation in product development. By providing a structured framework for brainstorming ideas, exploring user needs, and generating solutions, this template fuels ideation sessions. With sections for user persona development, problem validation, and idea prioritization, it guides teams through the product discovery process, ensuring that solutions are aligned with user needs and market opportunities. This template serves as a catalyst for generating and refining innovative product ideas.
I Like | I Wish | I Wonder
Works best for:
Agile
Feedback is a key part of any project development and crucial to the iterative process.
Easter Egg Retrospective
Works best for:
Agile Methodology, Retrospectives, Meetings
The Easter Egg Retrospective template offers a themed approach to retrospectives, incorporating elements of the Easter holiday. It provides elements for reflecting on past iterations, hunting for hidden insights, and brainstorming improvements. This template enables teams to have fun while addressing serious topics, fostering creativity and collaboration. By promoting a playful yet productive atmosphere, the Easter Egg Retrospective empowers teams to uncover hidden gems, drive improvement, and strengthen team cohesion effectively.