Do As I Say Not As I Do Quote

The Do As I Say Not As I Do Quote: How It Actually Works In Practice

Most people throw this around as a joke without understanding what makes it useful. The quote itself is simple: "Do as I say, not as I do." It appears in parenting, leadership, mentorship, and pretty much any situation where someone with more experience gives advice they can't fully follow themselves. But treating it like a bumper-sticker phrase misses the actual mechanics of when it works and when it backfires. The quote comes from situations where the speaker has knowledge but not the discipline, resources, or circumstances to apply it consistently. A father who smokes tells his kid not to. A manager who works eighty-hour weeks tells their team to maintain boundaries. A trainer who barely sleeps recommends eight hours of rest. The pattern is identical across every context. What most people don't realize is that the quote only carries weight when there is actually a knowledge gap to bridge. If someone is handing out advice in an area where they have no real expertise, the "not as I do" part doesn't save them. It just makes them look dishonest. The quote functions as an honest admission of your own limitations while still claiming authority over what you know. That distinction matters more than people give it credit for.

I spent years managing a team where we had to scale a deployment pipeline under tight deadlines. I kept telling engineers to write comprehensive test suites before merging code. I wasn't doing it myself because I was heads-down on architecture decisions and third-party integrations. One junior dev called me out publicly in a standup, which was fair. I didn't have a good answer other than the quote itself. That exchange changed how I approached the problem. Instead of just telling people what to do, I started blocking out specific time in my own sprint to do the testing alongside them. The quote stopped being a shield and became a benchmark I had to actually close the gap on. Here is what beginners in leadership tend to miss. The quote works best as a transitional phrase, not a permanent stance. When you say "do as I say, not as I do," you are implicitly admitting that your behavior is behind your guidance. That admission should drive action, not excuse inaction. I've watched too many people use this as a get-out-of-jail-free card for years. It stops working the moment anyone notices you haven't moved. There is also a structural problem with the quote that nobody talks about. It creates a credibility trap. The more you lean on it, the more people tune out the actual advice that comes with it. You start hearing versions of "yeah yeah, do as she says, not as she does" muttered under breaths in meetings. The advice itself—the part that is actually good—gets rejected on association. This happens faster than you would expect. Within three or four instances of the same pattern, people stop hearing the guidance and start hearing the hypocrisy.

From a practical standpoint, here is how you handle this when you find yourself in the position of giving advice you aren't fully following. First, qualify it immediately. Don't drop the quote and walk away. Say exactly what you are missing. "I know I'm not doing X right now, but the reason I'm saying it is Y." That removes the sleaze factor and keeps the advice itself accessible. Second, pair the quote with a timeline. Tell people when you expect to be living it yourself. Even if that timeline is unrealistic, it shows you aren't treating the gap as permanent. Third, create a checkpoint. Pick a date three weeks out and ask someone to hold you accountable on whether you've closed the gap. This last one is the part most people skip, and it is also the part that determines whether the quote survives beyond the first conversation. The quote has hard limits. It does not work when the advice involves harm prevention. Telling someone not to do something dangerous while you are doing it yourself is not a wisdom gap, it is a contradiction that will blow up. It also breaks down in high-stakes technical fields where your behavior is directly observable. If you are telling an engineer to review pull requests carefully and you are submitting unreviewed code, the quote doesn't help. The evidence is right there in the repo. For reference, in contexts where mentorship is the primary dynamic—coaching, advisory roles, teaching—the quote retains more value because the power distance justifies a temporary credibility deficit. In peer relationships, it tends to erode trust quickly because there is no structural reason to accept your authority over the advice.

If you want to read about the broader concepts this quote touches on, the closest academic framework is what is called "legitimate peripheral participation" in communities of practice, originally described by Lave and Wenger. It explains how newcomers learn from people who are further along but still learning themselves. The quote is basically a colloquial shorthand for that dynamic. There isn't a single canonical source for the exact phrasing. You will find variants dating back to at least the early twentieth century in American speech, often attributed to various figures in military and vocational training contexts where experienced personnel gave guidance they could no longer fully follow due to age or role changes. The takeaway is straightforward. The quote is a tool, not a personality trait. Use it when there is a real knowledge advantage you can offer despite your own gaps. Drop it the moment it becomes a pattern people notice. And always, always close the gap faster than you advertise it.