
Module 2 · Lesson 3 of 6 · with Nova
Give AI the Context That Matters
Objective
Identify the constraints and background information that genuinely change what a good answer looks like.
AI suggests a lovely dinner that takes ninety minutes. You've got twenty-five, no oven and three hungry people asking when they'll eat. The missing ingredient wasn't food. It was context.
When you ask for 'a quick dinner', the assistant has to guess what quick means, how many people you're feeding, which ingredients you own and what equipment you can use. A perfectly reasonable answer can be completely wrong for your particular evening. The assistant isn't necessarily ignoring you. You haven't yet given it the information that matters.
Now imagine saying: 'Dinner for three in twenty-five minutes. I've got rice, eggs and frozen vegetables. No oven tonight, and I don't want to shop. Suggest three possibilities.' That isn't a clever technical prompt. It's a small collection of facts that rule out unhelpful choices and make useful ones more likely.
Context is whatever changes the appropriate answer. For a presentation, the audience and purpose may matter. For learning, what you already know may be more useful than your job title. For a plan, timing, budget and immovable commitments may determine everything. The skill is deciding which details make a difference, not sending AI your entire life story.
There's a temptation to believe that longer prompts must always be better. But a page of unrelated background can obscure the few constraints that actually matter. Start with the essentials. If the assistant suggests something unsuitable, notice the assumption it made. That often tells you exactly what information to add.
Suppose the dinner ideas include mushrooms and somebody at home hates them. You can simply say, 'No mushrooms, and keep the flavours mild.' The assistant should adapt. You can also invite it to ask you a question if an important detail is missing. A good conversation develops its context gradually rather than requiring you to anticipate every possibility before you begin.
Personalisation doesn't require sharing private information. For a fictional budgeting problem, approximate numbers may be enough. For a work scenario, roles may matter more than people's names. Give the assistant what's relevant to the problem and appropriate for the service, not everything you happen to know.
Let's change one thing in the dinner example. You now have thirty minutes rather than twenty-five, but one person cannot eat eggs. That isn't just extra background. It changes which suggestions are acceptable. If you say only 'someone doesn't like eggs', the assistant might treat the ingredient as a negotiable preference. If it's an allergy, say so clearly. Some details set boundaries; others simply help rank the choices.
Context can also explain why you are asking. Suppose you have everything needed for a complicated dish, but you're cooking after a particularly tiring day. 'I want the fewest possible steps and minimal washing-up' may be more useful than listing another ingredient. You don't have to justify yourself. You just need to tell the assistant which part of the experience matters tonight.
What if you don't know which information is relevant? You can start with a short description and ask the assistant what it needs to know. A useful assistant might ask whether you're cooking for children, what equipment is available or whether there are dietary restrictions. You can answer one question at a time. This is often easier than writing an enormous briefing for a task you're still trying to understand yourself.
Consider a second setting: asking AI to help you prepare for a job interview. Your target role, relevant experience and the kind of questions you want to practise could matter a great deal. Your home address, personal identifiers and details about unrelated colleagues probably don't. The skill transfers from cooking to careers because you're selecting information according to the job, not because there's one universal prompt template.
And context can change as a project develops. Imagine you first ask for ideas, then choose one and begin planning it. The early conversation needs variety; the later conversation needs the decisions you've already made. A brief recap — 'We've chosen the simplest option, the budget is fixed, and I need a checklist' — can be more helpful than making the assistant sift through every possibility you've discarded.
Try noticing how a response changes when you add one genuinely relevant detail. That's the practical value of context. AI starts behaving less like a generator of generic advice and more like something helping with the situation you're actually in.