Skip to case study
All selected work

Making an enterprise technology strategy understandable across the organization

A large, highly regulated enterprise had a multi-year technology strategy whose initiatives depended on one another. Working within an agency team, I developed the narrative and planning approach that made its logic readable at different levels of detail—without creating a competing version of the strategy.

Client
Fortune 500, highly regulated enterprise (confidential)
Role
Communications strategy, working within the agency team
Focus
Technology transformation narrative and planning

One strategy, many interpretations

The transformation spanned technology, data, customer experience and new ways of working. None of these efforts stood alone; each relied on others to deliver its intended value. Yet leaders, teams and employees encountered the strategy one piece at a time, and at very different levels of detail.

Communicating each initiative separately risked a familiar problem: many accurate explanations that, taken together, described different strategies. The request was for a shared narrative leaders could repeat consistently.

The strategy already existed

The strategy already existed. The challenge was making its logic understandable.

My interpretation of the brief—not a client statement.

That distinction shaped everything that followed. Writing a fresh story would have introduced a second strategy beside the real one. The useful work was to keep the existing logic intact and make its relationships visible.

Reframing the brief

Not the task

  • Create a competing strategy narrative
  • Announce initiatives as separate projects
  • Simplify until the relationships disappear

The communications task

  • Translate the existing strategy
  • Show how each initiative contributes to shared priorities
  • Keep the interdependencies readable at every level
Editorial comparison based on the original brief.

Connecting direction to practical meaning

Within the agency team, I developed a narrative framework that let different audiences enter the strategy at the level they needed, while each level stayed connected to the one above it.

A useful way to understand the approach

  1. Enterprise direction

    What is the strategy for?

    Strategic priorities and intended outcomes, and how the components work together.

  2. Individual initiatives

    Where does this effort fit?

    Each effort’s contribution to those priorities and its relationships to other initiatives.

  3. Practical implications

    What changes for me?

    Relevance to leaders, teams and the way work is carried out.

Anonymized editorial synthesis of the documented approach; not the client’s formal framework.

The planning resources then addressed how the narrative would be carried over time: leadership messaging, sequencing, and support for employee understanding as the transformation progressed.

Work produced

  • Technology strategy narrative framework
  • Initiative-translation approaches
  • Coordinated communications planning resources

Delivered frameworks and planning resources only. No claims of client adoption or measurable business outcomes; the client and its materials remain confidential.