Une Obeya est une « grande salle » où la stratégie prend vie.

Illustration Obeya

À l’origine, il s’agissait d’un espace physique dans les pratiques Lean, et aujourd’hui les espaces physiques et numériques se combinent.

Dans l’Obeya, les objectifs, les progrès et les défis sont rendus visibles afin que les dirigeants et les équipes puissent s’aligner, partager des informations et agir rapidement.

Cette clarté accélère la prise de décision et permet de transformer la stratégie en résultats.

Plus qu’une simple salle, l’Obeya est une manière de travailler.

Elle renforce la confiance, la concentration et la collaboration.

Elle connecte les dirigeants aux équipes en temps réel.

Chacun voit la vision globale, avance dans la même direction et contribue au succès commun.

An Obeya is a "big room" where strategy comes to life.

Illustration Obeya

It began as a physical space in Lean practices, and today physical and digital rooms blend together.

In the Obeya, goals, progress, and challenges are made visible so leaders and teams can align, share insights, and act quickly.

This clarity speeds up decisions and helps strategy turn into results.

More than a room, the Obeya is a way of working.

It builds trust, focus, and collaboration

It connects leaders with teams in real time.

Everyone sees the bigger picture, moves in the same direction, and contributes to shared success.

What is a Story Map?

A Story Map is an agile tool that allows you to create and structure tasks that respond to user needs. The objective is to identify the functionalities that respond to the needs and then plan their realization. To do this, a Story Map is illustrated as follows:

  • A part where the users’ needs are marked and detailed
  • A part where we prioritize the functionalities that respond to the needs
  • A part where we classify the order of the tasks to achieve our goal

A team gathers around a board divided into these 3 parts. Each participant marks, according to their roles, the user needs and/or the functionalities that meet these needs. The team must first focus on the needs and then on the features. Once this is done, the team synthesizes everything and should highlight the most important elements. Finally, you can plan the different tasks to be done.

Why is a Story Map used?

A Story Map is widely used because it aims to respond to users’ needs in the most efficient way possible. This tool allows teams to structure ideas, but also to bring new ones. Finally, the fact that a Story Map allows teams to define, through a few sessions, functionality and/or a product that meets the needs makes the use of this tool very common, especially when doing agility.

Who uses a Story Map?

Mainly, it is the teams that commonly use agile as a way of working that use a Story Map. However, this tool has the particularity of being very accessible to all teams looking to structure and plan actions in order to meet user needs. Thus, all teams with this goal can find themselves using a Story Map, no matter the sector or department.

How to set up a Story Map board in iObeya?

  1. Enter your room, then click Configure the room at the bottom right of the screen.
  2. Add a blank board to your room.
  3. Select the Story Map background from the background catalog.
  4. Add in your tool dock a new set of Notes and rename them : User Objectives
  5. Add in the tool dock the User Story card
  6. Your board is now ready to be used.

Pro Tips on how to set up a Story Map

We recommend that you call on your Product Owner to identify and address the needs that are most important to users. In addition, throughout the sessions, the Product Owner plays an important role because he or she must remind the teams of the real needs that must be met. Finally, do not try to have a final vision of the product from the first session, it is important to use this tool over several sessions in order to develop new ways of thinking and to plan your actions efficiently.

Get started with this template