Wednesday, January 14, 2009

A New Approach to Mentoring

A New Approach to Mentoring

These days, you need more than a single person. You need a network.

By KATHY E. KRAM and MONICA C. HIGGINS

SEPTEMBER 22, 2008

Working with a mentor is a classic recipe for success in business. But the traditional mentoring relationship just doesn't work anymore.


Typically, you choose a single senior colleague -- or get assigned to one -- who can show you the ropes and open the right doors. But the world of work has gotten too complicated for one person to provide all the guidance and opportunities you need to manage challenges and prepare for the future.



Consider this: How can one teacher know enough to help you keep up with rapidly changing technology, as well as navigate the challenges of globalization, a multicultural work force and team-based decision making? Even people who have served as mentors often need help staying abreast of all these changes.


A better approach is to create and cultivate a developmental network -- a small group of people to whom you can turn for regular mentoring support and who have a genuine interest in your learning and development. Think of it as your personal board of directors.


The composition of the group depends on where you are in your career and what you're looking for. If you're just getting started, you could certainly turn to your boss or assigned mentor for help. But you should also look further, seeking out peers to get feedback on areas where you need to improve, such as public speaking or working in teams.


At midcareer, you might look to other managers and people outside the organization; someone you know from a professional association might have insight on new ideas in your industry, for instance. Senior managers might get coaching from peers on the next steps to take in their career, from family members on achieving a better balance in their lives, and even from juniors who have crucial technical expertise vital to immediate business challenges.


What sets this group apart from people you network with more generally or from casual or one-time relationships? The relationships have a high degree of mutual learning and trust in which both individuals give and receive various kinds of informational, emotional and strategic support. What's more, these individuals have been enlisted by you to provide the guidance and support that will enable you to take the next step forward, whatever that next step may be.


A number of organizations are now helping employees build these kinds of networks. In one pharmaceutical company, for instance, product-development team leaders come together monthly in groups of 10 to 12 to coach one another. They start each meeting with a check-in where each member identifies new challenges, such as dealing with a poor performer and building a team that could deliver new designs in a timely manner. Members address each issue in turn, giving their peers possible strategies. The give and take also helps boost their interpersonal skills.


Boston University Professor Kathy Kram sits down with WSJ's Jennifer Merritt and shares the skills needed to build good relationships at work. (Sept. 22)


Similarly, in a consumer-products company, groups of junior executives have been meeting with a senior executive on a regular basis to discuss challenges they face as they seek positions of greater executive responsibility. Here, these junior executives have opportunities to enlist one or more peers and a senior executive into their developmental networks. And, in a major urban school district, informal mentoring circles for principals provide opportunities to enlist peers as members of their developmental networks to support their leadership development.


Developmental networks can also be extremely valuable in the context of global and multicultural business environments. For example, the challenges that expatriates face as they move abroad, and then again when they return to their home country, can be met most effectively when the expat has a strong developmental network to draw on.


These initiatives are beginning to show results in critical measures such as enhanced employee engagement and satisfaction, faster cycle times in new-product development, customer satisfaction and employee retention. The quality of developmental relationships is, indeed, a real source of competitive advantage.


Here's a look at the steps you need to take to develop your own developmental network.


1. Know Thyself


Although this tip may sound clichéd, it's crucial. When people seek out help, they generally aren't as well-prepared as they could be. Only if people know their own goals, strengths and weaknesses will they be able to figure out whom to turn to for support -- and know how to ask for and apply advice effectively.


You should start by reviewing appraisals and developmental feedback that you have received. And ask yourself tough questions. What do you really enjoy doing at work? How can you best contribute, given your talents and interests? Where would you like to be in two years? In five years? Are there skill and knowledge gaps that you want to fill? Do you have a healthy balance between your work and outside commitments? Who knows you well enough to give useful feedback?


You should also assess your interpersonal skills. Are you comfortable reaching out for help, sharing your experiences and soliciting feedback? Or even just starting conversations with strangers? If you have shortcomings here, it's vital that you address them, or you may have trouble creating an effective developmental network.


Fortunately, many organizations offer a range of activities to help people answer these kinds of questions, such as leadership-development programs and career-assessment tools.


2. Know Your Context


Knowing yourself is only half the equation. You must also know as much as possible about how to achieve your goal -- whether that means a promotion, a new career or simply better balance in life.


If you're looking to advance at your job, for instance, you must understand how the promotion process works at your company and figure out which potential sponsors might be keen on coaching you. If you want to change careers, you would want to be sure you understood the ins and outs of your desired field, everything from its hiring practices to what's expected in the job. A good way to proceed is to build up contacts in the industry, perhaps by attending professional conferences.





These new contacts may then introduce you to people already working in the area that you aspire to join. And if you nurture these relationships, over time these people may become part of your developmental network. But it's key to focus on a handful of relationships with individuals who seem to genuinely care about you and have wisdom or resources to offer. And be mindful of what you can offer to each of these individuals to create mutual learning.


3. Enlist Developers


Next, it's time to actually build your developmental network, enlisting people who can help you advance your goals. So, whom should you choose?


Let's say you're a product manager in a technology company aspiring to reach a higher position. You'll want to develop alliances with people at more senior levels who can sponsor and promote you, coach you and serve as a role model.


This, however, isn't sufficient. What about peers who can help you learn to navigate the company's politics and can share information about those at more senior levels? And are there individuals outside your organization who can help you keep learning? Professors or fellow students from graduate school could remind you about theories or practices that might be useful in your current job. Contacts at professional organizations could give you insights into new technology, while people in your family could act as a sounding board.


For some, forming outside developmental relationships may be just the kind of help they need to make a career change. Indeed, the greater the diversity of one's network, the more open-minded one is likely to be regarding next steps.


It is critical to remember that high-quality mentoring is a process of give and take, where both parties learn from each other. So, you should approach potential developers with a sense of how they might benefit from an association with you.


What can they learn from you -- new skills? Maybe they'll be able to develop insight into how people in your job see the world and prioritize what's important. Could helping you be an opportunity for a senior manager to hone coaching skills or to develop confidence in mentoring others?


Having a clear sense of these possibilities will make it easier for you to empathize with your allies, ask relevant questions and disclose relevant information about yourself as you ask for guidance.


4. Regularly Reassess


As your career and life unfold, you'll need to keep reassessing your developmental network; the setup that served you well a few years ago may not work as your situation changes. You must ask yourself which developers can still help you meet your goals, and which need to be eased aside for new ones.


This may sound calculating and borderline manipulative, but remember that you're not actually discarding old allies. As you bring new people into your network, don't discard the old ones, just look on them in a different way -- perhaps as valued friends whom you consult occasionally instead of colleagues that you frequently rely on for advice.


In short, it's a matter of being more intentional when it comes to seeking out advice, and this is relevant for everyone, at every career stage, not just for those starting out.


For a look at a successful reassessment, consider a young software executive we've interviewed. When he started out, he wanted to become an expert in dealing with client problems, so he sought out a senior colleague who served as a role model and eventually provided him with exposure to clients. He was promoted several times and built a strong developmental network, including his boss, the vice president of marketing, several of his immediate subordinates and one of his peers.


It Takes a Network



· The Situation: The traditional mentoring arrangement just doesn't work anymore. A single senior colleague can't possibly keep up with all the changes in the fast-moving world of work.

· The Solution: People should create and cultivate developmental networks instead -- small groups of people who provide regular advice and support.

· The Strategy: There are a number of steps to take when setting up a network, such as carefully assessing your strengths, weaknesses and goals and figuring out what you need to know to advance your goals. And when your network is in place, you should regularly reassess it as your situation changes -- while making sure that you help out your allies as much as they help you.


After 12 years, he was interested in moving into a leadership position where he could run one of the company's business units. But the current leaders appeared to be quite comfortable in their roles. And he began to feel that there were few people he could turn to for advice, given an increasing sense of competition among his peers (and his own fast-paced trajectory).


So, he began to build a developmental network that could help him manage his new challenges. The first person he turned to was his wife, who provided continuing support and confirmation during this difficult time. As she worked through the issues with him, she hit upon a crucial piece of advice, encouraging him to look outside the company for a new job where he could meet his goals. At the same time, he consulted an executive-search firm, which counseled him about where he might turn for opportunities.


Putting all of it together, he left his company for another firm, where he led several teams. Now he's considering launching a start-up of his own.


5. Develop Others


As you enlist people in your network, consider how you can benefit them, as well. Remember, high-quality mentoring is about mutual learning; consider how your high-quality relationships serve to develop others and your organization.


As you enlist more senior colleagues, for instance, you'll be providing them with opportunities to gain new knowledge from you, to hone their coaching skills and possibly boost their enthusiasm at work. Similarly, as you enlist junior colleagues in your developmental network to hone your coaching skills, you are creating an opportunity for them to bring you into their developmental networks. Exploring these complementary personal goals can solidify the relationship and ultimately help both of you and your organization.


If you're a senior leader, meanwhile, you should also work to foster developmental networks in your organization. Just by forming your own network, and joining other people's networks, you will serve as a role model. But you can also actively encourage coaching and mentoring among those that you manage, by designing jobs to encourage peer coaching, for example. And you can launch leadership-development programs that help individuals to develop the skills and self-awareness they'll need to build strong developmental networks.


Ultimately, these developmental networks can enhance organizational performance and development. It is, in essence, a win-win proposition for you and your organization.


—Dr. Kram is a professor of organizational behavior and a distinguished faculty scholar at Boston University's School of Management. Dr. Higgins is an associate professor focused on leadership and organizational behavior at Harvard University's Graduate School of Education.

13 Rules for Surviving A Horror Movie Project

13 Rules for Surviving A Horror Movie Project


Horror movies follow unique and immutable laws of physics. There's never anything in the backseat unless you forget to check it. Brand new cars with the sticker still on the window will refuse to start when zombies attack. Even with a full gas tank and 35 mpg, you're going to end up with an empty tank on a deserted highway with no shelter but a creepy haunted old mansion. Sound like some of the projects you've worked? We thought so too. So with our favorite creepy holiday approaching, we decided it was time to publicize our favorite rules and tools for surviving a (project) horror movie. There are thirteen, naturally; read at your own risk!


The 13 Rules for Surviving Projects


- Never do anything on a dare
- Don't pickup hitchhikers
- Recombinant DNA is not a toy
- It's probably deserted for a reason
- Wear running shoes
- Check the ammo supply
- Turn on the lights
- It wasn't just the cat
- Look behind you
- Don't split up
- Don't be afraid to call in backup
- Coffee is for when the building's not on fire
- No, it's not dead yet


1. Never Do Anything on a Dare


Any idea that's followed by the words "that would be really cool" is a good candidate for a stop, look, and think approach. Sticking your hand into dank, musty markets or spending the night in an abandoned product line in order to impress the execs is only going to work if you don't lose something important (like reputation, capital, or critical project resources). This template walks you through the entire rationale, so you can assess new ideas in a consistent, repeatable fashion that allows you to compare their benefits against each other as well as against objective reality. (Hint: Talking dolls are pretty much always a bad idea.)


2. Don't Pick Up Hitchhikers


A little yes here, a little yes there, and before you know it you're careening down the road with a homicidal clown and a guy with bolts sticking out of his neck. You'll never get to that quaint little town festival in the middle of nowhere if you keep stopping to pick up strangers. This worksheet helps you keep the project goals in clear view, and makes it very obvious what is out-of-bounds. Having a common understanding of these boundaries, in a simple "is/is-not" form, reduces do-overs and makes it easier to sort out requests that make sense and those that should prompt you to hit the door locks and floor it.

3. Don't Fool Around with Recombinant DNA Technology Unless You Know What You're Doing


Before you decide to throw in a little frog DNA just to round out the edges, make sure you've really thought it through. This table format provides a concise way to document, analyze, and communicate the scope and feature alternatives for your project. Consider and capture the critical factors, and compare the impact of various combinations on cost, schedule, resources, risk, and potential staff loss to rampaging carnivorous reptiles.

4. It's Probably Deserted for a Reason


If the locals say it's haunted or cursed, listen to them. They've been around a lot longer than you have. They can probably tell you exactly what the problem is, or at least where, if only someone asked, and if only they weren't so busy fighting off all those ravenous change requests and shambling zombies. This paper by Cinda Voegtli outlines how to get everyone to put down the shotguns, step out of the bunkers, and develop a new plan of attack so you can get your product out the door.


5. If You Expect Zombies, Go With the Running Shoes


Those shambling zombies are a LOT faster than they look; high heels and oxfords aren't going to cut it. Neither will laying around and screaming about it, for that matter. You need to have a plan and an escape route, and you need to know when to use them both. This collection of tables and guidelines helps you develop a comprehensive risk plan covering both technical and non-technical areas, and analyze them against factors like potential impact, probability, and how hard it is to spot them on a dark night or in a thick fog. It covers risk ownership too, so you can ensure someone is actually watching for the zombies instead of waiting for them to sneak up on you.


6. Check for Bullets BEFORE You Need the Shotgun


Why does it always come as such a surprise when they pull the trigger and nothing happens? Did no one think to look for ammo when they grabbed the weapons out of that old shed behind the farmhouse? This template provides a simple table for documenting the equipment and tools that will be needed during a project, before the project. Your list should include the things you'll need (decoy hockey mask, working flashlights, chainsaw repellent), as well as vital information like need dates and owners (before the city-sponsored graveyard relocation, any character that has lines in the second half of the script) to ensure that equipment is available on schedule.

7. Turn On the Lights


Something's gone bump in the night, so you fumble around for a bit, see something scampering around out of the corner of your eye, and announce with a relieved sigh that "it was just the cat." Wouldn't it be a lot easier and less stressful if you flipped on the light switch? This template includes several different one-page document formats for getting a true picture of a project or portfolio at a glance, and a presentation format for talking to management-everything you need to make sure that no one (including you) is stumbling around in the dark.


8. P.S.: It Wasn't Just the Cat


That little scamper you saw out of the corner of your eye? It was actually the cat trying to get the heck away from the giant axe-wielding maniac wreaking havoc on the other side of the room. (This is why turning on the lights is so important.) Sure would be nice if you had a high-level view of everything that's going on right now. This easily scanned form was designed to keep executives-who never read more than a page no matter what's chasing them-up to date on project progress, by showcasing all the major project parameters: scope, goals, resources, expenses, and risks. A compact form like this is a great overview for project managers as well as execs; it doesn’t leave axe-wielding maniacs anywhere to hide.


9. Look Behind You


How much carnage would be averted if people would just look over their shoulder once in a while? Reviewing the lessons learned from previous projects gives you a front-row view of the bogeymen that stalked them. If you don't have these invaluable records from the previous team(s), consider calling the lessons learned meeting yourself. This sample agenda shows you how to capture a wealth of information in just a few hours, with time left over to brainstorm better approaches. Even if you're calling on memories from months ago, people have an amazing capacity to remember disastrous results and near misses, and will probably be able to tell you right where the bogeymen are hiding. Shouldn't you know too?


10. Don't Split Up


"Let's split up" is almost always a terrible idea. (But go with it if you're pretty sure the other guy is one of the pod people.) You don't want to be the guy standing around wondering where everyone went and why the fog suddenly got so thick. So if you're pulling in an outside team, make sure they're really on the team, with a clear understanding of your goals, objectives, and timelines. This paper draws on QRPD principles to provide real world examples and specific recommendations for keeping everyone from running off in different directions.

11. Just Call the Cops Already!


When the creepy villain is chasing people around in the fog, how come they never call for backup? Self-sufficiency is admirable, but certain situations call for an authority figure with a really big gun and access to SWAT gear. An escalation process can help your team deal with high-level issues like threats to staffing (stealth reassignments, mysterious portals in appliances), unmet group dependencies (recalcitrant science teams who would rather "study it" than work on the antidote), scope disagreements (like whether to quarantine the neighborhood or the entire town), and issues with functionality (has anyone made sure the brand-new getaway car still starts?). This guideline will help you establish an escalation process appropriate to your situation. Examples from several different project environments are included, so you can see how escalation plans work when different factors like company culture and project complexity come into play.

12. Making Coffee Will Not Stall the Monsters


You'd better believe that the bad guys aren't popping off for a quick cappuccino while they discuss how to get around the hastily-rigged trap you just installed on the back porch. You need a better plan, and fast. By all means continue with the coffee maker, as long as it hasn't spoken a dead language or sucked anyone into a vortex yet. But while it's brewing, you might want to try some of these brainstorming techniques for getting a group focused on finding and fixing the problem, once and for all. Pound for pound, problem solving beats hitting the panic button (or the double-non-fat-whipped-mocha-lattes).

13. No, It's Not Dead Yet


Everyone knows that monsters have more lives than cats from suspicious cemeteries. If you need to send your monster project to its just rewards, you don't want it to pop up again (and again and again) where you least expected it. This detailed guideline helps you plan a strategy for closing it down once and for all, without leaving a nasty mess behind in the process.