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.
The Team Canvas (Basic)
Works best for:
Agile
The Team Canvas (Basic) offers a simplified framework for aligning on goals, roles, and processes within Agile teams. It provides structure for defining purpose, clarifying responsibilities, and visualizing the working environment. By fostering open communication and shared understanding, this template facilitates collaboration and increases team cohesion, empowering you to create a shared vision and drive collective success.
Fibonacci Scale Template
Works best for:
Agile Methodology, Prioritization, Agile Workflows
When you manage a team, you often have to estimate how much time and effort tasks will take to complete. Try what often works for Agile teams all over the world: Turn to the Fibonacci Scale for guidance. Based on the Fibonacci sequence, where each number is the summation of the two previous numbers (0, 1, 2, 3, 5, 8, 13, 21, etc.), this template can help you build timelines like a champ—by helping make sure that work is distributed evenly and that everyone is accurate when estimating the work and time involved in a project.
Skill Cards
Works best for:
Agile
Skill Cards are a dynamic tool for assessing and developing skill sets within Agile teams. They provide a structured framework for reflecting on strengths, weaknesses, and learning goals, fostering a culture of continuous improvement. With Skill Cards, teams can identify skill gaps, distribute knowledge, and tailor professional development plans, empowering you to cultivate a high-performing team with diverse skill sets and shared expertise.
Christmas Retrospective
Works best for:
Agile Methodology, Meetings, Retrospectives
The Christmas Retrospective template offers a festive and celebratory approach to retrospectives, incorporating the holiday spirit into the session. It provides elements for reflecting on achievements, sharing gratitude, and setting intentions for the future. This template fosters a sense of warmth, togetherness, and appreciation among team members, encouraging reflection on both professional and personal growth. By infusing the retrospective with the joy of the holiday season, the Christmas Retrospective empowers teams to strengthen relationships, cultivate positivity, and drive continuous improvement effectively.
Agile Board Template
Works best for:
Agile Methodology, Meetings, Agile Workflows
Part of the popular Agile framework, an Agile Board is a visual display that allows you to sync on tasks throughout a production cycle. The Agile Board is typically used in the context of Agile development methods like Kanban and Scrum, but anyone can adopt the tool. Used by software developers and project managers, the Agile Board helps manage workload in a flexible, transparent and iterative way. The Agile template provides an easy way to get started with a premade layout of sticky notes customizable for your tasks and team.
All-in-one PI Planning
Works best for:
Agile
The All-in-one PI Planning template streamlines the SAFe Program Increment (PI) Planning process by providing a comprehensive framework for teams to collaboratively plan and align on objectives and dependencies. It integrates essential elements such as PI Objectives, Team Breakouts, and Program Board, enabling teams to visualize, prioritize, and coordinate work effectively. This template empowers Agile Release Trains to deliver value predictably and efficiently, driving alignment and synchronization across the organization.