The signal moved.
Who owns the response?
Five signals reveal where the system is heading. They do not move on the same timeline. Record them once a quarter and the tool reads each against its threshold — returning a status, the cadence that owns the response, and what that response actually is.
Open the toolNot a dashboard.
A response discipline.
The hard part was never noticing that something moved. It is knowing whether this movement belongs in next week's review, next month's structural diagnosis, or the quarterly capital conversation — and being able to say which, without re-deriving the thresholds from memory every time.
Acting too early on a slow signal produces noise. Acting too late on a fast signal produces cost.
Signals are not operational metrics. They are early inputs into capital allocation decisions. This tool holds the thresholds, reads each signal against them, and names the cadence that owns the response — so the conversation starts at the right altitude.
What the system
tells you about itself.
Marginal cost trend
Is delivery getting cheaper or more expensive? Two consecutive quarters of increase confirms a structural trend; a single-quarter spike above 15% demands an immediate look at whether the cause is local or structural.
Technical debt ratio
Where is hidden cost building? Above 25% of engineering capacity it wants monthly diagnosis; above 33% it is a quarterly capital decision — remediation is funded, or velocity decline is locked in.
Platform reuse rate
Are systems compounding or fragmenting? Below 60% escalates to the quarterly cadence; below 50% is an architectural emergency. Two consecutive quarters of decline is a pattern regardless of level.
Integration complexity index
Where is friction accumulating? Three consecutive months rising is a structural diagnosis; a spike above 20% may mean a bypass decision or an unplanned dependency, and wants looking at now.
Delivery velocity
Is throughput holding, and if not, why? A single quarter's decline is a weekly observation. Two consecutive quarters escalates to monthly diagnosis — and a named structural cause takes it to the quarterly capital conversation.
A status per signal,
and the cadence that owns it.
Each signal is read against its own threshold — no single blended score, because a blended score is exactly what stops you seeing which signal is moving. Every status carries the cadence that owns the response and the response itself.
On track
Monitor. The signal is recorded and inside its threshold. It stays in ordinary observation — no escalation, no capital implication.
Monitor
Monthly. A threshold is crossed or a pattern is forming. This belongs in the monthly cadence as a structural diagnosis, before it compounds into a capital problem.
Act now
Quarterly. The signal is past the point where diagnosis is enough. It belongs in the quarterly capital conversation, expressed as a cost, a return, or a risk.
Two of the five signals carry a real number — the technical debt ratio and the platform reuse rate. For those you record the figure and nothing else: the tool works out the direction and how long it has been moving that way from the quarters you have already recorded. Judgments are not asked for where the arithmetic is available.
This tool instruments the Signal Response Summary table in Part V of The Modern CTO Operating System — the table that maps each signal to the threshold that makes it actionable, the cadence that owns the response, the response required, and the risk of delay. The thresholds here are that table's thresholds.
One thing worth knowing if you have just read Part V straight through: the five signal chapters cover marginal cost, platform reuse, integration complexity, technical debt and AI performance, but the Signal Response Summary table itself substitutes delivery velocity for AI performance. This tool follows the table. AI performance is deliberately not one of the five signals recorded here.
Record it once a quarter, close to the quarterly cadence, when the month's aggregated readings are fresh. A signal you have not measured is recorded as exactly that — the tool distinguishes “steady” from “not looked at”, and the difference is the point.
The single reading tells you where each signal sits today. The sequence tells you something the individual thresholds cannot: whether the signals are converging. Four signals pointing the same way at once is a structural emergency even when none of them has individually crossed a line.
Stop re-deriving the thresholds.
Record the quarter.
Five signals, read against the brief's own thresholds, returning the cadence that owns each response — quarter after quarter, so the pattern is visible before it is expensive.
Open the tool