Sprint and Garage - The No Device Rule

As fans of the Google Sprint, a five day process for solving business problems devised by three partners at Google Ventures, we were interested to find that they recommend a no-device rule. The Google Sprint is not dissimilar to the Fly Garage’s established by Mondelez for rapid idea and product development. Both methodologies promote creating unique teams for innovation and the creation of an environment in which normal working practices are disrupted to allow for more focused working on a specific theme over a short period of time. 


As the Google Sprint advises, “We have a simple rule: No laptops, no phones, or iPads allowed…These devices can suck the momentum out of a sprint. If you’re looking ata screen, you’re not paying attention to what’s going on in the room”. There are two exceptions to the rule: 

1. It’s okay to check devices during a break.

2. It’s okay to leave the room to check your device. 

Judging by recent research one wonders if such rules shouldn’t also be applied to education environments. A recent study on students’ laptop use in the classroom has brought a lot of attention to the issue of, well, attention in the classroom.  As their title indicates, Sana, Weston, and Cepeda (2013) found that “Laptop multitasking hinders classroom learning for both users and nearby peers.”  In a 45-minute lecture, half the students were given 12 questions easily answered by Google searches and the like (e.g., “What is on Channel 3 tonight at 10 pm?”), simulating the kinds of activities students might do while listening to a lecture.  In the comprehension test immediately following the lecture, those who multitasked on their laptops scored 11% lower than those who didn’t, and even more significantly, students not using laptops but in view of one scored 17% lower (p. 27, 29).*

Do you think such no-device rules only need to apply to specific working processes such as a sprint or could we adopt them on a more ongoing basis? 

(This post comes from our Designing Deeper blog)
(Este post foi retirado do nosso blog Designing Deeper)