Kênia Sousa
Business, Process & Data Analysis
Embracing the AI Shift: Copilot and the New Era of Work
Let’s talk about the elephant in the room: Artificial Intelligence (AI) is changing the way we work, fast. While some jobs are being redefined or even replaced, new roles and opportunities are emerging just as quickly. But disruption isn’t new in the world of Information Technology (IT). Rapid change is part of the DNA of our industry. Once again, we’re being called to adapt, grow, and embrace the opportunities this new wave brings.
A powerful tool transforming our workplace today is Microsoft Copilot, a productivity-boosting assistant powered by Large Language Models (LLMs). Its purpose? To free us from repetitive tasks and let us focus on creative thinking and strategic decision-making.
What is Microsoft Copilot?
Copilot integrates directly into the Microsoft 365 ecosystem, including Word, Excel, Teams, Outlook, PowerPoint, to provide intelligent support. It can summarize meetings, draft emails and reports, generate presentations, and extract insights from large datasets.
Think of it as your intelligent assistant that learns from your data and context to offer you insights.
The Momentum Behind Copilot
Microsoft reports that hundreds of large organizations are now rolling out Copilot to all employees, across industries like finance, healthcare, education, and retail. According to “Microsoft’s 2025 AI Trends report”, generative AI adoption jumped from 55% in 2023 to 75% in 2024 with momentum expected to further accelerate across industries in 2025.
However, some organizations are lagging behind due to concerns about data security, AI regulation, or integration complexity. Accenture’s “Front-runners’ Guide to Scaling AI” (May 2025) reveals that only 8% of companies are true front-runners scaling AI across the enterprise.
However, these challenges shouldn’t prevent progress, especially when Copilot can deliver tangible value through targeted, manageable use cases. In the next sections, I’ll share practical examples of how Copilot can automate key tasks from root cause analysis to workflow orchestration, demonstrating that even cautious adopters can take meaningful first steps toward AI-enabled transformation.
Real Work Automation Examples with Copilot
Here are some key activities worth exploring using Copilot in my daily work.
Data Analysis
Use Case: Analyze historical and contextual data from emails, spreadsheets, and documents to give quick insights.
Example: Copilot analyzes several data reports and highlights red flgs that require special attention that could be missed if done manually.
Advantages: Fast access to data insights, trends and forecasts.
Drawbacks: Requires high-quality, clean data, risk of over-reliance on generated insights.
Root Cause Analysis
Use Case: Leverage historical data to identify clusters, flag unusual variations and highlight top contributors for current challenges.
Example: Copilot analyzes patterns in incidents, identifies correlations between incident types, and surfaces contributing factors.
Advantages: Speeds up insight generation, accelerates troubleshooting.
Drawbacks: Quality of output depends on data labeling, may miss rare but critical edge cases not well represented or outside the available data.
Brainstorming
Use Case: Suggest draft content, templates, and alternative formats.
Example: Copilot generates multiple headline options and presentation outlines for a marketing campaign.
Advantages: Speeds up content generation, helps overcome creative block.
Drawbacks: Limited originality because it draws from existing content, may limit out-of-the-box thinking.
Automate Workflows
Use Case: Connect to external platforms (e.g. Salesforce, Confluence) through plugins to automate tasks across systems.
Example: Copilot can auto-update Salesforce from Outlook emails via an external connector.
Advantages: Seamless cross-platform integration, end-to-end process coverage.
Drawbacks: Requires connector setup, possible data privacy challenges without proper data classification or role-based access controls.
Monitor Impact
Use Case: Track process improvements, calculating ROI from time savings, efficiency, and error reduction.
Example: Copilot aggregates usage logs and time savings to calculate ROI on Copilot adoption, highlighting areas that where people need training.
Advantages: Transparent benefit tracking, objective insight into ROI and gaps.
Drawbacks: Harder to quantify intangible benefits, requires clear measurement baselines.
Collect User Feedback
Use Case: Summarize feedback from surveys, emails, and tickets to support process improvement efforts.
Example: Copilot summarizes customer support tickets and flags top pain points monthly.
Advantages: Real-time insights from sentiment analysis, flags recurring pain points.
Drawbacks: May misinterpret sentiment or context.
Whether we’re streamlining decision-making, surfacing insights from sensitive data, or automating tasks that span multiple systems, it’s essential to ensure Copilot is used in a way that respects data governance, privacy regulations, and ethical AI principles.
Looking Ahead
AI is here and it’s changing how we work. I see it as a call to evolve.
Copilot is helping us be more productive and focus on the work that matters: thinking critically, connecting with people, and creating value. Many, if not all of these tasks need human review and expert interpretation, so I see Copilot not as a threat, but as our ally.
I’m in for embracing this shift together and I’m ready to lean into AI to shape the next waves.
But what about the impact on critical thinking? With AI handling more of our cognitive load, there’s a risk it may weaken our ability to question, analyze, and think independently. The challenge ahead isn’t just adopting AI, it’s doing so in a way that keeps our human skills sharp. Are you concerned about that?
To explore more, check out the official “Microsoft Copilot Adoption Playbook”
“Microsoft’s Responsible AI Guidelines”
Continue reading...Product Owner and Process Engineer
I just got my certification as a Scaled Agile Framework (SAFe) “Product Owner and Product Manager” and I want to share my initial thoughts on how Product Owners and Process Engineers collaborate to enhance products and services.
As a Process Engineer, I collaborate with different teams to improve processes while a Product Owner collaborates with agile teams to deliver products or services to customers. I see several commonalities between their roles and mindset. Here are my top 3:
Continue reading...What I read in 2024

Kênia Sousa
Recent Posts
-
The Science of Choice
-
Rolling out Enterprise Architecture
-
7 Steps to Create Processes
-
First thoughts on Prediction Machines
-
The woman I am
-
Becoming a Runner
-
Business Process Overview
-
How to link Business Rules with Business Objects
-
Analysing Open Data from the Canadian Government with Python
-
Analysis of an Infographic according to Alberto Cairo's mechanisms
-
Git: How to know if your directory is already under version control?
-
Changing R library path
-
Shiny Application to analyse graduates per country and year
-
I don’t like boxes, do you?!
-
Need a solution to integrate a BPM and IT