In a Microsoft business, the opportunity often sits in familiar work: documents, spreadsheets, internal knowledge and the handoffs between teams.
I start with one of those jobs and the result the business needs. Platform choice follows from the task, the information it needs and the organisation’s approved ways of working.
Make the job specific
A team might need to check a paper against agreed criteria, prepare a structured first draft or find an answer in approved material. Work through real examples with the person who will use the result.
Question the process as you go. The useful solution may be a focused checker or a reusable skill, with fewer steps than the original request implied.
Choose the environment deliberately
Microsoft Copilot is a focus of my delivery work. I also work with OpenAI and Anthropic tools where they fit the job. The decision needs to account for approved access, data boundaries and how the team will use and support the solution.
Confirm those arrangements early. A build that depends on unavailable access has a delivery constraint to resolve before it can reach users.
Build the firm’s standards into the work
Provide the relevant templates, examples and review criteria. Make it clear when information is missing and where a person must approve the result. Package the useful instructions and checks so colleagues can reuse them.
Test with the business owner. Compare the full task with today’s method, including the time spent reviewing and correcting the output.
Give it a route into use
Agree how the solution will be published, who can use it and who owns it after handover. A bounded employee task may suit the fast delivery path. Core integration or greater operational consequence can require a different route.
Once the first workflow is in use, check its results and choose the next improvement. The aim is a repeatable way to improve work across the team.