Voice of Employee: the depot already knows where the work breaks

Ask a depot supervisor what slows the shift down and you will get a precise answer in about eight seconds. Ask the same question in a steering meeting and you will get a project.

Voice of Employee exists to close that gap. It captures what the front line says, in the words they used, and forces each observation into a shape you can act on: who said it, what they said, what would have to be true for it to be fixed, and what evidence you have that it is real.

This walkthrough uses Kembla Freight Services, a fictional regional freight operator invented for this guide. The depot, the roles and the numbers are made up. Every screenshot is the real tool.

The line supervisor at Unanderra said it plainly during a shift observation. They reprint half the run sheets because the system locks before the shift starts.

Type that sentence in as it was said. The temptation is to write system availability issue, which is shorter and sounds more professional, and which nobody will ever act on. The verbatim keeps the annoyance in the record, and the annoyance is what makes people care.

Then convert it. Run sheet reprints of two or fewer per shift is a target you can count on a clipboard tomorrow. It goes in the measurable CTQ column, the theme is Rework, and the evidence is fourteen observed shifts.

The forklift operator has nobody telling them when a load is running late. The dispatch clerk keys every consignment into two systems. The night shift lead has no escalation path after six. The yard marshal loses trailers.

Look at the counters. Five records, CTQ coverage at one hundred percent, and two marked Critical.

Note which two are critical. The supervisor and the dispatch clerk, both describing the same underlying thing from different ends of the building. Neither of them used the word rework.

Rework appears twice. Communication, Escalation and Visibility appear once each.

That is the finding. Two people in different roles, interviewed on different days by different methods, independently described duplicated effort. You did not decide rework was the problem. The register counted it.

This is the difference between a project scoped from evidence and a project scoped from whoever spoke loudest in the last meeting.

The tool runs four checks on your capture. Every record has a measurable requirement. Every record cites evidence. At least two sources are represented. Themes have been classified.

Five roles are represented here, from supervisor to yard marshal, and every observation traces back to something countable: shifts observed, operators in the room, consignments timed.

A grey check is not a failure. It is the tool telling you which conversation you still have to have before someone senior asks the same question.

Press Interpret evidence and the tool reads your records back to you. On this capture it grouped the observations, restated the critical requirements, and pointed at gaps in the coverage.

Treat it as a second reader, not an oracle. It is working only from the five rows you typed. It cannot know whether fourteen shifts is a representative sample, whether the dispatch clerk is the only one double keying, or whether the system lock has a cause nobody has mentioned.

What it is good at is noticing what you did not capture, which is exactly the thing you are least likely to notice yourself.

It will not make people tell you the truth. This is the real limit, and no software fixes it. If the last person who raised a problem got blamed for it, your register will be full of safe observations about car parking. The tool records what you were told. Whether you were told the truth is a question about your organisation, not your method.

It will not weight by frequency. Two people mentioning rework is two records. It does not mean rework is twice as expensive as escalation. That is a Measure phase question and Cost of Poor Quality is the tool for it.

It will not validate the evidence. Fourteen observed shifts is typed by you and counted by the tool. Whether those fourteen shifts were representative is your judgement to defend.

It will not replace the customer or the business view. Front line evidence on its own will optimise the depot and can still miss what the customer is actually paying for. Voice of Business and Voice of Customer exist for that reason, and the three are meant to be read together.

Where this goes next is the Define phase. Your repeated themes become the problem statement, your measurable requirements become the goal, and the evidence column is your answer when the sponsor asks how you know.