Pick the scenario closest to your partner's problem. You'll step through a Dojo conversation — but at each step, you answer a question about the thinking before you see what happens next. This is exactly how your own session will work.
⏸ PARTNER PAUSE #1
"Walk me through yesterday — when you got an assignment, what happened in the first 10 minutes? Step by step."
⏸ PARTNER PAUSE #2
"Of those three — the quick skim, handing it off to future-you, or not tracking what you've deferred — which one, if it disappeared, would change your week the most?"
⏸ PARTNER PAUSE #3
"Would you actually use something that makes you pause and answer 'what is Thursday-you giving up?' — or would you skip it?"
Broad problem: Partner delays assignments all week, then crams.
Specific component: The "future self" handoff — deciding to defer without questioning the cost.
What I'm building: A daily 2-minute check-in via text. When he defers a task, he texts three things: the task, when he'll do it, and what that time was already claimed for. I respond: "Do you still want to make that trade?"
How he uses it: Once daily via text when he gets new assignments.
Measurable: Over 5 days, how many decisions change after check-in. If 2/5 change, something shifted.
Started thinking "productivity app." Ended with a text protocol. Three things made that happen: (1) the AI demanded minute-by-minute instead of the general story, (2) research on emotion regulation killed the "push harder" instinct, (3) the partner said "I'd think about it if someone asked me" — and that determined the form. Your partner will do the same if you ask the right questions.
⏸ PARTNER PAUSE #1
"Pick one evening last week where you wanted to do interview prep or sleep early but couldn't. What happened instead?"
⏸ PARTNER PAUSE #2
"Two things: the officer role that makes you show up, and the pressure to stay late. Which one, if it disappeared, would give you the most time back?"
⏸ PARTNER PAUSE #3
"What if before each meeting you text me when you plan to leave, and I text you? Would that help or would you ignore it?"
Broad problem: Partner overcommitted, losing sleep + interview prep time.
Specific component: The post-meeting social tail — can't exit when the meeting ends.
What I'm building: Pre-commitment + exit protocol. Before each event, they text me exit time and what they're protecting. I text when time's up. It's both reminder and social excuse.
How they use it: Before each club event for one week (~3-4 events).
Measurable: Hours reclaimed after meetings. Currently ~6 hrs/week lost. Leave on time for 3/4 events = 4+ hours back.
Started with "prioritization system." Ended with "a text before each meeting." The partner's Tuesday story revealed the decision point was after meetings, not during. "The excuse matters more than the reminder" shaped the final design. Your partner's story will show you where the intervention actually lives.
⏸ PARTNER PAUSE #1
"When was the last time you sat down to work on job stuff? Walk me through what happened from the moment you opened your laptop."
⏸ PARTNER PAUSE #2
"Three things happened: too many options, not knowing if you qualify, and switching to YouTube. Which one — if it disappeared — would get you to actually submit an application?"
⏸ PARTNER PAUSE #3
"Two options: paste a listing into a tool, or a one-page cheat sheet you keep open while browsing. Which would you actually use next Tuesday?"
Broad problem: Partner browses job listings without applying.
Specific component: Qualification uncertainty — can't quickly tell if a listing matches his level.
What I'm building: Personalized "Job Listing Cheat Sheet" — one page based on his resume and target roles. Keywords that signal entry-level vs. senior, his skills mapped to common requirements, apply/skip/stretch decision framework. Evaluates any listing in under 30 seconds.
How he uses it: Pinned tab next to LinkedIn. 3 dedicated search sessions this week.
Measurable: Listings evaluated per session (currently ~10, 0 apps) and applications submitted. Goal: 3+ applications across 3 sessions.
Started with "job application tracker." Ended with "a one-page cheat sheet for reading listings." The partner never needed a tracking system — he needed to know how to read a listing in 30 seconds. Career research on role clarity explained why browsing fails. The low-friction form came from his actual workflow. Listen for the failed attempt. The solution lives in the part that broke down.