Decision-ReadyADAFSA · Strategy Sector

Home · Journey map · Self-paced

Stage 05 / 06

Review & Submit

Quality is three levels and a red team — not one tired reader at midnight.

01Self-review → cold read → leadership sign-off
02Red-team against the Top 12 return reasons
03Submit early; stay reachable for queries
Completion gate Before you move on — can you…
Start the stage →

Stage content

2 modules to complete this stage

Work in sequence and apply each idea to a live request.

Module 05

From Information to Answers

Synthesize — never staple

What you will be able to do

01Create one institutional answer
02Build an answer-first pyramid
03Frame the opening with SCQA
04Write a precise ask
05Handle uncertainty honestly
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

Explore the ideas

Open a card for the key message, the logic behind it, what good looks like and a practical example.

↗Visual briefFrom packet to position
Key messageStrategy adds value by turning many inputs into one defensible position.
01RESOLVEReconcile contradictions.
02SELECTKeep only decision-relevant evidence.
03SPEAKPresent one institutional voice.
Why it matters

Strategy adds value by turning many inputs into one defensible position. Reconcile contradictions. Keep only decision-relevant evidence. Present one institutional voice.

What good looks like

Take a packet of inputs and write the Authority’s position in one sentence. If you cannot, identify the contradiction or missing judgement that blocks the answer.

Practical example

RESOLVE — Reconcile contradictions. · SELECT — Keep only decision-relevant evidence. · SPEAK — Present one institutional voice.

From materials to an institutional position

The stapler and the author

A compiled submission transfers the work of interpretation upward. A built answer gives leadership one clear institutional position.

The stapler: compiler
  1. Collects departmental inputs
  2. Writes a short covering paragraph
  3. Attaches each input as an annex
  4. Sends the package upward
What the package contains
  • Data
  • Technical commentary
  • Departmental perspectives
  • Budgets
  • Risks
  • Policy caveats
What it lacks
  • A direct answer
  • Resolved contradictions
  • Prioritisation
  • ADAFSA’s judgement
  • A coherent recommendation
  • A precise decision sought
The document contains information, but the Authority has not yet spoken.
The author: answer-builder
  1. Returns to the governing question
  2. Extracts material facts
  3. Tests evidence and definitions
  4. Resolves contradictions
  5. Connects causes and implications
  6. Forms an institutional judgement
  7. Develops options where required
  8. States the recommendation precisely
  9. Produces a decision sought
One ADAFSA answer: one institutional position supported by evidence.
The hidden instruction to the reader
Here are the inputs. Please determine what they mean.
  • Several agenda items
  • Limited reading time
  • A non-specialist perspective
  • Need for a decision
  • No mandate to perform ADAFSA’s analysis
A senior reader should evaluate the Authority’s answer—not manufacture it from annexes.
Why compilation fails despite high information volume
More pagesMore attachmentsMore factsMore departmental effort
→ Less decision-readiness
  • Relevance is unclear
  • Evidence is not integrated
  • Conflicts remain visible
  • No conclusion is owned
  • The ask is buried
Volume is not synthesis. Completeness of material is not completeness of thought.
Six value-creation stages
01
Relevance

Which facts actually answer the request?

02
Integration

How do inputs connect across departments?

03
Reconciliation

Where do figures, assumptions or positions conflict?

04
Judgement

What do the combined facts show?

05
Implication

Why does the conclusion matter for leadership?

06
Position

What does ADAFSA recommend or ask leadership to decide?

One-voice test
Four-minute reader test
4minutes
Ownership model
Departments own
  • Technical facts
  • Source data
  • Subject expertise
  • Operational constraints
  • Departmental recommendations
Strategy owns
  • Governing narrative
  • Cross-department reconciliation
  • Executive interpretation
  • Institutional position
  • Final recommendation
  • Decision sought
◎A compiler moves documents. An author creates meaning. Send the Authority’s answer—not the organisation’s raw material.
1Visual briefBuild the pyramid
Key messageThe pyramid lets the reader grasp the answer before the detail.
01TOPOne governing answer.
02MIDDLETwo to four grouped arguments.
03BASEEvidence beneath each claim.
Why it matters

The pyramid lets the reader grasp the answer before the detail. One governing answer. Two to four grouped arguments. Evidence beneath each claim.

What good looks like

Write one governing answer, two to four supporting arguments and the evidence under each. Remove any item that has no logical home.

Practical example

TOP — One governing answer. · MIDDLE — Two to four grouped arguments. · BASE — Evidence beneath each claim.

Answer → why → proof

Start with the answer: the Pyramid Principle

A decision-maker should see ADAFSA’s conclusion first, the reasons that support it second, and the detailed evidence last.

Background-first
01Background
02History
03Methodology
04Analysis
05Recommendation on page four
Reader experience
  • Reads without knowing the destination
  • Must infer relevance
  • May never reach the answer
  • Mentally reconstructs the logic at the end
Answer-first
01Answer
02Two to four supporting arguments
03Evidence and detail
Reader experience
  • Knows the conclusion immediately
  • Understands why each section exists
  • Can stop at the appropriate level of detail
  • Tests the logic while reading
Three reading levels
01
30 seconds

Answer, recommendation and decision sought

02
3 minutes

Answer, two to four arguments and key implications

03
Full review

Evidence, methodology and supporting annexes

Sticky-note version
01
Answer

What should leadership believe or approve?

02
Why

What two to four reasons make that answer true?

03
Proof

What evidence supports each reason?

Poultry-biosecurity example
Is the Emirate’s poultry sector adequately protected against avian influenza this season?
Yes, with one material gap: commercial-farm controls are strong, but backyard surveillance should be strengthened before the high-risk season.
1
Commercial-farm readiness is strong

High surveillance coverage; vaccination compliance; inspection completion

2
Backyard holdings remain under-covered

Lower registration visibility; fewer samples; longer detection lead time

3
The gap can be closed through a targeted intervention

Costed option; available veterinary capacity; eight-week implementation plan

Pyramid quality tests
01
Vertical logic

Does the content below prove the statement above? If not, evidence is misplaced or the argument is unsupported.

02
Horizontal logic

Are the arguments distinct, non-overlapping and collectively sufficient?

03
Relevance

Does each paragraph or exhibit prove or qualify the answer? If not, remove it, move it to an annex or reframe it.

Common mistakes
  1. The answer is vague activity rather than judgement
  2. Too many pillars create a list rather than a structure
  3. Evidence appears before the argument and forces the reader to infer
  4. Background becomes a pillow of chronology
  5. The recommendation appears only at the end
Where background belongs
Why the issue existsWhy it matters nowWhat decision has preceded this oneWhat context shapes the available options
◎Lead with ADAFSA’s answer, support it with two to four reasons, and place every fact beneath the argument it proves.
2Visual briefBefore and after
Key messageAnswer-first structure is shorter because it replaces chronology with logic.
01BEFOREHistory, activities and annexes.
02AFTERAnswer, reasons and proof.
03TESTCan the first page stand alone?
Why it matters

Answer-first structure is shorter because it replaces chronology with logic. History, activities and annexes. Answer, reasons and proof. Can the first page stand alone?

What good looks like

Move the conclusion of an existing memo to the first paragraph, then reorganise the remaining content as proof rather than chronology.

Practical example

BEFORE — History, activities and annexes. · AFTER — Answer, reasons and proof. · TEST — Can the first page stand alone?

Rebuild the structure around the decision

From background-first to answer-first

Do not attach a recommendation to a chronology. Rebuild the submission around the decision.

Council question

Should ADAFSA continue the red palm weevil control programme at its current funding level?

Version A: chronological draft
01Agricultural importance — Date palms are strategically important
02History of the pest — Red palm weevil has existed for decades
03Programme phases — The programme evolved through several phases
04Inspection activity — Inspections were conducted
05Annex references — Data appears in Annexes 3–5
06Recommendation at the end — The programme should continue
What is missing until the final line?
  • Current funding level
  • Recommended duration
  • Why continuation is justified
  • Why the threat still matters
  • What should change within the programme
Version B: answer-first draft
Continue the programme at its current funding level for two further seasons, with targeted reallocation toward early detection.
Three supporting pillars
01
The programme is working

Infestation rates declined in treated zones; trapped holdings outperform untreated comparators; results show measurable control impact.

02
The threat has not receded

Re-infestation occurred elsewhere after controls were relaxed; risk can return within two seasons; premature withdrawal could reverse gains.

03
Detection offers the best improvement

Acoustic detection identifies infestation earlier; cost per palm is lower; improvement can be funded through reallocation.

Complete response to the Council
Decision dimensionADAFSA answer
Continue?Yes
Funding level?Maintain current envelope
Duration?Two further seasons
Adjustment?Reallocate toward early detection
Funding increase?Not required
Role of annexes
Annexes as storage
  • Annex 3: infestation data
  • Annex 4: budget utilisation
  • Annex 5: international examples
Annexes as evidence
  • Annex 3 proves programme impact
  • Annex 5 proves the risk of premature withdrawal
  • Pilot evidence supports reallocation toward detection
Compression test
Rebuild rule
Wrong approach

Add the recommendation to the front of the original chronological report—creating two competing structures.

Right approach

Council question → answer → supporting arguments → evidence.

Comparison prompts
01
What moved?

The answer moved from the final line to the opening.

02
What disappeared?

Non-essential history and unstructured description.

03
What became clearer?

The decision, rationale, duration and funding approach.

◎Same evidence. Less text. Clearer decision. Version A tells the programme story; Version B tells leadership what should be done—and why.
3Visual briefFrame with SCQA
Key messageSCQA gives the opening a complete decision narrative.
01SITUATIONWhat stable context matters?
02COMPLICATIONWhat changed or created tension?
03QUESTION → ANSWERWhat must be resolved, and how?
Why it matters

SCQA gives the opening a complete decision narrative. What stable context matters? What changed or created tension? What must be resolved, and how?

What good looks like

Draft a four-sentence SCQA opening for a live request. Check that the final sentence answers the question created by the complication.

Practical example

SITUATION — What stable context matters? · COMPLICATION — What changed or created tension? · QUESTION → ANSWER — What must be resolved, and how?

Four sentences orient the story

SCQA: frame the story before you build the argument

Situation, Complication, Question, Answer—orients the reader before the Pyramid proves the recommendation.

Four-sentence opening
S
Situation

The Emirate aims to increase local production of strategic food commodities, and ADAFSA operates the incentives supporting this objective.

C
Complication

Programme uptake has exceeded forecasts, and the existing funding envelope is expected to be exhausted before season end.

Q
Question

Should the programme be extended, and under what funding arrangement?

A
Answer

ADAFSA recommends extending support through the season using a targeted internal reallocation, while retaining current eligibility criteria.

SCQA as a diagnostic tool
1
Situation is too long

Too much background, unclear relevance and chronology replacing argument

Keep only context required to understand the issue.
2
Complication is weak

The team does not understand why the request arrived now

Identify the trigger, pressure or change.
3
Question is generic

“What should be done?” does not decode the Council’s decision

Restate the actual decision question.
4
Answer is vague

“Further consideration should be given” avoids a choice

State the preferred action precisely.
Abattoir example
A
Demand pressure

Updated forecasts indicate peak demand may exceed available slaughter capacity by 18%.

Should temporary capacity and extended operating hours be approved?
B
Regulatory change

A new food-safety requirement increases inspection time per animal and reduces effective throughput.

What operational changes and resources are required to maintain safe capacity?
C
Facility outage

One major facility is expected to remain partially unavailable during the peak period.

How should demand be redistributed, and is emergency support required?
Quick drill
Given situationADAFSA’s abattoirs handle peak Eid al-Adha volumes under an established seasonal operations plan.
Demand exceeds capacityFacility outageNew regulatory requirementStaffing shortageDisease-control measures reduce throughputCross-emirate demand surge
SCQA quality checklist
◎Situation establishes the ground. Complication creates urgency. Question defines the decision. Answer states ADAFSA’s position.
4Visual briefNo overlaps or gaps
Key messageStrong arguments are distinct, complete and easy to challenge.
01NO OVERLAPEach point has one job.
02NO GAPSObvious counter-questions are covered.
03GROUPEvidence belongs under one argument.
Why it matters

Strong arguments are distinct, complete and easy to challenge. Each point has one job. Obvious counter-questions are covered. Evidence belongs under one argument.

What good looks like

Test your supporting arguments for overlap and gaps. Merge duplicates and add the one missing argument a sceptical reviewer would ask for.

Practical example

NO OVERLAP — Each point has one job. · NO GAPS — Obvious counter-questions are covered. · GROUP — Evidence belongs under one argument.

Coverage test: no overlaps, no gaps

Nothing repeated. Nothing important left unanswered.

Strong argument sets are distinct enough to avoid repetition and complete enough to answer the reader’s obvious challenges.

Recommendation

Expand the farmer-support programme.

Are we saying anything twice?Have we left anything important unanswered?
Weak structure: overlapping arguments
Improves food securityIncreases local productionReduces import dependence

These overlap heavily. Different wording does not create different reasoning.

Cost of overlap
  • Repetition and padding
  • Shallow analysis
  • Harder recall
  • Inflated number of reasons
  • Lower reader confidence
Strong structure: distinct and complete
01
Proven impact

Delivers measurable production and farmer outcomes; strengthens domestic supply resilience; improves food availability.

02
Unmet beneficiary need

Demand remains concentrated in priority segments; current support does not meet need; equity and regional need remain.

03
Affordable and feasible expansion

Affordable within the envelope; delivery capacity exists; implementation risks are manageable.

No-overlap test
How to remove overlap
01
Domestic supply resilience

Local production increased; import dependence declined; priority commodity availability improved.

02
Measurable farmer outcomes

Yield improvement; income growth; higher programme uptake.

03
Operational and financial feasibility

Available delivery capacity; sustainable cost per beneficiary; manageable risks.

No-gap test
Demand is increasingThe investment cost is justifiedThe proposal aligns with strategy
Why not expand the existing laboratory?
The obvious alternative has not been answered.
Gap-finding questions
  • What is the strongest alternative?
  • Why not maintain the status quo?
  • What happens if we do nothing?
  • Who pays?
  • Who delivers?
  • What legal authority is required?
  • What could go wrong?
  • Which stakeholder bears the burden?
  • What assumption will a reviewer challenge first?
Veterinary-laboratory example
01
Existing capacity will become insufficient

Forecast testing volumes; turnaround delays; utilisation trends

02
Expanding the current facility is not viable

Site constraints; biosecurity limits; disruption; cost versus benefit

03
A new facility provides superior long-term value

Greater throughput; resilience; scalable capability; lifecycle comparison

04
Delivery risks are manageable

Land availability; funding route; implementation plan; operating model

30-second argument audit
If overlap exists
If a gap exists
Better review language
Not MECE.
  • Arguments 1 and 2 are making the same point.
  • The current-facility alternative has not been addressed.
  • The financial argument is missing.
  • Consumer impact has not been addressed.
Use native groupings
01
Biosecurity lifecycle

Prevention, detection, response, recovery

02
Mandate areas

Animal health, plant health, food safety

03
Stakeholder impact

Farmer, consumer, Authority, market

04
Implementation dimensions

Policy, operations, finance, technology

05
Option assessment

Impact, cost, feasibility, risk

◎Do not ask whether the structure is “MECE”. Ask whether any point repeats another—and what the sceptical reader will ask next.
5Visual briefWrite the precise ask
Key messageA precise ask makes the submission decidable.
01VERBNote, endorse, approve or fund.
02OBJECTName the exact action or commitment.
03TERMSState amount, duration and conditions.
Why it matters

A precise ask makes the submission decidable. Note, endorse, approve or fund. Name the exact action or commitment. State amount, duration and conditions.

What good looks like

Write the ask with an exact verb, object, amount, duration and conditions. A reviewer should be able to say approved or not approved.

Practical example

VERB — Note, endorse, approve or fund. · OBJECT — Name the exact action or commitment. · TERMS — State amount, duration and conditions.

The decision sentence is the project design brief

المطلوب: the sentence that carries the submission

A submission becomes actionable only when the decision sentence states exactly what the Council is being asked to decide.

Vague ask
The Council is requested to support the enhancement of food-security monitoring capabilities.
1
Verb

What formal action is required?

2
Object

What exactly is being acted upon?

3
Amount or scale

How much is being committed?

4
Duration

For how long?

5
Conditions

Under what safeguards or dependencies?

Precise ask
The Council is requested to approve AED 18 million over three years to establish an integrated food-security early-warning platform, subject to completion of the data-sharing arrangement and an eighteen-month mid-term review.
A precise ask can be approved, rejected or amended. A vague ask can only be returned.
Decision-verb ladder
1
Note

Receive information

Accuracy, completeness and relevance
2
Endorse

Agree to a direction or principle

Strategic alignment and institutional implications
3
Approve

Authorise a defined action

Options, feasibility, governance and delivery
4
Fund

Commit financial resources

Cost, funding source, value for money and recurring liability
5
Direct

Require entities to implement

Authority, accountability, dependencies and timeline
Decision-readiness test
Write the ask first
Common approach
  • Background
  • Analysis
  • Options
  • Recommendation
  • Write the ask last
↔
Recommended approach
  • Draft the ask on Day 1
  • Identify evidence needed
  • Frame departmental questions
  • Analyse options
  • Address implications
  • Build the recommendation
  • Design the submission structure
Words that can hide an incomplete ask
  • Support
  • Strengthen
  • Enhance
  • Consider
  • As appropriate
  • As deemed necessary
  • Provide guidance
  • Take necessary action
  • Continue efforts
  • Approve in principle without defining what follows
One-sentence builder
The Council is requested to [VERB] [OBJECT], at a cost or scale of [AMOUNT], for [DURATION], led by [OWNER], subject to [CONDITIONS].
◎Write the decision before you write the document. Precision is service: do not ask the Council to complete the decision ADAFSA should have framed.
6Visual briefUse the “so what?” test
Key messageEvery fact must earn its place in the decision logic.
01SO WHAT?Link the fact to an argument.
02MOVESend useful depth to the annex.
03DISCLOSEState ranges, assumptions and gaps.
Why it matters

Every fact must earn its place in the decision logic. Link the fact to an argument. Send useful depth to the annex. State ranges, assumptions and gaps.

What good looks like

Challenge every paragraph with “so what?”. Link it to the answer, move it to an annex or remove it; state uncertainty rather than hiding it.

Practical example

SO WHAT? — Link the fact to an argument. · MOVE — Send useful depth to the annex. · DISCLOSE — State ranges, assumptions and gaps.

Relevance first; transparency always

Earn its place: relevance and honest uncertainty

Every fact must strengthen the decision, and every material uncertainty must be visible. Relevance builds clarity; honesty builds trust.

Three destinations
01
Main paper

Proves the answer, explains a qualification, shows implications, supports the recommendation or is needed to decide

02
Annex

Provides methodological detail, complete datasets, technical background, supporting calculations or first-read non-essential detail

03
Remove

Repeats another point, exists only because it was submitted, demonstrates effort rather than result, provides history without purpose or is interesting but immaterial

The “so what?” test
1

Treated zones recorded materially lower infestation than untreated comparators.

Demonstrates the programme is working and supports continuation.
2

The programme conducted 1,400 awareness visits during the season.

Documents activity but does not establish impact.
3

The programme was launched at a ceremony attended by multiple stakeholders.

Irrelevant to whether funding should continue.
Emotional difficulty of editing
Why weak content survives
  • A department worked hard on it
  • A senior colleague requested its inclusion
  • The paragraph sounds impressive
  • Removing it may feel ungrateful
  • The author is attached to it
Professional reframe

Editing does not reject the contribution. It ranks its relevance to the decision.

False certainty
450 farms participated.
  • Registry contains duplicates
  • Reporting dates differ
  • Some holdings are inactive
  • Definitions are inconsistent
Precision without reliability is not strength; it is exposure.
Three professional moves
01
State assumptions explicitly
The projection assumes current import prices and volumes remain stable through the forecast period.
  • Key dependency
  • Sensitivity
  • Reasonableness
  • What changes if the assumption fails
02
Use ranges with a basis
Participation is estimated at 380–450 farms; the range reflects known duplicate records being reconciled.
  • Lower bound
  • Upper bound
  • Source of uncertainty
  • Expected resolution
  • Whether the decision changes within the range
03
Present real options and trade-offs
When evidence cannot support one certain answer, show act now, pilot first and maintain current approach—with cost, delay, evidence and implementation trade-offs.
  • Immediate cost
  • Exposure to delay
  • Evidence generation
  • Implementation risk
Trust equation
Trust = accuracy + transparency + consistency over time
Strengthens trust
  • Sources stated
  • Limitations visible
  • Assumptions explicit
  • Numbers reconciled
  • Changes explained
↔
Weakens trust
  • False precision
  • Selective evidence
  • Hidden caveats
  • Unexplained revisions
  • Contradictions across submissions
Dual test for every fact
01Does the fact support, qualify or enable the answer?
02Can its source, definition and level of certainty be defended?
How to communicate a material limitation
01
What we know

Confirmed participation records show at least 380 active farms.

02
What remains uncertain

The upper estimate may include duplicate registrations.

03
Why it matters

The programme’s cost per active beneficiary may be higher than the current point estimate.

Answer-builder’s creed
Application challenge
◎Be ruthless about relevance and transparent about uncertainty. Cut what does not support the decision; surface what could weaken it.
Exercise — The Local Harvest File — from messy packet to decision-ready brief
Key messageTurn a messy evidence packet into a one-page decision brief.
01ANSWERWrite the position first.
02STRUCTUREGroup the minimum supporting case.
03ASKFinish with a votable decision sentence.
Why it matters

Turn a messy evidence packet into a one-page decision brief. Write the position first. Group the minimum supporting case. Finish with a votable decision sentence.

What good looks like

Produce a one-page answer-first brief from a messy packet: one position, two to four arguments, essential evidence, honest caveats and one precise ask.

Practical example

ANSWER — Write the position first. · STRUCTURE — Group the minimum supporting case. · ASK — Finish with a votable decision sentence.

Pressure chamber for an institutional answer

The Local Harvest File: from messy packet to decision-ready brief

Turn fragmented evidence, conflicting signals and incomplete data into one defensible ADAFSA position.

1FormatTeam synthesis + peer review
2Team size4–5 people, or complete independently
3Duration55 minutes
4OutputOne-page decision brief
Council request

Assess the Local Produce Procurement Incentive Programme now completing its second season, and recommend whether it should be extended, on what terms, for how long and at what cost.

Messy packet
01
Participation and workshops
  • Registered farms: 210 to 452
  • Expansion across the Emirate

Caveat: Duplicates possible

Likely destination: Supporting evidence

So-what trap: Workshop satisfaction and catering
02
Procurement impact
  • Local share: 12% to 22%
  • Volume: 19,750 tonnes

Caveat: Baseline differs from dashboard; alignment pending

Likely destination: Core impact argument

So-what trap: Use without qualification
03
Financial position
  • Season 2 overspend requires regularisation
  • Season 3 estimate: AED 45–55M

Caveat: New funding and stronger controls required

Likely destination: Core decision condition

So-what trap: Hide the overspend
04
Food-safety performance
  • Participating farms outperform comparators
  • Compliance imperfect
  • Most corrective actions completed

Caveat: Stronger compliance conditions required

Likely destination: Supporting argument and condition

So-what trap: Treat compliance as perfect
05
Pending policy amendment
  • Proposed change may affect programme design
  • Timing and impact unknown

Caveat: Critical uncertainty

Likely destination: Assumption, condition or extension-review trigger

So-what trap: Ignore it or let it paralyse the decision
06
Communications metrics
  • 2.1M impressions
  • 34 media mentions
  • Positive public feedback

Caveat: Does not prove continuation value

Likely destination: Annex or remove

So-what trap: Use as impact evidence
07
Registry caveat
  • 8–12% of registrations may be duplicates
  • Participation and volume may be overstated
  • Clean data in three weeks

Caveat: Use a range and explain

Likely destination: Professional treatment of uncertainty

So-what trap: Convert to one flattering point estimate
08
Senior voice note
  • The programme is a success
  • Ask for five years
  • Double the budget

Caveat: Advocacy unsupported by evidence

Likely destination: Test against evidence; do not treat as institutional recommendation

So-what trap: Convert seniority into certainty
What Strategy must produce
SCQA
  • Situation: The Local Produce Procurement Incentive Programme is completing its second season.
  • Complication: Uptake and procurement impact increased, but funding is exhausted, regularisation is required, and data quality and policy uncertainty remain.
  • Question: Should the programme continue, on what terms and at what cost?
  • Answer: Extend for one additional season within AED 45–55M, subject to stronger data, financial and policy controls before any longer-term commitment.
Three argument pillars
01
Impact—delivering benefits

Local share 12% → 22%; volume 19,750 tonnes; participating farms outperform comparators.

02
Conditions and risks—improvements required

Duplicate-registration risk; quality non-conformities; pending policy amendment; baseline alignment.

03
Funding and feasibility—controlled extension

Regularise Season 2; estimated AED 45–55M for Season 3; new allocation required.

Key uncertainties
  • Duplicate registrations: 8–12% risk
  • Baseline misalignment
  • Pending policy amendment
  • Cost range AED 45–55M
  • Impact attribution limits
The Council is requested to

Approve extension for one additional season within a funding envelope not exceeding AED 55M; direct completion of registry cleaning, regularisation and alignment before any further extension; submit a mid-season evaluation.

Six-stage process
01
1–5 min

Draft the ask first

02
6–10 min

Sort the fragments

03
11–15 min

Frame with SCQA

04
16–20 min

Build the Pyramid

05
21–25 min

State uncertainty honestly

06
26–30 min

Compress and test

Possible answer-first direction
Extend the programme for one additional season within AED 45–55M, subject to stronger data, financial and policy controls before any longer-term commitment.
Evidence-ranking matrix
AssessmentTreatmentExamples
High relevance / high reliabilityUse prominentlyProcurement volume, local-share trend, budget commitment, compliance comparison
High relevance / lower reliabilityUse with caveatsParticipation figures, impact attribution, pending legal effect
Low relevance / high reliabilityAnnex or removeCommunications reach, workshop satisfaction
Low relevance / low reliabilityRemoveCatering detail, promotional narrative
Peer-review scorecard
Comparison points
Verb chosenDurationFunding amountConditionsTreatment of uncertaintyResponse to the senior voice note
Common failure patterns
PatternWhat it looks likeCorrection
CompilationSummarises each fragment in sequenceReturn to the governing answer.
False certaintyUses 452 farms as an unquestioned factUse a qualified range.
OverreachRequests five years and doubled funding without evidenceMatch commitment to evidence maturity.
Excessive cautionRefuses to recommend anything until every uncertainty is resolvedRecommend with conditions and review points.
Hidden overspendMentions future budget but omits Season 2 varianceSurface material financial implications directly.
◎One page. One answer. One institutional voice. Use the evidence that matters, expose the uncertainty that matters, and ask only for what the evidence can defend.
Questions to reflect on
  1. Think of a real submission you worked on that was returned for "insufficient information." Looking back through today's lens: was information genuinely missing, or was it present but unsynthesized?
  2. What makes cutting a department's material feel risky in our organisational culture — and what could make it feel safe? What role should the Strategy Sector's mandate play in that?
  3. Fragment 8 gave you a senior instruction that conflicted with honest synthesis. How do you handle that conversation in real life, and what would you want your section head to say on your behalf?
  4. When is "note" the right verb for المطلوب, and when is choosing "note" actually an evasion — a way to avoid asking for the decision we really need?
  5. Where is the line between an honest range ("380–450 farms, pending registry cleaning") and an unusable answer? How much uncertainty can a one-page brief carry before the recommendation itself loses credibility?
  6. SCQA assumes we can state the Complication — the reason the Council is asking now. For a recent request your team handled, could you have written that sentence? If not, what does that tell you about the intake conversation?
Decision ruleThe Council needs one institutional answer—not a packet of departmental inputs.
01AnswerLead with the governing message.
02LogicUse two to four distinct arguments.
03IntegrityState assumptions and uncertainty.
From inputs to one voice

From information to institutional answer: the synthesizer’s standard

The difference between a document and a decision product is whether the Authority has done the thinking required to turn information into an answer.

Six reflection questions
01
Information versus synthesis

Was information missing—or was the answer missing?

02
The courage to cut

Why does removing material feel risky, and what deserves the annex instead?

03
Conflicting senior direction

How do you explain that advocacy does not match the evidence?

04
Choosing the right verb

When is “note” appropriate, and when does it hide a decision?

05
Honest uncertainty

When does a range remain credible?

06
Finding the complication

Why does the request exist now?

Seven principles
01
Answer before evidence

The Council asked a question; a stack of annexes is not an answer.

02
Build the Pyramid

Answer → two to four arguments → evidence.

03
Frame with SCQA

Situation, Complication, Question and Answer.

04
Group logically

No overlap and no gaps.

05
Make the ask actionable

Verb, object, amount, duration and conditions.

06
Make facts earn their place

Every fact must answer “so what?”—or move to the annex or be removed.

07
Tell the truth about uncertainty

State assumptions, explain limitations, show ranges and present trade-offs.

Peer-review scorecard
Self-guided learning safeguards
  • Protect the exercise: writing, cutting, peer review and comparing asks are the learning moments.
  • When time is short, compress examples—not the exercise or peer review.
  • Challenge the logic and evidence without personalising the discussion.
Likely objections and responses
Leadership wants full detail.

The one-page brief is the front door, not the whole house.

Answer-first feels disrespectful.

Courtesy and structure are different. Respectful tone; clear answer.

We cannot challenge senior preferences.

Inform, do not confront: show risk, evidence and a stronger defensible option.

We cannot control departmental inputs.

Better tasking helps, but constructing the answer remains Strategy’s responsibility.

Role-calibrated focus
Analysts
  • Pyramid structure
  • SCQA
  • Evidence selection
  • Writing the ask
  • Cutting unnecessary content
Senior leaders
  • Permission to synthesise
  • Evidence-based advice
  • Protecting quality over volume
  • Owning difficult conversations
◎Do not send what the organisation knows. Send what the organisation concludes. Evidence informs. Judgement decides.
View all takeaways
  • The Council asked a question; a pile of annexes is not an answer. Volume never compensates for absent synthesis — the compiled submission is how "insufficient for decision-making" happens to hard-working teams.
  • Lead with the answer, support it with 2–4 grouped arguments, and put evidence beneath the arguments — the Pyramid Principle in one sentence.
  • Open every memo and deck with SCQA: Situation, Complication, Question, Answer — four sentences that orient the reader and expose fuzzy thinking early.
  • Group arguments so nothing is said twice and no obvious counter-question is left unaddressed — that is all "MECE" needs to mean.
  • Write المطلوب first, and make it votable: verb (note / endorse / approve / fund), object, amount, duration, conditions.
  • Every fact must pass the "so what" test or move to the annex; the strongest 60 per cent, all pointing at the answer, beats the full 100 per cent pointing everywhere.
  • State assumptions, give ranges with their basis, and present options with trade-offs. Decision-makers forgive uncertainty; they do not forgive concealment.
Module 07

The Quality Gate

Quality is a process, not a heroic final read

What you will be able to do

01Design three review levels
02Run a five-minute red team
03Complete a fact-check pass
04Record the sign-off trail
05Diagnose review blind spots

The three-level quality gate

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

The Top 12 reasons submissions come back

  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

Explore the ideas

Open a card for the key message, the logic behind it, what good looks like and a practical example.

↗Visual briefDesign quality into the process
Key messageOne tired reader cannot check logic, facts, language and risk at once.
01SEPARATEGive each review pass one purpose.
02ASSIGNName the person responsible.
03RECORDPreserve evidence that the gate was completed.
Why it matters

One tired reader cannot check logic, facts, language and risk at once. Give each review pass one purpose. Name the person responsible. Preserve evidence that the gate was completed.

What good looks like

Write the review sequence for your next submission and assign a different purpose, person and record to every pass.

Practical example

SEPARATE — Give each review pass one purpose. · ASSIGN — Name the person responsible. · RECORD — Preserve evidence that the gate was completed.

1Visual briefThree review levels
Key messageThree levels catch three different classes of risk.
01SELFChecklist for completeness.
02COLD READOne-pass test for comprehension.
03LEADERSHIPJudgement on position, exposure and commitment.
Why it matters

Three levels catch three different classes of risk. Checklist for completeness. One-pass test for comprehension. Judgement on position, exposure and commitment.

What good looks like

Assign level one to the author, level two to an uninvolved peer and level three to leadership. Give each reviewer only the questions their level must answer.

Practical example

SELF — Checklist for completeness. · COLD READ — One-pass test for comprehension. · LEADERSHIP — Judgement on position, exposure and commitment.

Additional detail Essential practical content retained from the full module
01
Level one is self-review against the checklist
This is you, the drafter, with the pre-submission checklist in hand — the one you will find in your Templates and Checklists Pack after this course. Dig out your Five-Question Audit worksheet from Module 1 as well: the gaps you scored yourself on there are exactly the gaps this checklist is built to catch. It is mechanical, and it is meant to be mechanical. Is every sub-question of the ask (المطلوب) answered, in order? Are financial implications stated and quantified? Is every data point carrying an as-of date? Does every annex referenced in the text appear in the annex list, and does every annex in the list get referenced? Is the template the current one? Are the Arabic and English versions saying the same thing? You are not asking "is this good?" — you are asking "is this complete?" Tick by tick, line by line, honestly. The discipline here is to do it as a separate pass with the checklist physically in front of you, not from memory. From memory, you will tick boxes your document has not earned. And what level one is not for: judging your own clarity. You cannot. You know what you meant, so the page always reads clearly to you. That is not a character flaw; it is how every human brain works. Which is why we need level two.
02
Level two is the cold read — a peer who did not work on the submission reads it once, at normal speed, and then answers two questions without looking back at the document: what is the Council being asked to decide, and what are we recommending?
That is the entire test. If a competent colleague cannot answer both after one read, the submission is not ready — full stop, regardless of how much work went into it. Think about who your real reader is: a Secretariat reviewer or a Council member working through a stack of files, giving your memorandum minutes, not hours. The cold reader simulates that person. The moment your colleague says, "I think you're recommending the budget increase, but I had to read the recommendation (التوصية) twice," you have learned something no amount of self-review could tell you.
03
Level three is leadership sign-off — and it is a judgement review, not a proofread
By the time a submission reaches your section head or executive director, levels one and two must already be done and evidenced. Leadership's questions are different in kind: Is this the position the Authority should take? Have we coordinated with the entities the Council will expect us to have coordinated with? What will the Authority's Chairman be asked in the meeting, and does this document survive that question? Are we creating a precedent, a financial exposure, a commitment we cannot deliver? If a director-level reviewer is catching arithmetic errors, two things are true: the arithmetic error will probably be caught, and the positioning risk will probably be missed — because the director spent their scarce attention on what a checklist should have caught for free. Every typo that reaches level three steals judgement time from the questions only leadership can answer.
2Visual briefFive-minute red team
Key messageRed-team the submission by asking why it could be returned.
01CHAIRRead from the Secretariat’s perspective.
02HUNTUse the Top 12 as a search list.
03FIXRemove the return reason before sign-off.
Why it matters

Red-team the submission by asking why it could be returned. Read from the Secretariat’s perspective. Use the Top 12 as a search list. Remove the return reason before sign-off.

What good looks like

Set a five-minute timer and review a live draft by asking only: why might the Secretariat return this? Use the Top 12 as the hunting list.

Practical example

CHAIR — Read from the Secretariat’s perspective. · HUNT — Use the Top 12 as a search list. · FIX — Remove the return reason before sign-off.

Detailed visual guide

The Top 12 return reasons

Use this list as a five-minute red-team hunt before leadership sign-off.

01
Ask not fully answered

One or more request sub-questions are missing.

02
Financial implications weak

Costs are absent, vague or not quantified.

03
Coordination not evidenced

Affected entities, dates, positions or records are missing.

04
Data not dated

Figures are stale or lack an as-of date.

05
Numbers inconsistent

Text, tables, slides or language versions disagree.

06
Recommendation vague

Action, owner, cost or timeline is unclear.

07
Options not analysed

The submission presents only a take-it-or-leave-it proposal.

08
Legal review missing

Regulatory implications appear without a legal position.

09
Annexes mismatched

Referenced files are missing or attached files are never cited.

10
Formatting below standard

The wrong or poorly applied template undermines confidence.

11
Arabic and English diverge

Years, figures, scope or recommendation strength differ.

12
Late with no margin

The submission leaves no time for clarifying questions.

3Visual briefFact-check and sign-off
Key messageFacts and approvals need dedicated, traceable passes.
01FACTSReconcile figures, names and dates.
02SEQUENCEComplete each gate before the next.
03TRAILRecord reviewer, date and evidence.
Why it matters

Facts and approvals need dedicated, traceable passes. Reconcile figures, names and dates. Complete each gate before the next. Record reviewer, date and evidence.

What good looks like

Trace every repeated number, official name and date to its source, then record who completed each review and when.

Practical example

FACTS — Reconcile figures, names and dates. · SEQUENCE — Complete each gate before the next. · TRAIL — Record reviewer, date and evidence.

4Visual briefSet up the hunt
Key messageA defect hunt reveals the review roles your team is missing.
01FINDCode each flaw to a return reason.
02COMPARENotice what every group missed.
03DESIGNAssign a specific pass to each blind spot.
Why it matters

A defect hunt reveals the review roles your team is missing. Code each flaw to a return reason. Notice what every group missed. Assign a specific pass to each blind spot.

What good looks like

Compare the defects your team usually misses with the review roles you currently assign. Add a named pass for each recurring blind spot.

Practical example

FIND — Code each flaw to a return reason. · COMPARE — Notice what every group missed. · DESIGN — Assign a specific pass to each blind spot.

Exercise — Return to Sender
Key messageFind the seeded return reasons before a real reviewer does.
01SCANRead the request against the response.
02CODEMap each defect to the Top 12.
03LEARNTurn missed defects into review roles.
Why it matters

Find the seeded return reasons before a real reviewer does. Read the request against the response. Map each defect to the Top 12. Turn missed defects into review roles.

What good looks like

Audit a flawed page against the Top 12, record every missed defect and convert those misses into a stronger review design.

Practical example

SCAN — Read the request against the response. · CODE — Map each defect to the Top 12. · LEARN — Turn missed defects into review roles.

Questions to reflect on
  1. In your sector today, who plays the cold reader — and if the honest answer is "nobody", what would it take to make the cold read a standing rule rather than a favour you ask when there is time?
  2. Which of the Top 12 return reasons has actually cost your team a returned submission? What did the return cost in elapsed time, rework and standing — and which level of the three-level gate would have caught it?
  3. The red-team question is "why would I return this?" What makes that framing more productive than "is this good?" — and what does it tell us about how we should brief reviewers generally?
  4. Where should the sign-off record live in ADAFSA's current systems so that it is findable in an audit eighteen months from now — and who should own keeping it complete?
  5. Is there a tension between the quality gate and the deadline? When time is genuinely short, which elements of the gate would you compress, which would you never skip, and who has the authority to make that call?
  6. The exercise showed that different teams miss different defects. What does your team's specific pattern of misses suggest about the review roles you need to assign?
Decision ruleQuality is a designed sequence of specialised reviews—not one heroic final read.
01CompleteThe author checks every requirement.
02UnderstandA cold reader tests the message.
03OwnLeadership judges position and risk.
View all takeaways
  • Quality is a designed process, not a heroic final read — if it depends on one person's tired eyes, it will fail on exactly the submission that matters most.
  • Three levels, three jobs: self-review against the checklist for completeness, a cold read by an uninvolved peer for comprehension, leadership sign-off for judgement and risk. Never let one level do another's job.
  • The cold read has one test: after a single reading, can your colleague say what is being asked and what is recommended? If not, the submission is not ready.
  • Red-team every submission with five minutes in the reviewer's chair, hunting against the Top 12 return reasons — returns are predictable, and predictable means preventable.
  • The fact-check is its own pass: reconcile every repeated number, verify every entity name and title as current, and date every data point.
  • The review trail matters as much as the review: signatures in sequence, recorded where an auditor can find them — that is how an institution, not an individual, takes responsibility.
  • Submitting with margin is a quality feature: a day of headroom means the Secretariat can ask a question instead of issuing a return.