The First Commitment Matters Most

The Day I Told the Team "The Date Is the Date"

Years ago I led a claims system redesign. The team had been working hard. They came to me with an escalation. They could not hit the committed date. The escalation was clean. They had data and they had reasoning. What they did not have was an alternative date, because nobody had ever taught them they were allowed to bring one. They brought me the risk. They did not bring me the choice.

The executive pressure was real. Sponsors had committed downstream things on top of the date. There were calendar items already booked, internal promises already made, downstream teams who had built plans on top of ours. I felt the weight of all of that. I let the weight do the talking.

I told the team the date was the date. I did not ask why they had flagged the risk. I did not try to understand what was at risk. I did not ask what date they would bring instead, because I was not in a frame of mind to listen to one. I closed the conversation by repeating the commitment back to them and walking out.

What That Cost

The team delivered on time.

That is the line that almost made me think the call had been right. They hit the date. The internal promises got kept. The other parts of the program that had been waiting on this foundation could finally start. On a status report, my piece was green.

Underneath the status report, the cost was substantial. The system was not in production yet. We were still building it in test, and what my team had finished was the first piece in a larger puzzle. The rest of the program was going to build on top of it.

We had delivered the piece to the date. We had not delivered it to the quality the rest of the program needed. Defects piled up. We pulled in critical resources to fix work that should have been finished the first time. The other pieces, the ones that were supposed to build on top of ours, started hitting the problems the foundation had not resolved. The program slipped. The pieces behind us got pushed behind further. The team that had done the carrying watched the cleanup happen, and they knew the cleanup would not have been needed if I had listened the first time.

Trust eroded. Not all at once. It eroded in the small ways trust erodes when a leader tells a team that the leader's information matters more than theirs. The team kept working. The next time they had a concern, they raised it more quietly. The time after that, they raised it later. The time after that, they did not raise it at all.

That was the cost. The first commitment had been mine to make on purpose, and I had made it on momentum instead. Everything I lost after that was a payment toward the first error.

The Father's Lesson About the Truth

My father told me a long time ago that you should always tell the truth, because that way you do not have to remember what you did not tell somebody.

The line was about personal honesty. It applies to commitments almost word for word. The first commitment is the truth you said out loud. Every commitment after that has to be consistent with the first one, or you have to spend energy maintaining different versions of the same story for different audiences.

A leader who makes a careless first commitment ends up keeping multiple versions of the work in their head. The version they told the executive. The version the team is actually working on. The version they told the sponsor last week. The version that will be in the next status report. Each version has a different shape. Each version requires its own maintenance.

The cost of that maintenance is high. The fix is to make the first version match reality, even when reality is not what the executive wants to hear.

What a Real First Commitment Includes

A first commitment that holds is not a single date. It is a Pack of Six conversation, said out loud at the same time. Time, cost, scope, resources, risk, and quality all get named, even if some of them are named loosely. Four bullets cover the work.

If those four are clear at the moment of the first commitment, the commitment can hold even when something changes. If they are not, the first commitment is a placeholder and you will be repairing it for the rest of the work.

How to Repair a Bad One

There are weeks where you discover the first commitment was wrong. The information that would have changed it shows up after the date is committed. The work turns out to be different from what you expected. The team flags the risk after the executive has already published the date.

Here is what I do now. The discipline came at a cost. There was a great analyst on the team I made accountable for a date I had refused to revisit. The pressure landed on him. He delivered. He also burned out. He doubted himself in ways he did not deserve to. I made my mistake his failure. Never again. The four steps below are the ones I built so I would never do that to somebody again. I run them every time. They are not always convenient.

The repair is not free. The repair is much cheaper than what I did the first time, which was to push through and pay later.

The first commitment matters most because it sets the floor for everything that follows. Make it on purpose. Name what is being committed and by when, with what and at what cost, at what level of certainty, and at what level of done. If you discover later that the first commitment was wrong, repair it quickly and clearly. The trust your team has in you is built and broken on the first commitments more than on anything else you do.