Wednesday, April 27, 2011

8 Things You Should Never Say to Employees | BNET

8 Things You Should Never Say to Employees | BNET

The Right to Management Competence

 

Imagine that you're conducting a performance appraisal with one of your people. You're discussing a major project that didn't turn out as hoped and you've just asked him why.

"Why did it fail?" he says. "Lots of reasons, but mostly because we didn't get what we needed from you. We were depending on other groups, but they couldn't have cared less. In fact, they didn't even know what we were doing and how it would help them. Plus, we never had a real strategy or plan and so we pretty much winged it every day, and every day you seemed to change your mind about what was important. In fact, Jack (your boss) never understood the project. So when people asked him, he couldn't support us."

What would your reaction be? We suspect a part of you would be thinking: "He can't say this. This is insubordination. I'm evaluating him. This isn't how it works."

And you'd be right. This isn't how it usually works. In virtually all organizations we know, the right to have formal expectations of others flows only downward, just like formal authority.

Notice we said "the right to have expectations." People certainly have expectations of those above them in the hierarchy, but there's little if any recognition of those expectations. Certainly there's no recognition of the right to have them.

We suggest that point of view should be questioned. We certainly don't think every expectation people have of a boss is appropriate. Many are naive, self-serving, and dysfunctional for the group. But there is one right we believe needs recognition by bosses, organizations, and all the people in them:

People have a right to competent management.

This is not a new idea. Even in Roman times it was said thatevery soldier had a right to competent command. In the same way, your people can and should expect you to be an able boss. They should expect this in the same way and for the same reason they can expect to receive the minimal tools and resources needed to do the work assigned to them. And they should be allowed to discuss these expectations with you, their boss, just as you and they discuss your expectations of them.

"That's fine, in theory," you're probably thinking. "But who knows what 'competent' management is? Look at the millions of words written about the subject."

Certainly there's room for ongoing negotiation, especially around how the requirements of good management apply in a given situation. But that's little different from your own expectations of your people. You know the general elements of what's required of each; how those elements apply to specifics is open to ongoing discussion.

What good management comprises — what bosses do to make their people productive — isn't really a mystery. We can argue about the exact wording, but the basic elements aren't in doubt. We've summarized them in what we call the "3 Imperatives": Manage yourself, manage your network, manage your team. In writing about these elements, we've described them in terms of what good managers do and what all managers should strive to do. But it's not hard to rephrase them from a direct report's point of view — in effect, a "Direct Reports' Bill of Rights" — as follows.

Every direct report should be able to expect that the boss will:

  • Be Trustworthy. Trust is based on competence and character, and so people can expect the boss (a) will know what to do and how to do it, and (b) will possess fundamental values, standards, interpersonal skills, emotional maturity, and levels of caring that support the work and those doing it.
  • Exercise influence beyond his or her group. Every group works in a web of interdependence within a broader organization and beyond. Success — through, for example, securing needed resources, attention, and cooperation — depends on the boss's ability to exercise influence in that broader context through a network of ongoing, mutually supportive relationships.
  • Create a team of his or her group. A group is a collection of people who work together. A team is a group whose members are mutually committed to pursuit of a clear purpose and the achievement of goals based on that purpose. In a team there is a "we" separate from the individuals involved and the people in that "we" believe they will all succeed or fail together. Why is this important? Because members of a team are more engaged and committed and as a group are more innovative and productive. A competent manager knows how to transform a group into a team — by fostering a compelling purpose, worthwhile goals and clear plans, productive work processes, and a culture of "we."
  • Recognize individuals and support their development. People want to belong and be recognized for themselves. Thus, an effective manager knows individual team members, works with them, supports their development, and recognizes their contributions — all within the context of the team.

How would you fare in the eyes of your people if they applied these standards? What if your organization told everyone that this is what all employees should expect of their managers? What if, in your performance reviews with your people, you discussed with them your own performance in terms of the expectations above?

http://blogs.hbr.org/hill-lineback/2011/04/the-right-to-management-compet.html

Thursday, April 21, 2011

Fun: The Key to Better Team Collaboration

 

Remember when collaborating was fun?

The news that Google’s staff bonuses now depend on the success of its new +1 social rank tool — and Mathew’s observation that “you can’t threaten people into being social” — brings to the fore an important but often unacknowledged issue surrounding collaborative business: While businesses focus on choosing tools, prescribing acceptable network policies and measuring ROI, the easiest way to get staff to collaborate is, well, to make it fun.

One organization I worked with last year used an internal social network that was literally devoid of any humor or personality whatsoever. Try as I might, I couldn’t bring myself to use it, and I wasn’t the only one. Who wants to “engage” when there’s nothing but a constructed corporate persona to engage with?

If you want staff to collaborate productively with one another, your suppliers, peers or customers, the simplest way is to make it fun.

You may think that’s unrealistic; a non-essential element in the cut-and-thrust of today’s heady business competition. But the fact remains that it’s the easiest way to get staff to work together.

What makes collaboration fun?

Human Contact

Collaboration is fun because we do it with others. Online collaboration helps us very efficiently avoid the tyranny of distance, which is equally great for making disparate teams feel closer, and for allowing us to learn from people we’ll never get a chance to meet.

We all know the kick that comes from engaging with someone we admire — albeit at a distance — over Twitter or Facebook. That thrill is echoed every day in good collaborative exchanges within teams.

Personalities

Personalities can make or break the collaborative effort. Evolving team member disagreements and friendships all have their impacts on the collaborative fun factor.

Establish your collaborative space as a supportive, open platform on which individuals’ unique aspects are welcome, and your staff will likely have more fun there.

A Shared Goal or Direction

Being part of something bigger than the individual is a key motivator for many collaborators. Most of us want to belong, and belonging involves sharing. Shared experience—especially the overcoming of collective challenges, and the achievement of common goals—strengthens team bonds and supports future collaborative efforts.

Think of the people you love collaborating with on work projects. They’re probably people who share your passion for the work, and who can communicate that enthusiasm equally well through in-person or online exchanges.

Learning, Contribution and Recognition

For most professionals, a key personal motivation for collaboration is the opportunities it provides to learn from peers, contribute to the collaborative effort, and be recognized for the good work we do by people we admire.

That cycle of mutual respect, admiration and knowledge exchange is self-perpetuating. Valuable, rich collaborative relationships usually continue even when team members change employers, and no longer have access to in-house collaborative systems.

The Payoff

If you’re thinking, “that’s fine and all, but it sure sounds like a lot of fun,” you’re right. But remember: more fun means stronger staff engagement, more effective collaboration, and greater productivity.

If your organization is one of those that’s still worried about the potential for staff to “spend all their time on social networks,” it’s way past time to join the age of social business. Engaging with staff about the networks they enjoy, and considering the ways they could be used to enrich workplace collaboration might be a good first step towards making your organization more collaborative and effective.

Teams that don’t collaborate well should assess their operation on the basis of the elements mentioned here. Certain tools may help you overcome specific collaborative issues, but the astute team leader will consider each possible solution in light of its potential to enhance the collaborative fun factor—knowing that more fun will likely lead to a greater ROI.

Anil Ananthaswamy: What it takes to do extreme astrophysics | Video on TED.com

Anil Ananthaswamy: What it takes to do extreme astrophysics | Video on TED.com

Joel Stein: the TIME 100 Most Influential Things in the World - The 2011 TIME 100 - TIME

Joel Stein: the TIME 100 Most Influential Things in the World - The 2011 TIME 100 - TIME