Welcome to Problem Framing

I'm glad you're here. Before we dive in, let me explain what we're doing together and why it matters.

What is Problem Framing?

Problem framing is the diagnostic work that happens before you start solving. Most teams jump straight to solutions—"Let's build this feature" or "Let's try this strategy." But without a clear understanding of what problem you're actually trying to solve, you end up building the wrong thing or solving symptoms instead of root causes.

Problem framing is different. We're going to work together to:

1. Define the problem precisely — Transform vague complaints into a clear, actionable problem statement
2. Map the boundaries — Understand where the problem exists and where it doesn't (contrasts reveal patterns)
3. Identify root causes — Drill past symptoms to understand why the problem exists
4. Analyze forces and constraints — Map what's pushing toward a solution and what's blocking it
5. Synthesize everything — Produce a self-contained Problem Framing document that serves as a complete handoff for Problem Solving

By the end of this session, you'll have a clear diagnostic picture that prevents false starts and wasted effort.

What We'll Produce

A Problem Framing document that captures:

• A refined problem statement (specific, observable, bounded)
• Problem boundaries (where it exists, where it doesn't)
• Root causes and contributing factors
• Forces supporting and resisting solution
• A Framing Summary that's complete enough that someone could start solving from it alone

This document becomes your north star—it keeps everyone aligned on what problem you're solving before you argue about how to solve it.

Context I've Reviewed

I've reviewed your project context document on the Productized Service SaaS for Coaches. Here's what stands out as relevant:

• Core insight: Coaches are trapped in manual admin work and hourly billing models because they lack a fast, professional way to sell productized services
• Target users: Independent coaches and audience-owners (Substack writers, podcast hosts) who have credibility and reach but no monetization infrastructure
• Value prop: A 5-minute checkout experience that enables coaches to escape hourly billing and feel professional
• MVP scope: Six core features focused on speed and simplicity (Stripe-first onboarding, pre-filled dummy page, split-screen editor, combined checkout + intake, auto-generated subdomain, one-click publish)

This context gives me a foundation, but I want to hear directly from you about the problem you want to frame.

Let's Begin: Your Problem

Now I'd like to understand what problem you want to frame. This could be:

• A problem with the product itself — Something about the MVP isn't working as expected
• A go-to-market problem — Uncertainty about how to acquire customers or position the solution
• An organizational problem — Something about how the team is working or deciding
• A strategic problem — Uncertainty about direction, timing, or market positioning
• Something else entirely — A different challenge you're facing

What problem would you like to frame today? How did you first notice it, and why does it matter to you right now?

This is a really important observation, and I appreciate the specificity. You've done the diagnostic work to isolate the exact moment where things break down—and that's actually valuable data. Let me make sure I understand the gap clearly before we move forward.

Clarifying the problem you're describing:

You have:

• 120 signups → 83 published services (69% activation, which is strong)
• 83 published → 5 first sales (6% conversion from publish to first customer, which is the problem)

The gap isn't in the product (people can publish). The gap is in what happens after publish—specifically, the moment where coaches need to actually share their link and ask their audience to buy.

A few clarifying questions to make sure I have the full picture:

On the 5 who did make a sale:

• Do you know what was different about those 5? Did they share immediately after publishing? Did they have larger audiences? Were they audience-owners (Substack/podcast) or regular coaches?
• How much time elapsed between when they published and when they made their first sale?

On the 78 who haven't made a sale:

• When you reached out, what were the most common reasons you heard? ("Still tweaking," "Haven't shared yet," "Not sure how to promote it," "Worried about the price," "Haven't had the right client come along yet"?)
• How long have they been sitting on a published service without sharing? Days? Weeks?

On the churn:

• Are the people going quiet the ones who published but didn't share, or is there a different pattern?
• How many have actually cancelled their subscription vs. just gone dormant?

I want to understand this gap from multiple angles before we frame it. The silence you're hearing from coaches is the real clue—it tells us something about the psychological or practical barrier they're hitting right at the moment of truth.

You just said something really important, and I want to make sure we're seeing it clearly together.

"They're tweaking because tweaking feels like progress without having to do the scary thing."

That's not a product problem. That's a psychological barrier problem. And it's hiding inside what looks like a product activation problem on the surface.

Let me reframe what I'm hearing:

The surface problem: "Coaches publish their service page but don't share it, so they don't get customers, so they churn."

The real problem underneath: "Coaches are hitting a moment of vulnerability—the moment where they have to actually ask their audience for money—and they're finding ways to delay that moment indefinitely by tweaking, waiting for testimonials, waiting for conditions to be 'perfect.'"

The product got them 95% of the way there. It removed the blank canvas problem, the technical friction, the "how do I build this" barrier. But it didn't solve the emotional job: overcoming the vulnerability of asking for money and feeling like a legitimate business doing it.

And here's the thing—your positioning actually promised to solve that emotional job. Your context document says:

"The emotional job (overcoming vulnerability and feeling professional) drives adoption more powerfully than features."

But the product solved the operational job (build a professional page) without solving the emotional job (feel confident enough to actually ask). So coaches built the page, felt professional for a moment, and then hit the wall when it was time to actually use it.

Before we go deeper, I need to understand the full context of this moment:

1. When coaches publish, what happens next in your product? Do they see a celebration moment? Do they get a prompt to share? Or do they just... publish and then the product goes quiet?

2. In your customer conversations, when someone says "I'm still tweaking," what happens if you push back gently and ask "What specifically feels wrong about it?" Do they have a real answer, or does it become vague?

3. The 5 who did share—did they experience a different moment after publishing? Did they have someone waiting to buy (the warm pipeline cases)? Or did the audience-owners just... push through the vulnerability moment differently?

I'm asking because I want to understand: Is this a product problem (missing a critical moment in the flow) or a positioning/messaging problem (we're attracting people who aren't ready to ask for money)? Or is it both?

What's your gut telling you?

Okay, now we're getting somewhere real. And I want to make sure we frame this precisely before we go deeper.

You've identified two potential problems:

1. Product abandonment at a critical moment — The experience ends right when coaches need the most support (pushing them to actually share)
2. Customer fit problem — You're attracting coaches who aren't psychologically ready to ask for money, when your ideal customers are audience-owners who have built-in forcing functions

Both could be true. But I want to be really careful here because the frame we choose determines what we investigate and what we solve.

So let me ask you directly: What problem do you actually want to frame right now?

Is it:

A) "How do we get the 78 coaches who already published to actually share their link and make their first sale?" (This assumes they're viable customers, just stuck at a specific moment)

B) "Why are we attracting coaches who aren't ready to ask for money, and how do we fix customer fit?" (This assumes the real problem is upstream—we're selling to the wrong people)

C) "How do we redesign the post-publish moment so coaches feel supported to share instead of abandoned?" (This assumes the product itself has a critical gap)

D) Something else — a combination, or a different angle entirely?

The reason I'm asking is that each of these is a different problem to frame. A is about activation/behavior change. B is about positioning and ICP. C is about product design. And the diagnosis method we use, the root causes we uncover, and the solutions we generate will be completely different depending on which problem we're framing.

What matters to you most right now? What's the problem that, if solved, would change the trajectory of this business?

Perfect. You've just articulated something really clear, and I can feel the conviction in it. Let me make sure we sharpen this into a precise problem statement that will guide everything that comes next.

You said: "Coaches publish a professional service page and then go quiet because the product abandons them at the exact moment they need a forcing function to actually share it."

That's a strong starting point. But before we finalize it, I want to probe a few dimensions to make sure we're capturing the full problem—not just the symptom, but the core issue.

Let's Refine This Together

First, on the gap between what you promised and what you delivered:

You said you sold coaches on "feeling professional and legitimate." That was the emotional job. But when I look at your product, it solved the operational job (build a professional page in 5 minutes) without solving the emotional job at the moment it matters most.

So the real problem might be: You created a product experience that delivers on one emotional promise (professionalism) but breaks a different emotional promise (confidence to actually ask for money).

Does that feel accurate? Or is the problem more about the specific absence of a forcing function (the missing post-publish moment)?

Second, on who this problem affects:

You said "coaches go quiet." But from what you've told me, it's specifically coaches without warm prospects and without a built-in audience forcing function who go quiet. The audience-owners and coaches with pipelines didn't need the forcing function because they already had one.

So is the problem: "Coaches without external forcing functions publish and then go quiet"? Or is it broader than that?

Third, on what "abandonment" really means:

When you say the product "abandons" them, you mean: the product goes silent, offers no next step, provides no support or momentum at the moment they need it most. But I want to make sure we're clear on what they need at that moment.

Is it:

• Practical support (here's how to share, here's a template email, here's who to send it to)?
• Emotional support (you can do this, it's okay to ask for money, here's proof others succeeded)?
• A forcing function (a deadline, a public commitment, a ritual that makes sharing feel inevitable)?
• All of the above?

What do you think the coaches who went silent actually needed at that moment?

Fourth, on the scope of the problem:

Is this problem specific to the post-publish moment? Or does it point to something bigger—that your product is designed around the creation job (build a page) but not the sales job (actually use the page to sell)?

I'm asking because the frame we choose determines what we solve. If it's just the post-publish moment, we add a forcing function and move on. If it's bigger, we might need to rethink the whole flow.

What's your sense?

You're being really honest with yourself, and I respect that. You know where the bigger issue lives, but you're choosing to frame the problem at the point where it becomes visible and actionable. That's smart—it keeps you grounded and prevents paralysis.

So let me synthesize what you've told me and propose a refined problem statement. Then we'll test it against what you're actually experiencing.

Refined Problem Statement

Coaches without external forcing functions (warm prospects, audience commitments) publish their service page but don't share it with their audience because the product provides no forcing function or social proof at the exact moment they need both to overcome the vulnerability of asking for money.

Let me break down what's in here:

• Who: Coaches without external forcing functions (narrower, more precise than "all coaches")
• What: They publish but don't share (the observable gap)
• When: Right after publishing (the specific moment)
• Why: The product abandons them at that moment and provides no forcing function or social proof (the root cause of the gap)
• The emotional job: Overcoming the vulnerability of asking for money (the deeper promise that's breaking)

Testing This Against Reality

Before we lock this in, let me make sure it captures what you're actually seeing:

1. Does this statement explain the 78 who froze? Yes—they published, had no external forcing function, got no forcing function from the product, and went quiet.

2. Does it explain the 5 who succeeded? Yes—three had audience forcing functions, two had warm prospects. All had something making them push through.

3. Does it point toward what needs to be fixed? Yes—the post-publish moment needs to provide a forcing function and social proof for coaches without external ones.

4. Does it avoid the "whole product is broken" spiral? Yes—it's scoped to the post-publish moment, which is where the problem becomes visible and actionable.

Now, the Context & Success Criteria

Before we move forward, I want to capture a few more things:

On prior attempts:

• Have you tried anything to address this gap yet? (A follow-up email sequence, a Slack notification, anything?)
• What feedback or signals told you it wasn't working?

On constraints:

• What's the constraint on your side? (Time, engineering resources, runway, something else?)
• What constraints exist on the coaches' side? (They're bootstrapped, they're skeptical of "tactics," they're introverted, something else?)

On stakeholders:

• Who needs to agree that this problem is worth solving? (Just you, investors, a co-founder?)
• Who will be affected by how we solve it? (The coaches, your business metrics, something else?)

On success:

• If we frame this problem well and then solve it, what would success look like?
• Is it "more of the 78 actually share and get their first sale"?
• Is it "we learn which of the 78 are actually viable customers"?
• Is it something else?

What's your answer to those?

Perfect. You've given me everything I need to build a solid problem frame. Let me synthesize this into a complete Problem Definition section, and then we'll move into the next phase.

Problem Definition Summary

Refined Problem Statement: Coaches without external forcing functions (warm prospects, audience commitments) publish their service page but don't share it with their audience because the product provides no forcing function or social proof at the exact moment they need both to overcome the vulnerability of asking for money.

Problem Context:

You launched the MVP two months ago and have 120 signups with 83 reaching publish (strong 69% activation). However, only 5 of those 83 have made their first sale to a real client—a 6% conversion from publish to first customer. The gap isn't in product quality or feature completeness; the pages work and look professional. The gap is behavioral and emotional.

You've identified a clear pattern: the 5 who succeeded all had external forcing functions pulling them through the vulnerability moment (warm prospects already in pipeline, or audience-owner status with public commitments). The 78 who froze are coaches without those external forces. They publish, then experience silence from both the product and their own courage, and go quiet. Most have been sitting on published pages for 10-45 days without sharing once. Churn is visible: 15 have formally cancelled, and ~63 more are dormant and will churn at renewal.

The coaches' stated reasons for not sharing are delay language ("still tweaking," "waiting for testimonials," "not sure who to send to first"), but when probed, these reasons are vague and post-hoc. The real barrier is psychological: they're experiencing the vulnerability of asking their audience for money and finding ways to postpone that moment indefinitely.

You attempted a basic intervention three weeks ago—a 24-hour post-publish email with a link and encouragement to share. Open rates are 50%, but behavior hasn't changed. This suggests a passive nudge is insufficient; coaches need something more active (a forcing function) and something more human (social proof from peers, not just a product prompt).

You've also noticed that the coaches freezing are disproportionately introverts, writers, and thinkers—people who are allergic to anything that feels gimmicky or salesy. They're mostly bootstrapping on the side of day jobs, so their windows of courage and energy are limited. Any solution must feel like peer support, not marketing tactic.

Constraints & Context:

• Your constraint: Solo founder, 7 months of runway. You can ship something meaningful in 1-2 weeks but can't build a whole new product surface. Solution must be lean.
• Their constraint: Introverted, allergic to sales tactics, limited energy windows, bootstrapping on the side. Any forcing function must feel like coaching, not marketing.
• Stakeholder: Just you. No investors or co-founder, so you can move fast on conviction.
• Problem category: This is a performance gap — the product is working (people publish) but not delivering the outcome it's supposed to (people sell).

Success Criteria:

• Primary metric: Publish-to-first-sale conversion rate. Current state: 6%. Target: 25% within 60 days on a new cohort. This is the headline win that proves the post-publish moment matters.
• Secondary metric: Customer fit clarity. The solution should also act as a diagnostic—if coaches still freeze even with a forcing function and social proof, that signals the customer fit problem (B) is real and upstream.
• Framing success: A problem statement that explains the 78 who froze, explains the 5 who succeeded, points toward what needs to be fixed in the post-publish moment, and avoids the "whole product is broken" spiral.

Now I'm going to generate the initial Problem Framing document skeleton with the Problem Definition section filled in. This will give us a working document that we'll build on through the remaining steps.

Ready for Step 3?

We've got a solid problem definition. The refined statement is clear, specific, and grounded in data. The context is rich enough that someone reading this would understand exactly what's happening and why it matters.

Now we move into Step 3: Diagnose & Bound the Problem using an Is/Is Not Analysis. This will map the exact boundaries of where the problem exists and doesn't exist—which will reveal patterns that point toward root causes.

Are you ready to move forward? Any adjustments to the problem definition before we go deeper?

That's a really smart flag, and I appreciate you naming it upfront. You're right—with only 5 successes, we're working with a small sample. But that's actually okay for this phase of diagnosis.

Here's why: Is/Is Not Analysis isn't about statistical proof. It's about mapping the boundaries of where the problem shows up and where it doesn't, so we can see contrasts that point toward root causes. Even with a small "doesn't exist" sample, the contrasts between the 78 who froze and the 5 who succeeded will be directional and valuable. We'll treat the patterns as hypotheses to test, not certainties.

You've already done some of this analysis in our conversation. You know:

• The 5 who succeeded had external forcing functions; the 78 don't
• The 5 shared within 72 hours; the 78 have been sitting for 10-45 days
• The 5 audience-owners didn't need much from you; the coaches without pipelines froze

Now we're going to be more systematic about it and look across multiple dimensions to see what else distinguishes the two groups.

Let's Map the Boundaries

I'm going to walk through the dimensions of Is/Is Not Analysis. For each, I'll ask about the problem cases (the 78 who froze) and the non-problem cases (the 5 who succeeded). We'll look for contrasts and patterns.

Let's start with WHERE the problem exists:

WHERE does the problem occur?

• Geographically, are the 78 distributed globally or concentrated in certain regions?
• By coaching niche, are they all in the same space (executive coaching, life coaching, health coaching, etc.) or spread across niches?
• By platform/audience type, are they mostly solo practitioners with no audience, or a mix?

WHERE doesn't the problem occur?

• The 5 who succeeded—what's their distribution? (3 audience-owners, 2 coaches with warm prospects)
• Are there any other segments where you've seen people publish and not freeze, even if they haven't made a sale yet?

What's your sense of the WHERE dimension?

Excellent. You're already seeing the contrasts, and that last observation is really important—you've just identified a third group that's distinct from both the successes and the frozen. Let me capture that and keep going.

So we have:

• Group A (5): Published + shared + made a sale = had external forcing function
• Group B (8-10): Published + shared + no sale yet = different problem (execution/market fit, not courage)
• Group C (60-65): Published + never shared = the frozen group we're framing

The fact that Group B exists is valuable. It tells us that some coaches can overcome the vulnerability moment and actually share. We'll come back to that.

Now let me probe the contrasts you're seeing:

On coaching niche: The life coaches are frozen, the executives and creators aren't. That's striking. Let me understand this better:

• Why might life coaches be more frozen than executives? Is it because life coaches are more introverted? Less used to selling? More vulnerable about their positioning? Or something else?
• The two executives who succeeded—what's different about them? Are they more comfortable asking for money? More used to sales conversations? Do they have more credibility in their field?
• The 3 creators who succeeded—are they frozen on the coaching part of their business, or did they just treat it as an extension of their existing platform? In other words, did they overcome the vulnerability, or did they skip it by leveraging existing audience trust?

On audience type: All 5 successes had something—either a real platform or a real pipeline. None of the 78 frozen had either. That's a clean contrast.

But I want to probe this:

• Of the 8-10 in Group B who did share but didn't get a sale—did they have a platform or pipeline? Or did they somehow push through without one?
• The coaches with "small email lists in the low hundreds"—are any of them in the frozen group or the sharing group? That might tell us if there's a threshold of audience size that matters.

What's your read on these questions?

Okay, this is really clarifying. Let me map what we're seeing across the WHERE dimension and then we'll move through the other dimensions.

WHERE — Summary of Contrasts:

The emerging pattern: The problem doesn't exist for people who either (1) have an existing platform with engaged audience, (2) have a warm prospect in pipeline, or (3) are experienced at sales/charging. It exists for coaches who are new to sales, have soft positioning, and have no external forcing function.

Now let's move to WHEN — the time dimension. This is about understanding the temporal pattern.

WHEN does the problem occur?

• At what point in their coaching journey are the frozen coaches? (New coaches? Established but transitioning? Something else?)
• How quickly after publishing do they go silent? (You mentioned 10-45 days—is there a pattern within that range?)
• Is there a time of day or day of week when coaches are more likely to share or freeze?

WHEN doesn't the problem occur?

• The 5 who succeeded—how quickly did they share after publishing? (You said 72 hours for all of them—is that a pattern?)
• Did the timing of when they signed up matter? (Early cohort vs. later cohort? Seasonal patterns?)

What's your read on the WHEN dimension?

You've just identified something critical: the 72-hour window is the entire game. That's not just a timing observation—that's a leverage point. If you can't move coaches to share in the first 72 hours, you've lost them. After that, momentum is gone and you're fighting inertia.

Let me capture that and keep moving through the remaining dimensions of Is/Is Not Analysis.

WHEN — Summary of Contrasts:

Now WHO — the people dimension. We've touched on this, but let's be systematic.

WHO is affected by the problem?

• You've identified life coaches as disproportionately frozen. Are there other demographic or psychographic patterns? (Age, gender, introversion/extroversion, educational background, previous career?)
• You mentioned coaches are "allergic to anything that feels gimmicky or salesy"—is that equally true across all 78, or are some more open to tactics than others?
• Are there personality or mindset patterns that distinguish the frozen from the sharers in Group B?

WHO isn't affected?

• The 5 successes: what do they have in common beyond "external forcing function"? (Confidence? Sales experience? Comfort with being seen? Something else?)
• The 8-10 in Group B who did share: what was different about them psychologically? What gave them the courage to press send even without a guarantee of results?

What patterns do you see in the WHO dimension?

WHO — Summary of Contrasts:

Now let's move to WHAT — the nature of the problem itself.

WHAT is the problem?

• You've said it's "coaches don't share their page." But is it specifically the email send that's hard, or is it something broader (telling people in person, sharing in a group, posting on social)?
• Is it the asking for money that's hard, or the visibility of asking?
• Is it the commitment (once I send this, I'm a coach charging money) that's hard, or the rejection risk?

WHAT isn't the problem?

• It's not product quality (pages look professional)
• It's not lack of knowledge (they know how to send an email)
• It's not the price being wrong (almost nobody complained about pricing)
• What else isn't the problem?

What's your read on WHAT the actual problem is, at its core?

You just said something that cuts to the core: "The product helps them build the artifact of a coaching business without helping them claim the identity of being a coach who charges."

That's the real problem. Not the page. Not the email. Not the mechanics. The problem is identity claim—making public, legible, and permanent what was previously private, ambiguous, and deniable.

Let me capture the WHAT dimension and then synthesize everything we've uncovered.

WHAT — Summary of Contrasts:

Synthesizing the Boundaries

Now let me pull together all the dimensions and ask you to validate the emerging pattern.

The 78 who froze have:

• Early career stage (1-3 years, mostly side practice)
• Introverted, perfectionist psychology with high identity stakes
• No prior experience with public visibility or asking for money
• Soft positioning (life coaches, personal development) that feels vulnerable
• Made a decision NOT to share in the first 72 hours
• A page that sits unshared because sharing it requires claiming an identity publicly

The 5 who succeeded all had:

• An external forcing function (warm prospect or audience commitment) that made the identity claim feel inevitable or less risky
• Either prior experience claiming a public identity (creators, execs) OR a specific person already expecting/asking for their service
• Shared within 72 hours, riding momentum from setup completion

The 8-10 in Group B (sharers but no sale) had:

• Slightly more psychological resignation and lower emotional stakes
• Existing audience habit that normalized the act of asking
• Enough platform to share (courage) but not enough reach (market fit)

The pattern that emerges:

The problem doesn't exist when coaches either:

1. Have an external forcing function (someone already asking, or public commitment made)
2. Have prior experience with public identity/visibility/asking for money
3. Have made peace with possible failure and lowered the stakes
4. Have an existing audience relationship that softens and normalizes the ask

The problem exists when coaches have none of these—when claiming the identity publicly feels like a permanent, high-stakes, irreversible decision with no external support or normalization.

Validating the Boundaries

Before we move to root cause analysis, I want to ask you:

Does this boundary map feel accurate? Are there contrasts I'm missing or overweighting?

And one more important question: In the 72-hour window, what's the difference between a coach who shares and one who doesn't? Is it something you can observe in the product (time spent, pages visited, etc.)? Or is it purely psychological—something that happens in their head, not in the product?

That distinction matters for what we diagnose next.

Perfect. You've identified both the boundary pattern AND a critical insight about the product's role in the freeze: the editor becomes a hiding place. Coaches use it to create the illusion of progress without facing the identity decision. That's a symptom, not a cause—but it's a symptom you can see and potentially interrupt.

Let me now synthesize everything into the Is/Is Not Analysis section and update the document.

Validation

Does this Is/Is Not Analysis capture the boundaries accurately? Are there patterns I'm missing or misweighting?

And importantly: Are you ready to move into Step 4 — Root Cause Analysis? We've mapped where the problem exists and doesn't exist. Now we need to drill into why the frozen coaches make the decision not to share in that 72-hour window, and what's sustaining that decision.

Perfect. I've noted the editor-as-hiding-place insight—it's a critical signal and we'll make sure it's visible in the analysis.

And I appreciate you naming what you're bracing for. You're right that we might land there, and you're also right that we shouldn't dance around it. Root cause analysis is about truth, not comfort. If the root cause is "I promised an emotional solution and delivered an operational one," that's valuable to know because it changes what we solve for.

But let's not assume the answer yet. Let's diagnose it systematically.

Root Cause Analysis: Choosing Your Method

We have several diagnostic methods available. Let me present them and you choose which one feels right for this problem:

1. Five Whys Root Cause Best for problems with a linear cause chain. You start with the problem (coaches don't share in the 72-hour window) and ask "Why?" five times, each answer becoming the subject of the next question. Fast, focused, good for getting to a single root cause. Works well when you suspect a straightforward causal chain.

2. Fishbone Diagram Best for complex problems with multiple contributing factors across different categories (people, process, product, environment, psychology). You'd explore: What people factors contribute? What process factors? What product design factors? What environmental/cultural factors? Good when you suspect multiple causes interacting.

3. Systems Thinking Best for problems embedded in interconnected systems with feedback loops and delays. You'd map: What are the system components (coaches, product, identity, audience, etc.)? What relationships exist between them? What feedback loops sustain the freeze? Where are the leverage points? Good when fixing one thing seems to create problems elsewhere, or when the problem sustains itself through circular dynamics.

Given what we've uncovered, here's my recommendation:

I'd suggest Fishbone Diagram, because we've identified multiple contributing factors across different dimensions:

• People factors: Introversion, perfectionism, high identity stakes, no prior sales experience
• Product factors: The product abandons them at the critical moment, the editor enables hiding
• Process factors: The 72-hour window, the decision made in the first 3 days
• Psychological factors: Identity claim as the core barrier, not mechanics
• Environmental factors: Coaches bootstrapping on the side, limited energy windows, allergic to sales tactics

A Fishbone would let us systematically explore each of these and see which factors are root causes vs. contributing conditions.

But you might prefer Five Whys if you want to drill straight down to the single core reason. Or Systems Thinking if you want to understand how all these factors create a self-sustaining loop.

Which approach resonates with you? Or would you rather combine two of them?

Excellent. You've thought this through clearly. Five Whys first to pressure-test the linear chain and force you to name the root honestly. Systems Thinking second to understand the self-sustaining loop and find the real intervention points.

Let's start with Five Whys.

Five Whys Root Cause Analysis

We start with the problem statement: Coaches without external forcing functions publish their service page but don't share it because the product provides no forcing function at the moment they need it most.

More specifically: In the 72-hour window after publishing, coaches make the decision not to share and then spend the next 10-45 days slowly accepting that decision.

Let's drill down.

Why #1: Why don't coaches share their published page in the first 72 hours?

What's your answer? What's the first-level reason they don't share?

Good. That's honest and specific. The barrier isn't mechanics—it's the irreversibility of the identity claim.

Now let's go deeper.

Why #2: Why does sharing the page feel like an irreversible identity claim instead of just... a business action?

In other words, why is the page loaded with so much identity weight? Why can't they just think of it as "I'm testing something" or "I'm putting this out there to see what happens"?

What's driving the high stakes?

Why #3: Why is this the first time they've made a concrete, definitive claim about their coaching identity?

This is getting at something deeper. Why haven't they made this claim before? Is it because:

• They didn't have a tool to make it (the page)?
• They weren't ready psychologically?
• They were waiting for some condition to feel "right" (testimonials, more experience, etc.)?
• Something else?

What's your answer?

Now we're getting somewhere real. Let me make sure I understand this before we go to Why #4.

You're saying: The product solved the tool problem (how do I build a professional page) but it did so before coaches had solved the readiness problem (am I actually ready to claim this identity and ask for money).

The tool should have been the final step in a sequence: internal readiness → claim identity → build page → share page. But instead, the tool became the first step, and it created an illusion of progress without the internal work.

So now they have:

• A professional artifact (page)
• But no internal permission (readiness)
• Which creates cognitive dissonance (I have the thing, but I'm not ready to use it)
• Which they resolve by hiding in the editor (pretending to prepare while actually avoiding the decision)

Is that the shape of it?

Why #4: Why don't they have the internal permission to claim the identity?

What's blocking the readiness? Is it:

• Fear of failure/rejection?
• Imposter syndrome (not feeling legitimate enough)?
• Moral/ethical concerns about charging?
• Something about their self-image or how they see coaching?
• Something else?

What do you think is really blocking the permission?

Okay. Now we're at the root. Let me name it clearly before we go to Why #5.

The root cause emerging: Coaches lack internal permission to claim a paid coaching identity because:

1. They haven't resolved their own questions/transitions yet (imposter syndrome specific to coaching's mirror dynamic)
2. They carry moral weight about charging for influence over someone's inner life
3. These unresolved pieces amplify failure risk into existential risk

The product promised to solve "how do I build a professional page" but the real barrier is "do I have permission to charge for this kind of help." Those are different problems entirely.

Why #5: Why do coaches carry this specific moral weight and imposter syndrome about charging for coaching influence?

This is the deepest layer. Why is coaching different? Why does charging for influence feel different from charging for other services?

And here's the pressure-test question underneath it: Is this a problem the product can solve? Or is this a problem that exists upstream of the product, in who these people are and what they believe about coaching itself?

What's your answer?

Perfect. You've just done the honest diagnostic work. Let me make sure I have the full picture before we move to Systems Thinking.

The Five Whys Chain:

1. Why don't they share? Because sharing means claiming an irreversible identity.
2. Why is sharing irreversible? Because the page is the first concrete, definitive claim they've ever made—the tool got ahead of the person.
3. Why haven't they made a claim before? Because they were waiting for internal permission, and the tool's absence gave them an excuse to keep waiting.
4. Why don't they have internal permission? Because of imposter syndrome specific to coaching's mirror dynamic, moral weight about charging for influence, and amplified failure risk.
5. Why this specific moral weight and imposter syndrome? Because coaching has weak gatekeeping, feels adjacent to therapy without protection, and the field has an image problem. The root is upstream and unfixable by product.

The Intermediate Layer (where product can intervene):

• Lower the stakes of a single launch
• Normalize the act through peer evidence
• Frame launching as an experiment, not identity declaration
• Borrow legitimacy from other coaches who've launched

Now let's move to Systems Thinking to understand the self-sustaining loop and find the real intervention points.

Systems Thinking: Mapping the Loop

You suspected a reinforcing loop earlier: page creates artifact → artifact loads identity stakes → high stakes trigger freeze → freeze sends them to editor → tweaking creates illusion of progress → illusion delays sharing → stakes climb further.

Let me map this more systematically. I want to identify:

1. The system components — What are the key elements interacting?
2. The relationships and feedback loops — How do they reinforce each other?
3. The delays — Where does time create a gap between cause and visible effect?
4. The leverage points — Where could a small intervention have a large effect?

Let me start by asking you to map the components:

What are the key elements in this system? (For example: Coach's readiness, page artifact, identity stakes, editor access, sharing decision, audience silence, etc.)

List out the main components you see interacting.

Excellent list. You've identified the key components. Now let me map the relationships and feedback loops.

I want to understand how these interact. Let me ask some specific questions about the connections:

On the reinforcing loop you suspected:

You said: page → identity stakes → freeze → editor hiding → illusion of progress → delayed sharing → stakes climb.

Let me pressure-test this sequence:

1. Does more time in the editor actually increase identity stakes? Or does the editor just delay the moment when stakes would be tested?

In other words: If a coach spends 6 days tweaking in the editor instead of 3 days, do the stakes get higher, or do they just get older? Does the tweaking actually reinforce the problem, or is it just a symptom of the problem happening in parallel?

2. The "illusion of progress" piece — who is that illusion for? Is it for them (they feel like they're doing something) or is it also for you (if you could see their activity, you'd think they're engaged)?

3. On the 72-hour momentum window — you said it "burns whether they use it or not." What happens at hour 72 that makes momentum irreversible? Is it psychological (they've accepted the decision) or logistical (they've moved on to other things)?

On the absence of external accountability:

You flagged this as "the big one." Help me understand the mechanism:

• If someone knew they published, would that change behavior? Or would it just increase shame without increasing action?
• If someone was waiting for the link, would that force the share? (Like the warm prospect cases and the creators with audience expectations?)
• Is the absence of accountability the cause of the freeze, or is it the absence of the thing that would interrupt the freeze?

In other words: Is the problem that they need external accountability to overcome imposter syndrome? Or is the problem that without external accountability, there's nothing stopping them from hiding in the editor indefinitely?

What's your read?

Now we're seeing the system clearly. Let me map the feedback loops:

The Reinforcing Loop (Spiral):

• Coach publishes page
• Page absorbs identity stakes (this is the first concrete claim they've ever made)
• High stakes trigger freeze (can't risk testing something loaded with this much identity weight)
• Freeze sends them to editor (hiding place, feels productive)
• Each day tweaking adds sunk cost
• Sunk cost requires page to be more perfect to justify time spent
• More perfection-seeking = more tweaking = more sunk cost
• Meanwhile, 72-hour momentum window closes
• Audience stays silent (no one knows page exists)
• Silence reinforces the freeze (no external forcing function to interrupt it)
• Stakes continue climbing as justifications accumulate ("waiting for testimonials," "still positioning")
• Loop continues until they churn or go dormant

The Interruption Points (where external accountability breaks the loop):

1. Warm prospect waiting — Creates external deadline, short-circuits identity loading
2. Audience expectation — Creates social obligation, makes sharing feel inevitable
3. Peer cohort witness — Creates solidarity + accountability, interrupts the hiding

The Critical Insight:

The loop isn't broken by giving them permission (that's upstream). It's broken by removing the option to hide indefinitely. Accountability doesn't solve imposter syndrome—it just doesn't let them spend 6 weeks in the editor processing it.

Now the leverage question:

Where in this system could you intervene with the least effort for the most effect?

You have several options:

1. At the moment of publish — Interrupt the spiral before identity stakes load. ("You just published! You're in the 72-hour window. Here's what happens next.")

2. At the editor hiding place — Make tweaking less available or less appealing. (Remove the editor after publish? Make it harder to access?)

3. At the audience silence — Create peer evidence and normalize launching. (Show them other coaches who launched. Create social proof.)

4. At the accountability gap — Create external forcing function. (Deadline? Cohort? Public commitment?)

5. At the sunk cost trap — Reframe what "done" means so they don't keep tweaking. (Page is live, tweaking can happen later, sharing happens now.)

Which of these feels like the highest-leverage intervention point to you? Or is it a combination?

Excellent. You've just designed the intervention by understanding the system. Let me make sure I have the root cause analysis complete and accurate before we move forward.

Root Cause Analysis Summary

Root Causes (from Five Whys):

1. Primary Root Cause: Coaches lack internal permission to claim a paid coaching identity because of:

   • Imposter syndrome specific to coaching's mirror dynamic (haven't resolved their own transitions)
   • Moral weight about charging for influence over someone's inner life
   • Weak gatekeeping in coaching creates fear of being a fraud
   • Fear of failure amplified by the above

2. Secondary Root Cause: The product got out of sequence with the person. It solved the tool problem (how to build a page) before coaches solved the readiness problem (am I ready to claim this identity). This created an artifact that absorbed identity weight without the internal work to support it.

Contributing Factors (from Systems Thinking):

• The reinforcing loop: Page → identity stakes → freeze → editor hiding → sunk cost → more tweaking → stakes climb → loop continues
• The 72-hour momentum window: Decision to not share is made early; after that, it's just slow acceptance
• Audience silence: No one knows the page exists, so there's nothing interrupting the spiral
• Absence of external accountability: Without someone waiting or watching, coaches can hide indefinitely in the editor

System Dynamics:

The problem sustains itself through a reinforcing loop where:

• High identity stakes trigger freeze
• Freeze drives hiding (editor becomes a room to avoid the decision)
• Hiding creates illusion of progress (tweaking, waiting for testimonials)
• Illusion delays sharing
• Delay lets stakes climb further
• Loop continues until churn

The loop is interrupted only when external accountability exists (warm prospect, audience expectation, or peer cohort) that makes sharing feel inevitable rather than optional.

The Intervention Point You've Identified:

A peer cohort mechanism that:

• Fires at the moment of publish (catches the 72-hour window)
• Creates external accountability (deadline + soft public commitment)
• Surfaces peer evidence in real time (normalizes launching, lowers stakes)
• Interrupts the hiding loop before sunk cost accumulates

This addresses the intermediate layer (where product can intervene) without trying to solve the root cause upstream (internal permission/imposter syndrome).

Validation

Does this root cause analysis feel complete and accurate? Have we gone deep enough, or does something feel off?

And importantly: Are you ready to move into Step 5 — Forces, Constraints & Framing Summary? That's where we'll analyze what forces are supporting and resisting solution, identify key constraints, and synthesize everything into a complete Framing document ready for Problem Solving.

Perfect. You've named the tension clearly, and it's important to hold it. The 5-minute promise is a strength in getting people to publish, but it's also a liability if it gets them to publish before they're psychologically ready. That tension will be visible in the Framing Summary and will shape what any solution needs to account for.

Let's move into the final step.

STEP 5: FORCES, CONSTRAINTS & FRAMING SUMMARY

Energy Checkpoint

We've done solid diagnostic work. We've defined the problem, mapped its boundaries, identified root causes, and understood the system dynamics. Now we're in the final stretch—analyzing the forces pushing toward and resisting solution, identifying constraints, and pulling it all together into a Framing Summary that will guide Problem Solving.

How are you feeling? Ready to finish this?

Force Field Analysis

Let me walk you through identifying the forces at play. For each, I'll ask you to assess strength (weak/moderate/strong) and whether we can influence it.

DRIVING FORCES (pushing toward solution):

These are forces that support solving this problem. What's motivating action?

• Runway pressure: You have 7 months of runway and need to prove unit economics. A 6% conversion rate isn't sustainable. How strong is this force? Can you influence it?

• Customer signal: The 78 coaches are churning or going dormant. That's visible, measurable, and urgent. The 5 successes prove it's solvable. How strong is this force?

• Speed of iteration: You're solo and can ship in 1-2 weeks. That's a real advantage—you can test hypotheses fast. How strong is this force?

• Clear diagnosis: We've mapped the problem precisely. You know what's broken and why. That removes false starts. How strong is this force?

• Existing product surface: You already have the publish moment, the editor, the ability to send emails, track behavior. You're not building from scratch. How strong is this force?

Are there other driving forces I'm missing? What else is pushing toward solving this?

RESTRAINING FORCES (blocking solution):

These are forces that make solving harder or slower. What's resisting change?

• The 5-minute promise tension: Your core value prop (fast page building) creates the sequence problem (people publish before they're ready). Solving the problem might require slowing down the experience or adding friction. That could undermine the marketing promise. How strong is this force?

• Coach psychology: The imposter syndrome and moral weight are upstream and unfixable by product. Even with accountability, some coaches will still freeze. How strong is this force?

• Introversion and sales allergy: Your target market is allergic to anything that feels gimmicky or salesy. Any cohort mechanism has to feel like peer support, not a marketing tactic. That's a design constraint. How strong is this force?

• Small sample size: You only have 5 successes and 8-10 in Group B. Any intervention is a bet on a small pattern. How strong is this force?

• Solo founder bandwidth: You can ship 1-2 weeks, but you also have to maintain the product, handle support, and run the business. How strong is this force?

Are there other restraining forces? What else is making this harder?

Once you answer these, we'll move to constraints and then synthesize everything into the Framing Summary.

What's your read on these forces?

You're right, my apologies. Let me update the Root Cause Analysis section in the document now.

Now let's continue with Force Field Analysis. Here are the driving and restraining forces:

DRIVING FORCES (pushing toward solution):

• Runway pressure: You have 7 months and need to prove unit economics. A 6% conversion rate isn't sustainable.
• Customer signal: The 78 coaches are churning or dormant. Visible, measurable, urgent.
• Speed of iteration: Solo founder, can ship in 1-2 weeks. Real advantage for testing.
• Clear diagnosis: We've mapped the problem precisely. Removes false starts.
• Existing product surface: You already have publish moment, editor, email capability, behavior tracking.

RESTRAINING FORCES (blocking solution):

• The 5-minute promise tension: Your core value prop creates the sequence problem. Solving might require slowing down or adding friction.
• Coach psychology: Imposter syndrome and moral weight are upstream and unfixable. Even with accountability, some will freeze.
• Introversion and sales allergy: Market is allergic to gimmicky tactics. Cohort mechanism must feel like peer support.
• Small sample size: Only 5 successes and 8-10 in Group B. Intervention is a bet on a small pattern.
• Solo founder bandwidth: Can ship 1-2 weeks, but also maintaining product, support, business.

What's your read on these forces? Which are strongest? Which can you influence? Are there others I'm missing?

Excellent clarity on all of these. And you've spotted something critical—the minimum viable cohort size problem is a real constraint that links back to acquisition. That's important to name.

Let me now move to Constraint Identification to map what's actually limiting your options.

Constraint Identification

You've identified several constraints in the forces above. Let me organize them and ask you to distinguish between hard constraints (non-negotiable), soft constraints (assumed or negotiable), and self-imposed constraints (limitations you've placed on yourself).

HARD CONSTRAINTS (non-negotiable):

• Runway: 7 months at current burn. This is real and finite.
• Coach psychology: The imposter syndrome and moral weight are upstream. You can't fix them with product.
• Solo founder: You're the entire team. Time and bandwidth are genuinely limited.

Are there other hard constraints?

SOFT CONSTRAINTS (assumed but potentially negotiable):

• The 5-minute promise: You said it's a marketing strength but also creates sequence problems. Is it actually negotiable? Could you slow down the experience for coaches without external forcing functions? Or is it truly locked in?

• Minimum viable cohort size: You said current signup volume might make cohorts thin. Is this a real constraint, or could you start with smaller cohorts and iterate? Could you batch signups differently?

• Solo maintenance: You said you can ship 1-2 weeks. Is that a hard limit, or is there flexibility if you deprioritized something?

SELF-IMPOSED CONSTRAINTS (limitations you've placed on yourself):

• "Can't build a whole new product surface" — You said this, but what does "whole new product surface" mean? Could you build a small new surface (a cohort page, a deadline tracker, a peer feed) without it being a whole product?

• "Tone has to feel like peer coaching, not marketing" — This is a real constraint but it's one you're imposing. Are you willing to be more direct if it moves the needle?

• "Can't risk breaking the 5-minute promise" — Is this truly non-negotiable, or are you protecting something you could actually challenge?

My questions for you:

1. Which of these constraints are you most certain about? Which ones feel immovable?

2. Which constraints could you challenge or relax if the data demanded it?

3. Is there a constraint I'm missing that's actually limiting your options more than you've named?

What's your read?

That last one is important. You've identified a constraint on your own thinking—you keep designing for the founder you want them to be, not who they actually are. That's worth holding onto as you move into Problem Solving.

Let me now synthesize all of this into Key Insights and then we'll move to the Framing Summary.

Key Insights

Before we write the final summary, let me ask you to pull together the most important learnings from this entire session:

What's the single most important thing we learned?

Is it:

• The 72-hour window is the entire game?
• The tool got out of sequence with the person?
• Accountability interrupts the loop, not permission?
• Something else?

What surprised you most?

Looking back at what we've uncovered, what assumption did you hold that turned out to be wrong or incomplete?

What's the most critical root cause to address?

We identified imposter syndrome upstream (unfixable) and the tool-person sequence problem (fixable at the intermediate layer). Which one will you focus on first?

What's the strongest force working for you? Against you?

For you: Is it runway pressure, your own conviction, or speed of iteration? Against you: Is it the 5-minute promise tension or solo bandwidth?

What constraint most limits your options?

Is it runway, coach psychology, or something else?

What will you test first?

Given everything we've uncovered, what's the first experiment you'd run to validate the diagnosis?

Answer these, and we'll have the raw material for the Framing Summary.

Perfect. You've got clarity on all of it. Now let me synthesize everything into the Framing Summary.

Crafting the Framing Summary

This is the capstone section—a cohesive narrative that ties everything together. I'm going to draft it based on everything we've uncovered, and then we'll iterate on it until it feels complete.

Here's the shape I'm thinking:

THE PROBLEM — One paragraph distilling the refined problem statement and its significance.

THE LANDSCAPE — Key boundaries, root causes, and system dynamics.

THE SOLUTION SPACE — What forces support resolution, what resists it, what constraints bound the options, and what the most promising angles of attack are.

READINESS FOR PROBLEM SOLVING — What a Problem Solving session should focus on first, what assumptions to test, what risks to watch, and success criteria.

Let me draft this and present it to you:

DRAFT FRAMING SUMMARY

THE PROBLEM:

Coaches without external forcing functions (warm prospects, audience commitments) publish their service pages but don't share them with their audience, resulting in a 6% publish-to-first-sale conversion rate and visible churn among the 78 coaches who published but never shared. The product successfully solves the operational job (build a professional page in 5 minutes) but breaks an implicit emotional promise: that building the page would give coaches the confidence to actually ask for money. Instead, the page becomes an artifact loaded with identity weight—the first concrete, definitive claim these coaches have ever made about being a paid professional. That weight triggers a psychological freeze at the exact moment they need to share.

THE LANDSCAPE:

The root cause is that the product got out of sequence with the person. Coaches sign up imagining the page is the missing piece, then discover that the page was never the missing piece—internal permission was. The real blocker is imposter syndrome specific to coaching (haven't resolved their own transitions yet), moral weight about charging for influence over someone's inner life, and weak gatekeeping in the field creating fear of being a fraud. These are upstream problems the product cannot fix.

However, the product can work in the intermediate layer. The system sustains itself through a reinforcing loop: high identity stakes → freeze → editor hiding → sunk cost → more tweaking → stakes climb → loop continues. This loop is interrupted only when external accountability exists (a warm prospect, an audience expectation, or a peer cohort) that makes sharing feel inevitable rather than optional. The 5 coaches who succeeded all had external accountability. The 78 who froze had none.

The 72-hour window after publishing is decisive. The decision to not share is made in the first 3 days. After that, momentum is gone and coaches enter slow acceptance. This is the only real intervention window.

THE SOLUTION SPACE:

Multiple forces support solving this. Runway pressure is acute (7 months to prove unit economics). Customer signal is clear (78 coaches churning, 5 successes proving it's solvable). Speed of iteration is a real advantage (1-2 weeks to ship). Clear diagnosis removes false starts.

However, several forces resist. The 5-minute promise creates a build-vs.-launch tension—the product speeds up page building but may speed up publishing before coaches are psychologically ready. Coach psychology (imposter syndrome, moral weight) is upstream and unfixable; even with intervention, some percentage will always freeze. The target market is allergic to anything that feels like marketing tactic; any solution must feel like peer support or it dies on contact.

Key constraints: Runway is finite and non-negotiable. Stripe flow and checkout can't change. The 5-minute build promise is negotiable, but the 5-minute launch promise was never actually a promise—it was a misframing of what the product is supposed to do. Solo founder bandwidth is real but has some flex if other work is paused.

The most promising angle of attack is the accountability gap. The 5 successes all had something forcing them through the vulnerability moment. If you can manufacture that for coaches who don't have it organically—through a peer cohort with a defined window and peer evidence—you're giving them what the successes had. This hits multiple leverage points: it fires in the 72-hour window (catches the decision), it creates external accountability (interrupts the hiding loop), and it surfaces peer evidence (normalizes launching, lowers stakes).

READINESS FOR PROBLEM SOLVING:

The diagnosis is solid but based on small numbers (5 successes, 78 frozen, 8-10 sharers). The first Problem Solving step should be running a controlled experiment: take the next cohort of 10-15 coaches who publish, put them in a small private group with a 7-day window, surface peer activity daily, and measure publish-to-first-sale conversion against the 6% baseline. This is cheap to build, fast to learn from, and tests the central hypothesis directly.

Key assumptions to test:

• Does peer evidence + accountability actually interrupt the freeze, or do coaches with high identity stakes still hide even with external pressure?
• What's the minimum viable cohort size? Does it need to be 20 people, or does 3-4 coaches feel like enough peer evidence?
• Does the tone matter more than the mechanism? Can you get adoption if the intervention feels like peer support vs. product tactic?
• Does introducing a cohort at publish break the 5-minute promise, or can you separate build speed from launch speed in customers' minds?

Risks to watch:

• If coaches still freeze even with accountability + peer evidence, that signals the customer fit problem (B) is real and upstream. You may be attracting coaches who aren't ready to claim a paid identity, period.
• If the cohort mechanism feels gimmicky to coaches no matter how you tone it, you'll get low adoption and the experiment will fail not because accountability doesn't work, but because the delivery felt wrong.
• If you can't reach critical cohort mass (even 3-4 coaches) because signup volume is too low, the intervention becomes logistically impossible.

Success criteria:

• Primary: Publish-to-first-sale conversion increases from 6% to 25% within 60 days on the cohort.
• Secondary: Cohort participation rate (% of coaches in cohort who share) is 50%+, signaling that accountability actually interrupts the freeze.
• Diagnostic: If cohort doesn't move conversion but some coaches still share, that tells you courage can be built but reach is the problem (Group B pattern). If nobody shares even with accountability, that tells you customer fit is the real issue.

Testing This Against Reality

Before we lock this in, let me ask:

Does this Framing Summary capture the full picture? Does it stand alone enough that someone could read it and understand the problem, the landscape, the solution space, and what to do next?

What would you sharpen or adjust? What's missing or overstated?

Does it hold the tension you wanted to preserve? The tension between the 5-minute promise as a strength and as a liability?

What's your read?

Perfect. Those are all sharp adjustments. Let me revise the Framing Summary to incorporate them, and then we'll finalize the document.

Let me update the Forces & Constraints and Framing Summary sections now:

Final Validation

Does this revised Framing Summary feel complete and accurate? Does it hold all the tensions and nuances you wanted to preserve?

Is there anything else you'd adjust before we finalize the document?

Excellent. We've completed the full problem framing.

Let me generate the final, complete Problem Framing document for you now

You're Done

This Problem Framing document is now complete and self-contained. It captures:

• The problem you're solving and why it matters
• The boundaries of where it exists and doesn't exist
• The root causes and system dynamics sustaining it
• The forces and constraints at play
• A clear Framing Summary that explains the landscape and points toward Problem Solving

You can hand this to anyone (a co-founder, an advisor, a future team member) and they would understand exactly what problem you're solving, why the 5 successes worked, why the 78 froze, and what the first experiment should be.

Next steps: Take this to Problem Solving. Design and run the cohort experiment. Let the data tell you whether you're solving the right problem at the right leverage point.

You did good diagnostic work here. You were honest about the uncomfortable parts (the tool got out of sequence, you've been giving your product credit it didn't earn, you pattern-match toward the wrong customer). That honesty is what makes this framing valuable.

Good luck with the experiment.