The phrase “we have always done it this way” is like nails scraping on a chalkboard for me, whether we are talking about a grant process, a program design, or, well … anything. And that specific phrase is not the only one that bothers me. I’ve heard that mindset brought up in seemingly countless other ways, and for some wordplay fun, I grouped other common phrases that have the same basic meaning or issue into three groups according to the underlying resistance:

Corporate & Bureaucratic

• “If it ain’t broke, don’t fix it.”
• “That’s our standard operating procedure (SOP).”
• “It’s just the way things are done around here.”
• “That’s how the playbook is written.”
• “We don’t want to reinvent the wheel.”

Dismissive & Resistant to Change

• “Let’s stick to the script.”
• “Why change a winning formula?”
• “Let’s not overcomplicate things.”
• “We’ve never had an issue with it before.”
• “I’m not looking to rock the boat.”

Philosophical & Traditional

• “Better the devil you know.”
• “Custom is a second nature.”
• “History is the best guide.”
• “Respect your elders (and their methods).”

But why are these phrases so bad? Why is NOT using them one of the lessons I learned in my 20 years of business? When I use any of these phrases aloud or to myself, whether about scope structure, pricing structure, team structure, or productivity tools, usually I am doing something because it is comfortable and maybe even easy, not because it is best for the overall impact, for me personally, or even for the business as a whole.

I also see clearly now, in reflecting on this lesson to not use ANY of these phrases due to their inherent stymying of innovation and progress, that my strong feelings are, of course, why this lesson is in my upcoming book, Playbook for Changemakers: Agile Ways of Working that Amplify Impact:

“Have you ever said, or heard, in your team ‘Because that is how we have always done it’? That phrase is very dangerous for a team, because it risks spending time and effort on something that is no longer of the highest value or impact to the community. It also introduces a risk of wasting team members’ skills and talents.… All of those statements and questions are immediate flags that the team will benefit from an Agile approach, where all team members come together to learn the root cause of the issue.”

• Playbook for Changemakers: Agile Ways of Working that Amplify Impact (Available for preorder on all your usual book sites; then, you can claim your pre-order bonuses.)

I feel so strongly about this particular lesson that it is even the focus of one of our Agile in Nonprofits Lunch & Learn sessions, “Trying New ‘Plays’ as a Team.” You can check it out here.

This lesson is just ONE of the many I’ve learned while being in business, so ICYMI, be sure to check out the rest of the 20 lessons I’m sharing as part of the 20th anniversary for DH Leonard Consulting.

If you have any other phrases you have heard that are like those listed above, I’d love to hear them! Let me know what they are in the comments.