How to Handle Lateness – It’s Everywhere!

Projects are late. Promises aren’t kept. Schedules are tweaked or ignored. We human beings are pretty bad at starting and ending our tasks on time, no matter how much planning we do.

A good article-plus-podcast Why We’re Late explains the causes. One is that lateness is due to the “planning fallacy” – our estimates of how long a task or project will take is often too optimistic. We don’t plan for all the possible interruptions we might encounter – after all, as the article said, we plan to succeed, not to fail. Two other contributors to lateness are:

  1. On big complex projects, we often forget to plan for the coordination required to pull various aspects of the project together.
  2. On a more personal level, we forget that humans aren’t very good at “impulse control”, meaning we procrastinate because we do what we want to do at the moment, instead of sticking to our scheduled plan. Like, I’m going to check my email for a minute first? Yeah, sure, and half an hour later I’m into a whole other mini-project. We humans are pretty distractible!

Solutions? They mention software that helps project team members see what other players are responsible for, and how project parts are related by schedules and dependencies. They suggest tracking your performance – get data on what takes a project off-course or distracts you personally from getting a task done. And also, of course, using that data to improve your time estimates.

Lateness is everywhere. People are late to meetings. Managers give assignments without a specific deadline, often over-using the word “priority” as if that will make things go faster. And when an assignment is turned in late, nobody says, “This is three days overdue.” We let it go.

Communication can shift the lateness habits of a work group. Performance Conversations and Closure Conversations help give more attention to timelines, including follow-up on whether deadlines were met.

  • Alex says, “I’d like to present this policy brief at the Board Meeting on Tuesday. Can you get the references needed, collect comments from the other three Advisors, and include the changes they suggest? I would need that finished by Friday close of business.”
  • Justin says, “Sure, I can do that. Send it over to me.”
  • Alex confirms that they have an agreement: “You promise you have time for this? I don’t want to be scrambling to pull things together on Monday.”
  • Justin: “Yep. Consider it done.”

So, a request from Alex + a promise from Justin = an agreement. Performance Conversation complete.

  • Justin, on Friday at 5:45, says, “Sorry, but one of the Advisors hasn’t responded yet. I’ve sent you the update using comments from the other two, but don’t know if that’s enough.”
  • Alex says, “Thanks, I’ll look at it over the weekend. But, FYI, close of business means 5:00 PM, not 5:45, so I was wondering whether you were going to deliver. I say this because I want all of us to pay more attention to keeping time agreements. I’ll talk with Advisor #3 this weekend about that too. Sorry I didn’t make it clearer before. And, despite being picky about timing, I really appreciate that you’ve made it possible for me to review this and plan my Board presentation over the weekend. Thank you very much.”

Closure Conversation complete. Bringing all “four A’s” into a conversation is powerful:

  • Acknowledge the facts of the situation – what happened and why it matters;
  • Appreciate the people – recognize the value of their effort and contribution;
  • Apologize for mistakes and misunderstandings – cleanup improves trust; and
  • Amend broken agreements – set up for a future where agreements can be honored.

The article pointed out there is data going back more than 100 years showing that at least 80% of projects have cost and/or time over-runs. Making clear agreements, and communicating with people about the success and failure of those agreements, can shift the communication habits of a work group to support being on time.

Training for Accountability: First Things First

Erin, a restaurant manager I know, was approached by a complaining customer the other day. Here’s a summary of what she told me about it:

  • Customer: The Servers here never paid any attention to us for over 15 minutes. No one even stopped by to say they would get back to us. Do your people know which tables they are responsible for serving?
  • Erin: Yes – it was really busy. And they are young, and most of them only work part-time. We train them, but they don’t always pay attention.

OK, it sounds like Erin is not listening to her Complaining Customer. But it got worse:

  • Erin continues, “For example, we have been training them how to set the tables properly – the flowers in the center, the salt and pepper on the right side, the sweetener on the left. But still they forget!”

How did Erin veer off into table-setting décor? She was defensive in the face of a complaint, and maybe that impaired her ability to sincerely acknowledge what the customer was saying. I heard the complaint as Servers neglecting their customers or not “owning” their tables. But maybe they don’t have “their” tables – maybe they just pay attention to certain people or locations they prefer.

I remembered putting myself through college as a waitress, when my boss made it very clear which tables I needed to tend to. Whoever sat at “my table” was “my customer”. I never heard much about settings or floral décor, just an emphasis on “clean and neat”. If your training emphasizes where to put the salt shaker, that’s what people will think is most important.

Erin’s job is now to improve her staff’s accountability for customer-oriented results. People can be accountable for the products, services, and communications they deliver – but only if they know exactly what those “deliverables” are. At a restaurant, greeting customers is one deliverable; taking food orders from customer to kitchen is another. Bringing food, checking on customer needs, and clearing dishes – all are results a restaurant Server is accountable for delivering. Ideally, that’s the core of training.

Erin and I talked about this, and at some point, Erin said, “You know, with such slow service I bet that customer didn’t give a hoot about the flowers, or whether the sweeteners were on left or even there at all. I’d better train people on what good customer service looks like.”

Accountability’s middle name is “count”, which is a clue that training people on their work responsibilities needs to be specific. If Erin’s servers don’t “own” their station of 4-7 tables (depending on space arrangements, etc.), then it’s time to invent the idea of “stations”, number the tables, and assign certain table numbers to each Server – and talk about the specifics of serving customers at those tables. That is something everyone can count, and Erin can count on her people to serve customers well.

The Manager’s Golden Rule: Make Production Goals Visible

Carrie is a longtime friend who has one persistent delusion: she thinks the people in her work group are all committed to producing the results she mentioned in the weekly staff meeting. But the truth is that she is the only one who really focuses on Getting Things Done.

Poor Carrie is astounded – at least once a week – to discover (for the millionth time) that not everyone is dedicated to Getting Things Done. “What’s the matter with them?” she asks me. “Do they forget what we’re doing here? Or are they just not organized for getting their work done?”

And, for the millionth time, I remind her that if you don’t have a visible “scoreboard” of the results you want, most people will focus on their own preoccupations. As I learned in a recent Landmark Worldwide program, most of us are going through life on auto-pilot, at least most of the time.

I remember when I learned that some people are not interested in Getting Things Done. Our publisher broke the news to me (ever so gently) as we were all trying to come up with a subtitle for our book, “The Four Conversations”. Me: “What? Some people don’t care about Getting Things Done? What are they doing with their lives?” OK, I gave up my subtitle idea and bowed to their expertise, eventually settling on the subtitle “Daily Communication that Gets Results” .

In case you, like Carrie, are interested in Getting Things Done – both for yourself and with other people – it helps to know all three parts of the Manager’s Golden Rule:

  1. Spell out the results you want to see.
  2. Specify when you want to see those results: what day, and what time. And, if you have other people who need to produce or deliver something, make note of that too.
  3. Then display that simple chart in a place where you (and everybody else) can see them at least twice a day.

A sample of items from Carrie’s chart looks like this:

Get It DONE! When Who Does It?
Newsletter out Noon – every 3rd Friday Arnie
Training materials updated & printed Friday 3 PM before every training program delivery Training-IT-Marketing Committee
Subscriber Report Before Tuesday staff meetings (9:15 am) Marketing Team
Budget plans & projections For the mid-month Tuesday staff meeting Kelsey’s Money Team

Carrie posted it on the door outside the meeting room, in a hallway between people’s offices and the coffee pot, where everyone would see it. One member of the Marketing Team told me, “It gives me a little boost every time I go by it, just to see how we’re all working together to make something happen.” Carrie rolled her eyes when she heard about that, and said, “They should know their jobs.” (Sometimes she’s crabby.)

Yes, maybe. Or maybe it’s just nice to be reminded that there IS a “big picture” purpose for the team, and not just a bunch of humans running around being busy. I know I keep my own list on the wall in my study. It helps me manage this rogue brain.

How to Deal With a “Do-It-My-Way” Person

Over the years, I’ve collected some tips from working people on the ways they solved a communication problem with a boss, a co-worker, or even a friend or family member. One favorite was how people interacted with someone who saw only “One Way – My Way” to do something. Here are a few examples of how people handled those conversations.

Amanda says, “I had a micro-manager boss who wanted everything done just-so. He was nit-picky about how we formatted internal documents, whether we did this task first or second, and who we collaborated with to get things done. One day I reminded him of our department’s goal: “Customer First – Service Excellence”. I told him that internal documents, task sequencing, and work partners didn’t really matter for that goal. He was shocked but didn’t say anything. Two days later he told me I was right, and that he had just been trying to help me. We talked about it, and at some point, he said he was confident I didn’t need that kind of “help” and that he trusted me to focus on our goals. It’s been a different workplace then, and not just for me. I’m glad I spoke up.”

Davis told me, “One of my colleagues seems to think he is a coach. He tells me what to do and how to do it – and he has no interest in hearing my perspective at all. The other day he lectured me about how to fix a computer problem I was having. I had just looked up how to fix it and was almost done when he started giving directions. I heard him out, then showed him the instructions I was following from the computer manufacturer. He kept arguing for his ideas until I asked him to stop, and to let me finish what I was doing. Then I told him, “I promise that I will ask you whenever I need some help or coaching. You’re good at that, so I really will do it. But not this, not now.” He gave me a little smile and left me alone. I just might call him sometime. Or not.”

Max told me about an argument he had with his cousin about his car maintenance plan. He said, “I looked at the manual that came with my car. It’s a used car, so I even checked with the dealership to be sure I take care of it right. But my cousin disagreed and told me three other things I should do. I’m not going to do them, but he kept bringing it up. I finally told him, “Look, I’m not going to do those things, so you should stop wasting your breath.” He looked at me like I’m an idiot, and said, “That’s on you, then, whatever happens.” As if I didn’t already know that. But at least he has stopped bugging me about it. I’ll keep talking straight with him and maybe someday he will understand that I’ve already made up my mind about how I’m going to do some things. That way he can save his breath with me. And we can still be friends and go fishing together.”

The best bottom-line tip I got was this: When people are trying to tell you what to do, if you have already decided what you’re going to do, then just tell them you’ve already decided – and that you hope they will support you. That kind of straight talk saves time and doesn’t hurt feelings – it works in almost every case of communicating with a person who is trying to set you on the “right path” of doing things their way. It’s OK to do it your way.

And another tip – this one for those annoying wanna-be coaches: Landmark Worldwide ( taught me I should never coach anyone who is not asking to be coached. Brilliant advice, and a time-saver for everyone involved.

Explaining Goals & Strategies is Not Enough: Bridging the Vertical Disconnect

High-level managers believe their mid-level managers and supervisors understand their organization’s top goals and strategies – and further, that they will align their work with those strategies. A recent article (see strategic misalignment) says that is not true. Why not? The article gives 2 reasons:

  1. “The top teams fail to agree among themselves on company-wide priorities.” More than half of the senior executives themselves could not state their own company’s official priorities.
  2. “Strategic alignment falls off a cliff from the top executives and continues to decline among lower-level managers.” It’s no surprise that when executives are not on the same page, those below don’t even know there is a page they could be on!

The authors’ recommended solution is that “Each top executive should consistently explain why his or her unit’s objectives matter for the team and for the company.” They went further, saying that executives should do a better job “explaining” to their mid-level managers how their unit’s goals fit into the overall organizational strategy.

Good advice, but note the authors rely on “explaining”, which is a weak form of communication. An alternative – and more effective – solution was demonstrated by one corporate client’s approach, using The Four Conversations as follows:

  1. Treat the executive-level goals and strategies as an “initiative conversation”, i.e., a proposal for corporate direction, rather than as a package of priorities to be delivered to – and consumed by – those below.
  2. Then arrange for several “understanding conversations” with the mid-level managers for the purpose of clarifying – and perhaps revising – the language of executive goals and strategies to match the language of mid-level goals and strategies (and vice versa). These dialogues design the bridge between organizational levels.
  3. Upon completing those dialogues, request that all members agree to use the organizational goals as a context for their more “local” goals, e.g., to keep both levels of goals and strategies visible in their workplace and part of their regular team meetings. These requests, promises, and agreements constitute “performance conversations”, and are useful to create a platform for alignment.
  4. Finally, revisit the success in implementing those alignment agreements on a regular basis with “closure conversations” that check whether – and how – the agreements are sustained and if they need to be updated in some way.

Communication to produce alignment between organizational levels will require attention to dialogue – a two-way discussion that incorporates the different perspectives into a unified perspective and language. Further, it calls for the rigor of making agreements to deploy those new perspectives and language at both ends of the bridge, as well as follow-up to support that implementation over time.

The vertical disconnect that can be found in most organizations does not always cause problems but the larger the organization, the larger the gap may become. Most people want to be effective and accomplish their own goals as part of accomplishing a larger purpose. It is the job of top executives to provide them with a well-structured opportunity to do that.

We Want Employee Engagement – But… Engagement in What?

The benefits of “employee engagement” are said to include better customer satisfaction, higher productivity, increased staff retention, etc.  Articles on improving “employee engagement” talk about how leaders don’t “treat employees respectfully”, or “take good care of employees”. There are surveys to measure those things, of course.

But if what we really want is better behaviors and attitudes from employees, let’s be straight about that. Because if we want employees to be “engaged”, then we have to offer something for them to be engaged in.  The unanswered question is, “Employees engaged in what?” Really, there is only one good answer:

  1. Employees are engaged when working to accomplish a clearly stated goal or objective.

The problem, however, is like that of the long-married couple, where the wife says, “We have been married for 46 years. Why don’t you ever say you love me?”  And the husband says, “I told you on our wedding day – how often am I supposed to repeat it?”

A once-a-year presentation by the CEO or Department Director about the progress and optimistic future of the company just isn’t enough. What gets people “engaged” in their work is something that is tied to a sense of accomplishment.  (Note: the word “accomplish” is derived from the Latin for “to fulfill or complete together.)

There are several tactics for engaging employees, but first you need to be up to something. An organization change? A new project or program? A task that is an important part of a larger goal?  You need something to engage people in working toward something – something that makes a difference to the organization and to other people in that organization. Just “doing stuff” is not engaging, and doesn’t activate “employee engagement”. So, you need a goal or end-point to be accomplished.

Then, you need to talk about the value of accomplishing that “something” – preferably more than every 46 years, and more than just at the annual retreat or holiday party. Here are three ways I’ve seen “engagement” work in organizations, large and small. They are all about communication: dialogue and discussion.

  1. Q&A sessions. After you roll out your newest strategic plan, or your next goal or project for people, have a few smaller-group “breakout session” where people get to ask and answer questions. This could be done in a round-table or a conference room. It’s good to have a recorder there, taking notes on what questions are important to people, and which answers need more development. It also shows people you are paying attention to their input.
  2. Success sessions. Once people are clear about the goals and objectives, another kind of discussion is to capture ideas (again, take notes) on what success will look like. Ask for what people think will (and won’t) work well, how to measure and track success and progress, and which people or groups should take on specific sub-goals or tasks. This lets people see the “big picture” of the work plan while also clarifying their “role in the goal”.
  3. Status update sessions. These are reliably regular meetings – weekly, bi-weekly, or monthly, depending on the timing of jobs to be done. They are to review the status of success and progress toward the goal, and the status of assignments for various responsibilities. It is also an opportunity to identify and discuss problems or delays, revise assignments, and declare some items complete – with a tip of the hat to those who have completed their task or project on-time and/or on-budget.

People do want to be engaged in their work. They just don’t always know exactly what their job or assignment is, or understand the bigger game they are working in. When you don’t know your “role in the goal”, or, sometimes, don’t even know the goal itself, there is nothing for you to engage in.

You want employee engagement? Spend a little time on engaging them in something that would be an accomplishment for them – and for you.


P.S. I’ll be away the next 2 weeks – working on something that is really engaging. Back to the blogging board when I return.

Preventing Change Fatigue: Burnout is Expensive – Communication is Not

When I first met the Supervisors at WaterCo, maintaining water lines in a Midwestern city, I was a “change consultant” hired to help them adapt to new regulations and to improve productivity. Those Supervisors were not happy to meet me: I was a consultant, and female, and they didn’t want anybody to “fix” them. That’s sometimes called “resistance to change”.

But I brought food to our meetings (very helpful!) and used my network approach to understand their work. We made circles and arrows on the whiteboard, identifying all the individuals and groups they interacted with at least once a week. They soon saw their work in a whole new way and forgave me for being a “girl consultant”. We all decided which changes would be most useful, and we implemented them together.

But the most important lesson I learned was why they were so “resistant” at that first meeting. They had been doing change projects – what they called “Churn & Burn” – for three years. One man explained it to me.

“We’ve been doing changes for so long that nobody really knows what their job is anymore,” Hank said. “We used to have routines. Now and then we’d make some improvements or get new equipment we had to learn about. But these days we get a new thing to change all the time, like our work processes, our assignments, or who we can and can’t talk to.”  He rolled his eyes, and I could tell he wasn’t interested in improving productivity – or anything else.

“Let’s look back over the last year,” I said to the whole group at that meeting. “I have 3 questions for you. (1) What was the last big change you guys made? (2) What were the results of that change?  And, (3) What did you do when it was complete?”

They looked at me as if I was talking Martian. Hank finally spoke up, saying, “The biggest change was when our crews were downsized from five men to four,” Hank said. “The result was we started using only one truck for over half our jobs, instead of two. I guess that saved money for the company. I know it saved some time for us, since we could get to our jobs faster. Also, different crew trucks had different equipment, so we went to the jobs that needed only what we were carrying – we didn’t have to take everything to every job site.”

“But it was never complete, never over,” he said. “Or at least they never said anything about that. They just told us to change the crew size, gave us three equipment lists to stock our trucks for different jobs, and went on to the next thing. We do the “Churn & Burn” dance these days – I guess that’s our new job description.”  They explained that the “churn” part of the dance was the endless instruction to modify a process, start or stop doing something, and use new forms for job reports or equipment requests. The “burn” part was that more people were leaving for other jobs – the Supervisors were losing experienced people and spending more time training new hires.

Bottom line: I met with the COO and got the statistics on the results of the change – dollars saved, job backlogs reduced, customer satisfaction improved. Then I asked him to come tell the Supervisors about the value of that last big change, and to thank them for all they did to implement it successfully. Surprise! The men appreciated it, and were able to work with me on ways to improve their productivity. They had ideas for what might work and how to do it!

So, it looks like a genuine “thank you”, supported by a little data, can turn change-resistant people who are doing the “Churn & Burn dance” into a team with a recognized accomplishment: they had made a difference for their company. A closure conversation – reviewing the status of a project with the people involved – goes a long way to curing “change fatigue” and restoring people to action. That COO learned the lesson too. Now he has monthly “change debrief” meetings now, with lots of statistics and lots of thank-you’s.

Developing People & Managing Performance… With Meetings? 

Markus, manager of a security team in a manufacturing company, has little patience for the idea that “developing people” (the quote marks are his) is the path to performance management.

He told me, “I get people who are already developed. They went to school, they have experience, they got hired here – and we have a good HR department for the other stuff. So my job is to work with my team to spell out our goals, schedules, and assignments, then track their assignments and results. They don’t need me to be their best friend – they need someone who will help them earn a good reputation for being effective.”

Lately, people are saying some mean things about managers: managers are selfish, unfriendly, and don’t relate well to the “human side” of their people. (Leaders, of course, are wearing their halos as perfect role models, while being busy with inspiring and motivating people. Leaders, good. Managers, not so much.)

Markus says, “The only human development I do is to structure our team meetings so that people get a good look at what we mean by performance. I use a tracking board of everyone’s assignments for the past week, and each person says something about what they got done and what problems they had or lessons-learned they acquired. Everyone sees the whole set of tasks and assignments, and everyone hears all the results. They learn from each other and offer support where it’s needed. Then we decide – together – what we’ll take on to accomplish next week and who will do what. That’s how we learn how to improve our performance as a group. Team performance is what I want to develop.”

Another manager I know has 1-on-1 meetings with each of her staff members. “It helps me focus them on their behavior”, she says, “and that will reduce conflicts. Also, it keeps their performance confidential, which I feel is important. Group meetings are only for information updates about organizational changes. Performance is more personal.”

Probably both methods have their benefits, but I’d rather be in one of Markus’ meetings. Looking at the work to be done with my colleagues seems more interesting (and energizing) than talking about my behavior or workplace conflicts and politics. But that’s probably because I’m an engineer, don’t you think? I’d rather see the bigger picture and improve the whole group’s performance. Either way, it looks like “developing people” means different things to different managers.

Servant Leadership vs. Management

I found this image online that itemized the “7 pillars of servant leadership”. OMG. I am such a total failure!

  1. Person of Character. I suppose I have a character, or maybe I even AM a character, but I don’t think either of those interpretations will meet servant-leader standards.
  2. Puts People First. Flunk this one too. My focus is on action, results, and outcomes – and engaging people in putting their attention on that. I don’t focus on people first, but even so, some of my best friends are people.
  3. Skilled Communicator. Well, I’m not a terrible communicator, but not sure if I qualify as “skilled”. I don’t always use the best practices I’ve been taught, and sometimes make communication mistakes. Fortunately, I’m pretty good at cleaning those up afterward.
  4. Compassionate Collaborator. Huh? Who put those two words together? I suspect it’s an attempt to combine collaborating with others while also “developing” them. I’d get about a C+.
  5. Has Foresight. I might pass this one, since I’m often looking ahead to see what’s coming in different projects. But I’ve really been enjoying lots of surprises lately, so foresight only goes so far.
  6. Systems Thinker. Nailed this one! I’m so addicted to systems thinking that I got a PhD in it. I love looking at things in context and finding connections that can make solutions and breakthroughs easier.
  7. Leads with Moral Authority. Clueless here. I don’t even know what this means. Does it require certain religious beliefs, or ethics training? Flunked this one too.

So, thanks to #6, I am one seventh of a servant leader. I just wrote a paper on leadership vs. management, and will present it at a conference in March. Frankly, the state of leadership literature and training today is quite a mess.

Leadership is useful for creating mission, vision, and purpose (MVP) – and for communicating it regularly. But I can do much of that for myself, so I’m hooked on management. One comprehensive definition of that is: “the function that coordinates the efforts of people to accomplish goals and objectives using available resources efficiently and effectively.” Yeah! That’s what produces action, results, and outcomes!

Seems like it might be a good idea for me to cultivate some moral authority, or some compassionate collaboration skills.  LOL.  Just kidding.

Why Do Some Managers Ignore Poor Performance?

This is a really good question, asked by Jill Christensen – an employee engagement expert, best-selling author, and keynote speaker – on a LinkedIn Group post. Here are the top 4 answers (in order of popularity) and some of the comments made about each:

  1. HR & senior management failure – HR is not doing its job to get poor performance on the corporate agenda and get the message to middle and senior managers. Managers fear that termination is the only solution (and finding a replacement may be difficult), so HR needs to give them ways of improving performance. Senior managers allow Managers to ignore poor performance. There isn’t enough “authentic leadership” to create a “culture” of leadership skills (eyeroll here).
  2. They don’t know how – Managers are not equipped to handle workplace conflict resolution. Managers lack lack the skills, courage, or confidence to address the issue of poor performance, and do not know how to address it properly and completely.  Managers do not have experience in how to mentor people to improve performance.
  3. Fear – Managers, like other people, dread having difficult conversations. They fear conflict, damaging relationships, and exposing themselves to the judgment of others above and below. Managers, like many others, avoid conflict.
  4. It takes work to manage performance and follow through as necessary.

After 30+ years as a management consultant, I say that answer #4 nails it for me!

All Managers know a few basics about the costs of poor performance:

  • Every individual’s performance contributes to organizational performance.
  • Ignoring low performance is a disservice to the employees who must compensate for poor performers.
  • Not handling poor performance undermines your own role as a Manager.

Managers also know it takes work to manage performance, and not just poor performance. To manage performance, a Manager must:

  1. Specify what “performance” is, in every case, with every person and team. Work with your group to define and update statements of measures and results. Specify what needs to be delivered to in-house and external users, customers, and collaborators. Get specific. Then: Make all “performance” clear to all.
  2. Make clear assignments. WHAT are the results and deliverables each person will be accountable for completing? WHEN are those results and deliverables due? WHO will be accountable for fulfilling each assignment?  WHY does each assignment matter to the group, and to the organization?  Then: Make all assignments clear to all.
  3. Follow up on a regular schedule: Update the status of performance assignments, in terms of percent completion, for example, and discuss barriers, problems, and ideas for improvements. Then: Make all performance status clear to all.

What does it mean to make all of these 3 things – [A] Performance measures, results, and deliverables; [B] Assignments for those completions; and [C] Performance status “clear to all”?  It means: Make it public (gasp!).  This is easiest if you use two indispensable elements of good management.

One, an indispensable management tool: Use a visible scoreboard or display for tracking assignment information (What-When-Who-Why).

Two, an indispensable management practice: Hold regular group “performance-update” meetings with the whole team. Those meetings are where you clarify [A] What performance is, [B] What assignment specifics will get us there, and [C] What our follow-up meeting agenda and schedule will be. Note: One-on-one discussions are insufficient for managing performance.

So, why do some Managers ignore poor performance? Because doing A-B-C, plus maintaining visual displays and facilitating performance-update meetings, is work and it takes time. And we all know that Managers are Really Busy.