Almost every assistant I talk to admits the same thing, usually in a lower voice than the rest of the conversation. "I think I should be further ahead with AI by now."

They say it like a confession. As if everyone else got the memo and they were off making the tea.

Here is what I have noticed. When you actually sit with it, the worry is rarely about the technology. Nobody has ever said to me, "I don't understand how it works." What they say is closer to "I've tried it, but it doesn't do what I expected," or "I'm not sure I'm using it right."

That is a completely different problem. And it is a much easier one to fix.

The Problem Was Never the Tool

I had the same experience. I would open the tool, type a quick instruction, and get back something that looked fine but read like it had been written by someone who had never met my executive. The tone was off. The context was missing. I would rewrite most of it and quietly wonder what the fuss was about.

The turning point was not a better tool. It was realising the problem was not the output. It was my input.

Most of us spent years holding context in our heads. The history behind a request. The stakeholder who needs careful handling. The thing the exec said in passing that changes everything. AI cannot see any of that unless you say it out loud. It is not reading your mind. It is reading your instructions.

Why the Feeling Spreads

There is also a quieter reason this worry catches on. Most of what you see online is the polished version. The clean output. The clever example. What you do not see are the five attempts it took to get there, or the judgement behind it. It creates the impression that everyone else is sprinting while you are still finding your shoes.

If that sounds familiar, start here. Be specific. Include the context you would normally carry in your head. Treat the first output as a draft, never a decision. And sense-check everything before it leaves your desk, because that part is still your job.

Try This Prompt Draft a reply from me to [name] confirming [meeting]. Tone: warm but direct. Acknowledge their earlier note about timelines. Keep it under 120 words. This is going to a senior stakeholder, so no filler.

Notice the difference. The output improves, not because the tool got cleverer, but because you did.

If any of this lands, you are not behind. You are at the exact point where the real learning starts.

Community Question

What is one task where you tried AI and thought, "this should be more useful than it is"?

Want to build prompting skills that actually work in your role? B.R.I.E.F. Prompting is the place to start.

Browse All Courses