YOUR CHOICE, NOT OURS

Useful measurement. Only with permission.

We use a necessary preference cookie to remember your choice. Google Analytics and PostHog stay off unless you allow analytics. Read the privacy and cookie notice.

Read the full launch guide

/ COMPANION CONTROL ROOM · 30 DAYS

Launch.
Observe.
Decide.

Four review points. One owner. Evidence before opinion.

/ HOW TO USE IT

Do not fill the board for ceremony.

At each review point, record what happened, attach the evidence, name the owner, and make the decision. “Monitor” is not a decision unless it includes the signal, threshold, and next review date.

00DAY 0

Prove the live system

DECISIONSafe to invite traffic?
  1. Confirm HTTPS, canonical domain, www and deployment redirects.
  2. Complete every priority journey on mobile and desktop.
  3. Verify consent behavior, booking confirmation, CRM entry, calendar event, and alerts.
  4. Check titles, descriptions, social preview, favicon, sitemap, robots, and error states.
EVIDENCE TO KEEP

A dated launch record with screenshots or links, a successful test lead ID, named owners, and no unresolved blocking defect.

01DAYS 1–7

Separate defects from behavior

DECISIONWhat must be repaired first?
  1. Remove or label internal and test traffic.
  2. Review failed requests, form abandonment, broken links, device issues, and consent rates.
  3. Record the initial Core Web Vitals and accessibility findings by template.
  4. Inspect a small set of sessions only where consent and policy allow.
EVIDENCE TO KEEP

A defect list ranked by journey impact, not visual preference, with an owner and due date for every blocking item.

02DAYS 8–14

Understand discovery quality

DECISIONAre the right questions reaching us?
  1. Review Search Console impressions, queries, indexed pages, and excluded URLs.
  2. Compare source quality in analytics with landing-page behavior and enquiry language.
  3. Check whether priority pages have descriptive internal links and distinct central questions.
  4. Record evidence or proof visitors appear to need but cannot yet find.
EVIDENCE TO KEEP

A short discovery brief: promising queries, weak or missing pages, poor-fit traffic, and the next answer worth publishing.

03DAYS 15–30

Ship one measured improvement

DECISIONWhat earns the next cycle?
  1. Choose one change tied to an observed constraint and state the hypothesis.
  2. Define the event, CRM outcome, or search signal that would support the decision.
  3. Ship the smallest coherent improvement and annotate the release date.
  4. Review after an appropriate window; continue, revise, or stop.
EVIDENCE TO KEEP

One decision record connecting observation → hypothesis → change → result → next action.

/ ONE MEASUREMENT CHAIN

Track the signal that answers the decision.

LayerQuestionExample evidence
Availability

Priority pages return the intended status and load consistently.

Uptime, failed requests, broken links
Discovery

Search and referral systems can find and understand canonical pages.

Indexed pages, impressions, queries, referring URLs
Attention

Relevant visitors reach and continue through priority pages.

Qualified sessions, engaged journeys, product-page depth
Intent

Visitors begin a meaningful action.

Booking starts, email actions, product selections
Outcome

The action becomes a useful business conversation.

Completed bookings, qualified leads, opportunities
Trust

People can use the journey safely and with control.

Consent choices, accessibility defects, security findings
/ MINIMUM DECISION RECORD

Observation → hypothesis → change → result → next move.

If the team cannot write those five lines, it has activity but not an improvement loop.

Return to the detailed guide Build the operating system with dotSuper