Decision Frameworks: Core Work

Why this matters

Founders typically make decisions the same way they make coffee. Habit. Whatever feels right at the moment. A bit of input from whoever is around. The result is a business where the same kind of decision gets made differently every time, judgment quality swings with the founder's mood, and the most consequential calls get made when the founder is most tired.

A decision framework is a structure that protects judgment from the conditions that would otherwise corrupt it. The aim is protection, not constraint.

A pattern you might recognise

A founder running a five-restaurant F&B group in Dubai with 46 staff across the venues made three large decisions in a single quarter. He signed a 10-year lease on a new venue at AED 380,000 (USD 103,500) per year. He hired a new head chef on a package of AED 45,000 (USD 12,250) per month. And he agreed to bring in a silent investor for a 15% equity stake in exchange for AED 1.2 million (USD 326,800).

All three decisions were made within a six-week period. All three were made under different kinds of pressure. The lease was signed because the agent said another buyer was circling. The chef was hired after a single interview because the previous head chef quit on a Friday and the new menu launch was on a Tuesday. The investor was brought in because cash flow was tight and the alternative was a personal loan.

Twelve months later, the new venue is the weakest performer in the group. The chef has been replaced. The investor wants more involvement than the founder agreed to. None of the three decisions was wrong on its own. They were made without any structure. There was no framework to name because no framework existed. Each decision was made on instinct, under pressure, by a tired founder.

Working prompts

Pressure prompts

• Which of your worst decisions in the last 12 months were made under time pressure that turned out to be artificial?
• Where do you say yes faster when you are tired than when you are rested?
• Which kind of decision (financial, hiring, partnership, client) consistently goes worse for you?
• Where does urgency from someone else become a substitute for your own judgment?
• Which decision pattern do you recognise in yourself and have not yet broken?

Input prompts

• For a decision worth more than AED 100,000 (USD 27,230), which inputs would you require if you had a written rule?
• Whose perspective do you wish you had asked for before the last big decision?
• Which decisions are you currently making without data that exists in your business?
• Where do you mistake confidence for evidence?
• What is the smallest piece of information that would have changed your last regretted decision?

Authority prompts

• Which decisions are coming to you that should belong to someone else on the team?
• Which decisions are being made by team members that should be coming to you?
• Where is decision authority unclear and slowing the business down?
• Which decision has been made twice because the first owner was overruled informally?
• What is the largest decision a team member made well in the last 90 days, and have you used it as evidence to expand their authority?

Review prompts

• Which decisions in the last year did you not review after the fact, and what did that cost you in learning?
• Where would a 30-day review of a recent decision change what you do next?
• Which kind of decision deserves a structured post-mortem, even when the outcome was good?
• Where does the team treat outcomes as luck instead of as data?
• Which lesson from a past decision have you still not turned into a rule?

Founder exercise (60 minutes)

Part A: Pick the decision and name the heat (15 minutes)

Choose one decision from the last 90 days that felt rushed, contested, or made under fatigue. Write down what was decided, who was involved, and what the actual pressure was at the moment of decision. Be specific about the heat. "I was tired" is not enough. "I had been awake since 5 AM, the client was leaving the country in 36 hours, and my partner was abroad" is enough.

Part B: Rebuild the decision with structure (15 minutes)

Now rebuild the same decision using these five fields:

• Owner - who should have made the call, alone or with whom
• Inputs - what information was required before a yes or no
• Time horizon - how long the decision should reasonably have taken given its stakes
• Downside - what the worst realistic outcome was, and whether it was survivable
• Review point - when the decision would be revisited and against what evidence

Write the actual decision in one column and the structured version in the other. The gap between them is your decision debt.

Part C: Pick the next decision and apply the framework (15 minutes)

Look at the next consequential decision on your plate. Apply the same five fields before the pressure builds. Write down the owner. List the inputs you still need. Set the time horizon. Name the worst realistic downside. Schedule the review point in your calendar now, before the decision is made.

Part D: Build the decision rule (15 minutes)

Decide one rule that would have prevented your worst recent call. Write it as a one-line trigger. Examples: "No lease over AED 300,000 (USD 81,700) per year is signed without 48 hours of overnight thinking." "No senior hire is made without two interviews and one reference call." "No equity decision is made in the same week the question is first raised." Pin the rule somewhere visible. Decision rules only work if they are visible at the moment of pressure.

---

When the person with the knowledge is not the person with the authority

This is the hardest decision dynamic in a founder-led business. Your operations manager knows the client relationship inside out. But you hold the authority to change the pricing. Your senior designer knows the project is behind schedule. But only you can tell the client.

The gap between knowledge and authority creates two problems. First, the person with knowledge waits for you to make the call. Second, you make the call without enough context because you were not present when the problem happened.

The fix: decision rights need to follow knowledge instead of titles. If someone is closest to the information, they should either make the decision or be the required input before anyone else does. Write it down. Make it visible.

Negotiating with people who hold leverage inside your business

Not every decision is yours to make alone. Sometimes you need agreement from someone who has power you cannot ignore.

A co-founder who controls the client relationships. A senior employee who is the only one who knows the system. A key hire who could leave and take half your clients with them.

These are not team management situations. These are negotiations. And most founders handle them badly because they treat negotiations as conflicts to avoid instead of conversations to structure.

Before you open your mouth

Start by understanding what the other person actually needs. Not what they say they want. What they need.

A co-founder who is blocking a decision might not disagree with the direction. They might feel unheard. A key employee threatening to leave might not want more money. They might want more authority. A partner who is resisting change might not be against the change itself. They might be afraid of what they lose if it works.

Before you make your case, label what you think the other person is feeling. "It seems like this feels rushed." "It sounds like you are worried about losing control of the client relationship." "It looks like you feel this decision was made without your input."

If you get it right, the other person relaxes. If you get it wrong, they correct you. Either way, you now know what you are actually negotiating about.

Ask questions instead of making arguments

The worst thing a founder can do in an internal negotiation is argue harder. Arguments create resistance. Questions create movement.

Instead of "We need to change our pricing model," try "How are we supposed to maintain margins if we keep pricing the same way?" Instead of "You need to delegate more," try "What would need to be true for you to feel comfortable handing off that client?"

The other person starts solving the problem with you instead of defending against you.

When someone holds knowledge hostage

Some people in your business hold power because they are the only ones who know how something works. The only one who can run the CRM. The only one who knows the client's history. The only one who understands the finance system.

This is a systems problem, not a negotiation problem. The fix is documentation. If one person's departure would cripple a function, that function needs an SOP before you need a retention plan.

Short term: have the honest conversation. "If you left tomorrow, what would break?" Most people are not holding knowledge hostage on purpose. They just never had a reason to document it.

Long term: build the system so no single person's knowledge is irreplaceable. This is about making the business resilient, not about making people disposable.

Founder exercise (negotiation)

1. Identify one person in your business who holds leverage you cannot ignore (a partner, a key employee, a major client contact).
2. Write down what you think they actually need (not what they have asked for).
3. Prepare one question that would move the conversation forward without creating resistance.

---

Common mistakes

1. Treating every decision as if it deserves the same depth. A AED 5,000 (USD 1,362) decision and a AED 500,000 (USD 136,200) decision should not get the same process. Frameworks are for decisions where the downside is real. Use them where they matter and skip them where they would just be theatre.
2. Mistaking speed for decisiveness. Fast decisions are not always good decisions. The founders who close clients fastest are not always the founders who keep them. Slowing a decision by 24 hours rarely loses the deal. Rushing it often loses the next year.
3. Reviewing only the decisions that went badly. A bad outcome from a good process is luck. A good outcome from a bad process is also luck. Review both. The pattern matters more than the result of any single call.
4. Confusing consensus with quality. Getting everyone to agree does not make a decision better. It often makes it slower and more diluted. The best decisions come from a clear owner who has consulted the right inputs before deciding.

ARCAS lens

Power is proven when judgment still holds under consequence, not when everything is calm. The hardest test of judgment is negotiating a decision with someone who has the power to say no, even when pressure is high.

Decision frameworks are where People and Systems meet at the founder level. People bring the judgment. Systems give the judgment a place to land. AI can help process the inputs but cannot replace the call. The founder who builds frameworks early protects future decisions from the conditions that would otherwise corrupt them - fatigue, urgency, conflict, isolation.

Frameworks are how the same founder makes the same quality of call on a Tuesday morning as on a Friday at 9 PM.

---

Start now: Quick self-assessment

Rate each statement from 1 (never true) to 5 (always true):

Score 24 or above: Frameworks are in place. Move to the next chapter. Score 15 to 23: There are decisions worth restructuring. Run the founder exercise above. Score below 15: This is where most expensive founder mistakes happen. Do the full working session before moving on.