Exercise - Build an AI initiatives repository

  • 5 minutes

Earlier, you refined the problem in our scenario. Then you reviewed a plan, generated a first version, and improved the solution through feedback.

Now it's time to apply that process yourself.

Teams are experimenting with AI. Ideas live in emails, chats, spreadsheets, and meeting notes. As the number of projects grows, it becomes harder to compare ideas, identify overlap, and understand progress.

You're going to use Copilot Code to create a repository where AI initiatives can be submitted, reviewed, compared, and tracked.

What you're building toward

Every active AI initiative is captured with a name, an owner, a status, and an expected outcome. Leaders can see all initiatives in one view and filter by owner or status.

How to work through it

  • Review the requirements and decide what success looks like.
  • Describe what you need in Copilot Code and ask to see a plan first.
  • Answer any clarifying questions.
  • Review the generated solution against your requirements.
  • Make one meaningful improvement and review the result.

Illustration showing information from emails, chats, spreadsheets, and meeting notes consolidated into a single AI initiatives repository.

Check your work

  Your solution won't look exactly like anyone else's, and it doesn't need to. Use these checks to confirm it does what the scenario requires:  

  • An initiative can be submitted with a name, an owner, a status, and an expected outcome.
  • Submitted initiatives appear in a single view rather than in separate places.
  • The view can be filtered by owner or by status.   If any check fails, describe the gap in plain language and let Code refine the solution. That's the same working loop you used earlier, not a sign that something went wrong.

Now think about your own version of this problem. It might be the report you manually build, the spreadsheet multiple people update, or the process that lives in your inbox.

The pattern is the same: start with a clear business need, describe it in plain language, and ask Copilot Code to refine the solution.

You don't need a finished, polished tool. You need a working first version and a clear idea of what to refine next.