Tuesday Prompt Day 🚀 | 6W + E — Practical Experiment #1
Last Tuesday, I introduced a simple principle I’ve been developing for better AI prompting: WHY → WHAT → WHO → WITH → WAY → WIN → EVALUATE 6W + E. 🔗 If you missed the original discussion: https://techcommunity.microsoft.com/discussions/6b6b9aaa-f41d-42fa-b90a-e1bb1d97a954/is-your-ai-prompt-missing-the-real-problem--introducing-the-6w--e-framework/4546006 Today, I don't want to explain the framework again. I want to test it. Let’s take a common Copilot request: “Create a summary of our cloud migration project.” Seems simple. But before asking Copilot to produce the answer, let's think about the problem. WHY are we creating the summary? WHAT exactly should it communicate? WHO will read it? WITH what information should Copilot work? WAY should the information be presented? WIN — what would make the result successful? And finally: EVALUATE — did Copilot actually give us what we needed? Now compare that with a more intentional prompt: “You are an enterprise cloud solution architect preparing an executive update. Create a concise summary of our cloud migration project for senior business and IT leadership. The objective is to communicate progress, business impact, key risks and the next priorities. Focus on the current quarter. Structure the response into: Executive summary • Business impact • Key achievements • Current risks • Next priorities • Decisions required from leadership Keep the language business-friendly and avoid unnecessary technical detail. Where information is missing, clearly identify the gap rather than inventing details.” The interesting part isn't simply that the second prompt is longer. The interesting part is that we have given Copilot a clearer way to understand the problem. And this brings us back to the final part of 6W + E: E = EVALUATE. I don't believe good prompting ends when Copilot gives us an answer. The real cycle is: Think → Prompt → Evaluate → Refine Sometimes the first response is good. Sometimes it isn't. Sometimes the problem isn't the AI's capability. Sometimes we haven't given AI enough direction to solve the right problem. So, here's today's community challenge 👇 Take ONE prompt you regularly use with Copilot. Don't share anything confidential. Share: Your original prompt What you wanted Copilot to achieve Which part of 6W + E was missing How you would improve the prompt Let's see whether we can improve real-world Copilot interactions together. I'll use the best examples from this discussion as we continue developing the 6W + E learning series. And this is only Experiment #1. Next, we'll look at what happens when we deliberately use EVALUATE to improve the first response. What has been your experience? Do you usually refine your Copilot response, or accept the first answer? #MicrosoftCopilot #GenerativeAI #PromptEngineering #MicrosoftCommunity #EnterpriseAI #AITransformation