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? rbrenmhXARWRMUvVyOdHlner@ChacxgDmtwOKrxnripPCoCanyon.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:
- Smart Bookshelves
- If you like to browse in bookstores, you probably know the thrill of new ideas and new perspectives.
When I find a book worth reading, I want to own it, and that's how it gets to my shelf. Here are some
tips to help you read more of what you really want to read.
- Figuring Out What to Do First
- Recovering Time: I
- Where do the days go? How can it be that we spend eight, ten, or twelve hours at work each day and get
so little done? To recover time, limit the fragmentation of your day. Here are some tips for structuring
your working day in larger chunks.
- Why Do Business Fads Form?
- The rise of a business fad is due to the actions of both its advocates and adopters. Understanding the
interplay between them is essential for successful resistance.
- Unnecessary Boring Work: I
- Work can be boring. Some of us must endure the occasional boring task, but for many, everything about
work is boring. It doesn't have to be this way.
Forthcoming issues of Point Lookout
- Coming July 17: Barriers to Accepting Truth: II
- When we work to resolve differences of opinion at work, we often depend on informing each other of what we believe to be real facts. At times, to our surprise, our debate partners reject these offerings as untrue, even when they're confirmed authoritatively. Why? And what can we do about it? Available here and by RSS on July 17.
- And on July 24: The Stupidity Attribution Error
- In workplace debates, we sometimes conclude erroneously that only stupidity can explain why our debate partners fail to grasp the elegance or importance of our arguments. There are many other possibilities. Available here and by RSS on July 24.
I offer email and telephone coaching at both corporate and individual rates. Contact Rick for details at rbrenmhXARWRMUvVyOdHlner@ChacxgDmtwOKrxnripPCoCanyon.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, 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
- The Race to the South Pole: Lessons in Leadership
- 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. We'll use the history of this event to explore
lessons in leadership and its application to organizational efforts. A fascinating and refreshing look
at leadership from the vantage point of history. Read
more about this program. Here's a date for this program:
- Baldwin-Wallace University, 275 Eastland Road, Berea, Ohio
44017: November 7,
Kerzner Lecture Series/International Project Management Day, sponsored by Baldwin Wallace University and the Northeast Ohio Chapter of the Project Management Institute.
- Baldwin-Wallace University, 275 Eastland Road, Berea, Ohio 44017: November 7, Kerzner Lecture Series/International Project Management Day, sponsored by Baldwin Wallace University and the Northeast Ohio 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.