Author Archives: Braden Kelley

About Braden Kelley

Braden Kelley is a Human-Centered Experience, Innovation and Transformation practice lead at HCL Technologies, a popular innovation speaker, and creator of the FutureHacking™ and Human-Centered Change™ methodologies. He is the author of Stoking Your Innovation Bonfire from John Wiley & Sons and Charting Change (Second Edition) from Palgrave Macmillan. Braden is a US Navy veteran and earned his MBA from top-rated London Business School. Follow him on Linkedin, Twitter, Facebook, or Instagram.

Compliance-Driven Customer Experience

Leave a reply

What Financial Services and Healthcare Teams Need to Know

Compliance-Driven Customer Experience

by Braden Kelley and Art Inteligencia

In most industries, a bad customer experience (CX) costs you a customer. In financial services and healthcare, it can also cost you an exam finding, a complaint to a regulator, or a line item in an audit report that someone on your compliance team now has to explain. That’s a meaningfully different kind of pressure, and it changes what a customer experience audit is actually worth to these two industries specifically — not just as a commercial tool, but as something that can double as genuine regulatory evidence.

A caveat before I go further: I’m not a lawyer or a compliance officer, and nothing here is regulatory advice. What I am is someone who’s watched CX and compliance teams operate as two separate functions inside the same organization, often documenting the same customer touchpoints in two different ways, for two different audiences, without either one fully benefiting from what the other already knows.

The silo that’s costing you twice

Here’s the pattern I see constantly in regulated industries: compliance runs its own fair-treatment reviews, complaint trend analysis, and documentation processes, built specifically to satisfy an examiner or auditor. CX, separately, runs its own journey mapping and improvement work, built to satisfy customers and the business. The two teams are frequently looking at the exact same touchpoints — the same loan application flow, the same patient intake process, the same claims experience — and producing two different, uncoordinated pictures of it, often without either team knowing in detail what the other found.

That duplication isn’t just inefficient. It means your compliance documentation and your actual customer experience improvement work rarely inform each other, and the organization effectively pays twice for insight into the same process it could have gotten once, more thoroughly, if the two efforts were designed together from the start.

What regulators in these industries are actually looking for

Across financial services and healthcare, the regulatory expectation increasingly isn’t just “treat customers fairly” as an outcome — it’s evidence of a systematic, ongoing process for finding and fixing where you aren’t. Fair lending and UDAAP-related reviews in financial services look for documented, proactive self-assessment, not just a clean complaint log. Patient experience standards in healthcare increasingly tie directly to things like CAHPS-style measurement and documented quality improvement processes, not just satisfaction scores reported upward once a year. In both industries, accessibility requirements for digital experiences — online banking, patient portals — are under increasing scrutiny on their own. What all of this adds up to is a consistent theme: proof that you looked, systematically and on a defensible cadence, matters as much as what you found.

Why a well-run CX audit produces exactly this kind of evidence

This is where the overlap gets genuinely useful instead of just theoretically interesting. A properly structured audit — validated personas, real journey mapping, an honest evaluation of existing complaint and service data, firsthand walkthroughs of the actual touchpoints, and benchmarking against what good looks like elsewhere — is, almost incidentally, precisely the kind of systematic, documented, dated process that compliance functions in these industries need to be able to point to. The commercial insight and the compliance evidence aren’t two different projects. They’re two outputs of the same rigorous process, if that process is designed with both audiences’ needs in mind from the outset rather than retrofitted afterward.

Timing matters more here than almost anywhere else

In most industries, a CX audit can happen whenever budget and bandwidth allow. In financial services and healthcare, timing it ahead of a scheduled exam or review changes its character entirely — it becomes proactive evidence of a mature process instead of a reactive scramble after a finding already landed. I’ve seen the difference in posture this creates firsthand: walking into a regulatory conversation with “here’s the systematic process we run and here’s what we found and fixed” is an entirely different position than walking in after a finding, trying to explain what you’re doing about it now that someone else noticed first.

Where to start

If your organization is in financial services or healthcare and hasn’t yet connected your CX and compliance efforts into a single, well-documented process, a Customer Experience Audit designed with both your commercial goals and your documentation needs in mind can serve both functions at once — worth coordinating with your compliance and legal teams on scope from the start. And if you want a sense of what unresolved experience gaps could be costing commercially, separate from the compliance conversation entirely, the CX ROI Calculator is a good place to start putting a number on it.

Download the Customer Experience Audit Checklist as a PDF

Image Credits: ChatGPT

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.

Is Your pDoom Less Than Zero Yet?

Leave a reply

Is Your pDoom Less Than Zero Yet?

by Braden Kelley and Art Inteligencia

Every statistician who just read that headline winced. Probabilities don’t go below zero, and they’re right. Hold that wince for a moment, because it points at something the whole conversation about superintelligence keeps skipping.

If you haven’t run into the term, pDoom is the probability you personally assign to artificial intelligence ending badly for humanity. People trade their pDoom numbers at dinner parties now, the way people used to trade fantasy football picks. It’s a useful little conversation starter. It’s also a lopsided one, because it only counts one column of the ledger.

Nobody asks for your pDoom of inaction.

Press play first

I built this article around a music video, because some arguments land better with a hook in them. Here it is: Nothing Went Foom! from Bright Mirror.

That title is a wink at one of the great nerd arguments of the last twenty years. “Foom” is the sound an intelligence explosion makes in the fast-takeoff story: the machine gets a little smarter, uses that to get a lot smarter, and before anyone finishes the meeting it has left us standing on the platform. The idea was batted around in the Yudkowsky and Hanson debates back in 2008 and has been living rent-free in our collective imagination ever since.

I love that the title makes the point that nothing went foom. Technology almost never works that way. Electricity took decades to rewire the world. The internet took decades more, and we are still arguing about what it did to us. Transformations arrive in increments, which sounds boring until you realize what increments give you: time to watch, time to measure, time to adjust, and time to build the guardrails while the thing is still being built. Gradual is where safeguards live.

What we’re actually talking about building

I get tired of conversations where superintelligence is only ever the villain, so let me describe the other movie.

We already have a preview. AlphaFold predicted the structures of hundreds of millions of proteins, a job that used to cost a doctoral student years per protein, and its creators shared a Nobel Prize in Chemistry in 2024 for it. That is what narrow, early, imperfect AI did to one corner of biology. Now scale the ambition.

A superintelligence, pointed carefully at our hardest problems, could plausibly help us:

Compress drug discovery from a decade to a few years, and take a serious run at diseases we’ve written off as incurable.
Design new materials for batteries, solar cells and carbon capture that human intuition would never stumble across.
Help tame fusion, where the physics is understood but the control problem is brutal.
Put a patient, personalized tutor in front of every child on earth, including the ones who live hours from the nearest decent school.
Bring specialist-level diagnostics to places that have never had a specialist.
Speed up science itself, which is the part that makes my futurist heart skip. When the engine of discovery accelerates, every other list gets longer.

I’m not promising any of it will happen. I’m saying it could, and that “could” is worth a lot of human lives and a lot of human potential.

The risk we never put on the spreadsheet

Here’s where the less-than-zero joke earns its keep. The standard pDoom calculation asks how likely it is that we build this and it goes wrong. Fair question. But look at what’s missing: the cost of every year we don’t build it, or build it late, or build it only in the places that don’t care about safeguards.

A disease that goes uncured for another decade is a cost. A grid that stays dirty for another decade is a cost. A child who never gets the tutor is a cost. Those costs are quieter than a robot uprising, so they never show up in the headline, but they are real people. If you only count the risks of acting and never the risks of not acting, you haven’t done risk analysis. You’ve done fear analysis.

So here’s my proposal for a better number. Take your pDoom from moving forward, then subtract the doom you are already accepting by standing still. I suspect that for a lot of people the net figure is a lot lower than they thought, and for some of us it’s flirting with the territory of the headline. Statisticians, you may now exhale.

Safeguards, of course

Now let me be extremely clear, because I know how this paragraph gets quoted without its neighbors: I am not arguing for recklessness. Brakes are what let you drive fast, and seatbelts didn’t kill the automobile, they saved the automobile.

Responsible innovation means staged deployment instead of big-bang launches. It means independent testing and red-teaming, transparency about what these systems can and can’t do, real accountability when they fail, and international cooperation, because a safeguard that only half the world adopts is a suggestion. It means keeping humans in the loop for the decisions that matter, and building systems whose values we can inspect rather than hope for.

And I’ll say this plainly: thoughtful, serious people believe the danger is real, and some put meaningful odds on catastrophic outcomes. They might be right. That’s exactly why the safeguards have to be real and not decorative, and why dismissing the worriers is as unhelpful as dismissing the optimists. The goal isn’t to win the argument. It’s to build the thing well.

Ask a better question

The debate usually gets stuck on “should we build superintelligence?” Treat it as a yes-or-no switch and one side has to lose. Ask instead: what would we need to see in place to say yes? What safeguards, what evidence, what governance, what tripwires that tell us to slow down?

That question has answers. It also has owners and deadlines, which a vibe never does.

So, how’s your pDoom?

Mine is not zero, and I would be suspicious of anyone whose is. But when I count both columns, including the diseases, the climate, the classrooms and the discoveries waiting on the other side of responsible progress, I find the biggest risk we face isn’t that we build this thing carefully. It’s that we let fear stop us from building it at all, and hand the future to whoever was less cautious.

Hit play on the video again. Then ask yourself what future you’d rather get to first.

OR, is it all an EVIL PLAN?

Image Credits: m365 CoPilot

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.

When a Bad Review Goes Viral

Leave a reply

Turning a PR Moment Into a Real Fix

When a Bad Review Goes Viral

by Braden Kelley and Art Inteligencia

The moment a bad customer experience goes viral, an organization snaps into a very specific and very well-rehearsed mode: crisis response. Legal gets looped in. Communications drafts a statement. Someone reaches out to make the customer whole, quickly and visibly. All of that is necessary, and none of it answers the only question that actually matters once the immediate fire is out: was this a genuine one-off, or is it the first time anyone’s noticed something that’s been happening quietly for a while?

The PR response and the real diagnosis are two different jobs

Here’s the trap I’ve watched organizations fall into repeatedly: the PR response feels like it resolved the problem, because from the outside, it did. The story dies down. The affected customer is satisfied, or at least quiet. Leadership moves on, understandably relieved. But making one visible customer whole and understanding whether the underlying failure is systemic are two completely different exercises, and only one of them actually happened. The apology addressed the symptom that became public. It said nothing about whether the same failure is quietly happening to other customers who simply didn’t have a large enough platform for anyone to notice.

The customer who went viral is rarely the only one it happened to

This is the part that gets lost in the relief of a crisis passing: the customer whose complaint went viral usually isn’t unique in what happened to them. What’s unique is that they had an audience willing to amplify it. For every customer with the platform and inclination to make a bad experience public, there are likely dozens or hundreds who had the same experience, said nothing beyond a quiet complaint or no complaint at all, and simply left — or stayed, resentfully, waiting for a better alternative to come along. A viral incident isn’t the problem. It’s a visibility event for a problem that was probably already there, silently costing you customers who never made noise about it.

Why this moment is actually a rare opportunity, if you use it right

There’s an uncomfortable but useful truth about the period right after a public incident: it’s often the single easiest moment to get real budget and leadership attention for a genuine diagnostic effort. The urgency that made the crisis painful is the same urgency that can get a proper audit approved in days instead of the usual months of internal advocacy. Most organizations waste this window by spending it entirely on the public-facing fix and the internal postmortem meeting, then let the appetite for deeper investigation fade along with the news cycle. The smarter move is using that same window to actually find out whether this was a true outlier or a known category of failure hiding in plain sight.

What the diagnosis actually needs to answer

A proper look at this needs to walk the exact touchpoint that failed, the way the customer who went viral actually experienced it — not the documented process, the real one, with whatever gaps and workarounds have accumulated around it. It needs to check the existing data for any pattern of similar complaints that never individually rose to leadership’s attention, because a string of quiet, unconnected complaints about the same root issue often exists well before one of them goes public. And it needs a clear-eyed read on whether this really was a rare edge case, because overcorrecting an entire process based on a single dramatic incident carries its own cost — reacting to n=1 with organization-wide policy changes can create new friction for the vast majority of customers who never experienced the original problem at all.

Turning a bad week into a real fix

The organizations that come out of a viral moment genuinely stronger aren’t the ones with the best-worded apology. They’re the ones that used the moment’s unusual clarity and unusual leadership attention to actually find out whether they had a true one-off or a systemic gap, and fixed the right thing instead of just the visible thing.

If you’re in or just past this kind of moment and want an honest answer to which one you’re actually dealing with, a Customer Experience Audit scoped to the failed touchpoint is built for exactly this kind of diagnosis. And if you want a fast sense of what a silent, unaddressed version of this problem could be costing beyond the one visible incident, the CX ROI Calculator is a good 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.

Expanding Into a New Market? Audit the Journey Before Your Customers Do

Leave a reply

Expanding Into a New Market? Audit the Journey Before Your Customers Do

by Braden Kelley and Art Inteligencia

Market expansion plans get validated within an inch of their life on almost everything except the one thing that determines whether customers actually stay once they arrive: whether the experience you’re bringing with you was ever built for the people you’re about to bring it to. Product-market fit gets tested. Go-to-market strategy gets modeled and re-modeled. The actual customer journey — the thing a real person will move through from first contact to renewal — usually just comes along for the ride, unexamined, on the assumption that if it worked here, it’ll work there too.

The assumption that quietly undermines expansion

That assumption is rarely stated out loud, which is part of why it survives so many planning cycles unchallenged. Nobody in an expansion planning meeting says “we’re assuming our existing journey translates perfectly to this new market.” They just don’t say anything about the journey at all, because it’s not the part of the plan anyone’s job is to stress-test. The financial model gets scrutiny. The competitive landscape gets scrutiny. The experience a new-market customer will actually have moving through your funnel, your onboarding, your support process — that gets inherited wholesale from whatever already exists, on the theory that if the core offering is sound, the wrapper around it doesn’t need a second look.

Where the existing journey actually breaks

It rarely breaks in the obvious place — translated marketing copy, currency formatting, the things everyone remembers to check. It breaks in the places built around assumptions nobody remembers making. A support response-time standard that felt generous in your home market can feel slow against a new market’s expectations, if the incumbents there have trained customers to expect faster. A sales cycle built around how your existing buyers evaluate a purchase can stall completely against a new segment’s actual buying committee structure, if nobody mapped how decisions really get made there before launch. Payment norms, preferred channels, even how directly or indirectly customers expect to be communicated with — all of it can differ in ways that don’t show up as an error, just as a slightly worse experience that a new-market customer has nothing to compare it to except the local alternative they almost chose instead.

Why waiting for complaints is the expensive option

By the time these gaps show up as customer complaints, you’ve usually already spent a meaningful share of the expansion budget acquiring the customers who are now quietly churning, and you’re competing for the next wave of customers in a market where your early reputation is already partly set by the people who had the rough experience first. Word of mouth in a new market works both directions faster than people expect — the same network effects that could help an expansion take off quickly can just as easily spread a “their onboarding is confusing” reputation before you’ve had a chance to fix it.

Auditing before launch instead of diagnosing after

The alternative is treating the new-market journey as something to validate deliberately before launch, not something to inherit by default. That means building out validated personas for the new market specifically, rather than assuming your existing personas translate — buying committees, decision criteria, and expectations can differ enough that a persona built for one market actively misleads you in another. It means walking the journey the way a new-market customer actually would, ideally with someone unfamiliar with your existing assumptions doing the walking, so the things your team has stopped noticing about your own process get caught before a real customer catches them instead. And it means benchmarking specifically against the local incumbents and best-in-class examples a new-market customer will actually be comparing you to, not against your existing competitors back home, since “good enough” is set by whoever they’re used to, not by whoever you’re used to competing against.

Where to start

If you’re heading into a market or segment expansion and want to validate the journey before your launch budget is already spent finding out the hard way, a Customer Experience Audit scoped to the new market specifically is built for exactly this. And if you want a rough sense of what an undiagnosed gap could cost in early churn before you scope that engagement, the CX ROI Calculator is a fast place to start putting a number on it.

Download the Customer Experience Audit Checklist as a PDF

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.

Turning Foresight Into an Actual Strategic Roadmap

Leave a reply

From “What If” to “What Now”

Turning Foresight Into an Actual Strategic Roadmap

by Braden Kelley and Art Inteligencia

I have seen more beautiful scenario maps gather dust than I can count. Gorgeous work — well-researched signals, genuinely thoughtful trends, three or four possible futures mapped out with real rigor, presented to an engaged room that nodded along and felt smarter walking out than they did walking in. And then, six months later, nothing about how the organization actually operates has changed. The binder is still on someone’s shelf. This is the single most common way foresight work dies, and it has nothing to do with the quality of the thinking.

“What if” is the fun part. That’s the problem.

Exploring possible futures is genuinely engaging work. There’s something almost playful about it — imagining how the market could shift, what technology could disrupt, which future would be exciting to build toward. Rooms come alive during this part of a planning session in a way they rarely do during budget reviews. That energy is valuable, and I’d never want to dampen it. But it’s also exactly why so much foresight work stalls right there: the “what if” conversation is satisfying enough on its own that it can feel like the destination, when it was only ever supposed to be the on-ramp.

Nobody’s job is the translation

Here’s the structural reason this happens, and it’s not about laziness or lack of follow-through. In most organizations, nobody’s actual job description includes turning a set of possible futures into this year’s specific strategic priorities. The strategy team’s job, as usually defined, ends at “here are the scenarios and here’s the probable one.” Execution teams’ jobs start from wherever the strategic plan already tells them to begin. The translation step — the actual “so given all that, what do we do differently starting Monday” — falls into a gap between two functions that both assume the other one owns it.

What “what now” actually requires

Turning a preferable future into a real roadmap means doing something more specific than restating the future in more urgent language. It means identifying the near-term moves that make sense regardless of exactly how the future unfolds — the no-regret moves, the ones that pay off whether your probable future arrives on schedule, arrives differently than expected, or gets overtaken by one of the other futures you mapped. It means sequencing those moves against a realistic timeline instead of listing them all as equally urgent. And it means naming specific owners for each one, because a strategic priority without a named owner is, in practice, nobody’s priority at all.

It also means building in signposts — specific, observable things you’ll watch for that would tell you your probable future is actually arriving, or that one of the other futures is starting to look more likely instead. Without signposts, “what now” plans quietly calcify into exactly the single-future thinking foresight was supposed to prevent in the first place. With them, the roadmap stays genuinely responsive instead of becoming next year’s version of the plan that goes stale by Q2.

This is exactly why I built a specific step for it

This translation gap is precisely why FutureHacking™ doesn’t stop at mapping possible futures. The methodology includes a dedicated step — I call it NowBuilder™ — built specifically to take the output of the “what if” work and force the room through the “what now” conversation before anyone leaves: near-term moves, sequencing, ownership, and the signposts that tell you when to adjust course. It exists because I watched too many organizations do genuinely excellent scenario work and then have no structured way to turn it into anything that showed up on an actual roadmap the following Monday.

You can learn more about the full methodology at FutureHacking™ — it’s the art and science of getting to the future first, and getting there requires both halves: the imagination to genuinely hold multiple futures, and the discipline to convert that thinking into something your organization actually does.

Where to start

The free FutureHacking Signal Picker is the right first step if your team hasn’t run a structured foresight exercise yet — it walks you through identifying and prioritizing real signals, the foundation everything else in the methodology builds on, at no cost.

Something new I’m building

I’m also finishing a second tool — the FutureCanvas Picker — that carries a planning team through the full arc in one sitting: from signals, to the trends they suggest, to a genuine set of possible futures, narrowing to your most probable future, and mapping the path to your preferable one. It’s the closest thing I’ve built yet to running a complete FutureHacking™ session on your own.

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 using it 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.

A scenario map tells you what could happen. It’s still just a very well-organized guess until something in your organization actually moves because of it.

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.

Auditing Customer Experience Before and After a Systems Migration

Leave a reply

Auditing Customer Experience Before and After a Systems Migration

by Braden Kelley and Art Inteligencia

Every systems migration I’ve ever seen gets sold internally with some version of the same reassurance: “nothing will change for the customer.” I understand why people say it — it’s meant to calm nerves and keep the project moving. It’s also almost never entirely true, and the gap between that promise and reality is exactly where a lot of quiet, expensive customer experience damage happens.

Migrations are measured by the wrong success criteria

A CRM cutover, a new billing platform, a support tooling replacement — these get judged by IT and project management on a specific set of criteria: did the data migrate correctly, is uptime where it should be, did the go-live happen on schedule. Those are the right questions for a systems team to ask. They’re the wrong questions, or at least an incomplete set, for understanding whether the customer experience survived the transition intact. A migration can hit every technical success metric on the project plan and still quietly degrade the actual experience a customer has, because nobody on the technical side was specifically measuring for that.

The silent regression problem

The most expensive migration failures I’ve seen aren’t the dramatic ones — the outage, the data loss, the system that won’t come back up. Those get noticed immediately and fixed fast, precisely because they’re loud. The expensive ones are silent regressions: a new billing platform that technically works but changes the invoice format customers had built internal processes around, so now their AP department has to redo reconciliation manually every month. A new CRM that migrates the data correctly but changes how support reps see a customer’s history, so reps start asking questions customers have already answered before, over and over, without anyone flagging it as a problem because each individual instance looks like a minor inconvenience rather than a pattern.

None of that shows up in a migration status report. All of it shows up, eventually, in retention numbers that took a hit for reasons nobody traced back to the systems change that happened two quarters earlier.

Why you need a real baseline before you touch anything

You can’t know what changed for customers after a migration if you don’t have an honest picture of what their experience actually looked like before it — not the technical specs of the old system, but the lived experience of using it. That means validated personas, a current journey map across the specific touchpoints the migration will touch, and a firsthand walkthrough of those touchpoints as they exist today. This is the step migrations skip most often, because the old system is about to be replaced anyway and it feels like wasted effort to study something on its way out. It isn’t wasted — it’s the only way to tell the difference between “the migration caused this” and “this was already broken and we just never noticed.”

What to actually check after cutover

Once the new system is live, the audit isn’t finished — it shifts to verification. This means walking the same touchpoints again, deliberately, rather than assuming success because no one’s complained yet. Complaints are a lagging indicator; most customers adapt to a worse experience quietly before they ever formally report it. It also means comparing the same data points — response times, resolution rates, whatever mattered in the baseline — against the pre-migration numbers specifically, not just against general benchmarks, since the question that matters is whether this specific change made things better, worse, or invisible.

The teams that get this right treat it as one audit, not two

The most effective version of this isn’t a rushed pre-migration check plus a separate, disconnected post-migration review commissioned only if something goes wrong. It’s a single audit designed from the start to bracket the migration — same personas, same touchpoints, same evaluation criteria, measured before and after, so the comparison is actually apples to apples. That structure is also what makes the business case afterward credible: “here’s exactly what improved, what regressed, and what stayed flat” is a far stronger position than a vague sense that the migration “went fine.”

Where to start

If you have a systems migration coming up and want a credible before-picture while there’s still time to establish one, a Customer Experience Audit scoped to bracket the migration is exactly the right tool — and if you’re trying to build the case for why that baseline is worth the investment before the project timeline locks in, the CX ROI Calculator is a fast way to put a number on what a silent regression could actually cost you.

Download the Customer Experience Audit Checklist as a PDF

Image Credits: Pixabay

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.

The Chief Strategy Officer’s Guide to Strategic Foresight Without a Foresight Department

Leave a reply

The Chief Strategy Officer's Guide to Strategic Foresight Without a Foresight Department

by Braden Kelley and Art Inteligencia

Every CSO I talk to agrees, without hesitation, that strategic foresight matters. Almost none of them have a foresight team. That’s not a contradiction — it’s a budget reality. Foresight sounds like a function you’d staff if you had unlimited headcount: a few analysts, a research subscription or two, maybe a futurist on retainer. Most organizations don’t have that, and most CSOs I’ve worked with have quietly concluded that means real foresight is out of reach for now. It isn’t. What’s actually out of reach is foresight-as-a-department. Foresight-as-a-method is a completely different proposition, and it’s one you can run yourself, starting with your next planning cycle.

The department was never the point

Here’s the thing dedicated foresight teams are actually good at: running a repeatable process for collecting signals, testing them against trends, and building out possible futures in a structured way. That process is genuinely valuable. The team that runs it is not the value itself — it’s just one way of executing the process, and an expensive one. If you can borrow the process without hiring the department, you get most of the value at a fraction of the cost, and you get it fast enough to actually use before your next planning cycle rather than after a hiring search.

What the process actually needs to include

Any real foresight process, department or no department, has to move through the same core stages, whether or not anyone calls it that explicitly:

Signals. Real, specific, early evidence of change — not opinions about the future, not trade press headlines repackaged as insight, but the actual raw material: a shift in customer behavior, a regulatory rumbling, a technology crossing from experimental to viable. Most organizations are already collecting fragments of this informally, scattered across different people’s inboxes and conference notes. The first job of a lightweight foresight process is simply gathering it into one place and being disciplined about separating real signal from noise.

Trends. What do multiple signals, taken together, actually suggest is happening? This is where a lot of informal foresight efforts quietly fail, because it’s tempting to jump straight from one interesting signal to a confident prediction. A trend needs more than one data point behind it, and it needs the room to genuinely disagree about what it means before converging.

Possible futures. Not one future — several, genuinely held as plausible at the same time, even when they contradict each other. This is the step organizations without a formal process almost never do at all, because it feels inefficient to build out three futures when you’re only going to act on one. It isn’t inefficient. It’s the entire point — holding multiple futures seriously is what keeps you from betting everything on the first plausible story anyone tells convincingly in the room.

The probable future, and the preferable one. Eventually you do have to narrow down — most organizations can’t operate against three futures simultaneously forever. But narrowing to your probable future is only half the job. The other half is identifying your preferable future and building a deliberate path toward it, rather than just passively waiting to see which future arrives and reacting once it does.

Building this into your existing calendar, not a new one

You don’t need a standing foresight function to run this. You need a recurring slot on a calendar you already have. Most CSOs I’ve worked with fold this into the run-up to quarterly business reviews as a lightweight signal-check, and run the fuller version — trends through preferable future — as a structured session ahead of annual planning. The key discipline is treating it as a process with defined inputs and outputs, not an open-ended brainstorm, because open-ended brainstorms are exactly what devolves into “opinions about the future” instead of genuine foresight work.

Who actually needs to be in the room

Resist the temptation to run this solo, or with just your immediate strategy team. The signals worth catching often live with the people furthest from the strategy function — sales hearing objections in real deals, support seeing friction firsthand, product watching usage patterns shift. A cross-functional group, even a small one, catches signals a strategy team working in isolation will miss entirely, and it builds organizational buy-in for whatever future the group eventually converges on, which matters enormously when it’s time to actually execute against it.

This is exactly what FutureHacking™ was built to be

I built FutureHacking™ to be precisely this — a structured, visual, collaborative methodology that takes a cross-functional team through signals, trends, possible futures, your probable future, and a real path to your preferable one, without requiring a dedicated foresight function to run it. FutureHacking™ is the art and science of getting to the future first, and it’s built for CSOs running lean, not for organizations with a research budget to spare.

Where to start

The free FutureHacking Signal Picker is the fastest way to run the first stage of this process before your next planning cycle — identifying and prioritizing real signals, at no cost, with no department required.

Something new I’m building

I’m also finishing a second tool — the FutureCanvas Picker — that carries a planning team through the full arc in one sitting: from signals, to the trends they suggest, to a genuine set of possible futures, narrowing to your most probable future, and mapping the path to your preferable one. It’s the closest thing I’ve built to running an entire FutureHacking™ session on your own.

I’m opening early access to a select group first — CSOs and strategic planners actively running planning processes right now — because I want real feedback from people using it 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.

You don’t need a department to see what’s coming. You need a process, run consistently, with the discipline to hold more than one future until you’ve genuinely earned the right to narrow it down.

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.

Why Net Revenue Retention Pressure Should Trigger a CX Audit

Leave a reply

Why Net Revenue Retention Pressure Should Trigger a CX Audit

by Braden Kelley and Art Inteligencia

If you’ve sat in a board meeting in the last few years and watched Net Revenue Retention go up on the screen, you’ve probably also watched the room’s mood shift with it, one way or the other. NRR has become the number investors ask about before almost anything else, and for good reason — it tells you whether the business you already won is actually getting bigger or quietly leaking. What it doesn’t tell you is why. That part gets left to whoever’s in the room to explain, usually on the spot, usually with less certainty than the number itself implies.

NRR is a symptom, not a diagnosis

Net Revenue Retention bundles together expansion, contraction, and churn into one tidy percentage, which is exactly what makes it useful to a board and exactly what makes it useless as a diagnostic on its own. A dip in NRR could mean your onboarding is failing, your support experience is fraying, your product isn’t delivering on renewal-time expectations, or three unrelated things happening in three different customer segments at once. The number tells you something’s wrong. It has nothing to say about what.

Why finance-driven pressure produces finance-shaped answers

Here’s the pattern I see constantly once NRR pressure shows up: the response comes from wherever the pressure originated, which is usually finance or the exec team, not from a customer-facing diagnosis. That means the first instinct is often pricing adjustments, packaging changes, or a renewed push on the renewal playbook — all reasonable moves, and all aimed at the revenue mechanics rather than the experience actually driving the number. You can restructure pricing all you want. If a customer’s day-to-day experience with your product is the real reason they’re not expanding, the pricing change just delays the same conversation to next quarter.

The expansion problem nobody’s diagnosing

Contraction and churn at least generate a paper trail — a downgrade request, a cancellation, a support escalation. Missed expansion is quieter and, in my experience, the more expensive half of an NRR problem. A customer who never asked about the add-on module, never expanded seats at renewal, never became the internal champion pushing for more — that’s not a data point anywhere. It’s an absence. And an absence born from friction they quietly worked around, or an onboarding that never got them to real product value, doesn’t show up in a churn dashboard. It shows up nowhere, until someone finally asks why expansion revenue has been flat for three quarters running.

Why the board wants a story, not just a fix

There’s a specific reason NRR pressure is a better trigger for a full audit than a targeted pricing tweak: a board that’s pushing on this metric usually wants to understand the mechanism, not just see the number move. “We adjusted pricing and NRR improved” is a fragile story — it invites the follow-up question of whether the improvement will hold once the pricing novelty wears off. “We diagnosed exactly where customers were hitting friction before expansion or renewal, and fixed the specific gaps” is a story that survives scrutiny, because it’s causal, not correlational. An audit is what gets you the second story instead of the first.

What this actually means to walk through

Diagnosing an NRR problem properly means treating it as a customer experience question first and a revenue question second: validating who your expanding customers look like versus your flat or contracting ones, mapping where the journey actually breaks down for each, and — critically — walking the onboarding and ongoing product experience firsthand rather than trusting a dashboard that was never built to explain expansion behavior in the first place. Benchmarking against what “good” onboarding and expansion experiences look like elsewhere in the market rounds this out, since a lot of NRR erosion in SaaS specifically comes from customer expectations that were set by a completely different product, not your direct competitors.

Where to start

If NRR pressure is the reason this is on your desk right now, the fastest way to get a real number to bring into that next board conversation is the CX ROI Calculator — it’ll give you a defensible estimate of what the underlying experience gaps are actually costing in retained and expansion revenue. And when you’re ready to find out exactly where those gaps live, a Customer Experience Audit scoped to your onboarding and expansion journey is how you turn “NRR is down” into an actual, fixable answer instead of another quarter of pricing experiments.

Download the Customer Experience Audit Checklist as a PDF

Image Credits: Pixabay

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.

Why Your Strategic Planning Offsite Needs a Foresight Exercise, Not Just Another SWOT

Leave a reply

Why Your Strategic Planning Offsite Needs a Foresight Exercise, Not Just Another SWOT

by Braden Kelley and Art Inteligencia

I’ve sat in more strategic planning offsites than I can count, and I can predict the SWOT exercise before it starts. Someone draws a four-quadrant grid on the whiteboard. The room fills in Strengths and Weaknesses quickly, because those are about the company as it exists right now, and everyone in the room already agrees on most of them. Then it gets to Opportunities and Threats, and the energy noticeably drops — because now the exercise is quietly asking the room to predict the future, and SWOT gives them no actual tool for doing that. So they default to whatever opportunities and threats came up in last year’s version of the same exercise, lightly reworded.

SWOT was never built for what you’re using it for

SWOT is a genuinely useful tool for organizing what you already know about your current position. It was never designed to help a group reason about an uncertain future — there’s no mechanism in the exercise for surfacing real signals, testing which trends they suggest, or imagining more than one way things could unfold. When a room uses it to fill in “Opportunities” and “Threats,” what actually happens is everyone reaches for whatever future feels most familiar or most recently discussed in the trade press, and the exercise quietly becomes a confidence-building ritual around a single assumed future rather than genuine strategic thinking.

The offsite is the right room. It’s the wrong exercise.

Here’s what I’d push back on if someone suggested dropping the offsite structure entirely: getting your leadership team in a room together, away from daily operations, is exactly the right container for this kind of thinking. The problem isn’t the offsite. It’s that the exercise running inside it isn’t built for the actual question a strategic planning session needs to answer, which isn’t “what do we already know about ourselves” — it’s “what’s actually changing around us, and what should we do about it before it’s obvious to everyone else.”

What a foresight exercise does differently

A structured foresight exercise starts somewhere SWOT never goes: the real signals your team is picking up from the market, technology, customer behavior, and adjacent industries — not opinions about the future, but the actual early evidence of it. From there, it asks the room to genuinely work through which trends those signals suggest, and to hold more than one possible future seriously rather than converging immediately on whichever one the most senior person in the room already believes. Only after that does it narrow toward a most-probable future and, critically, a preferable one — the future you’d actually choose to build toward, and the specific path to get there. That’s a fundamentally different exercise than filling in a quadrant, and it produces a fundamentally different kind of strategic plan.

Why this matters more in the room than anywhere else

The offsite is where organizational alignment either happens or doesn’t. A room that’s just filled in a familiar SWOT grid leaves with a comfortable, mostly unchanged view of the future — which feels productive in the moment and shows up as a strategic plan that’s already outdated within a couple of quarters. A room that’s worked through real signals together, disagreed about what they mean, and built a shared view of multiple possible futures leaves with something SWOT structurally can’t produce: genuine, tested alignment on what’s actually likely to happen and what the team is going to do about it either way.

Bringing this into your next offsite

This is exactly the gap FutureHacking™ was built to close — a structured, visual, collaborative foresight methodology any leadership team can run in a room together, without needing a dedicated foresight function or an outside futurist facilitating every session. FutureHacking™ is the art and science of getting to the future first, and the fastest way to feel the difference is to bring it into the room where your planning conversations already happen.

Where to start before your next offsite

The free FutureHacking Signal Picker is a genuinely useful way to arrive at your next offsite with real signals already identified and prioritized, instead of starting the room from a blank whiteboard. It’s the foundational first step of the full methodology, and it’s free.

Something new I’m building

I’m also finishing a second tool — the FutureCanvas Picker — that carries a planning team further into the full arc in a single sitting: 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 closest thing I’ve built yet to running a full FutureHacking™ session in miniature.

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 using it under real offsite 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.

Your next offsite is going to happen either way. The only real question is whether the room leaves with a shared view of one comfortable future, or a genuine head start on several possible ones.

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.

The Hidden Cost of Strategic Planning Built on a Single Future

Leave a reply

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.