Guided evaluation · Step 4 of 4

Starting brief

Turn the evidence into a five-minute starting brief without recording approval, authorizing a pilot, or creating a live effect.

12-minute pathExit guided evaluation

Earlier steps show sequence, not saved completion. Each proof resets on refresh, and this path creates no live effect.

Back to the product preview

Phase 2 Decision Room · browser-only

The demo is ready. The next move is six real decisions.

This room connects each unresolved Phoenix decision to evidence Marci can review now. It records no answer, assumes no approval, and authorizes no pilot or live effect.

No form submission. Review, copy, and respond through a channel you already trust. Do not send credentials, card data, or broad raw exports.

Current handoff

From product proof to pilot evidence

Synthetic product evidenceReady to review

Eight direct capability views and the connected role story are live.

Phoenix decisions recorded0 of 6

No Phoenix answer or approval is inferred from this presentation.

Real-client pilotNot authorized

Real clients, money, providers, migration, and outbound effects remain gated.

Technical readiness is not Phoenix approval.

Five-minute starting brief

Start with four answers—not all six gates.

Choose a first journey, the people needed, the riskiest unknown, and what evidence is available. The brief updates only in this browser tab and remains incomplete by design.

0 of 4starter prompts answered

01Which journey should the team examine first?
02Who else needs to be in the decision?

Marci Scott is already named as the primary coaching lead. Add any roles needed for the first review.

03What is the highest-risk unknown?
04How ready is the safest useful evidence?

Local draft

Nothing is sent or saved. Reloading clears these selections.

No form, account, cookie, local storage, database write, analytics event, or submission endpoint is used.

Six validation gates

Decide what becomes real—and what stays out.

Each gate names the question, accountable participants, safe evidence to bring, and the bounded outcome needed before pilot design can advance.

01
Awaiting validation

Choose the first real journey

Which one real client journey should PTOS validate first—and which variants must stay out of the first pilot?

A thin, real workflow is safer to validate than approving a broad feature list.

Decision partners
Marci + a representative coaching/operations owner
Gate outcome
One bounded pilot journey, with every excluded variant named.

Bring the safe minimum

  • One normal client journey with names and private details removed
  • One stalled or exception journey
  • One cancellation or offboarding journey
02
Awaiting validation

Name the people and promises

Who owns each handoff, exception, override, client message, and coverage decision?

Software cannot safely infer accountability, coverage, or the service level clients are promised.

Decision partners
Marci + staff/support owners
Gate outcome
A named owner, backup, authority boundary, and response expectation for every pilot handoff.

Bring the safe minimum

  • Who owns each handoff and client communication
  • Who covers absence or workload overflow
  • Who may resolve exceptions or approve overrides
03
Awaiting validation

Approve policy and data boundaries

What may PTOS collect, show, retain, send, or change—and who approves each high-impact boundary?

Health-adjacent, payment, coaching, community, and progress data need explicit rules before real use.

Decision partners
Marci + applicable policy/business owners
Gate outcome
An allowed-data and policy map with named owners, unresolved blockers, and review dates.

Bring the safe minimum

  • Approved agreement, payment, health/nutrition, media, privacy, and retention rules
  • Identity-verification, export, correction, deletion, and incident procedures
  • The accountable legal, financial, privacy, and health-adjacent decision owners
04
Awaiting validation

Approve what clients will see

Which brand assets, program names, coaching voice, media, and content are current and licensed for production?

The current direction is intentionally provisional; production must use owned, current, accessible material.

Decision partners
Marci + brand/content rights owners
Gate outcome
An approved, licensed brand/content pack with replaceable production tokens and copy.

Bring the safe minimum

  • Current approved logo and source assets
  • Exact colors, fonts, program names, audience, and voice examples
  • Content ownership, licenses, captions, and participant/media releases
05
Awaiting validation

Choose providers and the transition boundary

Which systems remain, integrate, or exit—and what is the smallest reversible data transition worth testing?

Feature resemblance does not prove export quality, field compatibility, account ownership, or a safe cutover.

Decision partners
Account/data owners + technical/operator owner
Gate outcome
A source-of-truth map and minimum dry-run migration with reconciliation and rollback criteria.

Bring the safe minimum

  • System and provider inventory with owner, purpose, contract, export, and exit terms
  • Redacted schemas or synthetic samples—never credentials or broad raw exports
  • Which system stays authoritative during a reversible parallel period
06
Awaiting validation

Define the pilot decision

What measurable outcome would justify continuing—and what safety or service failure would pause the pilot?

A convincing demo is not a result; the pilot must measure value and safety against an agreed baseline.

Decision partners
Marci + all acceptance/support owners
Gate outcome
A consented pilot charter with measures, stop rules, support, recovery, export, and rollback ownership.

Bring the safe minimum

  • Current baseline for coach time, turnaround, client friction, and missed handoffs
  • A small consented cohort, support owner, manual fallback, and incident path
  • Numeric success, pause, and stop thresholds recorded before any real data enters

Full six-gate worksheet

Continue only as far as the evidence allows.

The starting brief is enough to schedule a focused review. Use this longer outline only when the applicable decision owners are ready to record evidence gate by gate.

  • Replace bracketed prompts with an answer, owner, source, or “not decided.”
  • Use synthetic, blank, or explicitly redacted samples.
  • Send no password, token, private key, card data, or broad production export.

Nothing is sent or saved from this page.

The honest boundary

Nothing here turns presentation evidence into production approval.

Real Phoenix workflow, content, policy, providers, migration, money, client data, and pilot use remain gated until their accountable owners record the decision and evidence.

Replay the product storyReturn to the handoff