Castson Inc.
ArchiveChapter 01

Disruption Officer

The title was unusual. The mandate was literal.

I was responsible for changing how a global media organization worked — not improving one isolated function from the side.

A marble monolith standing on a frozen lakeshore at dusk
The organization was the system
The role

The mandate had a name.

By then, my work had already crossed marketing, technology, data and client experience.

The boundaries between those disciplines had become the problem.

A better client experience required different systems behind it. New technology could not succeed inside outdated roles. Leaders could not steer the business when reporting arrived late or data remained fragmented.

The organization had changed.

Its operating model had not.

The setting was a global media agency — brand, strategy and analytics converging under one roof. Disruption Officer was the first role that formally brought the whole question together — carried alongside the CEO and CHRO, with the authority to change how the company actually worked.

The method

The organization was the system.

The work moved across leadership, teams, technology, data and delivery.

I began with the people.

How were they doing? Did their roles still make sense? Where were capable people compensating for broken processes? What looked like resistance but was really uncertainty, overload or a loss of trust?

Then the business.

What were we trying to become? What did clients need to experience? Where was the current model creating delay, duplication or ambiguity?

Then the technology.

What should connect? What should disappear? What needed to become visible, automated or rebuilt?

I moved continuously between all three.

People. Business. Technology. Changed together.

The harder work

Technology was rarely the hardest part.

The harder work was helping managers lead differently, enabling teams to work across old boundaries and making change understandable enough that people could participate in it rather than defend themselves from it.

The visible work included executive reporting, data consolidation across platforms, a new project-tracking system, team design, and coaching that ran from line managers to the board.

They were not separate projects.

They were different parts of the same organizational system.

On-time delivery

67% → 98%

Attrition

35% → 18%

The numbers mattered. More important was what they reflected: clearer information, more coherent teams and a more reliable organization.

The pattern

The title ended. The mandate did not.

I still encounter the same underlying pattern: organizations constrained by systems, roles and habits designed for an earlier version of the business.

Sometimes it appears through AI. Sometimes through growth, reporting, marketing, client experience or team structure.

The surface changes. The work underneath remains the same:

Understand the whole system. Find the simpler answer. Help the organization become capable of what comes next.

Why it defines the work

The range is not a market invention.

It was the job.