Serious.Games
AgileFree

Lean Inception

Align your team on a clear and shared product vision in one week.

Duration · 2400 min
Participants · 6–15
Level · Advanced

Lean Inception is a series of collaborative workshops designed to help teams define a clear product vision, identify key personas, and establish essential features for a MVP. This process fosters close collaboration between developers, Product Owners, and stakeholders, ensuring optimal alignment from the outset of the project.

Walkthrough

  1. 1

    Introduction and Objectives

    30 min

    The facilitator begins by explaining the concept of Lean Inception and the importance of team alignment on a common product vision. They briefly present the week's steps and expected outcomes. Participants introduce themselves and share their expectations. This helps create an atmosphere of collaboration and mutual understanding.

    TipUse concrete examples of past successes to illustrate the importance of these workshops.

  2. 2

    Defining the Product Vision

    1 hour

    The facilitator guides the team in formulating an inspiring and concise product vision. Participants work in small groups to propose vision statements, which they then share with the entire group. Together, they discuss and refine these proposals to arrive at a common vision.

    TipEncourage the use of action verbs and measurable outcomes to make the vision more tangible.

  3. 3

    Identifying Personas

    1h30

    Participants identify and describe the key personas who will use the product. Each group works on a different persona, detailing its characteristics, needs, and behaviours. The personas are then presented to the whole group for discussion and validation.

    TipUse images or illustrations to bring the personas to life and foster empathy.

  4. 4

    User Experience Mapping

    2 hours

    The team creates a user experience map to visualise the journey of the personas when using the product. Each step is discussed and documented, focusing on pain points and opportunities for improvement.

    TipUse post-it notes of different colours to distinguish between steps, pain points, and opportunities.

  5. 5

    Identifying MVP Features

    2 hours

    Participants list all potential product features and then prioritise them to identify those that are essential for the MVP. They use criteria such as customer value and technical feasibility to guide their choices.

    TipFacilitate the discussion using an impact matrix to assist in feature prioritisation.

  6. 6

    Planning the Initial Iteration

    1 hour

    The team plans the first iteration of development based on the identified MVP features. They define specific tasks, responsibilities, and a preliminary timeline. This allows development to start with a clear direction.

    TipEnsure that each team member clearly understands their role and responsibilities for the first iteration.

Variants

  • Organise a feedback session with external stakeholders after defining the product vision.
  • Incorporate a creative brainstorming exercise to generate feature ideas before prioritisation.
  • Add a rapid prototyping step to test key concepts with real users.

Debrief guide

  • How does the defined product vision reflect the needs of our users?
  • What were the main challenges encountered during the identification of personas?
  • How did the user experience map influence our understanding of the product?
  • Which MVP features did we prioritise and why?
  • How can we ensure that our initial iteration plan remains flexible in the face of changes?