Module 18 · Lesson 01

Running Executive AI Sessions — The Biweekly Rhythm

Reading time: 17 minutes Track: Yungsten Tech Employee Curriculum · Consultant path

The biweekly session: purpose and principles

The biweekly 90-minute C-suite session is the heartbeat of a Yungsten engagement. It's where decisions get made, priorities get set, and the client's leadership team develops their own AI judgment — not just receives Yungsten's.

The session is not a status update. It's not a demo. It's a working session where the client's leadership team does real work with AI tooling while we facilitate and teach.

Core principles:

• The client does the driving. We set up the prompt, explain the framework, then hand over the keyboard.
• Every session produces at least one concrete artifact (a decision, a document, a revised process).
• The session teaches a pattern, not just a task. The client should be able to replicate the pattern independently.

Session structure: 90 minutes

Opening (10 min)

• Quick wins from the past two weeks: what's the team using, what worked?
• Session agenda and what we'll produce today
• Any blockers or issues from the past two weeks

Teaching segment (20 min)

Introduce one new pattern, concept, or capability. Keep it directly relevant to their current work — not generic AI theory.

Examples:

• "Today we're going to cover how to use Claude for your board update draft"
• "We're going to set up a new prompt pattern for your sales pipeline review"
• "Let's talk about how to debug when the agent gives an unexpected answer"

Working segment (45 min)

The client leadership team works on a real task using the pattern you just taught. Your role: observe, coach when stuck, prompt better prompting.

The task should be something they actually need done this week — not a practice exercise.

Debrief and documentation (15 min)

• What did they learn? (Ask them — don't tell them)
• What worked, what didn't?
• What goes in the wiki from this session?
• What's the one thing they're going to do differently this week?

Preparation checklist

Before each session:

• Review the previous session notes in the wiki
• Check what agent work is in progress — are there things to demo or review?
• Identify the teaching topic based on where the client is in the engagement
• Have a real task ready for the working segment (ask the client's EA 48 hours in advance: "what's a real piece of work [executive name] has this week that would be good to work on in our session?")
• Prepare the session notes template (pre-fill date, attendees, agenda)

What makes a session work vs. fail

Works:

• Client is doing the driving, not watching
• The work produced in the session is real work, not practice
• Something changes in how they operate after the session
• The session notes capture what was learned and decided

Fails:

• Yungsten is doing all the prompting while the client watches
• The session is a status update rather than a working session
• Nothing tangible was produced
• The client can't replicate the pattern the next day without you

If sessions are consistently falling into the "fail" pattern, address it directly: "I'd like to change how we run these sessions — let's shift so you're doing more of the driving and I'm coaching."