Voice of Business: turning boardroom pressure into measurable requirements

Most improvement projects fail long before anyone runs a hypothesis test. They fail because nobody wrote down what the business actually asked for, in words the business would recognise, with a number attached.

You have heard it in every steering meeting. The board wants better delivery performance. The CFO wants cost out. Someone wants visibility. None of that is measurable, so six weeks later the project team is solving a problem nobody asked for and the sponsor has quietly lost interest.

Voice of Business is the Recognise phase tool that stops this. It captures each strategic need in the stakeholder's own language, forces you to attach evidence, and makes you convert every need into a requirement you can measure. This article walks through it with a worked example. Kembla Freight Services is a fictional regional freight operator, invented for this guide. The numbers are made up, but they hold together, and every screenshot is the real tool.

Before you type anything, press Sample data. The tool fills itself with three worked records so you can see what a finished row looks like.

This matters more than it sounds. The most common mistake with Voice of Business is treating it as a list of complaints. Look at the sample and you will notice every row carries four things: who said it, what they said, a measurable requirement, and the evidence it came from. A row without those four is an opinion, not evidence.

When you are ready, refresh and start your own capture. The sample is there to teach the shape, not to be edited into your project.

Kembla Freight Services is under pressure on margin. The CFO put it plainly in the operating plan review: line-haul cost per pallet is eating the margin.

Type it exactly as it was said. Do not tidy it into management language. The verbatim is what you will read back to the sponsor in six weeks when someone asks whether the project is still solving the right problem, and a sanitised version will not carry the same weight.

Then do the work the tool is really asking for. The CFO's sentence is not measurable. Cost per pallet of eighteen dollars fifty or less is. That number goes in the measurable CTQ column, the theme is Cost, the method was an executive interview, and the evidence is the FY27 operating plan. One row, and the counters at the top of the screen move for the first time.

Keep going. The board minutes give you a second need about losing tenders on delivery performance, with a target of on time in full at ninety six percent or better. The Head of Sales gives you a third about customers wanting to see where their freight is.

Leave the evidence column blank on that third row and the tool interrupts you. An amber banner appears telling you to add an evidence source or sample note before you take this to a tollgate.

This is the part practitioners tend to resent and then come to rely on. A tollgate review is where an unevidenced claim gets found out, usually in front of the sponsor. Better that a banner tells you now than a reviewer tells you then.

Two more records complete the picture. The compliance manager needs chain of responsibility records that survive an audit, evidenced by two failed spot checks. The operations director has thirty consignment timestamps showing depot handovers cost close to a day.

Now look at the three counters. Five evidence records. CTQ coverage at one hundred percent, because every row has a measurable requirement. Three marked Critical, which are the CFO, the board and compliance.

Those counters are not decoration. CTQ coverage below one hundred percent means you have collected opinions you cannot yet act on. A critical count of zero means nobody senior has told you this matters, which is worth knowing before you ask for resources.

Underneath the table the tool counts your themes for you. Delivery appears twice. Cost, Visibility and Compliance appear once each.

That distribution is the first genuinely useful output of the Recognise phase. Two separate senior stakeholders, arriving independently, landed on delivery. That is your candidate project scope, and you did not have to argue for it. You can point at the count.

It also shows you what not to scope. Visibility appeared once, from sales. It may be a real need, but on this evidence it is a single voice, and a project charter built on it would be standing on one leg.

The readiness panel runs four checks. Every record has a measurable CTQ. Every record cites evidence. At least two sources are represented. Themes have been classified.

All four green means this capture will survive a tollgate. Any of them grey means you have work to do, and the tool has told you which work, which is considerably more useful than a reviewer telling you the capture is weak.

The four sources here are the CFO, the board, sales, compliance and operations. Five voices, four themes, and an audit trail back to a document for each one.

Press Interpret evidence and the tool sends your records to the model and returns a structured reading. On this capture it identified five themes, restated the critical requirements, and named a tension that is genuinely there: the mandate to cut cost sits against the investment needed for real time tracking and faster depot handovers.

It also named three coverage gaps. No employee voice. No data on the current technology. No supplier perspective on line-haul pricing. Those are fair observations, and two of them point straight at the next tools in the phase, which are Voice of Employee and Voice of Customer.

Read it as a second pair of eyes on your own evidence. It cannot tell you whether the CFO is right, whether ninety six percent is achievable, or whether your two failed spot checks are representative. It is working only from what you typed.

This is the section most tool guides leave out.

It will not validate your evidence. If you type a number from a spreadsheet nobody has checked, the tool will accept it, count it, and show it as one hundred percent CTQ coverage. The readiness checks confirm that a field is filled, not that it is true.

It will not tell you the need is achievable. On time in full at ninety six percent is a target, not a commitment. Whether the network can reach it is a Measure and Analyse question.

It will not represent the customer or the front line. Voice of Business is deliberately the view from the top of the organisation. The other two capture tools exist because that view is incomplete on its own.

It will not write your charter. What it gives you is the evidence a charter has to rest on: a problem the business recognises, in language they used, with a number attached and a document behind it.

Where this goes next is the Define phase. Your critical themes become the problem statement, your measurable CTQs become the goal statement, and your evidence column becomes the answer when someone asks how you know.