PRESSURE PATTERN #10

Stripped Threads

A thread strips from over-tightening beyond what it was designed to hold

Read this online Was this forwarded to you? Subscribe to Pressure Patterns and get the next one in your inbox.

Having integrity is one of the things I aspire to most as a leader. It is also the reason my team once stopped telling me the truth.

Years ago I ran a program building a ruggedized field radio for a defense customer. Nine months to prototypes. I had built that estimate myself and priced the work as a fixed bid against it, so the date was the economics too. But that is not why I held it. I held it because doing what we said we would do was who we were, and I believed it was most of the reason a client chose us over someone cheaper.

Then a senior engineer I will call Dan came to me while we were traveling in Amsterdam, just before a program review with vendors from around the world. The embedded software work on the core module that ran the radio was far more complex than anyone had estimated. Understanding it meant working through a four thousand page manual. Dan and the team estimated they needed three more months.

I said no. I walked him through the commitment, the analysis behind the nine months, the fixed bid. I told him the date was not one of the variables available to us and we had to find another way.

Dan did not argue. He was disappointed, and went back to work.

We shipped those prototypes three months late. Exactly the timeline Dan gave me. I filed it away as an estimation problem.

Six months later we were putting a proposal together for a different customer. Dan and his team built the estimate and it came back larger than I expected. I pushed on it in review, they held their ground, and I read it as caution and sent it to the customer.

The customer told me directly that our proposal came in twenty-five percent higher than every other one on the table. A margin that had stopped being a question about methodology and started being a question about whether we knew what we were doing.

We discounted to close the gap, and they went with us for that program. Then they did not come back for another one. The padding did not lose us the work. It cost us the relationship.

That is when I finally saw it. The estimate was inflated because of me.

I should say what I cannot prove. I have wondered since whether that margin was really the padding, or whether we were simply priced wrong for that class of work, and I cannot rule the second one out. What I can say is what I saw inside the estimate, because I watched the margin go in.

In Amsterdam I had taught a capable engineer that telling me the truth about risk was expensive and pointless. He did not need to say a word about it afterward. The team learned it from what happened to him. So the risk went into the one place I could not overrule.

He was not being dishonest. He was protecting himself and his coworkers from me.

A screw holds because it is tightened to a point.

Past that point the threads strip. It keeps turning, smoothly, easily, gripping nothing at all, and from above it still looks perfectly seated. You find out when the joint takes a load.

A thread strips from tightening, not from neglect. And once it is stripped, the instinct that got you there, turning it a little harder, does not bring it back.

I was not careless, and I was not under anyone’s thumb. I was holding a virtue, in public, with conviction, and the conviction is what made me deaf to the one person trying to tell me something I could not see.

Good values do not protect you from this. Held hard enough, they can become a mechanism for disconnection and distrust.

What it costs, beyond the schedule

Most numbers inside an organization are doing two jobs. Measurement, where the value sits in accuracy. And accountability, where the value sits in whether the number gets met. A schedule estimate is both at once, which is why it corrupts faster than most. Under pressure the second job tends to win, because the accountability consequence is immediate and personal while the accuracy consequence is distant and shared.

Steven Kerr wrote about this in 1975, in a paper on organizations that reward one behavior while hoping for another. His point was that people are not confused when it happens. They read the system correctly and act on it.

Three costs, none of them in the register of morale:

• Decision quality downstream. What you plan, price, and staff runs on numbers somebody handed you. Hidden margin does not make those decisions conservative. It makes them confident against inputs you have misread, and you attribute the gap later to execution.

• The earliest signal, which is the cheapest one. A risk raised months before a date costs a conversation. The same risk found in integration costs the schedule.

• Risk aversion drift. My team stopped asking how to deliver aggressively at the right quality, because I had settled that question for them. That is the cost I would most like back, because a team that stops proposing the bold version of the work does not announce it.

How to check your own threads

Here are four ways to check whether the threads are stripping:

1. Have estimates drifted in one direction over time, with nothing about the work to explain it?

2. When did someone last bring you a risk months early, while it was still cheap? If you cannot remember, that is the finding.

3. After you overrule someone and they turn out to be right, do they hear it from you?

4. Notice the absence of argument. A team that has stopped disagreeing with you is cause for concern.

None of this argues for caring less about your word. It argues for a different idea of what keeping it means. A commitment is made against a set of facts, and when the facts move, going back early to the person you promised is not a breach of integrity. It is what integrity looks like when it is done well.

This pattern is part of the library of leadership content at Resonant Vector published by Mark Benson to help leaders and teams thrive under pressure.