Personal Operating SystemPurpose to practice
Wave 0A remote pilot

Build, use, and test the journey.

We are testing the site, not you. Build one useful layer at a time, step away, return with evidence, and tell us where the experience needs to improve.

Four milestonesBuild in useful layers
5–6 hoursTotal working time
2–3 weeksSpaced sessions and field test
First session · 30–40 minutes

Orient, start, and create a first useful draft

  1. Open your invitation or the pilot website, complete any verification step, and sign in with the invited email address.
  2. Watch or read the first-visit orientation. It shows how the website supports BIGHT and the Who, What, Where, When, Why, and How; coach-guided reflection; human review; BUILD milestones; practical outputs; private decision support; and Review, Reflect, Refine.
  3. Explore the opening page and begin your own Personal Operating System in the way that seems most natural. After beginning, you may review Jordan's sample Personal Operating System without copying Jordan's information.
  4. You may complete the private 60-second check, but do not report your answers.
  5. Use deliberately non-sensitive test information to answer one focused coach prompt. Continue until the coach prepares a draft suggestion.
  6. Review the suggestion. Choose Keep talking, Discard, or Apply and edit based on what genuinely fits. Nothing changes until you choose what to apply.
  7. Make one small direct edit, ask the coach to review it, and then try undoing one change.
  8. When Milestone 1 becomes ready, complete its self-check, record your next session, and add that session to your calendar.
BUILD journey · spaced sessions

Complete the four milestones without rushing.

  1. Milestone 1 — Purpose captured: draft a working purpose, test it against one real choice, then wait at least 24 hours before the next BUILD session.
  2. Milestone 2 — Strategic foundation connected: connect purpose, values, identities, and vision in two 40–50 minute sessions. Leave at least 48 hours between the sessions and before the next milestone.
  3. Milestone 3 — Goals and habits connected: build one practical goal-and-habit pair in two 40–50 minute sessions. Leave at least 48 hours between the sessions, then try the pair for at least 72 hours before continuing.
  4. Milestone 4 — Initial end-to-end draft: complete the Time and Focus layer in two 40–50 minute sessions. Leave at least 24 hours between the sessions; 48 hours is preferred when circumstances allow.
  5. After each milestone, review only the next ready milestone and schedule the next return. Use Google Calendar, the Outlook or desktop calendar (.ics) option, or the secondary Microsoft 365 web calendar link.
Email reminders are not active in this pilot. Record every return date and use a calendar or your own reminder system.
USE · seven-day field test

Try the draft in real conditions, then refine.

  1. After Milestone 4, use the Personal Operating System Overview, complete planning details, or reference card for seven days.
  2. Notice what helps, what is ignored, what creates friction, and what is hard to read. Milestone 4 means ready to test—not finished, aligned, or proven.
  3. Try the private decision check on one practical choice. It does not score options, decide for you, save a result, or change your Personal Operating System.
  4. Return in a new browser session and confirm that the correct content and place are restored.
  5. Open the Overview, complete planning details, reference card, and Export backup. Use only the backup from your own authorized test account if you were assigned a restoration check.
  6. Complete the content-free evaluation below. Schedule the first quarterly Review, Reflect, Refine cycle separately from the field-test debrief. Identity and Habit reviews are quarterly; ordinary weekly planning remains under Time and Focus.
Short evaluation

Tell us what the experience was like.

Use 1 for strongly disagree and 5 for strongly agree when a rating is requested. Evaluate the experience without submitting your Personal Operating System text or coach conversation.

  1. Purpose comprehension

    In one sentence, what do you think this website is helping a user create and use?

    Do not include any of your Personal Operating System content.

  2. Orientation

    Did the first-visit orientation clarify BIGHT, BUILD, USE, and Review, Reflect, Refine?

    Yes / Partly / No. What remained unclear?

  3. Starting path

    Where did you expect to begin, and how easy was it to find that starting point?

    Rate 1–5, then add a short explanation.

  4. Account access

    Creating the account, signing in, signing out, and returning were clear and dependable.

    Rate 1–5. If something failed, name the step, but never share your credentials.

  5. Coach-to-draft transaction

    Before applying anything, did you understand that the coach had not changed your Personal Operating System?

    Yes / Partly / No. What made that clear or unclear?

  6. Control and trust

    I felt able to keep talking, discard, apply, edit, and undo without worrying that the coach would silently replace my work.

    Rate 1–5. What caused confidence or concern?

  7. Save and resume

    When I returned, the correct content and place were restored.

    Yes / Partly / No. What appeared missing or unexpected?

  8. BIGHT continuity

    Did earlier approved elements remain connected as you moved from beliefs and identities through goals, habits, and the way you use time and focus?

    Yes / Partly / No / Did not progress far enough. Explain without sharing content.

  9. BUILD pacing

    Did the four milestones and the spaced return sessions make the work feel manageable?

    Yes / Partly / No. Note which milestone or spacing instruction was clear or confusing.

  10. Calendar and reminders

    Could you record the next session and use Google Calendar, the Outlook or desktop calendar (.ics) option, or the Microsoft 365 web calendar link?

    Yes / Partly / No. Was it clear that email reminders are not active in this pilot?

  11. Practical use and outputs

    Which Overview, complete-details, reference-card, backup, or private-decision-check option was most useful?

    Describe the kind of utility, not your private content.

  12. Priority improvement

    What was the single most confusing, frustrating, or unnecessary part of the experience? Was there any point when you considered stopping?

    Describe the interaction, not your private content.
Content-free issue report

Describe the interaction, not your content.

Use these fields when you report a problem to your pilot coordinator.

Page or feature
Where did the problem occur?
Action
What did you click or attempt?
Expected result
What did you expect to happen?
Actual result
What happened instead?
Test environment
Device, browser, and approximate time
Ability to continue
Could you continue? Yes / No
Optional screenshot
Attach only a fully redacted image if it would help.
Never include purpose statements, values, coach transcripts, private-check answers, passwords, credentials, or screenshots containing personal draft content.
Thank you

Your feedback will shape the next pilot.

Please send your content-free evaluation and any issue reports through the channel provided by your pilot coordinator.

Return to the Personal Operating System home page