Practical ways to move ideas forward in complex organisations.

Change often sounds simple from the outside.

A better process is identified. A new idea is proposed. A problem becomes visible. The solution may even appear obvious.

But inside a complex organisation, change is rarely straightforward.

Large organisations are shaped by established systems, competing priorities, formal approval processes, internal politics, limited resources, and deeply rooted habits. Even a strong idea can struggle to move forward if it does not fit the organisation’s structure, timing, or culture.

This can be frustrating for people who see what needs to improve.

They may feel that progress is too slow, decision-making is too complicated, or leadership is not responding quickly enough. Some eventually conclude that meaningful change is impossible from within.

But change from inside the system is possible.

It requires more than having a good idea. It requires patience, influence, strategy, trust, and an understanding of how the organisation really works.

Why Good Ideas Often Get Stuck

People sometimes assume that a good idea should succeed on its own.

In reality, organisations do not evaluate ideas only on quality. They also consider risk, cost, timing, ownership, capacity, and alignment with existing priorities.

An idea may fail to move forward because:

• The right decision-maker has not been involved
• The benefits are not clearly explained
• The proposal appears too risky
• The timing is wrong
• Teams are already overloaded
• The idea threatens existing responsibilities
• There is no clear owner
• The organisation has seen similar initiatives fail before

This does not necessarily mean the idea is bad.

It may mean the idea has not yet been translated into a form the organisation can support.

Creating change requires understanding not only what should happen, but also what must be true for others to say yes.

Start by Understanding the System

Before trying to change a system, understand it.

Complex organisations often operate through both formal and informal structures.

The formal structure includes:

• Organisational charts
• Job titles
• Approval processes
• Budgets
• Policies
• Committees
• Reporting lines

The informal structure includes:

• Trusted relationships
• Influential individuals
• Unwritten rules
• Past experiences
• Internal reputation
• Political sensitivities
• Personal priorities

The formal structure may show who has authority.

The informal structure often reveals who has influence.

A successful change leader pays attention to both.

Ask:

• Who makes the final decision?
• Who influences that person?
• Who will be affected by the change?
• Who may feel threatened by it?
• Which team has the capacity to support it?
• What previous attempts have been made?
• What language does the organisation use when discussing priorities?

Understanding the system helps you move through it more effectively.

Define the Real Problem

Many change efforts begin with a solution.

“We need a new platform.”

“We should redesign the process.”

“We need another team.”

But before proposing a solution, clarify the problem.

A weak problem statement may focus on symptoms:

“The reporting process is frustrating.”

A stronger problem statement explains impact:

“The current reporting process requires employees to enter the same information in three systems, adding several hours of administrative work each week and increasing the risk of errors.”

The clearer the problem, the easier it is for others to understand why change matters.

A strong problem statement should explain:

• What is happening
• Who is affected
• Why it matters
• What the current cost is
• What may happen if nothing changes

People are more likely to support change when the problem feels real, specific, and relevant.

Connect the Idea to Organisational Priorities

An idea is easier to support when it helps the organisation achieve something it already values.

Instead of presenting change as a separate initiative, connect it to existing goals.

For example:

• Improved customer experience
• Reduced operating costs
• Faster delivery
• Lower risk
• Employee retention
• Regulatory compliance
• Revenue growth
• Better collaboration
• Stronger data quality

The same idea can sound very different depending on how it is framed.

“We should change this process because it is outdated” may create resistance.

“This change could reduce processing time, lower error rates, and support the organisation’s efficiency target” is more likely to gain attention.

This is not about manipulating the message.

It is about showing how the idea contributes to what the organisation is already trying to achieve.

Build Support Before Making the Formal Proposal

One of the most common mistakes is presenting an idea publicly before building support privately.

In complex organisations, formal meetings are often not where decisions begin. They are where decisions are confirmed.

Before presenting the idea, speak with people who:

• Understand the issue
• Will be affected by the change
• Have influence over the decision
• Could challenge the proposal
• May help improve the idea

Use these conversations to learn.

Ask:

• What concerns would you have about this?
• What would make this easier to support?
• Who else should be involved?
• What risks am I overlooking?
• Has something similar been tried before?
• What would leadership need to see?

These conversations help you identify resistance early.

They also turn potential critics into contributors.

People are more likely to support an idea when they have had a chance to shape it.

Find the Right Allies

Change is rarely created by one person.

Even if you are the original source of the idea, you will need allies.

Useful allies may include:

• A respected senior leader
• A subject-matter expert
• A well-connected colleague
• Someone close to the affected customers or employees
• A person with budget authority
• A trusted operational leader
• Someone who has successfully delivered change before

Different allies provide different forms of support.

One person may offer credibility. Another may provide technical knowledge. Another may help navigate the approval process.

The strongest change efforts are supported by a coalition of people who see value in the outcome.

You do not need everyone to agree at the beginning.

You need enough support to create momentum.

Start Smaller Than You Think

Large proposals can create large resistance.

When an idea requires significant budget, multiple teams, new technology, or major structural change, leaders may hesitate even if they agree with the goal.

A smaller pilot can make the idea easier to support.

Instead of asking for organisation-wide approval, ask:

• Can we test this with one team?
• Can we run a four-week pilot?
• Can we trial the process with one customer group?
• Can we use existing tools before investing in new ones?
• Can we measure the result before expanding?

Small experiments reduce risk.

They also turn a theoretical idea into practical evidence.

A successful pilot creates something powerful: proof.

Proof is often more persuasive than a presentation.

Make the First Step Easy to Approve

When people face a large decision, they often delay.

A useful strategy is to separate the full vision from the immediate request.

You may have a long-term goal, but the first decision should be clear and manageable.

For example:

Long-term goal:

Redesign the organisation’s internal approval process.

Immediate request:

Approve a review of the current process and allow interviews with ten employees who use it regularly.

The first step does not need to solve the entire problem.

It only needs to create movement.

Once the organisation takes the first step, the next step often becomes easier.

Use Evidence, Not Only Enthusiasm

Passion can attract attention, but evidence builds confidence.

When proposing change, support the idea with relevant information.

This may include:

• Customer feedback
• Employee feedback
• Process data
• Cost estimates
• Error rates
• Time lost
• Risk assessments
• Industry benchmarks
• Pilot results
• Case studies
• Examples from other teams

Evidence helps people see the problem more objectively.

It also reduces the perception that the proposal is based only on personal opinion.

However, do not overwhelm people with information.

Use the evidence that matters most to the decision.

A clear story supported by a few strong facts is often more effective than a long document full of data.

Translate the Idea for Different Audiences

Different stakeholders care about different outcomes.

A finance leader may focus on cost.

An operations leader may focus on efficiency.

A technology team may focus on security and integration.

Employees may focus on workload and usability.

Senior leaders may focus on strategic value and risk.

The core idea can remain the same, but the explanation should reflect the audience’s priorities.

This does not mean changing the truth.

It means making the value relevant.

Before each conversation, ask:

• What does this person care about?
• What problem does this solve for them?
• What concern are they likely to raise?
• What evidence would they find credible?
• What decision do I need from them?

Effective change leaders do not only communicate clearly.

They communicate with relevance.

Expect Resistance

Resistance is a normal part of change.

People may resist because they:

• Do not understand the need
• Fear losing influence or control
• Expect more work
• Do not trust leadership
• Have seen previous changes fail
• Feel excluded from the process
• Believe the current system works
• Worry about unintended consequences

Resistance should not always be treated as negativity.

Sometimes resistance contains useful information.

A critic may reveal a real operational risk. A cautious manager may remember an earlier failure. An employee may understand the practical impact better than the project team.

Instead of immediately defending the idea, ask:

• What concerns you most?
• What could go wrong?
• What would make this more workable?
• What experience is shaping your view?
• What part of the idea do you support?

This approach helps separate genuine risk from simple discomfort.

It also shows respect.

Avoid Making the Change Personal

When people strongly believe in an idea, they can begin to treat criticism of the idea as criticism of themselves.

This makes change harder.

If every objection feels personal, conversations become defensive. The focus shifts from improving the idea to protecting it.

Strong change leaders remain committed to the outcome while staying flexible about the method.

They are willing to say:

• This part may need to change
• I had not considered that
• Your concern is valid
• There may be a better approach
• Let us test both options

The goal is not to prove that your original idea was perfect.

The goal is to create meaningful improvement.

Build Credibility Through Small Wins

People support change leaders they trust.

Credibility grows when you:

• Follow through on commitments
• Communicate honestly
• Share credit
• Admit uncertainty
• Deliver practical results
• Respect people’s time
• Avoid exaggerating benefits
• Address problems early

Small wins are especially important.

A successful improvement, even a limited one, shows that change is possible.

It creates confidence and makes future proposals easier to support.

Momentum is built gradually.

One successful pilot can lead to a larger project. One improved process can create interest in wider reform.

Work With the System Without Becoming Trapped by It

Creating change from inside the system requires a balance.

You need to understand procedures, relationships, and organisational realities. But you also need to avoid becoming so cautious that the original purpose is lost.

Some people become frustrated and challenge everything directly.

Others become overly adapted and stop challenging anything at all.

Effective internal change leaders do neither.

They respect the system enough to work through it, but question it enough to improve it.

They know when to follow process and when to challenge unnecessary barriers.

They know when to compromise and when the core principle must remain.

This balance requires judgment.

Know When to Escalate

Not every obstacle can be solved through informal influence.

Sometimes a decision is blocked because:

• No one wants to take ownership
• The issue creates serious risk
• The problem affects customers or employees
• The delay is causing significant cost
• The current process is unethical or unsafe
• Lower-level discussions have failed

In these cases, escalation may be necessary.

Escalation should be thoughtful, not emotional.

Present:

• The issue
• The evidence
• What has already been tried
• The risks of inaction
• The decision required
• A practical recommendation

The purpose of escalation is not to embarrass people.

It is to move an important issue to the level where it can be addressed.

Communicate Progress

Change loses energy when people do not know what is happening.

Even if progress is slow, communicate clearly.

Share:

• What has been agreed
• What is being tested
• What has been learned
• What decisions are pending
• What happens next
• Where support is needed

This helps maintain trust.

It also prevents rumours and misunderstanding.

People are more patient with a complex process when they can see that movement is taking place.

Silence often makes progress look like failure.

Be Patient Without Becoming Passive

Change inside organisations often takes longer than expected.

Approvals are delayed. Priorities shift. Leaders change. Budgets move. Teams become overloaded.

Patience is necessary.

But patience should not become passivity.

Keep the idea moving through small actions:

• Schedule the next conversation
• Improve the evidence
• Build another relationship
• Test a smaller version
• Clarify the business case
• Follow up on decisions
• Document progress

Not every week will produce a major breakthrough.

But consistent movement matters.

Change often appears slow until several small actions suddenly create momentum.

Measure What Changes

A change effort is not complete when a new process is launched.

It is complete when the intended outcome improves.

Measure:

• What changed
• Whether the problem was reduced
• Who benefited
• What unintended effects appeared
• What should be adjusted
• Whether the change should expand

This creates accountability.

It also generates evidence for future change.

Organisations learn to trust change when they can see that results are being measured honestly.

The Role of Courage

Creating change from inside the system requires courage.

You may need to question a familiar process, raise an uncomfortable issue, challenge an assumption, or continue advocating after an initial rejection.

But courage does not always look dramatic.

Sometimes courage means asking one careful question in a meeting.

Sometimes it means sharing evidence that others would prefer to ignore.

Sometimes it means listening to criticism and improving the idea.

Sometimes it means continuing after progress becomes slow.

Courage inside a complex organisation is often quiet, patient, and persistent.

Final Thought

Change from inside the system is rarely created through one powerful presentation or one perfect idea.

It happens through understanding, relationships, evidence, timing, experimentation, and trust.

The people who create meaningful internal change are not always the most senior or the loudest.

They are often the people who understand how to connect a good idea with the right people, the right problem, and the right moment.

Complex systems do not change easily.

But they do change.

And often, the most lasting change begins with someone inside the system who sees a better possibility and learns how to move it forward.