organizational design – Gamestorming https://gamestorming.com A toolkit for innovators, rule-breakers and changemakers Mon, 02 Sep 2019 12:19:12 +0000 en-US hourly 1 https://wordpress.org/?v=6.6.2 https://i0.wp.com/gamestorming.com/wp-content/uploads/2017/07/cropped-Gamestorming-header-1.png?fit=32%2C32&ssl=1 organizational design – Gamestorming https://gamestorming.com 32 32 215212482 Friend or Foe? https://gamestorming.com/fof/?utm_source=rss&utm_medium=rss&utm_campaign=fof Fri, 08 Jun 2018 11:51:23 +0000 https://gamestorming.com/?p=1923

Any product change, project plan, change management initiative requires assessment of and approach to working with stakeholders, a term we use to describe anyone who can impact a decision. Stakeholders often slow or block change; in other cases, they bust obstacles and accelerate progress. To increase your likelihood of success, check out this activity from visual thinker Yuri Mailshenko and identify your stakeholders to understand how they feel about your work.

Object of Play
The object of this game is to create an organizational map of your stakeholders. In some cases this may look like your org chart. In other cases situation and context will dictate a unique shape — likely familiar but undocumented. In addition to mapping stakeholders’ organizational relationships, you’ll also analyze their contextual disposition regarding your initiative.

Number of Players
5 – 15

Invite players from across your project’s organizational spectrum to ensure thorough stakeholder mapping. Colleagues with experience from similar projects or relationships with suspected stakeholders may provide valuable information. Invite them, too!

Duration of Play
30-60 minutes

Material Required
Organizational Design Analysis works best on a whiteboard. Substitute a flip chart (or two) if necessary. To run a good session, you will need:

  • Dry-erase markers, we recommend using at least three colors (black, green, red)
  • Dry-erase marker eraser (or paper towels)
  • Sticky notes
  • Camera to capture the results

How to Play

Step 1: Map organizational structure

  1. Invite your players to a five minute stakeholder brainstorm, ask: Who are our project stakeholders? Ask them to consider teams and individuals both inside and outside your org or company. Have players write one stakeholder per sticky note.
  2. Once the brainstorm ends, have each player present their stakeholders by placing their sticky notes on a wall and provide to the group a brief description of their thinking.
  3. With all the sticky notes on the wall, ask the group to organize them into a rough org chart. This needs only to be an imprecise draft.
  4. With the sticky note draft org chart as your guide, create a cleaner version of the org using a whiteboard and dry-erase markers. Ask for a scribe to map the organisation top to bottom. When the scope is quite big (for example, you are mapping a large enterprise), map the parts of the org structure that are less relevant to the analysis with less detail, and vice versa.
  5. To help with navigation, label all stakeholders.
  6. Denote future parts of the organizations (ones that are missing at the moment but are important to be considered for potential impact).
  7. Draw a border around the areas that are affected by the change/initiative or are in the focus of the analysis.
  8. Your whiteboard map could now look something like these:
use dotted lines to identify matrixed teams
use dotted lines to identify matrixed teams
use colors to cleanly delineate multiple org dimensions
different colors work, too

Drawing considerations:

  • Avoid using prepared artifacts like your company’s official org chart. Create on-the-go with full engagement of the group.
  • Draw people. Draw a person as a circle and the upside down letter ‘U’. A group of people could be just three persons put close to each other; avoid drawing departments and teams as boxes.
  • Many organizations are matrices of different kinds. Introducing an extra dimension might create visual clutter. Try to avoid that by either using a different style of a line (dotted or dashed lines) or a different color for a weaker organizational component.

Step 2: Add insight

  1. Begin a group discussion with the goal of mapping stakeholder disposition and level of support regarding your initiative.
  2. Discuss each stakeholder one-by-one, try to uncover:
    1. Disposition towards the initiative: are they for, neutral or against? To what degree? Why?
    2. Level of impact: how much influence will this stakeholder have? High, medium or low?
    3. Relationship strength between stakeholders: who do they influence? who influences them? To what degree?
    4. Participation energy level: high, medium or low?
    5. If you are having difficulty dispositioning a particular stakeholder, move to the next one. Additional conversation may help you get unstuck and you can circle back to the troublemaker.
  3. As you near consensus, draw your findings using tokens or icons. Discover what works best for you, some examples:
    1. A green smiley face for a supportive stakeholder
    2. A battery with one out of three bars charged for a low-energy stakeholder
    3. A cloud overhead signals a confused stakeholder
use tokens and text to label different dimensions of stakeholder dynamics
Use tokens and text to label different dimensions of stakeholder dynamics

Strategy
Org charts are quite unambiguous and offer little room for opinion. This exercise’s value comes from mapping less obvious things like stakeholder influence, disposition and decision making power in relation to the initiative. Defined structures are rarely challenged but a necessary foundation. What is interesting is something that lies beyond the official org chart – people’s attitude to the topic of discussion, their real power and influence. Players will share their opinions openly — and surprisingly!–in a safe, structured and collaborative setting.

Complementary Games
You understand who your stakeholders are and the org design dynamics facing your project, now what?

  • Who do – identify what you need from each of your stakeholders
  • Empathy Map – get inside their heads to understand their pains and gains
  • Understanding Chain – create the story your stakeholders need to hear to contribute to your success!

Source

Activity developed by Yuri Malishenko – visual thinker, agile coach, product owner

Activity titled by Stefan Wolpers – agile coach and ScrumMaster.

]]>
1923