Journal · The AI Architect · 2026-07-11
Your AI starts each task knowing nothing about your world. Say the "obvious" context out loud, and the results jump.
Your AI starts each task knowing nothing about your world. Say the “obvious” context out loud, and the results jump.
The tension isn’t that AI is dumb. It’s that we keep expecting it to be smart in ways that require memory it doesn’t have. Every session, you’re talking to something that has read most of the internet and knows nothing about your Tuesday. That gap is where good work goes to die, and most people paper over it by just typing faster, hoping volume compensates for missing context. It doesn’t.
Your context is not obvious to the machine, even when it’s obvious to you
Here’s the trap: the things most worth mentioning are exactly the things that feel too basic to say. You know your company sells to hospitals, not retailers. You know “the report” means the quarterly board deck, not some generic template. You know your team already tried the simple fix and it failed for a specific reason. None of that is written down anywhere the AI can see. It’s living in your head, filed under “everyone knows this.”
The AI doesn’t know it. It will guess. Sometimes the guess is close enough that you don’t notice the miss. More often, you get an answer that’s technically responsive but quietly wrong for your situation — generic advice dressed up as tailored insight.
Try this: before your next real task, write a three-line preamble. Who this is for, what’s already been tried, and what “good” looks like here. Paste it in before your actual request. Watch how much the answer changes. Most people are stunned that three sentences of throat-clearing outperform a much longer, cleverer prompt.
Specificity beats eloquence
There’s a temptation to think good prompting is about finding the right magic words — some clever phrasing that unlocks a better answer. Mostly it isn’t. It’s about removing ambiguity the AI would otherwise have to invent an answer for.
If you ask for “a marketing email,” you’ll get a marketing email — the most statistically average one imaginable, assembled from every marketing email the model has ever seen. If you say “a marketing email for existing customers who haven’t purchased in six months, tone should be warm not pushy, and we’re not offering a discount because that trains people to wait for sales,” you’ve just eliminated a dozen wrong turns before they happened.
This isn’t about writing more. It’s about writing the two or three details that actually constrain the problem. A good test: read your prompt back and ask, “could this apply to literally anyone’s situation?” If yes, you’ve left out the part that makes it yours.
Context has a shelf life, so plan to repeat yourself
The other piece people miss: context doesn’t stick. You can have a brilliant exchange where the AI clearly “gets” your project, and then open a new session tomorrow and it’s a stranger again. This isn’t a bug you’re failing to work around — it’s just how these tools currently work, and it changes how you should operate.
The fix isn’t to get annoyed at re-explaining. It’s to make re-explaining cheap. Keep a standing document — half a page — with the context you find yourself repeating: what the project is, who it’s for, the constraints that don’t change week to week. Then you paste that in instead of reconstructing it from memory every time, which is where the “obvious” details quietly get dropped.
Try this: the next time you catch yourself giving the AI background information, save it. Not the whole conversation — just the setup. In a week you’ll have a small library of context blocks you can reuse, and you’ll notice you’re doing less explaining and getting better first drafts.
None of this is about tricking the AI or finding some clever workaround. It’s closer to what you’d do onboarding a sharp new hire who’s never met your clients, doesn’t know your history, and can’t read your mind. You wouldn’t hand them a one-line task and expect magic. You’d tell them what they need to know. Same idea here — except this new hire forgets everything by tomorrow morning, so the context has to travel with the request, every time.
I go into more depth on this in the book — how to build reusable context, where the line is between helpful detail and overexplaining, and why this one habit tends to matter more than any prompting trick people search for. But the short version is what’s above: say the obvious thing. It’s obvious to you. It isn’t to the machine.
Go deeper. The full method is in The AI Architect. New here? Start with the free companion pack, or explore the series.