Diese Präsentation wurde erfolgreich gemeldet.
Die SlideShare-Präsentation wird heruntergeladen. ×

Teaming on the fly: een speels leermoment - Jan Bal en Ive Vanderauweraert - Beanmachine

Anzeige
Anzeige
Anzeige
Anzeige
Anzeige
Anzeige
Anzeige
Anzeige
Anzeige
Anzeige
Wird geladen in …3
×

Hier ansehen

1 von 22 Anzeige
Anzeige

Weitere Verwandte Inhalte

Diashows für Sie (20)

Andere mochten auch (20)

Anzeige

Ähnlich wie Teaming on the fly: een speels leermoment - Jan Bal en Ive Vanderauweraert - Beanmachine (20)

Weitere von Antwerp Management School (20)

Anzeige

Aktuellste (20)

Teaming on the fly: een speels leermoment - Jan Bal en Ive Vanderauweraert - Beanmachine

  1. 1. TEAMWORK ON THE FLY Ive Van der Auweraert– Jan Bal Leadergathering 2016
  2. 2. 2 Leader Gathering 2016 Water Cube •  A joint effort of dozens of people: 20 disciplines, 4 countries, 4 large corporations, dozens of contractors and consultants. •  The goal was clear: Build an iconic structure to reflect Chinese culture, integrate with the site, and minimize energy consumption – on time and within budget. •  But how to do all this was less clear … •  It was an unusual endeavor, but the strategy employed to complete it—a strategy we call ‘teaming’—epitomizes the new era of business.
  3. 3. Leader Gathering 2016 3 To team or not to team… Stable teams of people who have learned over time to work well together can be powerful tools. But given the speed of change, the intensity of market competition, and the unpredictability of customers’ needs today, there often isn’t enough time to build that kind of team. Teaming is a way to gather experts in temporary groups to solve problems they’re encountering for the first and perhaps only time.
  4. 4. 4 Leader Gathering 2016
  5. 5. 5 Leader Gathering 2016 The new world needs teaming, not teams …
  6. 6. Leader Gathering 2016 6 So how to tackle the challenges? Hardware & Software To “team” well, employees and organizations must embrace principles of project management — such as scoping out the project, structuring the group, and sorting tasks by level of interdependence— and of team leadership, such as emphasizing purpose, building psychological safety, and embracing failure and conflict. This is the hardware and the software of teaming.
  7. 7. Teaming Hardware Scoping – Structuring - Sorting
  8. 8. Leader Gathering 2016 8 SCOPING
  9. 9. 9 Leader Gathering 2016 STRUCTURING (scaffolding)
  10. 10. Leader Gathering 2016 10 SORTING (prioritizing)
  11. 11. Teaming Software Team leadership – emphasizing purpose – building psychological safety – embracing failure and concflict
  12. 12. 12 Leader Gathering 2016 Emphasizing purpose Purpose is fundamentally about shared values; it answers the question why we (this company, this project) exist, which can galvanize even the most diverse, amorphous team.
  13. 13. 13 Leader Gathering 2016 Building psychological safety
  14. 14. Leader Gathering 2016 14 Building psychological safety In fast-paced, cross-disciplinary, cross-border teaming situations, it’s not necessarily easy for people to rapidly share relevant information about their ideas and expertise. Some people worry about what others will think of them. Some fear that they will be less valuable if they give away what they know. Others are reluctant to show off. Even receiving knowledge can be difficult if it feels like an admission of weakness.
  15. 15. 15 Leader Gathering 2016 Embrace failure
  16. 16. Leader Gathering 2016 16 Embrace failure Teaming necessarily leads to failures, even on the way to extraordinary successes. These failures provide essential information that guides the next steps, creating an imperative to learn from them.
  17. 17. Leader Gathering 2016 17 Put conflict to work
  18. 18. Leader Gathering 2016 18 Put conflict to work To move forward, all parties must be pushed to consider the degree to which their positions reflect not just facts but also personal values and biases, to explain how they have arrived at their views, and to express interest in one another’s analytic journeys. In this way, people can put conflict to good use.
  19. 19. Leader Gathering 2016 19 Behaviors for successful teaming
  20. 20. Leader Gathering 2016 20 Take time to reflect on the software and hardware of your team. Did we speak up? Did we invite people to speak up? Did we take time to reflect? Was there room for experiment? Did people actually experiment? Did you learn from these experiments? Did we intently listen to each other? Were we integrating ideas and approaches?
  21. 21. 21 Leader Gathering 2016
  22. 22. 22 Leader Gathering 2016 Want to know more? jan@beanmachine.be ive@beanmachine.be

×