The proper way to ask someone to create a PowerPoint presentation is to open with the concrete deliverable (for example, "a 12-slide deck for Thursday's budget review"), then supply the audience, the one-sentence goal, slide count, deadline, file format, and where the source material lives. Vague requests like "can you throw together some slides" fail because they leave the designer guessing on the five decisions that drive 80% of the work: purpose, audience, content scope, visual system, and handoff format.

This guide goes past etiquette. It explains the cognitive mechanisms behind why some slide requests produce usable decks and others produce rework loops, then gives thresholds and steps you can apply the next time you delegate a deck.

The delegation handoff mechanism

Slide creation is a translation task, not a typing task. The person building the deck converts your intent into structure, then structure into visuals, then visuals into a narrative that a room full of people will absorb in real time. Each conversion loses fidelity unless the original request pins down intent precisely.

Cognitive load theory explains the failure mode. Working memory holds roughly 4 to 7 chunks of information at once. When a request arrives with ambiguous scope, the designer spends that limited capacity on guessing your intent instead of designing. Every missing detail becomes a decision they must make blind, and every blind decision is a coin flip you will later flip back during review. Clear requests shift effort from telepathy to execution.

There is a second mechanism at work: the curse of knowledge. As the requester, you hold context the designer lacks — the backstory, the politics, the reason slide 4 matters. Research on expert communication shows people systematically overestimate how much of that context transfers through a short message. The fix is not longer messages; it is structured messages that name the missing pieces explicitly.

Think of the request as a specification, not a favor. A good spec tells the builder what "done" looks like before work begins.

What a complete request contains

A deck request that survives first contact carries seven data points. Missing any one of them adds a predictable round of revision.

Goal in one sentence: what the audience should think, feel, or do after the last slide. Audience profile: who sits in the room, their seniority, and what they already know. Scope: slide count range, sections required, and what to leave out. Deadline and timezone: the exact date and hour the file must exist, not the meeting time. Format and platform: PowerPoint file, Google Slides, 16:9 ratio, template or brand kit. Source material location: folder path, links, or attached documents with the key numbers flagged. Handoff and ownership: who presents, whether speaker notes are needed, and who approves the final version.

Requests that include all seven tend to produce one revision cycle. Requests missing three or more tend to produce three or more cycles, with each cycle costing the requester review time as well.

A working example compresses this into a short message: "Please build a 10-12 slide deck for Thursday 9 a.m. ET, for our VP and two finance leads, goal is approval of the Q3 marketing budget. Sources are in the shared folder under Q3-budget; the summary tab has the final numbers. Use the company template, 16:9, add speaker notes. I present it, and you and I review Wednesday at 2."

That message takes under 90 seconds to write and removes nearly every guess.

Quantified context: why specificity pays

Rework is the hidden cost of vague delegation. Industry surveys of knowledge workers consistently place the share of documents revised at least once above 60 percent, though exact figures vary by study and should be treated as directional rather than precise.

Time estimates matter more than revision counts. A typical 10-15 slide business deck takes a practiced designer 2 to 4 hours including content organization; a request that requires the designer to hunt down numbers or infer structure can double that. If your request omits the source location, expect roughly 30 to 60 minutes of the designer's time spent searching before any slide is built.

Deadlines compress quality faster than most people expect. Design work scheduled with less than 24 hours of buffer tends to skip the consistency pass, where fonts, alignment, and number formatting get unified. That pass is exactly what audiences notice first.

Plain version: vague asks are cheap to send and expensive to fix.

Comparison of request formats

Different channels and formats change how much structure survives the handoff.

Request format Typical completeness Rework rate Best used when
Verbal hallway ask Low: 2-3 of 7 elements High Almost never for real decks
One-line chat message Low: 2-3 of 7 elements High Only for tiny edits to existing decks
Email with bullet list Medium: 4-5 of 7 elements Medium Routine internal decks
Structured template or brief High: 6-7 of 7 elements Low Anything client-facing or high-stakes
Shared doc with linked sources High: 6-7 of 7 elements Low Decks built from data or research

The pattern is consistent: the more the request resembles a document the designer can revisit, the fewer questions come back. Chat is fast for you and slow for the whole project.

Timeline of a well-run request

A structured request follows a predictable arc. Timelines below are practical heuristics for a mid-sized business deck, not measured constants.

Stage What happens Typical elapsed time
Request sent Seven-element brief delivered Day 0
Acknowledgment Designer confirms scope and flags gaps Within 1 business day
Draft 1 Structure and content built 2-4 business days
Review Requester marks changes in one pass 1 business day
Revision Fixes applied, consistency pass 1-2 business days
Final handoff File delivered in agreed format 1 day before the deadline

The single biggest predictor of a smooth arc is the review step: feedback delivered in one consolidated pass cuts revision rounds roughly in half compared with feedback trickled across messages.

Edge cases and professional caveats

Cross-cultural and cross-functional requests need extra explicitness. In high-context communication cultures, an indirect request may be expected, but slide specifications still need to be concrete; politeness and vagueness are not the same thing. When working across time zones, state deadlines in both parties' local times or attach a UTC reference.

The counterintuitive caveat: more detail is not always better. Briefs over roughly 500 words start to bury the decisions that matter, and designers report skipping long preambles to find the deadline. Aim for density, not length — a one-page structured brief beats a three-page narrative.

Also expect pushback on ownership. If you ask someone to "create" a deck but actually need them to make judgment calls on messaging, say so explicitly. A designer can build slides; only you can decide what the room should be told.

Practical actions: how to ask next time

Use this sequence for any deck request that matters.

Write the goal sentence first: "After this deck, the audience should approve X." If you cannot write it, the deck is not ready to delegate. Name the audience by role and seniority, not by name alone. Set a slide range, not a slide number, and list required sections. Give a deadline with date, hour, and timezone, and add one day of buffer before the meeting. Link the source material directly and flag which tab or page holds the final numbers. Specify platform, aspect ratio, template, and whether speaker notes are needed. Request a single consolidated review pass and state who approves the final file.

Red flags to remove before sending:

"Just make it look nice" with no reference deck or brand guide attached. A deadline equal to the meeting start time. Numbers pasted into chat with no source attached. Multiple approvers named without a lead approver. Scope described as "a few slides" when the content implies 30.

Each red flag predicts a specific failure. Missing a reference deck predicts style rework. A deadline at meeting time predicts a rushed consistency pass. Multiple approvers without a lead predicts contradictory feedback.

Limitations and what this guide cannot settle

This framework rests on general principles of communication and cognitive load, not on controlled studies of slide delegation specifically. Revision-count and time estimates are practical ranges drawn from workplace experience, and actual figures depend on team, tooling, and deck complexity. Cultural norms around directness vary widely, so adjust the tone of requests to your organization while keeping the seven structural elements intact. Nothing here addresses procurement, contracts, or compensation for design work, which follow your organization's own policies.

This article is general educational information about workplace communication, not professional advice of any kind. It does not guarantee outcomes, timelines, or approval of any presentation. For employment, contractual, or accessibility-compliance questions related to presentation work, consult a qualified professional in your jurisdiction.