Decisions, Procedures & HIPPOs

Decisions, Procedures & HIPPOs

If there´s a moment in the organizational day-by-day that majestically embodies the term “Governance” that is the moment of making an important joint decision. What amazes me day in, day out is the absence of an “architected” approach to those moments of truth. In my experience, regardless the size of the organization, its industry and maturity level decisions are quite generally taken using a “primitive” procedure that exists just due to momentum and lack of critical thinking. In the coming lines I intend to raise this situation to the reader´s awareness and provide some food for thought for you all.

Let´s start with an example. July, CIO, is presiding the monthly IT Security SteerCo for ABC Enterprises. As per the recent increase of cybersecurity attacks, the committee must make a decision. They need to increase their IT security level. Thus, they need to choose between several IT Security suites and providers. The meeting begins somewhat late and there are solely 30min booked. To make things worse, conversation digresses and when the topic comes up, July takes command of the call and states her preference. Tommy, CSO, has concerns about the suggested solution, particularly with the 3rd party implementer. Mark, IT Ops Director, too, but more from the solution itself perspective. He has heard negative feedback from peers in other organizations. Luke, CTO, has no particular position. Ditto for Emiley, PMO Lead. The clock relentlessly spins its arms and after some discussions, the “Five minutes left in meeting” alarm pops-up in everyone screens. July takes again command of the meeting and states: “Okay, let´s get to a decision – every day that passes we are at risk, we must not postpone this anymore. I also have to jump to another call. I vote for the mentioned software, and I can have our friends from SuperDeploy next week on-site to define the implementation approach in order to get a formal proposal. So what is your final take, Tommy?” Tommy feels the pressure, he´s put on the spot. So he concedes. Mark makes a couple final rebukes but alas, “if July and Tommy agree, well, me too. So, yes”. The rest of the team robotically say “yes” and that´s it. The team adjourns the phone bridge. And we all say, “Geez, so, what just happened here?”

If you were paying attention, I guess you came to the conclusion that the aforementioned meeting was engineered to fail. Or more precisely, it lacked engineering. It was an ad-hoc, impromptu improvisation with no script, no guide, no agenda and no method, particularly for the moment of truth (the voting exercise). This is my core point: smart, logical, fact-based decisions are not taken like this. The scenario was perhaps exaggerated (lack of punctuality, lack of focus, short timeframe, etc.) but I think that we all have seen stuff like this in our careers. The voting exercise is the summit and culmination of it all. Once July makes her preference utterly clear and public (and that is the Highest Paid Personal Position or HIPPO) there is nothing left to be said. Her CIO role and commanding style pushes the rest of the attendees toward her preference. And the decision is taken.

So what´s to be done? I don´t have a one-size-fits-all answer, but First thing is to be aware of this issue which seems to affect us like a chronic disease to which we have become anesthetized. Secondly, I believe that this is the type of meeting (and particularly in a WFH / Remote culture) is the one that demands a more strict business approach: punctuality, pre-defined agenda, pre-defined time-slots, pre-defined priorities, pre-defined roles (eg, note-taker, chairman, etc.). And Third, I say that voting must not be taken lightly. The HIPPO(s) must be left at the end, for obvious reasons. If possible, the possibility of simultaneous voting tools should be considered, and perhaps in some cases, even private voting. Disclaimers should be warranted. Even second debates for final endorsement, maybe, in business critical matters. It´s a matter of creativity and tweaking an adequate solution for each org.

At the end, I believe the point is clear now: “Management is doing things right”, said Drucker. Let´s make sure that the second part of his quote – “Leadership is doing the right things” works out during voting exercises.

Fernando