# Modeling Patterns ## Table of Contents 1. [The Funnel Model](#the-funnel-model) 2. [The Role Leap Model](#the-role-leap-model) 3. [The Mindset Upgrade Model](#the-mindset-upgrade-model) 4. [The Value Density Shift Model](#the-value-density-shift-model) 5. [The Invisible Structure Model](#the-invisible-structure-model) 6. [How to Choose a Model](#how-to-choose-a-model) --- ## The Funnel Model **Pattern:** A large volume of inputs must be systematically reduced to reach the one thing that matters. **Structure:** N -> fewer -> one (e.g., 100 -> 10 -> 1) **When to use:** The experience involves filtering, prioritizing, or navigating from abundance to precision. **Before (raw experience):** > "I had hundreds of screenshots of potential business contacts on my phone. Manually entering them into a CRM was exhausting. I used AI to automate data extraction and saved 3 hours per day." **After (modeled):** > "To land one key partnership, you must first evaluate 10 serious candidates. To find those 10, you must sift through 100 fragmented leads. The real challenge isn't data entry -- it's building a reliable funnel from noise to signal. AI doesn't just save time on entry; it makes the entire 100->10->1 funnel visible and manageable." **Why it works:** The audience no longer hears "someone automated screenshots." They see a universal filtering problem they recognize in their own work -- sales pipelines, hiring funnels, content curation, investment screening. --- ## The Role Leap Model **Pattern:** The real transformation is not in what tools were used, but in what role the person now plays. **Structure:** Role A (reactive, task-level) -> Role B (strategic, system-level) **When to use:** The experience involves someone gaining agency, moving from executor to decision-maker, from consumer to creator, or from specialist to generalist. **Before (raw experience):** > "I used to write requirements documents and send them to the design team. Now I use AI to generate mockups myself, iterate on them, and bring near-finished concepts to design reviews." **After (modeled):** > "The shift isn't about AI generating mockups. It's about who gets to sit at the table. Before: you submitted requirements and waited. After: you walk in with a visual proposal and negotiate as an equal. AI didn't change the tool -- it changed the role from 'requester' to 'co-designer'." **Why it works:** The audience doesn't need the same tool stack. But they immediately recognize the pattern: "Am I still in the requester role in some part of my work? Could I leap?" --- ## The Mindset Upgrade Model **Pattern:** The key change is a shift in how problems are perceived, not how they are solved. **Structure:** Old mindset (reactive/linear) -> New mindset (proactive/systemic) **When to use:** The experience involves a fundamental change in approach -- from coping to shaping, from symptom-treating to root-cause-solving, from local optimization to global redesign. **Before (raw experience):** > "Our team used to scramble every quarter-end to compile reports. I built an automated dashboard that pulls data in real-time, so now reports are always ready." **After (modeled):** > "The old approach was firefighting: pressure builds, everyone scrambles, crisis passes, repeat. The new approach asks a different question entirely -- not 'how do we compile faster?' but 'why are we compiling at all?' When you shift from 'absorb the pressure' to 'dissolve the pressure,' you don't optimize the process -- you eliminate the category of problem." **Why it works:** The audience recognizes their own firefighting patterns and is challenged to ask: "Where am I optimizing a process that shouldn't exist?" --- ## The Value Density Shift Model **Pattern:** The transformation is about relocating effort from low-value repetition to high-value judgment. **Structure:** Time freed from X -> reinvested into Y, where Y has disproportionately higher impact. **When to use:** The experience involves automation or efficiency gains, but the real insight is about what the freed-up capacity was redirected toward. **Before (raw experience):** > "AI handles our routine customer inquiries now, which used to take 60% of my day. I've saved about 5 hours per week." **After (modeled):** > "The question isn't 'how much time did you save?' It's 'what did you do with the time you got back?' Saving 5 hours matters only if those hours move you from low-value-density work (answering the same 20 questions) to high-value-density work (spotting patterns in customer frustration that predict churn). AI doesn't give you more time. It gives you a choice: do more of the same -- or upgrade the game you're playing." **Why it works:** Every professional recycles time. The model challenges them to audit whether their saved time is truly being reinvested or simply absorbed by more low-value work. --- ## The Invisible Structure Model **Pattern:** What appears to be a capability problem is actually a structural/system problem that is invisible to the person inside it. **Structure:** Visible symptom -> Hidden structural cause -> Redesigned structure **When to use:** The experience involves discovering that the real problem was not what it appeared to be -- e.g., poor performance was caused by a workflow flaw, not skill gaps. **Before (raw experience):** > "Our new hires kept making errors in client proposals. We tried more training, but it didn't help. Finally I restructured the proposal template and built a checklist system. Errors dropped by 80%." **After (modeled):** > "When people keep failing at a task, the instinct is to fix the people -- more training, more supervision, more pressure. But sometimes the problem isn't the person, it's the invisible structure around them. A bad template silently generates errors. A missing checklist silently invites omissions. The fix isn't 'try harder' -- it's 'make the right action the easy action.' When you redesign the structure, performance changes without anyone needing to be smarter." **Why it works:** Managers and leaders immediately recognize the pattern: "Where am I blaming people for what is actually a systems problem?" --- ## How to Choose a Model | If the experience is primarily about... | Consider | |----------------------------------------|----------| | Filtering, prioritizing, narrowing down | Funnel Model | | Gaining authority, changing professional identity | Role Leap Model | | Changing how problems are framed or perceived | Mindset Upgrade Model | | Saving time/effort and redirecting it | Value Density Shift Model | | Discovering hidden root causes | Invisible Structure Model | **Multiple models may apply.** Choose the one that creates the strongest "I see my own work differently now" reaction for the target audience. When in doubt, prioritize the model that is **least obvious** from the raw experience -- that's where the most cognitive value lies.