“I love repeating myself” – said nobody ever. When asked to repeat ourselves, we seem to fall on a spectrum from “I don’t like it” to “I dread it so much it makes my blood boil”. People generally don’t like repeating themselves. As software engineers, we run into this far too often, probably because we value efficiency. The DRY principle in programming also doesn’t help. We’re taught that repetition, at least in code, is a bad practice and can lead to maintenance nightmares.

Substack is a platform for independent writers and journalists to publish and monetize their content. Through newsletters, articles, and podcasts, Substack offers insights into a wide range of topics such as politics, technology, culture, and personal development. Readers can subscribe to their favorite writers and receive regular updates, analysis, and commentary on the issues that matter to them. Additionally, Substack provides tools and resources for writers to grow their audience, engage with their readers, and monetize their content effectively.

Substack

Repetition in communication, although often perceived negatively, is essential for effective teaching, driving change, and ensuring tasks are completed. Key strategies include using multiple channels, setting up reminders, and asking for summaries to reinforce messages. Deliberate redundancy can enhance message retention, especially in leadership roles.

It's Not Nagging: Effective Communication is Deliberately Redundant

Let's look at why needing to repeat ourselves feels so unpleasant

Yet, there are good reasons why repetition is necessary

Here’s how and when to use redundancy deliberately to get your message across:

🚨 Last call for the 4th cohort of Impact through Influence 🚨

I am, in fact, Dory.
“Can you please confirm this is what you want (because last time it wasn’t either)”

A valuable leadership lesson: State and restate your intent.
It’s not micromanaging if you restate the goal but don’t over prescribe the solution.