Icon Design Communication & Stakeholder Relations 4 — Questions and Answers
Question 1: Which method best helps remote stakeholders give precise feedback on icon designs during an async review?
- Send icons as low-resolution JPEG attachments in an email
- Share a Figma or design tool link with comment-enabled prototypes at actual size (Correct answer)
- Mail printed copies of the icons
- Present only at in-person meetings
Correct answer: Share a Figma or design tool link with comment-enabled prototypes at actual size
Comment-enabled prototypes at actual size let remote stakeholders pinpoint exact concerns.
Question 2: A client rejects an icon set after final delivery because it doesn't match what they 'imagined.' What process failure does this most likely indicate?
- The designer worked too slowly
- Insufficient upfront alignment — no visual brief, mood board, or mid-project checkpoints were used (Correct answer)
- The client is always unreasonable
- The file format was incorrect
Correct answer: Insufficient upfront alignment — no visual brief, mood board, or mid-project checkpoints were used
Late-stage rejection usually traces back to skipped discovery and alignment steps early in the project.
Question 3: When should a designer escalate a stakeholder conflict to a project manager?
- Immediately upon receiving any feedback
- Only after the project is complete
- When conflicting directives from different stakeholders block design progress and cannot be resolved directly (Correct answer)
- Never — designers should absorb all conflicts silently
Correct answer: When conflicting directives from different stakeholders block design progress and cannot be resolved directly
Escalation is appropriate when conflicting instructions create an impasse that only authority can resolve.
Question 4: You discover that a stakeholder has been sharing early-stage icon drafts externally without permission. What is the best course of action?
- Post the drafts publicly yourself in response
- Address it privately with the stakeholder, clarify the approval process, and add a confidentiality clause to future agreements (Correct answer)
- Abandon the project immediately
- Ignore it since the icons are already out
Correct answer: Address it privately with the stakeholder, clarify the approval process, and add a confidentiality clause to future agreements
A private conversation protects the relationship while a contractual clause prevents future occurrences.
Question 5: A marketing stakeholder wants the icon set to use brand colors while the UX stakeholder wants monochromatic icons for flexibility. How do you resolve this?
- Pick the stakeholder with higher seniority and implement their preference
- Design both a branded and a monochromatic version and present trade-offs for each context of use (Correct answer)
- Use only black icons regardless of both opinions
- Delay the project until they agree without your input
Correct answer: Design both a branded and a monochromatic version and present trade-offs for each context of use
Delivering both variants with use-case guidance lets each team choose the right tool for their context.
Question 6: What does a well-structured icon handoff package communicate to developers?
- The designer's personal style preferences
- Icon names, sizes, color tokens, intended states, and export formats with usage guidelines (Correct answer)
- Only the final SVG files with no documentation
- A list of fonts used in the project
Correct answer: Icon names, sizes, color tokens, intended states, and export formats with usage guidelines
A complete handoff package removes ambiguity and reduces implementation errors.
Question 7: A stakeholder approves icons in a review meeting but later emails requesting major changes. What documentation practice prevents this from being a free revision?
- Meeting notes don't matter since emails override them
- A signed or confirmed meeting summary noting approval, referenced in the contract's revision policy (Correct answer)
- Sending a thank-you email after every meeting
- Recording every meeting without informing participants
Correct answer: A signed or confirmed meeting summary noting approval, referenced in the contract's revision policy
Documented approvals tied to the contract's revision clause define what counts as billable change work.
Icon Design Communication & Stakeholder Relations 4
Which method best helps remote stakeholders give precise feedback on icon designs during an async review?