A project coordinator has a client email open and a half-finished reply. She wonders whether she can paste the thread into the AI tool to tidy her draft. It contains a customer name and a price. Is that allowed? She is not sure, so she opens the policy document, scrolls for two minutes, finds nothing specific, and messages a colleague, who says probably fine. She decides to write the reply by hand, and the hour that follows is a little slower than it needed to be.
Nothing dramatic happened in that scene. No data leaked, no rule was broken, no tool failed. A single small question simply had no ready answer, so it cost a few minutes, a message and some low-level worry. That is what a missing default looks like.
This matters because Stay Simple is about removing decisions we should not have to make. The same question, asked a dozen times a week across a team, is a decision tax that a single plain default could remove.
------------- Context -------------
Most workplaces have by now told people that AI is welcome. Culture Amp's 2026 AI at Work Benchmark, covering around 112,000 employees, found that 85 percent say they are encouraged to experiment, and 86 percent say they understand the risks. On paper, that sounds like a confident, well-informed workforce.
But a separate 2026 survey of US workers found that 44 percent say their company has no clear AI policy, or they are not sure whether one exists. Encouraged, informed and unsure all at once. The gap between those two pictures is where the daily friction lives.
When guidance is general, every specific situation has to be interpreted. Is this email too sensitive? Is this spreadsheet client data? Is a summary of a meeting recording acceptable? Each question is small, but each one needs a judgement call from someone who would rather be doing the work.
We usually respond to this by writing a longer policy. That tends to make things harder, not simpler. A twelve-page document answers every question in principle and none at the moment someone needs it. People stop reading, then stop asking, then guess.
The simpler framing is a default answer per type of task. Not a rule for everything, but a pre-decided yes, no or ask-first for the dozen situations that come up most. That is a short path in place of fifty options, and it is the heart of Stay Simple.
------------- A Policy Nobody Can Find Is a Decision Nobody Has Made -------------
A policy is only as useful as the speed at which it answers a question. If finding the answer takes longer than doing the task, people will skip the lookup. We see this when teams say they have guidance but still rely on asking each other in chat.
Imagine a team of eight with a good, careful AI policy that runs to ten pages. Each person meets a grey area about three times a week. Checking the document takes about four minutes, and about half the time it does not answer the question, so they ask a colleague, which costs another ten minutes between the two of them. Across the team, that is roughly three hours a week spent on a question that already has a sensible answer somewhere.
The cost is not only minutes. Each grey area is a small decision, and decisions wear us down. By the afternoon, the coordinator in our opening scene has made forty tiny calls, and whether she uses AI on the next email is one more she would happily give away.
What simplifies this is not more detail but fewer decision points. If the answer to "can I use AI to tidy a client email with names removed?" is a plain yes, no one needs to look anything up. Three minutes of checking becomes zero.
Stay Simple is scored on friction removed. Here, ten steps become one: see the situation, read the default, act.
------------- A Default Is a Decision Made Once for Everyone -------------
The power of a default is that it moves the thinking to a moment when we are calm, rather than leaving it for a moment when we are busy. A person deciding at four o'clock on a Thursday is a different decision maker from a team deciding together on a quiet Tuesday.
Consider how this works in a small agency. At a short meeting, the team agrees on a handful of default answers. Public information and our own drafts: use AI freely. Client material with names and figures removed: yes. Client material as it stands: ask first. Anything covered by a contract or involving health or money details: no. That is four lines.
After that meeting, the agency has swapped a vague, general attitude for four decisions made in advance. Someone new joining on Monday can learn them in two minutes. Someone returning from leave can find them without asking.
It also means fewer awkward moments. People who are cautious by nature stop holding back out of uncertainty, because the line is visible. People who are keen stop pushing at the edges, because the edges are written down.
The simplicity gain is concrete. Before, every grey-area task meant a lookup, a guess or a message. After, it means reading one line. The number of decisions per task falls from three to one.
------------- Defaults Work Best When They Are Few and Written in Everyday Words -------------
There is a temptation to turn defaults into a comprehensive matrix, with columns for every tool and rows for every data type. That is the twelve-page policy in a new costume. The value of a default lies in how little there is to remember.
We have found that around six to eight defaults cover most real situations for a small team. More than that and people begin to forget which is which. Fewer and the grey areas return. The test is whether a colleague could recite them from memory after a week.
Plain wording matters just as much. "Client names and prices removed: yes" is something a person can apply in a few seconds. "Personally identifiable and commercially sensitive information is subject to review" requires translation, and translation takes time and nerve.
A freelance bookkeeper working alone illustrates the point. She keeps a note of five lines on her screen: public and general questions, yes; her own notes and drafts, yes; client figures with names removed, yes; client files as received, never; anything unsure, wait and ask her accountant. In place of an uneasy hesitation fifteen times a week, she now has a two-second glance.
Fifteen hesitations of a minute each is fifteen minutes. Over a year, that is more than twelve hours of small pauses gone, plus the quiet confidence of knowing where the line sits.
------------- A Default Is Also How Trust Becomes Visible -------------
The most overlooked benefit of defaults is what they do for confidence. People often avoid AI not because they dislike it but because they cannot tell whether using it is safe. A clear default turns a worry into a boundary, and a boundary is far easier to live with than a worry.
It also helps those who lead teams. A manager with defaults in place does not have to repeat the same answer each time a person asks. The answer is already out there. She can spend her attention on the genuinely unusual cases, which are the ones that need a person to think.
And defaults can change. They should. When a new tool arrives or a client asks for something different, the team revisits one line, not a whole policy. Changing a single line is a small, calm job. Rewriting a policy is a project nobody starts.
The simplicity outcome here is fewer exceptions to track. Before, every new situation produced a fresh debate. After, it produces a single edit, usually agreed in a five-minute chat once a month.
------------- Practical Moves -------------
First, collect the real questions. For one week, note every moment you or your team hesitate over whether to use AI for something. Ten to fifteen examples is plenty, and the list will show which situations come up most.
Second, sort those examples into three buckets: yes, ask first, and no. Resist adding more buckets, because three is enough to cover nearly everything and easy enough to remember without looking.
Third, write six to eight default lines in everyday words, each short enough to fit on one line of a note. Replace anything that sounds like a legal clause with the version you would say out loud.
Fourth, put the lines where the work happens: pinned in the team chat, on the first page of a shared document, or stuck beside a screen. A default that takes a search to find is not yet a default.
Fifth, set a thirty-minute review once a month. Change one line at a time, delete any that nobody used, and add a line only when the same question has come up three times.
------------- Reflection -------------
The coordinator in our opening scene was not confused about AI. She was missing a single sentence. Across a workforce that is encouraged to experiment but often unsure of the rules, those missing sentences add up to a great deal of hesitation.
That is why a default answer matters so much for keeping things simple. It takes a decision that was being made fresh, by many people, many times, and makes it once. The friction does not shrink a little. It disappears for every case the default covers.
In the end, that is the kind of AI shift worth paying attention to. Not more tools, more training or more policy pages, but fewer moments where someone has to stop and wonder. When the answer is already there, people get on with the work.
Where in your week do you pause to ask yourself whether AI is allowed for something?
Which three situations come up so often that they deserve a pre-decided answer?
If you had to fit your whole guidance on one note, what would the first line say?