Work in sequence and apply each idea to a live request.
Module 02
Decoding the Ask
Answer the question that was actually asked
Raw request
?
Restated Ask✓
Learning pathFrom an ambiguous sentence to one executable brief
01
Classify
Identify the request type and its quality standard.
02
Uncover
Separate the written ask from the decision behind it.
03
Deconstruct
Read verbs, scope, form and decision context.
04
Test
Catch outline drift, debate and incompatible inputs.
05
Restate
Turn interpretation into one confirmable paragraph.
What you will be able to do
01Classify the request type
02Separate the explicit and implicit ask
03Deconstruct the request sentence
04Spot early warning signs
05Write a Restated Ask
Explore the ideas
Open a card for the key message, the logic behind it, what good looks like and a practical example.
↗Visual briefDecode before you mobiliseA perfectly executed answer to the wrong question still fails.3 minStart here
Key messageA perfectly executed answer to the wrong question still fails.
01READSlow down at the request sentence.
02INTERPRETName what decision sits behind it.
03CONFIRMMake your reading visible and correctable.
Why it matters
A perfectly executed answer to the wrong question still fails. Slow down at the request sentence. Name what decision sits behind it. Make your reading visible and correctable.
What good looks like
Choose one live request and write the decision it is meant to support in one sentence. Compare that sentence with the literal wording before any department is tasked.
Practical example
READ — Slow down at the request sentence. · INTERPRET — Name what decision sits behind it. · CONFIRM — Make your reading visible and correctable.
1Visual briefSix request typesDifferent requests require different definitions of “good”.6–8 minOpen full guide
Key messageDifferent requests require different definitions of “good”.
01DATAAccurate figures, definitions and dates.
02ADVICEOptions, implications and recommendation.
03URGENTA concise, defensible answer at speed.
Why it matters
Different requests require different definitions of “good”. Accurate figures, definitions and dates. Options, implications and recommendation. A concise, defensible answer at speed.
What good looks like
Classify a live request as data call, status update, emerging-issue brief, cross-government input, decision memorandum or urgent query. Write the quality standard for that type.
Practical example
DATA — Accurate figures, definitions and dates. · ADVICE — Options, implications and recommendation. · URGENT — A concise, defensible answer at speed.
Request diagnostic
The six request types—explained
This is a working taxonomy, not a rigid rule. Hybrid requests should be classified by the decision they ultimately support.
Facts & information→
Strategic & decision-heavy→
Urgent & time-critical→
01
Facts & information
Data & information call
Provides authoritative facts, often for a larger piece of work you may not see.
◎
Primary need
Reliable facts
◷
Typical turnaround
A few working days (sometimes less)
▤
Expected output
A clean, sourced table
What good looks like
Accurate and clearly defined
Source and as-of date stated
Caveats prevent misuse
Classic misreading
A raw data dump—or a 15-page essay.
02
Strategic & decision-heavy
Strategic status update
Shows progress against a Council directive or an agreed strategic commitment.
◎
Primary need
Accountability against commitment
◷
Typical turnaround
One to two weeks
▤
Expected output
Milestones, percentage complete, risks and next steps
What good looks like
Progress against commitment
Variance from plan
Risks, recovery and next steps
Classic misreading
Reporting activity instead of progress.
03
Strategic & decision-heavy
Emerging-issue brief
Explains a fast-moving incident or risk so leadership can respond confidently.
◎
Primary need
Rapid situational understanding
◷
Typical turnaround
24–72 hours (sometimes same day)
▤
Expected output
What happened, what it means, what is being done and what leadership needs to know or say
What good looks like
What happened
What it means
What leadership needs to know or say
Classic misreading
Writing a technical report for a leadership audience.
04
Strategic & decision-heavy
Cross-government input
Contributes ADAFSA’s position and evidence to another entity’s policy or strategy.
◎
Primary need
ADAFSA’s position within a wider strategy
◷
Typical turnaround
One to three weeks (often negotiable)
▤
Expected output
Portable, evidence-based paragraphs with implications and commitments explicit
What good looks like
Position and supporting evidence
Written in the requesting entity’s structure
ADAFSA implications and commitments explicit
Classic misreading
Sending everything known instead of the specific input requested.
05
Strategic & decision-heavy
Decision memorandum
Seeks a Council decision such as approval, funding or regulatory endorsement.
◎
Primary need
A clear decision
◷
Typical turnaround
Several weeks and review cycles
▤
Expected output
Options, implications, resource impact and a precise decision sought
What good looks like
Answer first
Genuine options and implications
Clear recommendation and decision sought
Classic misreading
Treating it as a report rather than an argument.
06
Urgent & time-critical
Urgent leadership query
Supplies a short, defensible answer needed before a meeting or intervention.
◎
Primary need
A usable answer before the meeting
◷
Typical turnaround
Hours
▤
Expected output
A short answer with confidence level and caveats
What good looks like
Direct and timely
Honest about uncertainty
Best available answer now
Classic misreading
Sacrificing timeliness for completeness.
✓Before drafting, ask four questions
01What is the reader trying to do?
02What decision or product follows?
03How quickly must the answer be useful?
04Is it a hybrid—and which output dominates?
Real requests hybridise
A status update may also seek funding approval. Treat it as a hybrid, then identify the dominant decision and final required product before drafting.
◉
Turnaround times are indicative practice only. Confirm every deadline against the tasking letter and current Secretariat guidance.
2Visual briefThe question behind the questionThe written request and the real decision are not always identical.6–8 minOpen full guide
Key messageThe written request and the real decision are not always identical.
01EXPLICITWhat the letter directly requests.
02IMPLICITWhat leadership is trying to understand.
03EVIDENCEGather proof for both layers.
Why it matters
The written request and the real decision are not always identical. What the letter directly requests. What leadership is trying to understand. Gather proof for both layers.
What good looks like
Write two lines: what the request says explicitly, and what leadership may actually need to decide. Identify the evidence required for each.
Practical example
EXPLICIT — What the letter directly requests. · IMPLICIT — What leadership is trying to understand. · EVIDENCE — Gather proof for both layers.
Intent diagnostic
The question behind the question
Fulfilling the explicit ask while missing the implicit expectation is one of the most common failures in executive communication.
“Provide an update on the farmer support programme.”
One sentence · Two readings · Two different projects
Explicit askWhat is written on the page
Disbursement figures
Farms supported
Activities completed
Milestones achieved
Literal reading: Type 2 — Status update
Implicit expectationThe reason behind the request
Is the programme working?
Should funding continue?
Productivity and farm-income impact
Cost per supported farm
Performance versus alternatives
Consequences of stopping
Real question: A funding and impact decision
Path A — Literal interpretation
▥
Status update
What have we delivered?
Evidence required
Inputs
Activities
Outputs
Progress against milestones
Likely sources
Programme records
Finance data
Delivery teams
Path B — Strategic interpretation
◎
Programme effectiveness / funding decision
Is it working, and is it worth continuing?
Evidence required
Outcomes
Impact
Value for money — cost per farm
Counterfactual evidence — what if it stopped?
Future scenarios
Likely sources
Farm productivity data
Farmer income records
Evaluation teams
Economic analysis
Benchmark programmes
Other government data
Three habits to uncover the question behind the question
01
Context
What is happening around this request?
Budget cycle
Recent incidents
Related agenda items
National priorities such as food security
02
Requester’s situation
What larger product is the Secretariat assembling?
Briefing
Agenda item
Funding decision
Cross-government strategy or submission
03
The trail
What has happened before?
Previous Council directives
Earlier submissions
Unresolved commitments
Colleagues involved in prior rounds
The cost of discovering the real question late
Day 1
Correct diagnosis early
Identify the likely implicit question; mobilise outcome and impact data; engage the right departments.
Week 1
Inputs mobilised
Collect inputs and outputs as usual—plus the evidence the real decision requires.
Week 2
Analysis underway
Test effectiveness, value for money and future scenarios.
Week 3
Late discovery
Leadership is actually asking whether funding should continue.
Submission
Decision quality exposed
Without early diagnosis, the paper is descriptive rather than decision-ready.
Discipline: hypothesis, not fiction
1Form a hypothesis about the implicit expectation.
2Write the hypothesis down.
3Test it against context and prior records.
4Verify it through the clarification channel when the stakes justify it.
The failure is not forming the wrong initial hypothesis; it is never surfacing or testing one.
3Visual briefDeconstruct the sentenceFour passes turn a vague sentence into a workable brief.6–8 minOpen full guide
Key messageFour passes turn a vague sentence into a workable brief.
01VERBSWhat action is requested?
02SCOPEWhat is included, excluded and bounded?
03CONTEXTWhat output and decision will follow?
Why it matters
Four passes turn a vague sentence into a workable brief. What action is requested? What is included, excluded and bounded? What output and decision will follow?
What good looks like
Mark the verbs, scope words, output form and decision context in a real request sentence. Convert the annotations into a working brief.
Practical example
VERBS — What action is requested? · SCOPE — What is included, excluded and bounded? · CONTEXT — What output and decision will follow?
Request markup
Deconstruct the request sentence
Ten minutes of disciplined markup can prevent weeks of misaligned work and a returned submission.
ADAFSA is requested to assess the readiness of the emirate’s abattoirs for the upcoming Eid season and propose any measures required, for presentation to the relevant committee within two weeks.
Decision context inferred
Plausibly: whether additional resources or emergency measures are needed before Eid.
Pass 01✎
Verbs
What work are we contracted to perform?
Assess
Requires judgement
Must conclude: ready or not ready
Must explain the evidence behind the verdict
Propose
Requires actionable recommendations
Must include owners, costs and timelines
Moves beyond aspiration into commitment
Pass 02◎
Scope
Where are the boundaries?
All abattoirs or selected facilities?
Public, municipal and private?
Red meat and poultry?
Abu Dhabi City, Al Ain and Al Dhafra?
Peak slaughter days only?
Livestock imports, markets and inspections included?
Current readiness or readiness after planned interventions?
Pass 03▤
Form
What container must the answer fit?
Likely implies
Executive slides
Short decision memorandum
Supporting technical annex
Likely does not imply
A forty-page technical study
Unstructured departmental reports
A raw spreadsheet without interpretation
Pass 04◆
Decision
What must leadership decide?
Likely decision
Whether additional resources, temporary capacity or emergency measures are required before Eid
Possible approvals
Additional slaughter capacity
Extended operating hours
Temporary staffing
Inspection surge resources
Veterinary coverage
Traffic and crowd-management arrangements
Emergency procurement or budget
From request to work contract
01
Judgement required
Are the abattoirs ready for Eid demand?
02
Scope to confirm
Facilities, geography, species and operating period.
03
Output required
Committee-ready slides or memorandum, with annex as needed.
04
Decision enabled
Approve measures, funding, owners and deadlines.
05
Deadline
Two weeks—including internal review and sign-off.
Quick check before you start
✓All verbs identified and translated into work?
✓Scope boundaries clarified explicitly?
✓Expected output form confirmed?
✓Decision context understood?
✓Assumptions validated where the stakes justify it?
4Visual briefThree warning signsDivergence is evidence that the interpretation is unstable.6–8 minOpen full guide
Key messageDivergence is evidence that the interpretation is unstable.
01OUTLINEYour structure answers another question.
02DEBATEThe team cannot agree what belongs.
03INPUTSDepartments return incompatible material.
Why it matters
Divergence is evidence that the interpretation is unstable. Your structure answers another question. The team cannot agree what belongs. Departments return incompatible material.
What good looks like
Review your draft outline and department tasks. If they answer different questions or provoke repeated debate, pause and repair the interpretation.
Practical example
OUTLINE — Your structure answers another question. · DEBATE — The team cannot agree what belongs. · INPUTS — Departments return incompatible material.
Early diagnosis
Red flags: how to know you have misread
Misreading rarely appears as a request problem. It disguises itself as drafting drift, team debate or inconsistent departmental inputs.
Three red flags in ascending order of costDrafting drift→Team misalignment→Interpretation multiplied→
01
Drafting drift
The outline answers a different question
Low cost · 5 minutesWhat you observe
The request sentence and planned submission do not align.
Request sentence
“Assess the readiness of the emirate’s abattoirs.”
Draft outline
Number of abattoirs
Facility locations
Daily slaughter capacity
Historical throughput
What it really means
The team has shifted from assessment—judgement—to description—inventory. The request asks for a verdict: are abattoirs ready or not ready, and why?
Corrective action
Stop before drafting begins
Re-read the request sentence and confirm the verbs
Rewrite the governing question
Rebuild the outline around that question
02
Team misalignment
The room keeps debating what to include
Moderate cost · hours / daysWhat you observe
The team repeatedly argues about individual content items.
Do livestock markets belong?Should import figures be included?Does the analysis cover poultry?Only peak slaughter days?Do we include inspections before Eid?
What it really means
Content arguments are often scope arguments wearing a disguise. The team is applying different interpretations of the request boundaries.
Corrective action
Stop debating individual content items
Return to the request and jointly confirm facilities, geography, species, time period, activities and exclusions
Document a short scope statement and circulate it
03
Interpretation multiplied
Departments return different types of answers
High cost · reworkWhat you observe
Four departments receive the same tasking and return four different products.
OperationsO
Facility statistics
RiskR
Readiness-risk assessment
ProjectsP
Improvement plan
FinanceF
Request for clarification
What it really means
The ambiguous request has been broadcast and multiplied. Each department decoded the task independently because no common interpretation was provided.
Corrective action
Pause consolidation and reissue a clarified tasking note
State the governing question
Define scope and exclusions clearly
Specify the exact input required from each department
Provide a common template and timelines
Reset deadlines where necessary
What the symptom says—and what it may actually mean
Visible symptomLikely diagnosisPrimary question
01Weak or drifting outline
The verbs were misread; the outline answers a different question.
Are we answering what the request actually asked?02Repeated content debates
The scope was not aligned; different boundaries are being applied.
Do we agree what the request covers and excludes?03Incompatible departmental inputs
The interpretation was not translated into a clear tasking.
Did everyone receive the same understanding and instructions?
The escalating cost curve
Early catchBefore drafting
Rewrite the outline
Minor re-planning
Minimal time lost
High quality preserved
Mid-stage catchDuring team design
Reopen team decisions
Revisit scope
Delay builds in
More review cycles
Late catchAfter tasking departments
Retask multiple departments
Rework and resend
Delayed consolidation
Less time for review
Lower quality risk
Erodes Secretariat confidence
5Visual briefThe Restated AskThe Restated Ask converts interpretation into a controlled commitment.6–8 minOpen full guide
Key messageThe Restated Ask converts interpretation into a controlled commitment.
01SCOPEState what the response will cover.
02DELIVERABLEName format and exact deadline.
03ASSUMPTIONSExpose what must be confirmed.
Why it matters
The Restated Ask converts interpretation into a controlled commitment. State what the response will cover. Name format and exact deadline. Expose what must be confirmed.
What good looks like
Draft one paragraph covering scope, deliverable, deadline and assumptions. Name the person who will confirm it and where that confirmation will be retained.
Practical example
SCOPE — State what the response will cover. · DELIVERABLE — Name format and exact deadline. · ASSUMPTIONS — Expose what must be confirmed.
Mandatory artefact
The Restated Ask: your first deliverable
No substantive work begins until the interpretation has been written in one visible, checkable paragraph.
Start gateNo work begins without a Restated Ask
ScopeDeliverableDeadlineAssumptions
01
Scope
State what is included—and just as deliberately what is excluded.
02
Deliverable
Name the form, language and approximate size of the product.
03
Deadline
Record the final deadline and any internal checkpoints or review time.
04
Assumptions
Expose every interpretive choice, including the suspected question behind the question.
Completed example¶
We understand the committee is deciding whether additional measures or resources are required before Eid. We will assess operational readiness—capacity, staffing, inspection coverage and hygiene compliance—of all licensed abattoirs in the emirate for the Eid al-Adha peak period, and propose specific measures with owners, indicative costs and timelines. Deliverable: a presentation of roughly twelve slides with a one-page summary memorandum, within two weeks. Assumptions: livestock markets and import logistics are excluded except where they directly constrain abattoir throughput; readiness is measured against last Eid’s peak demand plus a margin; all planning figures will be marked as indicative.
Why it works
01
Visible
Interpretive choices are written down.
02
Discussable
Others can test the same interpretation.
03
Correctable
Misalignment is fixed before it becomes work.
How it is used at work
◎
Tasking reference
Departments receive one common interpretation.
◎
Outline yardstick
Every section can be tested against the governing ask.
◎
Scope anchor
Later debates return to the paragraph, not to memory.
What happens next
Stage 3 explains how to confirm the Restated Ask, route clarification through the correct channel and retain an audit trail.
Interpretation is work. Unexamined interpretation is risk.
Exercise — The Divergence Test
Key messageUse disagreement to find ambiguity before it becomes rework.
01COMPAREInterpret the same request independently.
02EXPOSEMark where answers diverge.
03RESTATEAgree one paragraph before tasking.
Why it matters
Use disagreement to find ambiguity before it becomes rework. Interpret the same request independently. Mark where answers diverge. Agree one paragraph before tasking.
What good looks like
Ask two colleagues to interpret the same request independently, compare their proposed outputs and use the differences to produce one confirmed Restated Ask.
Practical example
COMPARE — Interpret the same request independently. · EXPOSE — Mark where answers diverge. · RESTATE — Agree one paragraph before tasking.
Applied practice
The Divergence Test
Experience how capable people interpret ambiguous requests differently—and practise turning ambiguity into one clear Restated Ask.
◎
Purpose
Reveal interpretive divergence
●
Mode
Solo or 3–4 peers
◷
Duration
20 minutes
▤
Output
Three Restated Asks
Complete all four steps for every card
01
Classify
What type of request is this?
02
Deconstruct
Mark the verbs, scope, form and decision context.
03
Infer
What is the question behind the question?
04
Restate
Write one aligned paragraph covering scope, deliverable, deadline and assumptions.
Complete all four steps independently before comparing answers. Do not ask clarification questions during the test.
Card 1Likely typeData and information call
“The General Secretariat requests updated figures on local poultry and egg production and current self-sufficiency levels, in the context of the forthcoming food security review.”
Key ambiguities to resolve
Which years are “updated”?
Poultry meat, eggs or both?
Self-sufficiency based on production ÷ consumption?
Volume or value?
Emirate-level or national comparison?
Table, narrative or both?
Which definitions and caveats are required?
Hidden clue
“In the context of the forthcoming food security review.”
Likely question behind the question
What do these figures imply for food-security performance, gaps and future priorities?
Card 2Likely typeStatus update—possibly hiding a decision request
“ADAFSA is requested to provide a status update on the date palm sector development programme, highlighting key challenges and the way forward.”
The request can split into two readings
Reading A — Progress update
Milestones achieved
Activities completed
Delivery against plan
Current risks and next steps
Reading B — Programme redesign
What is not working?
What should change?
Which new interventions?
Which resources or approvals?
Hidden clue
Does “the way forward” mean planned next steps—or recommendations for changing the programme?
Likely question behind the question
Is leadership asking for progress, or for a decision on the programme’s future?
Card 3Likely typeUrgent emerging-issue brief
“Leadership requires a brief on the recent increase in red palm weevil detections in the Al Dhafra Region and the Authority’s response, by tomorrow morning.”
What the brief may actually be for
Reassure leadership that the issue is contained
Prepare leadership to answer questions
Seek additional operational resources
Trigger an escalation or intervention
Hidden clue
Under time pressure, prioritise: what happened, why it matters, what ADAFSA is doing, whether it is contained and what leadership may need to say or decide.
Likely question behind the question
What must leadership be able to do with this brief tomorrow morning?
Exercise timeline
2 min01Brief the task
5 min02Decode Card 1
5 min03Decode Card 2
4 min04Decode Card 3
4 min05Compare and reveal
Restated Ask worksheet
Request type
Which of the six types dominates?
Question behind the question
What decision or use sits behind the wording?
Scope
What is included and excluded?
Deliverable
What exact product will be produced?
Deadline
When is it required, including review time?
Assumptions
What have you assumed because the request is unclear?
Restated Ask paragraph
◎Open the reveal after writing your answers
The reveal: same request, different answers
Card 2 — Date Palm Programme
A
Five-slide progress update
B
Two-page programme review
C
Decision memorandum seeking approvals
D
Performance dashboard plus recommendations
Same sentence. Same room. Different projects.
What differed?
Scope
Definitions
Output format
Purpose
Evidence needed
Why did it differ?
Ambiguous verbs
Unstated boundaries
Missing output form
Different assumptions about leadership intent
What would it cost?
Incompatible inputs
Late analysis
Rework
Missed deadlines
Lower decision quality
Erosion of confidence
Questions to reflect on
Reflect and apply
Turn insight into a working habit
Use the six prompts to examine a real request and define what must change in your own process.
01
Look back
Think of a submission from the past year that came back or was harder than expected. Which type was it, and was there a hidden question discovered late—or never?
Request typeHidden questionLate discovery
02
Test the clock
The tasking letter governs. Where do internal assumptions about available time most often diverge from the true deadline?
How do we seek clarification without appearing weak?
How do we plan from the real deadline?
How do we protect review and sign-off time?
View all takeaways
The request sentence is the highest-leverage text in the entire fulfilment cycle: decode it wrongly and perfect execution still fails.
Six working types — data calls, status updates, emerging-issue briefs, cross-government inputs, decision memoranda, urgent queries — each with its own "good", its own typical turnaround, and its own classic misreading.
Every request has two layers: the explicit ask and the implicit expectation. "Provide an update" may really mean "should we keep funding this?" — and that changes what evidence you gather, from outputs to outcomes.
Deconstruct in four passes: underline the verbs, circle the scope words, box the output form, name the decision context. Ten minutes that can save weeks.
Three red flags of a misread: your outline answers a different question; the room debates what to include; departments return incompatible interpretations. All three are symptoms — the disease is upstream.
Write the Restated Ask — scope, deliverable, deadline, assumptions, one paragraph — before any work starts. It converts silent interpretation into a visible, correctable artefact.
Interpretation happens whether you manage it or not. The only choice is whether it is written, examined and shared — or silent, private and multiplied.