Repetition: Why You Need to Become a Chief Repeating Officer

You’ve hosted the webinar, you’ve shared the case study, and you’ve presented the ROI of your latest project. You think, "Right, they’ve got it. We can move on now." Then, three weeks later, a senior stakeholder asks: "Why did we only test this with five users?" or "Do we really need research for this next phase?"

Your first instinct might be frustration. You might feel like you’re failing at the "education" part of your job. But here is the mindset shift you need: The education is never done.

In design leadership, if you aren't tired of saying it, they haven't heard it. You aren't just a Design Director anymore; you are now a Chief Repeating Officer.

Why People "Forget" Design

It’s not that your stakeholders aren't listening. It’s that they have a thousand other pressures on their mind—revenue targets, technical debt, hiring, and roadmaps. Design isn't their default setting; it’s yours.

When the pressure mounts, people revert to their "factory settings." They go back to what’s safe and what’s fast. Your job is to constantly, gently, steer them back toward the user.

The Power of Small and Frequent

One mistake I see emerging leaders make is trying to "dump" all the information at once. We give them a 40-page deck and expect them to remember it for six months.

Stakeholders have short attention spans. If you want your message to stick, you have to serve it in bite-sized pieces:

  • Zoom in when things go awry: Use your relationships to spot when a project is drifting away from user needs. Don't wait for the big review; have the quick 5-minute chat now.

  • Adapt the practice: Don't just repeat the same words. Change your delivery for different stakeholders. What works for a Product Manager might not resonate with a CTO.

  • Always communicate: Even as your design practice matures, don’t stop talking about the basics. There will always be new people joining and old habits returning.

Don't Grow Tired of the Basics

It can feel like a "broken record" situation when you’re explaining for the tenth time why we don't need 1,000 users for a qualitative study.

But look at it this way: Every time they ask a "basic" question, it’s an opportunity for you to reinforce the impact of your team. It’s a chance to show, not just tell, how design solves their specific business problems.

Final Thoughts

Communication is the heartbeat of leadership. As the design practice grows, your role moves away from the "doing" and into the "communicating."

Don't resent the repetition. Embrace it. By being the voice that consistently champions the user, you’re creating the space your team needs to do their best work.

If you want the business to value design, you ha

Venessa Bennett

Thanks for reading. I’m a Design Leader and speaker based in London. I help to craft digital experiences and solve problems for businesses and their users.

Next
Next

Drop the Design Jargon