Decision-ReadyADAFSA · Strategy Sector

Home · Journey map · Self-paced

Stage 06 / 06

Follow Up & Learn

Every return is data; every request should make the next one faster.

01Fifteen-minute debrief — four questions
02Code every return against the Top 12
03Feed the precedent library and the glossary
Completion gate Before you move on — can you…
Start the stage →

Stage content

2 modules to complete this stage

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

Module 06

Building the Submission

Memoranda and decks that meet the standard

Learning pathFrom complete material to a decision product that stands alone
  1. 01
    Build the memo

    Make all eight sections answer the decision questions.

  2. 02
    Design the story

    Use action titles and one message per slide.

  3. 03
    Prove the evidence

    Source, date and reconcile every exhibit.

  4. 04
    Align both languages

    One decision, matching figures and terminology.

  5. 05
    Finish professionally

    Approved template, controlled file and linked annexes.

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 aloneWhat is on the page is what the institution has decided to say.3 minStart here
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 sectionsEight sections externalise the decision-maker’s checklist.6–9 minOpen full guide
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 slideA Council slide makes one claim and proves it.6–9 minOpen full guide
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 scrutinyA chart is evidence only when its meaning and origin are explicit.6–9 minOpen full guide
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 truthArabic and English must express one institutional truth.6–9 minOpen full guide
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 respectFormatting signals whether the content was handled with care.6–9 minOpen full guide
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.
Module 08

Closing the Loop

Every request makes the next one easier

Learning pathFrom sending the file to a system that improves with every request
  1. 01
    Submit with discipline

    Submit early, confirm receipt and stay available.

  2. 02
    Respond to returns

    Treat them as process signals, not personal verdicts.

  3. 03
    Capture the lesson

    Run a short review and name one change.

  4. 04
    Reuse the knowledge

    Update precedents, sources, terms and contacts.

  5. 05
    Measure the system

    Track acceptance, time, causes and input timeliness.

  6. 06
    Make the commitment

    Apply one visible practice to the next request.

What you will be able to do

01Complete the submission sequence
02Respond professionally to returns
03Run a 15-minute debrief
04Build four knowledge assets
05Track four system metrics
First-time acceptanceReturns per quarter 46% 11 Q1 61% 8 Q2 74% 5 Q3 88% 2 Q4
Illustrative What discipline buys: first-time acceptance climbs as return reasons shrink (illustrative)

Explore the ideas

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

↗Visual briefThe request is not over at sendSending the file completes a transaction; closing the loop improves the system.3 minStart here
Key messageSending the file completes a transaction; closing the loop improves the system.
01FOLLOWStay reachable for questions.
02LEARNCapture feedback while it is fresh.
03REUSEConvert experience into shared assets.
Why it matters

Sending the file completes a transaction; closing the loop improves the system. Stay reachable for questions. Capture feedback while it is fresh. Convert experience into shared assets.

What good looks like

Define what “closed” means for a request: receipt confirmed, queries resolved, lesson recorded and reusable assets updated.

Practical example

FOLLOW — Stay reachable for questions. · LEARN — Capture feedback while it is fresh. · REUSE — Convert experience into shared assets.

1Visual briefSubmit with disciplineDisciplined submission creates time for questions instead of returns.6–9 minOpen full guide
Key messageDisciplined submission creates time for questions instead of returns.
01CHECKConfirm final file and attachments.
02SENDUse the correct channel and reference.
03RECEIPTRecord acknowledgement and remain available.
Why it matters

Disciplined submission creates time for questions instead of returns. Confirm final file and attachments. Use the correct channel and reference. Record acknowledgement and remain available.

What good looks like

Create a submission checklist that covers final file, attachments, reference number, official channel, early delivery and receipt confirmation.

Practical example

CHECK — Confirm final file and attachments. · SEND — Use the correct channel and reference. · RECEIPT — Record acknowledgement and remain available.

2Visual briefTreat returns as dataA return is a signal about the process, not a verdict on the person.6–9 minOpen full guide
Key messageA return is a signal about the process, not a verdict on the person.
01RESPONDAcknowledge it the same day.
02ROOT-CAUSECode the reason honestly.
03CHANGEFix the process that produced the pattern.
Why it matters

A return is a signal about the process, not a verdict on the person. Acknowledge it the same day. Code the reason honestly. Fix the process that produced the pattern.

What good looks like

For the most recent return, acknowledge the issue, code the root cause and specify the process change that prevents recurrence.

Practical example

RESPOND — Acknowledge it the same day. · ROOT-CAUSE — Code the reason honestly. · CHANGE — Fix the process that produced the pattern.

3Visual briefThe 15-minute ritualFifteen minutes is enough to protect the lesson from being lost.6–9 minOpen full guide
Key messageFifteen minutes is enough to protect the lesson from being lost.
01ASKWhat was requested?
02RESULTWhat feedback was received?
03NEXTWhat one practice changes next time?
Why it matters

Fifteen minutes is enough to protect the lesson from being lost. What was requested? What feedback was received? What one practice changes next time?

What good looks like

Schedule a 15-minute debrief for the next major request and record the ask, response, feedback and one change for next time.

Practical example

ASK — What was requested? · RESULT — What feedback was received? · NEXT — What one practice changes next time?

Detailed visual guide

The four reusable knowledge assets

Feed these assets after every major request so the team does not restart from zero.

01
Precedent library

Original request, Restated Ask, final submission and feedback received.

02
Data-source registry

Indicator owner, custodian, authoritative system and refresh cycle.

03
AR/EN terminology glossary

One approved translation for every recurring institutional and technical term.

04
Focal-point contact map

Primary contact, deputy and the inputs each person can validate quickly.

4Visual briefMeasure the systemMetrics should reveal where the system needs help.6–9 minOpen full guide
Key messageMetrics should reveal where the system needs help.
01ACCEPTANCEFirst-time acceptance rate.
02FLOWCycle time and input timeliness.
03PATTERNReturn reasons over time.
Why it matters

Metrics should reveal where the system needs help. First-time acceptance rate. Cycle time and input timeliness. Return reasons over time.

What good looks like

Review first-time acceptance, cycle time, return reasons and department timeliness as trends. Choose one system intervention, not one person to blame.

Practical example

ACCEPTANCE — First-time acceptance rate. · FLOW — Cycle time and input timeliness. · PATTERN — Return reasons over time.

Detailed visual guide

Four metrics for improving the system

Review trends quarterly and use them to improve the process—not to assign blame.

01
First-time acceptance

Share accepted without a query or return; the headline health measure.

02
Cycle time by request type

Track light and heavy requests separately so the average does not hide delay.

03
Return-reason trend

See which Top 12 categories persist and whether fixes reduce them.

04
Department input timeliness

Identify where briefs, data shapes or standing arrangements need improvement.

5Visual briefBecome a trusted advisorReliability turns a request handler into a trusted advisor.6–9 minOpen full guide
Key messageReliability turns a request handler into a trusted advisor.
01ANTICIPATESee the decision behind the request.
02ADVISEOffer a defensible point of view.
03EARNBuild confidence through consistent delivery.
Why it matters

Reliability turns a request handler into a trusted advisor. See the decision behind the request. Offer a defensible point of view. Build confidence through consistent delivery.

What good looks like

On the next request, add one useful judgement beyond coordination: the decision implication, a viable option or a clear risk.

Practical example

ANTICIPATE — See the decision behind the request. · ADVISE — Offer a defensible point of view. · EARN — Build confidence through consistent delivery.

6Visual briefMake the commitmentOne observable commitment starts the improvement loop.6–9 minOpen full guide
Key messageOne observable commitment starts the improvement loop.
01CHOOSESelect one practice.
02SPECIFYMake the behaviour verifiable.
03APPLYUse it on the next live request.
Why it matters

One observable commitment starts the improvement loop. Select one practice. Make the behaviour verifiable. Use it on the next live request.

What good looks like

Write one behaviour you will use on the next live request and give a colleague permission to verify that you did it.

Practical example

CHOOSE — Select one practice. · SPECIFY — Make the behaviour verifiable. · APPLY — Use it on the next live request.

Exercise — The Commitment Card and the Rapid-Fire Review
Key messageConvert the course into one action the team can observe.
01RECALLReview the full six-stage journey.
02WRITEState one specific commitment.
03SHARELet a colleague check that it happened.
Why it matters

Convert the course into one action the team can observe. Review the full six-stage journey. State one specific commitment. Let a colleague check that it happened.

What good looks like

Complete the rapid review, then write one observable commitment beginning: “On the next Council request, I will…”

Practical example

RECALL — Review the full six-stage journey. · WRITE — State one specific commitment. · SHARE — Let a colleague check that it happened.

Questions to reflect on
  1. Who in our team is reachable during the post-submission window today — and what would a named-deputy arrangement need to look like for it to actually work during leave season and field inspection weeks?
  2. Think of the last submission that was returned or heavily queried. If you coded it honestly against the Top 12, which reason fits — and what single system fix would have prevented it?
  3. What is stopping us from running a 15-minute debrief after every major request — calendar, culture, or candour? Which of those is really the binding constraint?
  4. If we could only build ONE of the four knowledge-base assets this quarter — precedent library, data-source registry, terminology glossary, contact map — which would save us the most hours on the next ten requests, and why?
  5. How do we track department input timeliness in a way that our colleagues in the departments would themselves see as fair — and even useful to them?
  6. What would have to be true, twelve months from now, for the General Secretariat to describe ADAFSA's submissions as a model for other entities? What is the first visible step towards that?
Decision ruleClose every request in a way that makes the next one faster and stronger.
01FinishSubmit early and confirm receipt.
02LearnDebrief and code every return.
03ReuseStore precedents, sources, terms and contacts.
View all takeaways
  • Submit through the official channel, ahead of the deadline, and confirm receipt — early submission buys goodwill and, more importantly, margin for queries.
  • Stay reachable after you submit: a fast, composed answer to a Secretariat query can save a submission from becoming a return.
  • A return is data, not defeat — respond the same day, root-cause it against the Top 12, and log it; the pattern across returns is your improvement roadmap.
  • Run the 15-minute debrief after every major request: the ask, the submission, the feedback, the one thing to do differently. Lightweight enough to always happen.
  • Build the four-asset knowledge base — precedent library, data-source registry, AR/EN glossary, contact map — so a small team gets faster every quarter instead of starting from zero.
  • Track first-time acceptance, cycle time, return-reason trends and input timeliness — to improve the system, never to blame individuals.
  • Serve the decision, not the document: consistent decision-ready work turns the Strategy Sector from request handler into trusted advisor, and grows ADAFSA's voice in Emirate-level decisions.
Previous stage: Review & Submit

You have walked the road. Now prove it.

Open the red-team exercise in The Quality Gate and hunt the ten seeded defects — then keep the Quick Reference at your desk.

Take the red-team challenge Open the Checklist