Evaluation: Why You Cannot Transform What You Cannot See

You Are Not Seeing Your Organization Clearly

Many leaders are transforming a version of their organization that does not actually exist. The dashboards look fine. The roadmap looks impressive. Everything looks under control. But is that what your customers are actually experiencing right now? In 2024, Air Canada found out the hard way what happens when the answer is no. And what they discovered goes far deeper than a chatbot mistake.

Welcome to Digital Transformation for Leaders, a journey from insight to strategy to execution. I am Tamer Badawy, strategic IT and transformation leader and author of Life in the Digital Bubble. We are in Phase 1 of the transformation journey, Recognize Potential, and this is Step 3. In the first two steps, we looked at the forces outside organization: the changing expectations of society, and the technology capabilities that create real value when connected properly to the business. In this step, we look inside the organization. Because before you choose a strategy, approve a roadmap, or scale AI across the whole organization, you need to answer one honest question: what is actually happening here? Not what the reports suggest. Not what gets presented in the quarterly review. But how your customers, employees, processes, data, and decisions are actually working together in reality. That gap between the organization you think you have and the one your customers experience is where digital transformation quietly fails. And it fails before a single line of code is written.

Air Canada’s Chatbot Was Not the Problem

In 2024, Air Canada was taken to a tribunal, not because of a technology failure, but because of an organizational one. And here is what happened. A passenger who had lost a family member asked the chatbot about bereavement fares. The chatbot gave information that did not match the airline’s actual policy. He booked his flight based on that answer. When he requested the discount he had been promised, Air Canada refused, arguing that the chatbot was a separate entity and its responses were not official company policy. The tribunal rejected that completely. Air Canada was held responsible.

Now here is what most people miss. That chatbot did not cause this. It just made it visible. The problem already existed inside the organization, and it came down to four questions nobody had a clear answer to: which information is current? Which policy is the actual source of truth? Which system can be trusted when they conflict? And who owns the answer once technology delivers it to a customer? AI did not create the confusion. It exposed it, in front of a paying customer, in a tribunal, on the record. This was not a chatbot failure. This was a leadership failure. And in most complex organizations right now, these gaps exist. They just have not surfaced yet.

Your Team Has Data. But No One Sees the Full Picture

Here is a pattern that exists in every complex organization, and no leadership team talks about it openly. Every function has its own dashboards, its own KPIs, its own version of how things are going. Your head of sales sees growing demand. Your head of operations sees a team that has not slept for weeks to keep up with it. Your CFO sees stable margin. Your CTO sees a system held together with workarounds that nobody has had the time to fix. Same organization. Nobody is lying. Nobody sees the full picture.

When you put them together in a leadership meeting, you do not get a clear picture of reality. You get five partial views, each defended by someone measured against their own slice. This is what I call the illusion of clarity. The organization has data, but it doesn’t have one shared understanding of where value is being created, where it is blocked, or where transformation is most needed. Without that, transformation does not fail dramatically. It fails quietly, through the misalignment of priorities and decisions that make sense in one department and create problems in another. Data without a shared view is just noise with good formatting.

Ask Your Team This. The Answer Will Shock You

Here is a test that can expose the real maturity of your transformation in less than ten minutes. Ask your CFO, your head of operations, and your head of customer support one question: how well are we actually delivering to our most important customer right now? Do not let them align first.

If you get three different answers, you do not have a dashboard problem. You have a leadership problem, because different answers mean different definitions, different data sources, different assumptions. One team measures delivery when the product leaves the factory. Another when it reaches the customer. A third against the originally promised date. All three believe they are right. But you cannot steer a transformation with three versions of reality. This is the source of truth problem. When leaders cannot agree on what’s true today, every strategic conversation becomes a negotiation about which data to believe rather than what to do next. Evaluation starts by fixing that, not with perfect data, but with data trusted enough to make better decisions together. Run the test. You will likely be surprised.

Stop Writing Reports. Start Seeing Reality

Most assessments produce the same output: long reports, maturity scores, traffic light dashboards that tell you what you already suspected but cannot act on. If I were advising a leadership team on where to begin, I would not give them a two hundred question maturity model. I would ask them to look at the organization through five lenses. This is the same diagnostic view I use with leadership teams before they commit to a transformation roadmap, because without it, strategy becomes guesswork. And I call it the Transformation Reality Map.

The first lens is customer reality. What do customers really experience? Where do they wait, complain, or lose trust? The second lens is process reality: how work really happens, not how it is documented. Where are handovers breaking down? Where are people compensating for systems never properly connected? The third lens is data reality: which data to trust, which data is duplicated, delayed, or defined differently depending on who you ask. The fourth lens is technology: which systems genuinely support the business, which create friction or limit what’s possible? The fifth lens is operating model reality: who actually owns outcomes? Who has the authority to resolve conflicts and change how work happens?

Together, these five lenses move leadership from opinion to evidence. The output is a ranked list of customer friction, process breaks, data gaps, technology constraints, and ownership problems, ordered by business impact. Most organizations have the data to build this map. They have just never looked at it all at once.

Stable Revenue, Broken Business. Here Is What They Found

Here is what a weakening business looks like before anyone realizes it’s actually weakening. A logistics company. Revenue stable. Dashboard looks reasonable. Walking into that leadership meeting would feel comfortable. But when the team applied the five lenses, here is what they found.

Customer lens: complaints about late deliveries rising, not dramatically, consistently. Nobody had connected that trend to anything else. Data existed somewhere, just not where it was needed, and never in time. Process lens: operations firefighting exceptions every day, manually. Data lens: customer service could not explain delays before customers called. The process looked clean on paper, but in reality, the process was held together by people compensating for systems that did not talk to each other. Technology lens: the tracking system had never been integrated with the delivery platform. IT knew it. Nobody else did. Operating model lens: nobody owned the end to end delivery experience. Every department owned their part, but nobody owned the outcome the customer cared about.

Five lenses, five findings, each manageable in isolation. Together, they told a different story than the revenue dashboard. The team did not need more data. They needed a connected view of what they already had. Once they had it, priorities became obvious. And that is what the Transformation Reality Map is designed to produce.

AI Will Not Save You From This

At some point in almost every transformation conversation, someone says, can we use AI to get better visibility into this? The honest answer is yes, but there is a condition most organizations skip past. AI does not show reality. It amplifies what’s already there. If your data is fragmented, AI makes decisions from that fragmented data faster and at greater scale. If metrics are misaligned, AI accelerates those misaligned decisions. If nobody owns the output, AI produces outputs nobody feels responsible for. If processes are broken, AI makes broken processes move faster.

This is not about avoiding AI. It’s about not skipping the step that makes AI actually work. Before you ask what AI can predict, ask a more important question: can we trust the reality we ask AI to learn from? I have seen organizations investing heavily in AI while sitting on fragmented data, undefined ownership, and processes never properly designed. The AI worked exactly as intended. It amplified a version of reality no one bothered to clean up first. Better algorithms cannot compensate for weak definitions, fragmented data, and unclear ownership. This is not a technology limitation. This is an organizational one. And the cost is not just a failed AI project. It is an entire transformation program that stays busy without moving forward.

Your Leadership Team Is Not Ready. Here Is How to Know

Before any leadership team moves from technology possibilities to transformation strategy, five questions need honest answers, not as a formal exercise, but as a genuine leadership conversation.

First, can we distinguish between symptoms and root causes? Most organizations treat symptoms. They digitize flawed services. They automate broken processes. If you cannot separate symptom from cause, you will keep solving the wrong problems faster. Second, do we have one trusted view of the metrics that matter, not another dashboard? One trusted baseline the entire leadership team accepts as the starting point for every strategic conversation. Third, do we understand how value flows across the organization, from input to outcome, not within departments, end to end? Because that is where the breaks are hiding. Fourth, do we see where customers, employees, and operations experience friction? Not where we assume they do, where they actually do, based on evidence. Fifth, do we know who owns the most important transformation outcomes? Not who sponsors the project. Who is accountable after go-live, when the budget is spent and the consultants have left?

These are not IT questions. They are leadership questions. And if a leadership team cannot answer them clearly, then they are not ready to choose a direction. They are ready to do the evaluation that makes that choice possible.

You Cannot Transform What You Refuse to See

Phase 1 is about one thing: building the clarity that makes every decision after it worth making. In Step 1, we looked outside. Society has already changed the expectations of your customers. Employees and markets are not waiting for your roadmap. In Step 2, we looked at technology, not as a shopping list, but as a system of capabilities that only creates value when it connects properly to the business. In Step 3, we moved inside, because the gap between the transformation you plan and the one that truly delivers value almost always comes down to one thing: how clearly you understand and see the organization before you start changing it.

Three steps. Three evidence based tools that every leadership team can use immediately. That is the Digital Expectations Assessment, the Technology to Capability Map, and the Transformation Reality Map. If you want to work through any of these with your leadership team, all three are available at tamerbadawy.com.

Closing

Most leaders entered Phase 1 confident they understood their organization. Those who worked through these three steps honestly know something different by now. Phase 2 is where the real decisions begin. Not which technologies to buy. Not which projects to launch. But which playing field to choose, what to prioritize, and what to deliberately leave behind. That is strategy. And that’s exactly where we are going next.