The host prefers action-based meetings in which participants solve problems or work through material together. Routine updates are moved to asynchronous Loom recordings, while synchronous time is reserved for collaboration and selected one-on-ones.

Reserve meetings for active collaboration
Move routine updates to asynchronous channels
Use Loom for status communication
Keep one-on-ones where they add value

“I, for the most part, want all meetings to be action based and everything else to be async.”
09:30

“If that's like updates, I try to get it async via Loom.”
09:30

#async work#meetings#loom#collaboration

Explainer· 1

Explainer04:00

What an AI-Generated Project Brief Can Reveal

The generated project brief goes beyond a superficial progress summary. It identifies goals, current performance, differentiation questions, resource concerns, discovery opportunities, and risks such as content saturation or stalled growth.

Expose growth and execution concerns
Identify missing discovery opportunities
Prepare strategic questions before meetings
Review budget and resource implications

“Questions to prepare for. Again, think about this for your own project.”
04:30

“So just goes through this whole prep of all of the things you need to know to be prepped for any kind of project.”
04:30

#project risk#strategy#meeting preparation#ai

Tool· 4

Tool01:00

Use AI to Predict the Agenda for Your Next One-on-One

The first prompt searches email history and shared project documents to predict five topics that a colleague will likely want to discuss. Connecting the model to tools such as Gmail, Google Drive, Calendar, Asana, and HubSpot gives it enough context to produce a useful meeting agenda.

Search prior communication with the attendee
Include project and one-on-one documents
Ask for five likely discussion topics
Connect the model to relevant workplace systems

“What are five topics they'll likely want to discuss?”
01:00

“This way you can actually preempt what are the most important things to talk about.”
01:30

#ai prompts#meetings#one-on-ones#productivity

Tool03:00

Generate a Real Project Update From Eight Weeks of Communications

The second prompt reviews recent project communications and drafts a status update containing performance indicators, blockers, and questions. The demonstration shows how AI can consolidate scattered operational information before a project meeting.

Specify the project being reviewed
Set a defined communication window
Request KPIs and blockers
Generate questions to prepare for

“Review all project communications for marketing against the green from the past eight weeks and draft an update with KPIs, blockers, and questions I should…”
03:00

“It can pull out your current performance indicators.”
03:30

#project management#status updates#ai prompts#kpis

Tool05:00

Ask AI for the Probability That a Project Will Hit Its Deadline

The deadline reality-check prompt asks the model to assess a project using its documents and recent email updates. Instead of returning a binary prediction, the model can provide a probability score alongside positive indicators, risks, critical-path requirements, and actions that could improve the odds.

Name the project and deadline
Ground the assessment in recent evidence
Request a probability score
Review risks and critical-path work
Ask how to improve the probability

“You want to say what's the probability we'll hit a certain deadline, and then you want to give it the actual project.”
05:00

“And so what it does, it will come back with a probability score.”
05:30

#deadlines#risk assessment#project management#ai prompts

Tool07:00

Use AI to Audit Whether You Work or Just Attend Meetings

The fourth prompt analyzes a month of calendar and email activity to explain how time is actually being spent and suggest productivity improvements. The host emphasizes that the resulting analysis is only as reliable as the underlying calendar data.

Analyze one month of calendar and email activity
Categorize meetings, work, and leadership time
Identify productivity problems
Improve calendar data before trusting the analysis

“So analyze my calendar in email for the past month. Tell me how I'm actually spending my time and how I can be more productive.”
07:00

“I think one of the things you want to do is be really rigorous about how you use your Google calendar.”
07:30

#time audit#calendar#productivity#ai prompts

Takeaway· 4

Takeaway06:00

Turn a Deadline Forecast Into a Concrete Leadership Decision

A useful deadline analysis should clarify the most likely delivery scenario and expose the tradeoff leadership must resolve. In the example, AI distinguishes a partial October launch from full feature parity in November and frames the choice directly.

Distinguish partial delivery from full completion
State the most likely outcome
Translate uncertainty into an explicit tradeoff
Ask leadership to choose scope or delay

“You would likely achieve a partial launch by October, but maybe November for full feature parity.”
06:00

“Key question for leadership, would you prefer limited but functional October launch or a delay to November?”
06:00

#leadership#scope#deadlines#decision making

Takeaway08:00

Your AI Time Audit Fails When Work Blocks Are Missing

The host discovers that unrecorded evening work and inconsistently scheduled focus blocks distort the model's conclusions about meeting load and peak meeting days. The practical lesson is to record all meaningful work blocks, not only the periods that need protection from meeting requests.

Record evening and off-hours work
Add focus blocks consistently
Do not treat every calendar block as a meeting
Correct the source data before interpreting patterns

“And so that's actually lesson number one is put everything in your calendar.”
08:30

“This is why I want to make sure that I'm actually marking all of this out correctly”
09:00

#data quality#calendar#focus time#time management

Takeaway11:00

Why Thirty-Minute Gaps Become Wasted Time

The calendar analysis identifies fragmented scheduling as a productivity problem. The host agrees that thirty-minute gaps between meetings are too short for deep work and often get consumed by Slack and lightweight communication instead.

Avoid alternating meetings with short open blocks
Protect longer periods for deep thinking
Treat fragmentation as a scheduling cost
Batch communication into appropriate windows

“Many 30-minute blocks may not allow deep thinking.”
11:00

“I really struggle with meeting 30 minutes, meet in 30 minutes, and that 30 minutes I just find I'm totally unproductive.”
11:00

#deep work#context switching#calendar#productivity

Takeaway12:00

AI Leadership Prompts Depend on Access to Real Work Data

The episode closes by stressing that the prompts are portable across Claude, Gemini, and ChatGPT. Their usefulness depends less on the chosen model than on whether it can access the calendars, messages, documents, and project systems needed to ground its response.

Use the prompts with multiple major AI assistants
Enable connectors to workplace data
Ground responses in current organizational information
Expect weaker results when key channels are unavailable

“You can use it in Claude, Gemini, or ChatGPT.”
12:00

“They'll all work as long as you have the connectors and they can access that information.”
12:00

#connectors#claude#gemini#chatgpt#workplace ai

Frameworks in this episode

Action-or-Async Meeting Rule

Deadline Reality Check

Real Project Status

Smart Meeting Prep

Work-or-Meetings Time Audit

Insights & moments

◆Hot Take· 1

Meet to Do the Work, Not Merely to Share Updates

✶Explainer· 1