AI Guides › Getting Started
By Nigel Guy · 2 min read
Most onboarding advice arrives as a flat list — set this up, try that, remember the other thing — with no sense of what order actually helps. Done all at once on day one, half of it doesn't stick because there's no context yet for why it matters. Spread across a week, in the right order, each step makes the next one more useful.
The rule: the order matters more than the list — each day's step is designed to make the next day's step land better, not just to fill seven days with tasks.
| Day | Focus | Why it goes here |
|---|---|---|
| 1 | Tell it about yourself, briefly, in its own short conversation | Everything else benefits from this being in place first |
| 2 | Run one low-stakes, checkable practice task | You need a feel for what a good answer looks like before trusting a real one |
| 3 | Do one real, but reversible, task — something you can check against a draft you already have | This is where judgement actually starts forming |
| 4 | Correct it once, deliberately, on something it got slightly wrong | Practising the correction loop matters as much as the initial ask |
| 5 | Start one Project for something you'll come back to, and put the standing context in it | By now you know what "standing context" for your work actually looks like |
| 6 | Connect exactly one tool you'll genuinely keep using | Wait until you have a real use case before granting any access |
| 7 | Review what it's kept in memory, and what settings you've actually used | A short audit catches anything that drifted, before it compounds over week two |
None of these days need more than fifteen or twenty minutes on top of whatever real work you're already doing — this isn't a curriculum that competes with your actual job for time. Day 3 isn't "your biggest task of the month"; day 6 isn't "connect everything you have access to." Each day is deliberately small.
Skip compressing this into one long session on day one — the sequencing is the actual point, and doing it all at once removes the benefit of each step informing the next. Skip adding a second connected tool or a second project before the week's out; one of each is enough to learn from properly.