1 min read
Architecture Matters - PART 5: Project Management Belongs in the Flow of Work
Mike Taylor
:
Updated on April 13, 2026
Most organizations don’t decide to do project management outside their flow of work. It just… happens.
If your company is Microsoft 365–centric, people are already doing project work every day inside the platform:
-
Meetings in Teams
-
Chats and channel conversations
-
Files in Teams channels/SharePoint
-
Tasks in Planner, To Do, Loop, and email
-
Decisions documented in conversations - not systems
THAT IS PROJECT MANAGEMENT. It’s just unmanaged, unconnected, and under-leveraged.
The architectural question isn’t: “What project tool should we buy?”
It’s: “Why would we move project management out of where work already happens?”
“Bringing PM into the flow of work” actually changes everything.
YOU STOP ASKING PEOPLE TO LEAVE WORK TO MANAGE WORK.
Instead, PM becomes an extension of collaboration, not a parallel system.
Here’s what that unlocks:
1. Less friction, more adoption (because nothing feels “new”)
Teams don’t have to:
- Learn another UI
- Duplicate updates
- Re-enter data
- Reconcile systems
Projects are where people already are. Adoption stops being a change management problem because the architecture aligns with behavior.
2. Automation that actually compounds
Microsoft 365 isn’t just collaboration. It’s an automation platform. When project data lives inside the tenant:
-
Power Automate orchestrates workflows
-
Approvals, notifications, and lifecycle flows stay connected
-
Automation is additive, not brittle integration glue
You’re not automating a tool. You’re automating how work moves.
3. Reporting that reflects reality - not last week
When work, conversations, tasks, and files live on the same platform:
-
Power BI doesn’t chase snapshots
-
Status reflects what’s actually happening
-
Reporting becomes near real time, not forensic
The question shifts from: “Is the project plan up to date?”
To: “What decisions do we need to make now?”
4. AI that understands context - not just tasks
This is where architecture becomes decisive.
Microsoft Copilot and agents can only reason across:
-
DATA IN YOUR TENANT
-
Conversations in Teams
-
Files in SharePoint
-
Tasks and plans tied to real work
When PM lives in the flow of work: AI stops being a feature… and becomes situational intelligence.
Bringing project management into the flow of work isn’t about convenience, it’s about compounding value. Every meeting, task, file, automation, and insight:
-
Reinforces the same system
-
Strengthens data gravity
-
Improves AI reasoning over time
That only happens when the architecture is right.
Features still matter. But where project management lives matters more.
Author's note: This post was originally shared on LinkedIn as part of a series