Early in my career, I learned one of the most valuable lessons I've ever received about communicating with executives. In a meeting with a CEO, he asked me for a particular set of data.

I responded honestly. "I can't give you that." He wasn't happy.

After the meeting, he pulled me aside and offered some advice. "When a CEO asks you for data, your answer should be yes." At first, I thought he was asking me to promise something impossible. Eventually, I realized he was teaching me something much more important.

I Was Answering the Wrong Question

My response was technically correct. The data didn't exist.

• It had never been collected electronically.

• There was no report to run.

• No dashboard to query.

• No database containing the answer.

So I answered the question I thought had been asked. "Can you give me this data?" "No."

The problem was that wasn't the question the CEO was really asking. He wasn't asking whether a report existed. He was trying to understand the business.

A Few Days Later...

I came back with a different answer. I had contacted Deloitte. Their estimate was straightforward. A team of forensic accountants could reconstruct the information from paper records and employee interviews. It would take approximately six months. The estimated cost was roughly $500,000. I presented the information.

The CEO smiled. "Never mind." The conversation was over.

Not because I had said no. Because I had given him enough information to make a decision.

The Difference Between Refusing and Framing

Since that day, I've tried to avoid telling executives "no" even when the answer is almost certainly going to be no. Instead, I explain what "yes" actually requires.

• I'd be happy to provide that information.

• The challenge is that we never captured it electronically.

• We can reconstruct it.

• It will require approximately six months of work and significant consulting expense.

• How important is this information?

• What's the available budget?

Notice what changed. The answer didn't change. The framing did.

The conversation moved from: Can we?

To: Should we?

Every "No" Has a Price

I've noticed that great operators rarely respond with: "That can't be done." Instead, they respond with:

• "It can absolutely be done."

• "It will require twelve engineers."

• "Six months."

• "And approximately two million dollars."

Those are very different conversations. One ends discussion. The other enables decision-making.

The Hidden Cost of Missing Data

There was another lesson hiding inside that conversation. Years earlier, someone had decided not to collect that information. At the time, it probably made perfect sense. The data wasn't important then.

Years later, however, leadership wanted answers. Now the cost of not collecting the information had become painfully expensive. I've come to think of this as data debt.

Much like technical debt, the decision to postpone investment feels inexpensive in the moment, but the bill arrives years later. Usually when the information becomes strategically valuable.

Leaders Don't Need Perfect Answers

One of the biggest misconceptions about executive leadership is that CEOs expect perfect information. Most don't. Rather, they expect clarity, they expect tradeoffs, they expect someone to explain the implications of different choices.

Sometimes the answer really is impossible. Sometimes it simply isn't worth the cost. Helping leaders distinguish between those two situations is incredibly valuable.

The Job Isn't to Say Yes

Ironically, my CEO wasn't teaching me to always say yes. He was teaching me never to stop the conversation prematurely. Leadership isn't telling executives what they can't do. Leadership is helping them understand what it would take to do it.

Those are very different skills. One ends decisions. The other enables them.

And that's what great operators do.

Recommended Articles

1. Leadership Lessons: The Moment a Leader Realizes They No Longer Know Everything

2. Leadership Lessons: Why Leaders Must Sometimes Slow the Organization Down

3. Leadership Lessons: The Quiet Power of Operational Discipline

4. Growth & Scaling: When Organizational Design Becomes a Competitive Advantage

5. Leadership Lessons: Why Good Leaders Design Systems Instead of Solving Problems

6. Leadership Lessons: The Difference Between Authority and Influence

7. Why Revenue Problems Rarely Start in the Sales Team

About Carter Cathey

Carter Cathey is a sales and revenue leader with more than 20 years of experience helping market research, technology, and private-equity-backed businesses scale revenue, improve operations, and build predictable growth systems.

Throughout his career, he has led sales transformation initiatives, pricing strategy projects, subscription business model transitions, operational redesign efforts, and commercial growth programs.

He writes about leadership, organizational design, business systems, data-driven decision making, and the challenges companies face as they scale.

Learn more about Carter Cathey

• About Page

• Resume

• Case Studies

• LinkedIn