Put AI between you and the task
The most useful mental model we have found for working with AI every day: stop treating it as a tool you pick up, and start treating it as a layer the work passes through.
Most people treat AI like a tool in a drawer. You have a task, you decide whether this is an AI-shaped task, and if it is, you go get the tool, use it, and put it back. That framing quietly caps how much it can help, because you only reach for it on the tasks you have already pre-judged as suitable.
We work differently, and it is the single habit we most want to pass on to the teams we work with. We put AI between us and the task. Not beside it. Between it.
A layer, not a tool
When AI is a layer the work passes through, the default flips. The question is no longer “is this an AI task?” It is “what does this task look like once it has gone through the layer first?” Drafting a document starts from a draft. Debugging starts from a set of hypotheses. Reading a long thread starts from a summary with the decision already pulled out. Planning starts from a plan you can argue with.
You are still the one who decides, edits, rejects, and ships. But you start every task one full step in, on the editing side of the work rather than the blank-page side.
Why the default matters
Defaults are quiet but relentless. If using AI requires a decision each time, you will skip it on exactly the tasks where it felt like overkill, which are often the small frequent ones where the time actually adds up. If passing the work through AI is the default, you capture all of those without thinking about it.
This is also why editor autocomplete, useful as it is, undersells the idea. It puts AI inside one task. The layer goes around all of them: the email, the config, the query, the review, the retro, the roadmap.
The discipline it requires
A layer you pass everything through needs judgment at the output, not blind acceptance. The skill that matters shifts from “can you do the task” to “can you quickly tell a good result from a confident wrong one.” That is a learnable skill, and building it on a team is most of what real adoption is.
We do this on nearly everything, every day. It is not a productivity hack we read about. It is how we work, and it is the practice we bring into the rooms we are invited into.
By Activated
Want this applied to your delivery, not just discussed?
Book a working session