An old friend, Marcia, owns a cookie business that in 20 years has grown from a tiny kiosk to a fine store employing 12 workers and a manager. She recently visited me to discuss a personnel accountability problem. Not uncommonly, however, she didn't see it as an "accountability" problem, but rather as a "people" problem.
"The business is stagnating, and so am I," she complained. "Production is down, deliveries are late, quality is worsening...and so is my throat from yelling at my manager. I don't want to have to look over everyone's shoulders all the time. I just want to play bridge with my friends."
"But Marcia," I said, "if after 20 years you still have to be there every day to oversee everything, apparently your people don't really understand what they're supposed to be doing."
"Listen, we're just making cookies, not splitting the atom," she sighed. "I hire good people, tell them what to do, and they do it. Except that sometimes - too often, in fact - they don't."
Marcia's dilemma was the classic lament of a business owner unwittingly managing by assumption: She assumes each employee knows what to do, while they assume someone else is responsible, and, ultimately, all accountability falls with a splat at the feet of the owner.
"The cornerstone of a working relationship that works is called Management by Agreement and Exception," I told Marcia. "Whether we're talking about accountability for an entire position or a single, specific project, you and your employee need to mutually understand, and formally agree on, the terms regarding the work to be done."
This, obviously, is the Agreement part of the equation. For example, the employee will sign a written document accepting full accountability for performing the required work and achieving results, while the manager agrees to provide the employee with resources and guidance, as requested.
With this formal agreement in place, the manager can then assume that all work will be done as agreed unless otherwise notified. The goal, besides obtaining the stated results, is to avoid unpleasant surprises.
"OK, I understand all of that," Marcia responded, "but stuff happens. There are breakdowns and blackouts, foul-ups and freak-outs. And the bane of my existence is to be caught unaware."
"So, your employees need to agree to an important condition," I counter. "The moment they know they won't be able to complete a task on time, whatever the reason, they'll notify the manager. This is the Exception side of the equation." For example, some businesses use Exception Report Forms that state the original commitment, the reason the commitment won't be met, and a proposed alternate solution.
"I like that idea," Marcia nodded. "I would much prefer knowing in advance that something isn't going to happen. I may not like it, but at least I can make adjustments before it becomes a crisis. I'll also get to decide whether the reason for missing the deadline and the proposed alternative are acceptable or not. Either way, I'll have kept communication channels open, preserved the chain of command, and maintained my ability to manage strategically."
"Remember, Marcia," I said, "if employees don't understand and agree on their accountabilities, you can't count on their results, and you therefore won't be free to do your own thing. The beauty of Management by Agreement and Exception is that employees will proactively deliver as promised, your manager will provide constructive support, and relationships built on trust will be strengthened. And with these personnel accountability issues resolved, you'll be free to spend your time concentrating on winning bridge tournaments."
Submitted Jun 26, 2007 4:38 PM
Submitted Jul 31, 2007 12:13 PM
Clearly defined roles are definitely needed in every business, a job letter which outlines the responibilities before that person starts, signed in the presense of a witness leaves nothing to be challenged as to what is expected performance wise. What I find really interesting here is the "exception" report, it forces staff to be accountable for an arising issue which they may have just swep under the rug to be discovered at the detriment of the company, by reporting it. Now the issue can be addressed before the business can be discredited too badly or in any way at all.
I found this very helpful, management by exception is a powerful tool.
Submitted Feb 3, 2008 6:59 AM
I had already understood the part about making sure everyone is clear about what's expected of them (although like most I'm not sure I've been too good at making sure that happens in the past!) but what I didn't get before was the Exception part. That's definitely a powerful concept and something I will want to be using in the future.
What's people's thoughts on how to deal with staff that still don't perform as requested such as consistntly not perform an agreed task or not report expeptions. Would this be considered a good enough reason for dissmissal?
Submitted Apr 1, 2008 2:55 AM
Clearly, Job Descriptions offers great help. The point is well explained by Simon. I too was not aware of the "exception" report. I will use it here after in all the Job Descriptions.
The RACI (Responsible, Accountable, Consulted, Informed) matrix can work in this scenario. May be, we can modify the matrix to include an "E" (Exception) in it.
Also, a sample on the Agreement shall be of great help.
Submitted Jun 19, 2008 9:30 PM
Mark,
I would look at the person's past history, were they reliable and then have become unreliable? Is it something that can be fixed? Or are they not suited for the job (personality, and/or skills)? I have found that sometimes people really are not a good fit for the job, and I have to be the one to point it out. Also, does the employee understand that they are not measuring up?
Also, I would look at your hiring/promotion systems, trying to find out how the person came into your organization, or got the job. I got caught in the hiring for great expertise, only to get a person who does not work well with others, had alienated so many people, they could not get their work done (required influencing people).
One caveat, if some is not working out, skills and personality, the longer the person is there, the worse it is for the business.
I find the RACI matrix to heavy weight, and a way to increase paperwork, unless the project is that complex. I find I want just a couple of major objectives/tasks, in either done, not done (according to plan), ongoing (according to schedule), not going according to schedule (here is the exception part), and not done (not according to plan). Anything else is either details( I can drill into further), or just a maze of excuses.
Submitted Jul 6, 2008 11:27 AM
Marcia knows her business, the question is do her team know what she knows, the best way forward is to manage by clearly defined objectives. MBO's, if there are Clearly defined MBO's for each person on the team, they then are held accountable and responsible, which in turn encourages them to think outside the box and be creative in coming up with a solution if stuck. At the onset of any employment it is necessary for MBO's to be defined and agreed giving detailing to the team members, what impact the MBO has in each area of their responsibility to the business, this is what I call taking ownership, People must think that they own the business and lead from anywhere in the organisation. That is what frees up the owner to strategise, expand and create an organisation that is outstanding.Regards,
Jennifer Randive focus direct Management Consultants. Dubai, United Arab Emirates
Submitted Jul 8, 2009 11:46 PM
Subscribe to the E-Myth ViewPoint Newsletter