Showing Work Without Showing Everything | Agentic AI and MCP for Product Managers

Agentic AI and MCP for Product Managers

What 'Agentic' Actually Means

The Autonomy Ladder

Why Most Things Called Agents Aren't

What This Course Covers

Tools Are the Interesting Part

What the Agent Remembers

Stopping Conditions

Copy This Prompt - Mapping Your Agent's Loop

Exercise - Trace Your Own Agent

The Problem MCP Solves

Servers and Clients

The Three Things a Server Offers

What MCP Gives You and What It Doesn't

Copy This Prompt: Working Out What You'd Connect To

Exercise: Map Your Connections

Why Tool Design Is Product Design

Names and Descriptions

What a Tool Returns When It Fails

Copy This Prompt - Designing Your Tool Inventory

Exercise - Write Your Tool Inventory

Three Categories, Not Five

Where the Approval Goes

Approval Fatigue

Designing the Approval Moment

Copy This Prompt - Designing Your Permission Model

Exercise - Build Your Permission Model

Why the Final Answer Isn't Enough

Trajectory Evaluation, Plainly

A Test Set of Tasks, Not Questions

The Four Things to Measure

Copy This Prompt - Building an Agent Test Set

Exercise - Build and Run an Agent Eval

Why Cost Per Task Has a Long Tail

Where the Seconds Go

Loops, Retries and Runaways

Budgets and What Happens at the Limit

Copy This Prompt - Modelling Agent Cost

Exercise - Model Your Costs and Set Your Caps

The Waiting Problem

Showing Work Without Showing Everything

Interruption, Correction and Undo

Building Trust One Delegation at a Time

Copy This Prompt - Designing the Agent Experience

Exercise - Design the Experience

The Blast Radius Question

Prompt Injection When the Agent Can Act

Compounding Errors

Rehearse the Incident

Exercise - Work Out Your Blast Radius

Five Situations Where a Workflow Wins

Agent, Workflow, or Just a Button

What Agents Structurally Struggle With

Reducing Autonomy Instead of Adding Capability

Copy This Prompt - Checking Whether You Need an Agent

Exercise - Check Your Own Choice

Lesson FP.1: What You're Producing

Prompt Library: Understanding the Task

Prompt Library: Designing Tools

Prompt Library: Permissions

Prompt Library: Evaluating

Prompt Library: Cost and Caps

Prompt Library: Experience and Risk

Prompt Library: Checking Yourself

Words Explained: Glossary

Lesson 2

Showing Work Without Showing Everything

The full trace is too much, nobody wants to read every tool call and raw result. But a summary alone gives the user nothing to check. The answer is layered disclosure.

Three Layers

LAYER 1 - ALWAYS VISIBLE (while running)

Checking shipment status...

Found: held at customs since 4 March

Checking customs records...

Found: missing form C88

Drafting update...

LAYER 2 - THE RESULT

Shipment 44182 is held at Felixstowe customs because

form C88 was not submitted. Estimated release is 2-3

working days after submission.

[Draft update ready for review]

LAYER 3 - BEHIND "SHOW DETAIL"

Every tool called, arguments, raw results, timings.

Nobody opens this until something looks wrong,

and then they need all of it.

Layer 1 builds trust. Layer 2 is the product.

Layer 3 is how users and your support team

debug a bad result.