He emerges late in the project. He was never mentioned in the brief, or the kickoff, or any of the three rounds of revisions you thought brought you to approval. He appears suddenly in a Tuesday morning email with the subject line “small thought from my nephew who does a bit of this” — and from that moment forward, nothing is the same.
The nephew knows about design. Or more precisely, the nephew has used Canva, has opinions about fonts, once helped a friend with a logo for a food truck, and has watched enough YouTube to feel confident in a visual critique. He is eighteen. He works in construction. He does not have a client relationship with you or a budget or a stake in the outcome. None of this matters. He is the nephew, and his feedback has entered the process.
The Taxonomy of the Design-Adjacent Relative
The nephew is the most common variant, but the category is broader. There is the daughter who studies graphic design in her first year of university and has Opinions about color palettes. The husband who worked in advertising in the nineties and therefore believes he understands the current landscape. The business partner who once hired a freelancer for a personal project and now considers themselves a procurement expert. The friend who just redesigned their blog.
What unites all of them is the same dynamic: they are not the client, they did not commission the work, and they have been given informal veto power by someone who does not fully understand that this is what they’re doing. The client isn’t malicious. They showed the nephew because they were excited, or uncertain, or because the nephew is around and has an opinion on everything. And then the nephew had an opinion on this, and now here you are.
The feedback, filtered through the client, arrives in one of two forms. The gentle form: “My nephew had a thought, take it or leave it, just wondered what you think.” The catastrophic form: “I showed it to some people and they felt the logo could be more dynamic. Can we try something bolder? Maybe something with more energy? They also thought the blue was a bit flat.”
Why This Feedback Is Uniquely Dangerous
All creative feedback has to be interpreted. The client says “make it pop,” and you translate that into something actionable. The client says “I don’t love it,” and you ask questions until you understand what “love” looks like in visual form. This is normal. This is the job.
The nephew’s feedback is dangerous because it has already been translated once, by someone who also isn’t a designer, and what arrives to you is a twice-removed approximation of an instinctive reaction from a person with no professional context for their instincts. “More dynamic” might mean “I found it boring” or “I liked the previous version better” or “I found the background color slightly overwhelming on my phone screen” — and you have no way to ask the nephew which of these he meant, because the nephew is not your client and is probably installing drywall right now.
You act on it anyway, because the client is excited about the nephew’s input, or slightly insecure about their own taste, or just wants to see what “dynamic” looks like before they decide. You come back with three new directions. One of them the client likes. The nephew would have preferred the original, apparently. The project has now added a week and one invoice dispute.
How to Handle the Nephew Without Losing the Client
The first line of defense is the brief. A proper brief — one that establishes stakeholder sign-off, defines who has decision-making authority, and clarifies the review process — makes it harder for the nephew to enter the process formally. It doesn’t stop the client from showing the work to family; nothing stops that. But it gives you a frame to reference when the feedback arrives. “As we agreed, decisions on visual direction are being made by you and your marketing manager. Happy to schedule a call to discuss any concerns before we act on them.”
The second line of defense is curiosity, not defensiveness. “Tell me more about what your nephew noticed — what specific element was he reacting to?” This slows the feedback down. It forces translation back through the client. It often reveals that the nephew’s concern was minor and specific, not the brand overhaul it sounded like in the email.
The third line of defense is accepting that this is the job. Not because the nephew is right — often the nephew is emphatically wrong — but because client management is creative work too, and how you handle the nephew situation says as much about your professionalism as the work you delivered.
The KPI Shark notebook is ideal for writing down what you wish you’d said to the nephew in a format that never gets sent. Highly therapeutic. Highly recommended.
A Note for the Nephews Reading This
If you have opinions about design: excellent. Opinions are the beginning of taste. If those opinions are being relayed to a professional who has been hired, briefed, and paid to deliver a specific result: please consider that there is context you don’t have. The blue might be flat because the brand is deliberately restrained. The font might feel boring because legibility at small sizes was a requirement. The “energy” you’re missing might have been in the version before the client asked for it to be removed.
You’re not wrong to have the feeling. You’re just maybe not the right person to act on it in this particular chain. Visit No Briefs Club when you’re ready to develop your opinions into expertise. We’ll be here.
