Decision-making series · Part 4 of 6

Which decision models fit the board, its committees, the executive and operations

21 October 2026 · 6 min read · DecixionIQ

A board approving an acquisition and an operations team handling an exception both make decisions, but they need very different tools. Matching the analytical approach to the level of the organisation keeps big decisions rigorous without burying everyday ones in process.

A map of levels, focus and tools

The table below is a starting point. Your organisation's own structure, delegations and risk appetite should shape the final version.

Governance level	Decision focus	Useful combination of models
Board of directors	Strategy, oversight, material commitments	Decision Quality review, scenario planning, independent challenge, verification of authority
Board committees	Risk, audit, investment, remuneration	MCDA, financial analysis, risk frameworks, assurance
Executive committee	Strategic execution, resources, performance	RAPID, OODA, decision trees, portfolio prioritisation
Investment committee	Capital allocation, acquisitions, funding	NPV, IRR, real options, sensitivity and scenario analysis
Business units	Commercial and operational performance	PDCA, MCDA, RACI, cost-benefit analysis
Project steering committees	Scope, budgets, delivery and change control	Stage-Gate, risk assessment, change control
Operational teams	Daily decisions, exceptions, corrective actions	OODA, PDCA, root cause analysis

Reading the table

The higher the level, the more the tools are about challenge and authority. At board level the main risks are a poorly framed question, untested assumptions and a decision taken outside the board's or a delegate's authority. Decision Quality reviews, scenario planning and independent challenge address those directly.
Committees go deeper on their own subject. An investment committee needs valuation and sensitivity analysis; a risk or audit committee needs risk frameworks and assurance.
Executive and operational levels need speed. RAPID clarifies roles so cross-functional decisions are not stuck, while OODA and PDCA support fast, repeated decisions that can be corrected as you go.
Projects need gates. Stage-Gate and change control stop a project from consuming more money than the approval allowed without coming back for a decision.

Models inform decisions; they do not authorise them

In South Africa, who may decide is a legal question, not an analytical one. The governance part of any decision framework must line up with:

the Companies Act, 2008 — including the board's general authority to manage the company's business and affairs, and the directors' standards of conduct in section 76;
the company's Memorandum of Incorporation, which can limit or extend the board's powers;
board and committee charters, which set out each forum's mandate; and
the delegation-of-authority policy, which says what management may decide and what must come to the board.

King V principles can inform how you design the framework, but they do not replace legal authority. For what the business judgement rule asks of directors, see our section 76(4) checklist; for King V disclosures, see the King V guide.

Where DecixionIQ fits

In DecixionIQ, your organisation sets its own governance levels and approval authorities by the size and type of decision. Each decision shows the authority expected to approve it, and only a person with that permission can record the approval. The thresholds in the app are examples to replace with your own, not universal standards.

Sources and further reading

General information, not legal or professional advice.