Numbers record what the business produced. Management changes what it will produce next.
Every executive target is written in the wrong language.
Not because the number is wrong. Because a number is a record of something the business has already produced. Setting a target for a record is not management. It is a request directed at an outcome that has already been determined by the relationships that preceded it.
This is not a criticism of targets. Targets are necessary. They define expectations, create accountability, and establish the standard against which performance is measured. The problem is not that leadership sets targets. The problem is that leadership mistakes target-setting for management.
They are not the same thing.
What Management Actually Requires
Management is the act of changing what a system will produce before it produces it.
That definition is precise and consequential. It means management must happen before the outcome exists — in the relationships, decisions, and operating conditions that will determine what the number records. A leadership team that engages with a business only after numbers appear is not managing the business. It is reviewing it.
The distinction between managing and reviewing is architectural. A review produces accurate descriptions of what the business has done. Management changes what the business will do next. Both are necessary. Only one of them has the ability to change an outcome.
Numbers cannot be managed because numbers exist after outcomes are determined. The close rate that appears in Thursday's operating review was determined by the lead quality that entered the pipeline six weeks ago, the financing constraints that tightened three weeks ago, and the competitive conditions that shifted two weeks ago. By Thursday, every input that will determine next month's close rate is already in motion. The number leadership is reviewing reflects decisions that have already been made. The decisions that will determine the next number are being made now, in relationships leadership may not be monitoring at all.
That is the management gap. And it lives between every number leadership reviews and every relationship that will determine the next one.
Why the Illusion Persists
The illusion that numbers can be managed persists because the organizational system is designed around numbers in a way that makes number management feel like business management.
Targets are written in numbers. Accountability is assigned to numbers. Performance reviews are organized around numbers. Compensation is tied to numbers. Every structural element of the operating system points toward the number as the object of management. That architecture is not wrong. It is incomplete.
Numbers are the correct unit of measurement for outcomes. They are the wrong unit of intervention for causes. When the entire operating system is organized around numbers, the gap between measurement and intervention becomes invisible. Leadership manages what the system makes manageable. The system makes numbers manageable. The relationships that produce them remain unmanaged beneath every operating review.
The interventions are real. They are not reaching the place where the business actually changed.
A coaching program addresses the rep. The lead quality that changed the rep's conversion environment is not addressed by coaching. The financing approval rate that tightened the rep's closing window is not addressed by accountability calls. The plan is directed at a number. The number is produced by a relationship. The relationship is not addressed by anything in the plan.
The Business Relationship Model™ as Management Instrument
The Business Relationship Model™ has three prior canonical applications. This article establishes a fourth — the most consequential because it operates before outcomes are determined.
Interpretation tells leadership what a number means. Consequence tracing tells leadership where a consequence originated. The management application tells leadership where to intervene before the next number is determined.
That intervention has a location. A specific relationship in the sequence the BRM describes. A relationship that can be changed before the outcome it produces is recorded.
What Relationship Management Looks Like in Practice
When leadership applies the Business Relationship Model™ as a management instrument, the operating review changes in a specific way.
Not: which number is off target?
Which relationship is producing the number that will be off target in six weeks?
That question has a time dimension the first question does not. It moves leadership's attention from the outcome that has already been recorded to the relationship that is currently determining the next outcome.
In each case, the management action precedes the number. The number records the result of management that has already happened. Leadership that waits for the number is not managing. It is confirming.
The Executive Standard
A leadership team that engages with relationships before they produce outcomes can change what the business will record.
A leadership team that engages with numbers after they are recorded can only explain what the business has already produced.
The difference between those two leadership teams is not intelligence. It is not effort. It is not the quality of the operating system. It is timing.
Numbers measure outcomes. Relationships determine them.
The Business Relationship Model™ is the instrument that tells leadership which relationships are currently determining the outcomes that have not yet been recorded.
That is where management begins.
Not in the operating review.
In the relationships that are writing next month's numbers right now.
Article 67 establishes the Business Relationship Model™ as a management instrument — its fourth canonical application — building on its prior applications as an origin framework in Article 63, an interpretive instrument in Article 65, and a consequence tracing map in Article 66. All applications are maintained as part of the proprietary framework universe at verisynhq.com/intelligence-hub.