Agile 2026 · Future of Work & Careers
AI & The PM:
Redefine Your Role
Before AI Does.
Dave Prior & John Tanner
Today
Four chapters. Forty-five minutes.
01
Introduction & Setup
00:00 to 00:15
AI already changed your job. Let's establish that and talk about where you are in the journey.
02
Professional Identity Reset
00:15 to 00:20
Your PM identity needs a reframe. The role isn't dying. It's evolving. We'll show you how.
03
Real World Scenarios
00:20 to 00:35
Dave walks through AI-powered time reports from Slack. John walks through PMO as Code. Real tools, real results.
04
Things To Do Right Now
00:35 to 00:45
Specific actions you can take this week to build your AI skills and keep delivering value.
👤
Your host
Dave
Prior
AI Productivity Coach & PM
Agile Coaching
AI Adoption & Practice
PM Leadership
👤
Your host
John
Tanner
PMO Strategist & AI Practitioner
PMO Strategy
AI Implementation
Stakeholder Leadership
Where to find us
[Link placeholder]
[Link placeholder]
[Link placeholder]
[Link placeholder]
Grab everything now
All session resources in one place.
Chapter 01 · 00:00 to 00:15
Introduction
& Setup
AI already changed your job. Let's establish that and figure out where you are in the journey.
Let's start here.
AI is not going to show up
and change your job.

AI already changed your job.

That ship has sailed.
Quick show of hands
Who's in
this room?
We're making three assumptions about you. See which one fits.
Which one are you?
The Skeptic
You don't want to be the "prompt guy." You want to understand AI in context, not just play with toys. You're here to figure out what's real.
The Overwhelmed
Too many tools, moving too fast, no clear starting point. You've been waiting for someone to cut through the noise and tell you what actually matters.
The Curious
You're already experimenting. You want to go deeper and know what's actually worth your time. You're ready for the next level.
The journey
6 Stages of AI Adoption by a PMP
1
Uncertainty
"This is probably a fad." Then: "Oh no."
2
Fear & Dismissal
"I don't need to learn this." Then: "Everyone else knows it."
3
Anger & Frustration
"This is replacing me!" Then: "What do I even do now?"
4
Anxiety & Loss
"My skills don't matter." Then: "Do I start from scratch?"
5
Resignation
"I give up trying to keep up." Then: "...okay, let's try."
?
Stage 6.
DRUNK
WITH CLAUDE.
You stopped fighting it.
You started winning with it.
Four things to accept right now
01
It changes faster than you will ever be able to keep up with.
02
There will always be someone in the room who seems to understand it better than you.
03
That person also has no idea what they are doing.
04
Everyone in this room has FOLS.
F — O — L — S
Fear of
Looking Stupid.
It stops more PMs than any other force in AI adoption.
You will look stupid.

So will everyone around you.

And you'll all grow from the experience together.
Why it felt so hard
Why AI
scared us
so much.
It's moving too fast
Evolving faster than any documentation, training course, or expert can track.
Confidence is not competence
Everyone acts like they know how to use it well. Almost no one does — yet.
The vendors don't help
Every tool claims AI can handle project management. That's the sales pitch, not the reality.
Chapter 02 · 00:15 to 00:20
Professional
Identity
Reset
Reframe your PM identity for an AI-driven world.
Honest question
How many of you worry that AI is going to take away your job?
🤔
The real problem
The collapse
of understanding.
Organizations no longer agree on what PMs are for.
Schedulers, not strategists
Over 15 years, the PM function got reduced to spreadsheet management and meeting coordination.
The tool became the job
PMs were told their job was to update the schedule and make sure meetings got recorded. Full stop.
When PM becomes reporting, everyone loses
The organization loses its strategic partner. PMs lose their seat at the table.
No one is coming
to save you.
The people who need to fix this — to redefine the role of PM, Program Manager, Portfolio Manager, and PMO — is us. We're the ones who remember what it's for.
Chapter 2 conclusion
The PM role,
reimagined with AI.
AI doesn't replace the PM. It frees the PM to do what only a PM can do.
Clarity
Know what's happening.
AI surfaces project health in real time. You stop chasing status and start leading on it.
Strategy
Own the decisions.
PMs who use AI shift from task-tracking to strategic decision support. That's your value.
Value
Prove it, don't just claim it.
The PM function is not disappearing. It's being modernized by those who adapt.
Chapter 03 · 00:20 to 00:35
Real World
Scenarios.
Dave and John walk through what this actually looks like in practice.
Dave's scenario
Time reports
from Slack.
Export Slack messages. Feed to Claude. Get a structured time-spent report. No spreadsheets.
The problem
Time tracking is painful, inaccurate, and nobody trusts it. It never reflects what actually happened.
The solution
Export a Slack channel, prompt Claude, get a clean breakdown of where time actually went — per person, per project.
The payoff
Managers trust the data. Teams stop wasting time filling out timesheets that no one reads.
How it works
The workflow.
Three steps from Slack export to trusted report.
Step 1: Export
Pull the Slack channel export. This is a standard feature — no special access needed.
Step 2: Prompt
Feed the export to Claude with a structured prompt asking for time spent by person and project.
Step 3: Review
Claude returns a clean breakdown. You review, adjust if needed, and share. Done in minutes, not hours.
John's scenario
PMO
as Code.
Your project context, stored as Markdown. Your AI reads it and answers anything.
The problem
Project knowledge lives in slides, spreadsheets, and people's heads. It's scattered, stale, and locked in proprietary tools.
The idea
Store your project context as plain text files in a Git repository. Version-controlled, portable, and readable by any AI.
The result
Ask Claude anything about your project and get an accurate, sourced answer — without scheduling a status meeting.
Breaking it down
What "as Code" actually means.
Treat your project knowledge like software. Version-controlled, structured, AI-readable.
Markdown files
Plain text, always.
Status updates, decision logs, risk registers — all written in Markdown. No proprietary formats. Any tool can read it.
Git repository
Version control for your project.
Every change is tracked. You can see what was decided, when, and by whom — just like code.
AI context window
Load it, then ask anything.
Point Claude at your project folder. Now it knows your project as well as you do. No re-explaining context every session.
Portable & durable
Survives tool changes.
When the org switches tools — and it will — your project knowledge comes with you. Plain text never goes stale.
Chapter 04 · 00:35 to 00:45
Things To
Do Right
Now.
Specific actions you can take this week. No vague advice.
Action 1
Stay current.
Read.
AI Daily Brief is Dave's daily habit. Libby for longer reads. Even 10 minutes a day compounds fast.
Listen.
Follow practitioners, not pundits. Find people actually using the tools, not just talking about them.
Experiment.
Use Claude or ChatGPT on a real work question today. Break something. Learn from it. Then share what you found.
Action 2
Build your
Personal Context
Portfolio.
What is it?
Documents that tell your AI your role, your writing voice, your projects, and your context. Think of it as your AI onboarding kit.
Why do it?
Every new AI session starts cold. A Personal Context Portfolio ends that — permanently. Stop rebuilding context from scratch.
Start here
play.aidailybrief.ai/episodes/personal-context-portfolio
Action 3
Teach AI
to write
in your voice.
Give it samples
Provide 5 to 10 examples of your own writing: emails, status updates, meeting recaps. The more real, the better. Don't clean them up.
Ask it to describe your style
Have Claude write a style guide based on your samples. Review it, correct it, then save it to your Personal Context Portfolio.
Version-control it
Export as Markdown and store in GitHub. Retrain over time. Your AI voice gets sharper with every iteration.
Action 4
Build a
knowledge base
about your project.
Daily spoken updates
2 to 3 minutes of audio about your project each day. Voice-to-text, then Claude structures it into a clean entry.
Store as Markdown
Export, version-control in GitHub. Your project now has persistent, queryable memory that follows you across tools.
No more lost context
"What did we decide about the vendor issue last month?" Answered in seconds from your own notes.
AI is not here
to do your job.
It's here to partner with you. Help you surf the chaos. Power up your ability to do what only you can do. Be vulnerable with it. Let it be your devil's advocate.
Tentanda
via est.
The way must be tried.
Remember: no one in this room really knows what they are doing. Neither does anyone outside of this room. Now is the time to decide what we are doing, together.
Where to find us
[Link placeholder]
[Link placeholder]
[Link placeholder]
[Link placeholder]
Keep going
Thanks for being here. Start experimenting today.
Q&A
Dave Prior & John Tanner
Agile 2026