A 1:1 workflow mapping session. Help them see their work as a system of flows, then build and name their first real workflow together. The barrier they walked in with: "I don't know what to automate." The shift they walk out with: "I see my work as a system of flows."
Facilitated by Adam Schlender · 45-60 minutes
00 · Before the session
Come in prepared
Circuit only works if you've done your homework. You should know their profile, their first build, and have at least one workflow candidate ready before you sit down.
01
Review their First Light profile
Pull up their First Light results. Look at the four dimensions: Energy (what drains them), Craft (what they love), Fit (role alignment), and Edge (growth areas). These scores tell you where the automation opportunities live.
02
Review their Spark Card
What did they build in Spark? What was the pain point they targeted? How much time did the first build save? Their Spark Card is a window into their current relationship with AI.
03
Identify 3 workflow candidates from First Light
Go back to their First Light transcript. The gold is in three questions:
Where to look
Q2: Work they dread (highest negative energy = highest automation value) Q9: Systems designed for someone else (processes that feel forced) Q11: Things they'd hand off if they could (delegation fantasies)
04
Pre-build one example workflow
Using their actual data from First Light, build a working prototype of one workflow in Claude. Have it ready to show, not as a finished product, but as a starting point they can touch. This removes the abstraction and makes it real from minute one.
Facilitator tip
The pre-built workflow is a conversation starter, not a deliverable. If they change direction in the session, let it go. The point is showing them what's possible, not locking them into your idea.
Check-In
Map
Build
Hand-Off
Bridge
01 · 5 minutes
Start with Spark
This is their third session. They've done First Light (discovery) and Spark (first build). Start by meeting them where they are.
Open with
"How did Spark go? Tell me about [their Creation Name]."
What to explore
Review their spark log: have they been using Claude daily since Spark? What patterns have emerged? Any wins they want to share?
Listen for
Energy level: Are they excited or drained? Confidence with AI: Do they talk about Claude like a tool or like a partner? Specific wins: Have they used their Spark creation since the session?
Check-In
Map
Build
Hand-Off
Bridge
02 · 20 minutes
Map the flows
Walk through their typical week together. The goal: sort every piece of their work into one of four categories. This is where "I don't know what to automate" dissolves, because the categories make it obvious.
Set the frame
"Let's walk through your week together. I want to map every kind of work you do into four buckets. Don't overthink it. We'll just talk through what a normal week looks like."
The four categories
Repeatable
Same steps every time. Process-driven. Predictable inputs, predictable outputs.
Ask
"What if Claude handled 80% of this?"
Creative
Requires judgment, intuition, taste. Can't be fully templated.
Ask
"What if Claude was your thinking partner here?"
Administrative
Scheduling, reporting, tracking. Necessary but not where their talent lives.
Frame
AI handles. They review.
Relational
People, communication, trust. The human work that can't (and shouldn't) be automated.
Frame
AI assists. Human leads.
Listen for
The tasks described with the most energy are the highest-value automation candidates. Even negative energy counts. If they light up describing how tedious something is, that's your signal.
Facilitator tip
If they're stuck categorizing, ask: "If you were sick for a week and someone had to cover for you, which of these could they do with a checklist, and which ones would they need to actually be you for?" Checklist tasks are Repeatable. "Be you" tasks are Creative or Relational.
Check-In
Map
Build
Hand-Off
Bridge
03 · 15 minutes
Build it together
Take their #1 workflow candidate from the mapping exercise and build it live in Claude. Their hands on the keyboard. You guide, they drive.
Transition
"Okay. Out of everything we just mapped, which one would change your week the most if it just... worked? Let's build that one right now."
Pick the workflow. Let them choose. If they can't decide, suggest the one with the highest frustration from the mapping grid.
Define the trigger. "What starts this workflow? An email? A Slack message? A time of day?" Every workflow needs a clear beginning.
Map the steps together. Walk through each step of the process as they do it today. Then rewrite it with AI handling the repeatable parts.
Build it in Claude. Open Claude together. Write the prompt together. Test it on real data from their work.
The naming ceremony. This is the moment. Ask them: "What do you want to call this workflow?"
"This is real now. It has a name."
Workflow name
What it does
Facilitator tip
Never take over the keyboard. Guide their hands, don't replace them. If they're stuck, say: "What's the most annoying part of this task? Start there." Name everything. Workflows, patterns, moments. Naming makes things real.
If they hit a wall
Watch for overwhelm signals, perfectionism, or "I should already know this." Use R&P language: "Here's a door, not a directive." The goal is one working workflow, not a perfect one.
Check-In
Map
Build
Hand-Off
Bridge
04 · 10 minutes
Let them fly
Transfer the workflow to their personal Claude. Then step back and watch them run it on their own. This is the proof moment.
Transfer. Copy the workflow prompt into their personal Claude instance. Make sure it's in their environment, not yours.
Watch. They run the entire workflow themselves while you observe. Resist the urge to jump in. Let them work through the small stumbles.
Celebrate. When it works, acknowledge what just happened. They built something that changes how they work. That's worth marking.
Listen for
If they hit a snag and debug it themselves without asking you, that's a strong readiness signal. If they ask "Can it also do [X]?" that's even better. They're already thinking in systems.
Check-In
Map
Build
Hand-Off
Bridge
05 · 5 minutes
Bridge to Current
Close the session by connecting what they just built to their daily life, then set them up for Current (the self-guided daily integration session).
Ask
"What shifts about your week if this workflow runs every day?"
Set the homework
"Between now and your next session, run your workflow daily. Every time you notice something repetitive, write it down. You're training yourself to see in systems now. That list becomes the starting point for Current, where you'll integrate AI into your daily rhythm on your own."
Explain Current
Current is the next session in the Superconductor Program. Unlike Circuit, it's self-guided. They'll take the system-thinking lens from this session and start integrating AI workflows into their daily work independently. Circuit gives them the first workflow. Current gives them the habit.
06 · After the session
Log and observe
Record what happened, flag readiness signals, and note anything that needs attention before Current.
Post-session steps
Log completion in the Training dashboard at /training
Record what was built, the workflow name, and what problem it solves
Note readiness signals and watch items for Current
Record your next session recommendation and any timing considerations
Readiness signals
What to look for
1
Uses Claude daily without prompting
2
Asks good follow-up questions to Claude (not just accepting first outputs)
3
Identifies automation opportunities independently ("I noticed this could be a workflow...")
4
Can explain their workflow to someone else in plain language
5
Said something like "this is just how I should work now"
Session capture
Named workflow
Other workflow candidates
Readiness signals observed
Watch items
07 · Session tracker
Circuit sessions
Track every Circuit session. The patterns across the team will tell you what's working and where people need more support.