Decision-ReadyADAFSA · Strategy Sector

Home · Journey map · Self-paced

Stage 04 / 06

Synthesize & Build

Lead with the answer; make every fact earn its place.

01Pyramid: answer → 2–4 arguments → evidence
02The ask (المطلوب) in one sentence — amount, duration, conditions
03Eight memo sections — financial implications and coordination never missing
Completion gate Before you move on — can you…
Start the stage →

Stage content

3 modules to complete this stage

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

Module 04

Orchestrating the Organization

Right inputs, first time, from every department

What you will be able to do

01Diagnose failed inputs
02Write a complete Tasking Brief
03Choose the right contributors
04Use checkpoints and early samples
05Validate every input

Explore the ideas

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

↗Visual briefInputs are designed upstream
Key messageDo not ask departments for “input”; design what a usable answer looks like.
01CONTEXTExplain the decision and why it matters.
02SPECIFICATIONDefine questions, format and completion.
03CONTROLCheck progress before the deadline.
Why it matters

Do not ask departments for “input”; design what a usable answer looks like. Explain the decision and why it matters. Define questions, format and completion. Check progress before the deadline.

What good looks like

Open the last tasking message you sent. Highlight where it explains the decision, specifies the output and defines completion. Rewrite anything left implicit.

Practical example

CONTEXT — Explain the decision and why it matters. · SPECIFICATION — Define questions, format and completion. · CONTROL — Check progress before the deadline.

Failure begins inside the tasking sentence

The anatomy of a failed input

Most bad inputs are not caused by weak departments; they are commissioned by vague tasking.

Opening scenario
General Secretariat request

Provide a brief on farmer-support programme performance covering uptake, expenditure and impact on local production. Required soon.

→
Analyst email
“Dear colleagues, kindly send us what you have on the farmer-support programmes at your earliest convenience.”
What the department heard
What Strategy intended

Send the specific evidence needed to answer three defined questions.

What the department received

Send any available material related to farmer-support programmes.

A rational response to the instruction received
Existing reportsOld presentationsRaw spreadsheetsPreviously prepared materialWhatever is quickest to locate
The department did not ignore the request. It followed the instruction it actually received.
Anatomy of the returned material
01
Old annual report

60 pages · two years out of date

Contains
  • Programme background
  • Activity summaries
  • Historical achievements
Does not answer or provide
  • Current uptake
  • Current spend
  • Current production impact
02
Conference presentation

Promotional rather than evidential

Contains
  • Promotional messages
  • Selected success stories
  • High-level charts
  • Programme narrative
Does not answer or provide
  • Definitions
  • Sources
  • Complete data
  • Decision-relevant analysis
03
Unusable spreadsheet

“FINAL v3 updated NEW.xlsx”

Contains
  • Raw rows and mixed fields
Does not answer or provide
  • Column headings
  • Units
  • Source notes
  • Reporting period
  • Definitions
  • Final-versus-draft indication
Timeline of failure
01Tuesday — Vague tasking issued
02Wednesday–Thursday — Department searches for existing material
03Friday — Three incompatible files return
04Monday — Strategy discovers that the three questions remain unanswered
The remaining choice
  • Retask the department: awkward and time-consuming
  • Improvise from inadequate evidence: fast but risky
Who failed?
Apparent failure: the department
  • Department sent old material
  • Shared unusable data
  • Did not answer the real questions
Root cause: the tasking
  • No questions specified
  • Evidence undefined
  • Time period absent
  • Format unspecified
  • Definitions absent
  • Quality standard absent
  • Deadline vague
  • No clarification contact
The department delivered what was requested: “what you have”.
The commissioning principle
Weak commissioning
1Vague tasking2Undefined output3Open-ended deadline4Inconsistent input
↔
Strong commissioning
1Precise tasking2Defined evidence3Standard format4Named deadline5Usable input
What should good tasking have said?
Weak commissioning
“Please send what you have on farmer-support programmes at your earliest convenience.”
Strong commissioning
“By 12:00 Thursday, provide eligible and enrolled farms by region and component; approved budget, expenditure and committed balance for the current year; and measured production impact with methodology, period and caveats. Use the attached template, cite every source and date, and name one clarification contact.”
What changed?
Exact questionsDefined periodRequired breakdownEvidence standardFormatDeadlineNamed contact
The orchestration shift
01Module 3: log, triage, clarify, confirm and plan backwards
02Module 4: specify, assign, standardise, follow up, challenge, accept or return
03Module 5: integrate, analyse, recommend and draft
Department and contributor landscape
Animal HealthPlant HealthFood Safety OperationsPolicy and RegulationResearch StationsFinanceData and Digital
Every contributor must understand
  • Why they are being asked
  • What exact contribution is required
  • How it connects to the final decision
  • When and how it must be delivered
Input acceptance test
◎Most bad inputs are commissioned, not committed. Ask departments exactly what the decision requires.
1Visual briefWhy good people miss
Key messageCapable colleagues cannot infer requirements you never stated.
01LOADThey manage competing priorities.
02CONTEXTThey may not see the Council decision.
03STANDARDThey need a visible definition of done.
Why it matters

Capable colleagues cannot infer requirements you never stated. They manage competing priorities. They may not see the Council decision. They need a visible definition of done.

What good looks like

Read your tasking as a busy department colleague. List every choice they would still have to guess and make those choices explicit.

Practical example

LOAD — They manage competing priorities. · CONTEXT — They may not see the Council decision. · STANDARD — They need a visible definition of done.

Diagnose the commission before blaming the input

Six predictable failure modes of unusable input

Every common complaint can be corrected upstream through task clarity, context, source fit, format and time.

What was wrong with the last input you could not use?
“It did not answer the question”
“The data was old”
“It came as a PDF”
“There were no definitions”
“It arrived too late”
“The numbers did not reconcile”
01
Vague tasking
What we sent

“Please send what you have on date-palm pests.”

What came back
  • Reports
  • Presentations
  • Historical statistics
  • Unfiltered background
  • Irrelevant attachments
Why it failed

The request names a subject, not a question.

Corrective discipline

Ask for eligible farms reporting red-palm-weevil infestation in each region during the defined year, plus the percentage treated within the approved response time.

Ask a precise question—not for a topic.
02
The wrong question
What we sent

“Council asks: what was the impact? Strategy asks: what activities were delivered?”

What came back
  • Workshops held
  • Farms visited
  • Subsidies disbursed
  • Inspections completed
Why it failed

Departmental tasking did not preserve the Council’s governing question.

Corrective discipline

Request production increase, compliance improvement, income change, response-time reduction and risk reduction.

Translate the Council ask into component evidence questions.
03
No context
What we sent

“Please provide inspection statistics.”

What came back
  • Routine figures
  • Limited checking
  • Material caveats omitted
Why it failed

Without purpose, contributors cannot apply greater judgement or surface material limitations.

Corrective discipline

Explain who requested the work, what decision it supports, why the input matters and how it will appear.

Context is not courtesy. It is free quality control.
04
No format specified
What we sent

“Any file and any structure will do.”

What came back
  • Narrative paragraph
  • PDF report
  • Screenshot
  • Spreadsheet
  • Percentages
  • Absolute figures
  • Different reporting years
Why it failed

Strategy inherits retyping, reformatting, recalculation, rechecking and new-error risk.

Corrective discipline

Specify file type, table structure, required columns, units, time period, breakdown, source notes and maximum narrative length.

If you do not define the container, you inherit the conversion work.
05
No real deadline
What we sent

“At your earliest convenience—or simply quote the external deadline.”

What came back
  • No operational priority
  • Late or rushed response
  • Strategy loses synthesis, quality review, approval and contingency time
Why it failed

A mood is not a milestone, and the submission date is not the input date.

Corrective discipline

Give an earlier internal date and time derived from the backward plan, with a reason and escalation expectations.

A deadline is a timestamp—not a mood.
06
Wrong source
What we sent

“Ask the director for detailed figures or ask the data team for institutional judgement.”

What came back
  • Opinion instead of data
  • Raw data without meaning
  • Delayed response
  • Missing definitions
Why it failed

Information ownership and authority to interpret or commit are different.

Corrective discipline

Verified figures → data owner; operational explanation → delivery team; technical judgement → expert; policy position → policy owner; commitment → accountable leader.

Choosing the source is an analytical decision—not an organisational reflex.
Six-mode diagnostic
ModeReturnsCorrective discipline
Vague taskingEverything availableAsk a precise question
Wrong questionActivity instead of impactPreserve the Council ask
No contextRoutine-quality responseExplain purpose and decision
No formatIncompatible files and unitsSpecify output structure
Weak deadlineLate or unusable responseSet the real dated deadline
Wrong sourceOpinion instead of data—or data without judgementSelect the right evidence owner
Tasking quality equation
1Task clarity×2Context×3Source fit×4Format×5Time= usable input

If one factor approaches zero, the input weakens regardless of contributor competence.

The fix has a name: the Input Commission
1Exact question2Required evidence3Source and owner4Format and definitions5Dated deadline6Acceptance standard
✓Good people cannot reliably produce good inputs from vague questions, missing context and undefined expectations.
2Visual briefThe Tasking Brief
Key messageSix elements turn a request email into a Tasking Brief.
01WHYContext and decision purpose.
02WHATNumbered questions and exact format.
03WHENTrue deadline, contact and definition of done.
Why it matters

Six elements turn a request email into a Tasking Brief. Context and decision purpose. Numbered questions and exact format. True deadline, contact and definition of done.

What good looks like

Draft the six Tasking Brief elements for a live request and ask a colleague to identify any remaining ambiguity without seeing the original request.

Practical example

WHY — Context and decision purpose. · WHAT — Numbered questions and exact format. · WHEN — True deadline, contact and definition of done.

The email transmits; the brief defines

Never task a department by bare email again

The email may transmit the request. The Tasking Brief defines the work.

Bare email
“Please send your inputs on abattoirs by Thursday.”
Produces
  • Different interpretations
  • Unstructured material
  • Missing evidence
  • Incompatible formats
  • Clarification after work begins
  • Rework for Strategy
Anatomy of the Tasking Brief
01
Context

Why is this input needed?

Example

The Council has requested a briefing on local red-meat supply resilience. Your input on abattoir throughput and capacity utilisation will support the current-situation section.

02
Exact questions

What must the department answer?

Example

What was total throughput by facility and species for the last three years? What is current utilisation against design capacity? What are the three main constraints during Eid peak demand?

03
Required format

What must the response look like?

Example

Excel, not PDF; rows by abattoir; columns for 2023–2025; values by head of livestock; separate tab for each species. Narrative response: maximum 150 words per constraint.

04
True internal deadline

When must the input arrive?

Example

Completed response by Thursday 14 May at 14:00 to allow consolidation, quality review and leadership approval before the external deadline.

05
Named contact

Whom should the contributor call before guessing?

Example

For questions, contact the named Strategy owner before beginning. Do not assume where scope, definition or format is unclear.

06
Definition of done

What makes the response complete?

Example

All questions answered in the specified format; every figure sourced and dated; assumptions and data gaps explicitly flagged.

Bare email versus Tasking Brief
Bare emailTasking Brief
Names a topicStates the mission
Requests “inputs”Asks exact questions
Leaves format openSpecifies the response
Uses vague timingGives a dated internal deadline
No clarification pathNames one contact
Assumes completion is obviousDefines done explicitly
Produces material to sortProduces evidence to integrate
The Tasking Brief as a reciprocal contract
Strategy commits to provide
  • Clear purpose
  • Precise questions
  • Defined scope
  • Usable template
  • Realistic deadline
  • Accessible support
⇄
Department commits to provide
  • Complete answers
  • Reliable evidence
  • Correct format
  • Sources and dates
  • Visible caveats
  • Delivery by the agreed time
The leverage equation
Bare email
  • 2 minutes to write
  • Four days waiting
  • Multiple clarification rounds
  • Reformatting
  • Missing evidence
  • Compressed integration
Tasking Brief
  • About 20 minutes to prepare
  • Aligned effort
  • Usable inputs
  • Faster consolidation
  • Fewer errors
  • Protected review time
The orchestration sequence
01Restated Ask confirmed
02Evidence requirements identified
03Contributor selected
04Tasking Brief issued
05Questions clarified before work begins
06Input received
07Acceptance test applied
08Accept, clarify or return
Quality check before issuing
Recommended one-page structure
  1. Context and purpose
  2. Questions to answer
  3. Required evidence and definitions
  4. Required format
  5. Deadline and delivery method
  6. Named contact
  7. Definition of done
Tasking Brief
Relevant answersComparable dataClear accountabilityFewer clarification loopsFaster integrationSubmission-ready evidence
◎Do not send “your inputs please”. Send a precise commission. Twenty minutes now saves days later.
3Visual briefChoose the right source
Key messageMatch each question to the person who owns the answer.
01OWNERUse data owners for authoritative figures.
02EXPERTUse specialists for interpretation.
03LEADERUse leadership for position and commitment.
Why it matters

Match each question to the person who owns the answer. Use data owners for authoritative figures. Use specialists for interpretation. Use leadership for position and commitment.

What good looks like

For every question, assign the best source: data owner, subject-matter expert or department leader. Use a short kickoff when several roles must align.

Practical example

OWNER — Use data owners for authoritative figures. · EXPERT — Use specialists for interpretation. · LEADER — Use leadership for position and commitment.

Three kinds of authority for one answer

Choosing your sources: who answers what?

Decision-ready submissions require data owners for facts, experts for meaning and leaders for the institutional position.

◎
Council request
“Brief leadership on a suspected avian-influenza outbreak, its implications and the recommended response.”
Three-lens source map
01
What is happening?

What is?

Data owners
Typical evidence or contribution
  • Suspected and confirmed case counts
  • Laboratory results
  • Affected farms and locations
  • Inspection completion rates
  • Vaccination or surveillance coverage
  • Registered populations
  • Dates, trends and geographic breakdowns
Best sources
  • Surveillance teams
  • Laboratory information owners
  • Inspection operations
  • Registration and licensing teams
  • Data and performance units
What Strategy should confirm
  • Verified figures
  • Definitions and units
  • Reporting period
  • Data source
  • As-of date
  • Known gaps

Common mistake: Asking a director for detailed figures that technical data teams own.

Likely result: Approximate numbers, memory-based response, delay and missing definitions.

For a number, go to the person or system that produces the number.
02
What does it mean?

What could happen?

Subject-matter experts
Typical evidence or contribution
  • Technical interpretation
  • Transmission dynamics
  • Severity and likelihood
  • Possible scenarios
  • Control options
  • Benchmark responses
  • Scientific caveats
  • Emerging risks and uncertainties
Best sources
  • Veterinary epidemiologists
  • Laboratory specialists
  • Biosecurity experts
  • Regulatory specialists
  • Field veterinarians
  • Research and technical advisers
What Strategy should confirm
  • Interpretation of evidence
  • Material implications
  • Plausible future scenarios
  • Risks of action and inaction
  • Technical feasibility of options
  • Caveats leadership must understand

Common mistake: Treating an expert’s preferred option as the department’s formal position.

Likely result: The expert can advise what is desirable but may not commit resources or accept institutional risk.

Experts interpret the evidence; they do not automatically speak for the institution.
03
What should ADAFSA do?

What is our position?

Department leadership
Typical evidence or contribution
  • Preferred recommendation
  • Operational commitment
  • Resource pledge
  • Risk ownership
  • Implementation responsibility
  • Departmental constraints
  • Formal endorsement
Best sources
  • Section heads
  • Department directors
  • Executive directors
  • Accountable programme owners
What Strategy should confirm
  • Supported option
  • Commitment available
  • Resources available
  • Risks accepted
  • Dependencies requiring escalation
  • Delivery owner

Common mistake: Asking an analyst or technical expert to commit the department to a course of action.

Likely result: Unendorsed commitments, policy misalignment and institutional risk.

A commitment must be endorsed by someone authorised to make it.
Source-matching matrix
NeedQuestionSourceOutput
FactsWhat is happening?Data ownerVerified dataset
MeaningWhat does it imply?Subject-matter expertInterpretation and scenarios
PositionWhat should we do?Department leadershipEndorsed recommendation
CommitmentWhat can we deliver?Accountable leaderOwner, resources and timeline
Worked avian-influenza example
1
What happened?
Surveillance and laboratory data owners

Confirmed cases, affected farms, geographic spread and reporting dates

Verified facts
2
What does it mean?
Veterinary epidemiologists and biosecurity experts

Likelihood, containment, risk, scenarios and options

Interpretation and risk assessment
3
What should ADAFSA do?
Department leadership

Recommended control, operational response, resources, dependencies and approval sought

Endorsed position and ownership
Five-minute source-mapping tool
D
Data question

Verified number · dataset · factual status

Data owner
E
Expert question

Interpretation · technical judgement · scenario analysis

Subject-matter expert
P
Position question

Recommendation · commitment · resources · risk acceptance

Department leadership
Wrong-source failure modes
1
Opinion instead of data

Question went to leadership instead of the data owner

Opinion-based numbers, delay and missing definitions
2
Data without meaning

Data team was asked for judgement it cannot authorise

Raw data without context and incompatible advice
3
Expert opinion presented as policy

Technical advice was not converted into an endorsed position

Overstated authority, policy misalignment and institutional risk
Use a kickoff huddle for complex requests
Use when
  • Cross-department request
  • Cross-government submission
  • Multiple interdependent datasets
  • Overlapping responsibilities
  • Tight deadline
  • Significant decision or sensitivity
30-minute agenda
  1. Restate the Council ask
  2. Walk through the evidence map
  3. Confirm boundaries
  4. Confirm outputs
  5. Confirm milestones
  6. Confirm ownership
What the huddle prevents
Without the huddle
  • Duplicate requests
  • Conflicting definitions
  • Data gaps
  • Overlapping analysis
  • Unowned questions
  • Late dependency discovery
  • Long reply-all chains
With the huddle
  • Shared interpretation
  • Visible dependencies
  • Clear accountability
  • Compatible inputs
  • Faster issue resolution
  • Stronger audit trail
Close the audit trail
1Agreed scope2Question owners3Deliverables4Deadlines5Dependencies6Decisions and assumptions
◎Ask the data owner for facts. Ask the expert for meaning. Ask leadership for the position.
4Visual briefManage the middle
Key messageThe middle of the input window must be actively managed.
01CHECKPOINTSchedule contact before risk becomes delay.
02SAMPLEReview 20–30% of the work early.
03ESCALATEFrame the deliverable risk, not the person.
Why it matters

The middle of the input window must be actively managed. Schedule contact before risk becomes delay. Review 20–30% of the work early. Frame the deliverable risk, not the person.

What good looks like

Put a checkpoint and an early-sample review in the calendar now. Phrase any escalation around risk to the submission and the decision.

Practical example

CHECKPOINT — Schedule contact before risk becomes delay. · SAMPLE — Review 20–30% of the work early. · ESCALATE — Frame the deliverable risk, not the person.

The middle is correction time, not waiting time

Managing the middle: catch problems while they are still cheap

Do not task on Day 1 and wait for the deadline. The middle of the timeline is correction time.

The input flight path
Disciplined route
01Tasking issued
02Early sample
03Light checkpoint
04Midpoint course check
05Final input
06Accepted on time
Failure route
01Tasking issued
02Silence
03Deadline-day surprise
04Problems discovered
05Rework or escalation
06Deadline at risk
The pattern to break
Day 1Task issued
Days 2–6Silence
Day 7Input arrives
Problems discovered
  • Wrong scope
  • Wrong breakdown
  • Incorrect format
  • Missing evidence
  • Unresolved definitions
  • Late delivery
Surprise when correction is most expensive.
Early-sample rule
At 20–30% of the input window
  • One completed table row
  • One drafted paragraph
  • One region’s figures
  • One worked calculation
  • One completed template section
Purpose
  • Confirm understanding
  • Test direction before full effort
“Please share one completed row by Tuesday so we can confirm the structure and definitions before the full dataset is prepared.”
Why the sample saves time
  • Error found on Day 2
  • One conversation
  • One revised example
  • About one hour
  • Minimal wasted work
  • Error found on Day 7
  • Full dataset rebuilt
  • Contributor retasked urgently
  • Integration delayed
  • Buffer consumed
  • Deadline at risk
How to frame the sample
Poor framing
“Send me what you have so far.”
Professional framing
“Please share a small sample so we can confirm that the format and interpretation work before you invest in the full response.”
  • Protection of contributor effort
  • Shared accountability
  • Early quality assurance
  • Permission to clarify
Proportionate checkpoint cadence
1
Short window: up to 5 working days
  • Early sample
  • One midpoint check
2
Medium window: 1–2 weeks
  • Early sample
  • One or two short checkpoints
3
Long window: 3 weeks or more
  • Early sample
  • Weekly checkpoints
  • Interim synthesis or milestone review
Each checkpoint asks only
  • Are you on track?
  • Any blocker?
  • Any ambiguity?
  • Has the evidence changed?
  • Is the agreed deadline still realistic?
Checkpoint ladder
1
Light touch

Work appears on schedule; no major dependency; sample is acceptable.

  • Two-line message or brief conversation
2
Working-level correction

Sample is off track, a blocker emerges or minor delay appears likely.

  • Clarify issue
  • Agree corrective action
  • Confirm next step
  • Record material change
3
Formal escalation

Working-level correction fails, deadline or quality is at risk, contributor is unreachable, dependency needs authority or issue threatens submission.

  • Escalate with the deliverable risk and help needed
Escalation etiquette
Person-focused escalation
“Ahmed has not sent the data and is not answering.”
Deliverable-risk escalation
“The Council submission is due Monday. The final Plant Health input is outstanding; without it we either miss the deadline or submit without pest-response evidence. Can you help unblock it?”
  • Submission context
  • Deadline
  • Missing dependency
  • Consequence
  • Support required
Five-part escalation formula
  1. Name the deliverable
  2. State the deadline
  3. Identify the dependency
  4. Explain the consequence
  5. Ask for help
Avoid
BlameMotive speculationEmotional languagePersonal criticismUnnecessary copying of senior recipients
Escalation decision tree
01Is the input on track?
02Can the issue be resolved at working level?
03Does it threaten quality, timeline or completeness?
04Continue monitoring or escalate as a deliverable risk
Protecting the relationship
Today’s objective

Deliver the current Council submission.

Long-term objective
  • Preserve effective support for the next submission
  • Next urgent request
  • Future data verification
  • Future policy development
  • Future crisis response
Complete middle-management rhythm
01Tasking Brief issued
02Early sample at 20–30%
03Sample checked and course corrected
04Proportionate checkpoint
05Working-level intervention
06Risk-based escalation
07Final input accepted
◷No silence until the deadline. No blame when escalation is required. Escalate the risk—not the person.
5Visual briefValidate before use
Key messageNo input enters the answer until it passes validation.
01COMPLETEEvery brief question is answered.
02TRACEABLESource and as-of date sit with every figure.
03CONSISTENTUnits, totals and both languages agree.
Why it matters

No input enters the answer until it passes validation. Every brief question is answered. Source and as-of date sit with every figure. Units, totals and both languages agree.

What good looks like

Validate one incoming file for completeness, source dates, units, totals, cross-language consistency and interdepartmental contradictions before accepting it.

Practical example

COMPLETE — Every brief question is answered. · TRACEABLE — Source and as-of date sit with every figure. · CONSISTENT — Units, totals and both languages agree.

Acceptance transfers ownership

The input validation gate: what you accept, you own

Nothing enters integration until it is complete, traceable, consistent and reconciled.

Ownership transfer
Before acceptance: department owns the input
  • Figures
  • Definitions
  • Sources
  • Technical accuracy
▣✓
After acceptance: Strategy owns its use
  • Interpretation
  • Integration
  • Consistency
  • Defensibility
Validation decision tree
1
Does the input meet the brief?

No → return with missing items specified

2
Are figures sourced, dated and consistent?

No → clarify or return

3
Are units, languages and departmental figures reconciled?

No → resolve with evidence owners

4
All checks pass

Accept into integration

15-minute validation gate: six checks
01
Complete against the Tasking Brief
Ask
  • Every numbered question answered?
  • Required format used?
  • Definition of done met?
  • Gaps and assumptions flagged?
Rule: Do not allow partial delivery to become invisible through acceptance.
02
Internally consistent
Ask
  • Rows add to total?
  • Percentages reconcile?
  • Narrative matches table?
  • Trend description matches data?
  • Baseline aligns with previous reporting?
Rule: You are reading with your eyes open—not conducting a full audit.
03
Source and as-of date attached
Ask
  • Source system or record
  • Reporting period
  • Known limitation
  • As-of date
  • Definition
Rule: A number without provenance is not yet an executive fact.
04
Units and definitions consistent
Ask
  • Tonnes versus kilograms
  • Hectares versus donums
  • Calendar versus fiscal year
  • Animals versus holdings
  • Monthly versus cumulative
  • Percentage points versus percentage change
Rule: Align units and definitions before analysis.
05
Arabic and English reconciled
Ask
  • Reconcile all material numbers
  • Match dates and labels
  • Check decimal separators
  • Confirm technical translations
  • Verify final versions
Rule: The reader should never discover a translation discrepancy before the author does.
06
Cross-department contradictions resolved
Ask
  • Different registers?
  • Different definitions?
  • Different reporting dates?
  • Farms versus licensed establishments?
  • Active versus registered entities?
Rule: Agree one authoritative figure or present the difference transparently with scope and reason.
What to do when validation fails
Temptation: fix it quietly
  • Appears faster
  • Avoids awkward conversation
  • Keeps drafting moving
  • Alters evidence Strategy cannot verify
  • Blurs accountability
  • Reinforces weak delivery
Professional response: return it precisely
  • State what is missing or inconsistent
  • Cite the failed Tasking Brief requirement
  • State the required correction
  • Name who must validate it
  • Give the revised deadline
Accept, clarify or return
Accept
Use when
  • All questions answered
  • Evidence current
  • Sources and dates visible
  • Definitions clear
  • Figures reconcile
  • Safe to integrate
Clarify
Use when
  • Minor ambiguity
  • One source note missing
  • Label or definition needs confirmation
  • No material rework required
Return
Use when
  • Material questions unanswered
  • Data cannot be verified
  • Figures contradict
  • Format prevents analysis
  • Units unclear
  • Position lacks endorsement
Credibility multiplier
01Unresolved contradiction
02Secretariat discovers it
03Questions reliability of the exhibit
04Questions reliability of the submission
05Applies greater scrutiny to future submissions
Incoming and outgoing quality gates
◇
Module 4 input validation gate

Checks departmental material before integration

◇
Module 7 submission quality gate

Checks the full memorandum before submission

Quick validation checklist
Organisational learning loop
01Precise Tasking Brief
02Early sample
03Validation gate
04Specific return feedback
05Better departmental capability
✓Validate before integration. Resolve contradictions at the source. Return material gaps precisely.
6Visual briefBuild relationship capital
Key messageReliable relationships reduce transaction cost on every future request.
01CLARITYBe predictable in what you ask.
02RESPECTReturn defects quickly and specifically.
03TRUSTClose the loop and recognise strong work.
Why it matters

Reliable relationships reduce transaction cost on every future request. Be predictable in what you ask. Return defects quickly and specifically. Close the loop and recognise strong work.

What good looks like

Close the loop with the contributing team: explain what was used, return defects respectfully and recognise input that met the brief.

Practical example

CLARITY — Be predictable in what you ask. · RESPECT — Return defects quickly and specifically. · TRUST — Close the loop and recognise strong work.

Trust earns the warning call and the extra mile

Relationship capital: the long game

Process secures compliance; relationships inspire the extra effort that protects quality under pressure.

Start from the contributor experience
Strategy view
01Request issued
02Input received
03Submission completed
04Work moves on
Department view
1Urgent request arrives
2Significant effort invested
3Input disappears
4No outcome shared
5No acknowledgement
6Next urgent request arrives
What does the department experience in return for supporting Strategy?
Transactional cycle
01Urgent request
02Department works under pressure
03Input disappears into Strategy
04No acknowledgement or outcome
05Motivation declines
06Next request requires more chasing
Consequences
  • Minimum viable response
  • Slower turnaround
  • Less proactive problem-solving
  • Caveats surfaced late
  • Lower willingness to prioritise Strategy
  • More escalation required
Relationship-capital flywheel
01
Ask professionally
  • Clear Tasking Brief
  • Realistic internal deadline
  • Accessible contact
  • Respect for contributor expertise
02
Support during delivery
  • Early sample protects effort
  • Proportionate checkpoints
  • Collaborative blocker resolution
  • Escalate the deliverable
03
Close the loop
  • Confirm submission
  • Share what happened
  • Explain how input was used
04
Recognise the contributor
  • Thank the person by name
  • Inform their manager
  • Describe the value added
05
Share outcome and credit
  • Connect contribution to leadership action
  • Make department role visible
  • Share credit appropriately
06
Trust compounds
  • Faster responses
  • Better early samples
  • Proactive warnings
  • Easier contradiction resolution
  • Extra discretionary effort
Habit 1: close the loop
Tell contributors what happened
  • That it was submitted
  • When it was submitted
  • How contribution was used
  • Any next step
  • Outcome where protocol allows
Example“The briefing was submitted Monday. Your abattoir-capacity analysis formed the core of the current-situation section, and a follow-up options paper has been requested.”
Why it works
  • Work had purpose
  • Expertise shaped the product
  • Effort reached senior decision-makers
  • Request was not administrative busywork
Habit 2: recognise contributors by name
Generic acknowledgement
“Thanks, everyone.”
Specific recognition
“Fatima’s disease-surveillance summary was delivered ahead of schedule and materially strengthened the submission.”
Why it matters
  • Recognition in performance discussion
  • Evidence of cross-department contribution
  • Stronger professional relationship
  • Motivation for next request
Habit 3: share outcomes and credit
01Departmental analysis
02Strategy integration
03Secretariat submission
04Council discussion or decision
Share where appropriate
Decision outcomeFollow-up directionApproved optionLeadership acknowledgementDepartmental role
Relationship capital as a measurable asset
Deposits
  • Clear requests
  • Respectful deadlines
  • Early support
  • Fair escalation
  • Specific thanks
  • Outcome sharing
  • Visible credit
Withdrawals
  • Vague urgent emails
  • Unexplained pressure
  • Silence after delivery
  • Public blame
  • Uncredited use of work
  • Repeated chasing
  • Escalation without working-level contact
Why relationships matter most under pressure
Normal conditions
  • Defined responsibilities
  • Standard timelines
  • Adequate compliance
Brutal deadline
  • Stay late to rerun figures
  • Call before a problem is visible
  • Move request higher in queue
  • Resolve contradictions rapidly
  • Offer better evidence than requested
Ten-minute relationship protocol
1
Within minutes

Confirm receipt of final input and thank contributor specifically

2
When submitted

Tell contributors the submission went out and where their input appeared

3
When outcome is known

Share it within protocol, credit contributors and inform managers of exceptional support

Apply it to a real tasking email
1Add missing context2Convert topics into exact questions3Specify format4Set real deadline5Name contact6Define done7Use language that preserves the relationship
↗Make contribution visible. Share the credit. Build the next response before you need it.
Exercise — From Bad Email to Tasking Brief
Key messageReplace a vague request with a brief a department can execute once.
01DRAFTWrite all six Tasking Brief elements.
02TESTAsk another team to interpret it.
03TIGHTENRemove every avoidable assumption.
Why it matters

Replace a vague request with a brief a department can execute once. Write all six Tasking Brief elements. Ask another team to interpret it. Remove every avoidable assumption.

What good looks like

Rewrite one vague departmental request as a complete Tasking Brief, test it with another reader and revise it until they produce the intended answer without further explanation.

Practical example

DRAFT — Write all six Tasking Brief elements. · TEST — Ask another team to interpret it. · TIGHTEN — Remove every avoidable assumption.

Self-guided exercise for an answerable commission

Exercise: from bad email to Tasking Brief

Convert an unclear request into a complete, source-specific commission that departments can answer correctly the first time.

1FormatSelf-guided or 3–4 colleagues
2Time25 minutes
3OutputOne complete Tasking Brief
4MaterialsScenario, bad email and blank canvas
The real situation
Monday, 10:00Next Monday, 12:00Thursday, 14:00
The Secretariat requests a brief on
  • Current farmer uptake
  • Expenditure to date
  • Evidence of production impact
  • Evidence of pest-control impact
Time needed after inputs
  • Integration
  • Arabic–English alignment
  • Quality review
  • Leadership clearance
The bad email
“Management urgently needs everything you have on the date-palm programme. Please send reports, statistics and presentations as available. This is high priority, so we need it by tomorrow morning at the latest.”
Rapid-fire diagnosis
  1. No decision context
  2. No exact questions
  3. No format
  4. False deadline
  5. No named contact
  6. No definition of done
  7. No source selection
  8. “Urgent” replaces explanation
Challenge: rebuild the request as a one-page brief
1Context2Exact questions3Required format4True deadline5Named contact6Definition of done7Source and checkpoint plan
Tasking Brief canvas
1 · Context and purpose

Explain the Secretariat request, the Council decision and how departmental input will be used.

2 · Exact questions
3 · Format by question
QuestionFormat
UptakeExcel table: region, eligible farms, enrolled farms, uptake %, reporting date, source
FinancialApproved budget, expenditure, committed amount, remaining balance
ImpactMaximum 200 words per outcome: baseline, current value, comparison period, methodology, caveats
4 · True internal deadline

Thursday at 14:00—protecting time for integration, reconciliation, quality review and approval.

5 · Named contact
6 · Definition of done

Every question answered in the required format; every figure sourced and dated; assumptions and gaps explicit; responsible department validates the response.

7 · Sources and checkpoints
RequirementSourceSampleDue
Uptake figuresData ownerOne completed regional rowTuesday 14:00
Spend and commitmentsFinance data ownerOne costing lineTuesday 14:00
Production interpretationAgricultural expertOne impact paragraphTuesday 14:00
Pest-control impactPlant Health expertOne impact paragraphTuesday 14:00
Institutional recommendationDepartment leadershipOne recommendation lineTuesday 14:00
Three-source test
D
Data owner

What is?

Uptake, spend, production figures, pest detections
E
Subject-matter expert

What does it mean?

Attribution, trends, caveats, impact interpretation
P
Department leadership

What is our position?

Recommendation, commitment, resources, risk ownership
Is a kickoff huddle warranted?
Yes, because
  • Two departments involved
  • Data and technical interpretation must align
  • Questions overlap
  • Timeline tight
  • Different definitions possible
Agenda
  1. Confirm Council ask
  2. Assign questions
  3. Agree definitions
  4. Confirm format and deadlines
  5. Surface dependencies
Exercise timeline
012 minutes — Diagnose the email
0213 minutes — Build the Tasking Brief
0310 minutes — Compare, test and improve
Self-comparison after completion
DimensionOriginal emailStrong brief
FocusEverything you haveFour or five targeted questions
Source selectionBoth departments copiedQuestions split by source
CoordinationNo kickoff huddleKickoff used where warranted
DeadlineTomorrow morningThursday 14:00
FormatAny formatDefined tables and narrative
ContactNo contactNamed owner
Completion standardNoneDefinition of done and acceptance checklist
Common mistakes to expose
!Topic headings instead of questions
!False urgency retained
!Wrong source assigned
!Early sample forgotten
Learning equation
  • 2 minutes to write
  • Four days waiting
  • Incompatible material
  • Clarification and rework
  • 13–20 minutes to prepare
  • Correct effort
  • Usable evidence
  • Faster integration
◎Do not make urgency the instruction. Make the required answer unmistakable.
Questions to reflect on
  1. Think of the worst input you ever received from a department. Using the six failure modes, whose failure was it really — and what would the Tasking Brief for that request have looked like?
  2. How much context about a Council request can we share with contributing departments, and where is the line? How do we align colleagues to the mission while respecting the confidentiality and protocol that Council correspondence demands?
  3. When two ADAFSA departments hold genuinely different figures for the same thing — different registers, different definitions, both defensible — who should own the resolution, and what does a good "single agreed figure" process look like in our organisation?
  4. Escalating the risk to the deliverable rather than complaining about a colleague sounds clean in a classroom. What makes it hard in practice here — and what happens to your next ten requests if you get it wrong once?
  5. Requesting an early sample at 20–30% of the window: in which of our standing relationships would this land as protection, and in which as distrust? What wording makes the difference?
  6. What does closing the loop look like in practice given confidentiality constraints — what can we realistically share with contributors about what the Council decided?
Decision ruleThe quality of departmental input is largely designed at tasking.
01BriefAsk precise questions in a precise format.
02ManageInspect early, not only at the deadline.
03ValidateWhat you accept, you own.
Turn good orchestration into an operating habit

From request to reliable input: orchestrating the organisation

Good submissions happen because Strategy commissions, coordinates and validates the right contribution.

Input excellence cycle
1Commission clearly
2Source intelligently
3Manage delivery actively
4Validate before acceptance
5Build relationship capital
Decision-ready input
Six leadership reflection prompts
01
Diagnose failure

Who really failed, and what Tasking Brief should have been used?

02
Context versus confidentiality

Share enough to align while protecting protocol.

03
Resolve conflicting figures

Two numbers may both be defensible; leadership should never see a contradiction the team could reconcile.

04
Escalate professionally

Escalate the risk, not the person.

05
Use early samples

Protect quality without creating a surveillance culture.

06
Close the loop

Let contributors see their impact without exposing confidential details.

Five-stage operating model
1
Commission the right input
Tool: Tasking Brief
  • Context
  • Questions
  • Format
  • Deadline
  • Contact
  • Definition of done
2
Choose the right source
Tool: Three-source triangle
  • Data owner: facts
  • Expert: meaning
  • Leadership: position
3
Manage the middle
Tool: Delivery timeline
  • Early sample at 20–30%
  • Light checkpoints
  • Working-level correction
  • Risk-based escalation
4
Validate before accepting
Tool: Incoming quality gate
  • Complete
  • Consistent
  • Traceable
  • Comparable
  • Languages reconciled
  • Contradictions resolved
5
Build relationship capital
Tool: Trust flywheel
  • Close loop
  • Recognise contribution
  • Share credit
  • Build future trust
Seven key principles
  1. Input quality follows tasking quality
  2. Never task by bare email
  3. Give people the “why”
  4. Match source to question
  5. Check understanding early
  6. Escalate the risk
  7. Accept ownership at validation
Common objections and responses
“We do not have time to write briefs.”

Proportionality matters: simple requests need simple briefs; complex submissions need disciplined commissioning.

“Departments ignore deadlines.”

Ask whether the reason, dependency and consequence were made credible and explicit.

“It is faster to fix it ourselves.”

That teaches weak standards, creates unverifiable corrections and repeats the problem next cycle.

“The kickoff huddle is another meeting.”

Thirty focused minutes can replace long email chains, misaligned assumptions and late discovery.

Seniority-calibrated application
Analysts
  • Write precise questions
  • Select sources
  • Define formats
  • Run validation checks
Section heads and leaders
  • Set the standard
  • Confirm interpretation
  • Protect review time
  • Manage escalation
  • Build relationship capital
Module boundaries and next transition
01Module 4: get the right inputs
02Module 5: turn inputs into the answer
03Module 6: build the bilingual document
04Module 7: review the final submission
◇Good inputs are not found. They are designed: commission precisely, coordinate respectfully, validate rigorously and build trust continuously.
View all takeaways
  • The quality of the input you receive is a direct function of the quality of the tasking you send — most bad inputs are commissioned, not committed.
  • Never task by bare email. The Tasking Brief carries six elements: context, exact numbered questions, specified format, the true internal deadline, a named contact, and a definition of done.
  • Give departments the "why": a colleague who knows the input is going to the Executive Council checks the numbers twice — context is free quality control.
  • Choose sources deliberately: data owners answer "what is", experts answer "what does it mean", leadership answers "what is our position". For requests touching three or more departments, a 30-minute kickoff huddle beats a week of email.
  • Ask for an early sample at 20–30% of the window — misunderstanding caught on day two costs an hour; caught on deadline day it costs the submission.
  • Escalate the risk to the deliverable, never a complaint about a colleague — same facts, opposite outcomes.
  • What you accept, you own: validate every input for completeness, consistency, sources and as-of dates, units, Arabic–English reconciliation, and cross-department contradictions — and never let the Council find a discrepancy you could have resolved.
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.

Opening scene
Day 6 of a 10-day assignment

The departmental inputs are complete—but the submission is not.

Do these materials collectively answer the Council’s question, or merely provide the ingredients?
Food-security planning tableAgricultural Affairs narrativeInspection and compliance summaryFinance budget extractPolicy and regulation note
Receiving all inputs marks the start of building the answer—not the end of the assignment.
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?

Poultry-biosecurity example
Is the Emirate’s poultry sector adequately protected against avian influenza this season?
Compiled packet
  • Vaccination log
  • Inspection schedule
  • Laboratory-capacity table
  • Surveillance statistics
  • Policy note
Reader must infer
  • Whether protection is adequate
  • Where vulnerability remains
  • Whether intervention is required
VS
Built answer

Yes, with one material qualification: protection is strong across commercial farms, but backyard holdings remain under-covered. ADAFSA recommends targeted surveillance and vaccination before the high-risk season.

Decision proof
  • Coverage evidence: 92% of commercial farms
  • Gap size: about 18% of backyard holdings remain uncovered
  • Risk implication: elevated spill-over exposure
  • Costed action: AED 2.4M
  • Owner and timing: Veterinary Services before 15 October
Hierarchy of the final submission
01
Top—main paper

Ask, answer, evidence-led judgement, implications, recommendation and decision sought

02
Middle—exhibits

Essential tables, charts, options, costing and risk analysis that prove the answer

03
Bottom—annexes

Detailed departmental data, methods, contracts and supporting records

One-voice test
Four-minute reader test
4minutes
Compiler versus answer-builder
Compiler
  • Organises what was received
  • Preserves departmental structures
  • Avoids choosing between views
  • Measures completeness by inclusion
  • Lets annexes carry the substance
  • Transfers intellectual work upward
  • Produces a package
↔
Answer-builder
  • Determines what the evidence means
  • Rebuilds around the Council question
  • Resolves or exposes disagreements
  • Measures completeness by decision-readiness
  • Uses annexes as supporting evidence
  • Completes intellectual work before submission
  • Produces an institutional position
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
Executive Pyramid
1
Answer

What does ADAFSA conclude or recommend?

2
Supporting arguments
The programme produces measurable impactCurrent uptake remains unevenThe redesign is financially viableDelivery risks can be managed
3
Evidence
The programme produces measurable impact
  • Yield data
  • Income change
  • Benchmarks
Current uptake remains uneven
  • Enrolment by region
  • Eligible versus supported
  • Participation barriers
The redesign is financially viable
  • Cost per beneficiary
  • Budget requirement
  • Scenario analysis
Delivery risks can be managed
  • Implementation capacity
  • Owners and timeline
  • Risks and mitigations
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
The three rules
01
Lead with the answer

State the conclusion, direction, material qualification and decision required at the start.

02
Support it with 2–4 grouped arguments

Arguments must be distinct, collectively sufficient and directly linked to the answer.

03
Place evidence under the argument it proves

Every fact must know which claim it serves; evidence is organised, not scattered.

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
Answer-first is not oversimplification
It does not mean
  • Ignoring nuance
  • Hiding uncertainty
  • Omitting background
  • Forcing a recommendation unsupported by evidence
↔
It means
  • State the best current conclusion
  • Include material qualifications
  • Organise evidence around the decision
  • Make uncertainty visible where it affects the recommendation
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
Transformation
01
Move the answer

Last line → first line

02
Organise evidence

Annex filing system → proof for specific arguments

03
Reduce history

Chronology → only the context needed for the decision

04
Make the recommendation precise

Continue → continue for two seasons, at current funding, with targeted reallocation

05
Compress the document

Accumulated information → decision-relevant meaning

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
Compiler versus answer-builder
Compiler
  • Organises facts chronologically
  • Begins with subject background
  • Refers generally to annexes
  • Says the programme should continue
  • Makes the reader find the logic
  • Describes the programme
↔
Answer-builder
  • Organises facts logically
  • Begins with the decision answer
  • Links evidence to specific claims
  • States duration, funding and adjustment
  • Makes the logic visible
  • Judges what should happen next
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.

SCQA in one view
S
Situation
What is true and stable?

State the agreed context in one or two sentences: what exists, ADAFSA’s role and the objective.

C
Complication
What changed—and why now?

Name the change, pressure, gap or trigger that created urgency.

Q
Question
What decision does this create?

State the decision that, once answered, fulfils the purpose of the submission.

A
Answer
What does ADAFSA recommend?

State the option, scope, duration, cost or funding, owner and material qualification.

SCQA explains why the reader is here.The Pyramid explains why the recommendation is right.
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.
Background-first versus SCQA
Background-first
  • Sector history
  • Programme evolution
  • Previous initiatives
  • Methodology
  • Current activity
  • Recommendation later
↔
SCQA
  • Stable context
  • Material change
  • Decision question
  • Recommendation
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
Where to use SCQA
01
Memorandum: opening paragraph or executive summary

02
Presentation: first slide or first two slides

03
Briefing note: first four to five sentences

04
Verbal briefing: opening spoken structure

◎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.

Pairwise overlap test
01Could two points be merged without losing meaning?
02Do they rely on the same evidence?
03Would removing one change the conclusion?
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.
Reader-to-interrogator shift
Complete logic
  • Reader understands
  • Tests the recommendation
  • Accepts or decides
↔
Logic with gaps
  • Notices omission
  • Becomes sceptical
  • Searches for more weaknesses
  • Asks for clarification
  • Submission slows or returns
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

Worked argument comparison
Weak grouping
  • Increases production
  • Strengthens food security
  • Reduces imports
  • Supports farmers
↔
Strong grouping
  • Delivers measurable production and farmer outcomes
  • Unmet demand remains concentrated in priority segments
  • Expansion is affordable within the envelope
  • Delivery capacity and risks are manageable
◎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.
Why the ask matters
Strong evidenceClear analysisCredible optionsComplete implicationsCompelling recommendationPrecise decision sentence
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
Weak versus strong examples
Vague ask
The Council is requested to support the enhancement of the Emirate’s food-security monitoring capabilities.
What is missing?
  • What does support mean?
  • What capability?
  • What action?
  • What cost?
  • What period?
  • What conditions?
Precise ask
Approve AED 18 million over three years to establish an integrated early-warning platform, subject to a data-sharing agreement and mid-term review.
Vague ask
The Council is requested to note the Authority’s efforts in the date-palm sector and provide directives as deemed appropriate.
What is missing?
  • Efforts is undefined
  • No institutional position
  • No timeframe or action
Precise ask
Note the results of the current season’s red-palm-weevil programme and endorse continuation at the current funding level for two further seasons.
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
How the ask governs the whole project
01
Verb

Approval route, evidence standard and sign-off seniority

02
Object

Scope, contributors and technical analysis

03
Amount

Finance involvement, value for money and budget source

04
Duration

Delivery plan, milestones and evaluation horizon

05
Conditions

Dependencies, risk controls and follow-up requirements

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.

Evidence filter
01Departmental material
02Filter 1—relevance: does it prove, qualify or act on the answer?
03Filter 2—defensibility: is it sourced, caveated and honest about uncertainty?
04Decision-ready memorandum
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

Compression principle
100% of material
  • Multiple directions
  • Repetition
  • High reading burden
  • Weak hierarchy
↔
Deliberate selection
  • Every fact points to the answer
  • Stronger logic
  • Faster comprehension
  • Greater decision value
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
Concealment versus candour
Conceal weakness
  • Select the most flattering figure
  • Omit the caveat
  • Present one scenario as certain
  • Hope the reader does not ask
↔
Surface it professionally
  • State the assumption
  • Quantify the range
  • Explain the limitation
  • Show the decision implication
  • Provide a plan to improve the evidence
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
Answer-building engine
1Decode2Judge3Group4Caveat5Recommend6Compress
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.

Four decision dimensions
01
Continue?

Is there enough evidence of value?

02
On what terms?

What controls or conditions are needed?

03
For how long?

One season, two seasons or longer?

04
At what cost?

What allocation can the evidence justify?

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.
Timing ribbon
01
5 min

Briefing

02
30 min

Team synthesis

03
10 min

Peer review

04
10 min

Plenary debrief or self-review

◎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.

Transformation journey
1
Inputs

Department reports, tables, notes and opinions

2
Synthesis

Filter, structure, challenge and decide

3
Institutional answer

One voice, one position, one decision

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.

One-page decision-brief standard
Top: answer + ask

Answer + Ask: recommendation, decision verb, object, amount, duration and conditions

Middle: three arguments
Argument 1—strategic or policy rationaleArgument 2—key facts, trends and analysisArgument 3—risks, trade-offs and implications
Side panel: context and caveats
Material uncertaintiesAssumptionsData limitationsConditions
Bottom: decision required

Decision required: what the Council is requested to decide and what the decision enables

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
Continuity into the next modules
01Module 4—commission better inputs
02Module 5—turn inputs into an answer
03Module 6—build the complete bilingual submission
04Module 7—apply the final quality gate
◎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 06

Building the Submission

Memoranda and decks that meet the standard

What you will be able to do

01Build the eight-section memorandum
02Repair common section failures
03Create action-title slides
04Protect exhibit integrity
05Maintain bilingual consistency

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

Explore the ideas

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

↗Visual briefThe page stands alone
Key messageWhat is on the page is what the institution has decided to say.
01STAND-ALONEAssume no author is present to explain.
02STANDARDUse the current approved structure.
03SCRUTINYMake every claim traceable.
Why it matters

What is on the page is what the institution has decided to say. Assume no author is present to explain. Use the current approved structure. Make every claim traceable.

What good looks like

Open the file without its covering email and ask whether a new reader can identify the decision, recommendation and evidence without your explanation.

Practical example

STAND-ALONE — Assume no author is present to explain. · STANDARD — Use the current approved structure. · SCRUTINY — Make every claim traceable.

Opening reflection

The document is the decision

The document is not a container for analysis. It is the visible expression of ADAFSA’s judgement, discipline and credibility.

The paper goes in alone. Make sure it can stand alone.
01The supplier-document test
01
Your immediate questions

Before reading deeply, a poorly assembled document makes you ask:

  • Was the author careful?
  • Are the numbers reliable?
  • Can I trust the conclusion?
  • Did anyone review this?
02
The same judgement applies to us

A reader assesses quality before accepting the argument. Presentation creates—or erodes—permission to trust.

The Council experiences the document, not the effort behind it.
02The Secretariat reader reality
The reader’s environment
  • Many submissions from many entities
  • Fixed Council time and a moving queue
  • Limited time for the first read
↔
What the reviewer cannot do

The governing question is: Can this document support a decision?

  • Rebuild your logic
  • Search for missing implications
  • Reconcile contradictions
  • Guess what you intended
03Behind the scenes versus in front of the reader
01
What the team did
  • Department inputs
  • Analysis sessions
  • Data checks
  • Expert discussions
  • Review meetings
  • Internal debates
02
What the Secretariat sees

Only the submission.

  • Not how hard the team worked
  • Not how many meetings happened
  • Not what the author planned to explain verbally
03
What they judge
  • Structure
  • Clarity
  • Evidence
  • Consistency
  • Professional discipline
The document is the only version of ADAFSA that reaches the decision-maker.
04Credibility equation and silent killers
=
The credibility equation

Strong analysis + weak document = weak submission. Strong analysis + strong document = decision-ready product.

01
Missing sections
  • Financial implications
  • Legal implications
  • Implementation requirements
Reader inference: “Was the impact considered?”
02
Poor architecture
  • Unnumbered annexes
  • Cross-references that fail
  • Inconsistent headings
  • Random sequencing
Reader inference: “Can this organisation manage complexity?”
03
Contradictory information
  • Memo: AED 20m
  • Deck: AED 25m
  • Annex: AED 18m
A small inconsistency creates a large credibility question.
05Three crafts, one institutional position
01
Memorandum—the decision document

Creates the formal decision record.

  • Executive summary
  • Background and current situation
  • Analysis and options
  • Implications and recommendation
02
Executive deck—the decision conversation

Helps leaders understand quickly.

  • One message per slide
  • Logical storyline
  • Visual hierarchy
  • Clear decision points
03
Exhibit—the evidence carrier

Proves the point without overwhelming the reader.

  • Clear title
  • Source and date
  • Definitions and units
  • Relevance to the argument
Memo: what decision is recorded? Deck: how is it communicated? Exhibit: what evidence makes it trustworthy?
06The document-alone principle
01
The document has no companion
  • No analyst beside it
  • No department expert beside it
  • No author explaining verbally
  • No meeting context to rescue it
02
It must answer independently
  • What is happening?
  • Why does it matter?
  • What evidence supports the conclusion?
  • What options exist?
  • What should leadership decide?
If a person must stand beside it to explain it, the document is not finished.
07Bilingual discipline and the quality test
01
Two languages ≠ two documents
  • One decision
  • One set of facts
  • One recommendation
  • One institutional voice
  • Validate numbers, dates, names, terms, wording and conditions
02
Document quality test
  • First impression—can the reader orient immediately?
  • Logic—does the structure lead to the decision?
  • Evidence—are claims supported?
  • Precision—are numbers, terms and recommendations exact?
  • Consistency—do all components agree?
  • Professionalism—does it reflect the Authority’s standard?
08Mindset shift
Old: the document summarises our work
  • Add information
  • Preserve everything
  • Explain later
  • Depend on context
↔
New: the document is the decision product
  • Structure thinking
  • Prioritise
  • Reconcile
  • Edit
  • Make judgement visible
◎The document is not where the decision is explained. It is where the decision is created.
1Visual briefEight memo sections
Key messageEight sections externalise the decision-maker’s checklist.
01CONTEXTSubject, background and current situation.
02CASEJustification, financial and legal implications.
03ACTIONCoordination, recommendation and annexes.
Why it matters

Eight sections externalise the decision-maker’s checklist. Subject, background and current situation. Justification, financial and legal implications. Coordination, recommendation and annexes.

What good looks like

Map every paragraph to one of the eight memo sections. Fill hollow financial, legal or coordination sections with specific, evidenced content.

Practical example

CONTEXT — Subject, background and current situation. · CASE — Justification, financial and legal implications. · ACTION — Coordination, recommendation and annexes.

Eight sections · eight reader questions

The anatomy of the memorandum

A strong memorandum makes the decision-maker’s thinking journey visible. Each section answers a silent question before it creates return risk.

01The eight-section memorandum map
01
Subject | الموضوع

What is this about, and why should I read it?

  • One precise decision-focused line
  • Action + topic + decision relevance
Tell the reader why the memorandum exists before they open it.
02
Background | الخلفية

Why does this exist and why now?

  • Originating Council request
  • Secretariat correspondence
  • Prior decision or directive
  • Relevant obligation
Explain the trigger, not the entire history.
03
Current situation | الوضع الراهن

Where do things stand today?

  • Current position
  • Key metrics and trends
  • Verified gaps
  • Facts with source, date and definition
Describe reality; do not argue yet.
04
Justification and analysis | المبررات

Why is this the right course of action?

  • Options and criteria
  • Trade-offs
  • Evidence interpretation
  • Reasoning behind the recommendation
Facts belong in the current situation; judgement begins here.
05
Financial and legal implications | الآثار

What does this cost, who pays, and what authority is required?

  • Cost, basis, horizon and funding source
  • Mandate, approvals, amendments and dependencies
A visible limitation is stronger than a vague statement.
06
Stakeholder coordination | التنسيق

Has everyone affected been engaged and aligned?

  • Entity, date, method and formal position
  • Support, concerns and resolutions
  • Outstanding issues and evidence reference
Transparency creates more credibility than artificial agreement.
07
Recommendation / decision sought | المطلوب

What exactly do you want me to decide?

  • Specific, actionable and decidable
  • Verb + object + amount + duration + conditions
Could the reader approve, reject or amend it in ten seconds?
08
Annexes | المرفقات

Where is the proof?

  • Tables, studies, letters and methodology
  • Numbered and referenced in the body
Annexes support the argument; they never replace it.
02The memorandum as a decision journey
01
Why are we here?

Subject + background

02
What is happening?

Current situation

03
What does it mean?

Analysis

04
What does it require?

Financial, legal and stakeholder implications

05
What should happen?

Recommendation / decision sought

06
What proves it?

Annexes

03The “missing question” diagnostic
SectionIf it is weak, the reader asks…
SubjectWhat am I deciding?
BackgroundWhy is this here?
Current situationWhat is the reality?
AnalysisWhy this option?
Financial / legalWhat are the consequences?
CoordinationWho else is affected?
RecommendationWhat do you want me to do?
AnnexesCan I verify this?
Every unanswered question creates return risk.
04Common memorandum failure patterns
01
The history essay

Too much background.

Fix: compress to the decision trigger.
02
The data dump

Facts without interpretation.

Fix: move from information to analysis.
03
Recommendation without implications

“Approve this” without consequences.

Fix: include financial, legal, operational and stakeholder effects.
04
The annex warehouse

Dozens of attachments.

Fix: use annexes only as evidence.
05
The empty recommendation

“The Authority will continue monitoring.”

Fix: state the decision.
05Quality test before submission
06Two golden annex rules
01
Rule 1—number and reference every annex

Example: “As detailed in Annex 2.”

02
Rule 2—no orphan annexes

If an annex is never referenced, the body is missing a point or the annex is unnecessary.

Confirm the current Secretariat template and formal guidance before submission.
◎A memorandum is not a record of work completed. It is a vehicle for a decision.
2Visual briefOne message per slide
Key messageA Council slide makes one claim and proves it.
01STORYLINEAgree the sequence before designing.
02ACTION TITLEWrite a full-sentence message.
03TITLE TESTRead titles only; the story should hold.
Why it matters

A Council slide makes one claim and proves it. Agree the sequence before designing. Write a full-sentence message. Read titles only; the story should hold.

What good looks like

Read only the slide titles. Rewrite each as a full-sentence message until the titles alone form a coherent storyline.

Practical example

STORYLINE — Agree the sequence before designing. · ACTION TITLE — Write a full-sentence message. · TITLE TEST — Read titles only; the story should hold.

From slides to story

The Council deck: build a decision story

A senior deck is not a collection of information. It is a sequence of conclusions supported by evidence—one message per slide.

01Storyline before slides
Wrong approach
  • Open PowerPoint
  • Create slides
  • Insert departmental content
  • Discover the story is unclear
  • Rebuild the deck
↔
Right approach

A ten-minute storyline review can prevent days of reconstruction.

  • Define the decision question
  • Write the storyline
  • Agree the messages
  • Create slides
  • Add evidence
02One-page storyline example
01
Slide 1

The programme improves farmer outcomes, but its design limits scale.

02
Slide 2

Demand exceeds available funding, creating a decision point this season.

03
Slide 3

Three options exist with different cost and impact profiles.

04
Slide 4

ADAFSA recommends Option 2 because it balances impact, cost and feasibility.

05
Slide 5

Approval is required to proceed under the proposed conditions.

03One message per slide
Weak slide—“Abattoir capacity”

It names a topic and leaves the conclusion to the reader.

  • Capacity, history, locations, staffing, risks, options and recommendations on one page
↔
Strong slide

“Existing abattoir capacity will be exceeded during the Eid peak unless throughput is expanded.”

  • Forecast demand
  • Current capacity
  • Gap size
  • Recommended action
04Action titles and the title test
01
Label title

“Food Security KPIs”

  • Names the topic
  • Requires interpretation
02
Action title

“Three of five KPIs are on track; the two gaps share a supply-chain data constraint.”

  • States the finding
  • Reveals the insight
  • Guides interpretation
03
The title test

Remove all content and read only the slide titles.

  • Do situation, complication, answer and support remain?
  • If titles read “Introduction, Background, Analysis, Next steps,” you have a filing structure—not an argument.
Titles alone should tell the story.
05The pyramid inside the deck
01
Slide 1—answer

What should leadership conclude?

02
Slides 2–4—arguments

Why is the conclusion correct?

03
Slides 5–8—evidence

What proves each argument?

04
Backup—detailed analysis

Calculations, methodology and additional charts.

06Density discipline and content placement
01
Working-file mindset
  • Every input, chart, detail and methodology note
Result: information overload.
02
Council-deck mindset
  • One message
  • Essential evidence
  • Clear implication
  • Required decision
Sparse is not thin; sparse is confident.
03
Main slide
  • Decision message
  • Critical evidence
  • Key implication
04
Backup / annex
  • Detailed calculations and supporting analysis
  • Full datasets, methodology and source material
Moving content does not lose it; it places it where it serves the reader.
07Executive reader behaviour
01
First 30 seconds
  • What is this about?
  • What is the conclusion?
02
First 3 minutes
  • Why should I believe it?
  • What are the implications?
03
Decision moment
  • What do you want me to do?
08Slide-creation workflow
01
Define

Decision question

02
Write

Storyline

03
Title

Action titles

04
Select

Supporting evidence

05
Design

Visual explanation

06
Test

Read titles only

09Council-deck quality checklist
◎Do not build slides. Build a decision story. If the titles do not tell it, the slides will not save it.
3Visual briefExhibits that withstand scrutiny
Key messageA chart is evidence only when its meaning and origin are explicit.
01MESSAGEVisually isolate the point that matters.
02TRACEShow source and as-of date.
03RECONCILEUnits and totals match the text.
Why it matters

A chart is evidence only when its meaning and origin are explicit. Visually isolate the point that matters. Show source and as-of date. Units and totals match the text.

What good looks like

Select one exhibit and add the message, units, source and as-of date. Recalculate totals and reconcile the figure with every other appearance.

Practical example

MESSAGE — Visually isolate the point that matters. · TRACE — Show source and as-of date. · RECONCILE — Units and totals match the text.

Evidence with a job

Exhibits that survive scrutiny

An exhibit is not decoration. It must prove one message clearly, accurately and consistently wherever it appears.

01Start with the message, not the format
01
Message: compliance improved consistently over three years

Best format: chart.

  • Direction
  • Trend
  • Change over time
  • Pattern
02
Message: the programme requires AED 24m across five facilities

Best format: table.

  • Exact values
  • Individual line items
  • Reference points
  • Traceability
If you cannot state the sentence the exhibit proves, the exhibit is not ready.
02Chart versus table decision guide
01
Use a chart when shape is the message
  • Comparison—region versus region or option versus option
  • Trend—production, compliance or cost over time
  • Shape or distribution—geographic concentration, risk profile or portfolio mix
02
Use a table when precision is the message
  • Exact budget or facility values
  • Commodity breakdowns and option costs
  • Reference checks, quotations and row comparison
03Common exhibit mistakes
01
Charting a table

Twelve budget lines and values to two decimals create no readable pattern.

Fix: use a table.
02
Tabling a trend

Five-year compliance data in a dense table forces the reader to calculate the pattern.

Fix: use a chart.
03
Exhibit without a message

“Farm statistics” says what it contains, not what it means.

Fix: use an insight title that states the finding and its caveat.
04Five evidence-integrity rules
1
Every number has a source

“1,200 registered farms—Farm Registration System.”

2
Every number has a date

When was it true? Is it current and comparable?

3
Every number has a unit

Tonnes or kg; hectares or dunums; AED thousands or millions; farms or percentage points.

4
Totals reconcile

A 100% total with segments adding to 97% creates a credibility question.

5
One number, one truth

Memo, deck, annex, executive summary, tables and charts must show the same approved figure.

05Number-consistency sweep
One independent reviewer should perform the sweep: authors see meaning; reviewers see evidence.
06Figure log
FigureApproved valueSourceAs-of dateUsed in
Programme costAED XFinanceDec 2025Memo p.3 · Slide 6
Farm participationX farmsRegistryJan 2026Summary · Exhibit 2
Compliance rateX%Inspection systemQ4 2025Slide 4
The log prevents contradictions, speeds updates, supports review and creates traceability.
07Exhibit acceptance gate
All six “yes”? The exhibit is ready.
08Good exhibit examples and the cheapest improvement
01
Trend chart

“Food-safety compliance improved steadily over three years, reducing the operational risk profile.”

  • Show trend and benchmark
  • Label source and date
02
Decision table

“Option 2 delivers the required capacity increase at lower cost and implementation risk.”

  • Option
  • Cost
  • Benefit
  • Risk
03
Thirty-minute quality investment
  • One reviewer
  • One figure log
  • One final pass
Potentially avoids returns, rework, credibility loss and leadership questions.
09Relationship to the full submission
01
Memorandum

Contains the decision logic.

02
Deck

Communicates the decision story.

03
Exhibits

Prove the evidence behind the decision.

04
Figure log

Protects consistency across all formats.

◎Every exhibit must earn its place—and survive the question: “Can you prove this number?”
4Visual briefTwo languages, one truth
Key messageArabic and English must express one institutional truth.
01OFFICIALTreat Arabic as the governing version.
02MEANINGTranslate the message, not word order.
03MATCHReconcile dates, figures and scope.
Why it matters

Arabic and English must express one institutional truth. Treat Arabic as the governing version. Translate the message, not word order. Reconcile dates, figures and scope.

What good looks like

Compare the Arabic and English versions line by line for dates, figures, scope and recommendation strength. Update the shared glossary when a term is settled.

Practical example

OFFICIAL — Treat Arabic as the governing version. · MEANING — Translate the message, not word order. · MATCH — Reconcile dates, figures and scope.

One decision · two languages · one source of truth

Two languages, one truth

A bilingual submission is not two documents. It is one decision expressed consistently across two languages.

01Opening principle
Wrong mindset

English first → rushed Arabic translation.

  • Arabic is treated as a courtesy copy
↔
Right mindset

Parallel bilingual production from the beginning.

  • The Arabic memorandum is the official government correspondence and receives equal planning, drafting and review discipline.
02One source-of-truth system
01
ADAFSA position

One institutional decision.

02
One master source

Approved facts and analysis.

03
One figure log

Every approved number.

04
One glossary

Approved Arabic–English terminology.

05
One recommendation

Identical force and conditions.

06
One final review

Both versions reconciled.

03Production workflow
Wrong workflow
  • Days 1–8: English analysis and drafting
  • Final evening: translate to Arabic
  • Problems: layout, numbers, terminology, strength and insufficient review time
↔
Better workflow
  • Start: identify Arabic and English requirements
  • Draft: develop both versions together
  • Review: reconcile numbers, terms and meaning
  • Finalise: one decision, two aligned expressions
04Right-to-left layout discipline
01
Mechanical mirroring fails
  • Charts become confusing
  • Tables lose logic
  • Visual hierarchy fights the reading direction
02
Design Arabic deliberately
  • Check reading start point
  • Reverse table columns where appropriate
  • Review chart labels and axis direction
  • Rebalance icons, arrows and whitespace
RTL changes design thinking—not only text direction.
05One number, two languages
01
Inconsistency example
  • Arabic memorandum: programme cost AED 45m
  • English deck: programme cost AED 50m
Reader asks: Which figure represents ADAFSA’s position?
02
Possible causes
  • Late update
  • Different rounding
  • Old draft version
  • Translation-stage change
Rule: one approved figure feeds every language and format.
06Bilingual consistency sweep
The sweep runs across languages—not only across documents.
07Translate meaning, not words
Word-translation mindset

A literal sentence may be grammatically correct but weak, unnatural, less decisive or tonally wrong.

  • Translate the sentence
↔
Meaning-translation mindset

Translate the decision, not merely the sentence.

  • Preserve intent
  • Preserve decision strength
  • Preserve technical accuracy
  • Preserve institutional tone
08Recommendation-force test
01
Check both languages communicate the same
  • Verb
  • Level of commitment
  • Conditions
  • Amount
  • Duration
  • Responsibility
02
Example

English: “Approve AED 20m for three years.” Arabic must not become “support, consider, encourage or facilitate.”

A weaker translation silently weakens the decision.
09Terminology control and ownership
01
Maintained AR/EN glossary
  • Foot-and-mouth disease
  • Biosecurity
  • Early warning system
  • Surveillance
  • Quarantine
  • Risk assessment
Use approved terminology consistently.
02
Technical teams own
  • Correct meaning
  • Subject terminology
  • Technical accuracy
03
Strategy and language reviewers own
  • Decision consistency and final narrative
  • Language quality and terminology consistency
  • Readability and final reconciliation
One accountable owner maintains the glossary, figure log and reconciliation process.
10Bilingual production checklist
◎Two languages. One decision. Zero contradictions. Language is part of decision quality.
5Visual briefFormatting shows respect
Key messageFormatting signals whether the content was handled with care.
01TEMPLATEUse the current approved file.
02CONTROLVersion filenames and number annexes.
03FINISHCheck pagination, print and references.
Why it matters

Formatting signals whether the content was handled with care. Use the current approved file. Version filenames and number annexes. Check pagination, print and references.

What good looks like

Run the finish check: current template, controlled filename, referenced annexes, clean pagination and a print-ready final file.

Practical example

TEMPLATE — Use the current approved file. · CONTROL — Version filenames and number annexes. · FINISH — Check pagination, print and references.

The document speaks before the author does

Formatting as respect: the invisible signals of quality

Formatting is not cosmetic design. It is a credibility and usability control system that lowers the effort required to make a decision.

01The quality signal before the first read
01
Structure

Required sections and logical hierarchy.

02
Consistency

Same conventions, figures and styles.

03
Navigation

References and annexes are easy to follow.

04
Accuracy

Numbers, labels and versions are controlled.

05
Presentation discipline

The page is readable on screen and paper.

02Formatting is not decoration
Weak interpretation

“Formatting is administrative work after analysis.”

  • Last-minute changes
  • Inconsistent structure
  • Broken references
  • Unclear navigation
↔
Professional interpretation

“Formatting is how we respect the reader’s time.”

  • Faster comprehension
  • Easier review
  • Lower cognitive load
  • Greater confidence
03Five formatting disciplines
01
Approved template
  • Use the current approved version
  • Preserve required sections
  • Do not create personal variants
  • Confirm current guidance
Templates create predictable structure and familiar navigation.
02
File naming discipline
  • Subject
  • Document type
  • Version
  • Date
Professional: ADAFSA_DatePalm_Programme_Memo_v03_2026-08-06.docx
03
Annex discipline
  • Number every annex
  • Reference it in the body
  • No orphans
  • Every annex has a reason to exist
04
Exhibit discipline
  • Source
  • As-of date
  • Units and definitions
  • Clear title and consistent figures
Every chart and table must answer: “Can the reader trust this?”
05
Print readiness
  • Margins and page breaks
  • Page numbers
  • Chart readability without colour
  • Colour dependence
  • Table alignment and annex references
04The black-and-white test
01
If meaning disappears when colour disappears…
  • The design was carrying the meaning—not the analysis.
02
Use redundant signals
  • Direct labels
  • Patterns
  • Annotations
  • Clear titles
05Silent return triggers
01
Missing sections
Reader: “Was this considered?”
02
Unnumbered or orphan annexes
Reader: “Where is the evidence?”
03
Exhibits without sources
Reader: “Can I trust this figure?”
04
Contradictory figures
Reader: “Which number is the Authority’s position?”
05
Recommendation without a decision
Reader: “What am I being asked to decide?”
Formatting exposes weak thinking; it cannot rescue it.
06The document-quality chain
01
Analysis

Clear problem, evidence and options.

02
Structure

Logical flow, complete sections and clear argument.

03
Formatting

Consistency, navigation, accuracy and presentation discipline.

04
Reader confidence

Time saved, trust earned, better decisions.

07Before-submission sweep
08Formatting ownership
01
Author owns
  • Content accuracy
  • Argument clarity
  • Evidence relevance
02
Coordinator / document owner owns
  • Structure and version control
  • References
  • Final package integrity
03
Reviewer owns
  • Challenge
  • Quality assurance
  • Reader perspective
Formatting is not owned by “someone at the end.” It is part of producing the decision product.
09Final checklist
◎Professional formatting is respect made visible. The reader should spend attention deciding—not searching or correcting.
Exercise — Slide surgery — and the memo sorting drill
Key messageRepair the story and structure—not merely the appearance.
01SLIDESGive each slide one action title.
02MEMOPlace each fragment in the right section.
03DEFECTSFlag weak evidence and vague recommendations.
Why it matters

Repair the story and structure—not merely the appearance. Give each slide one action title. Place each fragment in the right section. Flag weak evidence and vague recommendations.

What good looks like

Repair one weak slide and one memo section by fixing the decision logic, evidence and structure before changing visual formatting.

Practical example

SLIDES — Give each slide one action title. · MEMO — Place each fragment in the right section. · DEFECTS — Flag weak evidence and vague recommendations.

Self-guided executive document clinic

Submission surgery: from defects to decision-ready products

Good submissions are not created by adding more. They are created by diagnosing what prevents the reader from understanding and deciding.

The surgeon’s question: Does this help the decision—or only occupy space?
01The executive-document clinic
01
Patient arrives

Overloaded slide, silent chart and weak memorandum fragments.

02
Diagnosis

Identify the defects that block understanding.

03
Surgery

Remove, restructure and clarify.

04
Recovery

A decision-ready document.

02Memo sorting drill—the anatomy map
01
Subject

What is this about, and why should I care?

02
Background

Why does this memorandum exist now?

03
Current situation

What is the factual position today?

04
Justification and analysis

Why is this the recommended option?

05
Financial and legal implications

What does it cost and what authority is required?

06
Stakeholder coordination

Who was consulted and what is their position?

07
Recommendation / decision sought

What exactly should the Council decide?

08
Annexes

Where is the supporting proof?

03Two hidden memorandum defects
01
Coordination without evidence

“Relevant entities were consulted and support the expansion.”

  • Missing: who, when, how, exact position and evidence
Fix: entity name + date + formal position + referenced record.
02
Recommendation without a decision

“The Authority will continue monitoring and coordinating.”

  • The Council cannot approve, reject, fund or direct it.
Fix: convert it to “The Council is requested to approve…”
04Slide surgery—three patients
01
Patient 1—the wall of text
  • Diagnosis: dense bullets, mixed fonts, no hierarchy, source or implication
  • Surgery: write the action title, keep only evidence, use one conclusion
Lesson: the solution is stronger prioritisation—not smaller text.
02
Patient 2—the silent chart
  • Diagnosis: default title, no source, units, date, benchmark or risk
  • Surgery: message title, real names, units, source, date, capacity benchmark and highlighted gap
Lesson: the chart was not wrong; it was mute.
03
Patient 3—the topic label
  • Diagnosis: “Date Palm Sector” makes the reader interpret the finding
  • Surgery: replace with the conclusion, add the callout, source, date and implication
Lesson: the cheapest slide improvement is often the title.
05Action-title test
Weak title sequence

Result: table of contents.

  • Introduction
  • Background
  • Analysis
  • Findings
  • Next steps
↔
Strong title sequence

Result: decision story.

  • Demand will exceed capacity during Eid peak.
  • The gap is concentrated in two facilities.
  • Option 2 balances capacity, cost and risk.
  • Council approval is required to proceed.
06Self-guided exercise workflow
01
Minute 1

Receive the memo fragments and patient slides.

02
Minutes 2–8

Sort fragments into the eight memorandum sections.

03
Minutes 9–12

Diagnose the two hidden memo defects.

04
Minutes 0–2

Assign one patient slide.

05
Minutes 2–14

Rewrite the title, decide what stays and apply integrity rules.

06
Minutes 14–19

Peer review: title first, message second, evidence third.

07
Minutes 19–22

Apply the title test and final correction.

07Peer-review checklist
08Four learning moments
01
Cutting is synthesis

Removing content ranks it by decision value.

02
A chart without a message is decoration

The exhibit must prove a conclusion.

03
Titles are the cheapest improvement

They reveal whether the story exists.

04
An assertion can still fail

Coordination without evidence and a recommendation without a decision remain defects.

◎Do not improve a document by adding more. Improve it by making every element earn its place.
Questions to reflect on
  1. Think of the last submission your team prepared. Which section of the memorandum anatomy was weakest — and what question did that leave unanswered in the reader's mind?
  2. "Coordination claimed but not evidenced" — why does this failure damage trust more than an honest statement of an unresolved disagreement with another entity?
  3. Whose job should the number-consistency sweep be — the author, a peer, or a designated reviewer? What does your answer imply for how your division organises final production?
  4. In practice, which version of a submission gets built first in your team — Arabic or English? What risks does that sequence create, and what would it take to change it?
  5. A department sends you a 40-page technical annex and insists all of it "must go to the Council". How do you honour the substance while protecting density discipline?
  6. Look at the last deck you produced: would it pass the title test? What would it take to make title-test review a standard step before anything goes to your section head?
Decision ruleThe submission must carry the decision without its author in the room.
01MemoEvery section answers a reviewer question.
02DeckTitles alone tell the story.
03EvidenceFigures reconcile across every format.
From decision logic to decision product

The submission standard

A decision-ready submission is where thinking, evidence, language and presentation discipline come together.

01Decision-product quality model
1
Logic

Is the argument clear?

2
Evidence

Can every claim be defended?

3
Alignment

Do all formats and languages say the same thing?

4
Presentation

Can the reader understand and act quickly?

Clear thinking · reliable evidence · one bilingual truth · disciplined presentation.
02Six production reflections
01
Memorandum diagnosis

Which section failed—and what question did it leave unanswered?

SubjectBackgroundCurrentAnalysisImplicationsCoordinationRecommendationAnnexes
02
Coordination credibility

Why is an unsupported agreement worse than a disclosed disagreement?

Honest: entity, date, issue and resolution. Unsupported: no name, date, evidence or confirmation.
03
Ownership of number consistency

The author knows the intended meaning; a peer reviewer sees the written discrepancy; a designated quality owner makes the process repeatable.

04
Bilingual production sequence

Which language comes first today—and what risks does that create?

  • Plan Arabic production time
  • Maintain one figure source
  • Review meaning—not translation only
05
Protecting density discipline

When a department sends 40 pages, extract decision-relevant evidence, keep technical depth in annexes and preserve the contributor’s effort without transferring it to the reader.

06
The title test

Would the last deck survive if only its titles were visible?

If it says “Background, Analysis, Next steps,” it is a filing structure—not an argument.
03Memorandum standard—eight questions
SectionReader question
SubjectWhat is this about?
BackgroundWhy does this exist now?
Current situationWhat is true today?
AnalysisWhy this recommendation?
Financial / legalWhat does it cost and what authority is required?
CoordinationWho is affected and aligned?
RecommendationWhat exactly should I decide?
AnnexesWhere is the proof?
04Two biggest return triggers
01
Financial implications missing or vague

Weak: “Additional resources may be required.”

  • How much?
  • Who pays?
  • When?
  • From where?
Strong: “AED X over Y years, funded through Z, subject to conditions.”
02
Coordination claimed but not evidenced

Weak: “Relevant entities were consulted.”

Strong: “Entity X confirmed support through official letter dated [date], subject to [condition].”
Claims require evidence.
05Council-deck standard
01
Storyline first

Write the message sequence before PowerPoint.

02
One message per slide

One conclusion—not one topic—per slide.

03
Action titles

The title expresses the conclusion.

04
Title test

Print titles only and ask whether the story survives.

06Exhibit integrity and number sweep
01
Exhibit integrity standard
  • Source—where did it come from?
  • As-of date—when was it true?
  • Units—what is measured?
  • Reconciliation—does it match everywhere?
  • Message—what does it prove?
If one element is missing, the exhibit is not decision-ready.
02
Number-consistency sweep
  • Same number
  • Same unit
  • Same date
  • Same rounding
One person other than the author performs the final sweep across memo, deck and annexes.
07Two languages, one truth
01
Arabic memorandum

Official government document.

02
English materials

Working and supporting versions.

One source of truth: approved figures, approved terminology and approved recommendation.
08Formatting discipline
09Production ownership model
01
Analysts own
  • Action titles
  • Evidence selection
  • Figure logs
  • Annex references
  • Exhibit preparation
02
Section heads own
  • Storyline approval
  • Recommendation quality
  • Quality expectations
  • Final sweep ownership
03
Strategy leadership owns
  • Production discipline
  • Arabic planning
  • Standards enforcement
  • Institutional consistency
10Common objections and role focus
01
“The Secretariat template is different.”

The structure shown is typical logic; follow the current official template.

02
“One message per slide doubles the deck.”

It usually reduces content because weak slides contain multiple competing messages.

03
“Translation is handled elsewhere.”

Meaning and numbers remain the submitting team’s responsibility.

04
“The sweep is bureaucracy.”

Thirty minutes can prevent weeks of delay and credibility damage.

11Module handover
01
Module 5

Create the answer.

02
Module 6

Build the decision product.

03
Module 7

Install the quality gate.

◎The document is the decision. Make it worthy of the decision: clear logic, reliable evidence, one bilingual truth, disciplined presentation.
View all takeaways
  • The document is the decision: the Council and its General Secretariat judge what is on the page, and the page goes in without you.
  • The memorandum anatomy — subject, background, current situation, justifications, financial and legal implications, coordination, recommendation, annexes — is the decision-maker's checklist externalised; a missing or hollow section is an unanswered question, and unanswered questions come back. Confirm the exact template against the Secretariat's current guidelines.
  • The two most expensive memo failures: financial implications that are absent or vague, and coordination that is claimed but not evidenced with named entities, dates and referenced letters.
  • Storyline before slides; one message per slide; action titles as full sentences — and the title test: reading only the titles must tell the whole story.
  • Every exhibit carries source, as-of date and units; totals reconcile; and the same number never appears differently in two places — enforced by a number-consistency sweep across text, tables and slides, run by someone other than the author.
  • Arabic is the official language of government correspondence: plan real time for the Arabic version, reconcile figures across both languages, translate meaning not words, and maintain an AR/EN glossary of technical terms.
  • Formatting is respect made visible: approved templates, versioned file names, numbered annexes referenced from the body, no orphans, print-ready — these alone eliminate a whole class of returns.
Previous stage: Task & Collect Next stage: Review & Submit