I got my first experiences from working in pairs when agile software development started gaining ground in early 2000s. Part of the Extreme Programming manifesto was to work in pairs: a more senior programmer would work with a less experienced one. The benefits included better code, fast learning and often innovative solutions. On the downside, “wasting” two programmers on one screen can’t often be justified. Part of the Extreme Programming manifesto was to have customer present in the development. Even though difficult to arrange, it’s still a very novel idea.
This kind of approach can be adapted to business side as well. Business development, go-to-market strategies, designing marketing campaigns are activities -just to name a few-that require creative thinking. Thus, there is usually a benefit from having another brain around. Thinking back, in my previous jobs I’ve often -accidentally- ended up working in this kind of setting. And when looking back, I think the results from this kind of working have been better than when working alone. There have been two different kind of personalities and different kind of competences that have complemented each other.
Working in pairs -approach requires certain kind of personality: you can’t take credit for yourself for anything you do and you can’t have “not invented here” -mentality. What you need is open mind, capability to admit you’re wrong (for many men it’s actually a very liberating experience to admit that you are wrong from time to time) and being able to keep things as things, nothing bigger.
Some years ago I was working in a start-up in this kind of set-up. As persons we were very different and also in private lives we were almost exact opposites. However, we did respect each other professionally. Sometimes we would go outside the office to even yell at each other -at a matter level, never on a personal level. Each time we came to a conclusion on the matter and were able to choose the best option -regardless of who came up with the idea. After that we’d stand united behind the decision.
We have also taken this approach at Dedicto in our consulting cases. We operate so that one takes the lead and the other looks at the project from a slightly remote view. In this way we can have fresh out-of-the-ordinary ideas throughout the project. When you work alone, you easily go too deep into details and after a while won’t see the forest from the trees.
Working in pairs -setting doesn’t require any kind of formal status in an organization. It can be manager – subordinate or two persons at the same level working as a pair. Not everything should be done jointly but rather focus on activities than can benefit from team working such as creative tasks, planning complex stuff or when trying to make something extra-ordinary. My all time favorite duo was John Stockton and Karl Malone who played for years together at Utah Jazz basketball team. Stockton (a small caucasian point guard) controlled the game and gave amazing passes to Malone (Aftican-American power forward) who would score because of duo’s seamless cooperation.
Juhana & Matti
Excellent post. Very much agree with your observations and conclusions. I have had the pleasure of a similar set-up a couple of times in the past. Not only it has proven fun, but I dare claim that it’s also been very effective leading to good output and solid results.
Cheers,
Antti Pikkusaari