Skip to content

Personas & Tracks

Different people in the same company need different things from the program. We name three personas and map the modules each one needs. A small company may have one person wearing all three hats; a larger one runs the tracks in parallel.

The three personas

1. Leader · decides, funds, champions

  • Who: owner, CEO, GM, department head.
  • Cares about: outcome, ROI, risk, competitive position, "what does this mean for us."
  • Does NOT want: to learn to prompt at a keyboard for an hour.
  • Core modules: M01, M02, M11 (policy), present at M12 kickoff.
  • Success looks like: sponsors the program, signs the security policy, approves the OS deployment.

2. Operator · runs the business day to day

  • Who: ops, sales, marketing, finance, admin — the people doing the recurring work.
  • Cares about: doing their actual job faster and better today.
  • Core modules: M03, M04, M05, M06, M07.
  • Success looks like: uses Claude weekly, has prompts saved, has at least one task they no longer do by hand.

3. Builder · makes the technical things work

  • Who: the technical 1–2 people, an IT lead, a developer — or us, on the company's behalf.
  • Cares about: wiring tools together, automating, deploying, security.
  • Core modules: M06, M07, M08, M09, M10, M11, M12.
  • Success looks like: automations live, data connected, cloud running, OS deployed.

Track map

Module Leader Operator Builder
M01 Awareness
M02 Maturity
M03 LLMs & Models
M04 Prompting
M05 Claude Ecosystem
M06 Claude Code CLI
M07 Skills & MCP
M08 Agents & Automations
M09 Data Integration
M10 Cloud Setup
M11 Security & Sovereignty
M12 Deploy the OS

● = core for this persona ○ = recommended / optional

How tracks run

  • Leadership track is short and front-loaded (Stage A) plus the policy and OS bookends. A few hours total.
  • Operator track is the bulk of Stage B–C — the literacy and tools that change daily work.
  • Builder track carries Stages C–F and is where the OS prerequisites get assembled. Often this is us pairing with the company's one technical person, or doing it for them.

If the company has no builder

Common for small companies. Two options, both fine: 1. We are the builder — Analytica runs the builder track and the M12 deployment as a service. 2. Grow one — a motivated operator takes the builder track; we support. Slower, more sovereign.