Define your requirements
Good solutions start with a clear problem. Before you open Copilot Code, spend a few minutes turning your idea into something specific enough to build against.
Three questions to guide you
What is the real problem? Focus on the friction people feel, not the tool you're already picturing. You rarely need a dashboard. You need to know which projects are behind.
Who will use this, and what do they need to do? Submit something, find something, compare options, approve a request. Naming the actions shapes the solution.
What does success look like? Be specific enough that you'll recognize it when you see it.
Common business scenarios
Organizations use Copilot Code to create dashboards, trackers, workspaces, and apps.
- A finance team turns a weekly leadership report into a live status dashboard.
- A sales team creates a workspace that brings together customer information, meeting notes, and next steps.
- A marketing team turns customer feedback into a dashboard that highlights trends and recurring themes.
- An HR team builds a tracker for open roles, interview progress, and hiring status.
The scenario in this module
A product team is experimenting with AI initiatives, but information is scattered across emails, chats, spreadsheets, meeting notes, and shared documents. This makes it difficult to identify overlap and track progress.
Apply the three questions to define the requirements:
What is the real problem? The team lacks a complete view of its AI initiatives.
Who will use the solution, and what do they need to do? Project owners submit initiatives. Leaders review, compare, and track them.
What does success look like? Each initiative includes a name, owner, status, and expected outcome. Leaders can view all initiatives in one place and filter them by owner or status.
These requirements provide a clear starting point for planning the solution.