Benhail Acosta

  A leadership transition is often declared successful because projects remain on schedule, systems stay available and the organization experiences no immediate disruption. Those are necessary signals of operational continuity. They are not proof that strategic accountability has survived the departure. An experienced CIO may have been doing work that never appeared clearly in the organization chart: challenging investments, negotiating acceptable risk, deciding when not to modernize and confronting assumptions that had become comfortable. When that executive leaves, the systems can remain. The decision rights may not.   A handover can transfer information without transferring judgment Transition plans normally identify contracts, active projects, budgets and operational responsibilities. The more difficult inventory is made of recurring executive decisions: which investments deserve priority, what exceptions are defensible, when a supplier recommendation should be rejected an...

  Contratar un director de tecnología puede ser una decisión correcta. También puede ser una forma costosa de evitar una conversación que la dirección todavía no ha tenido: qué necesita gobernar y quién debe responder por ello. En empresas que están creciendo, la aparición de nuevas exigencias tecnológicas suele interpretarse como evidencia de que ha llegado el momento de crear una posición ejecutiva permanente. A veces es cierto. Otras veces se está intentando corregir con estructura un vacío de decisiones. La diferencia importa porque una contratación no reemplaza el diseño de autoridad.   El costo fijo no es el único criterio Reducir el debate al salario de un CIO o al impacto en el OPEX sería insuficiente. Una organización regulada, con operación crítica o exposición significativa puede necesitar liderazgo permanente incluso antes de alcanzar determinada escala de ingresos. En cambio, una compañía más grande puede tener una operación razonablemente estable y necesitar, por...

  Complexity is not evidence of misconduct. Some decisions are difficult because the underlying business really is difficult. The governance failure appears when complexity becomes an accepted reason for not answering a legitimate executive question. A CFO asks how an investment will affect recurring expenditure. The response describes architecture. A director asks what happens if the supplier fails. The response describes service levels. Management asks who will own the risk after launch. The answer is a diagram of participating departments. The information may be accurate. It may still be irrelevant to the decision that must be made. Explanation without accountability is not oversight An executive committee does not need to become an engineering department. Nor should it assume that every technical matter can be reduced to a simple slogan. Its obligation is different: require that the consequences of a proposed decision be stated in terms the organization can approve, challenge a...

  A well-established international practice can be a useful reference. It cannot assume responsibility for what happens when a company applies it in a different operating environment. This distinction matters to investment groups and regional management teams making technology decisions across Caribbean markets. A design approved at headquarters may rest on assumptions that are not valid for the local institution responsible for executing it. The mistake is not using global expertise. It is treating that expertise as if it eliminated the need for local judgment. Standardization does not eliminate the duty to decide Uniformity can improve coordination and control. It can also create a false sense of assurance if management has not examined local constraints: regulatory obligations, contractual responsibilities, operational dependencies, business continuity and the capacity to sustain a decision over time. A regional policy may be appropriate at group level while requiring a justifie...

  Hay una dependencia que no aparece en el inventario de sistemas ni en los contratos con proveedores. Es la dependencia de una persona que sabe por qué se tomó una decisión, qué se descartó, qué riesgo se aceptó y en qué circunstancia habría que cambiar de rumbo. Mientras esa persona está presente, la organización suele confundir continuidad con capacidad institucional. Los proyectos avanzan, las operaciones responden y las excepciones se resuelven. Parece suficiente. La pregunta incómoda surge cuando esa persona deja de estar disponible: ¿quién puede tomar hoy las decisiones que ayer dependían de su juicio? No es solamente un problema de documentación Documentar procesos ayuda, pero no sustituye autoridad. Una empresa puede tener manuales actualizados, reportes completos y proveedores contratados. Aun así, puede carecer de alguien con legitimidad para decidir qué inversión se pospone, qué riesgo deja de ser aceptable o qué excepción requiere escalarse. La situación tampoco se res...

A supplier can make a technically sound recommendation and still be wrong for the business that must live with its consequences. This is not an accusation against vendors. Their expertise can be essential. The problem begins when an executive committee treats a recommendation as a decision already made, merely awaiting budget approval. The supplier owns its proposal. The company owns the exposure created by accepting it. Those are not interchangeable responsibilities. Approval is not the same as judgment A board may receive a detailed implementation plan, a commercial offer and an attractive business case. None of those documents proves that management has evaluated what the organization would lose by choosing a different path—or by refusing to proceed. Who established that the proposed investment addresses the real business constraint? Who challenged the recurring obligations that will remain after implementation? Who determined the degree of dependence the organization can accept? An...