Files

4.4 KiB

Inversion Examples - Artem's World

Example 1: TISA Eindhoven Launch

Goal

Successfully open TISA Eindhoven with 50 students in Year 1

Inverted Question

"How would I GUARANTEE Eindhoven fails?"

Failure Paths

🔴 FATAL:

  1. Open without regulatory approval → Forced to close

    • AVOID: Legal review 6 months before, permit in hand before any marketing
  2. Run out of cash before breakeven → Project dies

    • AVOID: 18-month runway minimum, milestone-based spending
  3. No qualified teachers available → Can't open

    • AVOID: Start recruiting 9 months early, backup candidates

🟡 DAMAGING: 4. Copy-paste Leiden without local adaptation → Doesn't resonate

  • AVOID: Local advisory board, community research first
  1. Artem stretched too thin → Both schools suffer

    • AVOID: Hire Eindhoven director first, delegate fully
  2. No local partnerships → Unknown brand, slow enrollment

    • AVOID: ASML/tech company partnerships before launch

🟢 ANNOYING: 7. Facility not ready in time → Delayed opening

  • AVOID: 3-month buffer on facility timeline

Anti-Checklist

â–¡ Never announce opening date before permits secured â–¡ Never hire teachers less than 6 months before start â–¡ Never open without local director in place â–¡ Never use Leiden marketing materials without adaptation â–¡ Never commit to facility without exit clause


Example 2: TeddySnaps Launch at New TeddyKids Location

Goal

Successfully deploy TeddySnaps at new location

Inverted Question

"How would I guarantee staff hates TeddySnaps and parents never use it?"

Failure Paths

🔴 FATAL:

  1. Staff sees it as surveillance → Active resistance

    • AVOID: Frame as "parent communication tool", not "monitoring"
  2. Parents don't download app → No engagement

    • AVOID: Include in enrollment, demo at first meeting

🟡 DAMAGING: 3. Photos are bad quality → Parents unimpressed

  • AVOID: Photo quality training for staff, good lighting
  1. Face recognition fails often → Trust breaks

    • AVOID: Enroll all faces properly, test before launch
  2. Staff forgets to take photos → Empty feeds

    • AVOID: Gamification, daily minimums, visible leaderboard

🟢 ANNOYING: 6. App crashes occasionally → Frustration

  • AVOID: Thorough testing, quick bug response

Anti-Checklist

â–¡ Never launch without staff buy-in session â–¡ Never go live without all children's faces enrolled â–¡ Never expect photos without clear daily targets â–¡ Never skip the parent onboarding demo


Example 3: GolfTab Sales to First Golf Course

Goal

Sign first paying customer within 60 days

Inverted Question

"How would I guarantee every golf course says no?"

Failure Paths

🔴 FATAL:

  1. Can't demonstrate ROI → No business case

    • AVOID: Build ROI calculator, case study from pilot
  2. Decision maker unavailable → Never get meeting

    • AVOID: Multi-channel outreach, warm intros via network
  3. System isn't ready for demo → Looks amateur

    • AVOID: Demo environment polished, rehearsed presentation

🟡 DAMAGING: 4. Price too high → Immediate rejection

  • AVOID: Competitive analysis, risk-free trial structure
  1. Seems too complicated → "We don't have time"

    • AVOID: Emphasize simplicity, 1-day implementation
  2. No urgency → "Call back next season"

    • AVOID: Limited-time launch pricing, seasonal urgency

Anti-Checklist

â–¡ Never pitch without knowing their current pain â–¡ Never demo without tested, working system â–¡ Never quote price before establishing value â–¡ Never leave meeting without next step scheduled


Quick Inversion Template

GOAL: [What you want to achieve]

INVERTED: "How would I guarantee failure at [goal]?"

FATAL FAILURES:
1. [Would kill it] → AVOID: 
2. [Would kill it] → AVOID:

DAMAGING FAILURES:
3. [Would hurt] → AVOID:
4. [Would hurt] → AVOID:

ANTI-CHECKLIST:
â–¡ Never...
â–¡ Never...
â–¡ Never...

Artem's Personal Anti-Checklist

Based on pattern recognition across your businesses:

â–¡ Never start building before validating demand â–¡ Never launch without a clear owner responsible â–¡ Never assume staff will adopt without training â–¡ Never skip the parent communication angle â–¡ Never expand without documenting what works first â–¡ Never promise timeline without buffer â–¡ Never make decisions when tired/rushed