The Three Questions Every Operator Should Ask Before Saying Yes

Most operators are not drowning because they lack talent, resources, or ambition. They are drowning because they say yes to everything. The fastest way to cut operational chaos in half is to stop treating every request like a priority and start running each one through a three-question filter before you commit.

These three questions come straight from Richard Rumelt's strategy kernel. They are not theoretical. They are the same diagnostic, policy, and action framework that separates operators who ship results from operators who ship status updates. (If you want to see the kernel applied to competitive strategy, see how Costco uses strategy to say no.)

The Problem: No Filter, No Strategy

Here is what happens in most mid-market organizations when a new initiative lands on the table. Someone in leadership says "we should do this." A VP nods. Resources get allocated. Three months later, the team is running 12 initiatives simultaneously and none of them are moving the needle.

This is Hallmark #3 of bad strategy: mistaking goals for strategy. A list of things you want to accomplish is not a plan. It is a wish list with a budget attached.

The root issue is not that operators pick the wrong things. It is that they never ask whether they should pick anything at all. They lack a decision filter.

Rumelt's Kernel gives you one. It has three parts: Diagnosis (what is actually going on), Guiding Policy (what approach will we take), and Coherent Actions (what specific moves follow from that policy). Translated into an operator's daily reality, these become three questions you can ask in under two minutes.

The Three Questions

Question 1: What is our core challenge right now?

This is the diagnosis. Not "what are all our problems" but "what is the single constraint that, if we solved it, would unlock the most progress?"

Goldratt's Theory of Constraints makes the same point. Every system has one bottleneck. Pouring effort into non-bottleneck areas does not improve throughput. It just creates the illusion of activity. (For a detailed walkthrough of constraint identification, see why your warehouse constraint is probably not what you think.)

Before you say yes to anything, name the constraint. If you cannot articulate it in one sentence, you are not ready to evaluate new commitments.

Question 2: Does this initiative directly address that challenge?

This is the guiding policy test. If the answer is no, you have your answer. Full stop.

Most of the initiatives that flood an operator's plate are good ideas that do not solve the right problem. A warehouse automation project might be valuable in isolation, but if your constraint is inbound supplier reliability, automating the warehouse faster just means you are processing bad inventory more efficiently.

Apply inversion here: instead of asking "could this help?" ask "if we do not do this, does our core challenge get worse?" If the answer is no, the initiative is a distraction, no matter how appealing it looks in a deck.

Question 3: What are we not doing if we say yes?

This is the coherent action check. Every yes is a no to something else. Operators who skip this question end up with a portfolio of half-finished projects and teams stretched across too many fronts.

Map out the tradeoff explicitly. If you say yes to this initiative, which existing priority loses resources, attention, or timeline? If you cannot name the tradeoff, you have not thought hard enough about the commitment.

Second-order thinking matters here. The direct cost of saying yes is the budget and headcount. The indirect cost is the context-switching tax on your team, the management overhead of one more workstream, and the slower execution speed on everything else in the portfolio. (For more on tracing downstream consequences, see second-order thinking for operators.)

What This Looks Like in Practice

Consider a VP of Operations at a regional hardlines distributor, a company doing $1.8B in revenue, moving outdoor equipment, grills, and large-format appliances across 14 distribution centers in the Southeast.

At the start of Q3, her team had 12 active improvement initiatives. New WMS implementation. Carrier diversification program. Returns process redesign. Demand forecasting model upgrade. And eight more, each with its own project lead and weekly status meeting.

Performance was flat. On-time delivery sat at 88%, well below the 95% Elite threshold. Inventory turns were stuck at 4.2x. The team was busy but not making progress on the metrics that mattered.

She applied the three questions.

Question 1: What is the core challenge? After reviewing trailing six-week performance data, the answer was clear: inbound receipt variability. Suppliers were delivering late or delivering the wrong SKU mix 31% of the time, and that single UDE (Undesirable Effect) was cascading into warehouse congestion, mis-picks, and missed outbound windows.

Question 2: Which of the 12 initiatives directly addresses inbound receipt variability? Three. The supplier scorecard program, the inbound appointment scheduling tool, and the receiving dock redesign. The other nine, including the WMS implementation, did not touch the constraint.

Question 3: What happens to the nine we stop? She mapped each one. Two could be paused with no downstream impact. Four were moved to a "next quarter, if the constraint shifts" parking lot. Three were cancelled outright because they addressed problems that would partially resolve themselves once inbound reliability improved.

The result: by the end of Q4, on-time delivery hit 94.2%. Inventory turns improved to 5.1x. The team was running three initiatives instead of 12, and every one of them was aimed at the bottleneck.

She did not work harder. She did not hire more people. She just stopped saying yes to things that did not address the core challenge.

Your Monday-Morning Action

Next time someone asks you to take on a new initiative, ask these three questions before you answer:

1. What is our core challenge right now?
2. Does this initiative directly address it?
3. What are we not doing if we say yes?

Write the answers down. If you cannot answer all three clearly, the answer is not yes. It is "not yet."

The operators who build reputations for execution are not the ones who take on the most. They are the ones who take on the right things and finish them. The three-question filter is how you tell the difference.