I can usually tell you within the first discovery call whether a digital transformation project is going to fail. Not because I’m particularly clever—I’ve just watched this pattern play out enough times that I often recognize the shape of it before anyone else in the room does.
It’s not the technology. It’s not the budget. It’s who’s in the room—and more importantly, who isn’t.
I’ve watched organizations pull together transformation teams that were genuinely excited about the work ahead. They secured eight-figure budgets, lined up partners across the globe, built momentum that felt unstoppable. Then one decision maker’s spouse said “I don’t trust that agency” over dinner, and within a week the entire project was frozen. Budget pulled, team disbanded, momentum gone.
That’s not an edge case. That’s a pattern I’ve seen play out across enough engagements that I now look for it deliberately.
The Real Failure Point Lives in the Org Chart
The data backs this up in ways that should make the industry uncomfortable. 70% of digital transformation initiatives fail to meet their objectives. Organizations have burned through $2.3 trillion on transformation while maintaining an 84% failure rate. Those aren’t rounding errors—those are structural problems the industry keeps trying to solve with better technology instead of better understanding.
The industry blames technology adoption when projects fail. They point to change management issues. They talk about user resistance like it’s a character flaw instead of a signal.
I’m telling you it’s simpler and harder than that.
When I start a transformation engagement, the first thing I do is map two separate org charts—not because I enjoy organizational sociology, but because the gap between them tells me whether this project has a chance. The formal chart shows who has official go/no-go authority on paper. The informal one shows who actually drives conversation inside the organization—the opinion leaders, the trusted advisors, the board members who don’t show up on any diagram but absolutely show up in every decision that matters.
The bigger the gap between those two maps, the less likely transformation will ever take hold. I’ve learned to measure that distance early.
If highly opinionated, influential people aren’t in direct authority to make decisions about transformation, you’re not really leading the project—you’re watching it get managed from the sidelines. Sometimes from the stands. And you’re going to lose momentum to forces you can’t see and conversations you’re not part of.
The Detractor You’re Not Seeing
I’ve seen this in family businesses where one decision maker was genuinely eager to transform part of the operation. They had vision, they had energy, they had budget. What they didn’t have was everyone else on board with them. The vision wasn’t shared—it was imposed, or assumed, or just never really communicated in a way that built actual agreement.
Sometimes the detractor is protecting something real. They’re afraid that changing the organization will eliminate what makes it special—an indefinable quality that built loyalty over years or decades. They’re worried about letting down long-time customers by not doing things exactly as they’ve always done them. That fear isn’t irrational. It’s often rooted in something true about the organization’s history or identity.
Here’s what I’ve learned after watching this dynamic across dozens of organizations: they’re not usually right, but they’re not often wrong either. There’s usually a seed of legitimate concern buried in the resistance.
If you overlook that during discovery—if someone in that sphere of influence hasn’t been heard or acknowledged, or if their concern gets dismissed as mere resistance to change—that seed doesn’t just sit there quietly. It grows into resentment. I’ve watched people go from skeptical to actively working to prove the transformation will fail, and the shift happens precisely because they felt ignored when it mattered.
That’s why I map the blast radius early. Who gets a vote? Who has informal influence? Who are the people driving conversation about anything that happens inside this organization? Where does opinion actually form, versus where does it get officially recorded?
That map saves significant headaches later—or it tells me the project isn’t viable before we’ve invested months building toward a launch that will never happen.
When we’re doing user discovery for a website transformation, nothing in the rules says we can’t bring in one of those potential detractors as part of the interview process. We sit down with them. We listen to their concerns. We ask what they’re afraid will be lost. Then we draw them back to the data we’re using to drive decisions—not to prove them wrong, but to find the common ground between what they’re protecting and what users actually need.
Often it comes down to something straightforward—somebody feels valuable and hasn’t been heard. We may not be able to alleviate every concern they raise. We may not even agree that all their concerns are real problems versus inherited assumptions. But the act of hearing them out and bringing their voice back into the planning process gives us the ability to diffuse that tension early. Or at minimum, it helps us identify where the land mine is buried before we step on it during implementation.
When Leadership Wants Transformation for the Wrong Reasons
I’ve watched clients select transformation partners because they want to hang out with the hottest agency in town. Because that prospective partner has access to a club box at their favorite sporting venue. Because that designer worked on a project for a brand the decision maker admires and wants to be associated with.
Early in discovery, you have to figure out whether you can win a person over to a story that’s built from real-world data—or whether they’re living out a personal fantasy where someone gave them a budget and now they get to wish cast and daydream and spend someone else’s money on a process that makes them feel important. Those are two fundamentally different projects, and only one of them has a chance of serving users well.
The work we do isn’t glamorous. It’s not full of shiny conference rooms and applause. It’s grinding out a solution in the most effective way possible for the users you ultimately want to serve—and that means spending time in spreadsheets and user interviews and uncomfortable conversations about what’s actually broken.
Early in our discovery process, if we determine that a prospect is undertaking transformation with outcomes in mind that don’t really involve the people they’re trying to serve, we respectfully decline those projects. We’ll say “We don’t think we’re going to be a good fit for you.” Sometimes we’ll recommend a partner agency or someone we know who might be better suited to what they’re actually looking for.
If a client is focusing on internal politics, or on something that will make them look good to their peers, or on personal taste instead of data-driven insight about what their audience actually needs—they’re not ready for the kind of work that leads to sustainable transformation. And pushing forward anyway just burns time and trust on both sides.
The Golden Gut Doesn’t Really Exist
I came up through radio in the 1990s and early 2000s, and one of the transformations I watched reshape the entire music industry was the shift from broad listener surveys to SoundScan—an actual phone-based data-gathering system that pulled real sales numbers from retailers and measured what actually got played on radio stations versus what program directors claimed was popular.
The transformation was wild. It completely upended who got airtime and why.
SoundScan ushered alternative music, hip hop, and rap onto mainstream American radio in ways that hadn’t been possible before. Up until that point, professional tastemakers had systematically prevented a lot of those artists from getting significant airplay—not because audiences didn’t want to hear them, but because the gatekeepers didn’t believe they belonged there. Once you had actual data showing what was selling, bands like R.E.M. and Public Enemy found their way into the mainstream. You couldn’t argue with the numbers. They were moving units.
It’s the same dynamic when a client is working on a website transformation.
If a client knows their business—if they’re paying attention to what actually drives their customers, their stakeholders, the people they’re trying to reach—they can tell me more than just what their gut says. If all they can offer is instinct without any supporting evidence, I’m going to assume one of two things: they don’t know what’s actually happening in their customer journey, or they don’t particularly care as long as the end result matches their personal vision.
If they don’t care, they’re not a good fit for the way we work. If they don’t know, we can help them design data gathering to validate whether their instincts are directionally correct or if they need some calibration based on what users actually do versus what leadership assumes they do.
The tell comes when you show someone data that contradicts their taste and they respond with “I just want what I want.” Or they point at a specific website—usually something built by a team with vastly different resources—and say “I want my site to look and work exactly like that.”
Sometimes I have to tell them directly: the website you’re pointing to has four dozen in-house developers working on it every single day. You’re trying to achieve that same level of polish and functionality in a project that’s a fraction of that scale. The aspiration isn’t wrong, but the expectation about what’s possible within your constraints needs to be recalibrated.
If we can bring the client back to the reality of where they are and what they’re prioritizing—if we can have an honest conversation about what’s achievable given their actual resources and organizational capacity—we can do meaningful work together. If they really want that level of transformation and they need to show return on the investment they’re proposing, that’s not just a matter of our team doing the math for them. That’s them having to build the business case for their investors, their board, their shareholders. We can help frame it, but we can’t want it more than they do.
The Gap Between Aspiration and Reality
Sometimes that gap between what someone wants and what’s actually achievable reveals something deeper than a budget mismatch. Sometimes it reveals the difference between a leader who’s genuinely aspirational about their organization’s potential and someone who’s become completely untethered from the operational reality underneath them.
I’ve worked with leaders who were almost completely detached from the day-to-day reality their teams were navigating. They operated inside a bubble of their own making. But here’s what made it work—they’d built a world around themselves where they had genuinely talented people who could translate their vision into something executable. Those translators became the crucial layer between aspiration and implementation.
In those situations, success comes down to making sure your communication lands with both audiences at once—the practical people who are going to actually implement the project, and the visionary leaders who might be operating at a more conceptual level but who have that instinct for what could resonate with audiences. Both perspectives matter. The trick is keeping them connected instead of letting them drift into separate conversations.
The real challenge is making sure those big ideas get translated into something realistic and tangible without constant iteration that expands scope until the project collapses under its own weight. Vision needs boundaries, or it just becomes an expensive way to avoid shipping anything.
What Digital Transformation Actually Exposes
The hardest thing I’ve had to learn how to communicate is when there’s an unspoken fault line running through the organization—something broken in the underlying culture or operations—that digital transformation isn’t going to fix on its own. The new website or platform will just make that existing problem more visible to everyone, especially to the people you’re trying to serve.
This plays out most clearly on the customer experience side, where the gap between organizational assumptions and user reality becomes impossible to hide.
Here’s a pattern I’ve seen repeatedly: an e-commerce organization decides to offer customers the option to pay extra for expedited shipping. It seems like a straightforward value-add. They set up three tiers during checkout—standard shipping that’s free, two-to-four-day shipping for an additional $5, overnight shipping for $20 extra.
Customers see those options and feel like they have control over their experience. They’re willing to pay for speed when it matters to them.
But what leadership doesn’t realize—or hasn’t thought through carefully enough—is that regardless of which shipping speed the customer selects, there’s still a delay at the warehouse level. Orders come through, but they sit in a queue before anyone picks and packs them. That delay might be two days, might be three, depends on warehouse staffing and volume. What you intended as a helpful feature just created a structured opportunity for customers to feel disappointed. They paid extra for expedited shipping. They’re expecting their package to arrive the next business day. What they don’t know is there’s hidden friction in your fulfillment process that makes that timeline impossible—and you never told them it existed.
The digital transformation didn’t create that problem. The operational gap was always there. What the transformation did was make it visible and measurable in a way it wasn’t before. Now customers can see the promise you made and feel the disappointment when you don’t deliver on it.
When I uncover these kinds of gaps during discovery—problems that digital transformation will expose rather than solve—I have to tell leadership something they usually aren’t expecting to hear: your new website is going to make your operational problems more visible to the people you’re trying to serve. If you’re not prepared to fix what’s broken behind the scenes, we’re just building a faster way for customers to discover you can’t deliver on your promises.
That’s not a conversation most transformation projects plan for. But it’s often the most important one we have.
The Luxury of Delivering Bad News
I’m usually more prepared for that conversation than the client is, which gives me a particular kind of leverage. There have been multiple times when I’ve had to be the person who—because I’m coming in as an outside consultant—has the relative luxury of delivering bad news that the client’s own team doesn’t feel safe saying out loud.
I’ve been in engagements where my findings exactly mirrored what an internal team had already discovered and reported. But because I’m an outside subject matter expert with no political ties inside the organization, I’m perceived as more neutral, less biased, less threatening. I can say things that might get someone fired if they said it internally. That asymmetry matters.
If it’s genuinely the kind of bad news that would cost someone their position if they delivered it themselves, the worst outcome for me is that my agency gets dismissed from the project and whoever comes in next has to pick up the pieces we’ve left behind. That’s still a better outcome than watching a once-trusted team member lose their job for telling the truth about what’s broken. I can absorb that risk in ways they can’t.
More often than not, though, it turns into something more productive—an opportunity to bring people together around a problem they simply had a blind spot about. They genuinely didn’t know it was happening, or they knew but hadn’t had sufficient reason to prioritize fixing it until transformation forced it to the surface. Once it’s named and visible, it becomes something the team can actually work on together.
What Actually Needs to Change
Digital transformation fails before it starts because organizations keep looking at the wrong problems. They’re solving for symptoms instead of addressing the structural issues underneath.
They get focused on platforms and feature sets. They get excited about AI deployment and new tools that promise efficiency gains. They measure success by whether they hit launch dates and stayed within budget parameters.
But transformation doesn’t fail because the technology wasn’t sophisticated enough or because the budget wasn’t large enough. It fails because of the system surrounding the technology—the organizational architecture that determines whether new capabilities can actually take hold and create sustained change.
It fails when informal power structures don’t align with formal authority. When potential detractors get overlooked during discovery and turn into active saboteurs during implementation. When leadership wants transformation for vanity or competitive positioning instead of genuine user need. When personal taste masquerades as strategic direction. When aspiration becomes so disconnected from operational reality that the gap can’t be bridged within available resources.
The organizations I’ve seen succeed at transformation—the ones that actually make it past launch and into sustained improvement—do something fundamentally different from the beginning. They map influence and power dynamics before they map features and user flows. They surface uncomfortable truths during discovery instead of papering over them with optimistic timelines and new platform capabilities. They bring actual data into conversations where gut instinct and personal preference used to be the deciding factors. They acknowledge the gap between where they currently are and where they want to end up, and they’re honest—sometimes painfully so—about what it’s going to take to close that distance.
They understand something crucial: the website isn’t the transformation. The platform isn’t the transformation. Those are just the places where all your unresolved organizational problems become visible to the people you’re trying to serve. They’re the surface where internal dysfunction meets external expectation, and that friction either builds trust or destroys it.
If you’re not ready to address those deeper problems—if you’re hoping technology alone will paper over gaps in your culture, your operations, your decision-making structures—you’re not ready for transformation. And no amount of budget is going to change that reality.
Need to understand what your digital presence is actually communicating to the people you’re trying to serve?
You don’t have to leap all the way into a major transformation project. The Website Reality Check audio series shows you what’s working, what’s broken, and what’s quietly costing you trust—from the perspective of someone who’s mapped these patterns across hundreds of organizations and learned to recognize the gap between intention and reality.
