Training for individual contributors teaches people to keep standards. Don't pour without inspection, don't bypass an interlock, recall the cookies with the missing allergen label. Becoming a manager changes the question. The standards stay the same, but output targets, bonuses and losses land on the same table. Repeating the standard doesn't resolve it, and hitting the number doesn't end it.
All four maps in First Run end at a management title: Director at the IT company, Line Manager at the semiconductor fab, Site Manager on the construction site and Center Manager at the co-op. As your level rises, quests from customers and stakeholders and from the executive seat open up. This article lays out the four shapes of answer that recur in those quests, and how to use them in new manager training.
The four answers in manager quests
Put the six executive quests from the fab, the construction site and the co-op side by side and the options split the same way.
- Poor: look only at the numbers. Ship every held lot, trim curing time, end a loss-making route with a letter.
- Risky: look only at the principle. Refuse without discussion because safety comes first, keep things without discussion because of tradition, carry on without a plan because members come first.
- Good: compromise, but leave out the people affected. Split the difference without evidence, put it to a majority vote without information, or cut back without asking those it affects.
- Excellent: fix what won't be cut, build options, bring the affected people's voices in, and publish the reasons.
The wrong answer new managers pick most easily is not Poor but Risky. The better someone learned to keep standards as an individual contributor, the more a refusal on principle looks like the safe answer once they become a manager.
1. Numbers only: Poor
Three days before the quarter closes, the fab's Line Manager is told that hitting the target means shipping ten held lots still under investigation for a borderline defect signal. Releasing all ten, or labelling them engineering samples to ship outside the normal quality release, is Poor.
The construction site's Site Manager candidate hears that the owner will pay a bonus for handing over a month early. Hitting the date by trimming curing time and inspections is Poor.
The co-op's Center Manager candidate gets the finance committee's proposal to end a mountain delivery route that loses money every year. Ending it as proposed and sending the affected members a letter is Poor. The shopping and weekly watch visits of 120 households end with one letter.
2. Principle only: Risky
In the same quests, answers in the opposite direction are Risky.
- Recommend refusing the acceleration request without further discussion because safety comes first: Risky. A refusal without review takes options away from both the owner and head office, and some of it might be safely possible.
- Announce that thirty years of farm-direct milk will continue, without discussion: Risky. The outcome may be what most members want, but the members worried about price were left out of the process.
- Keep running the loss-making route as it is, with no plan, because members come first: Risky. Unplanned losses pile up on other members and come back later as a bigger cut.
The IT company map is the same. When a client demands a two-week schedule cut with no extra budget, flatly refusing is Risky, and disclosing the risk and negotiating an MVP scope is Excellent. Protecting something means offering a way to keep it going.
3. A compromise that leaves people out: Good
Compromise is familiar ground for managers, but in First Run most compromises stop at Good or Risky.
- Release five of the ten held lots and hold five (fab): Risky. There is no evidence for which half is safe.
- Settle quickly at 10%, halfway between a producer's 15% rice price request and the buyer's 5% limit (co-op): Good. Nobody checked whether the producer's costs are actually covered, and there is nothing to explain to members.
- Decide the farm-direct milk question by online majority vote (co-op): Good. A survey without information can't reflect thirty years of relationship or the quality difference, and older members' voices are easily missed online.
- Propose cutting the loss-making route to every other week (co-op): Good. Nobody asked the members how fortnightly delivery affects storing frozen food or the watch service.
What they share: they found a midpoint, but not why that number is right, and not what the people affected have to say.
4. What the Excellent answers have in common
The Excellent answers share the same elements across industries.
Fix what won't be cut, first
In the acceleration quest, the Excellent answer works out what acceleration really takes and offers conditional options, such as early handover of some blocks, with cost and risk, while curing, inspections and safety staffing stay fixed. Once you separate what is negotiable from what isn't, the rest can be combined freely.
Bring data and voices together
In the mountain route quest, the Excellent answer lays out the real cost structure alongside what members rely on the route for, builds options such as adjusting frequency, linking with a mobile store or working with the municipality, meets the members in that area and brings the data and their voices to the board together. The board can then discuss how to keep it going, not just whether to end it.
Publish the reasons
In the farm-direct milk quest, the Excellent answer shares the price gap, what farm-direct milk guarantees and the dairy farmers' situation with member committees and representatives, holds discussions and a survey, considers keeping farm-direct milk while adding a cheaper line, then publishes the decision and the reasons. When the reasons are public, even members who disagree with the outcome can trust the process.
Under pressure, decide on evidence
In the output target quest, the Excellent answer keeps the hold, fast-tracks lot-by-lot disposition with extra testing, ships what passes and explains the gap early. It doesn't give up on the target; it changes how to get closer to it to a way that rests on evidence.
With customers and owners: neither an unfounded yes nor a bare no
Managers make the same call in front of outside stakeholders.
In a fab customer quest, the customer has heard about a yield problem and asks whether next month's full quantity will ship.
- Say yes to the full quantity so the relationship isn't hurt: Poor
- Say plainly that the full quantity isn't possible, and leave the details for the next meeting: Poor
- Promise the full quantity by adding wafer starts without checking capacity: Risky
- Share a data-based quantity and date, the recovery plan and options like split shipments, and set the next update date: Excellent
Customers have customers of their own to explain to. Telling them early, in numbers, with options, lets them prepare.
The construction owner who wants upgraded countertops and tiles three months before handover, with the same date and budget, gets the same treatment. Saying yes on the spot is Risky. Refusing flatly because it isn't in the contract, or saying without analysis that it would take six more months, is Poor. Excellent welcomes the request, checks lead times, cost and schedule impact, and comes back with conditional options (which units, by when, at what cost), agreed in writing.
Using these scenarios in new manager training
- Place them after the individual-contributor quests. People who have already kept a standard as a contributor see more clearly where standards and numbers collide when they take the manager's seat.
- Use the Risky options for discussion. In a group session for new managers, talking through why "safety first, so refuse" isn't the answer builds the sense that a principle is not the same as a review.
- Point out the gap between Good and Excellent. It is usually the affected people's voices and whether the reasons are made public.
- Look at the options people chose in one-to-ones. Someone who mostly misses toward the numbers needs different coaching from someone who mostly misses toward the principle.
Checklist for new manager judgment scenarios
- Are both numbers-only and principle-only answers included as wrong answers?
- Does the feedback explain why a refusal without review isn't the answer?
- Are compromises kept from being correct when they lack evidence and the affected people?
- Does each Excellent answer include what is fixed, options, the affected people's voices and the reasons?
- Is there a quest about answering a customer or owner with data, options and a next update date?
- Do players meet the manager quests only after the individual-contributor quests?
For design rules shared across industries, read Onboarding scenarios for industries beyond IT. How a manager should respond to a report is covered in Teaching new hires to report near-misses.
Try workplace scenarios as onboarding quests
On any map, raising your level opens quests from stakeholders and the executive seat. Play the Onboarding