The Hidden Cost of Strategic Planning Built on a Single Future

by Braden Kelley and Art Inteligencia

Nobody puts a line item in the budget for “cost of assuming we knew what was going to happen.” And yet, if you looked honestly at what a single-scenario strategic plan actually costs an organization when the future doesn’t cooperate, it would be one of the largest hidden expenses on the books. It just never gets counted, because it’s spread across a dozen decisions that never get traced back to the plan that caused them.

The cost of defending a plan past its expiration date

Once a strategic plan is approved, it develops a kind of institutional gravity. Budgets are allocated against it. Teams are staffed against it. Leaders have put their names on it in front of the board. When early signals suggest the assumed future isn’t materializing quite the way the plan predicted, the natural organizational instinct isn’t to update the plan — it’s to defend it, because updating it can feel like admitting the original thinking was wrong. I’ve watched organizations spend months, and real budget, propping up a strategy that the market had already started to move past, simply because nobody wanted to be the one to say so first.

The cost of the resources you didn’t allocate to what was actually happening

This is the harder cost to see, because it’s a cost of omission rather than a line item you can point to. Every dollar and every hour committed to executing a single assumed future is a dollar and an hour not available to the future that was actually starting to emerge in the market signals your team either didn’t collect or didn’t take seriously. You don’t see this cost in a budget review. You see it eighteen months later, when a competitor who built in flexibility is suddenly in a category you didn’t think was coming yet.

The cost of strategic surprise

There’s a specific, expensive kind of organizational chaos that happens when a shift arrives that the strategic plan gave leadership no framework for anticipating. It’s not just the scramble to react — it’s the credibility cost inside the organization when leadership is visibly caught off guard by something that, in hindsight, had been signaling for a year. Teams notice. Boards notice. The plan’s failure to hold more than one possible future becomes a trust problem, not just a strategy problem.

The cost of decision paralysis when the single future finally, visibly breaks

Counterintuitively, some of the most expensive moments I’ve seen come after a single-scenario plan visibly stops working. Leadership, having built no muscle for holding multiple futures at once, doesn’t know how to respond except by freezing — commissioning study after study, delaying decisions that can’t actually wait, because the organization has no established process for reasoning under genuine uncertainty. A team that’s practiced foresight moves faster in exactly this moment, not slower, because they’ve already done the work of imagining more than one path.

Why the fix isn’t more analysis — it’s a different structure

None of this means the answer is spending more time forecasting, or hiring more analysts to build a more detailed single prediction. A more detailed wrong future is still wrong. What actually closes this gap is a structured way of holding multiple possible futures at once — genuinely mapping from the real signals in your market, to the trends they suggest, to a real set of possible futures, then identifying which one is most probable while still building a deliberate path toward the future you’d actually prefer. That’s the specific gap FutureHacking™ was built to close — a structured, visual, collaborative methodology any leadership team can run, without needing to build an internal foresight department first. FutureHacking™ is the art and science of getting to the future first, and the organizations that practice it don’t avoid uncertainty — they get better at moving through it faster than everyone still defending last year’s single-scenario plan.

Where to start

If your team has never run a structured foresight exercise, the free FutureHacking Signal Picker is the fastest way to find out what it feels like — it walks you through identifying and prioritizing the real signals worth watching, at no cost, and it’s the foundational first step of the whole methodology.

Something new I’m building

I’m also finishing a second tool — the FutureCanvas Picker — that carries you further into the full arc: from signals, to the trends they suggest, to a genuine set of possible futures, narrowing to your most probable future, and then mapping the path toward the future you’d actually prefer to build. It’s the fastest, clearest way I’ve built yet to feel the full power of FutureHacking™ in a single sitting.

I’m opening early access to a select group first — strategic planners, CSOs, and leaders actively running planning processes right now — because I want real feedback from people doing this work under real deadline pressure before it’s available more broadly. If that’s you, and you’d like to be considered for early access, reach out and let me know — I’ll be following up personally with the first few who get in.

The organizations that get to the future first aren’t the ones who guessed correctly. They’re the ones who stopped betting everything on a single guess.

Image Credits: Gemini

Content Authenticity Statement: The topic area, key elements to focus on, etc. were decisions made by Braden Kelley, with a little help from Claude to clean up the article.

Sign up here to get Human-Centered Change & Innovation Weekly delivered to your inbox every week.

Merging Two Customer Experiences After M&A

Leave a reply

Where to Start

Merging Two Customer Experiences After M&A

by Braden Kelley and Art Inteligencia

Every M&A announcement talks about synergies, market position, and combined capabilities. Almost none of them talk about the fact that, on day one, you now have two customer bases who each learned to expect something different from the companies they chose — and neither of them signed up for the other company’s version of the relationship.

The assumption that quietly sinks post-merger CX

The default assumption in most integrations is that the better-resourced or larger company’s experience simply becomes the standard, and the other customer base adjusts. I’ve watched this assumption cost companies real customers, because it skips a step that matters enormously: nobody has actually compared the two experiences at the touchpoint level to know which one is genuinely better, versus just louder or more familiar to the leadership team making the call.

Two journeys, two sets of expectations, one deadline

Integration timelines are usually set by finance and legal milestones — closing conditions, systems cutover dates, reporting deadlines — not by how long it actually takes to understand two customer journeys well enough to merge them intelligently. That mismatch is where the damage happens. Support processes get unified before anyone’s mapped where they genuinely differ. Pricing and billing experiences get standardized before anyone’s identified which parts of each were actually working. By the time customer complaints start flagging the problems, the systems decisions are already locked in, and unwinding them costs far more than getting it right the first time would have.

Start by mapping both journeys independently, before merging anything

The instinct in an integration is to move fast toward one unified experience, because ambiguity feels risky to the deal’s momentum. I’d argue the opposite is true here: the riskiest move is unifying before you understand what you’re unifying. Mapping both customer journeys independently — validated personas, current-state touchpoints, the data each company has been collecting, and, critically, walking both journeys firsthand rather than trusting either side’s internal narrative about how good their own experience is — gives you an honest picture before any integration decision gets made instead of after.

Whose employees explain the friction matters as much as whose customers report it

In an acquisition especially, frontline employees from the acquired company often sit on institutional knowledge about their customers’ real pain points and workarounds that never made it into any deck during diligence. They also, often, feel like their side of the business is being absorbed rather than genuinely evaluated — which makes them less likely to volunteer that knowledge unless someone specifically goes looking for it. An audit that treats both organizations’ frontline teams as equally credible sources, rather than defaulting to whichever side is running the integration, tends to surface friction neither leadership team knew existed.

Benchmark both experiences against the market, not against each other

The other trap is treating this purely as an internal comparison — which company’s process wins. The more useful question is how each one stacks up against what customers in the combined market now expect, especially if the merger changes your competitive position or brings you into contact with a new set of competitors either customer base is now implicitly being compared against.

What this actually buys you

Getting this right doesn’t just avoid a bad integration story — it turns the merger into a genuine opportunity to build a better combined experience than either company had running independently, using the best of what each side was actually doing well. That’s a very different outcome than the default of one side’s process quietly winning by default and both customer bases losing something in the process.

If you’re heading into an integration and want an independent, evidence-based read on both customer experiences before any systems or process decisions get locked in, a Customer Experience Audit scoped to both organizations is exactly the kind of diagnostic this moment calls for. And if you want a rough sense of what experience misalignment could cost during an integration before you scope that engagement, the CX ROI Calculator is a fast place to start.

Download the Customer Experience Audit Checklist as a PDF

Image Credits: Pexels

Content Authenticity Statement: The topic area, key elements to focus on, etc. were decisions made by Braden Kelley, with a little help from Claude to clean up the article.

Sign up here to get Human-Centered Change & Innovation Weekly delivered to your inbox every week.

What’s Your Learning Objective?

Leave a reply

What's Your Learning Objective?

GUEST POST from Mike Shipulski

Innovation is all about learning. And if the objective of innovation is learning, why not start with learning objectives?

Here’s a recipe for learning: define what you want to learn, figure how you want to learn, define what you’ll measure, work the learning plan, define what you learned and repeat.

With innovation, the learning is usually around what customers/users want, what new things (or processes) must be created to satisfy their needs and how to deliver the useful novelty to them. Seems pretty straightforward, until you realize the three elements interact vigorously. Customers’ wants change after you show them the new things you created. The constraints around how you can deliver the useful novelty (new product or service) limit the novelty you can create. And if the customers don’t like the novelty you can create, well, don’t bother delivering it because they won’t buy it.

And that’s why it’s almost impossible to develop a formal innovation process with a firm sequence of operations. Turns out, in reality the actual process looks more like a fur ball than a flow chart. With incomplete knowledge of the customer, you’ve got to define the target customer, knowing full-well you don’t have it right. And at the same time, and, again, with incomplete knowledge, you’ve got to assume you understand their problems and figure out how to solve them. And at the same time, you’ve got to understand the limitations of the commercialization engine and decide which parts can be reused and which parts must be blown up and replaced with something new. All three explore their domains like the proverbial drunken sailor, bumping into lampposts, tripping over curbs and stumbling over each other. And with each iteration, they become less drunk.

If you create an innovation process that defines all the if-then statements, it’s too complicated to be useful. And, because the IF-THENs are rearward-looking, they don’t apply the current project because every innovation project is different. (If it’s the same as last time, it’s not innovation.) And if you step up the ladder of abstraction and write the process at a high level, the process steps are vague, poorly-defined and less than useful. What’s a drunken sailor to do?

Define the learning objectives, define the learning plan, define what you’ll measure, execute the learning plan, define what you learned and repeat.

When the objective is learning, start with the learning objectives.

Image credits: Pexels

Sign up here to join 17,000+ leaders getting Human-Centered Change & Innovation Weekly delivered to their inbox every week.

Why Going Above and Beyond Doesn’t Work

Leave a reply

Why Going Above and Beyond Doesn't Work

GUEST POST from Shep Hyken

This article answers the question: Should organizations aim to go above and beyond in every interaction, or focus on consistently meeting customer expectations?

This is a story about a disagreement I had with a client. I should mention, this was a friendly disagreement. His idea of an amazing experience was to go above and beyond, always exceeding the customer’s expectations.

His company is the one you call when a disaster, such as a flood, tornado, or fire, hits your home or office. The company specializes in cleanup and restoration. The owner believed it was important to go above and beyond in every interaction. So, I asked him for an example.

He said that when a customer calls – day or night, 365 days a year – someone will be there, and an emergency team will be dispatched immediately.

As nicely as I could, I told him that what he described was not an above-and-beyond example. No, what he described was what every customer expected. While the customer may be elated with how quickly the company responds to their emergency, that’s what his company is supposed to do.

Above and beyond experiences are reserved for unexpected moments. Not long ago, I wrote about the story Steve Wynn, the chairman of Wynn Resorts, a group of hotels and casinos, shared about how an employee helped a guest get medicine she had left at home. That was truly an above-and-beyond example.

It doesn’t always have to be something big.

However, it doesn’t always have to be something big. For example, the surprise piece of cake with a candle the server at a restaurant brings to the table, not because someone told him it was a guest’s birthday, but simply because he overheard the patrons talking about the birthday. He took advantage of that information and created the surprise-and-delight moment, another version of above-and-beyond.

But you can’t count on emergencies and birthdays to happen every time. You can take advantage of those moments when you know they’re coming, but if every day, in every interaction, you focus on giving the customer your best effort to meet, and even slightly exceed, their expectations, you’re operating in the zone of amazement.

Going above and beyond should never be the goal for every interaction. It’s not sustainable, and it’s definitely not a realistic goal. What is realistic is delivering consistent and predictable experiences that meet expectations every time and occasionally rise just a bit above them. The point is, customers don’t demand fireworks unless that’s the kind of experience you sell. What they want is reliability, ease, and empathy. When those are in place, the occasional above-and-beyond or surprise-and-delight moments become icing on the cake, not the foundation of your service. Do what customers expect, every time, and you’ll amaze them with your consistency. That’s what builds trust, loyalty, and the kind of reputation that gets customers to say, “I’ll be back.”

Image Credits: Pexels

Sign up here to join 17,000+ leaders getting Human-Centered Change & Innovation Weekly delivered to their inbox every week.

Why Do People Resist Change?

Leave a reply

Why Do People Resist Change?

by Braden Kelley and Art Inteligencia

Why Do People Resist Change? (Short Answer)

People resist change when the new way costs them more than it returns — in effort, status, safety, time, or trust — or when they cannot see how to succeed at it. Much of what leaders call resistance is a rational response to the design of the change. Fear is sometimes part of the story. It is rarely the whole story.

Resistance is information. It tells you where the change asks people to lose something you have not replaced.

Below you’ll find what resistance actually signals, the reasons it shows up, how to tell design failure from unwillingness, and what to do before you diagnose someone’s character. Change management exists to achieve objectives in people’s behavior — see What Is Change Management? — and resistance is one of the clearest signals that those activities are missing or misaimed.

What Is Resistance to Change, Really?

Resistance is what people do when a proposed change threatens something they rely on and the replacement is unclear, unfair, or unworkable. It shows up as questions, workarounds, silence, delay, and sometimes open pushback.

Silence is easy to misread as agreement. In most transformations, the real objections travel in hallways because honesty has had a cost before. Those quiet questions — about jobs, power, time, metrics, and whether this effort is real — are catalogued in 10 Questions Employees Quietly Ask During Every Transformation.

Treat the signal as data about the change. People are telling you where the new way fails a basic test: Can I succeed at this, and is it worth what I give up?

What Are the Main Reasons People Resist Change?

They cannot see themselves succeeding.
The future state is described in slogans. The skills, the first week, and what “good” looks like for their role stay vague. Uncertainty reads as risk, so people stay with the work they already know how to do.
They lose status, identity, or control.
Expertise that took years to build can become less valuable overnight. A new system can move decisions away from the people who used to make them. That loss is concrete. Calling it “mindset” does not replace what was taken.
The new way adds work and nothing stops.
Another process, another tool, another meeting, stacked on the current job. If leaders cannot name what people will stop doing, the change is an extra load. People protect their capacity by dragging their feet.
The old scorecard still pays.
Promotions, bonuses, and manager praise still follow the behavior the change is supposed to replace. People follow the metric that affects their livelihood. They are responding to the system you still run.
There is no time to practice.
Training is scheduled. Practice on real work is not. People are asked to perform the new way in front of customers or leaders before they have been allowed to be clumsy at it. Avoidance is how they protect quality and reputation.
Trust has already been spent.
Earlier initiatives launched, faded, and left the extra work behind. People wait for proof that this one will change tools, decisions, and consequences — not only the branding. Belief returns when receipts show up in the work.
The change itself is hard to use.
Broken handoffs, missing authority, bad data, and tools that make the job slower produce “resistance” that is really feedback. The people closest to the work are often the first to discover that the design does not survive contact with a real day.

How Do You Tell a Design Problem from Unwillingness?

Ask where the friction sits before you decide who is “on board.”

If the same pushback shows up across teams that do not share a personality, look at the design: the job, the metric, the tool, the time, the loss.
If people can explain the change and still cannot do it on a normal day, you have an enablement gap, not a communications gap.
If a few people resist after the path is workable, the loss is named, practice is funded, and the old incentive is gone, then you are dealing with individual choice. That is a smaller group than most steering committees assume.

Leaders still reach for the shorter story: resistance means the people are the problem. That story feels efficient and skips the redesign. I treat it as one of the myths that keep showing up in 8 Change Myths Leaders Still Believe in 2026.

Diagnose the work before you diagnose the person.

How Do You Respond to Resistance to Change?

Ask what they stand to lose, and answer in specifics: role, status, workload, and what happens if they speak up.
Publish a stop list alongside the start list. If nothing stops, the change is additional work.
Align one metric that still rewards the old behavior. People will not abandon a scoreboard that still decides their review.
Fund practice on real work, with coaching, before you judge performance in the new way.
Give sponsors levers, not only airtime: decision rights, staffing, and the authority to remove the old path.
Fix the design people are tripping over — handoffs, permissions, data, tools — and say what you changed because they told you.

For how those activities sit inside a full change effort — planning, leadership, management, maintenance, and portfolio — see 5 Steps of Human-Centered Change That Survive Reality.

People move when the new way is safer and more workable than the old one. Make that true, then ask for commitment.

Ready to Take the Next Step?

Resistance gets quieter when people can see the whole change, name what they will stop, and practice the new way with sponsors who can actually change the work. That is a planning problem you can take on directly.

See the methodology. Explore Human-Centered Change™, my visual, collaborative approach to planning change so the people who must live it can see the whole effort and adopt the new way.

Get the toolkit. Read Charting Change, my practical guide to Human-Centered Change™, built around the Change Planning Canvas™ and 70+ visual tools for getting everyone on the same page.

Listen to the resistance long enough to redesign the change. Then give people a path they can actually walk.

FAQ: Why People Resist Change

Why do people resist change?

People resist change when the new way costs them more than it returns, in effort, status, safety, time, or trust, or when they cannot see how to succeed. The resistance often points to a design problem: unclear benefit, extra work, old incentives, no practice time, spent trust, or a change that is hard to use.

Why do employees resist organizational change?

Employees resist organizational change when their job, status, or workload is threatened and leaders have not said what stops, who decides, how performance will be judged, or whether speaking up is safe. They are often protecting their ability to do good work inside the system that still exists.

Is resistance to change normal?

Yes. Resistance is a normal response when a change threatens something people rely on and the replacement is unclear or unworkable. It is useful information about the change. It becomes a problem when leaders treat it only as a mindset issue and leave the design untouched.

How do you overcome resistance to change?

Name what people lose, publish what they will stop doing, align the metrics that still reward the old way, fund practice on real work, give sponsors real decision rights, and fix the parts of the design people are tripping over. Commitment follows a path that is safer and more workable than the status quo.

What are the main reasons people resist change?

The main reasons are inability to see how to succeed, loss of status or control, added work with nothing removed, incentives that still pay for the old behavior, no time to practice, broken trust from past initiatives, and a change that is genuinely harder to use than the current way.

Image credits: Cursor

Content Authenticity Statement: The topic area, key elements to focus on, etc. were decisions made by Braden Kelley, with a little help from Cursor to clean up the article, add images and create infographics.

Sign up here to get Human-Centered Change & Innovation Weekly delivered to your inbox every week.

How to Learn Fast — and Kill Weak Bets Early

Leave a reply

The Experiment Canvas™: Five Gravity-Control Innovation Experiments Visualized

How to Learn Fast — and Kill Weak Bets Early

by Braden Kelley and Art Inteligencia

What Is The Experiment Canvas™? (Short Answer)

The Experiment Canvas™ is a one-page innovation tool for structuring experiments that prove or disprove the feasibility, viability, and desirability of a potential innovation — before you burn capital on the wrong bet. It forces a clear hypothesis, helpers, resources, risks, assumptions, barriers, a three-phase experiment plan (setup → execution → wrap-up), and learning metrics that can falsify the idea.

Below: why the canvas accelerates innovation speed and success rates — and five filled examples for a hypothetical gravity control appliance, showing how a radical idea can be broken into sequenced experiments that cull likely failures early.

Why Innovators Need to Instrument for Learning — Not Hope

Most innovation waste is not bad imagination. It is unfalsified imagination: teams fund prototypes, labs, and roadmaps without a written hypothesis, kill criteria, or a learning metric anyone would defend in a budget meeting. Activity photographs well. Learning does not — unless you design for it.

I created The Experiment Canvas™ as part of the Human-Centered Innovation Toolkit™ to help teams instrument for learning fast in iterative new product or service development. The canvas makes the experiment visual and collaborative — so alignment, accountability, and outcomes improve together. Specs can follow. Hope should not lead.

Used well, the canvas helps you:

Accelerate speed — by sequencing the questions that matter (physics before scale; safety before market theater; cost before Series B fantasy).
Raise odds of success — by naming helpers, resources, assumptions, and barriers before the first dollar of build.
Cull likely failures early — with fail-fast gates and learning metrics that can say “no” while the bet is still cheap.

How The Experiment Canvas™ Structures a Bet

Each canvas asks the same disciplined questions, in roughly this flow:

Zone	What it forces
Hypothesis	The question, feasibility/viability/desirability angles, fatal flaws, adoption blockers
Who can help / resources / risks	Real people, real tools, real downside — not a slide of optimism
Phases 1–3	Setup, execution, wrap-up with evidence, insight, and next gate
Assumptions & barriers	What must be true — and what can stop you
Learning metrics	Three measures that can falsify the bet

To show how this works on something intentionally extreme, I recently built five Experiment Canvas examples (CLICK THEM to get the big version) for a hypothetical gravity control appliance. The point is not sci-fi cosplay. The point is method: even a moonshot becomes manageable when you break it into experiments that can fail honestly.

Example 1 — Physics Feasibility: Is There Any Measurable Effect?

Core hypothesis: Can we create >0.1% weight reduction on a 1kg mass — or is there any measurable effect at all?

This first canvas attacks the fatal question: is there a signal, or are we chasing EMI / magnetic tricks and reputational risk? Helpers include a chief scientist, a gravimetry lab, metrology, and an external skeptic reviewer. Learning metrics demand delta-G, signal-to-noise (>3 sigma), and repeatability. Next gate: if yes → energy test; if no → pivot or kill.

The Experiment Canvas example 1 — physics feasibility for a gravity control appliance testing measurable weight reduction — Example 1 — Physics feasibility: measurable effect, SNR, and repeatability before any product story.

Example 2 — Energy Efficiency: Is the Cost Per Newton Survivable?

Core hypothesis: Can we achieve >1 Newton of lift per kW — and modulate ±2% for 60 seconds — without an energy cost that makes the product impossible?

Prerequisite: Example 1 success. This canvas puts power electronics, thermal management, and fail-fast gates on the page (>5 kW/N kills the path). Metrics: watts per Newton, modulation accuracy, thermal stability. Insight: is the curve linear — or a cliff? Soft landings for radical tech start with honesty about energy economics.

The Experiment Canvas example 2 — energy efficiency and modulation for a gravity control appliance — Example 2 — Energy efficiency: cost per Newton, modulation, and thermal limits with a fail-fast gate.

Example 3 — Safety Envelope: Is Exposure Safe Enough to Sell?

Core hypothesis: Is 8-hour exposure at 0.5G at 1 meter safe — for cells, electronics, and humans?

Prerequisite: a stable Example 2. Here feasibility, desirability, and viability collide: bio impact, EMC, nausea, regulatory classification, liability. Metrics include cell viability (>95% vs control), bit-error rate / EMC compliance, and human symptom reports. Next: define a safety manual and exclusion zone — or stop before market theater begins.

The Experiment Canvas example 3 — safety and exposure envelope for a gravity control appliance — Example 3 — Safety: biological, electronic, and human-factor metrics that define the operating envelope.

Example 4 — Market Desirability: Who Has Gravity Pain Worth Paying For?

Core hypothesis: Which segment has ~$10M gravity-related pain — and will they sign LOIs at real price points ($120k+ / $520k+), or is this cool tech nobody wants?

Prerequisite: safety envelope from Example 3. This is the desirability canvas — interviews, pain scores, willingness to pay, and traction via pilot LOIs. Done when you have enough contact evidence for a go or a clear no-go. Building without a segment that hurts is innovation theater with better physics.

The Experiment Canvas example 4 — market desirability, pain scores, and LOIs for a gravity control appliance — Example 4 — Market desirability: segment pain, willingness to pay, and LOI traction before beta spend.

Example 5 — Manufacturing Viability: Can We Build 10 Betas Under $50k BOM?

Core hypothesis: Can we build 10 beta units at under $50k bill of materials — with a real path through supply chain, yield, and compliance?

This viability canvas asks whether the existing supply chain works, whether FCC/OSHA/product safety is a path or a wall, and whether cost or yield kills margin. Fail fast if BOM exceeds $100k. Metrics: unit cost, manufacturability (yield and hours), compliance blockers. Next: if cost and path are clear → fund the next round; if not → redesign before you scale a fantasy.

The Experiment Canvas example 5 — manufacturing BOM, yield, and compliance for a gravity control appliance — Example 5 — Manufacturing viability: BOM, yield, and compliance path before you scale.

What These Five Canvases Teach About Speed and Success

Read the five examples in sequence and a pattern appears:

Sequence the fatal questions. Physics before energy. Energy before safety. Safety before market. Market before manufacturing scale.
Write the kill criteria in advance. Null result, >5 kW/N, unsafe exposure, no LOIs, BOM blowout — each canvas names how to stop.
Make learning metrics falsifiable. Three metrics per canvas beat a hundred vanity KPIs.
Surface helpers, risks, assumptions, and barriers. Innovation fails politically as often as it fails scientifically.
Treat wrap-up as a decision, not a report. Evidence → insight → next gate. No cemetery of unfinished experiments.

You do not need a gravity appliance to use the method. You need a bet you are tempted to fund on enthusiasm alone — and the discipline to instrument learning before the money gets loud.

Download The Experiment Canvas™ and Run Your Next Bet

The Experiment Canvas™ is available as a free, premium 35″ × 56″ scalable PDF — suitable for wall-sized workshops, 11″ × 17″ (A3) printing, or as a background in Miro, Mural, Lucid, Microsoft Whiteboard, and similar tools. It is one of the optional components of the Human-Centered Innovation Toolkit™.

Go download The Experiment Canvas™ here:
https://bradenkelley.com/product/experiment-canvas-35″-x-56″-poster-size/

Write the hypothesis. Name the metrics that can kill the bet. Run the experiment. Soft landings for innovation are designed — one falsifiable canvas at a time.

Frequently Asked Questions

What is The Experiment Canvas™?

The Experiment Canvas™ is a free innovation tool by Braden Kelley for structuring experiments that test feasibility, viability, and desirability. It covers hypothesis, helpers, resources, risks, setup/execution/wrap-up phases, assumptions, barriers, and learning metrics.

How does The Experiment Canvas™ accelerate innovation?

It forces teams to write a falsifiable hypothesis, sequence fatal questions, name kill criteria and learning metrics, and decide next steps based on evidence — so weak bets die early and strong bets get clearer gates before capital scales.

What are feasibility, viability, and desirability in innovation experiments?

Feasibility asks whether it can work technically. Desirability asks whether humans want it enough to hire it. Viability asks whether it can be made, sold, and sustained economically and legally. The Experiment Canvas™ helps you instrument learning across all three.

Where can I download The Experiment Canvas™?

Download the free 35″ × 56″ poster-size PDF from Braden Kelley’s product page: https://bradenkelley.com/product/experiment-canvas-35″-x-56″-poster-size/

Why use a gravity control appliance as an Experiment Canvas example?

An intentionally extreme hypothetical shows the method under stress: physics, energy, safety, market, and manufacturing each get their own canvas with kill criteria. If the tool works for a moonshot-style idea, it works for the bets already on your roadmap.

Image Credits: Gemini

Content Authenticity Statement: The topic area, key elements to focus on, etc. were decisions made by Braden Kelley, with a little help from Cursor to clean up the article.

Sign up here to get Human-Centered Change & Innovation Weekly delivered to your inbox every week.

Top 10 Human-Centered Change & Innovation Articles of August 2026

Leave a reply

Top 10 Human-Centered Change & Innovation Articles of August 2026 Drum roll please…

At the beginning of each month, we will profile the ten articles from the previous month that generated the most traffic to Human-Centered Change & Innovation. Did your favorite make the cut?

But enough delay, here are August’s ten most popular innovation posts:

Time to Rethink Pitch Fests and Business Plan Competitions — by Arlen Meyers
What If You Could Prove the Government is Ripping Us Off? — by Braden Kelley
The Surprising Innovation History of the Bicycle — by John Bessant
Dead Actors Society — by Art Inteligencia
Amazon Connect Combines Human Empathy with AI to Redefine Service — by Shep Hyken
AI Will Create a More Human Future, Not a Less Human One — by Braden Kelley
Managing Your Work Friends — by David Burkus
Building the Business Case for a Customer Experience Audit — by Braden Kelley
Customer Experience Audit vs. Customer Satisfaction Survey — by Braden Kelley
Case Study – Innovating Around a Disruption — by Jason Hauer

BONUS – Here are five more strong articles published in July that continue to resonate with people:

What Happens When AI Becomes Your Customer? — by Shep Hyken
How to Calculate the ROI of Customer Experience — by Braden Kelley
How to Keep Learning as a Leader — by David Burkus
Why Collective Intelligence is the New Scarce Resource in an Age of Abundant AI — by Braden Kelley
Why Conversations Are the New Digital Gold — by Braden Kelley

If you’re not familiar with Human-Centered Change & Innovation, we publish 4-7 new articles every week built around innovation and transformation insights from our roster of contributing authors and ad hoc submissions from community members. Get the articles right in your Facebook, Twitter or Linkedin feeds too!

Have something to contribute?

Human-Centered Change & Innovation is open to contributions from any and all innovation and transformation professionals out there (practitioners, professors, researchers, consultants, authors, etc.) who have valuable human-centered change and innovation insights to share with everyone for the greater good. If you’d like to contribute, please contact me.

P.S. Here are our Top 40 Innovation Bloggers lists from the last five years:

Sign up here to get Human-Centered Change & Innovation Weekly delivered to your inbox every week.

The Slowing EV Market

Leave a reply

The Slowing EV Market

GUEST POST from Geoffrey Moore

One initiative that is top-of-mind for curtailing climate change is the electrification of ground transportation. The meteoric rise of Tesla drew the world’s attention to EVs, and China’s fast-follower public-private partnership has taken the industry to a whole new level. But now it is encountering a lull, and that raises the question, where do we go from here?

A couple of years ago LG announced a breakthrough in a battery-manufacturing technology called dry-coating that is expected to lower cost from 17 to 30%, with expected deployment in 2028. In a steady-state market, this would be welcome news indeed, but for a market that is still developing, it is not the sort of risk-adjusted return on investment (ROI) nor the kind of rate of return (IRR) that will attract private equity. LG is looking to future growth in its existing battery business to reward its efforts and counting on its investors to have the patience to wait for it.

Meanwhile, in the US, the first wave of venture returns has come and gone, and the next wave depends upon enormous amounts of capital being invested in very long-term charging infrastructure projects, the kind that are normally funded by bonds. This is reminiscent of the national commitment that underwrote the interstate highway buildout in the 20th century, but it is not clear we have the political consensus to prioritize such a project.

Ironically, we do not lack for capital to fund these efforts. The past several decades of digital transformation have created enormous pools of wealth, and financial managers are anxious to put that capital to work. The problem is that, for this phase of investment, the ROI and IRR performance metrics that accompany the creation of that wealth are neither appropriate nor available.

Private capital, for better or for worse, is driven by its compensation systems. We saw this when we tried to leverage its expertise to create carbon-credits exchanges. Not surprisingly that led to a sustained gaming of the system that has generated plenty of fees but done nothing to improve the climate situation. What we need instead is a private-public partnership based on a genuine commitment to global good.

Such a partnership is possible, but only if our political leaders are committed to such values, something we should all keep in mind when we vote this fall. At present, the electoral conversation is so consumed with personalities seeking to score points with abusive rhetoric that there is little prospect for any such partnership to emerge. But we need not capitulate to that rhetoric. If the time to change course is now, then we should hold ourselves and our country accountable for doing so.

That’s what I think. What do you think?

— Image credit: Pexels

Sign up here to join 17,000+ leaders getting Human-Centered Change & Innovation Weekly delivered to their inbox every week.

How Do You Build a Culture of Innovation?

Leave a reply

How Do You Build a Culture of Innovation?

by Braden Kelley and Art Inteligencia

How Do You Build a Culture of Innovation? (Short Answer)

You build a culture of innovation by making innovating the easy, rewarded path — not by decorating the office or running more brainstorms. That means a shared definition and strategy, deep customer insight, a fair path from idea to adoption, resources that can move, psychological safety with accountability, clear roles, and leaders who remove friction. Culture is what people do when the poster isn’t watching.

An innovation culture isn’t what you put on the walls. It’s what gets funded, forgiven, and finished.

Below you’ll find what an innovation culture actually is, the theater that pretends to build one, seven building blocks that do, how to tell if it’s working, and where to start. One foundation first: without a shared definition of innovation, “culture of innovation” means whatever each leader wants it to mean. Start with What Is Innovation? A Clear Definition, With Examples.

What Is an Innovation Culture — Really?

An innovation culture is not free snacks, a quarterly hackathon, or a lab with cool furniture. It is not a slogan that “everyone is an innovator” while people have no time, permission, or path to finish anything.

An innovation culture is the habits, roles, permissions, incentives, and information flows that make innovating normal — not heroic. It shows up in how people get insights, generate and kill ideas, get time and money, collaborate across silos, and own adoption after launch.

In my experience writing Stoking Your Innovation Bonfire, organizations rarely fail innovation because they lack ideas. They fail because barriers — strategy, psychology, structure, information, and resources — extinguish good ideas before they can become widely adopted solutions. Culture is what people do under those conditions: what gets praised, promoted, punished, and ignored.

What Doesn’t Build an Innovation Culture?

A lot of well-intentioned activity builds a costume instead of a culture. Watch for these substitutes:

Pilot purgatory and demo days with no clear kill-or-scale decision
Idea contests and suggestion boxes with no path to development
Innovation labs that never touch the core business (for why labs stall, see 5 Reasons Innovation Labs Fail — and 5 Replacements That Work)
Celebrating creativity while punishing smart risk and bad news
Measuring idea volume instead of adoption and value

I catalog the most common costumes in 7 Types of Innovation Theater.

If your culture rewards the costume, you’ll get a costume.

How Do You Build an Innovation Culture? Seven Building Blocks

Agree on what innovation means — and spread the definition.
If one team means “new patents” and another means “adopted value,” you will fight over resources and celebrate different things. Choose a definition and teach it widely.
First move: put your definition in every innovation review and funding request for the next quarter.
Set an innovation strategy and goals.
Where will you play? Which types of innovation will you fund — incremental, adjacent, radical, disruptive — and what does “good” look like this year? Innovation without strategy is experimentation; strategy without innovation is incrementalism forever. For the type lens, see What Are the Different Types of Innovation?
First move: write one page: where we innovate, for whom, and how we’ll know.
Start with human-centered insight.
Brainstorms without insight produce noise. Sustainable innovation almost always starts with deep understanding of customer and employee jobs, frustrations, and unmet needs.
First move: require a named insight (who, what job, what evidence) before any ideation workshop.
Build a fair path from idea to adoption.
Evaluation that only funds “safe” tweaks will starve bigger bets. Development needs real time and money. And someone must own adoption after launch — not only the build.
First move: name the adoption owner for every funded innovation before work starts.
Reduce resource and information friction.
Culture dies when people and budget cannot move to the work that needs them, or when insights sit trapped in one silo. Leaders serious about innovation make resources and relevant information easier to move.
First move: pick one policy that blocks cross-team funding or data sharing and fix it this quarter.
Shape psychology on purpose.
People need permission to experiment, safety to surface bad news, and accountability for learning and outcomes — not blame for every miss. Fear of failure and fear of looking foolish are culture, whether you designed them or not.
First move: in the next review, praise a smart kill or a well-documented miss as loudly as a launch.
Install roles and rhythms.
A lone “innovation person” cannot carry a culture. You need multiple roles — champions, facilitators, implementers, and more — and a cadence for reviewing the portfolio. Reinforce the new norms with recognition and promotion. For the role map, see 10 Innovation Roles Every Enterprise Needs.
First move: assign who owns insight, who owns evaluation, and who owns adoption for your top three bets.

How Do You Know If Your Innovation Culture Is Working?

Signs it’s working	Signs it’s theater
Ideas from the edges get heard	Only a favored few get airtime
Cross-functional work is normal	Innovation lives only in a side building
Pilots have kill-or-scale owners	Pilots renew forever with no decision
People can name the innovation strategy	“We’re innovative” with no shared focus
Adoption has a named owner	Success is measured at launch day
Leaders ask about learning, not only dates	Bad news is hidden until it’s too late

Measure maturity with a baseline you can retake, and track a few outcome metrics — adoption, value, what got replaced — not poster counts or idea tallies. For measurement beyond idea count, see 12 Metrics That Actually Measure Innovation Value.

Where Should You Start Building an Innovation Culture?

Don’t try to change everything at once. Use this sequence:

Diagnose barriers — don’t guess. Get a clear picture of where friction is highest.
Pick one or two highest-friction barriers for this quarter — not ten initiatives.
Fund a visible win that proves the new way is better than the old, and communicate it.
Change one incentive or metric that still punishes the new behavior.
Assign roles so culture isn’t “everyone and no one.”

Culture change often comes last, after new practices prove themselves. Friction, though, can be reduced now.

Start where the fire keeps going out.

Ready to Take the Next Step?

Building a culture of innovation starts with seeing your barriers clearly — then removing them with a roadmap, not another brainstorm.

Find out where you stand. Take the free Innovation Maturity Assessment: 50 questions, about 10–15 minutes, scored against a five-level Innovation Maturity Model so you can see your biggest barriers and set a baseline to improve from.

Learn how to remove the barriers. Read Stoking Your Innovation Bonfire, my roadmap for identifying what’s blocking innovation in your organization and building a culture where it can flourish.

Posters don’t build culture. Removing friction does — and that work starts with an honest baseline.

FAQ: Building a Culture of Innovation

How do you create a culture of innovation?

Create a culture of innovation by agreeing on a shared definition, setting an innovation strategy, starting from human-centered insight, building a fair path from idea to adoption, reducing resource and information friction, shaping psychological safety with accountability, and installing clear roles and review rhythms. Leaders remove barriers; they don’t just run brainstorms.

What is an innovation culture?

An innovation culture is the habits, roles, permissions, incentives, and information flows that make innovating normal — not heroic. It is what people do when it comes to funding, finishing, and adopting new solutions, not what appears on posters or in lab lounges.

What are the characteristics of an innovative culture?

Characteristics include a shared definition of innovation, clear strategy and goals, insight before ideation, a fair idea-to-adoption path, low friction for resources and information, psychological safety with accountability, cross-functional collaboration, and named ownership of adoption — not only launches.

How do leaders build an innovation culture?

Leaders build an innovation culture by diagnosing barriers, setting strategy, moving resources and information to where they’re needed, rewarding learning and smart kills as well as launches, assigning clear roles, and changing metrics that punish the new behavior. Culture follows what leaders fund, forgive, and finish.

Why do innovation culture initiatives fail?

They fail when organizations buy theater — hackathons, labs, and slogans — without removing barriers, aligning incentives, or owning adoption. Initiatives also fail when there is no shared definition or strategy, when fear blocks honesty, and when success is measured by activity instead of adopted value.

Image credits: Gemini

Sign up here to get Human-Centered Change & Innovation Weekly delivered to your inbox every week.

Why Your Annual Strategic Plan is Obsolete by Q2

Leave a reply

Why Your Annual Strategic Plan is Obsolete by Q2

by Braden Kelley and Art Inteligencia

Every January, I watch the same ritual play out inside otherwise well-run organizations. Leadership spends weeks, sometimes months, building a strategic plan for the year ahead: a single narrative about where the market is going, what the company will do about it, and how success will be measured twelve months from now. By the time Q2 closes, half of that plan is already quietly out of date, and everyone in the room knows it. Nobody says so out loud, because saying so would mean admitting the process itself is the problem, not the plan.

The plan was never wrong. It was just singular.

Here’s what I’ve learned after two decades of helping organizations navigate exactly this moment: the plan usually wasn’t badly built. The people in the room were smart, the research was real, the logic held together. The failure isn’t in the thinking, it’s in the structure. A traditional strategic plan describes one future and commits real budget, real headcount, and real organizational attention to it. When that one future doesn’t materialize exactly as modeled, and it never does, not exactly, the plan doesn’t bend. It breaks, quietly, and everyone starts working around it instead of updating it.

Strategic planning and strategic foresight are not the same discipline

This is the distinction most planning processes skip entirely. Strategic planning asks: given what we believe about the future, what should we do? Strategic foresight asks a prior question: what do we actually know, and don’t know, about the future we’re planning for? Skip that second question, and you’re not really planning for uncertainty, you’re planning for a single scenario and hoping it holds. Most organizations skip it not because they don’t value it, but because nobody on the team has been trained to do it, and hiring a dedicated foresight function feels like a luxury reserved for companies with a research budget most teams don’t have.

Why I built FutureHacking™

That gap, real demand for foresight, no accessible way to practice it, is exactly what I built FutureHacking™ to close. It’s not a framework that asks your team to become professional futurists. It’s a structured, visual, collaborative methodology that takes a cross-functional leadership team from raw signals in the market, through the trends those signals suggest, to a set of genuinely possible futures — and from there, to identifying which future is most probable and building a real path toward the future you’d actually prefer. “FutureHacking™ is the art and science of getting to the future first” isn’t a tagline I use lightly. It’s the whole point: the organizations that see a shift coming, and start moving before it’s obvious to everyone else, are the ones who get to shape what happens next instead of reacting to it after the fact.

Where to start before your next planning cycle

If your team has never run a structured foresight exercise, the fastest way to feel what this actually looks like is with the free FutureHacking Signal Picker — it walks you through identifying and prioritizing the real signals worth watching, the first and most foundational step in the whole methodology, at no cost. Run it before your next planning offsite, and bring the output into the room instead of starting from a blank whiteboard.

Something new I’m building

I’m also putting the finishing touches on a second tool, the FutureCanvas Picker, that goes a step further than signal identification. It’s designed to give planners a genuine taste of the full arc: moving from signals, to the trends they suggest, to a real set of possible futures, then narrowing to your most probable future, and finally mapping the path to the future you’d actually prefer to build. It’s the clearest, fastest way I’ve built yet to feel what FutureHacking™ makes possible in a single sitting.

I’m not opening this one to everyone right away. I’m looking for a select group of strategic planners, CSOs, and leaders running planning processes right now to get early access before it’s broadly available — partly because I want real feedback from people doing this work under real deadline pressure, not from a general audience. If that’s you, and you’d like to be considered for early access, reach out and let me know — I’ll be following up personally with the select few who get in first.

The organizations that get to the future first aren’t the ones with the biggest planning budgets. They’re the ones who stopped mistaking a single confident narrative for genuine foresight, and built a process that can hold more than one future at a time.

Image Credits: Gemini

Content Authenticity Statement: The topic area, key elements to focus on, etc. were decisions made by Braden Kelley, with a little help from Claude to clean up the article.

Sign up here to get Human-Centered Change & Innovation Weekly delivered to your inbox every week.