Strategy as Story: Part 2

Strategy is about telling stories. Good strategy is about telling the ongoing saga of your brand.

This is part two. In part one we introduced the premise and a framework to hang our strategic direction on. Then we got into Mission & Goals (What). This time we’ll be examining the Value Network (Who) and Strategy (How)

Value Network

Who are the primary character in our story? Is there a main protagonist we’ll tell the story (Vision) through? Is there an antagonist?

This last one is tricky. Most strategic visions are rosy pictures of the perfect world our strategy leads us into. Without conflict stories don’t exist. Even Seinfeld, a show about nothing, had conflict. The same is true here. If there is no conflict, noting in the way of success, then there is no need to develop a strategy.

Conflict can come from many places. In the corporate world there’s almost always an aspect that comes from people. Resistance to change from within. Reluctance from customers. Event external pressures from competitors. These antagonist may or may not be referenced in your strategic vision. Recognizing them will help you develop better strategies. We’ll talk more about conflict with strategy. For now lets get back to the Value Network.

Your Value Network is made up of the most impactful roles on success. Notice I said role and not people or jobs. As you start to build your Value Network focus on the roles people play. It’s common for the same person or job title to play multiple roles. By separating the role from the job your strategies will have greater longevity. This will also help to remove potential bias. Tina in sales might be great with social media, but that doesn’t make social media curation a function of sales.

Technically, once you’ve identified the roles and responsibilities of the network, you’re done. Go further. We’re here to talk about the elements of story. Understanding the roles needed is the beginning, not the end. Begin shaping your roles into characters. In business parlance these would be personas. Thinking of personas as characters creates a richer vision. The stronger your vision the easier it is for people to rally around it. But remember, each character has a role to play that moves the story forward. If they don’t, they shouldn’t be there.

Note that I’ve chosen to write this series in a way that indicates a flow. Now throw that notion away. Don’t look at these as a series of steps to be checked off. The truth is you’ll bounce around between Network, Strategy, and Vision. The Mission is the touchstone everything co-develops around. You may even find through the process a need to adjust the Mission. That’s OK, and you should have processes in place to allow that.

I’ll be talking about character and the Value Network in the future. Next we’ll be diving into strategy.

Strategy as Story: Part 1

Strategy is about telling stories. Good strategy is about telling the ongoing saga of your brand.

So how does the structure of story relate to strategy? Let’s first review a framework for developing strategic direction I’ve been using. It comes from an article in the Harvard Business Review written by Michael D. Watkins. It breaks it down into four buckets that are all interrelated. Mission & Goals (What), Value Network (Who), Strategy (How), and Vision & Incentives (Why). Let’s tie this to how we craft a story. The Mission is the theme. The Value Network, are your primary characters. The Strategy is your plot/outline. and the Vision is the story itself. All together these create your strategic vision, or story arc. A story arc can be a part of a larger campaign, and so on.

Mission & Goals

What does it mean when I say this relates to a stories Theme? First, a quick explanation of a stories theme. Many people confuse theme with plot. The theme of A Christmas Carol isn’t that a man is visited by three ghosts and becomes a nice guy. Though change is a valid thematic element of the story.

Let’s try again with our theme. “Even the harshest of men is capable of becoming compassionate.” Hurm…Still too thematic. Like a goal should be actionable and measurable, a theme should be specific and evident in a story. This is the touchstone that everything else ties back to. When in doubt, ask the question am I moving my theme forward. Or, does my strategy move me closer to my goal(s)?

One more time. “When shown the entirety of his life, Ebenezer Scrooge recognizes the pain he’s caused and vows to become the man he should have been.” I don’t know if that’s a good theme for A Christmas Carol, but it suits our needs. It’s specific. We can measure if it’s evident in the story. Relating back to our strategic direction, it provides a focal point for network, strategy and vision.

In practice Mission and Goals are generally handed down, but it’s still important to bare this in mind. I’ve talked before about the strategy fountain. Where the objective of a strategy becomes the goal that drives the next level of strategy. We need to craft our strategic objectives through the lens of theme. This will set the next level of strategy up for success.

Next time we’ll get into the Value Network and Strategy

The Strategy Fountain

Goals and strategies are like a champagne fountain cascading from one tier to the next. The bottle being the top most goal. Your strategies (the champagne) pours from one goal to the next (the bottle and glasses). You take and replace glasses across the tiers of the fountain. You empty one bottle before opening another. There is a finite capacity of how many bottles you can pour from and be effective. Similarly you let a glass fill before taking it and you empty it before filling it again. In some cases when a glass is empty you may set it aside, and replace the spot with a new glass.

While not the perfect metaphor, it invokes a sense of something grandiose, connected, and beautiful when done right. There’s an interconnectedness between all the “goal > strategy > objective > outcome” chains when looked at through an enterprise lens. The goal of one chain may be the objective of a higher chain. The strategies being the connective material.

Should I Stay or Should I Go

A few days ago I wrote about finding inspiration. It got me thinking about goals and when it’s time to change the destination.

If you read the original post, you’ll notice that I didn’t talk about changing the destination or goal. The purpose of applying disruptive thinking to our strategies is not to come up with a new destination. It’s to find a better way to get there. Often times when you hear about companies pivoting in their strategies, you find that they have still remained true to a higher goal. A disruptive idea may lead to new stops and opportunity along the way. These may become smaller micro-goals, but we’re still driving towards the original destination. It’s tempting to chase shinny objects and there is a seductive force to emerging technologies. You need to be realistic about the reasons your chasing it. Is it something your interested in on your own, or does it contribute to the betterment of your goal. If you have passion for an idea follow it, but don’t fall into the trap of forcing something that doesn’t fit. Worse yet is abandoning a solid strategy for personal reasons.

There will be cases when an idea is divergent from the original goal, but valid for the company. Don’t abandon the idea. Flesh it out so you can come back to it later. It may even be worth a minor expedition to learn more. Remember that those larger goals will change in time. The learnings from that divergent thought may become the seed for the next major destination. Never abandon a good idea. Give it care and let it incubate. Learn to know when it’s the right time, place and problem to hatch it.

There can be a fine line between knowing when to pivot in a new direction and when to keep your eye on the prize. A good strategy with measurable outcomes, will provide clarity and insight for making those decisions.

Expand Your Inspiration

“Think outside the box.” You hear it all the time, but what does it mean and how do you go about doing it? The first part of the question is the easy bit. We all know fundamentally that it’s encouraging us to apply new methods to an old problem. However; I want to put a finer point on this for my purposes. Thinking outside the box is about disruptive thinking. To change the status quo and move forward in new ways. Sometimes bold and sometimes subtle, we are changing the course to our destination.

So how do we do that? Where do those disruptive ideas come from? You steal them. No, I don’t mean take someone else’s idea and make it your own. I’m talking about what inspires you. The different paths to inspiration are as diverse as there are people. I’m going to discuss two; 1) following an emerging trend, and 2) adapting another discipline.

The first is the one I see the most. It involves looking at your industry, those related and investigating the emerging trends. Looking at how others solve problems can inspire you to do the same. For example, machine learning (ML) can identify sentiment from facial expressions. Then letting that inspire you to use ML to identify stress factors that broke a part from a photo. I refer to this one as standing on the shoulders of giants (to see further than you can on your own.)

The second is one I don’t see as often and wish I did. I’ve always felt the best inspiration comes from disciplines outside of your own. Using machine learning for facial recognition extended from artificial intelligence. But artificial intelligence was inspired by studying the brain. While the AI case is a direct parallel, your inspirations don’t need to be. You can be inspired from anywhere. Examine the process Monet used to paint his water-lilies. Study the migratory patterns of birds and butterflies. Anything. I encourage this method for many reasons. It can lead to truly new ideas and thinking. It gives you a non-technical metaphor to make communication easier. It can inspire others in new ways that make the idea better. It can reignite your passion for your job. And, by studying other disciplines not your own, you improve yourself.

These are only two paths to inspiration, but they paint a wide canvas and tend to be the two I lean on the most. I often find myself mixing the two. Using external disciplines to find new ways to utilize emerging trends.

Regardless of how or where you find your inspiration, find it. Trust it. Evolve it.

Three Laws

I read an article not too long ago that discussed how everyone is looking for the next Silver Bullet to fix all their problems. “If we just migrate all of our apps to the cloud, we’ll be able to scale as much as we want. Move to the cloud. Deploy to containers. Serverless for the win!” What we don’t talk about is craft. The craft that makes an application scale in the cloud. The craft that ensures your container environment can support your workload. The craft of being cost efficient. And the craft to know the limits of serverless technologies and when not to use them.

Some time ago I developed my own take on the “three laws of robotics” as related to software development. I know it’s been done before, but I like where mine ended up. I’ve had the chance to test these with both developers and product owners and they’ve held up. I’ve even had a product owner surprise me by quoting one of them. Pay close attention to how number three addressing the opening rant.

Three Laws of Development

  1. A developer may not actively jeopardize the long term health of a project, or through inaction, allow the enterprise to come to harm.
  2. A developer must adhere to the user stories created by the product owner, except where such stories would conflict with the First Law.
  3. A developer must further advance the craft of software development as long as such advancement does not conflict with the First or Second Laws.