Commitment Language is a concept that focuses on creating explicit agreements and expectations between individuals and teams. I was introduced to it by Richard Halliwell (CEng), but it originally comes from the book Elastic Leadership by Roy Osherove.

Not commitment language ❌
“I *hope* to have this done by tomorrow”
“I’ll *see* if I can do it this week”
“I’ll *try* and get around to it *sometime soon*”

Commitment language ✅
“I *will* have this done by tomorrow”
“I *will* complete it by the end of the week”
“I *will* have it done by next Wednesday”

Yoda says it best, “Do or do not, there is no try”

Initially, I thought “yikes”, this sounds a heavy handed and a way to beat people with a stick when things go wrong. However, experiencing it in practice led to an “aha” moment.

It’s about removing ambiguity and creating clarity. Clear commitments build trust within and between teams and individuals. Everyone knows what to expect, reducing friction, preventing time-wasting, and improving collaboration.

🤔 What if you’re uncomfortable committing to something? Just say so! It’s a great way to flush out what’s actually priority.

🤔 What if you can’t meet a commitment? Just communicate this as soon as possible. It’s perfectly acceptable not to meet a commitment if circumstances change, *provided* you keep everyone informed.

🤔 What if you’re like me and struggle with on the spot commitments? Try a commitment to a commitment. For example, “I’ll get back to you by tomorrow to confirm when I can complete this task.”

Commitment Language doesn’t just change how we talk; it transforms how we collaborate, fostering a culture of reliability and mutual respect.

Where do you start? Have a conversation about it with your team, and review your role responsibilities so there’s clarity around accountability and responsibilities. A good first step (and something I’m a stickler for) is having owners and dates on actions from meetings.

Give it a try!