01
Log
Create one traceable record before the request lives in private inboxes.
Home · Journey map · Self-paced
Stage 03 / 06
Task & Collect
Departments answer exactly what you ask — so ask exactly.
01Tasking Brief: six elements, including the definition of done
02Ask for an early sample at 20–30% of the window
03Validate every input before synthesis begins
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 03
Intake Discipline
One front door, and a plan that starts from the deadline
- 01Log
One front door, one ID and one visible record.
- 02Triage
Match the machinery to complexity and deadline pressure.
- 03Clarify
Batch questions early and show your interpretation.
- 04Confirm
Turn interpretation into an institutional Restated Ask.
- 05Plan backwards
Protect synthesis, quality and sign-off time.
- 06Task precisely
Mobilise departments only after direction is clear.
What you will be able to do
01Log every request at one front door
02Select the right response track
03Clarify once and early
04Confirm the Restated Ask
05Back-plan with a protected buffer
Explore the ideas
Open a card for the key message, the logic behind it, what good looks like and a practical example.
↗Visual briefThe first-hour effectThe first hour sets the cost curve.
Key messageThe first hour sets the cost curve.
01DIRECTIONInterpret before departments mobilise.
02TIMINGReserve time for synthesis and review.
03REWORKA wrong start is discovered when time is gone.
Why it matters
The first hour determines the direction of every department that follows. A weak start remains hidden until inputs return and the timeline is already spent.
What good looks like
Create control before motion: log the request, interpret it, select the track and reserve time for synthesis and review.
Practical example
Forwarding a raw request in ten minutes feels fast; clarifying it for one hour can prevent days of contradictory rework.
Detailed visual guide
The first-hour control sequence
The first hour determines whether the team gains direction or merely creates motion.
02
Triage
Match ownership and process to complexity and deadline pressure.
03
Clarify
Batch every material question once and early, with a proposed interpretation.
04
Confirm
Make the Restated Ask an endorsed institutional position.
05
Plan backwards
Protect synthesis, quality review, sign-off and a roughly 20% buffer before tasking.
1Visual briefOne front doorIf it is not logged, it does not exist.
Key messageIf it is not logged, it does not exist.
01IDCreate a traceable request record.
02OWNERName one accountable person.
03DEADLINECapture the exact date and time.
Why it matters
Requests held in individual inboxes are invisible to the institution. A single front door creates continuity, accountability and a reliable audit trail.
What good looks like
Every live request has a unique ID, one accountable owner, the exact deadline and a traceable source from the day it arrives.
Practical example
If the owner is on leave, another team member can still see the request, its status and the next required action.
If it is not logged, it does not exist institutionally
The single front door: if it is not logged, it does not exist
Every Council or senior-office request enters once, is logged immediately and is owned through submission.
The scenario we all know
Monday afternoon
Request arrives by email from the General Secretariat.
Tuesday
A section head sees an accompanying field visit to date-palm farms.
Wednesday
The email is opened and forwarded to the director.
Thursday morning
The request finally surfaces in a conversation.
Why the inbox model fails
✉×
- Visible to one person only
- Vulnerable to absence
- Difficult to track
- Easy to overlook
- Hard to hand over
- Disconnected from portfolio priorities
- Missing a reliable audit trail
The single front door: one entry, one record, one owner
Request ID
One identifier for the full lifecycle.
- Emails
- Tasking notes
- Departmental inputs
- Drafts
- Review comments
- Final submission
- Follow-up actions
Named owner
One accountable person from intake to submission.
- Confirm interpretation
- Coordinate inputs
- Maintain the schedule
- Escalate risks
- Drive internal clearance
- Confirm submission
Deadlines
Record the external deadline and derive internal ones.
- Secretariat submission
- Leadership sign-off
- Quality review
- Draft complete
- Departmental inputs
The 30-second accountability test
“Where are we on the Council request about the food-security dashboard?”
Without a log
- Search inboxes
- Call several colleagues
- Reconstruct the history
- Give an uncertain answer
With a log
- Named owner
- Current status
- Next milestone
- Deadline
- Current risk
- Latest document version
The log begins the audit trail
1Request received2Logged with date and time3Owner assigned4Interpretation confirmed5Departments tasked6Draft reviewed7Leadership approved8Submission sent9Decision followed up
Who knew what—and when?The process survives people and circumstances
Annual leaveSick leaveField visitsStaff transfersRestructuringCompeting priorities
The operating rule: non-negotiable
- Capture or forward through the single intake channel
- Log within hours of receipt
- Assign one named owner
- Record the external deadline
- Trigger triage and backward planning
The platform may vary; the discipline cannot.
2Visual briefSelect the response trackUse machinery proportionate to risk and urgency.
Key messageUse machinery proportionate to risk and urgency.
01FASTKnown answer, narrow scope.
02STANDARDSeveral inputs, normal governance.
03COMPLEXCross-entity, high-risk or ambiguous.
Why it matters
Using the same process for every request either overloads simple work or under-governs risky work. Triage keeps effort proportionate.
What good looks like
Classify on two dimensions—complexity and deadline pressure—then select fast, standard or complex handling.
Practical example
A factual answer due tomorrow may be fast-track; a cross-entity policy proposal due in fifteen days may still require the complex track.
Proportionality determines the machinery
Triage: match the machinery to the request
Every request needs discipline, but not every request needs the same ownership, coordination and review.
Opposite failures from one root: no triage
Over-processing
- Too many meetings
- Excessive review layers
- Senior attention wasted
- Simple responses delayed
- Team fatigue
Under-processing
- Complexity discovered late
- Dependencies unmanaged
- Leadership informed too late
- Cross-government input missing
- Submission overwhelms the team
The two triage axes
Axis 1: complexity
Single-department
- One main evidence source
- Limited coordination
- Factual or narrowly defined
Example: Updated figures on abattoir inspections
Cross-department
- Several ADAFSA divisions
- Inputs must be integrated
- Definitions and positions aligned
Example: Progress against food-security indicators
Cross-government or sensitive
- External government entities
- Strategic or political implications
- Major policy, budget or regulatory decision
Example: Animal-disease emergency preparedness
Axis 2: deadline pressure
Comfortable
Enough time for normal tasking, synthesis, review and approval
Tight
Possible, but milestones and escalation must be activated early
Immediate
Hours or a few days; speed must shape the response design from the start
Triage matrix: cross the axes to choose the track
ComfortableTightImmediateSingle-departmentFast-trackFast-trackFast-track with escalationCross-departmentStandardStandard with accelerated checkpointsComplex: urgent mobilisationCross-government or sensitiveComplexComplexComplex: executive response
Quick track-selection test
- 1More than one ADAFSA department?
- 2Another government entity, sensitive issue or major decision?
- 3Deadline tight relative to the work required?
When uncertain, escalate the provisional track and simplify after verification.
What changes by track / What never changes
What changes by track
- Owner seniority
- Who is informed and how often
- Number of stakeholders
- Depth of coordination
- Review and challenge level
- Checkpoints and escalation
- Type and extent of deliverables
What never changes
- Log entry
- Confirmed ask
- Recorded deadline
- Backward plan
- Quality check
- Clear submission record
Fast-track: simple, focused, factual
Best for
- Single-department request
- Factual response
- Limited synthesis
- Narrow scope
- Short or manageable deadline
Ownership
Analyst or senior analyst; section head informed
Proportionate process
1Log2Confirm ask3Obtain targeted input4One quality check5Secure sign-off6Submit
Typical products
- Data table
- Short factual note
- Brief response
- Updated figures
Failure to avoid: Adding five layers of review to a simple two-page response.
Standard: integrated internal work
Best for
- Cross-department request
- Normal or moderately tight timeline
- Strategic update
- Integrated brief
- Several internal perspectives
Ownership
Senior analyst or section head; directors informed at tasking
Proportionate process
1Log and assign2Restated Ask3Tasking notes4Backward plan5Coordinate inputs6Resolve gaps7Quality gate8Leadership sign-off9Submit
Typical products
- Strategic status update
- Cross-functional briefing
- Executive presentation
- Short memorandum
Complex: cross-government, sensitive or decision-heavy
Best for
- Cross-government request
- Political or reputational sensitivity
- Significant Council decision
- New programme
- Regulatory change
- Budget commitment
- High uncertainty
Ownership
Section head or director; executive leadership informed on day one
Proportionate process
1Kick-off2Workstream leads3Stakeholder and dependency map4Early submission skeleton5Interim checkpoints6Early implications analysis7Senior challenge8Escalation plan
Typical products
- Decision memorandum
- Policy proposal
- Funding request
- Cross-government response
- High-stakes brief
3Visual briefClarify once, earlyClarify once, early, and with a point of view.
Key messageClarify once, early, and with a point of view.
01BATCHSend every material question together.
02EARLYDay one or two — never at the end.
03INTERPRETOffer your reading, then ask to confirm.
Why it matters
Early clarification signals careful reading. Late or fragmented questions signal that the request was not understood until the deadline was already at risk.
What good looks like
Send one organised batch in the first day or two. State your interpretation and ask the requester to confirm or choose between specific alternatives.
Practical example
“We understand the request to cover current-period KPI performance and corrective actions. Please confirm whether revised targets are also required.”
Professional clarification begins with analysis
Asking well: the clarification protocol
A well-framed clarification sent early signals diligence. A wrong submission signals weakness.
✉
The ambiguous request arrives
“Provide an update on food-security performance and the way forward.”
The myth
“Going back with a clarification question makes the Authority look weak.”
The reality
- The request was read carefully
- Ambiguity was identified early
- Consequences of different interpretations were understood
- Rework was prevented early
What actually signals weakness?
- Answering the wrong question
- Discovering ambiguity late
- Sending repeated follow-up questions
- Requiring a second submission cycle
When is clarification legitimate?
Is the ambiguity material?
Would two reasonable interpretations produce materially different scope, evidence or approval?
Scope
- Fresh produce imports only or all categories?
- Abu Dhabi Emirate only or UAE-wide?
- Current programme or full historical period?
Decision sought
- Note progress?
- Endorse direction?
- Approve funding?
- Select an option?
Format and depth
- Two-page brief?
- Presentation deck?
- Full memorandum with exhibits?
- Technical annex required?
Deadline meaning
- Entity submission date?
- Secretariat screening date?
- Leadership review date?
- Council session date?
The clarification formula
State our interpretation
“We understand the request to require…”
Confirm or correct
“Kindly confirm whether this interpretation is correct…”
Present the specific fork
“…and advise whether the submission should include X or remain limited to Y.”
What is not legitimate clarification
“What do you mean by paragraph two?”
“Please explain what is required.”
“What information would you like?”
“Can you provide more details?”
“Please clarify the request.”
What it signals
- No interpretation attempted
- Burden transferred to the requester
- Too broad to answer efficiently
- Weak analytical preparation
The three rules
Batched
Ask all material questions together in one analysed and structured note.
Avoid the drip: repeated questions say “we are still confused”.Once
Pressure-test the batch internally with the owner, section head and director where needed.
Use one professional opportunity; do not substitute the requester for internal analysis.Early
Send within the first day or two—never in the final days.
Day 1–2 shows diligence; days 3–6 increase risk; days 7–10 expose delay.Worked example: a batched clarification note
Our understandingWe understand the request to require a current-period assessment of performance against approved food-security indicators, including material gaps, causes and corrective actions.
Scope
Current period indicators only or complete Emirate indicator set?
Decision sought
Is the paper intended to inform, endorse targets or seek approval?
Deliverable
Short executive brief or full memorandum with exhibits?
Deadline
Receipt by Secretariat or completion of internal screening?
When ambiguity appears late
- Do not create avoidable delay with an open-ended question
- Form the most reasonable interpretation
- Record the assumption explicitly
- Assess risk and escalate to leadership
- State the interpretation transparently
- Flag any material limitation or alternative reading
Channel and audit trail
1Request owner prepares clarification2Internal review and approval3Leadership or authorised channel4General Secretariat5Response received6Request file updated
4Visual briefConfirm the Restated AskMake the interpretation institutional.
Key messageMake the interpretation institutional.
01RESTATEWrite the ask in one paragraph.
02CONFIRMRequester or accountable ADAFSA leader.
03RECORDKeep the agreement in the audit trail.
Why it matters
Interpretation creates risk. Confirming the Restated Ask turns one analyst’s reading into an institutional position that can be defended later.
What good looks like
State what is wanted, by when, in what form and on which assumptions; obtain confirmation and retain it in the request record.
Practical example
For a fast-track item, internal confirmation by the accountable ADAFSA leader may be proportionate when external clarification is unnecessary.
From personal judgement to institutional position
The Restated Ask: making the interpretation institutional
An interpretation becomes safe to act on only when it moves from one person’s judgement into an endorsed institutional position.
A request arrives
“Provide an update on the farmer support programme.”
The hidden work
- What exactly is required?
- What is the expected output?
- What decision will this support?
- Who owns the interpretation?
The Restated Ask anatomy
Scope
What is included and excluded?
Deliverable
What product is required?
Deadline
When must it be ready?
Assumptions
What interpretation choices were made?
Decision context
What decision will this enable?
Why confirmation matters
Protects the analyst
- Without confirmation: “An analyst interpreted it incorrectly.”
- With confirmation: “The Authority made an endorsed interpretation based on available information.”
Protects leadership
- What assumption was made?
- Who reviewed it?
- Why was the approach selected?
- What risks were considered?
Improves the interpretation
- Scope errors
- Hidden assumptions
- Missing stakeholders
- Wrong decision framing
- Wrong output expectations
Confirmation pathways
External confirmation: gold standard
Use when- Ambiguity is material
- Interpretations change the work
- Time allows clarification
- Decision stakes are high
1Restated Ask prepared2Batched clarification3Requesting office confirms or corrects4Shared interpretation in writing
Your interpretation becomes their interpretation—in writing.Internal confirmation: proportionate alternative
Use when- Fast-track request
- Tight deadline
- Clarification is unnecessary
- Interpretation is sufficiently clear
1Restated Ask prepared2Accountable leader reviews3Agreement recorded4Institutional position
The Authority owns the interpretation.The risk ownership principle
Personal risk
“I assumed this was what they wanted.”
Institutional ownership
The Authority reviewed and endorsed this interpretation.
The five-minute habit versus weeks of rework
With the habit
- Write Restated Ask
- Confirm ownership
- Record agreement
- Proceed confidently
Without the habit
- Departments mobilised incorrectly
- Evidence collected for the wrong purpose
- Draft rewritten
- Deadlines compressed
- Additional reviews required
Common mistakes
“I wrote the Restated Ask, so it is done.”
Writing is only the first step; confirmation makes it institutional.
“We are experienced; we do not need confirmation.”
Experience reduces risk but does not remove interpretation risk.
“We will clarify if it becomes a problem.”
Late clarification is often discovered after resources are already committed.
The operating sequence
Log it
The request enters the institutional record.
Restate it
Convert the request into a clear interpretation.
Confirm it
Obtain external confirmation or internal endorsement.
Task it
Only now mobilise the departments.
5Visual briefPlan backwardTen working days becomes four.
Key messageTen working days becomes four.
01DAY 4Department inputs due.
02DAY 8Quality gate complete.
03DAY 9Leadership sign-off; hold the buffer.
Why it matters
The submission date is not the working deadline. Synthesis, quality review and leadership sign-off consume more than half of a typical ten-day window.
What good looks like
Plan from the deadline backward, protect roughly 20% as contingency and give departments the true input date—not the final submission date.
Practical example
On a ten-working-day request, inputs are commonly due around day four, quality review on day eight and leadership sign-off on day nine.
The input deadline is the real working deadline
Planning backwards: the true deadline is earlier than instinct suggests
The submission deadline is not the working deadline. Inputs must arrive early enough to protect synthesis, quality review and leadership decision-making.
The backward plan: what must happen before submission?
Department inputs due
The real deadline; ask early because one input will be late.
Input deadline at latest
Friday is a half day and leaves only the minimum synthesis time.
Synthesis and draft
Analyse inputs, identify gaps, build recommendation, draft narrative and exhibits.
Quality gate
Structured challenge of the five questions, evidence, logic, implications and consistency.
Leadership sign-off
Provide a full day for real review and approval.
Submission to Secretariat
Better practice is Thursday; keep Friday morning for rescue.
Two rules that protect the plan
The buffer rule
Keep about 20% of the total timeline in reserve: two days in a ten-day request.
- Returned inputs
- Data discrepancies
- Additional options
- Scope clarifications
- Unexpected dependencies
Never plan final-hour approval
- Final-afternoon approval
- Meetings overrun
- Leaders travel
- New questions emerge
- Review becomes rushed approval
Where did the days go?
Backward-plan template
Request loggedIntake ownerDay 0
Restated Ask confirmedRequest ownerDay 1
Department tasking issuedStrategy ownerDay 1
Department inputs dueContributorsDay 4
Synthesis completeStrategy teamDay 7
Quality gateReviewerDay 8
Leadership sign-offLeadership officeDay 9
Secretariat submissionRequest ownerDay 10 by noon
Why instinct fails
Instinct says
“We have ten days.”
Reality says
“We have ten days minus everything required to produce a decision-ready product.”
The module connection
Decode the request
Control intake and timeline
Task departments using the real input deadline
Quick check
6Visual briefMotion vs progressHalf a day of discipline prevents days of rework.
Key messageHalf a day of discipline prevents days of rework.
01RESISTDo not forward the raw request.
02SEQUENCELog → triage → clarify → plan.
03TASKMobilise departments with precision.
Why it matters
Urgency creates an instinct to forward the request immediately. That motion feels productive but multiplies inconsistent interpretations and later rework.
What good looks like
Complete the intake sequence before tasking: log, triage, clarify, confirm and back-plan. Departments then receive one precise direction.
Practical example
Four departments responding to one interpreted brief produce compatible inputs; four departments interpreting the raw request produce four different answers.
Direction first, distribution second
The emotional trap: motion is not progress
The first impulse is to act. Professional discipline creates direction before creating activity.
The emotional impulse
What was actually sent?
“Please provide your inputs.”
What was missing?
- No Restated Ask
- No scope boundaries
- No expected format
- No decision context
- No evidence requirements
- No true internal deadline
The multiplication effect: one request, four interpretations
Operations
Interprets it as: Data request
Produces- Numbers
- Tables
- Statistics
Policy
Interprets it as: Strategic update
Produces- Narrative
- Progress summary
- Challenges
Technical team
Interprets it as: Technical assessment
Produces- Risk analysis
- Technical detail
Finance
Interprets it as: Resource question
Produces- Cost information
- Historical spending
The cost of the shortcut
Started quickly: raw request forwarded
Inputs return with different assumptions, formats, scopes and missing evidence
Re-explain, re-task, rewrite, lose synthesis time and consume contingency
Fast start becomes slow finish
The professional alternative: first hours belong to intake
Log
Create visibility and ownership
Triage
Understand complexity, urgency and stakeholders
Clarify
Resolve material ambiguity once and early
Confirm
Create a shared Restated Ask
Plan backwards
Protect the real deadline and buffer
Task
Mobilise departments with precision
Reframe the feeling
Anxious instinct
“If I have not forwarded something, I have not started.”
Professional discipline
“If I have not clarified the work, I have not started the right work.”
The driving analogy
Leave immediately
- Speed high from the start
- Wrong direction
- Multiple detours
- Late arrival
Plan for ten minutes
- Route defined
- Correct destination
- Fewer corrections
- Early arrival
Test the difference
?
Think of the last request you forwarded immediately. What ambiguity did you distribute?
Exercise — The Ten-Day Countdown
Key messageBuild the ten-day plan backwards.
01START AT 10Fix submission and sign-off first.
02PROTECT 20%Keep two days for the unexpected.
03LAND ON 4Set the true department-input date.
Why it matters
Backward planning makes the hidden work after departmental inputs visible and converts a vague deadline into an operational commitment.
What good looks like
Every milestone has a date and owner, the buffer is explicit, and the plan respects quality review, sign-off and Friday working hours.
Practical example
A strong ten-day plan places inputs near day four and aims to submit on Thursday, holding Friday morning as contingency.
Self-guided application exercise
The Ten-Day Countdown
A ten-day submission window does not mean ten days of departmental work. Backward planning reveals the real input deadline.
Illustrative scenario
Monday morning: the Secretariat asks for a memorandum on progress in strengthening biosecurity at poultry farms.
- Current control measures
- Gaps identified
- Recommended next steps
- Indicative costs
Your task: build a dated milestone plan backwards from submission
Receive
- Request ID
- Owner
- Deadline
- Required output
Decode
- Restated Ask
- Scope
- Decision context
- Evidence needs
Plan backwards
- Start from submission day
- Assign dates
- Assign owners
- Protect the buffer
Defend your plan
- Where is the buffer?
- Why this input deadline?
- Who owns each milestone?
- Is the sequence realistic?
Ten working days: work backwards
Intake logged and clarification batch sent if needed
Request owner
Restated Ask confirmed
Accountable leader
Department inputs due
Animal Health · Policy/Regulation · Finance
Buffer for late or missing inputs and reconciliation
Request owner
Synthesis, draft and exhibits
Strategy team
Quality gate
Independent reviewer
Leadership sign-off
DG or executive office
Submission to Secretariat
Request owner
Where does the time actually go?
Stress-test your plan
Common planning mistakes
- Giving departments days 7–8
- Placing work on weekends
- Clarifying after tasking
- No named owner
- No reserve or buffer
Your personal milestone plan
Questions to reflect on
Reflect and apply
Test your intake discipline
Use a live request and identify where control is currently lost.
Find the front door
What would happen to the last request in a personal inbox if its owner were absent?
VisibilityCoverAudit trail
Notice the urge
Where do you feel pressure to “just start”, and what rework has that motion caused?
AdrenalineRaw forwardingRework
Name the barrier
What stops early clarification: protocol, hierarchy, fear or habit—and which constraints are real?
ChannelConfidenceTiming
Test proportionality
Where are simple requests over-processed and complex requests under-processed?
FastStandardComplex
Protect the buffer
When a late input consumes the buffer, what must the owner do within 24 hours and who needs visibility?
Escalate riskReset planLeadership visibility
Set authority
Who can set the internal input deadline, and how is pushback against an “early” date resolved?
Accountable ownerBackward planDecision rights
Decision ruleThe first hours belong to intake — not tasking.
01ControlOne ID, one owner, one deadline.
02ClarifyOne early batch, with a point of view.
03PlanOn ten days, inputs are due around day four.
View all takeaways
- Every Council request goes through one front door: logged with a request ID, a named owner and a recorded deadline within hours of arrival. No request lives only in an inbox.
- Triage on two axes — complexity and deadline pressure — and place the request on one of three tracks: fast-track, standard or complex. The track sets who owns it, who is informed, and how much process is proportionate.
- Clarification questions are a sign of competence when they are batched, sent once, and sent early — never a drip, and never in the final days.
- Phrase every question as an interpretation to confirm plus a specific choice to make — do the work first, then ask.
- Confirm the Restated Ask with the requester or with ADAFSA leadership so the interpretation is owned institutionally and sits on the audit trail.
- Plan backwards from the deadline: subtract sign-off, quality gate and synthesis, and what remains — usually less than half the timeline — is the true department-input deadline. And respect the shape of the week: Friday is a half working day, so a Friday deadline means Friday noon — aim to submit on the Thursday.
- Keep roughly 20% of the timeline in reserve, never schedule leadership review for the last hours, and remember: rework is always slower than a disciplined first day.
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 upstreamDo not ask departments for “input”; design what a usable answer looks like.
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
Provide a brief on farmer-support programme performance covering uptake, expenditure and impact on local production. Required soon.
“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
Old annual report
60 pages · two years out of date
- Programme background
- Activity summaries
- Historical achievements
- Current uptake
- Current spend
- Current production impact
Conference presentation
Promotional rather than evidential
- Promotional messages
- Selected success stories
- High-level charts
- Programme narrative
- Definitions
- Sources
- Complete data
- Decision-relevant analysis
Unusable spreadsheet
“FINAL v3 updated NEW.xlsx”
- Raw rows and mixed fields
- Column headings
- Units
- Source notes
- Reporting period
- Definitions
- Final-versus-draft indication
Timeline of failure
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 commissioning principle
Weak commissioning
1Vague tasking2Undefined output3Open-ended deadline4Inconsistent inputStrong commissioning
1Precise tasking2Defined evidence3Standard format4Named deadline5Usable inputWhat 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
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
1Visual briefWhy good people missCapable colleagues cannot infer requirements you never stated.
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”
Vague tasking
“Please send what you have on date-palm pests.”
- Reports
- Presentations
- Historical statistics
- Unfiltered background
- Irrelevant attachments
The request names a subject, not a question.
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.
The wrong question
“Council asks: what was the impact? Strategy asks: what activities were delivered?”
- Workshops held
- Farms visited
- Subsidies disbursed
- Inspections completed
Departmental tasking did not preserve the Council’s governing question.
Request production increase, compliance improvement, income change, response-time reduction and risk reduction.
No context
“Please provide inspection statistics.”
- Routine figures
- Limited checking
- Material caveats omitted
Without purpose, contributors cannot apply greater judgement or surface material limitations.
Explain who requested the work, what decision it supports, why the input matters and how it will appear.
No format specified
“Any file and any structure will do.”
- Narrative paragraph
- PDF report
- Screenshot
- Spreadsheet
- Percentages
- Absolute figures
- Different reporting years
Strategy inherits retyping, reformatting, recalculation, rechecking and new-error risk.
Specify file type, table structure, required columns, units, time period, breakdown, source notes and maximum narrative length.
No real deadline
“At your earliest convenience—or simply quote the external deadline.”
- No operational priority
- Late or rushed response
- Strategy loses synthesis, quality review, approval and contingency time
A mood is not a milestone, and the submission date is not the input date.
Give an earlier internal date and time derived from the backward plan, with a reason and escalation expectations.
Wrong source
“Ask the director for detailed figures or ask the data team for institutional judgement.”
- Opinion instead of data
- Raw data without meaning
- Delayed response
- Missing definitions
Information ownership and authority to interpret or commit are different.
Verified figures → data owner; operational explanation → delivery team; technical judgement → expert; policy position → policy owner; commitment → accountable leader.
Six-mode diagnostic
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
2Visual briefThe Tasking BriefSix elements turn a request email into a 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
Context
Why is this input needed?
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.
Exact questions
What must the department answer?
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?
Required format
What must the response look like?
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.
True internal deadline
When must the input arrive?
Completed response by Thursday 14 May at 14:00 to allow consolidation, quality review and leadership approval before the external deadline.
Named contact
Whom should the contributor call before guessing?
For questions, contact the named Strategy owner before beginning. Do not assume where scope, definition or format is unclear.
Definition of done
What makes the response complete?
All questions answered in the specified format; every figure sourced and dated; assumptions and data gaps explicitly flagged.
Bare email versus Tasking 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
Quality check before issuing
Recommended one-page structure
- Context and purpose
- Questions to answer
- Required evidence and definitions
- Required format
- Deadline and delivery method
- Named contact
- Definition of done
Tasking Brief
Relevant answersComparable dataClear accountabilityFewer clarification loopsFaster integrationSubmission-ready evidence
3Visual briefChoose the right sourceMatch each question to the person who owns the answer.
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
What is happening?
What is?
- 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
- Surveillance teams
- Laboratory information owners
- Inspection operations
- Registration and licensing teams
- Data and performance units
- 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.
What does it mean?
What could happen?
- Technical interpretation
- Transmission dynamics
- Severity and likelihood
- Possible scenarios
- Control options
- Benchmark responses
- Scientific caveats
- Emerging risks and uncertainties
- Veterinary epidemiologists
- Laboratory specialists
- Biosecurity experts
- Regulatory specialists
- Field veterinarians
- Research and technical advisers
- 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.
What should ADAFSA do?
What is our position?
- Preferred recommendation
- Operational commitment
- Resource pledge
- Risk ownership
- Implementation responsibility
- Departmental constraints
- Formal endorsement
- Section heads
- Department directors
- Executive directors
- Accountable programme owners
- 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.
Source-matching matrix
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
What happened?
Surveillance and laboratory data ownersConfirmed cases, affected farms, geographic spread and reporting dates
Verified factsWhat does it mean?
Veterinary epidemiologists and biosecurity expertsLikelihood, containment, risk, scenarios and options
Interpretation and risk assessmentWhat should ADAFSA do?
Department leadershipRecommended control, operational response, resources, dependencies and approval sought
Endorsed position and ownershipFive-minute source-mapping tool
Data question
Verified number · dataset · factual status
Data ownerExpert question
Interpretation · technical judgement · scenario analysis
Subject-matter expertPosition question
Recommendation · commitment · resources · risk acceptance
Department leadershipWrong-source failure modes
Opinion instead of data
Question went to leadership instead of the data owner
Opinion-based numbers, delay and missing definitionsData without meaning
Data team was asked for judgement it cannot authorise
Raw data without context and incompatible adviceExpert opinion presented as policy
Technical advice was not converted into an endorsed position
Overstated authority, policy misalignment and institutional riskUse 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
- Restate the Council ask
- Walk through the evidence map
- Confirm boundaries
- Confirm outputs
- Confirm milestones
- 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
4Visual briefManage the middleThe middle of the input window must be actively managed.
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
Failure route
The pattern to break
Problems discovered
- Wrong scope
- Wrong breakdown
- Incorrect format
- Missing evidence
- Unresolved definitions
- Late delivery
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
Short window: up to 5 working days
- Early sample
- One midpoint check
Medium window: 1–2 weeks
- Early sample
- One or two short checkpoints
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
Light touch
Work appears on schedule; no major dependency; sample is acceptable.
- Two-line message or brief conversation
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
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
- Name the deliverable
- State the deadline
- Identify the dependency
- Explain the consequence
- Ask for help
Avoid
BlameMotive speculationEmotional languagePersonal criticismUnnecessary copying of senior recipients
Escalation decision tree
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
5Visual briefValidate before useNo input enters the answer until it passes validation.
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
Does the input meet the brief?
No → return with missing items specified
Are figures sourced, dated and consistent?
No → clarify or return
Are units, languages and departmental figures reconciled?
No → resolve with evidence owners
All checks pass
Accept into integration
15-minute validation gate: six checks
Complete against the Tasking Brief
- Every numbered question answered?
- Required format used?
- Definition of done met?
- Gaps and assumptions flagged?
Internally consistent
- Rows add to total?
- Percentages reconcile?
- Narrative matches table?
- Trend description matches data?
- Baseline aligns with previous reporting?
Source and as-of date attached
- Source system or record
- Reporting period
- Known limitation
- As-of date
- Definition
Units and definitions consistent
- Tonnes versus kilograms
- Hectares versus donums
- Calendar versus fiscal year
- Animals versus holdings
- Monthly versus cumulative
- Percentage points versus percentage change
Arabic and English reconciled
- Reconcile all material numbers
- Match dates and labels
- Check decimal separators
- Confirm technical translations
- Verify final versions
Cross-department contradictions resolved
- Different registers?
- Different definitions?
- Different reporting dates?
- Farms versus licensed establishments?
- Active versus registered entities?
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
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
6Visual briefBuild relationship capitalReliable relationships reduce transaction cost on every future request.
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
Department view
Transactional cycle
Consequences
- Minimum viable response
- Slower turnaround
- Less proactive problem-solving
- Caveats surfaced late
- Lower willingness to prioritise Strategy
- More escalation required
Relationship-capital flywheel
Ask professionally
- Clear Tasking Brief
- Realistic internal deadline
- Accessible contact
- Respect for contributor expertise
Support during delivery
- Early sample protects effort
- Proportionate checkpoints
- Collaborative blocker resolution
- Escalate the deliverable
Close the loop
- Confirm submission
- Share what happened
- Explain how input was used
Recognise the contributor
- Thank the person by name
- Inform their manager
- Describe the value added
Share outcome and credit
- Connect contribution to leadership action
- Make department role visible
- Share credit appropriately
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
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
Within minutes
Confirm receipt of final input and thank contributor specifically
When submitted
Tell contributors the submission went out and where their input appeared
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
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.
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
- No decision context
- No exact questions
- No format
- False deadline
- No named contact
- No definition of done
- No source selection
- “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
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
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
Data owner
What is?
Uptake, spend, production figures, pest detectionsSubject-matter expert
What does it mean?
Attribution, trends, caveats, impact interpretationDepartment leadership
What is our position?
Recommendation, commitment, resources, risk ownershipIs a kickoff huddle warranted?
Yes, because
- Two departments involved
- Data and technical interpretation must align
- Questions overlap
- Timeline tight
- Different definitions possible
Agenda
- Confirm Council ask
- Assign questions
- Agree definitions
- Confirm format and deadlines
- Surface dependencies
Exercise timeline
Self-comparison after completion
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
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
Questions to reflect on
- 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?
- 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?
- 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?
- 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?
- 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?
- 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.
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.