Posts

Management for Accomplishment, 1-2-3: Here is Step Two

Two weeks ago (https://usingthefourconversations.com/blog, Sept. 15, 2020) I mentioned three examples of projects I consulted on where managers wanted to implement a change in their organization. For the most part, they did not know how to set the project up in a way that everybody could win and accomplish the goal. One of those projects will serve as an example for Step Two in Managing for Accomplishment.

A city government’s Department of Electricity had five Units related to their project: Electricity Distribution, the Meter Shop, Engineering, Customer Service, and Purchasing & Stores. These groups worked well together – except for the Engineering and the Distribution Units, who rarely interacted except to argue about equipment and supply requirements.

The diagram below has 6 circles, representing the 5 Units in the project + the electricity Customer. It also has 11 arrows, representing the primary “communication relationship” between the groups, i.e., the most important products, services and/or communications that moved between each pair of circles and what they talked about most.

Notice in the diagram that installation equipment and supplies were determined by the relationship between the Engineering Unit and Purchasing & Stores. The Distribution Unit, which was made up of teams that handled construction, installation and repairs of electrical wires and stations, were the primary users of that equipment, yet were left out of the decisions on what equipment was outdated or needed to be changed for new kinds of projects.

One member of the Distribution team told me, “We aren’t able to satisfy our Department’s mission to ‘provide energy, street lighting and related services reliably with competitive pricing’. We can’t always pay for the city’s need for streetlights.” He was discouraged that they had no voice in improving construction and installation for electricity distribution.

The administrator of the Electricity Department wanted the Engineering and Distribution Units to find a way that they could both have a say in the selection and purchase of electricity installation equipment and supplies, to ensure that Distribution teams would have the equipment they needed to solve the engineering and maintenance problems in the field. He told them to work together and come up with a solution, but the Engineers had little respect for the Installers – and vice versa – so they made no progress.

This administrator did not know that “management for accomplishment” begins with creating a “team”, i.e., getting people aligned on the basics of working well together. Management for Alignment is Step One, and once Team members are clear on the intention of the project, have identified a responsibility structure for the Team, and agree to recognize the relevant rules and regulations for working together, they are ready for Step Two: “Management for Production”.

Getting people ready lay the foundation for productivity requires Team collaboration to define three Step Two elements: (a) the metrics of success; (b) the Team’s performance network of agreements for goal-relevant communications etc. (that’s where their diagram came into existence, even though this version does not spell out all the deliverables); and (c) the production and delivery systems, and standards and practices, to coordinate work and agreements within the Team and with others, including for processes, quality, schedules and costs.

The idea of a “performance network” of deliverables and receivables is sometimes hard to grasp for people who haven’t thought of projects in terms of “deliverables”. We tend to think of “doing” a project and we look forward to when it’s “done”. But we don’t often think of what needs to be “delivered” between Team members and others in order to get the project completed successfully. There’s a big difference in what happens when you focus your attention on Doing vs. Done vs. Delivered.  Tip: Go with “delivered” – get the results (products, services and/or communications) produced into the hands of the people who will put them to work. And get the resources you need delivered to you.

Ultimately, this city Electricity project involved discussions with Purchasing & Stores and the Meter Shop, which produced changes in the way installation equipment and supplies were ordered. Meter equipment was then ordered using the same computer system that Distribution and Engineering would use, which included updated reporting formats that would go to Customer Service from all of the groups.

Production is not a matter of “doing”, nor of getting something “done”. Production requires looking at what needs to be produced and by whom, and to whom it is delivered. All 11 arrows in this performance network diagram were altered – with many added specifics and new agreements – as the Engineering and Distribution Units invented out a way to make more effective purchasing decisions. Note: The Engineering Unit also collaborated with the IT Unit for this project.

As with Step One, the elements of Step Two require the ability to ask 6 questions and to work together to develop the answers. And again, none of these elements involve managing the people (we manage agreements here).

Step Two: Management for Production

WHAT-WHEN-WHY – Spell out the metrics for each key goal: What are the success metrics for budget and cost goals; What are the key performance indicators for production processes, product quality, and service quality. When are the key due dates and milestones. Why these metrics and timelines are important for fulfilling the overall purpose of the work.

WHO-WHERE – Identify the project’s performance network and establish agreements for sending and receiving goal-relevant products, services and communications: Who & Where are the non-Team players who are important for the Team to send and receive goal-relevant products, services and communications (e.g., funding, HR, maintenance, operations, product and service delivery, legal obligations, etc.). Assign responsibilities to the Team members to “own” one or more of these relationships and establish and honor agreements with external non-Team players for goal-relevant delivery content, quality, timing and costs between the Team and external players.

HOW – Spell out production and delivery systems, standards and practices for the project: How all aspects of the work and its deliverable products, services and communications will be produced, coordinated and delivered among Team members, and with players in the performance network, to satisfy goal-relevant requirements, e.g., content quality, schedules and costs, for key functions including: Budget, Operations, Product and Service quality and delivery, IT, Marketing, and Public communication.

Sounds like a lot, doesn’t it? But managing for production requires structures to accommodate the velocity of production and the partnerships in the Team’s external environment. Especially: (a) The metrics that will let everyone see progress and success (or failure) in meeting targets; (b) The relationships with other individuals and groups outside the Team who have resources and ideas that can support success and integrate the project’s results into the larger work environment; and (c) The Team’s organization and coordination of its work and its products, services and communications within its performance network and with other key functions.

A team of people aligned on working productively with goal-relevant partners, using its own custom-designed goal-relevant structures of (a) success metrics, (b) a functional performance network and (c) agreements for coordination and communication, will be ready to manage itself – for accomplishment. I’ll tell you that story in 2 weeks!

Management for Accomplishment, 1-2-3: Here is Step One 

We talk about it a lot, but mostly we see management as a concept rather than a set of steps or tools. One way out of that conceptual view is to say what we are managing FOR: What do we intend to accomplish? Here are a few ideas of results I’ve seen managers choose to accomplish:

  1. Bring together two groups that have interrelated activities to draft a plan that will improve the interactions, efficiency and/or productivity of one or more of the processes they both participate in. Example: People from the Engineering section and people from the Maintenance team get together to redesign the way they select, purchase and use the equipment needed to solve engineering and maintenance problems in the field.
  2. Have a group of people design and perform a specific change in their organization, such as implementing a new IT process and operating it properly for both users and customers. Example: A restaurant decides to implement a new Point of Sale (POS) system to improve staff productivity and customer satisfaction.
  3. Finish a long-term project that is persistently postponed due to staff shortages, poor scheduling and/or deadline changes on other projects (or maybe just simple procrastination). Example: A cleanup project in a corporate library to clear out old books and files, many of which would be re-categorized for other purposes, given to other programs, or recycled.

Management for Accomplishment is a three-step process. To prepare for managing any of these projects, Step One is alignment, which itself has three elements: develop team alignment for focus on the task at hand; plan the set-up for the production and performance of the task; and plan for accomplishment of the task, taking into account the environment it will be operating in. There are three interesting points about these elements:

  • All three are effective for preparing to manage a short-term or one-time project as well as a larger one,
  • None of them involve managing the people (we manage agreements here, and
  • They all require the ability to ask 6 questions, then work together to develop the answers. The questions are: What? When? Why? Who? Where? and How?

Step One: Management for Alignment

WHAT-WHEN-WHY – Spell out the Intention for the task: What we want to make happen, and what will tell us when it is complete. When we will want it done, including goals for interim timelines. Why it matters for those performing the task and for others including customers, co-workers, or executives.

WHO-WHERE – Identify the “authority” structure for the task: Who will lead the team to ensure the intention is fulfilled, who will fill the necessary roles for task accomplishment, whether inside the team or outside it, e.g., people the team will report to, work with or get materials, information and/or support from, and who the beneficiaries of the end results will be. Where these people are operating from – their “base” – and where else people will need to go to fulfill their responsibilities.

HOW – Clarify the relevant rules and regulations for working together: How all aspects of the work to be done will comply with corporate rules and guidance as well as the needs and requirements of others within the organization and externally, and how all relevant federal, state and local laws and policies might pertain to the work at hand.

Seems pretty basic, doesn’t it? But these three sets of questions are often overlooked, especially for defining (a) the foundation of a team so that everyone is aligned on what the team is out to accomplish; (b) the relationships among team members and with external associates, senders and receivers; and (c) how the team will operate with respect to its surrounding infrastructure.

Creating team alignment is Step One in ‘Management for Accomplishment’ and is especially important for a group that has not worked together on a task or project like this before. The way such a project is launched begins with these 6 questions and their discussions to build direction, clarify responsibilities and respect the new environment they will be operating in for the duration of the task.

I’ll be back with Step Two in 2 weeks.

What to Manage: Workers? Or the Links Between Them?

I’ve been reading an article (HBR, Competent Management) which mentioned “obstacles that often prevent executives from devoting sufficient resources to improving management skills and practices”. The research they reported made it clear that better management skills lead to higher competitiveness and better performance all around. So, understanding obstacles to good management is a good idea.

What are the “obstacles”? First, overconfidence: managers think they’re already doing a good job. Another obstacle is that many managers can’t make an objective judgment about how well things are really going. The article included several other obstacles, but the whole list made me recall the most frequent problem I encountered in my career as a management consultant: managing the people and their activities. That’s not what needs to be managed.

I learned about that obstacle very early in my career, from the CEO of a non-profit firm. I saw a need for better management practices – aligning people on goals, measures, tracking and reporting. Two of his groups were making mistakes in the products and communications they were sending out to the firm’s members, prospects and customers and the reason was they were not collaborating with one another at all. When I suggested to the CEO that it would be useful if his Marketing team and his Communications Office got together at least once a month to clarify what each of them needed or wanted from the other, he banged his fist on his desk and shouted at me, “They should already know their jobs!”

Omigosh – he was watching what his people DO instead of what they DELIVER to others! Wow.

I was startled that he shouted at me, of course. But it was difficult to believe he did not have a process for ensuring that different units in his organization had an opportunity to talk with each other to stay updated on the products, services and communications they produced, sent out, and/or exchanged with one another. That would have given the Marketing team an opportunity to find out what the Communications Office was sending out to the firm’s prospective members, which would have helped Marketing do a better job of recruiting new members.

The CEO couldn’t see that the Marketing team needed information from the Communications Office and vice versa. Instead of supporting effective and goal-oriented communications between groups, he was watching what goes on inside those groups, as if they were stand-alone entities. As I went through my whole career, that was something I came to see as a frequent cause of misunderstandings in organizations. It was also a source of blaming “those people” for not knowing what they’re doing.

The mistake was the focus on what people were “Doing”, which isn’t what I was watching for at all. I focused on what moved from one group to another or went out to a customer: the products, services and communications that go out of Group 1 and into Group 9, then on to a user/customer. This allowed me to start at the end of the line, getting ideas from the Receiver of a delivery about how they evaluate or measure the quality and effectiveness of what they received. Then I could work with the Sender to obtain and use that feedback from the Receiver on a regular basis. I admit, it was sometimes touchy, especially if the Receiver was unhappy with what they got from the Sender. But I was the “ambassador”, carrying feedback to the Sender and assisting them in finding ways to put it to work. Ultimately, though, the two groups would establish a productive relationship and better products, services and communications were then available to all.

I was surprised to find that almost no manager watches the links between Senders and Receivers. They’re watching the “job”, the “work”, the people and their activities – but that’s not where the leverage is. Just sending something from one place to another doesn’t mean you’re getting the job done. You need to get the Receiver’s feedback on how well it worked. Was it the right quantity or size? Was the quality what they wanted or needed? Did it arrive on time? Does it perform properly, producing the effects the Receiver desired?

Getting feedback requires establishing a reliable communication link between Sender and Receiver, an easy management practice to implement. And, according to the article, good management practices will pay off in a big way, delivering better overall organization performance. That non-profit CEO actually learned how to improve the whole network of teams in his firm.

Even though that article I read didn’t focus on the links between groups, it had a lot of smart things to say about competent management. One valuable point was that companies think strategy is more important than management. I haven’t seen this discussed for over a decade, and the research reported in this article clarified that management competence is more important than strategy. It’s a good read, even if it is over 3 years old. Check it out: (HBR, Competent Management).

A Close-Up Look at Micro-Management

When I was a management consultant, clients sometimes complained about “micro-management” in their organizations. I had to look it up, because I thought it just meant someone was paying too much attention to details. I learned that it’s much worse than that, but now I have been educated in real life, because I have now been micro-managed.

I am working, post-retirement, as a volunteer in a small organization. I support three Committees, each of which has a Chairman, so I take my job to be assisting those Chairmen in setting and attaining goals as well as supporting the Committee members in working as a team and being productive and effective. All was going smoothly until one Chairman resigned and was replaced by Captain Micro.

The Captain watched every action I took, heard every idea I offered and saw every communication I delivered to Members. He then criticized each of those things, saying this email to members was “too complicated”, and that idea was “inappropriate”. His instructions to me were specific but piecemeal, and I wasn’t always able to assemble them into a meaningful whole. I confess to having lost my sense of humor at one point, telling him that his latest instruction was “another piece of our communication problem”, which was the first time I had let him know how I saw the situation.

Another annoyance was that he wanted me to check with him about every little thing before I took any action, as if I couldn’t see for myself what would work. He gave me miniature assignments – send out this email to the members, forward him a copy of Aaron’s article from last week, etc. And he often messed up my schedule by giving me several different due-dates and times for each request. Multiple emails and phone calls showered down in the first week of working with him, which became annoying. I suspect he could hear the impatience in my voice by that Friday afternoon.

Week Two didn’t gain any momentum. Fewer calls and emails, but he was still stalling on taking any substantive action for the Committee and was not allowing me to make any decisions (or he corrected the ones I had already made). What had been an unfolding project for the Committee was now a mute folder lying on my desk waiting for attention, and I couldn’t get him to move ahead. He didn’t seem to know or care what I had done for the prior Chairman nor to have any sense of urgency about moving the members’ teamwork forward to meet the goal everyone had aligned on before his arrival.

It’s over now. Captain Micro won’t work with me – he’s going to do it all himself. Perhaps I’m too headstrong, pushing to finish the Committee’s current project so we could move on to future aspirations. It appears he has decided to take over the facilitation tasks I had been doing – sending out what he chooses to the members, and perhaps also taking notes on their monthly calls and creating an agenda for the next call (though he may not think such tasks are necessary).

Now I’m supporting only two Committees. I initially feared that Captain Micro’s lack of support would undermine the group’s sense of purpose and cohesion, but several members have now been in touch with me, looking for more productive pathways to get what they wanted to accomplish. Captain Micro will go his own way with his new Committee – and I wish them all the best. I’ll continue my accountability for supporting the two remaining Committees as best I can, and be grateful for the trust and respect of their leaders.

 

Manager Tip: Clarify What You Really Want in Every Work Request

One job of a manager is to ask, invite, or demand that other people “do their work”. But people understand the word “work” in three different ways. You may be asking that I “do” something, like you want me to put the appropriate data into a spreadsheet for analysis. That’s not the same as getting something “done”, which is when you tell me to get that spreadsheet finished. And it also doesn’t mean “delivered”, which would be you asking me to send the finished product over to you by close of business today.

When you want something from me, it is important to clarify: Do you want me to work on something? Or produce something? Or bring it to you or someone else? Do – Done – Delivered: do you want to keep me busy, or finish something, or turn my final result over to somebody? Or maybe all three?

Good work typically generates a specific product, service, or communication that calls for all three: to be produced, completed, and delivered to someone who will use it and/or value it. The best way to produce results – to perform well – is to focus on those “deliverables”.

A focus on deliverables, sometimes called “Do-Dues”, requires giving attention to the desired outcome(s) – the products, services, and communications to be provided to another individual or group. Deliverable results always have:

  1. Specific characteristics such as production processes, amounts, formats, and other attributes or qualities,
  2. A producer/sender and a user/receiver,
  3. A due date and time it will be sent or received, and
  4. Some value or benefit that will serve others.

Both the work-requester and the Doer-Deliverer should clarify – and agree on – these four aspects of what a “good result” will look like.

If you want to improve someone’s “performance”, don’t focus on what they should do. Start by being clear on the specifications, requirements, and conditions for what will be sent and received, to and from others. This seemingly small shift in attention – from what people are doing to the outcome of what they do – is actually very useful. If you add the information of who will receive it and why it matters to them, you have added value to people’s “doing-work” and to the result it produces. Magically, their “work performance” will improve too.

 

We All Need Deadlines

“I don’t need time. What I need is a deadline.” -Duke Ellington, jazz pianist, composer, and conductor 

Although we resist, protest, and sometimes miss deadlines, they provide a structure time alone does not. “Deadlines are one of the most powerful tools for accomplishment you can use,” writes Jeffrey Ford. Deadlines let us know what is needed by when and, when added to a request, create an agreement that can be managed. Without a deadline, projects or tasks exist in limbo, their importance undetermined and their necessity questioned. 

No matter whether the task is for personal satisfaction or a critical business action, a deadline arranges time so you can measure success. So, the next time you are given a new assignment, take the first step to achieving success by asking, “by when do you need it?” If you don’t, getting it done on time suggests “It Don’t Mean a Thing”. 

Photo by Kevin Ku on Unsplash

How Reliable are “Expectations” for Getting Good Performance?

Answer: Not very. Why? Because expectations live in your head. If they are not put into a conversation with the person you “expect” will take action, those expectations have no way to get out of your head and into theirs. At least put them on a post-it and hand it to that person. That will increase the likelihood the person will take some action, all the way from 7% up to 24%.

OK, I made those statistics up. But in the past two days, I have heard three different people refer to “expectations” as if such a thing existed and are as real as a sign in the hallway or a billboard along the road – visible, in big bold print, where everyone can’t help but see them, and they know what to do. Here is one of those conversations:

Karyn, the head of an IT project management team, saw her boss in the hallway. He stopped her and said, I want you to gather the data on project performance over the last six months and prepare a report on what you find by the end of this month.” Karyn told him she would do that, and they went their separate ways.

Later that month, Karyn told me her boss was really cross with her because she had not delivered the report. “It wasn’t the end of the month”, she told me. “I thought he wanted me to prepare the report, but I didn’t know he wanted me to deliver it to him! Plus, I really had no idea that for him, the end of the month is really the middle of the month. He must think I am a mind reader.”

Karyn’s boss had “expectations”, thinking that she would know – of course – that “prepare a report” means “prepare a report and bring it to me”, and that she knew he meant the end of the company’s financial month, which was on the 15th of every month. Karyn was bothered by this, and by not seeing any way to tell her boss that he was making assumptions that weren’t valid.

I’m reminded of a former client’s response when I told him that the Marketing Department team was not giving the Customer Service office the information that they needed to keep customers informed about new options for different service packages. I thought he would help me be sure the communications between the two groups was workable for both of them. Instead, he banged his fist on his desktop and shouted, “They should know their jobs!” He apparently didn’t realize that jobs change faster these days due to technology and communication improvements, and that what it says on most people’s “job descriptions” (if they even have them) is usually way out of date.

So, if you have expectations for someone, whether a co-worker or a family member, it will be helpful to explain those expectations to the people you expect to perform in a particular way. If you explain what you want, when you want it and maybe even tell them why you want it that way… AND if they agree to that, then you have an agreement between you. If they don’t volunteer an agreement, ask them if they will agree to do what you ask.

You at least need a clear statement of what you want, and when – plus a “yes”, before you are entitled to have an “expectation”. What’s inside our head is less obvious to others than we think.

 

Step #3 – Using Conversations to Solve Workplace Problems

After Rodd filled out his own free Personal Workplace Communication Assessment, he received a Results & Recommendations (R&R) Report with suggestions for improving the biggest problem he saw: a lack of accountability. Those suggestions, summarized in Step #2, “Using Conversations to Improve Accountability”, moved him to invite all of his staff to take the survey and get their own Regional R&R Report based on responses from their own people. Maybe then they would all see the problem and work together to get it fixed!

Rodd decided to subscribe to the Consultant’s Workplace Assessment – because he wanted to have different Reports for each of his five Regional Offices, and might want to have follow-up surveys over time. He had talked about this survey idea at his last All-Staff meeting, and people sounded interested and willing to do it, so he was confident there would be a good response. He sent out the invitations to take the survey with a distinct link for each Regional Office’s personnel.

Out of 75 staff members, 70 completed the survey. To Rodd’s surprise, the five R&R Reports showed that the five Regional Offices really did see different worlds. And they didn’t all see “lack of accountability” as the biggest problem. But then, after studying the five Reports, he was intrigued to see the different patterns of responses, and figured that working on those differences as a group would help the Regions get better acquainted and begin standardizing StateOrg procedures and communications. (He was right about that!)

Rodd also made up a list of the “Non-Problems” – the items that got the lowest number of votes overall. “That’s the good news”, he told me. “I want them to see our real strengths before we talk about the problems and solutions. His plan was threefold: (1) Send the “Good News” email listing the strengths, or “Non-Problems”, of State Org to all 75 people on Thursday; (2) Send all five R&R Reports to everyone the following Monday; and (3) Schedule a one-day visit with each Regional Office the following week, to discuss their unique “Biggest Problems” and their ideas for improvement.

It was a smart thing to do – people responded well to hearing that this wasn’t all about problems and complaints. And, since each person had received their own individual survey feedback report and recommendations, they were already talking about the idea of using conversations to solve workplace problems. You can see Rodd’s Step #3 (out of 6 steps) here: Step #3 – Group Workplace Invitations & Results.

Step #2 – Choosing an Assessment to Identify Biggest Workplace Problems

We’ve received a wave of inquiries about practicing productive communication techniques to resolve workplace problems. Since last week’s post of Step #1 in a 6-step process used by Rodd, a former client (see Step#1 blogpost), it seems people recognize the need to repair a “fractured organization”. The idea of using 4 distinct kinds of conversation to get a group on track might be catching on – perhaps my retirement years will be well spent letting people know about this!

Rodd’s first introduction to using productive communication was the free Personal Communication Assessment – only 20 questions – to see how his own skills stacked up in this area. He got prompt feedback on his answers, showing him his strengths and his weaknesses. Then, he kept exploring by taking the free Workplace Communication Assessment – this time, 56 questions. Again, he got immediate feedback on 8 types of workplace problems in StateOrg (our name for his organization).  The report validated what Rodd saw as the biggest problem: a lack of accountability.  Even better, it gave him a recipe for how to use all four productive conversations to solve that problem.

First, though, Rodd thought about having all his staff take one of the Group Assessments so he could get an even stronger validation on that “biggest workplace problem”.  He only had to decide which Group Assessment he should get:

Rodd thought if everyone recognized that there was a “lack of accountability”, they would surely work together to solve it.  He also felt that getting feedback from everyone in all five regions would be a good way for them to experience themselves as part of one organization instead of five separate outposts. He was right about that part.

You can see the links to all six chapters of “The Case Study” on the Group Assessments page of the site. The story of Rodd’s second step is here, including the ideas he had for how to put the Consultant’s Workplace Assessment to good use in having his five-regions work together in a more coordinated way. (For a little more on the mess he was dealing with, see Step#1 blogpost.)

Supervisors See Four Kinds of Personnel

Best Employee. Supervisor gives work orders and turns job over to worker. Worker requires only recognition.

  1. Accurate and complete work; Good results.
  2. Accomplishes more jobs; Productive and efficient.
  3. Organized; Knows where things are.
  4. Can do all assignments; No hand-holding needed.
  5. Looks ahead; Thinks how to help; Has good ideas.
  6. Good attitude; Courteous to all.
  7. Volunteers to help team members; Gets involved.

Good Worker. Supervisor recognizes good performance and points out problems. Worker requires support for teamwork.

  1. Willing to learn; Wants to do better and improve skills; Interested in the job.
  2. Takes on any job and does what is asked.
  3. Hard working; Skilled; Paying attention.
  4. On time with results and finishing jobs.
  5. Careful worker; Does complete work.
  6. Keeps work environment in good order, equipment and supplies organized.
  7. Often helps others on the team.

Improving Worker – Supervisor is clear on details and gives encouragement. Worker requires instruction and appreciation.

  1. Doesn’t know all aspects of the job; needs guidance.
  2. Afraid to make decisions without asking what to do.
  3. Results sometimes good, sometimes not.
  4. Willing to learn with supervisor encouragement.
  5. Sometimes doesn’t see to do more than necessary.
  6. Capable, could do more with better results.
  7. Requires attention dealing with sensitivities.

High Maintenance Employee – Supervisor points out everything to do. Worker requires attention.

  1. Late to work or has to be told to do jobs.
  2. Works slowly; Inefficient. Makes small jobs big.
  3. Moody or argumentative; Complains to co-workers.
  4. Messy work area; doesn’t take care of equipment.
  5. Watches others at work; Sometimes distracts them.
  6. Takes easy jobs or waits to be told what to do.
  7. Often turns in work results that require more work or cleanup from others.