It’s that time of year. The summer sun is beating down harder than ever. The grass is fading from green to brown, and no amount of watering seems to be enough. School supply lists hit your Inbox as Back to School sales fill your mailbox.
Yep, it’s almost Strategic Planning & Budgeting season.
You’ve been through this before, so you know what a strategy is (a set of choices and actions to get you closer to your long-term goals). You know why you need one (set common goals, create shared understanding and responsibility, align key stakeholders, inform priorities and decisions, enable your team to be proactive).
But do you know how to create a strategy that gets used?
No, I’m not talking about a process (though that is important). I’m talking about the experience you create and the expectations you maintain for your team as you develop the strategy.
Earlier this week, a client and I talked about this. We were preparing for a strategic planning offsite, one that we vowed would be different from previous strategic planning efforts that were somewhat successful (a new idea was launched and has since become an essential part of the organization) but left the team with lingering frustration about the process and skepticism about this one.
As we shared our thoughts and I scribbled notes, themes emerged. The next day after the themes were presented to the nearly 50 people in attendance, the head of the group raised his hand. “You’ve just described the I Love Lucy approach to strategy.”
Now, I love a good pop culture reference, especially one that requires a bit of history. But I did not get this one. As I scrunched my face in confusion, he explained, “It’s Ay yi yi yi yi!”
And thus, the I Love Lucy approach to strategy was born.
If you want to create a successful strategy, one that gets you closer to your long-term goals despite an uncertain and changing environment, how you create it must be:
Inclusive: Use the IKEA effect to your advantage and give everyone in your organization a voice. Different voices bring different perspectives to the process and help you avoid groupthink. Research from BCG indicates that “organizations that engage a broad group of internal and external stakeholders in their strategy development efforts yield better results than organizations that leave strategy in the hands of a small, central team.”
Illuminating: In the same way, it’s easy to ignore the softball-sized dust bunny under the bed until your mom comes to visit, it’s easy to ignore the parts of the business that aren’t broke but aren’t in an ideal state until strategic planning season. Your process needs to shine a light on all the nooks and crannies of your business, revealing all the opportunities and flaws to be addressed.
Innovative: You would never write a strategic plan that makes your business worse, but are you writing one that makes it better? In most cases, and often for very sensible reasons tied to incentives and metrics, teams write strategic plans for steady and safe growth. But there’s no such thing in unsteady and uncertain times. If you’re not thinking about what’s possible, you’re not planning to achieve your long-term objectives.
Internalized: A common entertainment trope is a villain who monologues for so long that the hero can escape. So you know who else monologues? Managers talking about strategy. And yes, everyone is looking to escape. Don’t be the villain, be the hero and create a strategy everyone can remember and repeat.
Implemented: The most useful strategic plan I ever saw was in a binder being used to straighten a wobbly table. It was useful, but not in the way its creators intended. If no one acts on your strategy, you just made a great table leveler.
Bonus Recommendations
For best results, I also recommend chocolate during the process and Vitameatavegamin after (or during but outside of work hours)
What are your recommendations for a good strategy development experience, a successful strategy, or an I Love Lucy marathon? Let me know in the comments below.
What if a tool had the power to delight your customers, cut your costs, increase your bottom line, and maybe double your stock price? You’d use it, right?
That’s precisely the power and impact of Service Design and service blueprints. Yet very few people, especially in the US, know, understand, or use them. Including me.
Thankfully, Leala Abbott, a strategist and researcher at the intersection of experience, innovation, and digital transformation and a lecturer at Parsons School of Design, clued me in.
What is Service Design?
RB: Hi, Leala, thanks for taking the time to talk with me today.
LA: My pleasure! I’m excited about this topic. I’ve managed teams with service designers, and I’ve always been impressed by the magical way they brought together experience strategy, UX, and operations.
RB: I felt the same way after you explained it to me. Before we get too geeked up about the topic, let’s go back to the beginning and define “service.”
LA:Service is something that helps someone accomplish a goal. As a result, every business needs service design because every business is in the service industry.
RB: I’ll be honest, I got a little agitated when I read that because that’s how I define “solution.” But then I saw your illustration explaining that service design moves us from seeing and problem-solving isolated moments to seeing an integrated process. And that’s when it clicked.
LA: That illustration is from Lou Downe’s talk Design in Government Impact for All . Service Design helps us identify what customers want and how to deliver those services effectively by bringing together all the pieces within the organization. It moves us away from fragmented experiences created by different departments and teams within the same company to an integrated process that enables customers to achieve their goals.
Why You Need It
RB: It seems so obvious when you say it. Yet so often, the innovation team spends all their time focused on the customer only to develop the perfect solution that, when they toss it over the wall for colleagues to make, they’re told it’s not possible, and everything stops. Why aren’t we always considering both sides?
LA: One reason, I think, is people don’t want to add one more person to the team. Over the past two decades, the number of individuals required to build something has grown exponentially. It used to be that one person could build your whole website, but now you need user experience designers, researchers, product managers, and more. I think it’s just overwhelming for people to add another individual to the mix. We believe we have all the tools to fix the problem, so we don’t want to add another voice, even if that voice explains the huge disconnect between everything built and their operational failures.
RB: Speaking of operational failures, one of the most surprising things about Service Design is that it almost always results in cost savings. That’s not something most people think about when they hear “design.”
LA: The significant impact on the bottom line is one of the most persuasive aspects of service design. It shifts the focus from pretty pictures to the actual cost implications. Bringing in the operational side of the business is crucial. Building a great customer journey and experience is important, but it’s also important to tie it back to lost revenue and increased cost to serve
Proof It Works
LA: One of the most compelling cases I recently read was about Autodesk’s transition to SaaS, they brought in a service design company called Future Proof. Autodesk wanted to transition from a software licensing model to a software-as-a-service model. It’s a significant transition not just in terms of the business model and pricing but also in how it affects customers.
If you’re a customer of Autodesk, you used to pay a one-time fee for your software, but now you are paying based on users and services. Budgeting becomes messy. The costs are no longer simple and predictable. Plus, it raises lots of questions about the transition, cost predictability, control over access, managing subscriptions, and flexibility. Notice that these issues are about people managing their money and increasing costs. These are the areas where service design can truly help.
Future Proof conducted customer interviews, analyzed each stage of the customer journey, looked at pricing models and renewal protocols, and performed usability studies. When they audited support ticket data for the top five common customer issues, they realized that if Autodesk didn’t change their model, the cost of running software for every customer would increase by 40%, and profit margins would decrease by 15% to 20%.
Autodesk made the change, revenue increased significantly, and their stock price doubled. Service design allows for this kind of analysis and consideration of operational costs.
How to Learn More
RB: Wow, not many things can deliver better service, happier customers, and doubling a stock price. Solid proof that companies, and innovation teams in particular, need to get smart on service design. We’ve talked a lot about the What and Why of Service Design. How can people learn more about the How?
Several years ago, my now-husband and I were in London. It was his first time in the city but my 4th or 5th so, naturally, I talked a big game about how well I knew the city and how I would be, with the help of our handy tourist map, our tour guide.
Things were going fine until I took the wrong road leading away from Buckingham Palace. I thought we were heading straight to Parliament. We were not.
After a walk that lasted far longer than it should have, he nervously asked,” We’re lost, aren’t we?”
With wounded pride and astounding stubbornness, I declared, “We’re not lost. I know exactly where we are. It’s just not where we want to be.”
Maps are incredibly useful. Until they’re not.
Innovation literature has more maps than a Rick Steves’ guidebook, and most are quite useful. If they’re used at the right time for the right purposes in the right way by the right people (which is a lot of rights that have to be right).
Here are three of my favorites – 2 classics and a new one that blew my mind
Stakeholder Map:
Avoid getting blind-sided, buttering up the wrong people, or ignoring potential champions
What it is: A visual representation of the people, roles, and groups who (1) are involved in and affected by a challenge or system and (2) have the power to affect or are likely to be affected by the proposed solution. Stakeholders can be internal and/or external to the organization
Why you need one: To prioritize where and how you spend your time understanding, influencing, communicating, collaborating, persuading, and selling
When to create it: At the very beginning of a project and then updating as you learn more
Brainstorm who your internal AND external stakeholders are
Prioritize them using an Influence x Interest two-by-two matrix
Engage and communicate based on their place in the chart
Journey Map
Spot opportunities to create radical value through incremental innovations
What it is: A visual representation of what your customer/consumer/user does, thinks, and feels as they move from awareness of a need/want/JTBD to loyalty to a solution. Journey maps should dig deep into moments where customers currently interact with your organization and highlight opportunities where interaction can and should occur
Why you need one: To identify opportunities for innovation by surfacing customer current pain points between your customer and your business (or competitors if your business isn’t there and can/should be)
When to create it:
Create the basic structure (start and end point) or a hypothesized journey before primary research.
During research, work with individual stakeholders to develop their maps using (and adapting) your initial structure.
At the end of research and before ideation, synthesize insights into the smallest possible number of maps to use as inspiration for solution brainstorming
How to use it: IDEO offers simple instructions and tips based on practical use:
Brainstorm who your internal AND external stakeholders are
Prioritize them using an Influence x Interest two-by-two matrix
Engage and communicate based on their place in the chart
Service Map
Make journey maps actionable (and see how your innovation affects your operations)
What it is: A visual representation of the people, touchpoints, processes, and technology required/desired both frontstage (what customers see) and backstage (what happens behind the scenes). Similar to process documentation with a special focus on the customer
Why you need one: Doing something new (i.e., innovating) often requires changes to internal operations, organizations, and processes, but these changes are often ignored or unexplored until late in the process, potentially slowing or stopping the development and launch of a new solution.
When to create it: Draft a baseline current state once you have 50% confidence in the general area or type of solution to be created (e.g., we want to improve the use of digital tools in classrooms, so let’s create a service map for our current digital offerings and operations). Then continually revise and update it as the solution/service develops.
You are a leader, an innovator, and an optimist. You see what’s possible, and you sell people on your vision, encouraging them to come on the journey of discovery with you. You’re making progress, getting things done until *WHAM* you run right into that one person. You know who I’m talking about.
Dr. No.
Sometimes you see them coming because they’re from Legal, Regulatory, Finance, or another function that has the reputation of being a perpetual killjoy.
Sometimes you hear them coming:
“Why are we doing this? Don’t we have enough to do?”
“We tried this in 19XX. It didn’t work then, and it won’t work now.”
“I don’t have time for this. I have real work to do.”
Sometimes they sneak up on you, privately supporting your efforts only to undermine your efforts publicly.
But they’re always there. Waiting for the opportunity to not just rain on your parade but to unleash a category 5 Hurricane of obstacles, barriers, and flat-out refusals on your innovation efforts.
This is precisely why Dr. No is among the first people to invite to the parade.
Why You Need to Say Yes to Dr. No
Let’s be honest, no one wants to do this. At best, Dr. No’s negativity and smug predictions of inevitable failure are downers, dampening and discouraging the culture of questioning, experimentation, and learning you’re trying to create. At worst, it can feel like working with a saboteur hell-bent on doing the “I told You So” dance atop the ruins of your innovation team.
But just like eating your vegetables, you need to do it because it will make you and your innovation efforts healthier, stronger, and more likely to live longer.
How to Say Yes to Dr. No
Step 1: Be Human. Together.
As with many things in life, the first step is changing how you think and behave. Naturally, you have feelings, perceptions, and even predictions about Dr. No and their likely behavior. Set them aside. Not because they’re incorrect but because you can’t move forward if you’re standing in a hole.
So, start with what you have in common – Dr. No is a human being, just like you.
Like other human beings, Dr. No needs to feel connected and accepted. When they don’t feel connected and accepted, they will feel defensive and under attack and respond by taking steps to protect themselves and their jobs. But when they connect and feel accepted, you have the foundation for psychological safety.
To establish a connection and foster a feeling of acceptance, try:
Acknowledging the importance of the job they’re doing and its impact on the business
Asking questions to understand better how they think and what they prioritize
Building a rapport by sharing some of your aspirations and concerns and asking about theirs
Step 2: Invite Them on the Journey
People love what they create. It’s the only way to explain why people have outsized attachments to IKEA furniture, distorted art projects, and failed products.
Invite Dr. No to be part of the creation process. Don’t tell them they’re part of it, that’s the business version of kidnapping, and no one likes being kidnapped.
Instead, express your desire for them to be involved because you value their perspective. Ask them how and when they want to be involved. Share how you want them to be involved. Then work together to find a solution that works for both of you. Stay open to experimenting and changing how and when involvement happens. Make this a learning process for both of you as you work to do what’s best for the business.
Step 3: Stay curious
One of the most valuable lessons from Ted Lasso (and not Walt Whitman) is the importance of being curious, not judgmental.
As you do the work of innovation, there will be times when Dr. No lives up (or down) to their name. No matter how much time you invested in your relationship, how much psychological safety you built, or how involved they were in the process, they will still say No.
If you are judgmental, that No is the end of the conversation. If you’re curious, it’s the start.
So, get curious and ask,
What causes you to say that? (probe on what they see, think, and feel)
Have you seen something like this before? What was the context? What happened?
What do you need to see to say Yes?
Engage them in solving the problem with you rather than defending themselves against you.
Can Dr. No become Dr. Yes?
Maybe.
I’ve seen it happen, even to the point that Dr. No became the team’s loudest champion.
I’ve also seen it not happen. But even then, the No is less harsh, devastating, and final.
You won’t know until you try. Certainly, you won’t say no to that.
When my niece was 4 years old, she looked at her mom (my sister) and said, “I can’t wait until I’m an adult so I can be in charge and make all the decisions.” My sister laughed and laughed.
Being in charge looks glamorous from the outside, but it is challenging, painful, and sometimes soul-wrenching. Never is this truer than when you must make a tough decision and don’t have all the data you want or need.
But lately, I’ve noticed more and more executives defer making decisions. They’ll say they want more data, to hear what another executive thinks, or are nervous that we’re rushing to decide.
This deferral is a HUGE problem because making decisions is literally their job! After all, as Norman Schwarzkopf wrote in his autobiography, “When placed in command, take charge.”
When you decide, you lose
A decision is “a choice that you make about something after thinking about several possibilities.” Seems innocent enough, right? Coke or Pepsi. Paper or plastic. Ariana Madix or Raquel Leviss (if you don’t know about this one, consider yourself lucky. If you choose to know about it, click here).
The problem with making decisions is that loss is unavoidable. Heck, the word “decide” comes from the Latin roots “de,” meaning off, and “caedre,” meaning cut. When you choose Coke, paper bags, or Ariana, you are cutting off the opportunity to drink Pepsi with that meal, use a plastic bag to carry your purchases or support Rachel in a pointless pop culture debate.
Decisions get more challenging as the stakes get higher because the fear of loss skyrockets. Loss aversion, a cognitive bias describing why the psychological pain of loss is twice as acute as the pleasure of gain, is common in cognitive psychology, decision theory, and behavioral economics. You see this bias in action when someone refuses to ask questions or challenge the status quo, to take a good deal because it’s below their initial baseline, or to sell an asset (like a house) for less than they paid for it.
No decision is the worst decision
Deciding not to decide is often the worst decision of all. Because it feels like you’re avoiding loss and increasing your odds of making the right decision by gathering more data and input, it’s easy to forget that you’re losing time, employee engagement and morale, and potential revenue and profit.
When you decide not to decide, progress slows or even stops. No decision gives your competition time to catch up or even pass you. Your team gets frustrated, morale drops, and people search for other opportunities to progress and have an impact. The date of the first revenue slips further into the future, slowly becoming just a theoretical number in a spreadsheet.
Decide how to decide
In a VUCA world, a perfect, risk-free decision that offers only upside does not exist. If it did, the business wouldn’t need an executive with your experience, intellect, and courage. Yet here you are.
It’s your job to make decisions.
Make that job easier by deciding how to decide
Tell people what you need to see to say Yes. “I’ll know it when I see it” is one of the biggest management cop-outs ever. If you don’t know what you want, don’t waste money and time requiring your team to become mind readers. But you probably know what you want. You’re just afraid of being wrong. Instead of allowing your fear to fuel inefficiency, tell the team what you need or want to see and that, as they make progress, that request might change. Then set regular check-ins so that if/when it happens, it happens quickly and is communicated clearly.
Break big decisions down into little decisions. I once worked with a team that had an idea for a new product. They planned to pitch to the executive committee and request 3 million dollars to develop and launch the idea. After some coaxing, we decided to avoid that disaster and brainstormed everything that needed to be true to make the idea work. We devised a plan to test the three assumptions that, if we were wrong, would instantly kill the idea. When we pitched to the executive committee, we received an immediate Yes.
Present options and implications. As anyone with a toddler knows, you don’t ask yes or no questions. You give them options – do you want to wear the yellow or pink shirt? If they pick something else, like their Batman costume, you explain the implications of that decision and why the options previously presented are better. Sometimes they pick the yellow shirt. Sometimes they pick the Batman costume. You could force them to make the right decision, but no one wins. (Yes, I just compared managers to toddlers. Prove me wrong).
It’s your decision
Being in charge requires making decisions. When you decide, you lose the option (maybe temporarily, maybe forever) to pursue a different path. But you can’t be afraid to do it.
After all, “Sometimes you win, sometimes you lose, sometimes it rains.”
As the world around you becomes more volatile, uncertain, complex, and ambiguous (VUCA), you know that you need to build skills to navigate it and inspire others to follow your path.
But what if you are the source of ambiguity?
Because you are. Every time you speak.
The words we use always have clear meaning and intent to us but may not (and often don’t) have the same meaning and intent to others.
That’s why one of the first and most essential things a company can do when starting its innovation journey is to decide what “innovation” means. It may seem like an academic exercise, but it becomes very practical when you discover that one person thinks it means something new to the world, another thinks it’s a new product, and a third thinks it means anything commercialized.
Ambiguity = Efficiency?
“Innovation” isn’t the only word that is distractingly ambiguous. Language, in general, evolved to be ambiguous because ambiguity makes it more efficient. In 2012, cognitive scientists at MIT found the ambiguity–efficiency link, noting “words with fewer syllables and easier pronunciation can be ‘reused,’ avoiding the need for a vast and increasingly complex vocabulary.”
You read that right. In language, ambiguity leads to efficiency.
Every time you speak, you’re ambiguous. You’re also efficient.
The RIGHT level of Ambiguity = Efficiency!
In 2014, researchers at Pompeu Fabra University in Barcelona found that language’s ambiguity is critical to communicating complex ideas,
“the researchers argue that the level of ambiguity we have in language is at just the right level to make it easy to speak and be understood. If every single object and concept had its own unique word, then language is completely unambiguous – but the vocabulary is huge. The listener doesn’t have to do any guessing about what the speaker is saying, but the speaker has to say a lot. For example, “Come here” might have to be something like “I want you to come to where I am standing.” At the other extreme, if the same word is used for everything, that makes it easy for the speaker, but the listener can’t tell if she is being told about the weather or a rampaging bear.”
.
Either way, communication is hard. But Sole and Seoane argue that with just the right amount of ambiguity, the two can find a good trade-off.”
A certain level of ambiguity is efficient. Too much or too little is inefficient.
How to find the RIGHT level of Ambiguity for “Innovation”
In everyday life, it’s ok for everyone to have a slightly different definition of innovation because we all generally agree it means “something new.” Sure, there will be differences of opinion on some things (is a new car an “innovation” if it just improved on the previous model?). Still, overall, we can exist in this world and interact with each other despite, or maybe because of, the ambiguity.
Work is a different story. If you are responsible for, working on, or even associated with innovation, you better be very clear on what “innovation” means because its definition determines expectations and success for what you do. If it means one thing to you and a different thing to your boss, and a third thing to her boss, you’re in for a world of disappointment and pain.
Let’s avoid that. Instead:
Define the word
Get everyone to agree on the definition
Use the word and immediately follow it with, “And by that, I mean (definition)”
Gently correct people when they use the word to mean something other than the agreed-upon definition. Once everyone uses the word correctly, you can stop defining it every time because its meaning has taken root.
So, the next time someone rolls their eyes and comments on the “theoretical” or “academic” (i.e., not at all practical, useful, or actionable) exercise of defining innovation, smile and explain that this is an exercise in efficiency.
