You’ll learn
- How to compare options without fooling yourself
- What to check before a long-term commitment
- Why you may be solving the wrong problem
- When one good option is enough

first KEY POINT
The email lands at 4:40 pm on a Friday. A supplier has pulled out, a client wants an answer today, or a hiring manager needs a name by Monday. You have less information than you'd want and less time than you'd like. Most of us either rush it and hope or stall and call it due diligence.Decision-making consultant Edoardo Binda Zane blames neither habit. What ruins most decisions, he argues, is running a process that doesn't fit the situation. A hiring choice can carry two weeks of analysis without breaking. A pricing call in a moving market goes stale while you're still building the spreadsheet.What follows is a set of decision models. Some suit choices you have to make in minutes. Others are for the ones you'll live with for years. But they all come back to the same question: how much process does this decision deserve?
second KEY POINT
Three weeks before launch, the person responsible for half the work resigns. The instinct is to spend the next five days comparing replacements, redistributing tasks, and rebuilding the timeline. But the situation moves while the plan is being written. By the time it's ready, it can rest on facts that no longer apply.That's the difficulty with decisions under pressure: the information is incomplete, but it's also expiring. Waiting may improve your analysis while making the decision itself less useful.One way to handle this is the OODA loop, developed by US Air Force strategist John Boyd: Observe, Orient, Decide, Act. Binda Zane uses it where circumstances keep changing, because it treats a decision as something you keep updating.Start with Observe: separate what you know from what you are predicting. In the resignation example, you know the employee's final day, what work is finished, what remains, and which deadlines have been promised. You don't yet know how quickly you can hire, whether another employee can absorb the work, or whether the client would accept a smaller launch. That distinction matters. Predictions can guide you, but they shouldn't become facts.Next comes Orient: decide what kind of problem those facts create. Perhaps the real problem is capacity. Then temporary help makes sense. Or maybe the team could still hit the deadline by cutting two low-value features, and hiring is no longer the first question. The same facts can produce different decisions depending on how you frame them.Only then do you Decide and Act. Choose the strongest workable move with the information you have: cut the two features or move one task to another teammate. Then look at what the action reveals. Did the revised workload become manageable? Did the client reject the smaller scope? Those answers become the next round of observation.

Continue reading with Headway app
Continue readingfirst KEY POINT
second KEY POINT
third KEY POINT
fourth KEY POINT
fifth KEY POINT