The Struggle of Technology Governance

Technology governance is often described through visible mechanisms. Policies, approval routes, risk registers, reporting packs, standards and committees. These are important, but they are only the observable part of the system.

The harder work sits underneath. It involves aligning culture, maintaining a shared strategic direction, transferring knowledge that has never been written down and influencing how people behave when no formal control is watching.

These activities are difficult because they are intangible. They cannot be installed like software, completed like a project task or demonstrated by publishing another document. Yet they often determine whether the visible governance mechanisms produce meaningful results or become administrative theatre.

The visible side of governance is easier to manage

Visible governance activities are attractive because they can be counted and evidenced. A policy exists or it does not. A meeting happened or it did not. A risk was recorded, an approval was captured and a report was issued.

This creates a natural tendency to concentrate on artefacts. When leaders ask whether governance is in place, the answer may be a folder of policies, a calendar of review meetings and a set of dashboards.

Those items show that a structure exists. They do not necessarily show that people understand the purpose, make consistent decisions or behave in a way that supports the intended outcome.

Cultural alignment cannot be mandated

Culture influences what people consider normal, acceptable and worth prioritising. It shapes whether teams raise concerns early, share incomplete information, challenge weak decisions and accept responsibility across organisational boundaries.

A policy may say that risk should be escalated, but the culture may quietly reward people for keeping problems out of sight. Leaders may ask for collaboration while performance targets encourage local optimisation. Suppliers may be described as partners while every interaction is treated as a contractual dispute.

Cultural alignment becomes particularly difficult when technology crosses several groups with different incentives:

• business leaders may prioritise speed and commercial opportunity;
• technical teams may prioritise resilience, maintainability and security;
• finance may focus on cost control and predictability;
• suppliers may optimise delivery around contractual measures;
• employees may create workarounds to complete tasks more quickly.

None of these perspectives is inherently wrong. Governance must help the organisation reconcile them around a shared result. That requires repeated leadership behaviour, open discussion of trade-offs and consequences that match the stated priorities.

Culture changes when people see that the organisation consistently rewards the desired behaviour. It does not change because a value has been added to a presentation.

Strategic vision must survive everyday decisions

Most organisations can produce a high level technology vision. The difficulty is turning that vision into a practical guide for hundreds of smaller decisions.

A statement such as “simplify the technology landscape” may sound clear until a business unit requests another specialist platform. “Become data driven” may conflict with fragmented ownership and inconsistent definitions. “Automate where possible” can encourage activity without proving that the underlying work should exist in its current form.

The strategic vision becomes real when people can use it to answer practical questions:

• Which problems deserve investment?
• When should an existing platform be improved rather than replaced?
• Which local variation is genuinely necessary?
• What should be standardised across the business?
• Which short term compromise creates an unacceptable long term cost?

Governance therefore has to translate broad ambition into decision principles, priorities and boundaries. It must also keep those principles visible when urgent demands, supplier recommendations and attractive new technology compete for attention.

The strongest strategic alignment is not demonstrated by everyone repeating the same slogan. It is demonstrated by different teams reaching compatible decisions without needing every issue escalated to senior leadership.

Tacit knowledge is valuable because it is difficult to express

Some of the most important operational knowledge does not sit in a document. It exists in experience. Knowing which supplier contact can unblock an issue, recognising an unusual pattern in a report, understanding why an apparently unnecessary control was introduced or anticipating how one department will react to a change.

This is tacit knowledge. It develops through context, observation and repeated practice. Because it is difficult to articulate, organisations often underestimate how dependent they are on it.

The risk becomes visible when a key person is unavailable, leaves the organisation or is excluded from a decision. A formally documented process may exist, yet work slows because the document does not contain the judgement needed to navigate exceptions.

Tacit knowledge cannot be completely converted into procedures. The goal should be to reduce unhealthy dependency while preserving useful judgement.

Practical approaches include:

• pairing people during complex or infrequent activities;
• recording the reasoning behind important decisions, not only the final outcome;
• using short operational reviews to discuss what was noticed and why it mattered;
• rotating responsibility so knowledge is exercised by more than one person;
• building communities around shared problems rather than relying only on formal reporting lines;
• and creating enough psychological safety for people to admit what they do not know.

Knowledge sharing is therefore partly a cultural activity. People must believe that sharing expertise increases their value rather than making them easier to replace.

Behavioural compliance is different from formal compliance

Formal compliance asks whether a required step was recorded. Behavioural compliance asks whether people consistently act in line with the intention of the control.

A change may have an approval reference while the approver lacks the information needed to make a sound decision. A supplier review may occur every month while weak performance is repeatedly accepted. A security process may be followed on paper while employees routinely share information through unofficial channels because the approved method is too difficult.

This gap is not always caused by carelessness. People usually adapt their behaviour to the pressures and incentives around them. When a control creates excessive friction, they find a route around it. When deadlines dominate every discussion, risk considerations become a formality. When leaders bypass the process, others learn that compliance is optional for urgent or influential requests.

Behavioural compliance improves when:

• the purpose of the control is understood;
• the required behaviour is realistically achievable;
• leaders demonstrate the same behaviour they expect from others;
• exceptions are visible and genuinely exceptional;
• and consequences are applied consistently.

The objective is not blind obedience. Effective governance allows challenge and proportionate exceptions, but makes the reasoning and accountability clear.

The measurement problem

Intangible activities are difficult to measure directly, which can make them appear less valuable than visible outputs.

It is easier to report the number of policies reviewed than the quality of decision making. It is easier to count training attendance than to assess whether behaviour changed. It is easier to record that knowledge was documented than to know whether another person can apply it under pressure.

Measures can still help, but they should be treated as indicators rather than proof. Useful signals might include:

• fewer decisions being repeatedly escalated because ownership is unclear;
• greater consistency between local technology choices;
• earlier reporting of risks and operational concerns;
• reduced dependency on individual experts;
• fewer repeated exceptions to controls;
• and better alignment between supplier activity and business priorities.

Qualitative evidence also matters. Decision reviews, interviews, observed behaviour and the quality of cross team discussions can reveal more than a dashboard alone.

Making the intangible practical

Intangible governance should not become an excuse for vague discussion. It can be strengthened through deliberate and repeatable management practices.

1. Define the behaviour, not only the rule. Explain what people should do differently and why it matters.
2. Translate strategy into decision principles. Give teams practical guidance for common trade-offs.
3. Align incentives with the stated outcome. Check whether targets and rewards encourage contradictory behaviour.
4. Make reasoning visible. Record why important decisions were made, including assumptions and compromises.
5. Create repeated opportunities for knowledge transfer. Use pairing, reviews, communities and rotation rather than relying on one-off documentation.
6. Observe exceptions. Repeated workarounds often indicate that a control or process does not fit the reality of the work.
7. Review the system, not only the individual. When behaviour falls short, examine the pressures, information and incentives that shaped it.

This approach makes the intangible sufficiently visible to manage without pretending that culture, judgement and trust can be reduced to a checklist.

Signs that governance is working

Successful governance is often visible through what stops happening.

Fewer decisions are delayed while people search for an owner. Teams are less surprised by each other’s priorities. Suppliers receive clearer direction. Risks surface before they become incidents. Employees need fewer informal workarounds. Knowledge is less concentrated in one person. Exceptions are discussed openly rather than hidden inside routine activity.

The organisation also becomes better at dealing with ambiguity. People can make proportionate decisions without waiting for a policy to describe every possible situation because they understand the intended outcome, the relevant principles and the boundaries of their authority.

That is the central struggle of intangible technology governance. The most valuable results depend on activities that are difficult to see and impossible to control through documentation alone.

The answer is not to abandon formal governance. It is to recognise that policies, reports and approval structures only work when culture, strategic understanding, shared knowledge and everyday behaviour reinforce them.