A condition read · Act now

You have one quarter to fix a transformation
that took three years to break.

The board wants it corrected this quarter, not diagnosed over two. A six-week assessment is not available to you.

Ten questions. Five minutes. Free, and nothing is stored or sent.
01

What the pressure is actually asking

Not for a plan. For evidence that someone knows what is wrong. The fastest way to lose the quarter is to commission a study; the fastest way to hold it is to produce a defensible read of where the operating model stops converting, and act on the two conditions that matter most.

02

Why speed and rigor are not opposed here

A long diagnostic spends its time on breadth. What you need is depth on the conversion points: what enters, what commits, what executes, what proves. A focused read across the operating system is enough to surface whether the conversion structure is holding. That is enough to decide what deserves a deeper read. The instrument exists because the pressure is normal.

03

What to refuse

Accelerating along an unevidenced path. Moving faster produces more spend and no more proof, and it consumes the authorization that would otherwise fund the correction. A reset is not a restart — expect a meaningful share of the work to survive unchanged.

Before you commit to a plan,
find out what you are working with.