AI Driven PM: S2E1 - Stop Asking AI to Write. Start Asking AI to Think.

How to Turn Fuzzy Sponsor Dreams Into Clear Project Vision in Under 10 Minutes

Here's the thing nobody tells you at your PMP certification: You're not really a project manager.

You're a dream translator.

Every app you've ever loved, every bridge you've crossed, every streaming service you've binged—all of it started as somebody's dream. Your job? Make that dream come true without burning out your people or blowing up the budget.

But somewhere between the kickoff meeting and Sprint 37, we forget about the dream. We get obsessed with the date. The budget. The feature list. The Gantt chart that nobody reads.

And that's where projects go sideways.

The Elephant in the Room

Let's talk about the fear that's keeping half of you up at night: Will AI replace project managers?

Short answer? No.

Long answer? AI will never replace project management. But here's what I tell my consulting clients: You will absolutely be replaced by a project manager who knows how to leverage AI.

That's not a threat. That's reality.

I just read that IBM—the same IBM that said they'd stop recruiting for entry-level jobs because AI would handle it—just reversed course. They're doubling down on human hiring. Why? Because AI is effective, but human augmentation is where the real value lives.

AI can write your status report. It can't read the room when your sponsor's dream is dying and nobody wants to say it out loud.

The Value Paradox: Where Project Managers Actually Add Value

I ask my clients this all the time: What percentage of your week do you spend looking backwards versus looking forwards?

Looking backwards is updating documents, running status meetings, writing meeting notes, chasing down timesheets. There's some value there, but not much. You're reporting on things that already happened.

Looking forwards is anticipating needs, clearing blockers, mitigating risks, framing decisions, finding efficiencies. That's where all the value is.

So here's the real question: How is AI impacting project management?

It's shifting that percentage. It's letting you spend 80% of your time looking forward instead of 20%.

That's not automation. That's amplification.

The Problem With How You're Prompting AI Right Now

Most people treat AI like an intern.

"Rewrite this." "Summarize that email." "Make this sound more professional."

Commands. Tasks. Output.

And you know what? AI will do it. It'll give you exactly what you asked for—which is usually mediocre.

But here's what I've learned after 30+ years and 150+ PMO implementations: The best project managers don't command. They coach.

And if you want AI to actually help you think—not just type—you need to treat it like a thinking partner, not a typing service.

That's where Socratic prompting comes in.

What Is Socratic Prompting? (And Why It Changes Everything)

Instead of telling AI what to do, you ask AI to ask you questions first.

Here's the pattern:

Give AI a role (You're an expert project manager)

Ask AI to ask YOU clarifying questions (First, ask me 3 questions to understand the dream)

Tell AI to answer specific questions (Then answer: What's the vision? What are the outcomes? What are the risks?)

Ask for reasons, options, and trade-offs (Not just a single output)

This does two things:

You get better output because AI understands the context

You think better because the questions force you to clarify your own thinking

So instead of "rewrite this charter," you say:

"First ask me three questions. Then answer: What's the dream story? How does it motivate the team? What business outcome does this support? What mantra will keep us aligned?"

See the difference?

One gives you a document. The other gives you clarity.

Let Me Show You: From Fuzzy Idea to First Backlog in Three Prompts

I'm going to walk you through three prompts I use all the time. I ran these live in both ChatGPT and Claude (always use multiple tools—you'll get different ideas).

The example? An app idea I've had in the back of my head for years called Social Wishing—where people post bucket list items and their friends help make them happen.

Vague? Yes. That's the point.

Prompt 1: Vision Clarifier (Fuzzy Idea → Clear Vision)

Here's the prompt to copy:

You are an expert project manager and business analyst. I will share a vague idea from a sponsor.

First, ask me up to 3 clarifying questions to better understand the dream behind this idea.

Then, using my answers, help me think through the idea by answering these questions:

What is the clear project vision in 2–3 sentences?

What specific, measurable outcomes would show this dream came true?

Who are the key beneficiaries and how does this idea help them?

What are the top 5 risks or unknowns we should explore early?

Vague idea from the sponsor: [Paste Idea Here]

What happened when I ran it:

ChatGPT asked me:

When you picture this succeeding in 5 years, what's changed in people's lives?

Is this mission-first or venture-backed?

Who do you want to serve first?

Claude gave me a survey-style interface with options to select. Both made me think differently about the idea.

Then they gave me measurable outcomes:

"60% of posted wishes receive at least one concrete offer within 7 days"

"40% of wishes marked complete within 6 months"

I didn't come up with those. AI did. In about 90 seconds.

That's the power of asking AI to think with you, not just for you.

Prompt 2: Charter to Dream Story (Vision → Team Motivation + Mantra)

Once I had clarity, I needed to turn that into something my team could rally behind. Not just executives. The people actually building it.

Here's the prompt:

You are a senior project manager. I will share a project charter.

First, ask me up to 3 clarifying questions about the project and audience.

Then format the charter so that it explicitly answers these questions for executives and the team:

What is the dream story? (What are we ultimately trying to make true in the world?)

How does this dream motivate the team? (Why would they care about building it?)

What is the business outcome this supports? (How does it move a key metric or strategy?)

Is there a mantra or quick saying we can use to keep everyone aligned on the goal?

Present your output as:

1 short "dream story" paragraph

3–5 bullet points on team motivation

3–5 bullet points on business outcomes

3–5 candidate mantras/slogans

Project charter: [Paste Charter Here]

What I got back:

ChatGPT gave me this dream story: "Social Wishing exists to turn idle scrolling into human progress. We're building a platform where college students and retirees use their existing social networks to bring meaningful goals to life through shared skills, time, and encouragement."

Claude gave me: "For too long, social media has trained us to watch each other's lives instead of participate in them. Social Wishing flips that script."

I would use that line. I didn't write it. AI gave it to me because I asked the right question.

Mantras?

"Dreams deserve action"

"Scroll less, live more"

"Wishes are better out loud"

Again—10 minutes in, and I've got a vision, a team motivation story, and three mantras I can use in every standup to keep people anchored.

Prompt 3: Dream to First Backlog (Vision → Prioritized Features)

Now I need to get my product owner and team moving. I need an initial backlog that delivers early value and builds momentum.

Here's the prompt:

You are a product owner. I'll share a project vision.

Ask me 2–3 clarifying questions about scope, constraints, and what "first value" means to us.

Then help me think through the first backlog by answering these questions:

What are the 3–5 value themes that organize this work?

What 10–15 initial backlog items best deliver early value in those themes?

Why did you choose these as "first" items instead of others?

Vision statement: [Paste Vision Here]

What happened:

Both tools asked me:

What does "first value" mean? Someone posts a wish, or a wish gets fulfilled?

What's the absolute core if you had to cut everything else?

Then they gave me value themes:

Trust & Identity

Wish Clarity & Commitment

The Wish Loop

And 10-15 backlog items with rationale:

"First, completion requires clarity. Without structured wishes and a definition of 'done,' fulfillment rates will stall."

"Second, trust must precede action. If users don't trust identity controls, they'll only post safe or shallow wishes."

That's not a feature list. That's strategic prioritization.

And I didn't have to think it all up myself. I just had to ask the right questions.

Your Non-Negotiable Experiment This Week

Here's what I want you to do:

Use the Vision Clarifier (Prompt 1) on one real, fuzzy sponsor idea this week.

Not a fake example. A real one.

Notice:

How does the sponsor react when you ask clarifying questions?

How much faster do you get to the "why" instead of arguing about the "what"?

How much easier is it to explain the project once the dream is clarified?

Because here's the truth: When you talk to sponsors about their dream—not their project—the connection grows stronger, faster.

And that's where the real value of project management lives.

The Takeaway

AI won't replace you. But a project manager who knows how to think with AI instead of just commanding it? That person is going to run circles around you.

So stop asking AI to write.

Start asking AI to think.

And remember: You're not here to fill out forms. You're here to make dreams come true.

Want the full walkthrough with live demos? Check out Episode 1 of Season 2 of AI Driven PM on YouTube or wherever you get your podcasts.  YouTube Link: https://youtu.be/_Sz-GR-t9qk

Now go make a dream come true.

 

— Rick A. Morris

The Quiet Failure Killing Your Transformation

Your teams are not failing in the sprint.  They're failing two sprints earlier.

Every time a sprint goes sideways, leadership asks: "What happened in execution?"

Wrong question.

Most delivery failures don't start in build. They start upstream, in the work you thought was ready but wasn't.

The Pattern Leaders Keep Missing

Here's what I've been seeing across every client engagement, every industry, every methodology: Organizations adopt fast. They execute slow. And the gap between the two is massive.

Look at these numbers:

Domain	Adoption Rate	Success/Scale Rate	The Gap
AI implementations (McKinsey)	88%	10%	78 points
AI production deployment (Stanford)	78% of businesses	Low deployment	~60-70 points
Automation initiatives (Stonebranch)	98%	Persistent challenges	50+ points
Agile transformations	80%+ adoption	10-30% effective	50-70 points

This isn't coincidence. This is readiness debt at scale.

What's Really Happening

The pattern looks like this across every organization I work with:

1. Adopt quickly because modernization pressure demands it
2. Skip readiness because upstream preparation takes time
3. Fail during execution as readiness debt compounds
4. Declare success anyway while quietly missing business outcomes

"We're doing Agile."
"We implemented AI."
"We completed the sprint."

But the business impact never materializes.

That's not execution failure. That's readiness failure.

Loud Failure vs. Quiet Failure

Most leaders can spot loud failure:

• Project cancelled
• Team disbanded
• Initiative shut down

But quiet failure? That's everywhere, and it's invisible.

Quiet failure looks like this:

• Initiative declared "successful" but delivers no measurable outcome
• Framework adopted but discipline lacking
• Teams busy but not effective
• Technical success but business failure

The organization doesn't admit failure. It redefines success downward. Motion replaces progress. And the gap between adoption and results keeps widening.

Why This Keeps Happening

Multiple independent sources—across AI, automation, Agile, and ERP transformations—confirm the same root cause:

Implementation failures stem from inadequate upstream preparation, not technology limitations.

Forty-six percent of AI initiatives fail between proof-of-concept and production. That's not a technology issue. That's a readiness gap between "works in theory" and "scales in practice."

Automation studies highlight orchestration and governance gaps. That's upstream ownership failure.

Agile struggles rarely stem from stand-ups or retrospectives. They stem from unclear backlog ownership, unfinished decisions, and poor readiness discipline.

Different domains. Same pattern.

No one owns readiness before execution begins.

The Leadership Discipline That Closes the Gap

This is exactly why I created the 2-1-0 Execution Mantra. It's not just for Agile. It applies to any execution methodology.

2 means two units of work ready ahead. Product owns this.

1 means one unit fully designed and decision-complete. Architecture or enablement owns this.

0 means zero blockers when execution begins. Delivery owns this.

If you're not 2 ahead, 1 ahead, and 0 blocked, you're transferring risk into execution.

And execution is the most expensive place to discover risk.

The Real Executive Question

Stop asking:

• "What's the velocity?"
• "Why did we miss the sprint?"
• "Can we commit to more?"

Start asking:

• "Is the work truly ready before we commit?"

Because that 78-point adoption-execution gap isn't a methodology problem. It's a readiness discipline problem.

Until leadership owns readiness upstream, execution will continue to absorb avoidable risk.

The Bottom Line

Your organization doesn't struggle because it adopts too slowly. It struggles because it executes before it's ready.

Adoption is easy. Execution is hard. Discipline is what separates the 88% who adopt from the 10% who scale.

Before your next portfolio review, ask yourself one question:

Why are we allowing unready work into execution?

That's where predictability begins.

---

What's one thing your team committed to this sprint that wasn't truly ready? I'd love to hear your stories—hit me up in the comments or reach out directly.

 

AI Driven PM: AI Doesn’t Replace Project Managers—It Replaces Their Worst Tasks

 How I’m Using Prompt Engineering to Turn Reports Into Results

---

If you’ve ever lost half a day rewriting a status report for the fourth version of the same slide deck, you’re not alone. It’s one of the most frustrating parts of the job—and one of the least strategic.

That’s why I started using large language models (LLMs) like ChatGPT and Copilot. Not just for experimentation, but to systematically take work off my plate. But here’s the truth:

Generic AI gives you generic results.
Prompt engineering changes the game.

---

Why Prompt Engineering Matters (More Than You Think)

When most people talk about AI in project management, they focus on flashy dashboards or automated ticket creation. That’s fine—but it's not where the real leverage is.

The real impact happens when we combine clean project data with deliberate prompts—the kind that generate output we can actually use in executive reviews, steering meetings, and stakeholder updates.

“You can’t automate what you haven’t standardized.” — Rick Morris

Prompt engineering isn’t just writing a better question. It’s a system. And once you build it, the results speak for themselves:

• Weekly status reports in minutes, not hours
• Risk logs that auto-rate severity and recommend mitigations
• Steering decks that don’t require a weekend to assemble

---

The Three Prompts That Changed My Workflow

Here’s what I actually use week-to-week—no gimmicks, no fluff:

1. Status Narratives That Make Sense to the C-Suite

I feed in structured data from Jira, Smartsheet, or even a quick bullet summary. My prompt is tuned to produce something short, plainspoken, and focused on action.

Key Tip: Ask the LLM to quantify variance and end with a one-sentence ask.

2. Dynamic Risk Logs

Instead of manually rating every risk, I now have AI assign RAG status based on impact × likelihood. It also flags missing mitigations or inconsistent timelines.

Bonus: Add a Markdown or JSON output format so you can plug it straight into SharePoint or your PMIS.

3. Steering Committee Slide Drafts

I use a slide-friendly prompt that generates headlines, bullet points, and speaker notes—based on live data from my working files. I still review and polish, but I’m no longer starting from scratch.

“If you’re doing the same thing every week, it should be automated.” — Rick Morris

---

It’s Not Just About Speed. It’s About Focus.

The first time I used prompt engineering to prep a risk log, I cut my turnaround time by 80%. But the real win? I used those hours to coach a product owner through a launch delay instead of formatting slides.

Here’s what’s changed in my actual metrics:

• Status report time: Down from 6 hours/week to ~2
• Risk updates: From 2 days to under 4 hours
• Exec clarity: Survey scores on reporting jumped from 3.8 to 4.6 out of 5

“It’s not just about saving time. It’s about reallocating it to what matters.” — Rick Morris

---

What You Actually Need to Make This Work

You don’t need an AI team or a budget line. You just need a repeatable process:

1. Know where your data lives – PMIS, Confluence, Slack threads, spreadsheets
2. Standardize your outputs – Markdown for risks, JSON for status, PowerPoint XML for slides
3. Build and iterate your prompts – Make them tight, structured, and outcome-focused
4. Add guardrails – Validation scripts, human-in-the-loop reviews, compliance checks
5. Track the impact – Time saved, errors avoided, decisions accelerated

“A good process is one you don’t notice—because it’s working.” — Rick Morris

---

Final Thought: The Point Isn’t the AI—It’s the Outcome

LLMs didn’t make me a better project manager. What they did was give me time back—so I could show up where I was most needed: in risk meetings, in product launches, in conflict resolution.

Prompt engineering didn’t remove me from the loop. It just got rid of the noise.

“We don’t manage projects. We make dreams come true.” — Rick Morris

So if you’re spending more time narrating progress than driving it, prompt engineering might be your next best move. And if you want to see my actual prompts or workflows, just ask—I’m happy to share what’s worked and what didn’t.

Let’s build project management that works for the people doing the work.

AI Driven PM: The Future of AI and Project Management and How to Prepare

 What’s coming next—and are we ready for it?

AI is already changing how we manage projects. From automated reporting to risk forecasting, we’ve seen the early wins. But what’s around the corner is even more transformative. AI is evolving fast, and so is its role in how we lead teams, deliver outcomes, and shape strategy.

The next wave isn’t just about speeding up admin work—it’s about redefining project management itself. We’re talking about autonomous systems, intelligent collaboration, and real-time strategy support. The project manager of the future won’t just use AI—they’ll work with it.

Let’s look ahead at where AI is going in project management, and how we can prepare to lead with it, not just react to it.

---

1. Autonomous Project Management: From Assistant to Operator

Right now, most AI in project management acts like a very smart assistant—suggesting tasks, flagging risks, maybe generating a dashboard or two. But the next evolution is autonomy.

Autonomous project management systems will do more than assist; they’ll start to run day-to-day operations on their own.

🔍 What to expect:

• AI dynamically assigning and reassigning tasks based on availability, capacity, and project changes.

• Auto-generated status reports, meeting agendas, and risk updates—pushed in real-time to the right stakeholders.

• AI making low-risk decisions without human sign-off, freeing up PMs to focus on higher-value work.

💡 Why it matters:
It’s not about replacing project managers—it’s about giving them space to lead. Admin-heavy PM roles will shift toward strategy, alignment, and vision, while AI takes care of the tactical grind.

📌 How to prepare:

• Start identifying which parts of your current workflows are truly decision-based, and which are rule-based (i.e., can be automated).

• Test AI scheduling or task assignment tools now, so your team builds trust and familiarity early.

---

2. Predictive Analytics: From Risk Alerts to Outcome Forecasting

We’re already seeing AI used for early warning systems—flagging when a project is slipping or when risks might emerge. The future is more proactive and far more sophisticated.

Advanced predictive analytics will allow us to model entire project lifecycles, anticipate performance bottlenecks, and forecast ROI across multiple scenarios.

🔍 What to expect:

• AI generating “if-this-then-that” simulations based on real-time data.

• Forecasts that take into account human behavior, historical performance, even market or economic trends.

• Models that can recommend corrective actions, not just identify issues.

💡 Why it matters:
AI won’t just tell you there’s a problem—it’ll tell you what’s likely to happen next, and what to do about it. That’s a game-changer for both agility and strategic planning.

📌 How to prepare:

• Start capturing project data with an eye toward trends, not just metrics.

• Integrate predictive tools into retrospectives and planning conversations, even on a small scale.

---

3. Intelligent Collaboration: AI That Understands Teams

One of the most exciting (and underrated) trends is AI that understands how people work together.

The next generation of AI tools won’t just manage schedules and tasks—they’ll support team dynamics, flag potential miscommunications, and adapt collaboration processes to how teams actually work.

🔍 What to expect:

• Sentiment analysis tools that detect signs of burnout, conflict, or disengagement in team communications.

• AI-driven retrospectives that identify behavioral trends—not just task metrics.

• Intelligent meeting assistants that track decisions, assign follow-ups, and summarize key takeaways.

💡 Why it matters:
Project success isn’t just about task completion—it’s about team cohesion, communication, and clarity. AI that understands people adds a new layer to how we lead.

📌 How to prepare:

• Start tracking team engagement data—surveys, check-ins, communication patterns.

• Test AI assistants that can join meetings or summarize Slack/email threads, and evaluate their fit for your team’s culture.

---

4. Strategic AI: From Tools to Thinking Partners

The most transformative trend ahead? AI that helps you think. Not just act faster or automate smarter, but actually elevate how you approach complexity.

These AI systems will support strategic planning, scenario modeling, and real-time portfolio optimization.

🔍 What to expect:

• AI systems surfacing hidden patterns across multiple projects.

• Decision-support dashboards that weigh trade-offs and make recommendations based on business goals.

• Tools that link project outcomes to larger enterprise strategy—turning delivery metrics into strategic value.

💡 Why it matters:
Project managers are already being asked to act as strategic partners. AI will help close the gap between project execution and business value by translating delivery data into insight.

📌 How to prepare:

• Map your projects to business outcomes, not just milestones.

• Experiment with tools that connect delivery metrics to financial or operational KPIs.

---

What Does This Mean for Project Leaders?

We’re entering a new era where project managers must evolve from task managers to AI-augmented leaders. That shift isn’t just technical—it’s cultural, strategic, and human.

✅ The project manager of the future will:

• Collaborate with autonomous systems, not just operate them.

• Make decisions with predictive insight, not just historical data.

• Focus on enabling people while AI handles the process.

• Translate project data into strategy, not just execution.

This evolution won’t happen overnight, but it will happen. The teams that prepare now will lead the charge, not play catch-up.

---

Final Thoughts: AI Won’t Replace Project Managers—But It Will Redefine Them

AI is not just another software layer. It’s a catalyst for transformation, both in how we work and how we lead.

The future of project management isn’t just more efficient—it’s more intelligent, more adaptive, and more human-centered than ever before.

And the big takeaway? AI doesn’t remove the need for project managers—it reimagines the role entirely.

So, as we look ahead to autonomous systems, strategic decision support, and AI-driven collaboration—the question isn’t if you’ll use AI.

It’s how prepared you are to lead with it.

What AI trends are you watching—or already testing—in your projects? Drop your thoughts in the comments. Let’s look to the future, together. 🚀👇