Skip to content

THE REASON STAYS WITH THE WORK

The golden thread.

From the first signal to the next decision.
Keep the evidence, the intent and the outcome connected as the work changes shape.

An uninterrupted golden thread passes through six translucent planes, representing the connection between direction, evidence, decisions, scope, releases and outcomes.
Different records. One traceable story.
FOLLOW AN EXAMPLEFictional examples · Select a record
A product decisionHarbor · External-review sharing

GOAL-12 · Product direction

A goal gives the decision a reason.

Help customer teams finish a review without moving the conversation into email.

Proposed measureTime from review request to a decision

Direction and demand meet at the decision. A goal alone does not establish customer need.

RQ-184 · Customer portal

The request stays close to its source.

A customer asks to invite an external reviewer to a specific workspace item. The request retains the interview note and the access concern behind it.

Question to resolveWhat should an external reviewer be able to see?

A request is evidence to inspect. It is not yet a commitment to build.

DEC-006 · Review sharing

Choose the work. Keep the reasoning.

Compare a limited sharing workflow with a broader guest-account feature. Record the priority, the supporting goal and the gaps that could change the choice.

Decision basisA narrow review task, with access boundaries still to confirm

Accepted links join direction and demand to the chosen work. The ranking supports judgment.

SPEC-31 · Scoped requirement

The reason travels into the requirement.

Define item-only access, an expiry boundary and clear acceptance criteria. Keep a broader guest portal outside this first scope.

Review boundaryConfirm expiry and revocation before delivery

A specification preserves the need, goals, non-goals and conditions for acceptance.

REL-003 · Planned release

Record what is planned and what shipped.

Prepare a manual release record or connect the configured delivery workflow. Keep the release status and its evidence explicit.

Current example statusPlanned · no software deployed

A planned release is not a deployment. Build Factory is an optional, separately configured path.

OUT-004 · Review cycle time

Return to the promise with evidence.

Agree the baseline, target and follow-up review. Record adoption and outcome readings when they exist, then decide what the product needs next.

Observed resultNot measured yet

The thread closes with learning. A release does not establish that the customer problem improved.

Explore this workflow in the demo
A process improvementNorthstar · Client handoff

GOAL-12 · Handoff readiness

Start with the purpose of the change.

Make client handoffs ready for the delivery team to accept, with ownership and scope clear at submission.

Proposed measureHandoff completeness and time to acceptance

The intended improvement guides the investigation. It does not predetermine the solution.

SRC-003 · Handoff evidence

Keep the finding tied to the work.

A checklist, a workbook and an owner walkthrough show how incomplete requests return to Sales. Inspect the sources and exceptions together.

Question to resolveWho confirms readiness for an exceptional handoff?

Observed work adds operational context. Sources can disagree and gaps need to remain visible.

DEC-002 · Readiness decision

Compare responses with their assumptions.

Consider a procedure change, a readiness check and a replacement tracker. Record why a focused check is the proposed starting point.

Decision basisA bounded change to an existing handoff

The decision carries its dependencies and expected value, with people accountable for the choice.

BRIEF-004 · Handoff change

Agree what the change must respect.

Require an owner and the agreed scope before queue entry. Define the exception route, acceptance conditions and ongoing owner.

Review boundaryResolve the legitimate no-owner exception

Process, system and people requirements stay connected to the decision.

REL-002 · Delivery record

Accept the work on a stated basis.

Review the agreed deliverable and its checks. Where software is involved, distinguish merge, deployment and verification.

Current example statusPrepared example · no live delivery

The evidence needed depends on the change. A procedure update and a software release have different acceptance paths.

OUT-002 · Handoff measures

Find out what changed in practice.

Establish the starting point. Review completeness, exceptions and time to acceptance after the change, with the measurement source attached.

Observed resultFollow-up evidence needed

Time released, estimated capacity value and realized cash savings mean different things.

Explore this workflow in the demo

Direction and demand inform the choice. What you learn informs the next one.

See how the work connects ↗

THE THREAD IN THE PRODUCT

Follow one reason
across three screens.

The Northstar demo keeps the source, the answer and the plan linked.
Real product screens, fictional data.

  1. ProcessScout / TransformReal product · fictional data
    The Sources view of a fictional project: three files, each with the findings drawn from it

    01 · The source

    A walkthrough, checklist and records, each with its findings.

  2. ProcessScout / TransformReal product · fictional data
    Ask Sarah answers why a fictional handoff is delayed and cites the September handoff records

    02 · The cited answer

    Ask Sarah explains the delay and links the record behind it.

  3. ProcessScout / TransformReal product · fictional data
    A fictional blueprint turns the chosen readiness check into waves with named owners

    03 · The plan

    The chosen change, with owners and the reason it was chosen.

Follow it in the demo ↗

A CONNECTION YOU CAN EXPLAIN

The line is only useful
if you can follow it.

A source you can open.

Keep the original request, evidence and context close to the interpretation. Distinguish what the source says from what the team concludes.

A decision you can revisit.

Preserve goals, trade-offs, assumptions and accepted relationships. A later reviewer should be able to understand why this work was chosen.

An outcome you can question.

Separate a target from an observed result. Missing measurements remain a reason to investigate, with a person and a review point to agree.

PROCESS INTELLIGENCE

Start with the work.

Understand the process, the evidence and the change worth making.

Explore Process intelligence ↗
PRODUCT MANAGEMENT

Start with the product.

Connect customer needs, direction, planned work and the result.

Explore Product management ↗
Product view

ProcessScout interactive demo · Fictional Northstar data