A 48-Hour Decision Story
What happens when a major client pushes for a price reduction, but the factory is already close to its limit?
It is Monday morning. Katrin, the COO, reads the email that has just arrived. Then she reads it again. Not because she does not understand it. Quite the opposite. She understands it all too well. The company’s largest client is asking for a 12% price reduction on the remaining volume of the contract, citing “market conditions.” In return, they promise “higher future volume” and “a longer-term partnership,” but nothing concrete is included in the email. They expect an answer by Wednesday noon.
Katrin knows the factory is already running close to full capacity. There is very little buffer left in the system. Two key engineers have been under heavy pressure for months, often working overtime because unplanned maintenance and repair work keeps increasing. The quality manager has also started raising early warning signs: more rework, fluctuations in critical parameters and signals that often appear before customer complaints start rising.
The CEO is travelling and will not be available during the next 48 hours. In situations like this, the chairman has previously asked Katrin to quickly map the options and bring a recommendation. Katrin wants to present a view that is commercially sound and realistic under the circumstances. But this is not a simple choice between a “good” and a “bad” option. At first, three possible paths come to mind:
- If she accepts the client’s request, the company may face a serious quality issue, and key people may burn out or leave.
- If she refuses, the company may lose a significant order volume, with a direct impact on the business. It may also send a signal to the market that the company is not flexible or commercially responsive.
- If she delays the decision, she is effectively saying no, only more slowly, while also risking the company’s credibility by not responding on time.
Two poor reflexes and one better choice
This is the kind of situation where leaders often feel that a lot is at stake and certainty is limited. The mind looks for two easy exits: delay the decision and hope for more information, or make a fast decision just to reduce the pressure. Katrin feels the anxiety rising, but chooses a third path. Instead of rushing or avoiding the decision, she works through it using five steps.
1. Define the decision in one sentence
What decision are we actually making?
When Katrin brings the team together, people start talking about everything: market conditions, competitors, the client relationship, supply chain, product positioning, employee fatigue and factory capacity. All of it is relevant. Some colleagues suggest that they should have a few more discussions before making the decision. Katrin can feel the clock working against them. If the conversation continues like this, she will have to make a decision based on a large amount of valuable but scattered information. After hearing the different perspectives, she brings the conversation back to the core question:
“Do we accept the 12% price adjustment, and under what conditions, while keeping quality and workload risk under control, or do we refuse and prepare for a potential loss of volume?”
It may sound simple, but this is the moment where the discussion becomes manageable again. When the decision question is clear, the team is less likely to get lost in details or make a decision simply to reduce internal pressure. In complex decisions, a clear frame helps keep thinking rational. It also makes the decision easier to manage when the stakes are high and information is incomplete.
Questions Katrin used to define the decision:
- What do we know today: facts, assumptions and emotions?
- What is the actual decision question, not just the general topic?
- Would 72 more hours really improve the decision, or only postpone the discomfort?
- What would a good result look like 90 days from now, measured by two or three indicators?
2. Define the real options
Is this really just a yes-or-no decision?
The next trap in decision-making is binary thinking. In real life, there are usually many shades between “yes” and “no.” There are almost always more options than the first ones placed on the table. Some options only appear when different alternatives are combined. Katrin asks the team to define exactly four options. Not more.
Too many options create decision fatigue and delay. Too few leave the team trapped in a simplistic yes/no frame. The team defines four alternatives:
Which option is manageable, not just comfortable?
The team then compares the options. For each one, they write down the potential gain, the cost and the most likely way the option could fail. That comparison quickly makes one thing visible: the best option is not necessarily the most comfortable one. It is the one that can actually be managed. At this point, Katrin starts to see Option C as the strongest direction. For a leader, it is important to notice the options that were not handed to you at the beginning. If you stay only within the options given by the other party, you voluntarily give away initiative in the negotiation.
3. Stop asking “Are we sure?” and ask “What is irreversible?”
Option C now looks promising, but Katrin does not treat it as final yet. Her next step is to design the possible agreement in a way that does not lock the company into an unclear long-term price reduction. She knows the biggest risk is not only the 12% discount. The bigger risk is that the discount becomes the new normal without clear limits, metrics or review points. So she separates the decision into two parts:
- What is difficult or costly to reverse?
- What can be made temporary, measurable and adjustable later?
Questions Katrin asked at this stage:
- Which part of the agreement would be difficult to reverse, and what would reversal cost in money, reputation or relationships?
- Which conditions can be structured as a 90-day test with clear review points?
- Which two or three metrics would give us early signals that the agreement is working or failing?
- How do we design Option C with clear stop-loss rules and room to renegotiate, without taking uncontrolled risk?
4. Use a pre-mortem and turn risks into conditions
How could this decision fail six months from now?
On Tuesday afternoon, Katrin runs a pre-mortem on Option C. It is one of the simplest and most effective ways to surface risk without forcing anyone to sound “negative” or “difficult.” She says to the team: “Assume we make this conditional agreement, but six months from now it has failed. What happened?” Everyone writes down three to five reasons individually before the wider discussion begins. This matters. If the group starts discussing immediately, the loudest voices tend to fill the room first. Humanity, tragically, has not yet solved this bug. The responses are direct:
- “The client got the lower price but never guaranteed the volume. We gave away margin without getting anything concrete in return.”
- “Quality dropped and customer complaints damaged our reputation.”
- “The team burned out and we lost key people.”
- “Other clients started asking for the same discount. We created a precedent.”
Katrin does not leave these risks as “good points to keep in mind.” She turns them into conditions. If there is a risk that promised volume will not materialize, the agreement needs a minimum volume commitment and consequences if the client does not meet it. If there is a risk that quality and people will break under pressure, the agreement needs workload limits, delivery flexibility and clear prioritization during the pilot period. If there is a risk that the discount becomes a precedent, the agreement needs to be temporary, clearly justified and based on transparent pricing logic that can be reviewed if agreed triggers appear.
5. Clarify decision roles before execution starts
Who decides, who acts and how do we monitor progress?
Sometimes decisions do not fail because the choice itself was wrong. They fail because:
- no one knows who actually made the decision;
- no one clearly owns execution;
- there are no review points.
Katrin uses a simplified version of the RAPID decision model, described in the Harvard Business Review article Who Has the D? The principle is simple: decisions move faster when roles are clear.
Who recommends?
Katrin defines the roles:
- First step: After Katrin’s meeting with the client on Wednesday, a written conditional proposal is sent the same evening.
- Review point: After 30 days, the financial indicators, factory workload and quality metrics are reviewed.
- Stop-loss rule: If quality or workload exceeds the agreed threshold, contract terms or the delivery schedule are reviewed.
- Communication: The team receives a clear message: “We are not buying volume through burnout.”
The result: a decision without perfect certainty
On Wednesday afternoon, both sides sit down at the table. The client is not thrilled, but the proposal is clear. It is not an emotional defence or a vague “we just cannot do this.” It is a thought-through commercial framework with conditions and limits. In the end, the parties agree on a 90-day pilot, a volume commitment and review points covering financial indicators, factory workload and quality metrics. Katrin did not get perfect certainty. She got something better: a decision that can be managed and corrected if needed. When information is limited, time is short and the stakes are high, the best answer is neither a panicked “let’s just decide” nor an endless “let’s analyze more.” The best answer is a framework that makes the decision clear, the roles understood and the execution controllable.
References
- Gary Klein, Performing a Project Premortem, Harvard Business Review
- Paul Rogers and Marcia Blenko, Who Has the D? How Clear Decision Roles Enhance Organizational Performance, Harvard Business Review
- Hugh Courtney, Jane Kirkland and Patrick Viguerie, Strategy Under Uncertainty, Harvard Business Review
- Cheryl Einhorn, How to Make Rational Decisions in the Face of Uncertainty, Harvard Business Review
