If you want Copilot to work to its potential, the secret is giving it a navigable map. Below are three practical, repeatable techniques we use at Mobile Mentor to turn fuzzy asks into crisp outputs you can act on.
Read them, try them, and tweak for your team’s voice.
1) Build a clear prompt template (the CREATE approach)
Purpose: Give structure so Copilot knows what role to play, what to deliver, and what constraints to respect.
When to use it: Whenever you want a context-rich, concrete result. For instance, emails, policy notes, user messages, or any copy that needs specific details.
How to assemble it:
Quick example:
Why it helps:
A neat template removes ambiguity. Copilot can match role, inject the facts, and keep the output within the limits you set, which means less back-and-forth editing.
2) Specify every important axis (the Eight-Dimension frame)
Purpose: Train Copilot to consistently match tone, audience, and format instead of guessing.
When to use it: Reports, executive summaries, customer comms, or anything where consistency matters.
Eight axes to define:
- 1
Need: What exact thing are you asking for?
- 2
Context / Details: Background facts Copilot should use.
- 3
Objective: The goal: inform, persuade, celebrate, convert.
- 4
Role: Which voice or persona to adopt (CEO, support rep, product manager).
- 5
Perspective: From whose point of view should the answer come?
- 6
Tone: e.g., confident, conversational, empathetic.
- 7
Style: Short bullets, narrative, formal memo.
- 8
Output format: Word count, sections, or file type.
Example:
Why it helps:
When you define these axes up front, Copilot behaves like a teammate who already understands your brand playbook. The output is predictable and repeatable, and perfect for templates you reuse across teams.
3) Make Copilot reason out loud (step-by-step chain of thought)
Purpose: Force stepwise reasoning so outputs become logical and actionable.
When to use it: Complex process improvements, planning exercises, diagnostics, or anything that benefits from a sequence of thinking.
How to prompt it:
- 1
State the overall problem or goal.
- 2
Break it into ordered steps.
- 3
For each step, ask for a clear deliverable or question to answer.
- 4
Ask Copilot to produce a short synthesized plan at the end.
Example: “Improve our onboarding process.”
Why it helps: Asking Copilot to “walk through” the logic produces not just answers but the reasoning behind them.
Putting it together: practical workflow
- 1
Start with CREATE for any one-off content (emails, announcements).
- 2
Use the Eight-Dimension frame to standardize recurring outputs (reports, memos).
- 3
Use Chain of Thought when you need decisions, root causes, or plans.
Combine: for a new cross-team playbook, you might ask Copilot (role = program manager) to: (a) identify gaps step-by-step, (b) draft the rollout email with a CREATE template, and (c) produce a one-page executive summary using the Eight-Dimension specs.
Final takeaway
Copilot performs best when you give it clarity and scaffolding. Templates (CREATE), dimensioned instructions (Eight Dimensions), and stepwise reasoning (Chain of Thought) each solve different problems. Together they turn Copilot from a smart autocomplete into a reliable, repeatable teammate. Try one on your next task and iterate; small prompt investments pay back fast in time saved and cleaner outputs.
