Six questions every leadership team should be able to answer

Question 1: Where does margin pressure build, and which customers, products or projects explain it?

• Why it matters. Margin is the oxygen of your growth. A drop of 2 points on € 12 million in revenue costs € 240.000 in profit. As long as you cannot attribute the gap, you cannot steer on it.
• How you probably answer it now. With a total figure from the monthly report and an explanation that differs from meeting to meeting: purchase prices, the market, one difficult project.
• What ‘having the answer’ means. You can split the drop into parts that add up to the whole. For example 1,1 points from customer mix, 0,7 points from discounting, 0,4 points from returns, 0,2 points from rush deliveries. Every part carries a name and an option to act.

Question 2: Which sales opportunities deserve priority based on win probability, margin and capacity?

• Why it matters. Sales reps chase the biggest deals. Those are rarely the best ones. An order of € 400.000 at 8% margin that ties up your installation crew for six weeks is more expensive than three orders of € 90.000 at 22% margin.
• How you probably answer it now. With a pipeline overview by revenue and stage, and the sales manager's gut feel about who is going to close.
• What ‘having the answer’ means. Every opportunity carries three values side by side: expected margin, estimated win probability based on comparable deals, and the capacity it demands in the week it would land. The top five then looks almost always different from the top five by revenue.

Question 3: Which projects are at risk of delay, hours overruns or cash flow pressure?

• Why it matters. Project losses become visible at delivery, when stepping in no longer helps. Anyone who sees it in week three can still adjust or invoice the extra work.
• How you probably answer it now. Through the project managers, in a meeting, based on their estimate. Optimism is the norm there, not the exception.
• What ‘having the answer’ means. Every active project carries three weekly signals: hours spent against the estimate, schedule against milestones, and invoiced against delivered. Projects that deviate on two of the three sit at the top of the leadership team agenda before anyone asks for it.

Question 4: Where does growth become hard to manage operationally?

• Why it matters. Growth breaks processes one spot at a time. At 50 employees, informal coordination works. At 120 it does not. You only see the cost of that break when customers complain.
• How you probably answer it now. Afterward, when something goes wrong. Or through signals from the organization that you only recognize as a warning in hindsight.
• What ‘having the answer’ means. You track a handful of early indicators per process: lead time from quote to order, number of manual corrections per week, rush shipments, overtime hours, complaints per hundred orders. When two of them rise three months in a row while volume goes up, you know where the next break sits.

Question 5: Which knowledge is vulnerable because it depends on a few key people?

• Why it matters. In every company of 50 to 250 employees there are three to eight people who know things that are written down nowhere: which customer has which agreement, why that machine gets set differently, which supplier to call when it is urgent. If one of them leaves, it costs you months.
• How you probably answer it now. With a gut feeling about who is indispensable, and a vague intention to write it down some day.
• What ‘having the answer’ means. You have a list with a name, a knowledge area, what goes wrong if that person drops out, and the status: recorded, shared or still vulnerable. Every vulnerable area carries a date and an owner.

Question 6: Which information is missing exactly at the moment a decision has to be made?

• Why it matters. This is the question underneath the other five. Decisions are rarely postponed out of reluctance, but because of one missing number. Every week of delay on a decision that touches margin costs money.
• How you probably answer it now. Not at all. Almost no leadership team keeps track of which decision was postponed and which information was missing.
• What ‘having the answer’ means. For one quarter you note two things for every postponed decision: what was missing, and how many days the delay lasted. After three months you see the pattern. Usually the same kind of information is missing every time, and that is exactly where your first application should begin.

How do you score yourself?

Count one point per question if you get the answer on the table within one working day, with numbers and without someone having to spend an afternoon digging.

• 5 to 6 points. You steer on what is happening now. Focus your attention on question 6 and on shortening decision lead time.
• 3 to 4 points. A normal picture for a growing company. Pick the weakest question with the largest financial impact and tackle that one first.
• 0 to 2 points. You are steering on the past. Start with one question, not with all six at once.

Wat je vervolgens bouwt, hangt af van je zwakste antwoord. Hoe zo’n toepassing werkt, staat in What AI agents are. Hoe je in zes weken bewijst dat het werkt, in the 45-day pilot. Waarom je bestaande rapportage deze vragen niet beantwoordt, in From BI to Management Intelligence. En waar dat toe leidt als je doorbouwt, in Digital Business Twin.

Frequently asked questions

Which of the six questions is the best one to start with?

With the question that carries the largest amount and where you now have the least visibility. In practice that is question 3 for project organizations and question 1 for trade and manufacturing. Never start with all six at once: then you deliver six half answers.

How long does it take before you can really answer such a question?

For one question, count on six weeks, including a baseline measurement and testing with real management questions. That is the setup of the 45-day pilot. Answering all six usually takes twelve to eighteen months, because knowledge that now sits in people's heads has to be recorded as well.

Are these six questions also relevant below 50 employees?

The questions are, the urgency is not always. Below about 50 employees the owner often still oversees the company personally and informal adjustment works. Above that line, clarity gets lost and the same questions suddenly become hard, exactly at the moment the amounts get bigger.

What if our data is not good enough for these answers?

Then that is your first finding, and it is a usable one. Almost every company discovers at question 1 or 3 that data gets recorded too late or incompletely. Fixing that is a matter of management and usually costs little money, but it does take attention from the leadership team.