The Multitasking Name Game – or How Long Does it Take to Write a Name?

Share on FacebookShare on Google+Tweet about this on TwitterShare on LinkedIn

Here’s a useful simulation that illustrates how bad multitasking is, and how easily we get drawn into it.

The article is primarily written for teachers and facilitators who want to know how this simulation works and how to facilitate it successfully. However, anybody else reading the article will probably gain an appreciation for the issue of multitasking and will hopefully see ways to reveal and solve the problem in their own workplace.

15 Comments

  • 1
    December 7, 2011 - 10:10 am | Permalink

    […] The Multitasking Name Game – or How Long Does it Take to Write a Name? December 7, 2011By Crisp's BlogHere’s a useful simulation that illustrates how bad multitasking is, and how easily we get drawn into it. The article is primarily written for teachers and facilitators who want to know how this simulation works and how to facilitate it successfully. However, anybody else reading the article will probably gain an appreciation for the issue read more » […]

  • 2
    December 7, 2011 - 6:01 pm | Permalink

    Thanks for writing about this game! Since you introduced me to it at the Kanban Leadership course in early 2010 I played this game on various occasions like Kanban or Scrum introductions. It was always very educating for the participants and fun of course :)

  • 3
    December 7, 2011 - 10:10 pm | Permalink

    An excellent write-up of a great simulation. Thank you!

  • 4
    December 8, 2011 - 1:35 pm | Permalink

    Great stuff as usual, thanks!

  • 5
    December 15, 2011 - 9:40 am | Permalink

    Thanks, contains a useful bunch of argumentation to not assign multiple projects to the same developer.

  • 6
    Hans Samios
    January 5, 2012 - 12:35 am | Permalink

    Really like the idea of this simulation and I am looking forward to trying it.

    I’ve used a simple simulation in the past to show the impact of multi-tasking (get people to head two pages with “numbers”, “alphabet” and “roman numerals” and fill in 1 through 10 (a – j; i – x) by first going across the page, then down and note the time the difference for each case) and this gets the base message across (plus it is a really quick exercise).

    What I like about this simulation is that it shows directly the impact on project delivery and risk reduction and also introduces the concept of WIP limits which is only drawn out by inference in my previous approach. Nicely done.

  • 7
    March 4, 2012 - 10:14 pm | Permalink

    Have you simulated the multitasking and WIP policies with 1 developer and just 2 customers? Probably will not be much difference between them.

  • 8
    April 18, 2012 - 11:15 am | Permalink

    […] is a recipe for disaster. I love to explain these ideas to people as games and a great one is the “Name Game’ by Henrik Niberg. Which is pretty much the same as the mechanics analogy but using “writing a name” as […]

  • 9
    Sam
    October 8, 2012 - 6:24 am | Permalink

    Hello Henrik,

    Thank-you for sharing this resource with us.

    As always it is very, very useful – much like the two books that you shared so freely on InfoQ.

    Much appreciate your help.

    Just FYI – the original docx that you mention on the page is not a docx – but a pdf file. Just FYI.

    Best Regards

  • 10
    November 23, 2012 - 3:49 pm | Permalink

    […] To illustrate what happens when you switch from multitasking to one-piece-flow, I used the Multitasking Name Game. […]

  • 11
    April 5, 2013 - 12:09 am | Permalink

    […] is a recipe for disaster. I love to explain these ideas to people as games and a great one is the “Name Game’ by Henrik Niberg. Which is pretty much the same as the mechanics analogy but using “writing a name” as […]

  • 12
    August 31, 2013 - 3:42 pm | Permalink

    […] Écrire un prénom […]

  • 13
    July 10, 2014 - 11:13 am | Permalink

    […] Ein ausführliche Beschreibung gibt es z.B. hier: LINK […]

  • 14
    June 1, 2015 - 7:19 pm | Permalink

    Both Ken Rubin and Jeff Sutherland recently recommended this to me and credited you. I just ran it at a small meetup and had many aha moments happen. This is exactly what I have been looking for to be able to highlight context switching costs at the individual, team and organization levels. I plan on running this many more times in the near future. Thank you so much for the excellent write up.

  • Leave a Reply

    Your email address will not be published. Required fields are marked *