Part of the Pressure Intelligence™ framework
guide
Member
Member
Member

The Dateline

A field guide for a leader with a high-stakes deadline at risk: deciding what fits before a date that isn't moving, so the tradeoffs get made on purpose.

The Dateline
97
the-dateline

How to decide what fits before a date that isn't moving, so the tradeoffs get made on purpose instead of late at night.

Navigating outside forces

The challenge: A high-stakes deadline is compressing the time we have

When the date is fixed, something else gives, whether or not anyone decides it. Scope and standards get traded away in small late-night choices, and a team that blurs its date with its quality standard tends to defend the date while the standard slips. On large IT projects, McKinsey and Oxford found the schedule usually holds while value gets traded. The guide helps you decide what fits before the date decides for you, name the line that will hold, and hear early from the people who know the work.

Who it’s for: Leaders holding a date they can’t move: a program lead, a product owner, a function head with a launch, a contract or a public commitment on the calendar. Read it on your own first, then take the conversation in part three to your team.

How it shows up

Part 1 of 3 · Notice the effect. The scene, where it lands, and the questions that often sit with you before you fix anything.

The scene

Six weeks before a launch, the plan still looks sound on paper. Four weeks out, a test environment slips and two features turn out to be harder than estimated. Two weeks out, the team is working weekends, and small decisions start getting made late at night by whoever happens to be awake: a test skipped here, a known issue deferred there. The date belongs to a customer, or a market window, or a commitment made well above the team, and moving it isn’t on the table. Each choice the team makes is reasonable on its own. Taken together, they are reshaping what will ship, and the leader can’t point to the meeting where anyone agreed to that.

Where it lands

  • In you: you tend to work longer and say less about the tradeoffs, because there is a quality line you won’t drop that you haven’t yet said out loud.
  • In your team: scope and standards often get traded away without an explicit decision, defects are found late or in public, and the same few people work the weekends.
  • In your organization: the people who save launches typically get rewarded for the rescue, and the next launch is planned on the same assumptions that made the rescue necessary.

Questions to ponder

Think of the last week of the work, and ask:

  • Which tradeoffs got made this week, and can we name who made each one?
  • Is the quality line written down, or does it tend to live in the leader’s head?
  • If the leader left for a week, who would hold that line?
  • When someone last told us the work would take longer, what did we do with it?
  • Do the estimates from the people doing the work match the plan we are holding?

Questions to discuss

With the list of what is fixed and what is open in front of you:

  • Which of the six dials are we actually turning this week, and who decided? Teams can usually name a few tradeoffs that were made without a decision.
  • What would we rather slip, the date or the line? Ask it before the night it has to be answered.
  • How could we change the way we work so that each of us helps hold the line when the schedule pushes on it, and the person who says the work will take longer is heard rather than overruled? Name who holds the line when the leader is not there, and what the rest of you will do the next time someone says so.

Try this week

Before the pressure spikes again, take twenty minutes with the team. Write down what you are holding fixed and what is open: the date, what ships, what it can cost, who works on it, how good it has to be. For each one, say who gets to decide when it moves. Then name the one quality line that isn’t open at all. Many teams find at least one tradeoff that was already being made without anyone choosing it.

Keep reading with a free account

  • The six dials a deadline has, and why each one is turning whether or not anyone is turning it on purpose
  • What holding a date too hard taught one good engineer, and what it cost
  • How a launch date differs from the quality line underneath it, and the person who holds that line when you aren’t in the room
  • The question to ask the people doing the work before the plan is set, and again at each checkpoint: what would you cut first, and what would you protect?
  • The research behind it, and books to read next
  • The toolkit: questions to ponder, questions to discuss, things to subtract, actions to take
  • The kit, as downloads: the full Field Guide, a Leader’s Guide, and slides for the team conversation
Create a free account

Free, no card.

Open the field guide >>

About the author

Mark D. Benson
Mark D. Benson
Founder of Resonant Vector™
Resonant Vector
Full profile →

Mark D. Benson is the founder and principal writer of Resonant Vector, the home of Pressure Intelligence, and the host of Pressure Rising™. He is a product and systems leader who has spent his career running global teams, complex platforms, and consequential decisions under real constraint.

His career sits where strategy, technology and large human systems meet, in places where high stakes are the norm.

Resonant Vector is his commitment to learning in public and sharing what helps leaders and teams perform under pressure.

More about Mark can be found at markdbenson.com.