Executive Questions That Should Never Be Ad-Hoc

If leadership asks it every Monday, it is not a fire drill. It is a standing question. Standing questions belong in the model. Heroic extracts belong to surprises.

The pattern is familiar. The same cash, backlog, margin, or on-time ask hits the inbox before the ELT. Someone dumps a file. Someone rebuilds a slice. Someone is a hero until they are out. Then the question is “ad-hoc” again.

Standing questions versus fire drills

A fire drill is a one-time cut: a customer rumor, a plant incident, a scenario that will not repeat. That can stay a labeled working paper with an expiry. It should not get a workspace.

A standing question is the one that returns on a clock. Cash by entity. Bookings versus plan. Inventory that is cash. Scrap that never made the pack. If it has a weekday, it is product work, not a ticket.

This is not stop commissioning a dashboard per question. That piece is intake: how the next page gets born. This piece is the executive cadence: which questions are no longer allowed to live as extracts. Recurring leadership asks are the spec for the semantic product. Pages are optional. The measure and the grain are not.

This is also not a demo of talking to the estate. Conversational analytics without a trusted model is just chat. English is an interface. It inherits whatever you already certified. If Monday’s questions are still answered by a person with a SQL window, you are not ready to converse. You are ready to stop treating the clock as an emergency.

[Judgment:] a question that survives four Mondays is a requirement. Calling it ad-hoc is how you keep underfunding the model.

How a Monday question stays a hero job

Someone pings. The certified app is close but not quite: wrong entity, no as-of stamp, freight still mixed in. Faster to extract than to change the product. The extract wins. The product never learns.

Next Monday the same gap. Another extract. The hero now has a private ritual. The ELT thinks analytics is a person, not a loop.

Meanwhile the model could have held the measure. Grain named. Refresh owned. Access matched to who may see the plant. The standing question would have been a filter. You chose a fire drill because fire drills do not require a steward.

Screenshots of last week’s answer make it worse: ask the model, don’t screenshot. A picture cannot take the follow-up. The follow-up becomes another extract.

What heroic extracts actually cost

1. The clock never gets a product. Every Monday is day one. Nothing compounds. The model stays a museum of almosts. The meeting still waits on a person.

2. Definitions drift with the hero. Last week freight was in. This week it is not. Nobody wrote the sentence. The ELT thinks they asked the same question. They did not. That is how data quality shows up as arguments.

3. Risk sits in the inbox. Row-level rules do not travel with a CSV. A standing cash question answered as an attachment is a standing leak. The live model can restrict. The extract cannot.

4. Capacity and people both burn on the wrong work. Refresh of unused pages still runs. The analyst who should be changing a measure is rebuilding last week’s dump. You pay for a program and run a print shop.

5. Fire drills lose their meaning. When everything is “urgent ad-hoc,” real incidents wait behind the weekly ritual. You trained the organization that the only way to get a number is to shout.

6. Trust never attaches to the app. If the number the CEO uses arrived in email, the certified page is decoration. Adoption dies even when usage metrics look fine for analysts. The front door failed: nobody opens the dashboard.

You do not need a survey to see this. Open last month’s executive inbox. Count the repeats. That list is the backlog the PMO should already own: why the PMO should own the analytics backlog.

How to put Monday in the model

1. Write the standing list. Ten questions, not forty. The ones that hit every ELT. Cash. Margin. Backlog. Inventory. Throughput. On-time. Whatever your cadence actually fights about. If you cannot name them, you do not have a strategy. You have a suggestion box. Start from dashboards to decisions.

2. Turn each question into a measure contract. Include, exclude, grain, as-of, owner. One sentence leadership can say. If two questions share a word and not a definition, split the names. The product is the semantic model. The brochure can wait to be pretty.

3. Point the meeting at the product, not the person. The pack reads the certified app or connected Excel on the same model. The old extract is labeled working paper with an expiry. Change work is removing the competing file: change management without the theater.

4. Allow conversation only on that product. Plain-language follow-ups are useful when they hit named measures and trusted dimensions. Sandbox models stay mute in executive channels. Label the answer with the measure and the refresh stamp. If the interface cannot show lineage, do not point it at the CEO.

5. Route true fire drills to a labeled path. One-offs get a steward, a date they die, and a test: will this return? If it returns, it graduates to the standing list and the model. If it does not, it does not get a report. Intake still says no to a page per curiosity.

6. Review missed Mondays like incidents. The extract that still happened is a product bug or an ownership gap. Fix the measure. Do not praise the hero. A Quickstart can land the first standing loop. Keeping the list honest is Managed Data & AI Advisory. If the list is still “everything,” you need a roadmap before a microphone.

Finance packs that never left the scavenger hunt are finance reporting consulting. Monday cash has a diet: cash, not charts. Use those when the standing question is the close. This post is the rule for any function that repeats itself weekly.

What good looks like

The ELT can ask this week’s version of last week’s question without a ticket.

The answer matches the pack. The follow-up is a filter, not a rebuild.

True incidents still get a human. They are rare enough to notice.

The hero has another job.

Frequently asked questions

What if the CEO’s question changes every week? Then you do not have standing questions. You have a strategy gap. Name the decisions that actually repeat. Curiosity still does not get a workspace.

Can people ask the model in plain language? Yes, after the standing measures exist and only against that product. Chat on extracts is a faster argument.

Do standing questions all need a dashboard? No. They need a certified measure, a grain, and a place the meeting already opens. A page is one brochure. Connected Excel is another. The extract is not a third official.

Get started

Stop calling the weekly ask ad-hoc. Put it in the model. Save heroics for surprises.

Need a 30-minute look at which executive questions are still living in extracts? Contact Alluvium. We’ll name the standing list, the measures, and the fire drills that are allowed to stay one-off.

Book a 30-minute consult.