Getting started
Find where the business is losing control — and decide what to fix
3 min read Updated 05 Jul 2026
Start with the two free diagnostics: the Drift Report shows where the business is quietly losing control, and Should you automate this? scores one recurring pain and tells you honestly whether the fix is software, a clearer process, or neither yet. Then run the same loop your team will: snapshot, project, check-in.
You run the business, so you feel drift as money: missed deadlines, rework, client surprises, and too much depending on you personally. What you need first is two answers — where the business is losing control, and whether each repeated pain deserves a clearer process, a standing mechanism, or software.
The quickest value is the two free diagnostics. Both take a few minutes, neither needs payment, and each ends with a scored report you can act on and share.
Take a Drift Report
The Drift Report is a wide-angle read on your whole operating standard — not one project, the way the business runs.
- From your dashboard, find the Diagnostics section and press
StartunderTake a Drift Report. (Logged out, useGet a free reportin the top navigation.) - Answer the 24 questions — four for each of six themes, from drift visibility through to system learning.
- Enter your details to unlock the full report.
You'll see your score out of 100 with a maturity band from Reactive up to
Trusted / Systemised, a six-axis chart showing where the drift is hiding,
and a practical next step. The full report is emailed to you, and the
result page includes a drift-tax calculator that puts an annual cost on
what you've just scored.
Score a recurring pain with Should you automate this?
Not every pain should become software. This diagnostic scores one recurring task and tells you honestly which fix fits.
- From the Diagnostics section, press
StartunderShould you automate this?— orScore a task — freeon its page. - Describe the recurring pain in a sentence. Every question after that is scored against it.
- Score the pain across frequency, cost, detection, process shape, and what you've already tried.
The result lands in one of four bands — from Not Worth Automating Yet
through Systemise Before Automating to
Strong Portal / Software Candidate — with the reasoning shown. Run it
once per pain; each result is stored separately.
Find the patterns with the Friction Log
Diagnostics are point-in-time; the Friction Log is
the running record. Open Friction Log in the sidebar and press
Log a friction whenever something snags. When your review comes due,
press Start review to run a Systemise Review — the same
recurrence-consequence-detectability judgement, applied to every pain
you've logged. Over a few weeks this shows you which pains actually
recur rather than which ones you remember.
Run the loop on your own work
Before rolling anything out, run the standard on one piece of work you personally carry. Your dashboard checklist — Your first control points — walks you through it:
Take a Control Discipline Snapshot— score the ten disciplines once as a private baseline.Create your first project— mission, pillars, and a score over time. See projects.Submit your first weekly check-in— the second check-in is where the trend appears.
You'll know the loop is working when a check-in tells you something a status meeting wouldn't have.
Bring the team in
Once the loop has earned its keep on your own work, scale it: invite managers and team members, give each project an owner, and read drift from Team progress instead of chasing it in person. Team features sit on team plans — see plans and access — and the rollout itself is covered in getting started as a manager.
Who can do this
Both diagnostics are public and free — no account needed to start. The snapshot, projects, check-ins and Friction Log are available to everyone on every plan, free tier included. Inviting members and the Team progress view need a team plan and are limited to the account owner and users with team permissions.
Frequently asked
Are the diagnostics really free?
How is the Drift Report different from the Control Discipline Snapshot?
The automation diagnostic told me not to automate. Is that right?
Systemise Before Automating mean the process isn't stable enough for software to help yet — a written process or a standing mechanism is the cheaper, faster fix. Retake the diagnostic once the process has settled and see if the answer changes.Can I share a result with my team?
Related guides
Log friction and run a Systemise Review
The Friction Log turns recurring operational pain into decisions. Log a snag the moment it bites — ten seconds — then, on a cadence you choose, run a short Systemise Review and decide whether each pain is worth living with, writing down, building a mechanism for, or solving with software.
Projects and the ten disciplines
Projects are where you track real work against the ten control disciplines. Create a project, set its outcome and delivery mission, then submit a short check-in on a cadence you keep — scoring each discipline 1–5 to produce a Control Index score, a named status, and a trend you can coach from.
Get set up as a manager — run the loop, then bring the team in
Team plansSet up in two stages: run the loop on your own work first — learning plan, snapshot, a real project, a weekly check-in — then invite your team from Members. Automatic reminders chase each member's learning plan so you don't have to, and Team progress opens up once their check-ins land.
Understand plans and what's included
Six plans cover solo readers to whole departments: Free for one-off diagnostics, Individual for learning and running the standard alone, and Team, Business, Scale and Advisory for shared workspaces. Compare seats, snapshot limits and team features, and learn what happens to access and data if a paid subscription lapses.