Writing Effective Copilot Prompts

The difference between a mediocre Copilot experience and a transformative one comes down to how you write your prompts. This lesson teaches you the prompt engineering techniques that consistently produce better results across every Microsoft Copilot tool.

What You'll Learn

By the end of this lesson, you will master a proven framework for writing Copilot prompts, understand how to iterate and refine results, and have a library of ready-to-use prompt templates for common tasks.

The RISEN Framework for Copilot Prompts

Microsoft recommends the RISEN framework for structuring Copilot prompts. Each letter represents an element that improves your results:

R — Role

Tell Copilot what role or perspective to adopt:

• "Act as a marketing strategist..."
• "You are a financial analyst preparing a report for the CFO..."
• "As an experienced project manager..."

Setting a role shapes the vocabulary, depth, and perspective of the response.

I — Instructions

Give clear, specific instructions about what you want:

• "Write a 500-word blog post..."
• "Create a comparison table with 5 columns..."
• "Summarize this in exactly 3 bullet points..."

Be explicit about format, length, and deliverable.

S — Steps

For complex tasks, break the work into steps:

• "First, analyze the data for trends. Then, identify the top 3 opportunities. Finally, draft recommendations for each."
• "Step 1: Review the attached document. Step 2: Extract all financial figures. Step 3: Create a summary table."

Steps help Copilot approach complex work methodically.

E — End Goal

Explain what you want to achieve with the output:

• "...so that leadership can make a go/no-go decision at Friday's meeting"
• "...to use as a client-facing presentation"
• "...for posting on LinkedIn to establish thought leadership"

The end goal shapes tone, detail level, and content focus.

N — Narrowing

Add constraints to focus the output:

• "Do not include technical jargon"
• "Focus only on the North American market"
• "Keep the tone professional but approachable"
• "Use data from 2025 and 2026 only"

Constraints prevent Copilot from going too broad or including irrelevant information.

Full RISEN Example

"Role: Act as a senior business analyst. Instructions: Create a one-page executive brief. Steps: First, summarize the problem. Then, present three solution options with pros and cons. Finally, make a recommendation. End goal: This will be presented to the VP of Operations to decide on a vendor for our new CRM system. Narrowing: Focus on cloud-based solutions under $50K/year. Use a professional tone. Include a comparison table."

Common Prompt Patterns

The Transformation Pattern

Take existing content and transform it:

• "Take this meeting transcript and turn it into formal meeting minutes with action items"
• "Convert this technical specification into a non-technical product description for customers"
• "Transform these raw survey results into an executive insights report"

The Template Pattern

Generate structured, repeatable outputs:

• "Create a template for monthly department reports that I can reuse. Include sections for KPIs, accomplishments, challenges, and next month's goals"
• "Design a standard email template for responding to customer complaints. Include placeholders for [customer name], [issue description], and [resolution offered]"

The Comparison Pattern

Generate structured analyses:

• "Compare these three vendors across cost, features, support quality, and implementation time. Present as a table with a recommendation row at the bottom"
• "Analyze the pros and cons of hiring a contractor versus a full-time employee for this role"

The Iteration Pattern

Build on previous outputs in a conversation:

1. "Draft an outline for a marketing strategy document"
2. "Expand section 2 with more detail on digital channels"
3. "Add budget estimates to each initiative"
4. "Now write the executive summary based on everything above"

The Persona Pattern

Generate content for different audiences from the same information:

• "Explain our new return policy. Write three versions: one for customers (friendly), one for store employees (procedural), and one for management (strategic rationale)"

Prompt Refinement Techniques

Adding Specificity

If a response is too generic, add specific details:

• Before: "Write about project management"
• After: "Write about agile project management best practices for software development teams of 5-10 people working in two-week sprints"

Adjusting Length

Control the output volume:

• "Limit this to 200 words"
• "Expand this into a full page"
• "Give me the TL;DR version in 2 sentences"
• "Be comprehensive — do not leave out any important details"

Controlling Format

Specify exactly how you want the output structured:

• "Format as a numbered list"
• "Use a table with columns for X, Y, and Z"
• "Write in paragraph form with clear topic sentences"
• "Use headers and sub-headers to organize the content"
• "Present as a decision matrix"

Fixing Common Issues

When Copilot's response is not quite right:

• Too formal: "Rewrite this in a more conversational tone, as if you are explaining it to a colleague over coffee"
• Too vague: "Be more specific. Include actual numbers, dates, and names"
• Too long: "Cut this in half while keeping all key points"
• Wrong focus: "Shift the focus from [X] to [Y]. The audience cares most about [Y]"
• Missing context: "This is for [specific context]. Adjust the content accordingly"

Ready-to-Use Prompt Templates

For Word

Project Proposal: "Act as a business analyst. Draft a project proposal for [project name]. Include: Executive Summary, Problem Statement, Proposed Solution, Scope (in-scope and out-of-scope), Timeline with milestones, Resource Requirements, Budget Estimate, Risk Assessment, and Success Metrics. Target audience: [department] leadership. Keep it under 5 pages. Professional tone."

Meeting Summary: "Summarize the following meeting notes into a professional document. Sections: Meeting Purpose, Key Discussion Points, Decisions Made, Action Items (with owners and deadlines), and Next Steps. Keep it concise — one page maximum."

For Excel

Data Analysis: "Analyze this sales data and provide: 1) Total revenue by product category, 2) Month-over-month growth rate, 3) Top 5 products by revenue, 4) Any products with declining sales. Add these as new columns or a summary table below the data."

Dashboard Creation: "Create a summary dashboard at the top of this sheet showing: Total Revenue, Average Order Value, Number of Orders, Top Product, and Worst Performing Region. Use formulas that update automatically."

For PowerPoint

Client Presentation: "Create a 12-slide client presentation. Structure: Title slide, Agenda, About Us (brief), Client's Challenge (2 slides), Our Proposed Solution (3 slides), Implementation Timeline, Pricing Overview, Case Study / Testimonial, Next Steps, Contact Information. Use a professional, confident tone."

For Outlook

Stakeholder Update: "Draft an email to [stakeholder group] providing a project status update. Include: Current status (on track/at risk), key accomplishments this period, upcoming milestones, any blockers requiring their input, and a clear ask for what you need from them. Tone: professional but direct. Keep it under 200 words."

For Teams

Meeting Prep: "Based on the meeting agenda and related documents, prepare: 1) A brief summary of each agenda item, 2) Key questions to raise, 3) Data points to reference, 4) Suggested action items to propose."

Key Takeaways

• Use the RISEN framework (Role, Instructions, Steps, End goal, Narrowing) to structure effective prompts.
• Common patterns include Transformation, Template, Comparison, Iteration, and Persona — learn to recognize which pattern fits your task.
• Refine results by adjusting specificity, length, format, and focus rather than starting over from scratch.
• Save your best-performing prompts as templates for recurring tasks.
• The most effective Copilot users treat prompting as a skill that improves with practice — experiment, iterate, and keep what works.