A concept deck is a decision tool. Its purpose is to remind the client what was agreed, show how each direction answers that brief, and make the next decision specific. A gallery of polished mockups may look expensive while hiding weak reasoning.
By the end of this lesson, you will have a concise concept deck that a client can review on a phone or in a meeting. It will separate approved facts, proposed design choices, and clearly labelled simulations.
Build a Decision Sequence
Use this order for a small identity project:
- Cover: project, stage, date, and version.
- Decision needed: one sentence stating what feedback is required today.
- Agreed brief: audience, positioning, attributes, uses, and constraints.
- Evaluation criteria: the rules every direction will be judged against.
- Direction A: concept, rationale, flat artwork, and relevant application.
- Direction B: same evidence and level of finish.
- Direction C: only if the scope includes it and it is genuinely distinct.
- Comparison: tradeoffs against the agreed criteria.
- Recommendation: your professional view and why.
- Next step: choice required, revision boundary, owner, and date.
Do not begin with ten mood slides. The client needs the shared problem before the proposed answer. Give each direction equal presentation weight; a dramatic mockup for one and a plain logo for another manipulates the comparison.
Explain Fit Without Inventing Meaning
Use the brief as evidence. Replace “blue represents trust” with a testable statement such as: “The dark blue produces the reserved, high-contrast interface requested in the brief and remains legible in the sample mobile header.”
A useful rationale has four parts:
IDEA: what the visual system is doing.
BRIEF LINK: which agreed need it addresses.
EVIDENCE: where the client can see that behavior.
TRADEOFF: what this direction emphasizes or gives up.
AI can help shorten your notes, but it must not invent client preferences:
Rewrite the notes below into a 70-word design rationale. Preserve only facts
explicitly present in the brief and notes. State one visible tradeoff. Do not
add symbolism, audience research, performance claims, or client quotes.
BRIEF: [paste approved brief excerpt]
NOTES: [paste your observations]
Read the result against the source brief. Remove any statement you cannot point to in the design or approved notes.
Show Applications Honestly
Mockups help a client imagine use, but they are simulations. Label them “sample application” when they do not show a produced item. Use contexts the client actually needs: a WhatsApp avatar, invoice, storefront sign, packaging panel, or mobile screen. A luxury billboard mockup is irrelevant if the deliverables are receipts and social cards.
Keep artwork large enough to judge. Include at least one flat, unmocked view, a small-size view, and a one-color view for identity work. If AI generated a background scene, say so internally and ensure no protected client information, unapproved people, or misleading product detail appears in it.
Export a lightweight PDF for WhatsApp or email and retain a high-quality review copy. Test every page on a phone. Presenter notes do not help a client reviewing asynchronously, so the slide itself must carry the essential reasoning.
Worked Example
Sample project: a hypothetical Faisalabad bookkeeping practice is choosing between two identity directions. Draft one opens with a cinematic office mockup, uses tiny rationale text, and asks, “Which one do you like?” The client can react only by taste.
The revision opens with this decision:
TODAY'S DECISION
Choose the identity direction to refine: A — Structured Ledger or
B — Open Conversation. Judge both against mobile recognition, one-color
printing, bilingual use, and the "clear, steady, approachable" attributes
approved on 14 July. This is direction approval, not final artwork approval.
Each direction then shows the black symbol, bilingual lockup, invoice header, and 32-pixel avatar. Direction A is more compact but needs extra care around Urdu spacing. Direction B reads more warmly but is less distinctive at avatar size. The recommendation names that tradeoff instead of pretending one option is perfect.
The final slide provides three response fields: Choose A or B, What specifically supports the brief?, and One change required before refinement. A PDF filename records the stage: Hisab-Concept-Review-v02-2026-07-19.pdf.
Failure Cases to Diagnose
- The deck starts with decoration: restore brief, criteria, and decision before visual persuasion.
- Directions have unequal mockups: show the same relevant applications at the same scale.
- Rationales use universal color psychology: replace it with visible behavior tied to the approved brief.
- Every sketch is shown: curate only defensible directions and keep the exploration record separately.
- The client is asked “thoughts?”: request a bounded decision against named criteria.
- Text is unreadable on mobile: shorten, enlarge, and split slides after testing the exported PDF.
- Mockups look like produced results: label simulations and show flat artwork beside them.
🇵🇰 Pakistan Angle
Many client reviews happen through WhatsApp voice notes and phone screenshots. Send one numbered PDF, not a stream of unlabeled JPEGs. Ask the client to reference page and direction numbers in feedback. A lightweight copy prevents re-compression from making fine artwork or Urdu text impossible to judge, while the full-resolution file can follow through the agreed channel.
Use applications that match Pakistani production reality: a flex sign, cash memo, delivery sticker, Daraz tile, WhatsApp catalog cover, or school handout when relevant. If a deck contains customer faces, shop phone numbers, CNIC-derived documents, or internal sales data, replace them with clearly labelled sample material unless written permission covers that exact review audience.
Hands-On Exercise
- Choose a real authorized project or a labelled hypothetical identity.
- Write the exact decision required and five evaluation criteria from the brief.
- Build the ten-slide sequence for two genuinely distinct directions.
- Give both directions matching flat, small, one-color, and application views.
- Draft each rationale with idea, brief link, evidence, and tradeoff.
- Export a lightweight PDF and test it on a phone without narration.
- Ask a reviewer to make the requested decision; revise any slide that forces them to guess.
Done means: a reviewer can state the decision, compare the directions against agreed criteria, identify simulations, and give page-specific feedback without a live explanation.
Completion Rubric
- The deck names one bounded decision and the approved evaluation criteria.
- Every concept has equal evidence and a brief-linked rationale.
- Flat, small-size, one-color, and relevant application views are present.
- Simulations and sample material are clearly labelled.
- Recommendation and tradeoffs are explicit rather than disguised as taste.
- The exported PDF is legible and correctly ordered on a phone.
Sources
- Canva — Presentations
- Canva Help Center
- Adobe Acrobat — Create accessible PDFs
- W3C — Images tutorial
Key takeaway: a client-facing deck earns approval by making the brief, evidence, tradeoffs, and requested decision easier to see than the mockups.