I Once Believed Information Was Power

For a long time, I believed information was power.

And to be fair, I had good reason to believe it.

I began my career in technology at a time when organizations were becoming increasingly dependent on information, systems, data, and technology to make decisions and compete. I learned to look at businesses through processes, requirements, systems, dependencies, risks, metrics, and outcomes.

• A report could reveal a problem.
• Data could expose a trend.
• A process map could show where something was breaking.
• Requirements could uncover what a system actually needed to do.
• Metrics could tell us whether something was improving.

And when you worked across complex organizations, information gave you something incredibly valuable:

For someone like me, who naturally wanted to understand how things worked, it was fascinating.

• I wanted the information.
• I wanted to understand the system.
• I wanted to know what happened before, what happened next, where the dependencies were, what was missing, and why the outcome wasn’t matching what everyone expected.

I became very good at finding information.

But eventually I learned something much more important.

And that realization changed the way I understood transformation.

The System on Paper Is Not Always the System in Reality

One of the earliest lessons of my career was that there are usually two versions of an organization.

There is the organization represented in documentation.

And then there is the organization that actually exists.

On paper, a process might look perfectly logical.

• Step one goes to step two.
• A request moves from one department to another.
• A system generates information.
• Someone reviews it.
• Someone approves it.
• Something gets implemented.
• Everything appears connected.

Then you sit beside the people actually doing the work.

And suddenly the process looks very different.

• There is a spreadsheet someone created because the official system doesn’t provide what they need.
• There is a manual step no one documented.
• There is an approval everyone knows they need even though it isn’t formally part of the process.
• There is a workaround created years ago after something failed.
• There is information being entered twice because two systems don’t communicate.
• There is an employee who has become the unofficial expert because she is the only person who remembers why something works the way it does.
• There is a local market doing something differently because the corporate process simply doesn’t work in its environment.
• And there are decisions being made every day that will never appear in a process diagram.

The documentation isn’t necessarily wrong.

It is simply incomplete.

Because organizations are not made only of processes and systems.

They are made of people interacting with processes and systems.

That distinction became fundamental to the way I worked.

I Learned to Go Where the Work Was Happening

Later in my career, I had opportunities to work across different countries and cultures, particularly throughout Latin America.

I was coming from the corporate environment in the United States, often working on large technology and transformation initiatives.

It would have been easy to arrive with the headquarters perspective.

• Here is the process.
• Here is the methodology.
• Here are the requirements.
• Here is what needs to happen.

But I discovered very quickly that I could learn more by sitting beside the people doing the work than I ever could by simply reviewing another presentation.

• I talked with people across roles and organizational levels.
• I asked them to show me what they actually did.
• Not what the procedure said they did.
• Not what someone at headquarters believed they did.
• What they actually did.

Those conversations changed everything.

Because once people trusted that I wasn’t there simply to tell them what to do, they showed me the organization I could never have discovered from a report.

The People Closest to the Work Often Hold the Missing Information

• Executives see the organization from one level.
• Managers see another.
• Technology teams see another.
• Operations sees another.
• Customers see another.
• And the person completing a seemingly small step in a process may understand something no one else knows.

Every perspective contains part of the truth.

That is why transformation becomes dangerous when we assume organizational level determines the value of someone’s insight.

• Sometimes the person with the most important piece of information isn’t sitting in the meeting.
• Sometimes they aren’t even aware that what they know is important.
• They simply know:

“If we do it that way, this happens.”

That sentence can be worth more than a hundred slides.

Because they have lived the process.

• They know where it bends.
• They know where it breaks.
• They know what customers complain about.
• They know which workaround everyone uses.
• They know what happens during the last five minutes of a transaction.
• They know what doesn’t make sense.
• And they often know exactly what could make it better.

But someone has to ask.

And more importantly, someone has to listen.

Listening Became a Form of Data Collection

My technology background never stopped being valuable.

If anything, it became more valuable.

But my definition of information expanded.

I began to understand that data wasn’t limited to what could be extracted from a system.

• A conversation contains data.
• Behavior contains data.
• Resistance contains data.
• Confusion contains data.
• A workaround contains data.
• A recurring complaint contains data.
• A question people keep asking contains data.
• Silence in a meeting can contain data.

The difference between what someone says publicly and what they explain when you sit beside them can contain enormous amounts of data.

And patterns across those observations can reveal something a dashboard may never capture.

This does not mean replacing quantitative information with intuition.

It means recognizing that human information is part of the system too.

• The numbers tell us something.
• The process tells us something.
• The technology tells us something.
• The customer tells us something.
• The employee tells us something.
• The leader tells us something.

Transformation requires us to understand how those pieces interact.

Resistance Is Information Too

One of the easiest mistakes to make during transformation is to label people as resistant.

• They don’t want the new system.
• They don’t like the new process.
• They aren’t adopting the change.
• They keep questioning the decision.

Therefore:

They are resistant to change.

Sometimes they are.

But sometimes resistance is telling us something important.

• Maybe the new process creates a problem no one anticipated.
• Maybe the employee has information the project team doesn’t.
• Maybe the technology makes sense conceptually but creates five additional steps operationally.
• Maybe no one explained why the change is happening.
• Maybe employees were trained on which buttons to press but never understood the new business process.
• Maybe the organization changed someone’s responsibilities without giving them the authority or resources necessary to perform them.

Maybe people aren’t resisting the future.

Maybe they are responding to a gap in the transformation.

That changed the questions I asked.

Instead of:

“Why won’t they adopt this?”

I became more interested in:

“What is their response telling us?”

That doesn’t mean every objection should determine a decision.

It means every meaningful pattern deserves to be understood.

There Is a Difference Between Hearing and Understanding

Organizations collect enormous amounts of feedback.

• Surveys.
• Meetings.
• Interviews.
• Focus groups.
• Customer reviews.
• Employee engagement studies.
• Performance metrics.
• Exit interviews.
• Support tickets.
• Assessments.

But collecting feedback does not automatically create understanding.

Understanding requires context.

If an employee says:

“Communication is terrible.”

What does that actually mean?

• Too little communication?
• Too much?
• Too late?
• Different messages from different leaders?
• No opportunity to ask questions?
• Decisions without explanation?
• Information buried in email?
• Managers learning about changes at the same time as employees?

The word communication is only the beginning of the investigation.

The same applies to:

• “The system doesn’t work.”
• “Leadership doesn’t listen.”
• “The process is too complicated.”
• “Customers don’t understand.”
• “People aren’t engaged.”

Each statement is a signal.

The job is not simply to record the signal. The job is to understand the system producing it.

Data Without Context Can Lead Us in the Wrong Direction

• I still believe deeply in data.
• I believe in measurement.
• I believe in metrics.
• I believe in analytics.
• I believe in evidence.

But I also learned that numbers without context can create false confidence.

• A metric can tell us performance declined. It may not tell us why.
• An employee survey can tell us engagement changed. It may not reveal the experience behind the answer.
• A project dashboard can show green. The people implementing the project may already know something is going wrong.
• A customer satisfaction score can improve while a particular part of the customer journey is quietly deteriorating.

The answer isn’t to distrust data.

It is to interrogate it more intelligently.

That is when information begins becoming insight.

The Most Powerful Question Became “Why?”

Technology taught me to ask:

• What?
• What is the requirement?
• What is the process?
• What is the issue?
• What is the data telling us?

Transformation taught me to keep going.

And then:

What is underneath the why?

Because sometimes the first answer isn’t the root cause either.

That curiosity became one of the most important tools I carried from technology into transformation.

Technology Changes Faster Than Human Nature

Today we are entering another extraordinary period of technological change.

Artificial intelligence is giving organizations access to information, analysis, automation, prediction, and knowledge at a scale we could barely imagine earlier in my career.

And I find that incredibly exciting.

But it also makes this lesson even more important.

Because having more information does not automatically mean we have more understanding.

• AI can identify patterns.
• Systems can process enormous amounts of data.
• Dashboards can become more sophisticated.
• Organizations can automate processes that once required teams of people.

But leaders will still need to understand:

• What people need.
• What they fear.
• What motivates them.
• What they misunderstand.
• What creates trust.
• What destroys it.
• Why they resist.
• Why they engage.
• How culture affects behavior.
• How change affects identity.
• And how decisions made in one part of an organization affect human beings somewhere else in the system.

From Information Architecture to Transformation Architecture

Looking back, I can see the bridge much more clearly now.

My early career taught me how to understand systems.

• Technology taught me structure.
• Requirements taught me to ask better questions.
• Process work taught me dependencies.
• Data taught me patterns.
• Governance taught me accountability.
• Business Readiness taught me that technical completion and organizational readiness are not the same thing.
• Working across countries and cultures taught me context.
• Entrepreneurship taught me reality.
• Hospitality taught me experience.
• Wellness taught me how deeply human capacity affects performance.

And people taught me something none of those disciplines could teach alone:

Organizations do not transform. People transform organizations.

That doesn’t diminish the importance of technology, systems, governance, data, process, or methodology.

It explains why they must work together.

• A technically perfect solution that people cannot adopt is not a successful transformation.
• A brilliant strategy the organization cannot execute is not transformation.
• A process designed without understanding the people performing it will eventually expose its weaknesses.
• A change implemented without understanding culture will encounter consequences that may never have appeared in the project plan.

This is why my work today looks at transformation as an interconnected architecture.

• People.
• Processes.
• Technology.
• Knowledge.
• Governance.
• Leadership.
• Culture.
• Performance.

They cannot be separated as easily as organizational charts sometimes suggest.

Information Is Still Power. Understanding Gives It Direction.

I no longer believe my original idea was wrong.

Information is powerful.

But information alone is incomplete.

• Information gives us visibility.
• Patterns give us insight.
• People give us context.

Understanding connects them.

And perhaps wisdom is knowing when we need each one.

That is the lesson I carried forward from those early years into everything I have built since.

When I enter a new organization, business, program, or problem today, I still want to see the information.

• I want the data.
• I want the process.
• I want the systems.
• I want the metrics.
• I want the documentation.

But then I want to talk to the people.

• Not only the executives.
• Not only the experts.
• Not only the people presenting the strategy.

I want to understand the people who experience the system every day.

Because somewhere between the information we collect and the people living inside that information is usually where the real story exists.

And once we understand that story, we have a much better chance of creating transformation that actually works.

Transforming People. Organizations. Systems.