Saturday, May 5, 2018

If You Cut Employees Some Slack, Will They Innovate?

Learned a lot lending an editorial hand here:

MIT Sloan Management Review, May 4, 2018

by Yasser Rahrovani, Alain Pinsonneault, and Robert D. Austin

The idea of using slack resources — in the form of time, technology, and support — to bolster employee innovation falls in and out of favor. The return on slack innovation programs can be prodigious: 3M Co. attributes the development of the Post-it Note to its 1948 decision to allow employees to devote 15% of their paid time to side projects; and Google says its “20% rule,” which upped the ante on slack time devoted to innovation, yielded Gmail, AdSense, and Google Earth. But few, if any companies, have stuck with time off for innovation and other slack-based programs for as long as 3M. Even Google has reportedly waxed and waned in its commitment to its 20% rule.

Given the significant investment that slack-based innovation programs require, the decision to adopt one shouldn’t be made off the cuff. But what are the factors underlying that decision and how should such programs be designed? To begin to answer these questions, we conducted in-depth interviews of knowledge workers in different industries to understand what motivated them to take risks and explore new ideas, and, more specifically, whether and how slack resources might have contributed to their innovativeness. We then created and refined an empirical model based on the factors and relationships that appear to influence employee innovation and tested it using a sample group consisting of 427 employees from North American companies.

We found that different types of employees respond in different ways to slack innovation programs; that different kinds of slack resources are better suited to certain types of employees than they are to others; and that different kinds of slack innovation programs produce different kinds of innovation. Companies can use these findings to design more effective slack innovation programs and maximize their returns on slack resources...read the rest here

No comments: