Dave Pollard's papers on business innovation & knowledge management



June 2004
Sun Mon Tue Wed Thu Fri Sat
    1 2 3 4 5
6 7 8 9 10 11 12
13 14 15 16 17 18 19
20 21 22 23 24 25 26
27 28 29 30      
May   Jul


leafMADE IN CANADA

leaf trust your instincts



< £ Salon Bloggers & >








Click here to send an email to the editor of this weblog.

 


 

  June 22, 2004


stepping stones 3
In previous articles on New Collaborative (Existential) Enterprises, I've explained what existential enterprises are, how to avoid the most common landmines, how viral marketing works, and the role of innovation. This article will focus on assembling the team for your New Collaborative Enterprise. This step is what differentiates NCEs most from traditional small enterprises. It is also probably the hardest step, the most important, and the most personal.

Assembling the NCE is a juggling act. You need to simultaneously accomplish two things:
  • Find people you profoundly love and respect -- an NCE is a partnership every bit as deep as a marriage.
  • Find people whose skills and knowledge match, nearly perfectly, the skill and knowledge needs of the enterprise you want to build, with minimum overlap (if you have two experts in X and you only need one, guess what the two experts will spend most of their time doing?)
If this isn't hard enough, these attributes are likely to change constantly: You may change your mind about what you want your NCE to do, you and your partners' skills and expertise may change, and your attitude towards your partners may change (or vice versa). All of these will require changes to the team. The good news is that the selection of the team isn't your (or any one person's) job -- it is the essential collective responsibility of the team itself. NCEs are self-selected and self-managed enterprises, because a cohesive group together can always make better decisions than any one person can. As you're assembling the team, your first job is to explain what an NCE is and what's so good about them to your potential partners (I'll cover this in next week's article in this series), so that they accept the shared responsibility for building the team and the enterprise.

This will take some practice and may have some surprising fallout. You might find that as the team assembles itself, you're the one with the redundant skills, and the other potential partners will urge you to self-select yourself out of the enterprise. If so, it's back to square one, creating a new team, possibly doing something somewhat different from what you had envisioned, where your skills and expertise are truly critical to the enterprise. If it sounds a lot like dating, it's because that's precisely what it is.

You may also find that, with the collective wisdom of the team, you may have second thoughts about what you want the enterprise to do. One team member may inform the team that the need you thought you had identified doesn't really exist, or is quite different from what you'd thought. When you refocus on a new need, a new enterprise objective and purpose, it is likely that the skills and expertise you will need to bring it to fruition will also change, and the whole constitution of the team will need revisiting. Just remember, the selection of the team is a shared responsibility. There is no hierarchy.

There will also be a temptation, until the Internet and our society really understand NCEs and help facilitate their formation, to settle for something less than the ideal team. Obviously I can't tell you (and your team) that this is a categorically bad idea. But it's like lowering your sights after you've unsuccessfully asked several lovers to marry you, and propositioning someone you don't really love just to get a 'yes'. Sometimes it's better to keep looking rather than settle for something that's not likely to succeed or make you happy. If you want to be rich and miserable, an NCE is not the answer (marry someone rich instead).

Each potential partner brings acquired skills and knowledge to the enterprise. Let's look at what these terms mean.

From what I've observed in over a hundred entrepreneurial businesses, there are five key groups of business skills:
  • Creative skills -- the ability to conceive, design and apply new ideas
  • Communication skills -- the ability to compose, present, and express ideas and information
  • Information skills -- the ability to organize, understand and apply information
  • Interpersonal skills -- the ability to appreciate, connect with, and persuade other people
  • Spatial skills -- the ability to sense, visualize and coordinate physical objects and actions
While a base level of all these skills is essential for anyone who hopes to succeed in business (or anything else in life), we each excel at only a few of these skills. What we do best is largely a function of what we most enjoy doing (because all of these skills can be learned, and practice makes perfect). Our niche skills, our 'distinctive competencies', may be broad (across all five skill groups) or deep (e.g. the writer who composes brilliantly but can't even deliver his own speeches, or sing his own songs, well).

Knowledge, on the other hand, is what you have learned about specific subject matter. If I want to write software, just having the skills is not enough -- I also need to study and learn programming languages and about information systems and the business environments in which they're used. Some knowledge can be acquired academically, while other knowledge can only be learned from experience.

The combination of skills and knowledge is what we call expertise. Ideally, you want your enterprise team members to have expertise. But if you're young, you may have the skills but not the knowledge. And if you're old, you may have the knowledge, but your skills may be rusty. Your team may therefore consist of some people with skills and others with knowledge -- as long as they love and respect each other, that can be just as good as having expertise, and may be a lot easier to find.

I can see some eyebrows raising when I talk about loving the people you work with. We have been culturally conditioned to leave our emotions at the door when we go to work (and school), to spend half our waking lives sublimating what we feel and just doing what we're told. In a hierarchical organization this is ideal, though it saps the energy and creativity out of workers. But how sick is that? Why should we spend half our lives being what we're not?

If your enterprise is to be a place of passion, joy, and fulfilment (and it should be!), then it will be a place where emotions run free, and that means its partners need to deeply respect and love each other. No matter how perfect a fit their skills and knowledge are, if they don't care for, and about, each other, your enterprise will be a place of chaos and conflict, and will eventually self-destruct. That makes the task of assembling the team even harder. But imagine -- a whole team of people, doing what they do best, their expertise perfectly meshed, engaged and passionate and crazy about their jobs and each other -- isn't that worth the hard work of assembling the perfect team?

I have reviewed, quite negatively, the first generation of social software tools designed to help people find other people they want to be with and/or work with. It does not surprise me that many of these tools ask you for lots of personal information and seem to be used more for finding dates than business partners. In fact, I think that's what's good about them. Assembling the team for an NCE is a job of matchmaking, of seeking love interests, as much as it is a job of acquiring skills and knowledge in human 'containers'. That's one of the reasons NCEs must be self-selected: No one person can accurately gauge the affection that partners will have for each other, and it takes an enormous amount of energy and effort to find just the right people, more than any one person can hope to muster. The next generation of social software tools will, I believe, make it much easier.

The pioneers of NCEs will need extraordinary patience and tact, as all pioneers do, because we're not used to dealing with each other this way, especially in establishing business relationships. Like all pioneers, we'll need to learn by doing, and document what works and what doesn't, and share this with each other, to make the road easier for those that follow.

Last but not least, I have to confess, I have found no proven, successful model yet for a complete Existential, New Collaborative Enterprise. I am hoping that when I meet with Charles Handy, whose concept of Existential Enterprise is entirely consistent with the NCE concepts I have been writing about since before I had heard of his work, he will be able to tell me some success stories. I have studied about a dozen enterprises that claimed, or appeared, to be excellent models, but found them critically lacking in one or more attributes. I know of many enterprises that have some of the attributes of an NCE, and they all believe those attributes are what make them successful and happy, but these aren't yet the stuff of great models. If you took these attributes and combined them in one enterprise, you would have a complete NCE, and there is no reason to believe it wouldn't be a great company, and a perfect model for other pioneers to follow. But I must be honest -- all the individual parts have been tested and work wonderfully, but the whole has yet to be put together in one vehicle and driven. Before the publication of the book of which these articles are a part, I am hoping to find one, or even better, a few. If not, readers will have to settle for some limited-scope success stories instead of a comprehensive one. To illustrate this 'chapter' on Assembling the Team I would then fall back on three family-owned businesses I know well. Their partners meet all of the criteria I have described above -- they love and trust each other, they have a perfect match of skills and knowledge between them, with no overlap or redundancy to cause 'expertise conflicts', and they make all key decisions collaboratively and by unanimous consensus. My only reason for not describing them in more detail here is that they didn't have to go through the hard part of finding each other, assembling the perfect team. They were already together, by fortunate accident of birth or marriage. What's interesting is that I also know of many failed and miserable family-owned businesses, all of which lack the love, trust, respect, and/or mesh of essential skills and knowledge that my three successful proto-NCE family businesses have.

And even more interesting, neither the partners nor the employees in these three NCE-like family businesses work anywhere near as hard as most people. They have more leisure time, more time set aside for social activities, and more fun than those in any other businesses I know. And even when they are working, it is a true labour of love. They are workplaces of great joy.

We all deserve as much.

PS: I need your help, dear readers. I have been using Charles Handy's term Existential Enterprise, and my term New Collaborative Enterprise (NCE) interchangeably. This is probably confusing to readers, but I can't decide which term, if either, to use. I wrote about NCEs several times before I discovered Handy's work. His term is simpler and needs no acronym, but the word 'existential' sounds kind of academic, theoretical, even intimidating to those who don't know what it means. So what name should I use?

3:15:12 PM  trackback []  comment []


Click here to visit the Radio UserLand website. © Copyright 2004 Dave Pollard.
Last update: 02/07/2004; 2:41:45 PM.



SEARCH SITE
How to Save the World

SEARCH SALON
Search All Salon Blogs



Technorati Profile

Click to see the XML version of this web page.

.
.
.
.
.


Subscribe to "Business Innovation" in Radio UserLand.

Click to see the XML version of this web page.





WHAT THE BLOGOSPHERE WANTS MORE OF

Blog readers want to see more:
  1. original research, surveys etc.
  2. original, well-crafted fiction
  3. great finds: resources, blogs, essays, artistic works
  4. news not found anywhere else
  5. category killers: aggregators that capture the best of many blogs/feeds, so they need not be read individually
  6. clever, concise political opinion (most readers prefer these consistent with their own views)
  7. benchmarks, quantitative analysis
  8. personal stories, experiences, lessons learned
  9. first-hand accounts
  10. live reports from events
  11. insight: leading-edge thinking & novel perspectives
  12. short educational pieces
  13. relevant "aha" graphics
  14. great photos
  15. useful tools and checklists
  16. précis, summaries, reviews and other time-savers
  17. fun stuff: quizzes, self-evaluations, other interactive content

Blog writers want to see more:
  1. constructive criticism, reaction, feedback
  2. 'thank you' comments, and why readers liked their post
  3. requests for future posts on specific subjects
  4. foundation articles: posts that writers can build on, on their own blogs
  5. reading lists/aggregations of material on specific, leading-edge subjects that writers can use as resource material
  6. wonderful examples of writing of a particular genre, that they can learn from
  7. comments that engender lively discussion
  8. guidance on how to write in the strange world of weblogs


Creative Commons License
This work is licensed under a Creative Commons License.