Week 5 · Partner Discovery
Meet Your Partner
Today you discover a real problem. The challenge: understand deeply enough to build something they couldn't ask for themselves.
Week 5 · Partner Discovery
Today you discover a real problem. The challenge: understand deeply enough to build something they couldn't ask for themselves.
A Note From Me
I want to be honest with you about where we are.
I'm not certain this is the best approach. But I'm reasonably confident it's directionally right. I'm exploring — and part of what I'm exploring is how to push more into human capabilities: the things that matter more, not less, in a world with AI.
That means I need something from you.
I need you to be partners in this, not just students following instructions. Push back. Tell me what's working and what isn't. Explore alongside me.
This class is designed to be different. If you just follow my instructions without thinking about whether they make sense, you're missing the point. The skill we're building — figuring things out when there's no clear answer — starts right here, with how we run this class together.
Partner Assignment
You'll work with this partner for the next 4 weeks. Your reflections and check-ins are pair-averaged — their effort affects your grade, and yours affects theirs.
Your job: solve a real problem for them. Not what they ask for. What they actually need.
The question isn't "what's wrong with your life?" — it's "what's harder than it needs to be right now?"
Discovery Technique
A discovery conversation isn't random. There's a pattern.
Ask about time, routine, frequency. Things they can answer without introspection.
"Walk me through a normal weekday." · "What are the top 3 things you spend time on outside class?"
Stories reveal what opinions hide. Don't ask what they think — ask what happened.
"Tell me about the last time you tried to study and it didn't work." · "Walk me through the last job application you started."
When they hesitate, trail off, laugh uncomfortably, or say "I guess" — that's the signal. Go there.
"You paused there — what happened?" · "You said 'I guess' — are you sure, or is something else going on?"
Reflect the pattern back. "So the problem isn't X, it's actually Y?" Let them confirm or correct.
"So you have the time — the problem is deciding what to do with it?" · "It sounds like the issue isn't that companies aren't responding — it's that nothing in your application gives them a reason to pick you?"
Sample Conversation 1
Move 1 — Start with facts. Easy to answer.
This is where most people stop. "Not hearing back" feels like the problem. Keep going.
Move 2 — Ask for the last specific time. Get concrete.
Move 3 — The pause before the answer is the emotional beat. They're realizing something.
Move 4 — Name what they can't see.
Surface problem: "I'm applying but not hearing back"
Real problem: No strategy for differentiation. Treating applications as volume game without understanding what makes a candidate stand out. Hasn't thought about their value proposition — what they specifically bring that others don't.
Sample Conversation 2
Move 1 — Facts. A Tuesday. No introspection required.
Move 3 — "I guess" is the signal. And notice the claim: "not long enough."
Move 2 — Making the specific moment concrete. What's actually blocking them?
Move 4 — Name the real problem.
Surface problem: "Everything's fine" (no problem at all)
Real problem: Decision fatigue about task prioritization. Has available time but loses it to the overhead of deciding what to do. Pattern repeats across the whole day.
Sample Conversation 3
Move 1 — Facts, with a useful distinction: time vs. energy.
Move 2 — The last specific time.
Move 3 — The emotional beat is in the admission.
Move 4 — Name the specific cognitive gap.
Surface problem: "School is stressful"
Real problem: Can't decompose confusion into specific questions. The gap between "I'm lost" and "here's what I don't understand" is where all the wasted time lives. That's a solvable problem.
What to notice
In every sample, the same thing happened:
Your partner's first answer is a starting point, not the answer. Your job is to get from the surface to the pattern underneath — without putting words in their mouth.
Live Demo
I need two volunteers. I'll interview one of you while the class watches the moves in action.
Your Turn
Interview your partner. Use the four moves. Listen more than you talk.
Use your notebook and pen to take notes. Not your laptop, not your phone. Handwriting keeps you present in the conversation and forces you to capture what matters, not transcribe everything.
Start with the questions you prepared in Goal Setting Part I. But follow the conversation — your best questions will come from listening.
Switch
Your partner interviews you. Answer honestly — they're trying to find your real problem, not the polite version.
Pay attention to something specific:
Setup + Exploration · 20 minutes
Set up the tools you'll use throughout Sprint 2. These aren't replacements for thinking — they're partners for going deeper on what you just heard.
Set up the Symbiotic Thinking Dojo structure in your preferred chatbot (ChatGPT, Claude, etc.). We'll walk through this together.
The Dojo's approach — enter a response, get AI feedback, go deeper — is how you'll process your discovery interviews and verify your thinking throughout the sprint.
Set up at least one of these. Your goal: have it ready to use this week, not just bookmarked.
Upload your discovery notes. Ask it to find patterns in what your partner said that you might have missed.
Have a tutoring conversation about your partner's domain — the area their problem lives in.
Create a project with your discovery notes. Use it as a thinking partner for exploring solution directions.
Explore domain-specific tools that help you build knowledge about your partner's problem area.
These are your thinking partners for the sprint — set them up now so you actually use them.
Debrief + This Week
The stated problem. The first answer. What they told you directly.
The pattern underneath. What you noticed between the lines. Where they surprised themselves.
If these two things are identical, you haven't gone deep enough yet. That's OK — that's what the Dojo is for this week.
Goal Setting Part II
Set goals based on what you actually heard — not what you assumed before today.
Discovery Deep Dive Dojo
Process what you heard with AI as thinking partner. Go deeper than your notes.
Assumption Audit AI-Discussion + Domain Learning Dojo
Surface your assumptions before building. Plan what you need to learn about their world.
Productive Reflection #4 📓 Handwritten
How do you know you're not just projecting? What assumption scares you most?