The authors talks about the three parts of an actual commitment -

  1. You say you’ll do it
  2. You mean it
  3. You actually do it

He then talks about the importance of finding those telltale signs that one of those three stage is not going to happen for example when someone says “Need/Should”, “Hope/wish”, “Let’s” those are most likely not going to happen

On the other end of the spectrum there are signs that a commitment as been truly made - When someones takes it personnaly, for example “I will finish it by X”

If the commitments involve other people you shouldnt commit all the way but instead set specific actions to try to make sure that the commitment will go through,

Instead of saying yes to something that might be impossible you can commit to specific actions, instead of saying I will fix all 25 remaining bugs before the release you can commit to those actions:

  • Go through all 25 bugs and try to recreate them
  • Sit down with QA to see a repro
  • Spend all the time you have this week trying to fix each bugs

Sometimes you’ll just fail, and thats fine as long as you can reset expectation as soon as possible

The Meaning of Saying Yes

  1. Saying “Yes” as a professional is a commitment, not a guess.
  2. A true “Yes” means you understand the task, the risks, and the work involved.
  3. Once you say “Yes,” you own the responsibility to deliver on your promise.

When to Say Yes

  • You should only say “Yes” when:▪ You have enough information to make an informed decision.
  • You believe the task is achievable within the given constraints.
  • You are willing to be held accountable for delivering the result.

The Danger of Saying Yes Too Soon

  • Saying “Yes” without fully understanding the task leads to missed deadlines and stress.
  • A professional does not blindly commit to something they are uncertain about.
  • If unsure, instead of saying “Yes” immediately, ask questions, seek clarification, and estimate properly.

Making Commitments with Confidence

  • Instead of vague commitments, professionals should be clear and precise about what they are agreeing to.
  • If obstacles arise after saying “Yes,” a professional communicates early and works to re-negotiate expectations if necessary.
  • A commitment is not just to management but to yourself and your team.

A Professional’s Integrity

  • A software developer’s integrity is built on honoring commitments and delivering on promises.
  • It’s better to say “No” or “I don’t know yet” than to make a promise you cannot keep.

Saying “Yes” is just as important as saying “No.” A professional only commits when they truly mean it, ensuring they can deliver on their word. Integrity, accountability, and clear communication are key to making “Yes” a statement of confidence and professionalism.