On Tuesday evening, October 27, 2026, we are going to look at two ordinary situations where AI can be genuinely useful: researching a major purchase and writing a professional decline email. Neither requires technical skill. What they require is a willingness to give the AI enough context - and enough skepticism - to produce something you can actually use.

Try at least one before Sunday. That is the whole assignment.

Use Case 1 of 2

Use Case 1: Researching a Major Purchase Decision

At 7:40 p.m. on Wednesday, October 28, Martin Alvarez was sitting at his kitchen table with three laptop tabs open and a notepad beside him. He needed a new car before his current one became unreliable, but the choices had multiplied: hybrid, plug-in hybrid, electric, or a conventional gas model. Martin drives about 11,000 miles a year, keeps cars for a long time, has a $42,000 budget, and lives in an apartment without a private charging station. Every review seemed to recommend something different. One praised fuel economy; another warned about repair costs. He did not need more opinions. He needed a way to compare the choices against his actual life.

That is where AI can help - not by making the decision for you, but by turning a vague, exhausting search into a clear comparison. The best use is to have AI identify the questions, organize the tradeoffs, and show you what still needs verification. For a major purchase, that last part matters. AI can produce confident errors, so important claims should be checked against current manufacturer information, independent testing, contracts, warranty documents, and other trusted sources.

Here is the exact prompt to use:

Copy and paste this into ChatGPT or Claude:

> I am researching a major purchase and want help making a careful, evidence-based decision - not a sales pitch. > > My situation: > - Purchase: [describe the product] > - Budget: [amount, including whether taxes, delivery, installation, or accessories must be included] > - Location: [city, state/province, or country] > - How I will use it: [describe your normal use] > - How often I will use it: [frequency] > - Time horizon: [how long you expect to keep it] > - Must-have features: [list them] > - Nice-to-have features: [list them] > - Deal-breakers: [list them] > - Important personal constraints: [space, mobility, maintenance, charging, noise, compatibility, or other concerns] > > Compare these options: [list the specific products or categories]. > > Please do the following: > 1. Ask me up to five important questions if information is missing. > 2. Create a comparison organized around my situation, not generic popularity. > 3. Separate facts, estimates, assumptions, and opinions. > 4. Identify the three costs people commonly overlook, such as maintenance, accessories, subscriptions, installation, financing, insurance, or resale value. > 5. Explain which option appears strongest for my priorities and why. > 6. Explain which option appears weakest and why. > 7. List the claims I must verify independently before buying. > 8. Tell me what new information would change your recommendation. > > Do not invent prices, specifications, warranties, availability, or user reviews. If you do not know something or cannot verify that it is current, say so clearly. Do not recommend a product merely because it is popular.

Why this prompt works: It gives the AI a decision frame instead of asking, “What is the best product?” That question invites a generic answer. This prompt supplies budget, usage, constraints, priorities, and time horizon - the details that make one choice sensible for one person and wrong for another. It also tells the AI to distinguish facts from assumptions and to identify what must be checked. That is crucial because fluent AI output is not proof of accuracy; generative systems can confidently present false or inconsistent information.

Use Case 2 of 2

Use Case 2: Writing a Professional Decline Email

At 9:15 a.m. on Thursday, October 29, 2026, Elaine Foster stared at an email from a former colleague. The colleague wanted Elaine to join a six-month consulting project, beginning in two weeks. The work sounded interesting, and Elaine valued the relationship, but she had already committed to two clients and was caring for her husband after surgery. She knew the answer was no. The trouble was writing it. Her first draft began with an apology, wandered through several paragraphs of explanation, and ended with “maybe sometime later,” even though she had no idea whether that would be true.

A good decline email does not require a perfect excuse. It needs acknowledgment, a clear decision, a brief reason, and - only when genuine - a realistic alternative. The decision should appear near the beginning rather than being buried under apologies. Concise professional communication respects the recipient’s time and reduces the chance of creating a negotiation by accident.

Here is the exact prompt to use:

Copy and paste this into ChatGPT or Claude:

> Write a professional email declining the request below. > > The recipient’s name is [name], and my relationship with them is [client, colleague, former manager, vendor, acquaintance, etc.]. > > Their request is: > [paste or summarize the request] > > My decision is: [clearly state what I am declining]. > > My honest reason, in one sentence, is: > [brief reason] > > I am willing to offer this alternative, only if it fits naturally: > [alternative, referral, future date, or “no alternative”] > > My preferred tone is warm, direct, and professional. Write 120 to 170 words. Thank the person for thinking of me. State the decision clearly in the first two paragraphs. Give one brief reason without over-explaining or sounding defensive. Include an alternative only if it is realistic. Do not make promises I have not authorized. > > Avoid these phrases: “I’m sorry, but,” “unfortunately,” “maybe,” and “I hope you understand.” Do not make the refusal sound negotiable. Do not criticize the request or imply that the other person wasted my time. Include a clear subject line and a warm closing. > > After the draft, briefly explain any sentence that could accidentally sound vague, cold, or open to further negotiation.

Why this prompt works: It tells the AI both what to include and what to avoid. Most weak decline emails fail in one of two ways: they hide the answer beneath a long explanation, or they sound so apologetic that the recipient thinks persuasion might work. This prompt defines the relationship, decision, reason, tone, length, and boundary. Asking for a short explanation after the draft adds a useful review step rather than treating the first version as automatically right.