Today was my second day of the "Converting Strategy to Action" class, part of the Stanford Advanced Project Management series. The concept of the "Knowing-Doing Gap" by Stanford Professors Jeffrey Pfeffer and Robert I. Sutton was introduced by our engaging instructor Johann Lindig. In a nutshell, it says that despite a ton of classroom time, consulting, and research, people in business don't enact much change. You can't just sit in a classroom discussing things and then expect to be able to DO things that move a business.
Whoever built the slide introducing the concept is to be commended, since it showed an image of a ballet dancer. Dance was never brought up in the class, but yes, I thought, dance is a perfect example! You can't read books about ballet and expect to be able to just get up and show the world 32 fouettes, much less a beautifully turned out and pointed foot.
I realize I take for granted that everything in dance and in music I have to attempt to do before I can do anything. Without doing there is ... well, nothing. You can just stand there and think about how you are supposed to engage your muscles and align your hips and on and on and ... there you are, still in the same place. It's happened to me lots of times when I think about a movement excessively; I'm literally paralyzed. I can't move. I have to get over myself and just try it. It'll take many wonky tries before I even start getting it, but that's part of the process.
For the office, though, I've never thought about it quite the same way. Sure, there's no way you can know everything before you try something, but there's so much planning, analysis and re-analysis, and consensus building going on that individuals and teams are often similarly paralyzed into inaction. Talking is no substitute for action but it can be like a sedative; it makes us feel as if we've done something. Think about it this way: A dance isn't going to create itself from a lot of discussion. At the office, often it's simply a time constraint that forces us to action.
But what if we can see it as trying out a new step, or a new, difficult passage to play on a musical instrument? There's nothing until you do something. It may not be right the first time, so for this approach it's important to be in an organization that supports doing and doing again, with learnings from the first time. Google often encourages teams to "launch and iterate" and yet in some organizations we try so hard to avoid any "failures" at the first attempt due to significant resources on the line. What's the balance here?
I don't have an answer that satisfies me yet, but I do know that going back to the dance and music parallel helps ground me. I'll remind myself: Without doing, there is nothing.
Perhaps that is enough for now.
