What this principle is for.

A high hiring bar is only the start. Today's standard will not be enough tomorrow. Everyone is expected to raise their own bar. Customers will not lower theirs.

Quality is how you keep trust. When a product, a service, or a process fails, confidence drops in the thing and in the people who shipped it. That is true whether the consumer is an end customer or another team.

This principle shows up as operational excellence. You never assume the current process is good enough. You pick the few metrics that tell you the truth. You fix the root cause so the defect cannot travel. You balance this with Bias for Action. Highest standards is not a reason to block the business while you polish.

It also shows up in the thinking. The best calls come from writing: a press release for the vision, a FAQ for the hard questions, a short narrative that tests the assertions with data. Inviting scrutiny on the writing is how the work gets better. Sloppy prose is sloppy thought.

Under, just right, over.

Look for a defect they stopped from going downstream, and a launch they held for a real reason. "I have high standards" is a slogan. Perfection that never ships is the over move. Shipping junk and calling it Bias for Action is the under move.

SituationUnderJust RightOver

What it looks like in the work.

Stop the line

A defect is about to travel to the next team, or to a customer. The just-right move is to stop the line, fix the cause, and start again. Passing it downstream so your date looks clean is the under move. Look for a time they pulled that cord, and what stayed fixed afterward.

Hold the launch two days, not two months

A bad bug is a reason to slip a couple of days. A typo in an appendix is not. Highest standards without triage is fear. Bias for Action without standards is hope. Name the defect that was worth the hold, and the defects you shipped on purpose.

The writing is the thinking

A short narrative, a press release, and a FAQ will expose a weak idea faster than a slide deck. If the numbers in the appendix do not match the body, the thinking is not done. Look for how they invited other people to tear the document apart, and what got better because of it.

Individual and manager.

Individual

Your docs match themselves. You do not send a known defect to the next person. You can say which standard you raised after you hit the old one. You get annoyed by "good enough" when the customer will feel it, and you can still ship when the leftover work is truly leftover.

Manager

You set goals the team is proud to hit, not ones they sandbag or ones they cannot believe. You review work. You name the miss. You fix the system so the miss cannot recur. You do not confuse relentless standards with a culture where nobody will take a swing.

Questions that make the principle concrete.

  1. What defect did you stop from going downstream, and what did you change so it could not recur?
  2. When did you hold a launch, and which defect was worth the hold?
  3. Which standard did you raise after the team had already hit the old one?
  4. Where are you accepting a lower standard right now because the date is close?
  5. How do you decide a goal is a stretch instead of a sandbag or a fantasy?
  6. When the first answer on a problem was tidy, what did you do next?
  7. What did you refuse to compromise on, and who was the customer of that refusal?
  8. How do you review work without creating a team that is afraid to start?
  9. Where do the numbers in the document disagree with each other, and what does that tell you?
  10. How do you keep Bias for Action from turning into an excuse to ship junk?

Writing that goes deeper.

Principles that sit next to this one.