🪡 Pride Is Becoming the Quiet Reason We Skip AI
A senior copywriter opens a chat window, types the first line of a brief, and closes it again. Later, her manager asks whether she has tried the new tool. She says she has not got round to it yet. In truth she has tried it twice, and both times the draft sounded like someone she did not want to be.
That small scene is more common than it looks. In a 2026 survey from Omni Calculator, about one in four workers (26 percent) admitted to avoiding or refusing AI without telling their manager or team. When asked why they limit their use, the top answer was pride, at 39 percent, ahead of distrust in accuracy at 33 percent.
Pride is an uncomfortable word, so we tend to file it under resistance. But the more meaningful reading is that pride is a standard. It is a person saying that some of what they make has to stay theirs, and for Stay Human, that is exactly the signal worth listening to.
------------- Context -------------
Most workplaces handle quiet avoidance in one of two ways. Either the leader schedules more training, on the assumption that people just need to see how it works, or the leader raises the expectation, on the assumption that people need a push. Both treat the silence as a gap in knowledge or willingness.
The hidden problem is that neither response asks the question the person is actually answering. Someone who has tried the tool and set it aside does not lack a demo. They have already made a judgement about their own work, and that judgement is carrying real information about quality, voice and what they are willing to put their name on.
When we rename pride as craft, the picture changes. The people holding back are often the ones with the strongest standards in the room. They notice when a paragraph is almost right but not quite. They notice when a reply is polite but empty. Those instincts are precisely the human judgement that makes AI-assisted work worth trusting.
So the reframe is simple. Quiet avoidance is not a wall to knock down. It is an early report from the people best placed to say where AI helps the work and where it flattens it.
That matters for the human side of our work because standards that never get spoken never shape how a team uses these tools. The craft stays private, and the shared practice gets built without it.
------------- Pride Is a Standard Wearing the Wrong Label -------------
One of the quietest misreadings at work is hearing "I prefer to do it myself" as a refusal to change. Often it is a statement of what the person is protecting. The copywriter is protecting a voice. An analyst may be protecting the habit of checking every figure with their own eyes. A designer may be protecting the first, rough, personal sketch that everything else grows from.
Each of those is a human strength with a real job in the work. The voice is why a client recognises the brand. The checking is why the numbers hold up in front of the board. The sketch is why the design has a point of view. None of these is nostalgia.
Consider a team lead who hears a senior editor say she would rather not use AI for first drafts. The easy response is another workshop. The more useful response is to ask what she is protecting, and to write down the answer. Usually it fits in a sentence, such as "the opening paragraph has to sound like us".
That sentence is a gift. It names a piece of judgement that stays with a person, and it tells everyone else on the team where the line sits. For us, that is the whole point of staying human: the human part is named, kept and respected rather than quietly eroded.
------------- Silence Costs Us the Standards We Need Most -------------
When strong standards stay silent, the cost shows up elsewhere in the team. Imagine eight people, two of them senior editors who have decided privately to keep AI away from their own work. The six others use it freely, because nobody has told them where the quality line sits.
Drafts arrive in the editors' queue faster than before and rougher than before. The editors rewrite them in the evenings, say nothing, and quietly conclude that AI makes more work. The juniors, meanwhile, believe their output is fine, since nobody has said otherwise. Everyone is acting sensibly from where they stand, and trust slips on both sides.
The human cost here is not mainly the late evenings, though those are real. It is that the people with the best judgement are not shaping how the tool is used, so the team never learns what good looks like with AI in the loop. The juniors lose the chance to learn from their seniors. The seniors lose the feeling that their expertise counts.
A short, spoken standard fixes much of this. When the editors say what they look for, the juniors can aim for it before the draft arrives, and the seniors can see their craft travelling through the team rather than being quietly repaired at the end.
------------- Asking What We Should Never Lose Works Better Than Asking Why Not -------------
How we ask matters more than we usually admit. "Why aren't you using it?" invites a defence. It puts a person who takes care over their work in the position of explaining a failure to adopt, and the safest reply is a vague "I haven't had time".
A different question lands differently: "What about your work should never be handed over?" It treats the person as the expert on their own craft, which they are. It also tends to produce specific, usable answers, because people know exactly what they would hate to lose.
In a small team this can take ten minutes in a regular meeting. Each person names one thing in their work that must stay theirs, and one task they would happily hand over if it were done well. The pattern that usually emerges is generous. People protect the parts that carry judgement, voice and relationships, and offer up the admin, the formatting, the first-pass research and the tidying.
That is a more human way to design AI use than a blanket expectation. The boundary is drawn by the people who live inside the work, so the warmth, the judgement and the pride in the craft are written into the plan from the start rather than argued about later.
------------- Pride Can Choose Its Own Way In -------------
There is a final point worth making. The people who skip AI out of pride are not asking to be left alone for ever. Many of them are curious, and many have already tried it. What they need is an entry point that serves their standard rather than threatens it.
For the copywriter, that might be using AI to pull together background research and a list of the objections a reader might raise, with the writing left entirely to her. For the analyst, it might be asking the tool to spot inconsistencies in a table after she has done her own check. In both cases the person stays in charge, and the tool earns its place by making the craft sharper.
Over a few weeks, that kind of use can change the conversation. The copywriter finds that research is faster and her drafts are better informed. She might then try a rough first paragraph, notice what is wrong with it, and sharpen her sense of her own voice in the process. The choice to widen the use is hers.
That is what keeping people at the centre looks like in practice. AI amplifies the strengths already there, the person decides how far it goes, and the pride that looked like resistance turns into the quality control the whole team benefits from.
------------- Practical Moves -------------
First, listen for phrases like "I haven't got round to it" or "I prefer to do it myself", and treat them as an invitation to ask what the person is protecting rather than as a problem to fix.
Second, ask each person on your team one question this week: what part of your work should never be handed over, and why? Write the answers down in a shared place.
Third, ask the same people for one task they would gladly hand over if it were done well, and start your AI use there, since it is the least contested ground.
Fourth, let the senior voices set the quality line out loud. A single sentence such as "openings must sound like us" gives the whole team something clear to aim for.
Fifth, revisit the answers after a month. Boundaries move as trust grows, and giving people the right to move them keeps the choice theirs.
------------- Reflection -------------
A quarter of workers quietly avoiding AI, with pride as the biggest reason, is a signal and not a scandal. It tells us there are people in our teams holding standards that matter and carrying them alone.
That is why this belongs under Stay Human. The judgement, the voice and the care a person puts into their work are what make AI-assisted output worth sending, and they only travel through a team when someone makes it safe to name them.
In the end, the shift worth noticing is small. We move from asking who is resisting to asking what is being protected. And when people feel seen, heard and trusted with their own craft, they tend to bring it into the future with us rather than keep it out.
What is one thing in your work that you would never want to hand over, and have you ever said so out loud?
Where have you quietly skipped a tool because the result did not sound like you?
If your team named what must stay human in your work, what do you think the first answer would be?
36
5 comments
Igor Pogany
8
🪡 Pride Is Becoming the Quiet Reason We Skip AI
The AI Advantage
skool.com/the-ai-advantage
Founded by Tony Robbins, Dean Graziosi & Igor Pogany - AI Advantage is your go-to hub to simplify AI and confidently unlock real & repeatable results
Leaderboard (30-day)
Powered by