Decision-ReadyADAFSA · Strategy Sector

Home

Executive learning library

Frameworks

Every named framework of the programme on one page — the shared vocabulary of the Sector.

8frameworks 0 / 8frameworks reviewed · 35–45 min guided tour

How to use this page

01Choose the decision problemFind the question that is failing.
02Open the matching frameworkUse the framework as a working tool, not a poster.
03Apply it to a live requestLeave with a clearer decision, owner or next step.
01

Decision lens · Topic 1

The five questions every submission must answer

The universal decision-readiness diagnostic

Back to framework map ↑
  1. 1What exactly is being asked or decided?
  2. 2Why now?
  3. 3What is the evidence?
  4. 4What are the implications?
  5. 5What do we recommend — precisely?

If any of the five is missing, the submission is not decision-ready. Full stop.

02

Operating model · The Playbook backbone

The six stages of every request

The end-to-end route from arrival to organisational learning

Back to framework map ↑
1Receive & Triage
2Clarify & Plan
3Task & Collect
4Synthesize & Build
5Review & Submit
6Follow Up & Learn
03

Synthesis · Topic 5

The Pyramid Principle

The answer-first structure for executive reasoning

Back to framework map ↑
The Answer Lead with it 2–4 grouped arguments MECE — no overlaps, no gaps Evidence Sources and as-of dates on everything
The Pyramid Principle
04

Decision document · Topic 6

Anatomy of the memorandum (المذكرة)

The eight-question anatomy of a complete memorandum

Back to framework map ↑
05

Quality gate · Topic 7

The three-level quality gate

Three levels of challenge, with a red-team pass

Back to framework map ↑
Red-team pass — “Why would the Secretariat return this?”
Level 1Self-reviewMechanical completeness against the checklist
Level 2Cold readAn uninvolved peer answers: what is asked? what do we recommend?
Level 3Leadership sign-offJudgement, positioning and risk — not proofreading
06

Return diagnosis · Topic 7

The Top 12 reasons submissions come back

A common language for preventable return risk

Back to framework map ↑
  1. 1The ask not fully answered — sub-questions missed
  2. 2Financial implications absent or unquantified
  3. 3No evidence of coordination with concerned entities
  4. 4Stale data with no as-of dates
  5. 5Numbers inconsistent across text, tables and slides
  6. 6Recommendation vague or missing
  7. 7Options not analysed
  8. 8Legal review missing where needed
  9. 9Annexes missing or never referenced
  10. 10Formatting below standard or wrong template
  11. 11Arabic and English versions inconsistent
  12. 12Submitted late, or at the deadline with no margin
07

Intake discipline · Topic 3

Backward planning

The timeline that protects synthesis, review and sign-off

Back to framework map ↑
Mon Tue Wed Thu Fri S/S Mon Tue Wed Thu Fri Task departments Inputs due Synthesize Quality gate Sign-off Submit by noon
Backward planning on a ten-working-day request — the true department deadline is day 4
08

Learning loop · Quarterly review

What the metrics should show

A results view that shows whether discipline is improving outcomes

Back to framework map ↑
First-time acceptanceReturns per quarter 46% 11 Q1 61% 8 Q2 74% 5 Q3 88% 2 Q4
Illustrative What discipline buys: first-time acceptance climbs as return reasons shrink (illustrative)