Feedback, revisions & approvals
Make feedback specific, keep decisions clear, and avoid unnecessary rounds.
What does useful feedback look like?
Explain what is not working, who it affects, and why. “Our audience may miss the main action because this heading competes with it” is more useful than “make it pop.” You can describe the issue in plain language; I will work through the design response.
Should everyone on my team send comments?
Gather feedback from the people who matter, resolve conflicting opinions internally, and send one consolidated set of notes through one decision-maker. A clear approval path helps avoid designing in several directions at once.
What if the first direction is not right?
Tell me which parts miss the goal and what context might be missing. We will use that information to refine the work or revisit the direction. A reference can help, especially when you explain the specific quality you want to achieve.
Is a revision the same as a new request?
Refining an agreed direction is different from changing the audience, concept, deliverable, or approved content. A significant change may need a new request or revised estimate. I will clarify that before moving forward.
What should I check before approving?
Review the work in the context where it will be used. In particular, confirm:
- Names, spelling, prices, dates, claims, contact details, and links.
- Required formats, dimensions, versions, and brand consistency.
- Any legal, compliance, or stakeholder approvals your business requires.
Approval tells me the work is ready for its agreed next step. Changes after approval can affect timing and production costs.