A Scout skill that catches the right moment to teach — so learning happens inside the work, not after it.
01 — Context
Courses and reminders assume you'll circle back later. But the best time to learn something is right when it's in your way, not next Monday. So I asked a simple question: what if learning could just show up, exactly when the work calls for it?
So what
The gap isn't more content. It's timing, and permission to ignore it.
02 — Framework
Timing has to be earned by a real signal. The resource has to be one thing, never a list. The person stays in control the whole time. And what it's allowed to read stays visible and limited. Each rule stops one specific way this goes wrong.
So what
Signal-led timing is what makes the other three rules feel earned instead of annoying.
03 — Proof
Someone asks how to set up a conditional approval step, the meeting moves on, and normally that's the end of it. Scout notices the question in the transcript, waits until the meeting is over, and comes back with exactly one short resource for that exact gap.
Open this scenario full screen ↗So what
The moment was already there. It just needed someone to catch it.
03 — Proof
A kickoff lands on the calendar, and the agenda hints at unfamiliar ground. Scout picks up on that timing and queues one short primer early enough to actually read it, not the morning it's due.
Open this scenario full screen ↗So what
Earned timing is the whole difference between a helpful nudge and a notification you swipe away.
03 — Proof
A six-week project wraps, and Scout opens a quiet, private session with one question: what was hardest to navigate. No form, no scoring, just a moment to notice what you actually learned.
Open this scenario full screen ↗So what
Three different signals, one shape: earn the timing, then get out of the way.
04 — Risk
Every rule from the framework exists because skipping it breaks something specific. Read access without limits turns into monitoring. Timing without user control turns into nagging. These aren't nice-to-haves — they're what keeps this from becoming the workplace tool everyone already resents.
So what
Boundaries aren't a limit on the idea. They're the reason anyone trusts it enough to use it.
05 — Craft
Same approach every time: write the argument in plain prose first, then let it become a prototype. If an idea couldn't survive being written down clearly, it wasn't going to survive as a screen.
So what
Writing it first meant the prototype was never left guessing what the idea actually meant.
06 — Reflection
It was deciding when to stay quiet. Every scenario started out as “we could nudge here too,” and the real work was cutting that list down to the few moments that actually earned it. Restraint turned out to be the whole feature.