Posts Tagged ‘collaboration’

Language creates reality, even in business

Monday, December 14th, 2009

One of the most fun aspects of blogging has been re-immersing myself in language. At work, language is just something you use; you don’t scrutinize it. Yet, the (mis)use of language has a lot to do with effectiveness at work or in any collaborative context.

I don’t mean jargon; rather, I’m talking about the slippery language we use when we ask for or respond to requests to do something. Kids, of course, quickly master getting their way through exploiting language loopholes: if I don’t ask my 6-year-old son in precise, unambiguous language to do something he wouldn’t otherwise do (say, make his bed), he won’t do it, and tell me it’s my fault because I wasn’t clear.

He’s onto something there. Too often, I haven’t been clear in what I request from others at work; be they subordinates, peers or other colleagues. I also interpret as a clear “yes” words that don’t, in fact, mean that. (My son is not faultless, however. Too often I’ll blow off requests with half-hearted responses, such as saying “OK,” meaning “I understand you,” instead of “yes, I will do that.”) Imagine this brief conversation:

“I need that report by Friday. Does that make sense?”

“Sure.”

There are two fundamental problems with the above conversation. The requester has not specifically asked her colleague to hand in the report by Friday, and the colleague has not really agreed to anything. Let’s fill out the dialogue as the requester would have it – annotations in [brackets]:

“I need that report by [the end of the day] Friday [and I need you do complete it and get it to me]. Does that make sense? [Will you do that? Are there any questions before you get started?]”

“Sure. [I understand what you want and I will get it to you by close of business Friday.]“

Here’s how the colleague might fill in the blanks:

“I need that report by Friday. [If you don't have anything pressing, could you try to get it to me?]”

“Sure. [I have a lot of work already planned. If I get a free moment I'll try to work on it some. But no guarantees.]“

It’s obvious that this story won’t end happily. And it is replayed again and again, in all companies, all over the world.

If the above has piqued your curiosity, you must read this article in the new Strategy + Business magazine, covering the work of Fernando Flores (”Fernando Flores Wants To Make You An Offer“). Flores is a philosopher of communication who over the past thirty years has worked to understand and shape how people communicate to convey information or accomplish tasks.

The S+B article dwells on Flores’ personal story (former Chilean political prisoner, to successful US-based management consultant, to current member of Chile’s senate), but to me the discussion of his research and consulting work is most interesting.

Flores says, “Human beings are linguistic, social, emotional animals that co-invent a world through language.” And in his consulting practice he helped companies codify their communication to increase clarity of meaning. Central to this is the idea of offers, promises and commitments. Requests must be explicitly phrased as such, and commitments to do something are expected to be fulfilled.

As companies grow in size and scope, and communication becomes more virtual, the ability to hind behind weak requests and noncommittal responses will only increase. Therefore, the need for co-workers to become more explicit about their requests, and responders about their commitments, is urgent. It’s important for companies to recognize that, but I think each of us as individuals can get started, with our without company support.

Your company and career need you to do this. Will you? Is that a promise?

Related post:
Making and keeping commitments: a must
Making and obtaining effective promises – it’s important, and rare

The Best Business Books of 2009

Thursday, December 10th, 2009

In the wake of the worst US economic catastrophe since the Great Depression, everybody realized this: Making money is harder than we thought. So, this year, books on innovation had special resonance. Luckily, there were some great ones out there. So many, in fact, that this year’s best-of list includes two “companion volumes”–other good books from this year that cover similar material from another perspective.

These are the best books I read this year:

design-driven innovation1. Design-Driven Innovation – Roberto Verganti. A fascinating book that looks at companies that don’t merely create new products, but develop products and services that create new meaning for customers. Is that important? Well, companies that do it well avoid commoditization and generate outsized profits for long periods of time. Think Apple.

(companion volume: The Design of Business by Roger Martin)

Discovery-Driven Growth2. Discovery-Driven Growth – Rita Gunther McGrath and Ian MacMillan. Verganti’s book covers the more creative side of innovation, while McGrath and MacMillan discuss the process that established companies should use to improve their innovation efficiency–that is, bringing more successful products to market and spending less on the failures. The central lesson: do more work on paper, and scrupulously document & validate assumptions as you go.

(companion volume: Innovation Tournaments by Christian Terweisch and Karl Ulrich)

enterprise2.0

3. Enterprise 2.0 – Andrew McAfee. A clear description for the general business audience of how web 2.0 products, like social network software, wikis, messaging services, and the like, can be deployed to help corporations work more effectively. Excellent combination of case studies, theoretical models, and a clear-eyed assessment of the obstacles in the way of wide adoption.


4. Think Again: Why Good Leaders Make Bad Decisions and How to Keep it From Happening to You – Sydney Finkelstein, Jo Whitehead and Andrew Campbell. A timely book that shows how smart, experienced people can make terrible decisions, and what safeguards companies can use to improve their decisionmaking. Illuminates the many cognitive biases at work during the decision process, which helps the reader to understand why so many decisions that look atrocious in hindsight were considered reasonable and logical at the time.

Collaboration by Morten Hansen5. Collaboration – Morten Hansen. Discusses how collaboration in business works, and when it doesn’t work, then provides a map for companies to improve their collaborative behavior – including unifying your workforce, nurturing “T-shaped” management and using networks intelligently. Key message: collaboration has a cost, and you need to make sure the payoff of collaboration outweighs it.

Related posts:
Podcast: Sydney Finkelstein on “Think Again”
On “Discovery-Driven Growth”
Podcast: Roberto Verganti on “Design-Driven Innovation”
On “Collaboration”
Video Review of “Enterprise 2.0″

Video review of Andrew McAfee’s “Enterprise 2.0″

Monday, November 30th, 2009

enterprise2.0TRANSCRIPT:

We’re here today to talk about “Enterprise 2.0” by Andrew McAfee. He is with MIT, used to be at Harvard Business School. Just switched over a couple of months ago. He writes an excellent blog on IT and business, that I’d recommend you read if you haven’t come across it yet. And so, he’s just produced his first book. To explain the title, Enterprise 2.0 is a term he coined to refer to using web 2.0 tools like Flickr, Facebook, YouTube, Twitter and similar tools in a business context.

The book is a lot like a recent book, “Groundswell,” that explained to general business people how social tools affected customers and markets and how to use those to communicate and listen. Communicating from inside the business to outside. “Enterprise 2.0″ performs a similar task, focusing on using those tools inside the business, more for collaboration and tapping the collective intelligence of employees. And so it takes this marginal topic and moves it to a general management-type discussion. Which I think is really important, to get it out of the IT discussion into the management discussion.

So as part of that objective he does a really good job of explaining how these tools work and also what ties them together because if you think about tools like Flickr or YouTube or a blogging platform or a messaging platform or a wiki there are a lot of differences among those but he’s tied together the common threads, using an acronym called SLATES (search, links, authoring, tags, extensions and signals). Signals, for example, like RSS that allows people who follow these platforms without having to log on to them every single hour to see what’s changed.

Another important part of the book is in putting the different tools into a context in terms of how useful they’d be for different organizational problems. He uses a bullseye metaphor focused on the strength of ties between colleagues to explain that. At the center of the bullseye are strongly-tied colleagues meaning people who work together in the same department, in the same location, all the way out to the edge of the bullseye. meaning colleagues who have no relationship at all. Different tools apply at different levels of the bullseye. In the center, people with strong ties would use tools like wikis, or collaborative development tools, like Google Docs.

Midway out the bullseye are colleagues with weak ties. People who know each other but don’t get together often, who don’t talk often, but would like to keep apprised of each other’s activities for the purposes of sharing knowledge, best practices, identifying solutions to problems, and so forth. For that ring of the bullseye, Facebook-like tools are very useful.

At the outer edge of the bullseye, where colleagues have no relationship other than that they work for the same company, a prediction market is a useful tool, that gathers people’s guesses about the possibility of certain things happening like a certain sales volume being reached or likelihood an innovation will succeed in the marketplace and aggregating that information to get a better answer than any individual would come up with themselves.

He doesn’t go overboard in terms of enthusiasm for how great these things are and how it’ll change companies overnight, and he has a pretty clear-eyed view of how difficult it is going to be to bring these tools to wide use. It just takes a long time -and he dwells on that at some extent – how long it takes for revolutionary innovations to take hold, and he doesn’t think this is any different, though he is optimistic that it’ll happen eventually.

And finally in the book he talks about kind of different management models or practices that work well with these tools, and by contrast he talks about typical Model 1 behaviors which are more command-and-control type behaviors, self-protecting behaviors and less-collaborative behaviors, which don’t go well with these new tools. To really utilize these new tools, people have to adopt what he calls Model 2 behaviors, which are collaborative, not so much focused on self-protection but looking out for the best interests of the company. Quite a different model than what most people have seen where they work. And I think that heaps underline the challenges in getting these systems adopted and in wide use.

It’s an excellent book, very well-organized and well-written. It takes an important topic and brings it into the mainstream. I really enjoyed it and I think you will too.

My reading journal: Morten Hansen’s “Collaboration”

Monday, November 2nd, 2009

I’ve finished a few books recently but am a bit behind on reviewing them. My kids have started documenting their books in reading journals that help them with reading comprehension. To add a bit of variety (and to make sure I’m not getting lazy), I’m going to use the reading journal format for this week’s reviews.

collaborationCollaboration: How Leaders Avoid the Traps, Create Unity, and Reap Big Results,” by Morten Hansen. 2009: Harvard Business Press, 231pp.

When did you read it? September-October 2009.

Subject: A study of collaboration in business; when it is and when it is not appropriate, and best practices for successful collaboration.

Did you like it? How many stars would you give it (1-5)? 4 (thankfully I don’t have assigned reading… I won’t be writing about any 1-star books here!)

Summary: Hansen has spent his academic career studying how corporate groups collaborate, effectively and ineffectively. This book sums up a number of studies he has worked on with various companies over the past 15 years. First, Hansen discusses obstacles to collaboration – including the warning that not all collaboration is good collaboration. In other words, when the costs of collaboration (communication, coordination, negotiation, etc.) outweigh the benefits. This frequently happens when businesses lacking key synergies are combined via merger.

The bulk of the book is devoted to discussing what Hansen calls “disciplined collaboration.” He discusses four collaboration barriers – not invented here, hoarding, search (inability to find the insight you need), and transfer (inability to put others’ knowledge to use), and three “levers” to promote collaboration: “unify people, practice T-shaped management, and build nimble networks.”

These are practical suggestions and, on their own, not revolutionary. But to me seeing these three levers together as requirements for successful collaboration was distinctive and valuable.

Favorite quote: “Paradoxically, the emphasis on performance management over the past decade has created what Harvard Professor Leslie Perlow calls a ‘time famine’ at work. As people are pressured to perform, they feel that they don’t have the time to help others; reasonable requests for help are seen as burdens that put them behind in their own work. So people are faced with a trade-off – to do their own work (but not help others), or to help others (but get less work done).” p.55

Was it similar to anything you have read before? There are echoes of the recent book “Senior Leadership Teams” which takes up the question of how to get groups of senior executives, who naturally work to drive results from their own groups, to collaborate – another application of the “T-shaped management” approach.

Will this book end up on your bookshelf or in the library donation pile? The bookshelf. Collaboration is an important subject and I don’t have any books that deal with that as a main topic. Plus it’s good.

Related posts:
On “Senior Leadership Teams”

Teamwork works for Netflix Prize competitors

Monday, June 29th, 2009

Netflix has undoubtedly gotten much more than $1MM in publicity for its contest awarding a cool million to anyone able to improve its recommendation engine by more than 10%. But the contest appears to be winding down. According to the New York Times, a group has surpassed the 10% barrier, starting a 30-day countdown for any competitor to beat their performance and claim the prize instead.

It’s not likely to happen. That’s because the leading group is an alliance of several of the top performers in the competition, who abandoned their individual projects for a joint effort to push the needle past the magical 10% threshold. The Times wrote:

BellKor’s Pragmatic Chaos [the alliance's name] is a pretty elite crowd. The group is a collection of the 2007 and 2008 winners of the Netflix Progress Prizes — $50,000 a year for the teams that made the most progress toward the 10 percent improvement — and a pair of engineers from Montreal who have long been near the top of the contest’s leaderboard.

One of the tenets of alliances is that it’s better to get 25% of $1MM than 100% of nothing. For longtime competitors to band together shows how difficult the 10% barrier was, and the significant incremental value of combining different ideas.

In these times, it may be prudent to throw out the old rules of going it alone, and restricting alliances to those you don’t compete with. It worked for BellKor’s Pragmatic Chaos.

(Disclosure: I am a Netflix subscriber.)

Related posts:
Netflix demolishes own business model
Follow-ups: Netflix and “Harry Potter Marketing”

“Story banks” for dispersed collaborative communities

Wednesday, April 22nd, 2009

The Mistake Bank is a project that continues to surprise and delight. A couple of blog posts from Scott Berkun and Nat Torkington on O’Reilly Radar brought a few hundred new visitors and several dozen new members over the past week.*

This shows, I think, that the idea of story banks–collections of stories on a certain topics which users can read, comment on and share–has legs. And over the past few weeks, in part due to spending time with the New Tech Meetup of Central PA and meeting the folks from Symbian at CTIA, I’ve been thinking that story banks are a powerful tool that distributed development communities can use to share tips, tricks, even mistakes/dead ends/failures.

The story bank I’m thinking about combines the experience I’ve developed curating The Mistake Bank with a story-bank platform like Cynthia Kurtz’ Rakontu, deployed in a company or development community (like Symbian) as a way of sharing deep lessons among people who aren’t anywhere near each other physically, and at the same time developing a shared culture and values through the stories they tell and retell.

I’m looking for companies/groups who might like to pilot the idea. If you want to get in on the experiment, email me at john (at) caddellinsightgroup (dot) com or leave contact information in the comments.

*Ajeet left a great comment on the Radar blog to the effect that the Mistake Bank is the only bank guaranteed to grow into perpetuity. How true!

IT is a key weakness of joint ventures… and any collaboration

Tuesday, March 31st, 2009

Strategy + Business, the Booz & Company journal, just published an article discussing the results of a survey on information technology in automobile joint ventures. Booz’ conclusion: JVs systematically underinvest in IT because of cost pressures, difficulties in standardization and security.

Please read the article and come to your own conclusions. For me, it brought up an issue I’ve faced a lot recently–the IT disconnect between a company’s direct employees and the consultants it uses. When I’ve been in collaborative projects with companies, the lack of easy access to scheduling programs, file stores, and document management systems has been ubiquitous. The IT groups don’t want some temp to take up a lot of their time with nonstandard hardware, unknown applications, and other difficulties. So, they leave it up to the outsider to get along without the proper tools. Ironically, free or cheap off-the-shelf tools like Ning, Google Docs, Basecamp, etc., are far superior collaboration tools to those provided by the corporate IT shops I’ve worked with.

Companies’ value chains are becoming more and more unbundled. There’ll be a great deal more difficulty collaborating with partners as that happens. Corporate IT groups will have to radically change their approach to remain relevant.

Related:
Corporate IT Maximum Security is Damaging Innovation