Oh, no, not another quadrant chart!

Sorryyyy. But quadrant charts do have their uses. In today we’ll use one to help clarify whether, in our rapidly emerging post-COVID-19 world, employees who were shifted to remote work as a result of the pandemic should shift back to working on premises.

Start with a typical scenario: Executive leadership wants employees back at their desks. Many of its employees, though, having grown accustomed to the flexibility working remotely provides, are unhappy with this direction and are pushing back.

Which brings us to Lewis’s Law #Beats me, I stopped counting a long time ago. The law states that if a decision hinges on personal preferences, everyone involved is engaged in the wrong conversation.

Possibly because I’m a founding member of Sarcastics Anonymous, whenever I hear someone start with the words “I want …” I have to restrain myself from answering, “Well, I want a pony. And a Robot Commando™, and a … ”

That the executives want employees back at their desks, just doesn’t, or at least shouldn’t matter, any more than it matters that employees will happily comply, so long as the desks they’re back at are comfortably located in their home office.

What does matter is the nature of the work each employee is responsible for. Which brings us to this week’s dreaded Quadrant o’ Doom.

In this quadrant, the vertical axis denotes the extent to which process management and oversight are important factors in what it takes for those in a given role to do their work. The horizontal axis represents the importance of relationships, trust, and team dynamics.

The chart suggests that:

  • When neither process oversight nor relationships are important for an employee to get work done, it’s a role for which working remotely is a particularly good fit.
  • When relationships aren’t particularly important but process oversight (and by implication, direct supervision) is important, working remotely still can make sense, but only to the extent that automated process monitoring is available so the responsible managers can make sure work is being done correctly and at speed.
  • In situations where relationships are important but process management isn’t, employees need to be physically present for at least part of most work weeks. Not all, but enough to interact face to face. That provides a foundation for building the trust and alignment that are the heart of healthy team dynamics. This quadrant is labeled hoteled because in this situation, employees aren’t assigned to permanent cubicle locations. They park in an available cubicle when they’re on premise; someone else parks in that cubicle on a different day.
  • And finally, when both process management and interpersonal relationships are essential to success, the employees who do this work are needed on premises.

Bob’s last word: Without a doubt, this Quadrant o’ Doom is oversimplified. It’s also entirely possible that its basic dimensions of analysis – process management and relationships – aren’t even the most important determinants.

But the underlying premise – that determining whether a given employee should be allowed to work remotely or required to work on premises must depend on the nature of the work, not the personal preferences of anyone involved in the decision – is fundamental.

As a fringe benefit, starting the decision process by building out a framework, whether it’s the one described here or something completely different, can de-escalate what can otherwise become dysfunctional conflicts between management and staff that can cripple the organization’s ability to function.

Bob’s sales pitch: Not really a sales pitch, but if you have a different framework for making decisions regarding remote vs on-premises employees and are willing to share it, please post it in the Comments so the KJR community can take it into account in their own workforce planning.

Dear Dr. Yeahbut …

We have too many meetings.

I’m sure I’m not the first person to gripe about this, but if I’m not, why does it keep on happening? More important, what can I do about it? I need to do actual work, but easily half of every week goes into meetings. Help!

– Burnt

Dear Burnt …

Not all meetings are created equal, so there’s no one answer. In even numbers there are four types of meeting: Status, decision-making, information-sharing, and team working sessions. One at a time:

Status Meetings

These are weekly meetings of project team members and only project team members. Each team member reports on whether the tasks they were supposed to start started, the tasks they were supposed to finish actually finished, and, if not, what their plan is to get back on track.

Project status meetings are essential project-management tools. No, they aren’t an efficient way to collect task status information for the PM’s project status reports. They’re essential because they’re the most effective way to apply peer pressure to sub-par-performing team members.

If you’re on the invitation list for more than two weekly status meetings the problem isn’t that you have too many meetings. It’s that you’re assigned to too many projects. That’s an even harder problem to solve, but it’s a different problem.

Get out of meetings free card: You don’t get one. Project status meetings aren’t optional, even for team members who started and finished their tasks on time. These team members are, after all, the ones that exert the most and most effective peer pressure.

Decision-making meetings

There are, you might recall, five ways to make a decision: Authoritarian (I make it); Consultative (I collect informed opinions before making it); Consensus (we don’t all agree with the decision but do all agree to it); Democratic (we vote, the majority wins, and the minority pretends to accept it); and Delegated (someone else gets to make it).

Of these, the only decision style that calls for a meeting is consensus – the most expensive way to make decisions, delivering the second-lowest-quality results (voting is even worse). For most decisions, consultation strikes the best balance between quality and efficiency. Leaders should make it their go-to, reserving consensus for situations where stakeholder buy-in matters more than anything else.

Get out of meetings free card: If it’s your meeting, don’t have it. Consult or delegate the decision instead.

If you’re one of the invitees, politely decline the invitation and suggest a 15-minute one-on-one consultative call instead.

Information-sharing meetings

When managers were less buffeted by information, the conveners of information-sharing meetings asked, “Who needs to know about this?”

As most managers are buried in information, this quaint notion from days gone by has, or at least should have been supplanted by a different question: “Who can’t function effectively without this information?”

One more point about information-sharing meetings: Attendees are prone to try to turn them into decision-making meetings, on the grounds that “Why are you telling me this if you don’t want my opinion about it?”

Get out of meetings free card: If you’re the convener, ask yourself what it is about this information that requires a meeting and not just an internal blog post with a comments section for any back-and-forth that’s called for.

If you’re on the invitation list, ask if you won’t end up just as well informed by reading the meeting notes.

Team working sessions

Well, if the team really is getting work done then this counts as time you’re spending getting work done.

Get out of meetings free card: Even when teams met in 3D in a whiteboard-equipped room, working sessions should have been limited to seven participants. Limit web-conferenced meetings to five. If you’re the convener, adhere to these limits. If you’re invited and don’t need to add your voice to the proceedings, brief another participant … one you trust … with your perspective, and let the convener know you’ll accept the results.

Bob’s last word: Layered on top of this brief meeting taxonomy is a meta-purpose, which is that meetings are where team members get to know each other, building trust and shared purpose as they do.

Getting work done is transactional. It’s what can be tracked, and what pays the bills.

But relationships do matter. Leaders who ignore them find the teams they lead gradually enter a long, slow slide into dysfunction.

So along with discontinuing meetings that shouldn’t ever be scheduled, wise leaders find ways to replace their relationship-management meta-purpose.