There’s a war on reality.

The opening shots in this war weren’t fired by professional politicians, although professional politicians have certainly fired their share of its bullets.

But my professional experience suggests the war started decades ago, by the un-named villain whose efforts turned the word “Photoshop” from noun to verb. It was when an image could be Photoshopped that we could no longer believe what we saw.

The war escalated as the World Wide Web became popular and “virtual reality” became a thing, because virtual reality’s malleability compared to real reality led to visitor experiences convincing enough that we believed the virtual realities we experienced were … well, real.

No, this isn’t a “Golly gee whiz, look at how much better the world used to be back in the good-old-days” column. Well, maybe a little, but its lede, buried as it might be, is about your role as a business leader.

That’s because of the role all leaders have in shaping the cultures of the organizations they lead and influence. Culture is relevant to the war on reality because the war is being won or lost … increasingly, lost … not by technological innovation, although technical innovations certainly provide useful milestones for tracking the war’s progress.

But it’s the social culture, which cares decreasingly about the truthfulness of the content being bandied about, that’s where the war on reality’s battleground is being fought.

The next milestone in the war on reality is the perfection of deepfake technologies. But we could withstand the advent of deep-fake-driven counterfeit realities were it not for the collapse of something we used to take for granted – a culture of honest inquiry. Because it was the culture of honest inquiry that encouraged us to condemn casual falsehoods and whoever tossed them into our decision-making conversations.

I think it’s fair to say that the use of casual falsehoods to win arguments has become routine in our political discourse (as evidence check out Politifact), which has, through Confirmation-Bias-driven repetition, made it routine in our social conversations as well, and from there to business conversations.

This development certainly isn’t limited to business decision-making, but as business-decision-making falls inside KJR’s domain boundaries let’s stick to your business culture.

There’s no reason to expect business decision-making to impervious. And, in fact, technology-enabled dishonesty in business decision-making is at least as old as the electronic spreadsheet. Its use in ROI calculations to “solve for the number” became so expected that the process of calculating return on investment was, in most businesses, explicitly designed to counter this practice.

If you disagree, take a look at your company’s methods, where, I’d bet, preparing high, low, and middle cost/benefits estimates is, for project proposals, mandatory.

From the perspective of prudent decision-making I sure hope your company enforces some version of this practice. But let’s home in on what it says about business culture. Which is that falling for confirmation bias isn’t considered problematic, and in fact deliberate dishonesty in making a case isn’t just acceptable – it’s encouraged. With judicious job-hopping it can even be a useful career-management tactic.

The thing about real reality is that eventually it catches up. Not always on a convenient timetable to be sure, but it does eventually catch up. Managers who are in their job for the long haul know to be wary. Early in my management career I was lucky enough to report to one of this breed.

Call him Fred. He and I were talking about a project I was advocating. Fred had a knack for not provoking defensiveness. So when he told me, “The best thing you can do with this project is to loudly and publicly put a bullet in it,” I had the good sense to listen. Fred’s point was that my high/low/middle estimates relied on assumptions that were, shall we say, optimistic.

He wasn’t accusing me of being a morally inferior being, trying to pull a fast one. He and I both understood how the game was played. His complaint wasn’t that the project would fail. That was a given. But I did have a choice – not whether the project would fail, but when.

Fred advised that killing the proposal early and loudly would do more for my reputation than watching it fail miserably after the business had invested significant time and effort into it.

Fred did his best to instill his organization with a culture of honest inquiry. He chose his side in the war on reality long before it became a serious social battleground.

I suggest you do likewise – not as a moral concern, but because if you fail to do so reality will eventually make itself known. Our collective choice isn’t whether it does.

It’s when.

Projects have Stakeholders, according to  the founder of this column.  Stakeholders may be on board with the project, ambivalent, or even detractors, but they are still stakeholders.  We serve them and the project better when we ensure that we are keeping them informed, and addressing their need to not be surprised.  One key technique to keep Stakeholders apprised of a project is through a Steering Committee meeting, probably scheduled about once per month.

It seems like there are many approaches for how to best organize and operate a Steering Committee.  In the spirit of this column and community, we want to propose a  “Bare Bones SteerCO, what you can’t not do. ”  The problem is that Greg and Bob don’t see eye to eye on this yet–.

Greg Says

Let’s start with the belief that a SteerCO meeting is not the place for surprises, debates or design.

The purpose is to keep your stakeholders informed and involved, and as aligned as they can be towards solving the business improvement project at hand.  It is an informational meeting only.  Serious discussions deserve their own time and space, involving the appropriate stakeholders.

There is a corollary here—If we don’t want this meeting to devolve, we need to elevate our preparation, and make sure that we have informed all parties effectively.  Make sure that everyone attending has necessary and relevant information and decisions/options well ahead of time, so that “Surprises” are avoided.

Bob Says

I’m not a big fan of informational meetings, Greg. I’m not even a small fan. Depending on what’s being steered, the group’s members are important people. Steering Committees/Councils are the final escalation point for resolving project issues, which means its members should have enough authority and political capital to resolve issues that reach them.

Greg Says

So, If steering committee meetings are for escalation of issues,  does this mean:

– They are scheduled regularly, or only as needed to solve a problem?

Bob Says

I think we need to rewind. Before we can talk about how often a SteerCo should meet, or what its agenda should be, we need to talk about the process of chartering, staffing, and launching it.

That means determining such matters as: Purpose, vision, key messages; guiding principles; council roles and membership; SC staff support; and more (this is a conversation, not a PowerPoint!). And, for each of these, the SC, as it forms, should establish the cadence for each SC element. It’s those cadences that should determine the SC’s meeting schedule.

Greg Says

Then Is there is a gatekeeper (probably the project sponsor), who decides what the agenda is, and when to convene them?

Bob Says

Absolutely, although as a fine distinction these should be decided by the project sponsor wearing their SteerCO Chair hat and guided by a charter.

Greg Says

I hear your concerns about informational meetings– and to some degree, I agree. At best, I think they are a necessary evil.

Perhaps it is the PTSD from some poorly run Steering Committee meetings coming out, but I think problem solving meetings should be chartered separately, with the specific mission of solving a problem as the outcome of the time invested.

Bob Says

I think this aspect of things isn’t all that hard to solve. Just build “Status Update” and “Project Issues” into the overall agenda but don’t let them dominate it.

Greg Says

How about this?  Could a compressed informational “SteerCO” meeting be delivered as a pre-recorded video from the PMs to the Council of the company?  This would allow leaders to stay informed, but asynchronously, as they have time.

Bob Says.

Well, first of all you caused me to imagine the PM doing a tap dance while tap-dancing through any hard questions the SC might need to know about. Thanks a bunch!

But second … to be effective at steering whatever they’re steering, SC members will need to interact directly with the PM.

And third, I’m thinking that if the PM reports status via pre-recorded video, they’ll start thinking in terms of production value and not just substance.

That’s when it all falls apart, as the PM organizes the project team into a barbershop quartet, and other company PMs vie for winning the Best Project Status Video award. Back to you!

Greg Says

If we are going to get the time of these very valuable and busy people,  I think we need to promise to make the most of their time.   May I propose a Minimum Viable Agenda that I believe we can give our readers for the Bare Bones SteerCO?

o   The project charter and goals.  This is an important reminder—We need to remind ourselves why we are doing this project, and what benefits we are investing in.

o   Any changes to roles or responsibilities in the team.

o   A simple “green/amber/red” stoplight chart on budget, schedule and scope.  This is what most people think a SteerCO meeting is, and this information should be conveyed as simply and visually as possible.

o   Any comparison or chart about “Where we think we are” vs “Where we think we should be.”  This is another case of simple and visual communication works wonders.

o   Upcoming milestones, and who has responsibilities for some part of the accomplishment.

o   Risks, issues, disagreements, and key decisions- Ideally, these are pre briefed, and use something like a decision paper format, so that the Council understands the issues, options, and different opinions before the meeting, and they are prepared for the discussion.

Bob Says

Yes to the MVA. My opinion is that your proposed one isn’t sufficiently Minimal.

The project charter should include cadences for such things as reviewing the project charter, vision, goals, and so on. So they’ll be in some SteerCO meetings and not others. My opinion is that each SC meeting should include:

  • Project status
    • Current: Green/yellow/red; explanation
    • Look-ahead: Potential changes to schedule, scope, and budget
  • Issues update:
    • Status of past issues
    • Impending issues
    • Cadence-driven issues
    • For each issue, support needed from the SC
  • The buzz: What SC members are hearing from the rest of the company about the project.

That’s about all I have on the subject, unless I haul out my PowerPoint deck on the subject and apply Springer’s Law to it (Springer’s Law asks “Why use a picture when a thousand words will do”?).

So I’ll leave the last word to you.

Greg Says

I hope our readers will weigh in with some ideas about what they have found to be the most effective way to plan and manage this meeting.  I feel like we have just scratched the surface of this topic.