{"id":67,"date":"2026-04-12T01:10:56","date_gmt":"2026-04-12T01:10:56","guid":{"rendered":"https:\/\/karloneill.dev\/?p=67"},"modified":"2026-04-12T01:33:23","modified_gmt":"2026-04-12T01:33:23","slug":"stop-googling-start-prompting","status":"publish","type":"post","link":"https:\/\/karloneill.dev\/?p=67","title":{"rendered":"Stop Googling, Start Prompting"},"content":{"rendered":"\n

Most people use ChatGPT or Microsoft Copilot (or Gemini, or Claude) the same way they use Google \u2014
type a few words, hit Enter, hope for the best. And then wonder why the answer
feels generic, off-topic, or just not quite right.<\/p>\n\n\n\n

Here’s the thing: it’s almost never the AI’s fault. It’s the question.<\/p>\n\n\n\n

The difference between a useful AI response and a frustrating one usually
comes down to how much you tell it. Google is designed to guess what you mean
from a few keywords. AI tools like ChatGPT are designed to follow instructions
\u2014 and the better your instructions, the better your result.<\/p>\n\n\n\n

The Problem With Treating AI Like a Search Engine<\/h4>\n\n\n\n

When you type “email template” into Google, it works fine. You get a list of
pages with email templates. You pick one, copy it, done.<\/p>\n\n\n\n

Type “email template” into ChatGPT and you get\u2026 an email template. A bland,
generic one that doesn’t sound like you, doesn’t fit your situation, and
you’ll end up rewriting half of it anyway.<\/p>\n\n\n\n

That’s not the AI failing. That’s you asking Google-style when you have a much
more powerful tool in front of you.<\/p>\n\n\n\n

The 3 Ingredients of a Good Prompt<\/h4>\n\n\n\n

You don’t need to become a “prompt engineer” or learn anything technical. You
just need to give the AI three things:<\/p>\n\n\n\n

    \n
  1. Context \u2014 what’s the situation? Tell it who you are, who you’re talking to, or what’s going on. You don’t need an essay, just a sentence.

    \u258e “I’m a project manager at a small logistics company\u2026”

    <\/li>\n\n\n\n
  2. The task \u2014 what do you actually want? Be specific.

    Not:

    \u258e “write an email”

    but:

    \u258e “write a follow-up email to a client.”

    <\/li>\n\n\n\n
  3. Constraints \u2014 any limits or preferences? Tone, length, format. “Keep it under 100 words” or “make it friendly but professional” goes a long way. Put it together and instead of:

    \u258e “email template”

    Try:

    \u258e “Write a short, friendly follow-up email to a client who hasn’t responded to my proposal in two weeks. Don’t be pushy \u2014 just check in and offer to answer any questions. Keep it under 100 words.”

    That second prompt takes 20 extra seconds to write. The output is something
    you could actually send.

    And don’t expect AI to be perfect. Add your finishing touches. That is the satisfying part, you can focus on making the email your own after AI has done the heavy lifting.<\/li>\n<\/ol>\n\n\n\n

    3 Examples From a Typical Office Day<\/h4>\n\n\n\n

    Scenario 1: <\/strong>You need to summarise a long email thread before a meeting<\/p>\n\n\n\n

    Instead of: <\/p>\n\n\n\n

    \u258e “summarise this email”<\/p>\n\n\n\n

    Try:

    \u258e “Summarise this email thread in 3 bullet points. I need the key decisions
    made, any outstanding actions, and who is responsible for each. I’m preparing
    for a 15-minute catch-up meeting.”<\/p>\n\n\n\n

    Scenario 2: <\/strong>You need to push back on a request without causing offence<\/p>\n\n\n\n

    Instead of: <\/p>\n\n\n\n

    \u258e “help me write a professional email”<\/p>\n\n\n\n

    Try: <\/p>\n\n\n\n

    \u258e “Help me write a polite but firm email declining a request to take on
    extra work this month. I want to sound helpful and offer an alternative
    timeline without sounding like I’m just saying no. Keep the tone warm.”<\/p>\n\n\n\n

    Scenario 3: <\/strong>You’re preparing talking points for a presentation<\/p>\n\n\n\n

    Instead of: <\/p>\n\n\n\n

    \u258e “presentation tips”<\/p>\n\n\n\n

    Try: <\/p>\n\n\n\n

    \u258e “I’m presenting our Q1 sales results to senior management next week. The
    numbers are mixed \u2014 some targets hit, some missed. Give me 5 talking points
    that acknowledge the shortfalls honestly but keep the focus on what we’re
    doing differently in Q2.”<\/p>\n\n\n\n

    In each case, the extra detail isn’t busywork \u2014 it’s what lets the AI actually
    help you.<\/p>\n\n\n\n

    One Habit to Start Today<\/h4>\n\n\n\n

    Before you hit Enter on your next AI prompt, ask yourself one question:<\/p>\n\n\n\n

    \u258e “Would a colleague know exactly what I need from this?<\/strong><\/p>\n\n\n\n

    If the answer is no, add one more sentence. That’s it. You don’t need a
    perfect prompt \u2014 you just need enough context that a reasonably smart person
    could help you.<\/p>\n\n\n\n

    AI tools are at their best when you treat them less like a search engine and
    more like a capable colleague you can brief properly. The more you tell them,
    the more useful they become.<\/p>\n\n\n\n

    \n

    Next Post: <\/strong>how to get better results by asking the AI to think step by step \u2014
    and why it makes a surprising difference.<\/em><\/p>\n<\/blockquote>\n\n\n\n

    <\/p>\n","protected":false},"excerpt":{"rendered":"

    Most people use ChatGPT or Microsoft Copilot (or Gemini, or Claude) the same way they use Google \u2014type a few words, hit Enter, hope for the best. And then wonder why the answerfeels generic, off-topic, or just not quite right. Here’s the thing: it’s almost never the AI’s fault. It’s the question. The difference between […]<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[3],"tags":[],"class_list":["post-67","post","type-post","status-publish","format-standard","hentry","category-generative-ai"],"_links":{"self":[{"href":"https:\/\/karloneill.dev\/index.php?rest_route=\/wp\/v2\/posts\/67","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/karloneill.dev\/index.php?rest_route=\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/karloneill.dev\/index.php?rest_route=\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/karloneill.dev\/index.php?rest_route=\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/karloneill.dev\/index.php?rest_route=%2Fwp%2Fv2%2Fcomments&post=67"}],"version-history":[{"count":2,"href":"https:\/\/karloneill.dev\/index.php?rest_route=\/wp\/v2\/posts\/67\/revisions"}],"predecessor-version":[{"id":69,"href":"https:\/\/karloneill.dev\/index.php?rest_route=\/wp\/v2\/posts\/67\/revisions\/69"}],"wp:attachment":[{"href":"https:\/\/karloneill.dev\/index.php?rest_route=%2Fwp%2Fv2%2Fmedia&parent=67"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/karloneill.dev\/index.php?rest_route=%2Fwp%2Fv2%2Fcategories&post=67"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/karloneill.dev\/index.php?rest_route=%2Fwp%2Fv2%2Ftags&post=67"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}