Activity
Mon
Wed
Fri
Sun
May
Jun
Jul
Aug
Sep
Oct
Nov
Dec
Jan
Feb
Mar
Apr
What is this?
Less
More

Memberships

AI Without The Hype

54 members • Free

1 contribution to AI Without The Hype
The 4 parts of a good Copilot prompt
Happy 50+ members!!! 🎉🎉🎉 Huge thank you to all of you early founding members! it’s been great seeing you join, explore, comment and share🙏 I know quite a few of you are using Copilot, so here’s a quick bonus tip when you’re writing prompts: 💡Always include: 1. A GOAL: What are you trying to get out of it? 2. The CONTEXT: What are you working on / why does it matter? 3. The SOURCES: Where should it look? (e.g. emails, Teams chats, documents, websites) 4. Your EXPECTATIONS: How should it respond? ➡️Quick Example: Goal: generate 3–5 bullet points Context: preparing for a meeting with Manager X to update them on work progress Sources: focus on emails and Teams chats since June (if you want me to show you how to access your emails/chats, comment on this post!) Expectations: use simple language so I can get up to speed quickly It sounds simple, but it makes a big difference. 👇Let me know if you want more of these! And if you know someone who would find these tips useful, 🗣️ invite them over!
1 like • 1d
Love this — super clear framework 👏 One thing I see people struggle with a lot is what NOT to do when prompting. A few common mistakes I see: - Being too vague (“summarise this” with no context) - Skipping the audience (“make it better” — for who?) - No constraints (length/tone/format means you get unpredictable results) - Asking for too much in one prompt (better to break it into steps) - Not iterating (first output is rarely the best one) The way I think about prompts is: treat them like giving instructions to a new team member — the clearer you are, the better the outcome.
1-1 of 1
Bassam Farran
1
4points to level up
@bassam-farran-6459
Machine Learning PhD with experience in applications to healthcare, Formula 1, and telecoms

Active 20h ago
Joined Mar 23, 2026