More Information

On 26 January 1926, exactly 100 years ago, a frail Scottish inventor stood in a small London laboratory and showed the world something it did not yet know how to value.

John Logie Baird was chronically ill, nearly bankrupt, ridiculed by peers, and dismissed by investors. His experiments were built from scrap parts, funded by debt, and sustained by stubborn belief rather than institutional support.

The device he demonstrated — the world’s first public television system — produced a flickering, ghostly image. Poor resolution. Unstable motion. By any modern metric, it looked like failure.

But that blurry screen marked the beginning of one of the most profound shifts in how humans interact.

Baird’s real struggle was not technical. It was systemic. The surrounding ecosystem — markets, infrastructure, regulation, culture — was not yet ready to make sense of what he had built.

Television did not change the world because it was impressive in 1926. It changed the world because multiple systems eventually aligned around it.

Technology improved. Economic feedback loops formed. Social habits evolved. Regulatory frameworks emerged. No master plan existed. The transformation emerged through interaction, delay, resistance, and unintended consequences.

Television collapsed distance, created shared realities, reshaped politics and culture, and fundamentally altered how humans experience the world — for better and for worse.

This is where the story becomes uncomfortable.https://www.youtube.com/watch?v=3CTursi-K0k

Today, individuals and organizations repeat the same mistake Baird’s critics made — judging ideas in isolation while ignoring the systems required for them to succeed.

We ask whether AI is ready. Whether Agile works. Whether culture change delivers ROI. Whether innovation should wait until it is ‘perfect’.

Systems Thinking teaches us a harder truth: most transformations fail not because the idea is flawed, but because the surrounding system resists it.

So how do we avoid this trap?

First, shift the question.

Instead of asking, “Does this idea work?”, ask: “What must change around this idea for it to work?”

This reframes innovation from evaluation to system design.

Second, map the system — not the solution.

Before scaling any initiative, identify the reinforcing and balancing forces at play: incentives, power structures, habits, fears, metrics, and informal norms. Resistance is data, not defiance.

Third, design for co-evolution, not rollout.

Expect technology, behaviour, policy, and capability to mature at different speeds. Sequence change accordingly. Forcing alignment too early creates backlash; waiting for perfection guarantees stagnation.

Early-stage ideas always look fragile. Create safe-to-fail spaces where imperfect experiments can survive long enough for learning loops to form. Kill noise quickly — not novelty.

Fourth, measure system health, not just outcomes.

Track leading indicators: quality of dialogue, trust levels, decision latency, cross-boundary collaboration. Lagging indicators alone tell you what broke, not what is breaking.

For individuals, this means resisting the urge to seek certainty before acting. Influence the system you are in — conversations, incentives, assumptions — even when authority is limited.

For organizations, this means treating transformation as continuous system shaping, not a time-bound programme with a start and end date.

A final provocation
If your organization keeps “fixing” the same problems year after year, the issue is not capability, commitment, or effort.

It is organizational blindness.

Wicked problems survive because they are designed into the system, reinforced by structures, incentives, and unchallenged assumptions. More meetings, smarter people, and better tools will not solve them.

Systems Thinking changes the game by making the invisible visible.

This is the work I do with leaders and organizations: helping them see the feedback loops they are trapped in, identify real leverage points, and intervene where change actually sticks, not cosmetically, but systemically.

If you are serious about moving beyond symptom-fixing and ready to confront what your system is quietly producing, then let’s talk. Contact me directly for a non-obligatory discussion on how I can help you and your organization to use systems thinking to solve wicked problems.