Research and update your technology strategy with Copilot

Step 1: State what's driving the updateWord

Write one clear sentence naming the actual trigger — a new business priority, a specific technology shift, or a prior strategy that's visibly out of date — at the top of the doc before researching anything.

Without that anchor, the research in step 2 tends to sprawl into a generic "what's trending in IT" survey instead of staying focused on the one thing that actually needs to change.

Step 2: Ask for current best practice, not generic adviceCopilotChatGPTClaude

Ask specifically about how organizations similar to yours are approaching the trigger you named, not a broad "what's trending in IT."

Prompt idea:

Our technology strategy is three years old and doesn't address our shift to [specific priority]. Research current best practice for organizations our size addressing this, and draft an updated strategy section with reasoning for each recommendation.

Step 3: Stress-test each recommendation against your actual constraintsWord

A recommendation that ignores your budget, headcount, or existing vendor commitments isn't actionable — flag anything that doesn't survive contact with reality.

Step 4: Route to leadership with the reasoning intactWord

Keep the "why" behind each recommendation visible in the document, not just the "what" — leadership approving a strategy needs to see the reasoning to sign off confidently.

Check the work

• Every recommendation states the reasoning behind it, not just the conclusion.
• Recommendations were checked against actual budget and resourcing constraints.
• The update addresses the specific trigger named in step 1, not a generic refresh.

Source: Microsoft Copilot Scenario Library — Update technology strategy (2026)