Suppose you're a team lead of some kind, and a team member — call him Oscar — is exhibiting a pattern of substandard performance that limits team performance. If you aren't Oscar's supervisor, how can you put this right? What are some common mistakes to avoid?
Let's define performance issues first. A performance issue is any pattern of failing to meet organizational standards of conduct, attitude, or results. Examples include accomplishing assigned tasks late, excessive questioning of the legitimacy of assignments, or failing to comply with team priorities or norms.
The essential elements of a performance issue are the pattern and the organizational standards. Occasional deviation from organizational standards isn't a performance issue, because Life happens. What makes deviation from standards a performance issue is repetition. And even though you might have expectations relative to conduct, attitude, or results, performance is an issue only if your expectations are consistent with organizational standards.
Here are seven guidelines for dealing with performance issues as a non-supervisor.
- Confer with your supervisor and Oscar's supervisor
- Before acting, confer with your supervisor. Alert him or her to the problem. Ask for comments on your plan. Do the same with Oscar's supervisor. Emphasize to both that you'd like to settle the matter personally with Oscar. Express confidence.
- Have a private conversation
- Speak with Oscar privately. Avoid embarrassing him publicly.
- Remember: you aren't Oscar's supervisor
- Approach the conversation with Oscar as a negotiation between peers. Because you don't supervise Oscar, you cannot issue orders or commands. Make your needs known to Oscar, and request his cooperation.
- State your concerns clearly
- Express your concerns, explaining to Oscar how his performance compromises team performance. Ask Oscar for any information that could change your perspective.
- Seek agreement
- The goal of the conversation with Oscar is agreement about what will change and when. Determine what he needs, and provide it if it's reasonable. Write down what you both agree to, in hardcopy, signed by both of you.
- If you can't agree, explain what's next
- Tell Oscar Occasional deviation from organizational
standards isn't a performance issue.
It is repetition that makes
substandard performance an issue.that you're disappointed that agreement wasn't possible, and that you'll be consulting your supervisor about next steps. Oscar will likely contact his supervisor to prepare a defense, but if he doesn't indicate his intention to do so, recommend it to him.
- Follow through
- If Oscar makes real progress, celebrate it in some way. Express your delight and confidence in him. If Oscar doesn't make sufficient progress, consult your supervisor and explain what went wrong. Let him or her know that the team's objective is at risk. Work together to deal with the problem.
If your supervisor can't or won't intervene effectively to address the issue, then the task for which you're accountable might be at risk. If you have a risk plan, add this item, omitting Oscar's actual name, of course. At this point, you've done what you can do. It isn't satisfying, but that's that. Top Next Issue
Are your projects always (or almost always) late and over budget? Are your project teams plagued by turnover, burnout, and high defect rates? Turn your culture around. Read 52 Tips for Leaders of Project-Oriented Organizations, filled with tips and techniques for organizational leaders. Order Now!
Your comments are welcomeWould you like to see your comments posted here? rbrenPxDDyVgQVwoHZSYbner@ChacVQITmrLLoljVmyZYoCanyon.comSend me your comments by email, or by Web form.
About Point Lookout
Thank you for reading this article. I hope you enjoyed it and found it useful, and that you'll consider recommending it to a friend.
Support Point Lookout by joining the Friends of Point Lookout, as an individual or as an organization.
Do you face a complex interpersonal situation? Send it in, anonymously if you like, and I'll give you my two cents.
More articles on Personal, Team, and Organizational Effectiveness:
- Take Regular Temperature Readings
- Team interactions are unimaginably complex. To avoid misunderstandings, offenses, omissions, and mistaken
suppositions, teams need open communications. But no one has a full picture of everything that's happening.
The Temperature Reading is a tool for surfacing hidden and invisible information, puzzles, appreciations,
frustrations, and feelings.
- The Ups and Downs of American Handshakes: II
- Where the handshake is a customary business greeting, it's possible to offend accidentally. Here's Part
II of a set of guidelines for handshakes in the USA.
- Decisions: How Looping Back Helps
- Group decision-making often proceeds through a series of steps including forming a list of options,
researching them, ranking them, reducing them, and finally selecting one. Often, this linear approach
yields disappointing results. Why?
- Team Risks
- Working in teams is necessary in most modern collaborations, but teamwork does carry risks. Here are
some risks worth mitigating.
- False Summits: I
- Mountaineers often experience "false summits," when just as they thought they were nearing
the summit, it turns out that there is much more climbing to do. So it is in project work.
Forthcoming issues of Point Lookout
- Coming July 26: Strategic Waiting
- Time can be a tool. Letting time pass can be a strategy for resolving problems or getting out of tight places. Waiting is an often-overlooked strategic option. Available here and by RSS on July 26.
- And on August 2: Linear Thinking Bias
- When assessing the validity of problem solutions, we regard them as more valid if their discovery stories are logical, than we would if they're less than logical. This can lead to erroneous assessments, because the discovery story is not the solution. Available here and by RSS on August 2.
I offer email and telephone coaching at both corporate and individual rates. Contact Rick for details at rbrendMdnXQNcSWYMzMwdner@ChacJrVxkPSlLKsXlvFAoCanyon.com or (617) 491-6289, or toll-free in the continental US at (866) 378-5470.
Get the ebook!
Past issues of Point Lookout are available in six ebooks:
- Get 2001-2 in Geese Don't Land on Twigs (PDF, USD 11.95)
- Get 2003-4 in Why Dogs Wag (PDF, USD 11.95)
- Get 2005-6 in Loopy Things We Do (PDF, USD 11.95)
- Get 2007-8 in Things We Believe That Maybe Aren't So True (PDF, USD 11.95)
- Get 2009-10 in The Questions Not Asked (PDF, USD 11.95)
- Get all of the first twelve years (2001-2012) in The Collected Issues of Point Lookout (PDF, USD 28.99)
Are you a writer, editor or publisher on deadline? Are you looking for an article that will get people talking and get compliments flying your way? You can have 500 words in your inbox in one hour. License any article from this Web site. More info
- Creating High Performance Virtual Teams
- Many people experience virtual teams as awkward, slow, and sometimes
frustrating. Even when most team members hail from the same nation or culture, and even when they all
speak the same language, geographic dispersion or the presence of employees from multiple enterprises
is often enough to exclude all possibility of high performance. The problem is that we lead, manage,
and support virtual teams in ways that are too much like the way we lead, manage, and support co-located
teams. In this program, Rick Brenner shows you how to change your approach to leading, managing, and
supporting virtual teams to achieve high performance using Simons' Four Spans model of high performance.
Read more about this program. Here's a date for this
- Baci Grill, 134 Berlin
Road, Berlin, CT 06416: September 19,
Monthly Meeting, Southern New England Chapter of the Project Management Institute. Register now.
- Baci Grill, 134 Berlin Road, Berlin, CT 06416: September 19, Monthly Meeting, Southern New England Chapter of the Project Management Institute. Register now.
- The Race to the South Pole: Ten Lessons for Project Managers
- On 14 December 1911, four men led by Roald
Amundsen reached the South Pole. Thirty-five days later, Robert F. Scott and four others followed. Amundsen
had won the race to the pole. Amundsen's party returned to base on 26 January 1912. Scott's party perished.
As historical drama, why this happened is interesting enough, but to organizational leaders, business
analysts, project sponsors, and project managers, the story is fascinating. Lessons abound. Read
more about this program. Here's a date for this program:
- CTCPA, 716 Brook Street,
Rocky Hill, CT 06067: September 20,
Full-day Workshop, Southern New England Chapter of the Project Management Institute. Register now.
- CTCPA, 716 Brook Street, Rocky Hill, CT 06067: September 20, Full-day Workshop, Southern New England Chapter of the Project Management Institute. Register now.
- The Power Affect: How We Express Our Personal Power
- Many people who possess real organizational power have a characteristic demeanor. It's the way they project their presence. I call this the power affect. Some people — call them power pretenders — adopt the power affect well before they attain significant organizational power. Unfortunately for their colleagues, and for their organizations, power pretenders can attain organizational power out of proportion to their merit or abilities. Understanding the power affect is therefore important for anyone who aims to attain power, or anyone who works with power pretenders. Read more about this program.