The discipline, written down Book a study →
IV.
MMXXVI
Sheet four

Four subsystems

Three of them produce something. The fourth is what makes the other three correctable. Each is specified, measured and owned separately, because a fault in one looks identical to a fault in another until there is somewhere between them to take a reading.

Specification

One sheet per subsystem

Three readings each. Twelve in total, which is the whole diagnostic.

RefSubsystemSpecification
01

Demand

Attention created on purpose

Outbound, paid distribution, content placement, events, and reactivation of the contact database the company already owns and stopped using two years ago.

Measured on
  • Qualified contacts created per period, against the figure in the specification
  • Cost per qualified contact, split by source rather than averaged
  • The share produced from owned data against the share bought
Common fault. Volume gets bought before the conversion subsystem can carry it. The extra contacts arrive, sit unworked, and expire. The programme then reads as a demand failure when the fault was downstream all along.
02

Answers

Attention recovered

What the market finds when it goes looking on its own. Search results, and the generated answers that increasingly sit in front of them. This subsystem exists because attention created and never recovered is attention given to whoever ranks.

Measured on
  • Share of the target question set where the brand appears in a generated answer
  • Coverage: the questions buyers actually ask that have a page built to answer them
  • Crawl and render integrity on the pages carrying those answers
Common fault. Pages written to rank rather than to answer. They get retrieved by the engine and then not cited, which reads as a content quality problem and is almost always a structure problem. A separate and newer fault is a content delivery network quietly refusing the crawler by default.
03

Conversion

Interest into pipeline

Everything between an interested person and a qualified opportunity. Site, offer, form, routing, the speed of the first human reply, and the follow-up sequence that either exists or does not.

Measured on
  • The rate at each junction, from visit to enquiry to qualified opportunity
  • Time from enquiry submitted to first human reply
  • Leak rate at routing and at follow-up, measured from records rather than from intent
Common fault. A form that submits successfully into a routing rule that drops. Nothing errors, so nothing is investigated, and the quarter closes before anybody asks where the enquiries went.
04

Measurement

The instrumentation

The readings that make the other three correctable. Tracking, the data model, the definitions behind every field, attribution, and the report somebody actually reads.

Measured on
  • The share of junctions with a proven test event rather than a configured one
  • Agreement between the platform figure and the recorded commercial outcome
  • Time from an event happening to it appearing in the report
Common fault. Instruments installed and never proven. The first fault is then discovered by a client asking where their enquiries went, which is the worst possible moment to find out.
Plate IV  ·  Capital and entablature, measured  ·  Public domain
Why both

Demand and answers fail in opposite directions

Run either one alone for long enough and it produces something that looks like progress and does not compound.

A demand programme with no answer layer creates attention that cannot be recovered. Somebody reads the post, keeps the idea, goes looking three weeks later, and finds a competitor's page inside the answer. The spend produced the interest and handed it over.

An answer layer with no demand programme gets cited on questions nobody is asking yet. Coverage improves, citations appear, and the pipeline does not change, because being the answer to an unasked question is a position rather than a result.

Built together, the demand programme creates the question and the answer layer catches it coming back. Neither one is worth running without the other, which is the whole reason they are specified as separate subsystems and measured apart.

Failure one

Demand without answers

Somebody reads the post, keeps the idea, goes looking three weeks later, and finds a competitor's page inside the answer. The spend produced the interest and handed it over.

Failure two

Answers without demand

Coverage improves, citations appear, and the pipeline does not change, because being the answer to an unasked question is a position rather than a result.

Next

Where automation belongs in all four.

Six lifecycle stages, the two that get worse when a machine is left alone with them, and the four layers of a stack.