Mini management audit: how to translate company goals into requirements for foremen

Management · 5 min read · 20.08.2026

"Scrap −30 % by year-end." That goal has been hanging on the board in production meetings for three months. When we recently asked the welding shop foreman what it meant for his shift, he shrugged — apparently he was just supposed to cause less damage. The shift leader had heard about the goal. But he didn't know the number he carried for it. Meanwhile, the production director evaluated them every six months: whether they "held the team together" and were "solid". This is where the chain breaks. The company has targets for costs, scrap, and takt, but has never translated them into requirements for its leaders. Team evaluation is then a matter of gut feeling, development is random, and the decision to "develop or replace" is just a guess.

More companies than it seems are riding on this decision. Cost pressure is rising, and in a tight labor market you won't land a good foreman in a month. Before choosing between developing the people you have and searching for new ones, it pays to first find out what the team can really handle. That is exactly what a mini management audit is for — a production director can complete it alone in two to three weeks, in three steps: goals and requirements, team evaluation, actions. At Foreast, we usually use it to open our work with a management team, because without it every further decision is made blind.

A goal that can't be converted into requirements for specific people isn't a goal. It's a poster on the board.

Step 1 — Convert company goals into requirements for leaders

Start from what the company promises its customers and the strategies that follow. From this, derive what every management position must know, ensure, and decide for the goals to be met. Take the goal "scrap −30 %" for a welding shop foreman:

• Know: their shift's weekly scrap by defect type and the top three causes from memory.
• Ensure: analysis of the most frequent defect and a corrective action within 48 hours; a check of welding parameters after every wire change.
• Decide: on stopping welding when a defect repeats; on sending a workpiece to rework instead of the next piece.

Do the same sheet for the shift leader, the planner, and the quality manager. The result is a position × requirement table on one side of A4. There are only a few rules. A maximum of 5 to 7 requirements per position. Each one verifiable from existing data or observation. No "proactive approach", no "team player". For each requirement, note where you'll verify it — a report, a shop-floor visualization, shift observation. Can't it be measured or observed? It doesn't belong on paper.

Step 2 — Evaluate the team against requirements, not against feelings

Only now does evaluation come into play. Use three sources of evidence for each leader. The first is a structured interview of 60 to 90 minutes, run directly from the sheet: "Name the three most frequent causes of scrap in your shift and what you did about them in the last month." The second is observation during a shift — how they run the morning meeting and what they do when a disruption exceeds 30 minutes. Are they addressing the root cause, or putting out the symptom? On projects, we keep seeing that one hour on the shop floor reveals more than two in the office. The third is a case exercise: "Takt is falling and, simultaneously, a thread defect is being reported. What do you tackle first, and what do you postpone?" It shows how a person prioritizes under pressure.

Rate each requirement with three colors. Handles it — you have evidence. Borderline — they manage it when someone asks, but not on their own. Doesn't handle it. One discipline: for both yellow and red, at least two concrete pieces of evidence, not impressions. The result is not a grade, but a map of the team — where the company's goal gets stuck at the level of a leader.

Step 3 — Turn findings into actions

A finding without actions is a polite conversation. For every leader with a yellow or a red, one of three paths remains open.

The first is a personal development plan with assignments. A foreman who doesn't work with data doesn't need a "data analysis" course. For eight weeks, they will present their shift's scrap trend at the production meeting, supported by the planner. Assignment, deadline, owner, follow-up — nothing more. The second path is a transfer. An excellent welder or process engineer doesn't have to be a good leader of people, yet as a specialist or internal trainer they can be worth more than in a role where the whole team suffers. The third path is the hardest: replacement. If after three to four months of development they still don't give the team what the position requires, keeping them costs more than finding a replacement. The decision is usually unpleasant. Yet it can be made with the agreement of everyone who saw the same data.

The whole audit fits into three weeks plus one closing meeting with the team, where you explain the results and next steps. If you want outside support in translating goals, see what a management audit looks like in our services. A goal on the board won't translate itself to the shop floor. Someone has to translate it — and then every foreman can read it.