Software Delivery: Successfully Influencing Change

Software delivery is rarely just a technical challenge; technology is the easy part, right?. While tools, architectures, and processes matter, the real determinant of success is often how well change is influenced across people, teams, and organisations.

In modern software delivery, change is constant: new technologies, evolving customer needs, shifting priorities, and growing delivery pressures. Teams that succeed are not simply those that adopt the latest frameworks, but those that can guide people through change in a deliberate and human way.

Why Change Is Hard in Software Delivery

Most delivery transformations fail not because the ideas are wrong, but because the organisation isn’t ready to absorb them. I'm confident there are many teams in organisations today that agree with this.

Common challenges include:

• Resistance to new ways of working

• Fear of losing control or relevance

• Misalignment between leadership intent and team reality

• Change fatigue from too many initiatives at once

Software delivery touches many roles - developers, testers, product managers, operations, security, and leadership. Each group experiences change differently. Ignoring this complexity leads to surface-level adoption and long-term frustration.

Influence Over Authority

One of the most important lessons in leadership is this: you cannot mandate successful change.

Influence is far more powerful than authority. Teams commit to change when they understand why it matters, how it helps them, and what success looks like.

Effective influencers:

• Listen before they prescribe

• Frame change in terms of outcomes, not tools

• Build credibility through small, visible wins

• Respect existing constraints while challenging unhelpful habits

Change sticks when people feel part of it, not subject to it.

Start With Outcomes, Not Processes

Too many change initiatives begin with process diagrams and maturity models. Successful ones begin with clear outcomes.

Instead of saying:

“We need to implement Agile better”

Say:

“We need to reduce time-to-market and improve reliability without burning people out”

When outcomes are clear, teams can align decisions, experiments, and trade-offs around shared goals. Processes then become enablers, not rules.

Create Psychological Safety

Change requires learning, and learning requires failure. If teams fear blame, they will protect themselves rather than improve delivery.

Psychological safety enables:

• Honest conversations about what isn’t working

• Earlier surfacing of risks and issues

• Experimentation with new approaches

• Continuous improvement instead of defensive behaviour

Leaders influence safety through their responses - especially when things go wrong. Curiosity consistently outperforms criticism.

Use Incremental Change, Not Big Bangs

Large, sweeping transformations often overwhelm teams. Incremental change, delivered in small, meaningful steps, is more effective and sustainable.

In software delivery this might look like:

• Improving one workflow before scaling it

• Piloting new practices with a single team

• Measuring impact and adjusting before expanding

• Celebrating progress, not perfection

Momentum builds confidence. Confidence builds buy-in.

A quote I always refer to when working with teams:

"Continuous improvement is better than delayed perfection" ~ Mark Twain

Align Leadership, Middle Management, and Teams

One of the biggest risks to delivering change is misalignment across organisational layers.

Leadership may want speed. Middle management may worry about predictability. Teams may want autonomy and clarity.

Successful influence connects these perspectives rather than choosing sides. Translating goals up and down the organisation ensures change is reinforced, not undermined, at each level.

Change Is a Capability, Not a Project

The most successful software organisations treat change as an ongoing capability rather than a one-time initiative.

This means:

• Regular reflection on how work is delivered

• Investing in coaching and leadership development

• Measuring outcomes, not just outputs

• Continuously evolving practices as context changes

When organisations become good at change, delivery improves naturally.

Finally

Software delivery excellence is not achieved solely through frameworks. It emerges when technical practices are paired with strong influence, empathy, and leadership.

By focusing on people, outcomes, and trust, organisations can move beyond adopting change to truly owning it - and deliver software that consistently creates value.