When a digital initiative stalls, somebody eventually says, “It’s a cultural thing.” The room usually agrees, and the diagnosis changes nothing.

Culture is too broad a category to act on. It can mean incentives, status, decision rights, habits, professional identity, leadership behaviour or the memory of a previous programme that went badly. Treating all of that as one problem is like being told you are unwell without being told what is wrong.

The useful question is narrower: which observable behaviour is stopping this particular initiative, what sustains it, and who can change the conditions around it?

Across digital programmes in professional services firms, five patterns recur. A firm may show traces of all five, although one or two usually explain most of the drag on a given programme. Naming the pattern matters because each one requires a different response. A workshop about values will do little for unclear decision rights. A new governance committee will do little when personal incentives reward inaction.

1. Consensus becomes a veto

Partnerships depend on consultation. The trouble starts when consultation has no boundary.

A decision is made in a meeting. A partner who was absent raises a reservation, so the decision reopens. Another meeting is arranged, another person cannot attend, and a project that has budget, a delivery partner and broad support remains stationary. Nobody has rejected it. Nobody has quite authorised it either.

The underlying issue is often social rather than procedural. The cost of pushing a decision through over a colleague’s discomfort can feel immediate and personal. The cost of another month’s delay is spread across the firm and may never appear against one person’s name. Waiting is therefore the safer choice, even when almost everyone favours the initiative.

The response is bounded consultation. Before debating the proposal, agree:

  • who makes the decision;
  • whose input is required;
  • whether the threshold is unanimity, a majority or a named decision-maker after consultation;
  • what evidence could legitimately reopen the decision; and
  • the date after which further preferences enter a backlog rather than resetting approval.

These rules protect consultation while preventing every reservation from becoming a veto. Agreeing them at the start also makes the mechanics less personal when the difficult moment arrives.

Our article on building momentum for change in risk-averse industries looks more closely at how to move such decisions forward.

2. Inaction carries less personal risk than a failed attempt

Fear of failure rarely introduces itself by name. It appears as requests for more data, a smaller pilot or another revision to a business case. Those requests can be sensible. The pattern becomes visible when no amount of evidence is sufficient, or when a pilot is made so small that it cannot answer the decision it is supposed to inform.

Professional reputation is valuable. A visible initiative that falls short may attach itself to its sponsor, while the cost of doing nothing is harder to attribute. The internal calculation can become simple: if the project fails, people remember who proposed it; if the firm never starts, few people notice who hesitated.

Leaders cannot remove risk by declaring that experimentation is safe. People judge what happens after a real setback. When a pilot changes direction, do senior colleagues ask what it revealed, or search for the person who got the original proposal wrong? When an assumption fails, is the learning recorded and used, or hidden to protect the sponsor?

Make pilots answer explicit questions. Set the spending limit, success measures, stop conditions and decision date in advance. Then distinguish between three outcomes:

  1. the approach shows enough value to continue;
  2. the evidence supports changing the approach; or
  3. the test prevents a larger investment in an idea that does not work.

All three can be useful results. That principle becomes credible only when leaders apply it publicly and consistently.

3. Shared oversight replaces individual ownership

“The steering committee will oversee this” sounds reassuring. It may also conceal the absence of a person who owns the outcome.

A committee can challenge, advise and unblock. It cannot provide singular accountability if its members hold different definitions of success or assume somebody else has the final call. Programmes then accumulate updates, papers and meetings while decisions wait between them.

At approval, name one accountable owner. Give that person the authority needed to do the job, including the ability to reject scope changes, resolve trade-offs and escalate constraints. Be equally clear about the roles around them:

  • the steering group supplies challenge and organisational support;
  • the delivery lead manages the work;
  • subject specialists provide evidence and constraints; and
  • the accountable owner decides whether the programme is delivering its agreed outcome.

One owner does not mean one person does all the work. It means the answer to “who decides?” is a name rather than a committee title. If the named owner lacks time, budget authority or access to senior decision-makers, the firm has assigned responsibility without power. That is another form of non-ownership.

4. Every initiative is treated as a priority

Ask a leadership team to identify its three most important digital initiatives. If the answer is that all eleven are high priority, the portfolio has no priorities.

In that environment, work moves according to status, persistence and proximity. The partner who catches the COO after a meeting gets an enhancement moved forward. The largest practice group receives attention because disappointing it is difficult. Work with greater client or commercial value waits behind requests that are easier to sponsor.

This is rarely a failure to understand prioritisation. It is a reluctance to impose its consequences. Choosing one initiative means sequencing another, and the colleague whose request moves down the list may be an important fee earner or ally.

Use criteria that are agreed before individual proposals are scored. They might include client impact, strategic contribution, risk reduction, economic value, urgency, delivery effort and dependencies. Apply them across the portfolio at a set frequency. Record why an initiative has moved and what would cause the decision to change.

We use WHNN®, our own quarterly planning framework, for this kind of conversation. Firms can use other methods. The essential discipline is to compare work against common criteria and accept that prioritisation includes a decision to defer. “Later” should also have a review date; otherwise it is merely a softer word for “never”.

5. The organisation is viewed from the inside out

Professional services firms are built around practices, service lines and technical disciplines. That structure supports expertise, revenue management and careers. Clients, however, often move across those internal boundaries.

The source version of this article described a CRM programme in which three practice groups specified their needs separately. The resulting system met each group’s request and failed to provide a usable view of the whole client relationship. The IT leader’s summary remains the sharpest description of the problem: “Everyone got what they asked for, and nobody got what they needed.”

Siloed thinking is more than poor cooperation. It is a consequence of evaluating investment through local benefits. Each group can make a reasonable case from its own perspective while the combined result makes the client journey worse.

For cross-firm initiatives, add a client-outcome test to the business case:

  • Which client journey does this affect?
  • Where does that journey cross internal boundaries?
  • What information or action must pass between teams?
  • Who owns the complete experience?
  • Which local preference should give way if it damages the end-to-end outcome?

For example, replace “the employment team needs a better workflow” with “clients need a reliable handoff between employment and corporate work during a transaction”. The second framing exposes dependencies that the first leaves hidden. It also makes conflicts visible while there is still time to resolve them.

Diagnose behaviour, then change the conditions

Calling a problem cultural can make it sound permanent. These five patterns are sustained by identifiable conditions: unlimited consultation, asymmetric career risk, blurred accountability, absent portfolio choices and incentives tied to local rather than client outcomes.

A practical diagnosis should connect behaviour to consequence. Compare these two statements:

Our people are resistant to change.

Any partner can reopen an approved decision, adding several months to work after the budget has been agreed.

The first is a judgement about people. The second is an observable operating problem with a possible response. It identifies the behaviour, the cost and the decision rule that needs attention.

Choose the one or two patterns creating the greatest constraint now. Find a recent example, identify what rewarded or permitted the behaviour, and make one change to those conditions. Then watch what happens in the next real decision. Cultural change becomes manageable when it is treated as a sequence of changes to work, authority and incentives rather than a campaign to improve everybody’s attitude.

If your leadership team wants a starting point, use the cultural blockers diagnostic available through the download form below. Ask each person to identify the strongest current pattern and bring one example. Differences in their answers are useful evidence in their own right.

Once the pattern is clear, WHNN®, our framework for planning and delivering digital programmes, can help turn the diagnosis into an owned and sequenced response.