Tag Archive Business

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.

A wise man makes his own decisions. An ignorant man follows public opinion

Chinese Proverb

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

Reflexiones de un PM en un mal día (parte II) / The deliberations of a PM on a bad day (part II)

File:The Thinker, Rodin.jpg

El Pensador / The Thinker – A. Rodin (photo by Andrew Home)

VERSION EN ESPAÑOL (ENGLISH VERSION BELOW)

La ignorancia es la semilla de todo mal” – Platón

En un artículo/post anterior (adivinen su nombre…) dijimos que la causa última – lo que en inglés se llama la “root cause” – asociado al fallo de tantos proyectos (en mi humilde opinión, de la mayoría) es la organización: la empresa o entidad como tal. Más aún, dijimos que eran los procesos organizacionales los culpables: procesos mal diseñados, mal implementados o mal ejecutados (o una combinación de estos aspectos). Tenemos entonces a un sospechoso: el sistema como tal, y caracterizamos a este sospechoso bajo el calificativo de una deficiente o incluso ausente gobierno corporativo: se trata de ORGANIZATIONAL GOVERNANCE. Postulo entonces que el fallo de la mayoría de los proyectos no se debe a causas nacidas dentro del proyecto, sino a aspectos coyunturales asociados al entorno del mismo. Antes de brindar algunas ideas para atacar este “enemigo universal”, permítaseme justificar por qué sostengo que es ese el meollo del problema. Quiero decir, de momento es solo mi opinión: no he argumentado ni he brindado evidencia que sostenga la hipótesis.  Procedamos entonces a aportar una justificación.

Comienzo con datos. Vamos entonces al ultimo informe “Pulse of the Profession”, edición 2018, por el Project Management Institute (PMI). Es en la página 25 de este informe (parte del Anexo), se pregunta (la traducción es mía): “De los proyectos iniciados en su organización en los últimos 12 meses que fueron juzgados como fallidos, cuáles fueron las causas primordiales? (Seleccione hasta 3).” Luego se provee el compilado de las respuestas, que incluye 17 causales. Me permito transcribir aquí el top 7:

  • Cambio en las prioridades de la organización: 39%
  • Cambio en los objetivos del proyecto: 37%
  • Recopilación incorrecta de los requerimientos: 35%
  • Visión o meta inadecuada para el proyecto: 29%
  • Comunicación pobre o inadecuada: 29%
  • Oportunidades o riesgos no fueron definidos: 29%
  • Inadecuada gestión del cambio: 28%

Propongámonos la meta de tratar de encontrar un mínimo común denominador en esta lista. Es retador puesto que a primera vista, estas razones para el fallo en los proyectos aparentan ser algo disconexas. Sin embargo, si miramos más atentamente, podemos ver que la palabra “cambio” se menciona en tres de ellos. En otros tres de ellos se habla de una meta inadecuada y de requerimientos incorrectos (una visión inconexa con la estrategia organizacional o bien ajena a las necesidades), además se menciona una mala gestión del riesgo (nótese que el mismo PMI utiliza el término “riesgo” de una manera cuestionable, puesto que en este informa lo utiliza como sinónimo de “Amenaza” y no como sinónimo de evento incierto; véase la definición de “Risk” transcrita abajo). Los otros dos factores mencionan aspectos de comunicación y costos. Sostengo que el mínimo común denominador (o al menos, la mejor aproximación que puede haber a una causa común) es un asunto ajeno al proyecto: no es una “infección local”, se trata más bien de un “mal pandémico” asociado más bien a la ORGANIZACIÓN.

Prosigo: las tres razones que expone Mr. Mark A. Langley (Presidente & CEO del PMI) para justificar el hecho de que el 10% del presupuesto global en proyectos se “vaya a la basura” debido a un desempeño inadecuado son (PMI´s “Pulse of the Profession” report 2018, página 2):

  1. Las organizaciones fallan a la hora de intentar cerrar el “gap” entre el diseño de la estrategia y su ejecución/delivery.
  2. Los ejecutivos no reconocen que la estrategia se implementa a través de los proyectos.
  3. La importancia fundamental de la disciplina del Project Management como el “driver” de la estrategia organizacional no es adecuadamente interiorizada.

Lo interesante es que el PMI (ciertamente no en ese informe y – que sea de mi conocimiento – en ninguna otra parte) se pregunta el POR QUÉ se presentan esos problemas. De nuevo, postulo aquí que se trata de un asunto de (deficiente) gobernanza: en una analogía, cual si fuera una persona que desea bajar de peso y no puede imponer su voluntad para mantenerse a dieta, la organización carece del “auto-dominio” para comer nutritiva y sanamente – léase que le falta la capacidad de imponer la estrategias que define (ya hablaremos de las razones). Siguiendo la analogía, la organización tampoco acepta que los proyectos adecuados son esos platillos nutritivos y correctos que la llevarán al peso deseado y desconoce el valor del ejercicio y la nutrición (el Project Management).

Me voy a permitir seguir argumentando: el mismo reporte 2018 indica que solo el 37% de las non-enterprise-wide PMOs están altamente alineadas con la estrategia organizacional. Es decir, el 63% no lo están. En el caso de las enterprise-wide PMOs (EPMOs) el resultado no es mucho mejor: solo el 41% lo está. A mi parecer, esto es grave: si bajando un solo nivel de management (C-Suite a Enterprise PMO) se perdió el alineamiento en el 60% de los casos… ¿qué podemos esperar a la hora de bajar al nivel de los proyectos, por no hablar de sus requerimientos y entregables? Además, la disciplina del Portfolio Management es gestionada solo por el 48% de las EPMOs, y marcos normativos como PRINCE2 es usado solo por el 2% (!) de las organizaciones. Los resultados de la pregunta asociada a la madurez organizacional en torno a proyectos, programas y portafolios tampoco son alentadores. Otro resultado altamente contrastante es la respuesta a la pregunta “”Qué tan exitosa calificaría a su organización desarrollando lsa siguientes actividades sobre los siguientes tres años – formulación de una estrategia adecuada para las condiciones cambiantes del mercado?” Los ejecutivos calificaron como “Excelente” en el 43% de los casos y “Bueno” en un 50%, mientras que los líderes de PMOs indicaron un 13% yu un 46% en esas categorías de respuesta… Hmmm… me pregunto cuáles serían las respuestas en el caso de preguntarle esto a los Program y Project Managers. La distribución de respuestas también contrasta a la hora de preguntar por la priorización de los proyectos: aparentemente los Ejecutivos creen estar haciendo un excelente trabajo… pero el resto de la organización no coincide con esta apreciación. Tengo algún otros puntos, pero para efectos de mantener este artículo de  un tamaño “digerible”, voy a dejar mi argumentación hasta aquí: el “fiscal” descansa.

Sostengo entonces que esta pandemia está asociada a problemas de carácter estratégico, como lo son la visión, misión y objetivos organizacionales, y el alineamiento de los portafolios, programas y proyectos con los mismos. Finalmente, sostengo que este problema de alineamiento se deriva a su vez de un modelo de gestión de la gobernanza obsoleto, que como la teoría económica de hace solo unos 30-40 años, se erige sobre una serie de supuestos erróneos que desconocen la curiosa naturaleza del ser humano.

En el siguiente artículo de esta serie, vamos a explorar cuáles son esos supuestos que corrompen la toma de decisiones y ahondaremos en los problemas del modelo “usual” de gobernanza en las organizaciones, modelo que está “diseñado para fallar” y termina haciéndolo “brillantemente” de mil y una formas: aprobando el lanzamiento de proyectos que no deberían aprobarse, sobrecargando el “pipeline” con más trabajo de lo que los equipos organizacionales pueden gestionar, apurando de manera desmedida esfuerzos, etc. etc.

¿Curioso? Eso espero – le espero en el siguiente post…

 

Material complementario / fuentes:

  • Informe “Pulse of the Profession 2018” por el PMI, haz click aquí
  • Definición de riesgo del PMI: “El riesgo de un proyecto es un evento o condición incierta que, de producirse tiene un efecto positivo o negativo en uno o más objetivos del proyecto, tales como el alcance, el cronograma, el costo y la calidad”
  • “El pensador”, la estatua mostrada al principio, haz click aquí

ENGLISH VERSION

“Ignorance, the root and stem of all evil” – Plato

In the prior article of this series (guess that post´s title…) we said that the root cause behind the failure of so many projects (in my humble opinion, of the majority) is the organization itself: the company or entity. Moreover, we said that the organizational processes are the ones to be blamed: processes that are faulty designed, faulty implemented, or faulty operated (or a mix of those faults). We got as such a suspect: the org system, and we characterized the suspect under the ORGANIZATIONAL GOVERNANCE tag. As such, I state that the failure of the majority of the projects is a cause not hidden within the project itself, but in the environment around it. Before I suggest some ideas in order to tackle this “universal enemy” of Project Management, let me justify why I state that this is the real enemy. I mean, to this point, this is basically an opinion, but I have not provided arguments nor evidence to back it up: let´s proceed with those right away.

Data comes first… There is “gold” hidden in the last Project Management Institute (PMI) “Pulse of the Profession” report v. 2018. Let´s jump to page 25,  where this question is raised: “Of the projects started in your organization in the past 12 months that were deemed failures, what were the primary causes of those failures? (Select up to 3).” Then the stock of answers is provided. Below the top 7:

  • Change in organization’s priorities 39%
  • Change in project objectives 37%
  • Inaccurate requirements gathering 35%
  • Inadequate vision or goal for the project 29%
  • Inadequate/poor communication 29%
  • Opportunities and risks were not defined 29%
  • Poor change management 28%

Let´s try to figure a lowest common denominator to this list. It is a challenge because at first glance, the reasons seem to be rather arbitrary. But when we take a closer look, we notice that the word “Change” is mentioned in three of those. Another two mention an inadequate goal and inaccurate requirements (in other words, a project vision not aligned to the organizational strategy or goals – changes and changes are required to adapt along the way). Failed risk management is also there (notice that the PMI itself is doing a corrupt use of the term risk in this report, since it it uses it as a synonym of threat instead of the official definition associated to uncertainty – see official definition below). The other factor is linked to communication. I assert that the lowest common denominator (or its best approximation, if you will) is associated to the organization: its a pandemic fault, not a “local disease”.

Let me continute: the three reasons that Mr. Mark A. Langley (Presidente & CEO, PMI) mentions as the rationale behind the fact that 10% of the global project budget is literally wasted are (PMI´s “Pulse of the Profession” report 2018, page 2):

  1. Organizations fail to bridge the gap between strategy design and delivery.
  2. Executives don’t recognize that strategy is delivered through projects.
  3. The essential importance of project management as the driver of an organization’s strategy isn’t fully realized

The interesting thing here is that the PMI (certainly not in this report and to my current knowledge, nowhere else) ever asks WHY do these things happen. Again, I avow that this happens due to deficient organizational GOVERNANCE: in an analogy, like a person that wants to cut weight but cannot stick to the diet, the organization lacks the “self-control” to eat in a healthy and nutritive way (it lacks the ability to implement the defined strategy and select the right projects, we will talk as of the why soon). Continuing with the analogy, the organization also neglects the importance of those nutritive meals and of exercise which are the driver to the right weight (meaning, the importance of enforcing healthy Project Management).

And I have even more reasons to support my point: according to the same Pulse of the Profession report v.2018, just 37% of non-enterprise-wide PMOs are highly aligned to the org stratetgy. In other words, 63% are not. In the case of enterprise-wide PMOs (EPMOs) the result is frankly not much better: only 41% are. To my understanding, this is a big issue: if going down just one step of the org ladder (C-Suite to an EPMO level) generates strategical misalignment in 60% of the cases, what can we expect when we go down to the project, requisites and deliverables level? To make things worse, the same report states that Portfolio Management is steered just by 48% of the EPMOs and that powerful normative and structuring frameworks such as PRINCE2 is used just by 2% (wow!) of the organizations. The results that measure maturity level aren´t also heartening.

Yet another enlightening point is the answer to the question “How would you rate your organization’s success in performing the following activities over the last three years? – Formulating strategy appropriate for changing market conditions?” Execs went for “Excellent” in 43% of the times and “Good” in a 50%, whereas PMO-leads stated 13% and 46% for those categories (Excellent and Good) Hmmm… I wonder which would be the percentages if those questions were raised to PgMgrs and PMs. The contrast between Execs and PMO-leads perception is also apparent when asking about the quality of the project prioritization efforts: it seems Execs are quite positive about their work but the rest of the org is not very fond of it. I have even more arguments and evidence to support my case against organizational governance, but for the sake of brevity, I´ll leave it here: the prosecutor rests.

CONCLUSION: I affirm that the core cause is associated to strategic issues and its steering through the org: misalignment of the portfolios, programs and projects to the org strategy. And I finally assert that these alignment problems are due to an outdated governance model across our organizations that, like the economic theory that ruled just about 30 or 40 years ago, relies on a series of faulty assumptions associated to the way we human beings live, take decisions, enact and act.

In the next post of this series we will examine which are those assumptions and biases that corrupt the strategic and decision-making processes and we will deep-dive in the problems associated to the “standard” organizational governance model, which is “designed to fail”: and indeed it fails brilliantly, overloading the pipelines, approving for launch or for next-phase a load of “mutant” endeavors, smashing timelines, etc. etc. And we will also suggest some ways to tackle the problem – or at least reduce its intensity.

Curious? I hope so: see you in the next post of this series…

 

BONUS MATERIAL:

  • PMI´s official risk definition: “”an uncertain event or condition that, if it occurs, has a positive or negative effect on a project’s objectives.”
  • PMI´s “Pulse of the Profession” report v.2018, click here
  • The Thinker (the statue pictured on top), click here