AI made the team faster. Underneath the output, the reflex to reason a hard problem through is fading, "faster" quietly became "more expected", and it's harder to say "the AI got this wrong" out loud. None of that shows up in a velocity chart. This guide protects those three things — through team practice, not clinical support.
Haven't taken the check yet? Do that first — 14 questions, about four minutes. It scores you on the three areas below and tells you which one to fix first. Already have your result? Jump to your weakest area: Critical thinking · Sustainable pace · Psychological safety.
Three things to protect. Strong thinking that nobody dares voice is wasted; a safe team with an unmanaged pace just shares the strain out loud. Scope note: this is team practices and process — anything that needs individual care belongs with a qualified professional.
The check measures how the team works — not how anyone is doing. The engagement, in a sentence: find the weak one and reinforce it first.
The test: can people explain and defend AI-assisted work as their own reasoning? If the honest answer is "the model said so", judgement has been outsourced.
Make "explain it as your own" the standard for anything that matters — if you can't defend the reasoning, it isn't done. Add a norm that AI output is a draft to challenge, and set aside time where the team works a problem before it prompts.
The team challenges AI output for big things — extend that habit down, and name the judgement calls it should own outright. A short standing conversation about reasoning (not prompting technique) keeps the muscle in use.
Keep the "defend it as your own" bar high as deadlines press, keep naming what the team should not delegate, and watch for first-principles work quietly disappearing from the calendar.
Pace is whether the time AI frees up is spent by choice. The test: has the team actually decided what that time is for — and protected any of it?
Have the conversation the team hasn't had: what is the time AI frees up actually for? Then protect some of it. Design deep-work time into the week, and plan with the real cost of context-switching in view — not the demo-speed version.
Pace is discussed but not yet designed. Make workload a standing item in retros, protect focus time properly rather than in theory, and give the team language to push back on false urgency — most "urgent" AI-era asks aren't.
Keep reviewing workload as a team, keep deep-work time defended when demand rises, and keep separating urgent from important — that discipline erodes fastest under pressure.
Safety here is narrow and specific: can anyone say "I don't know", "this AI output is wrong", or "we're going too fast" without it costing them?
The fastest fix is how the team responds to problems: make it blameless and about the process, visibly, the next time something goes wrong. Then make "I don't know" and "this AI output looks wrong" normal things to say — model it from wherever the authority sits.
People speak up sometimes — make it reliable. Act visibly on the next "this is wrong" or "we're going too fast", so raising it is seen to be worth it, and check that it isn't only the senior voices who feel able to.
Keep acting on the hard flags, keep the blameless response under deadline pressure, and keep checking that the newest and most junior people feel as able to speak as anyone else.
Guardian AI doubles as a critical-thinking checkpoint — it asks whether a human actually thought about a prompt before it's sent. Free public beta.
If the weak area won't move — the reasoning habit keeps thinning, pace creeps back up, people still won't say "wrong" out loud — that's the point to bring Jon in on that one problem. A facilitated session with the team on how thinking, pace and candour actually play out, then the move: a working agreement, a workshop, or a change to how the team plans. Team practice only — individual support is a separate, professional matter.