Icon Design Communication & Stakeholder Relations 2 — Questions and Answers
Question 1: A client insists on adding a drop shadow to every icon in a set to make them 'pop.' How should you respond?
- Refuse and submit icons without shadows
- Implement shadows on all icons immediately without discussion
- Explain the visual consistency and legibility trade-offs, then propose a limited test on select icons (Correct answer)
- Ask the client to hire a different designer
Correct answer: Explain the visual consistency and legibility trade-offs, then propose a limited test on select icons
Proposing a controlled test respects the client's goal while educating them on potential downsides.
Question 2: Which document is most effective for aligning stakeholders on icon style before design work begins?
- A final invoice
- A visual style brief with mood boards and reference icons (Correct answer)
- A post-project retrospective
- A technical spec for file formats only
Correct answer: A visual style brief with mood boards and reference icons
A visual style brief with references aligns expectations before any pixels are created.
Question 3: During a review meeting, two stakeholders disagree about icon metaphor choices. What is the designer's best role?
- Leave the room until they decide
- Pick one stakeholder's preference to keep the project moving
- Facilitate the discussion with user research or usability data to guide the decision (Correct answer)
- Delay the project until both agree independently
Correct answer: Facilitate the discussion with user research or usability data to guide the decision
Bringing objective data into the room shifts the conversation from opinion to evidence.
Question 4: A stakeholder requests weekly progress updates on an icon design project. What format works best?
- A 30-page written report
- A brief visual snapshot showing icons completed, in-progress, and pending, with blockers noted (Correct answer)
- A verbal summary with no visuals
- A link to the raw design file with no context
Correct answer: A brief visual snapshot showing icons completed, in-progress, and pending, with blockers noted
Visual progress snapshots are fast to produce and immediately legible to non-designers.
Question 5: You receive vague feedback: 'These icons don't feel right.' What is the best follow-up?
- Redesign the entire set from scratch
- Ask clarifying questions such as 'Which specific icons feel off and what emotion or quality are you expecting?' (Correct answer)
- Ignore the comment and submit the icons as-is
- Send a long explanation defending your design choices
Correct answer: Ask clarifying questions such as 'Which specific icons feel off and what emotion or quality are you expecting?'
Targeted questions convert vague feelings into actionable, specific design criteria.
Question 6: When presenting icon concepts to non-designer stakeholders, which approach improves comprehension?
- Use technical jargon to establish credibility
- Show icons in realistic UI context rather than isolated on white backgrounds (Correct answer)
- Present only final polished files with no explanation
- Send SVG files without a presentation layer
Correct answer: Show icons in realistic UI context rather than isolated on white backgrounds
Context-placed icons let stakeholders evaluate them as users would, not as abstract shapes.
Question 7: A developer tells you the approved icon set doesn't match the component library's naming conventions. What should you do?
- Tell the developer to rename files themselves
- Ignore the issue since design and dev are separate concerns
- Collaborate with the developer to establish a shared naming schema and update exports accordingly (Correct answer)
- Deliver files with random names and let the PM sort it out
Correct answer: Collaborate with the developer to establish a shared naming schema and update exports accordingly
A shared naming convention prevents integration errors and reduces handoff friction.
A client insists on adding a drop shadow to every icon in a set to make them 'pop.' How should you respond?