How to Use Commitment Language to Build Integrity
Hey 👋 - Ilya here.
What's up and welcome to the Weekly One on One!
Here's one short tip on how to Level Up as a developer.
Today's issue takes about 3 minutes to read.
Enjoy.
In today's issue, you're going to discover one powerful way to practice integrity and build a reputation for honoring your word. I learned this framework from Roy Osherove's book Elastic Leadership.
People will judge you by how well you deliver on their expectations.
When you promise to do something, you're setting expectations. When something comes between you and your delivery, you will be judged. It might not be your fault, but it does not matter.
By using proper commitment language, you can make sure to always honor your word.
Let's dive in.
Integrity
Integrity consists of three parts:
- Say you’ll do something
- Mean what you say
- Do it (or raise a red flag)
Most of us are familiar with #1 (Say you’ll do something). Almost every interaction at work leads to someone committing to doing something.
Often we do not mean what we say. Lack of knowledge, experience, fear of speaking up. They all lead us to say something we don't really mean. And it leads us not doing it, and not raising a red flag.
Non-Commitment speak
Do those sentences sound familiar?
- The bug will be fixed by the end of the sprint
- I think I can do it tomorrow
- I hope we deploy it next Tuesday
According to Roy Osherove, those are just wishful speaking.
- Do you know for sure that the bug can be fixed by the end of the sprint?
- You may think you can do it tomorrow, but will you? Will you finish?
- You hope? So what? Will it or will it not be deployed?
How to fix it
The fix is simple. Practicing it is hard, but totally worth it. It consists of two parts:
- Use commitment speak
- Only commit to things under your control
1. Commitment speak
The first part is rephrasing every commitment with the following formula:
I will [do something] by [certain date]
- Will: not hope, not think, not might
- Do: something specific
- By: set expectations with a certain date
2. Only commit to things under your control
Using the above formula, you can still commit to something and end up not doing it.
This part was a game-changer for me. Only after learning this I realized how vague the language I was using was.
Always make sure, that you commit only to things under your control.
People
You may commit to meeting with Sara by Thursday noon, but she will not be available.
Circumstances
You might commit to fixing a bug by tomorrow morning, but bugs are unpredictable.
You can commit to:
- Sending out an email
- Spending 2 hours working on the bug
- Writing a document
- ...
Raising red flags
When you start following this framework, raising flags becomes easier.
People will know that you always do what you say you will. You will become more comfortable speaking up. Someone with your reputation raising flags means that the situation is serious and you're not just trying to avoid commitment.
Obstacles will be discovered and solved earlier.
Do it now
- Think of the next most simple thing you know you will need to commit to doing
- Phrase is using will, do & by
- Doublecheck its under your control
- Raise red flags when needed
Thanks for reading. See you next Wednesday.
That's all for this One on One. 1 tip at a time to Level Up as a developer.
If you're not getting value out of these tips, please consider unsubscribing.
I won't mind and there are no hard feelings.
Alternatively, if you are enjoying this newsletter, the best compliment you could pay me would be to share it with one person who you think would benefit from it.
See you again next week.
Cheers,
Ilya