Outcomes ‘v’ Requirements
Over the years I’ve worked on some projects where teams understand the what and focus on the how, but don’t always give the why the full attention that it deserves. Effectively there can be a gap in understanding and communicating outcomes, not just “requirements”. So I created a training activity to address that gap. And I made it into a game. Using Lego.
Lego
Why Lego? Because one of the most effective ways to learn is through play. And every time that I have facilitated this activity:
- Participants use their creativity, problem-solving, teamwork and communication skills
- Laughter happens (this is good)
- It highlights key lessons that you can take away and apply in real life, on your project
Customer perspective
Initial participants were internal ones: our BAs, plus PMs, then our senior developers. The activity takes 45-60 minutes to play out. It got such consistently good feedback that we have taken it to some of our customers, to help some of our Product Owners write better User Stories.
Training customers was a bit of step into the unknown, but one that I’m glad we made, because, having done the activity:
- They concurred – they found it a useful learning experience;
- We bonded more – team dynamics improved by doing the exercise together, and;
- Their project teams are now receiving better quality User Stories. Smiles all round.
So – underestimate the power of learning with Lego at your peril!
Give it a go?
If you’d like to try the activity yourself, then you can:
- Get in touch if you’d like us to run a session for you
- Learn how to run a session yourself:
- Spoiler alert: once you know how to facilitate it, then you know how to play and win!
- Download the Facilitator Slides and watch the Facilitator Pack video.
- If you do run it, then good luck, and please let us know how you got on!