Technology Decision Rights: Who Should Decide What

Technology decision-making in most organisations is less structured than it appears. Governance documents describe committees and approval processes, but in practice, decisions are often made informally, revisited repeatedly, or escalated upward not because the authority structure requires it, but because no one is confident who actually has the right to decide. The result is slow decisions, inconsistent outcomes, and accountability that is genuinely unclear when something goes wrong.

Decision rights answer three questions for each category of technology decision: who has the authority to make the decision, what process must be followed before the decision is made, and what information must be considered. The authority question is the most important. It identifies a specific role, not a committee or a group, as accountable for the decision. Shared accountability is, in practice, no accountability.

Technology decisions typically fall into several categories with different appropriate authority levels. Strategic direction decisions (platform choices, architectural standards, major vendor relationships) require senior executive or board involvement above a defined investment threshold. Tactical decisions (tool selection within an approved category, project methodology, team structure) can and should be delegated to technology leaders without executive involvement. Operational decisions (configuration, day-to-day technical choices) should sit with the practitioners who have the relevant expertise. The problem in most organisations is that all three categories get treated as requiring the same level of process.

Financial thresholds are the most common way decision rights are structured, but they are not sufficient on their own. A decision to select a standard enterprise platform might fall below a financial threshold that triggers board approval but carry architectural implications that will shape the technology landscape for ten years. Decision rights need to account for strategic significance and lock-in risk, not just dollar value.

Decision rights need to be written down and genuinely used, not just documented. The test is whether someone who disagrees with a technology decision knows exactly who made it, by what authority, and through what process. If that cannot be answered clearly, the decision rights are not working. Clear decision rights also make governance bodies more effective: a steering committee that understands exactly which decisions it makes, and which it does not, operates very differently from one that believes its role is to approve everything.

Organisations that establish clear technology decision rights typically see three benefits: faster decisions (because there is no ambiguity about who needs to be consulted), better decisions (because the right people are involved rather than the most senior or most available), and clearer accountability (because the person with the authority is also the person who is responsible for the outcome).