Performance Issues for Nonsupervisors

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 nonsupervisor.

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 welcome

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.

This article in its entirety was written by a human being. No machine intelligence was involved in any way.

Point Lookout is a free weekly email newsletter. Browse the archive of past issues. Subscribe for free.

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.

Related articles

More articles on Personal, Team, and Organizational Effectiveness:

Decisions, Decisions: II

Most of us have participated in group decision making. The process can be frustrating and painful, but it can also be thrilling. What processes do groups use to make decisions?

Communication Refactoring in Organizations

Inadequate communication between units of large organizations is one factor that maintains the dysfunction of "silo" structures in large organizations, limiting their ability to act coherently. Communication refactoring can help large organizations to see themselves as wholes.

Wacky Words of Wisdom: V

Adages, aphorisms, and "words of wisdom" are true often enough that we accept them as universal. They aren't. Here's Part V of some widely held beliefs that mislead us at work.

Monday Morning Minute Message Madness

As a leader of a large organization, if you publish a "Monday Minute Message" to help employees identify with the organization as a whole, there are some practices that might limit the effectiveness of the program. Six suggestions can be helpful.

Personal Feasibility Decisions

When considering whether to exploit a rare but desirable opportunity, there is a risk that desire can overcome good sense. Having at hand a predefined framework for making such decisions reduces the risk of blundering by acting in haste.

See also Personal, Team, and Organizational Effectiveness and Effective Communication at Work for more related articles.

Forthcoming issues of Point Lookout

Coming May 1: Antipatterns for Time-Constrained Communication: 2

Recognizing just a few patterns that can lead to miscommunication can reduce the incidence of miscommunications. Here's Part 2 of a collection of antipatterns that arise in communication under time pressure, emphasizing those that depend on content. Available here and by RSS on May 1.

And on May 8: Antipatterns for Time-Constrained Communication: 3

Recognizing just a few patterns that can lead to miscommunication can reduce the incidence of problems. Here is Part 3 of a collection of antipatterns that arise in technical communication under time pressure, emphasizing past experiences of participants. Available here and by RSS on May 8.

Coaching services

I offer email and telephone coaching at both corporate and individual rates. Contact Rick for details at rbrendPtoGuFOkTSMQOzxner@ChacEgGqaylUnkmwIkkwoCanyon.com or (650) 787-6475, 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, )
• Get 2003-4 in Why Dogs Wag (PDF, )
• Get 2005-6 in Loopy Things We Do (PDF, )
• Get 2007-8 in Things We Believe That Maybe Aren't So True (PDF, )
• Get 2009-10 in The Questions Not Asked (PDF, )
• Get all of the first twelve years (2001-2012) in The Collected Issues of Point Lookout (PDF, )

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-1000 words in your inbox in one hour. License any article from this Web site. More info