# The Power User Gap

Source: https://tpiros.dev/power-user-gap

A half-day for whoever owns learning, enablement or transformation somewhere that rolled AI out and watched usage split in two. Remote or on-site, up to fifteen people, no pre-work and no confidential material sent anywhere. A paid engagement, quoted against scope; nothing here is priced.

## The premise

EY's Work Reimagined Survey (August 2025, 15,000 employees and 1,500 employers across 29 countries) found 88% of employees using AI at work "primarily limited to basic tasks such as search and summarization", and only 5% "using it in advanced ways to transform the way they work". Same tools, same access, same organisation. The minority who broke through did something specific and unwritten, and it stays unwritten because it is particular to the work.

## Why the split happens

- Most people stopped at the first answer. Asking a question and reading the reply works well enough to feel like using the tool, and it is the ceiling for the majority of an organisation.
- The people who got further never wrote it down. What they know is specific to your documents, your approvals and your work, which is exactly why no vendor course sells it.
- The training was aimed at the wrong rung. A curriculum built to scale to a hundred thousand people teaches the product, not the change in how somebody works.

## What the half-day covers

- Giving work away rather than asking questions: what can be handed over whole, what has to be broken up, and what should stay with a person.
- Context as the job: the document, the constraint, the example of good, the thing that must not happen. Real tasks from your own people, rebuilt with the context that was missing.
- Judgement at speed: what is worth verifying, what can be spot-checked, and how to recognise the fluent, confident, wrong answer.

It deliberately does not cover cognitive load, trust and empathy, or what a person is worth once everyone can generate a decent draft. Those are real questions for somebody better qualified.

## What you keep

A written playbook, within a week of the session: eight to twelve worked patterns taken from your own people, the context each one needs, a verification checklist proportionate to the risk of the work, and the habits worth dropping. It belongs to you, and whoever runs enablement can hand it out and run the material again without me.

## How it runs

Three or four half-hour conversations with the people you have identified as getting the most from these tools, then the half-day, then the playbook. The conversations are conversations: no exports, no documents sent to me, no access to your systems.

## Who it is not for

Organisations that have not rolled anything out yet, engineering teams building agents (better served by the Agent Workshop at https://tpiros.dev/agent-workshop), and anyone wanting a tool recommendation. The session works with whatever you have already bought.

## On sourcing

A widely repeated claim that AI power users are four times more productive, credited to OpenAI, is deliberately absent: their report describes frontier workers sending roughly six times more messages, which measures activity rather than output. Figures used here are traceable to the publisher's own reporting.

## Next step

Email hello@tamaspiros.com with when the tools went out and who is getting the most from them, or book a call at https://calendly.com/tamas-piros/30min.