01 — What this is
A diagnostic with a fixed finish line
You bring a seam that feels wrong — brand, web, intake, handoffs between teams. Sightline names what the system was supposed to do, gathers evidence, and returns a written assessment you can act on.
The deliverable is an exposure map: where promises might fail, what to fix first, and what to watch. It is bounded — we do not expand into unlimited discovery or strategy re-litigation.
BDR-0005 · BDR-003002 — What you get
The deliverable — and two public samples
Every engagement ends in a structured document. These sections appear in the artifact (exact depth varies by seam):
- Observations — what we saw in artifacts and behavior, before naming a cause
- Hypotheses — competing explanations for the same seam (when evidence supports more than one)
- Evidence — what supports or undermines each hypothesis
- Assessment (bounded) — best read given current evidence; not final truth
- Exposure surface — where promises are at risk, tiered Urgent / Watch / Stable
- Recommended sequence — fix-first order and what to monitor — not a build proposal by default
Sample A
Convergent read
Boone Supported Living — Maintenance Request form failing silently for residents; convergent read when evidence points one way.
Sample B
Competing hypotheses
Brand-to-web seam — bounded assessment without forcing a single story (MCA illustrative).
03 — What this is not
Explicit scope exclusions
Clarity up front prevents the wrong engagement.
- ✕ Strategy audit — we assess whether the system kept its promises, not whether your original strategy was correct
- ✕ Unlimited discovery — scope is fixed; expansion requires a new conversation
- ✕ Build included by default — implementation is a separate engagement; the diagnostic stands on its own
- ✕ Bug hunt only — technical defects may appear, but the map includes seams, handoffs, and interpretation gaps
04 — The chain
How Sightline reads a seam
Methodology lives here — not on a separate framework page. Each step has a job; we do not skip to fixes before assessment.
- Observation Describe artifacts and behavior — not why yet.
- Hypothesis Name competing explanations and what we'd expect if each were true.
- Evidence Gather what supports or undermines each hypothesis — separately.
- Assessment State the best read given current evidence — bounded, not final truth.
- Intervention Address exposure in priority order — build may follow, but does not collapse the assessment.
05 — Who it's for
Organizations that sense disconnect
You do not need to name the seam perfectly. These entry points from the homepage inquiry map to common Sightline fits:
- A Trust Compression — legitimate work, brand not carrying it
- B Signal Loss — something slips between strategy and execution
- C Complexity Drag — too much, no source of truth
- D Not sure yet — something is off; that's a valid starting point
Option E on the inquiry form names Sightline directly — bounded assessment, not a redesign.
BDR-0006 · BDR-003006 — Fixed scope sketch
Timeline and boundaries
Placeholder range — conversation sets exact scope before work begins. No public pricing; fit matters more than a rate card.
Typical timeline
2–3 weeks
From kickoff to facilitated readout
In scope
- Scoped artifact review and stakeholder touchpoints as agreed
- Written assessment + exposure surface
- Facilitated readout (live walkthrough)
- Recommended sequence — not a build SOW
Out of scope
- Open-ended discovery without a finish line
- Implementation / redesign unless separately engaged
- Strategy correctness review
07 — Start
Conversation sets scope
If a bounded diagnostic sounds like the right next step, use the homepage inquiry — pick the force that sounds closest, option E for Sightline directly, or email with the subject below.
BDR-0030