JJudgment, acceleratedPresenter guide
The exact click path + words

Make it feel simple.

Your job is to show three moments where AI improves judgment, not to teach every technical detail. The Lenny’s engine is the one deliberate exception: it proves this is a purpose-built tool, not a clever prompt.

Default stance: everything is pre-made except the clicks. Do not generate a draft, query a live system, or authenticate during the meeting.
Before anyone joins

Five-minute preflight.

If any item fails, use the static screenshots or speak to the artifact. Never debug in front of the room.

Open the enhanced URL with a fresh query string.
Confirm the top bar says “enhanced edition.”
Use 100% browser zoom; enter full screen.
Press right arrow through all six chapters.
Test Reveal, Trace, Walk, and Evidence once.
Return to #start and refresh.
Open roadmap.html in a backup tab.
Open team-pulse.html in a backup tab.
Mute notifications and close unrelated tabs.
Choose before the meeting

Ten minutes by default. Five if compressed.

The right-arrow key advances the story. Within the roadmap, click Walk. No other exploration is required.

Recommended

10-minute path

Enough space for the engine and one interaction per workflow.

Set the arc + guardrail

One story, three decision moments, invented data.

Ideate

One conviction, two questions, reveal the revised decision.

How the engine works

Build once, retrieve tension, trace one objection.

Align

Click Walk; show four planes moving together.

Deliver

Open ownership evidence; state human review.

Close

Restate ownership; propose one bounded pilot.

Buffer

Take one question or land the final sentence again.

Fallback

5-minute path

Keep the engine; remove supporting detail.

Start

Arc + invented-data guardrail.

Ideate

Read the original; reveal the conditional strategy.

Engine

Archive → evidence → disagreement → citation.

Align

Click Walk; name the four synchronized planes.

Deliver

Open the ownership evidence; one sentence on governance.

Close

Human ownership + one bounded pilot.

Exact talk track

Say this, then move.

The scripts are short on purpose. Let the artifacts prove the point.

00

Start · one operating habit

“I use AI at three moments in product work: before I commit, before I align a room, and while the team delivers. It challenges assumptions, makes a strategy tangible, and finds patterns across work I could not read at once. I still own every decision. These are invented working examples—production use stays inside approved tools and controls.”
Click · Begin the story
If interrupted: “The arc is Ideate, Align, Deliver. I’ll show the most distinctive part first.” Then advance to Ideate.
01

Ideate · from conviction to falsifiable choice

“Most people ask AI to draft. I use it first to find the assumption I have not tested, then retrieve the strongest argument against me. Here, a broad distribution conviction was hiding two different causes of weak attach: discovery and workflow fit. The AI did not polish the slogan. It turned it into a conditional strategy with a six-week decision gate.”
Click · Reveal revised decision → Right arrow
If interrupted: “The headline is that the output can now be proven wrong.” Skip straight to the engine.
01A

The engine · a new kind of tool

“This is the part I built, and the reason the result is different from a prompt. The system converted a frozen archive into more than fifteen thousand typed pieces of evidence, then connected more than four thousand pairs of genuinely opposing views. On a new draft, it brings in only the relevant defender, critic, condition, and source. It is a small reasoning system built around the work—not a model pretending to be four famous people.”
Click · Trace one objection → Right arrow
If interrupted: “Extract once, retrieve the relevant tension, return a source trace.” Then move on. Do not explain embeddings, batch APIs, or model names unless asked.
02

Align · from memo to shared future

“The AI read the chosen strategy and translated every stage across four planes: the customer experience, the platform capabilities underneath it, the value unlocked, and the controls required. When I change stages, all four move together. People stop arguing about bullet points and start reacting to the same thing.”
Click · Walk · then Send milestone request → Right arrow
If interrupted: Click Walk and say, “Customer, platform, value, and controls evolve together.” Move on.
03

Deliver · reconcile two signals

“This does not score people. It reads ticket prose, groups recurring system problems, links each theme back to evidence, and compares those patterns with an anonymous pulse. Here, the team ranked ownership fourth; the work record showed it was the second-most common delay pattern. The insight is not that the team was wrong. It may have normalized a chronic boundary.”
Click · Open linked evidence → Right arrow
If interrupted: Open evidence and say, “AI proposes the theme; a human checks every linked ticket before leadership sees it.” Move on.
04

Close · one responsible next step

“Across all three, AI handles interrogation and synthesis. I own the evidence, the decision, and the consequences. The next step is not a broad rollout. It is one bounded pilot in an approved environment, with read-only inputs, a named reviewer, and success and stop criteria agreed in advance.”
Stop here · invite questions
If time is up: End after the first two sentences. Do not reopen the presentation.
Language discipline

Credible, precise, bank-safe.

These swaps preserve the ambition without implying unapproved production use or autonomous decision-making.

Topic
Avoid
Use
Adoption
“I’m not waiting for permission.”
“I’m learning responsibly so I can help shape adoption.”
Capability
“What Chase tools can’t do yet.”
“An end state our approved toolchain can work toward.”
Agency
“AI does the work.”
“AI handles interrogation and synthesis; I own the decision.”
Expert panel
“Four real operators reviewed my memo.”
“The tool retrieved critiques grounded in their documented viewpoints.”
Team signal
“Tickets show what actually happened.”
“The pulse captures experience; the record captures how work moved.”
Gap
“The team under-reported ownership.”
“The team may have normalized a major source of friction.”
Likely executive questions

Short answers, no defensiveness.

Answer the question asked. Return to the human boundary if the conversation becomes abstract.

Is this already in production?

No. These are tested personal prototypes using invented data. They demonstrate the workflow. Production use requires approved tools, approved sources, security review, and the relevant control owner.

Why not just use a general chatbot?

A general chatbot can draft. The custom engine prepares a domain-specific evidence system, retrieves opposing support, returns source traces, and has an explicit weak-evidence fallback. The quality comes from the context architecture.

Are those experts really saying that?

The named critique is AI synthesis grounded in a dated documented viewpoint—not a direct quote or simulated participation. The source trail is visible, and a name is withheld if retrieval cannot support it.

Could this work with internal knowledge?

Yes, if the source is approved and the use is appropriate. The same pattern can organize internal research, decisions, policies, or operating knowledge without moving it outside the approved environment.

Does Team Pulse evaluate employees?

No. It is team- and system-level only. If it is used to score people, responses become less honest and the instrument stops being useful.

What happens when the AI is wrong?

Important claims must link to evidence and carry a status: verified, directional, or needs review. A human can reject or relabel them. Thin evidence produces an insufficient-data result—not confident filler.

Why a clickable mock instead of a deck?

Because the room can see customer experience, platform work, value, and controls change together. It turns an abstract roadmap into one shared object people can test.

What would you pilot first?

One bounded workflow with read-only inputs, a decision owner, a human reviewer, and explicit success and stop criteria. Napkin → Narrative is the lowest-data starting point.

Hard stop: never improvise a claim that real Chase data, customers, employees, or production systems were used. Never call AI synthesis a quote. Never offer to live-connect Jira or generate the full narrative in the meeting.