The AI Opportunity Is Already Inside the Workplace
If you manage a team right now, there is a good chance AI is already showing up in small, informal ways.
Someone may be using ChatGPT to draft an email. Someone else may be using Microsoft Copilot to summarize a meeting. Another person may be testing Notion AI to organize notes, outline a document, or get unstuck on a first draft.
That does not mean your organization has a mature AI strategy. It means the first stage of AI adoption may already be underway, whether leadership has formally named it or not.
This is where managers have an important role to play.
The practical question is no longer whether employees will try AI. Many already are. The better question is whether managers and leaders will help shape that use into something responsible, useful, and aligned with the business.
My concern is that too many organizations are waiting for a perfect AI roadmap while their teams are already learning in scattered, unsupported ways. That creates risk, but it also creates an opportunity. Managers can help bridge the gap between informal experimentation and responsible adoption.
What Phase 1 Really Means
The raw idea behind Phase 1 is simple: before a business starts talking about advanced automation, AI agents, or department-wide transformation, employees need to learn how to work with AI assistants in everyday tasks.
Microsoft’s 2025 Work Trend Index refers to this early stage as the Human + Assistant model. In plain language, that means each employee has access to an AI assistant that can help them work better and faster, while the employee still owns the judgment, review, and final output.
That distinction matters.
Phase 1 is not about automating jobs. It is not about replacing departments. It is not about turning every process into an AI workflow before the organization understands what it is doing.
It is about helping people use AI for practical support:
- Writing a cleaner first draft.
- Summarizing a meeting or document.
- Outlining a proposal, job description, or report.
- Generating options before a discussion.
- Rewriting a message for clarity.
- Organizing notes into next steps.
- Finding a starting point when the blank page is slowing the work down.
The work is still human. The AI helps people get to a better starting point faster.
That is a realistic first phase for many teams.
Why Managers Should Not Wait
There are three reasons managers should pay attention now.
First, the workload pressure is real. Microsoft’s 2025 Work Trend Index found that 80% of workers and leaders say they are too stretched to do their jobs well — and that 53% of leaders still expect productivity to rise.
Whether you are looking at a sales team, service team, HR team, operations group, or administrative staff, that tension is familiar: people are being asked to do more, respond faster, and keep quality high with limited capacity.
Second, employees are already testing AI tools. The same research found that nearly one in three employees already use AI tools several times a week. That matters because informal AI use without guidance can quickly become shadow AI.
Shadow AI is not always reckless. In many cases, it starts with good intent. Someone is trying to save time, improve a draft, organize information, or keep up with demand. But without clear expectations, they may put sensitive information into the wrong tool, trust an output without checking it, or create work that no one knows how to review.
Third, future phases of AI adoption will depend on the habits built now. If a team has not learned how to use AI assistants responsibly, it will be harder to move into more advanced use cases later. Automation, agents, workflow redesign, and AI-enabled operations all require a foundation of trust, judgment, review, and practical use.
Phase 2 will not work well if the organization is still uncomfortable with Phase 1.
What Phase 1 Can Look Like on a Real Team
The good news is that Phase 1 does not need to begin with a major software purchase or a complicated transformation plan.
A manager can start small.
The first step is to identify low-risk, everyday tasks where AI can help without taking over the work. That may include:
- Drafting internal emails.
- Summarizing meeting notes.
- Creating first-pass outlines.
- Editing for clarity.
- Brainstorming options.
- Turning rough notes into action items.
- Preparing questions for a meeting.
- Reviewing a document for tone or structure.
The key is to keep the use cases practical and visible.
From there, managers can create a few simple adoption habits:
- Ask for prompt champions: Identify a few people who are willing to test useful prompts and share what works.
- Run a weekly AI show-and-tell: Keep it informal. Ask, “What saved you time this week?” or “What did not work?”
- Create a one-page guardrail document: Clarify what is allowed, what needs review, and what data should not be entered into AI tools.
- Encourage output checking: Make it clear that AI can help draft or summarize, but people still need to verify accuracy.
- Capture examples: Save useful prompts, before-and-after examples, and lessons learned so the team is not relearning everything privately.
This is not about making AI use flashy. It is about making it normal, safe, and useful.
The Guardrails Matter
A practical AI pilot should not ignore risk.
Managers do not need a 50-page policy to start a responsible conversation, but teams do need basic boundaries. Every Phase 1 effort should answer a few simple questions:
- What kinds of tasks are appropriate for AI assistance?
- What information should never be pasted into an AI tool?
- Who is responsible for checking AI-generated work?
- When does an AI-assisted output need a manager or subject-matter review?
- Which tools are approved, tolerated, or off-limits?
- How should employees report a useful use case, concern, or mistake?
These guardrails do not have to be perfect on day one. They do need to exist.
Without them, employees will either avoid AI entirely or use it quietly. Neither outcome is ideal. Avoidance slows learning. Unmanaged use creates risk.
The practical middle ground is to give people permission to experiment within clear boundaries.
What Managers Gain
A responsible Phase 1 pilot gives managers better visibility into how AI can actually help the team.
You may find that AI saves time on routine writing. You may find that it helps newer employees get oriented faster. You may find that it reduces the friction of starting proposals, reports, or customer communications. You may also find places where AI is not ready, not accurate enough, or not worth the risk.
That is useful information.
The goal is not to prove that AI belongs everywhere. The goal is to learn where it helps, where it does not, and what your team needs before expanding.
A small Phase 1 effort can help a manager:
- Reduce unmanaged AI use.
- Build team confidence.
- Surface good examples.
- Identify training needs.
- Clarify data and privacy concerns.
- Give leadership real observations instead of abstract opinions.
- Prepare the team for more advanced AI adoption later.
That is the kind of practical evidence leadership needs.
How to Bring This Up with Leadership
If you are a manager and want to raise this with leadership, keep it simple.
You do not need to pitch a company-wide AI transformation. In fact, that may make the conversation harder than it needs to be.
A better approach is to frame Phase 1 as a contained productivity and learning pilot:
“I have been looking at Microsoft’s latest AI research and how teams are beginning with the Human + Assistant model. I think we have an opportunity to test a small Phase 1 pilot with our team. This would not be a major rollout or automation project. It would focus on basic productivity use cases, light guardrails, and shared learning so we can see what works, where the risks are, and what support the team needs before we expand.”
That kind of message does a few things well. It shows leadership that you are not chasing hype. It makes the risk manageable. It connects AI adoption to real work. It also gives the organization a way to learn before making bigger decisions.
Brand Perspective
At Sixth City AI, we believe practical AI adoption starts with real work, not buzzwords.
Managers are often the people closest to that work. They know where teams are stretched, where the repetitive tasks are, where quality slips, where communication breaks down, and where employees are already trying to make things easier.
That makes managers essential to the first phase of adoption.
The truth is, waiting for a perfect AI strategy may feel safe, but it can leave teams without guidance while informal use continues. Starting small, with guardrails and honest learning, is often the more responsible path.
Phase 1 does not have to be complicated.
Start with assistant-style use cases. Keep the human in control. Share what works. Protect sensitive information. Review the outputs. Learn from the pilot. Then decide what should happen next.
That is how AI adoption becomes practical instead of theoretical.
If your team is ready to explore a responsible first step, Sixth City AI can help you assess where to begin, what to avoid, and how to build a practical adoption path.
Practical Checklist
- Identify three low-risk tasks where AI could help the team draft, summarize, organize, or edit work.
- Ask whether employees are already using AI tools informally.
- Choose one or two prompt champions to collect and share useful examples.
- Create a one-page AI guardrail document for acceptable use, review expectations, and private-data boundaries.
- Run a short weekly AI show-and-tell for practical examples and lessons learned.
- Capture what works, what fails, and what needs leadership review.
- Use the pilot to inform a larger AI readiness or adoption conversation.