Pełny AI Product Sprint na żywo: od analizy po działający produkt | LIVE AI Product Heroes

Agenda / Purpose

• Live “AI Product Sprint” demonstrating an end-to-end product workflow:
  • user discovery → hypothesis → fast prototype → iterate → move into production
• Key emphasis: AI can accelerate execution, but success depends on fixing the product-building process, not just coding faster.

Why AI-only “Speed” Fails (Process Critique)

• Even with faster engineering/design, teams often ship the wrong things because the end-to-end workflow is broken.
• Benchmarks are cited rhetorically (as stated):
  • 41% of code generated by AI (GitHub report, as stated)
  • 21% of Y Combinator startups supposedly have 95% of code written by AI (as stated)
  • 80% of functionalities rarely/never used (Pendo report, as stated)
  • 10–20% of experiments succeed (Google/Bing as stated; Microsoft “not much better”)
• Core failure mode: President/Presence-Driven Development (PDD) / “feature factory”
  • CEO/client brief comes in → team builds features immediately → release → learn later (too late)

The “Proper” Process / Playbook (Framework)

• The workflow is framed as a tight loop:
  1. Talk to users
  2. Form hypotheses based on market signals + user problems
  3. Test quickly and cheaply with a prototype (not production code)
  4. Implement in production (iterate continuously)
• Prototype principle:
  • Prototypes are “pretend products” to validate hypotheses
  • Don’t add prototypes to the backlog; validate then discard/replace
• Iteration guidance:
  • “Iterate at least 3 times” is referenced (attributed quote: “Martin Kegen once said…”).

AI + Tooling to Run the Workflow

Tools are demonstrated conceptually across stages:

• NotebookLM: research synthesis over uploaded interview transcripts/notes (answers must be grounded in provided data)
• GPT Chat “synthetic user”: interview practice via sandbox roleplay
• WhisperFlow: transcription/dictation into tools
• Gemini/LLM Notebook: cross-checking against market research (as described)
• Miro: organizing insights (mind maps/flashcards) and AI-assisted summarization
• Lovable: rapid prototype apps (website/app generation from full prompts; code + UI together)
• Figma / Figma Maker: design prototyping and design iteration
• Cloud Code + MCP: connect AI with code and other tools (translation layer between design/prototype and production components)
• Pencil: alternative “Figma-like” environment with AI-driven updates and transcript-linked flows
• Posthog-like analytics: A/B testing + feature flags + session replay

Case Study: Fictional SaaS “Onboard Hero” (Onboarding Churn)

Business Context / Baseline Metrics (as stated)

• B2B SaaS for onboarding salespeople
  • target companies: 50–200 employees
  • 2–12 salespeople per company
• Current customer base: 120 paying clients
• Pricing metric: MRR = PLN 45,000
• Retention issue: client base declining at ~8% per month (churn)
• Current product:
  • onboarding checklists
  • product training
  • knowledge tests
  • automated emails
  • onboarding ends after a few days

Initial “Brief” (Symptom-Level Problem)

• Customer success / HR managers don’t see onboarding effectiveness.
• Requested solution: HR dashboard with metrics like completion rates, test results, engagement, attendance frequency, etc.

Discovery Findings (The Real Problem)

Using interview transcripts synthesized in NotebookLM, the team identifies a “black hole”:

• After checklist completion, employees “disappear” (no visibility on progress)
• “Completion ≠ readiness”
  • A salesperson can pass tests (even 100%) but still fail in real customer communication
  • Example: “Tomek” passes tests but can’t sell
• Key insight:
  • HR’s complaint is not the root business problem
  • The root issue impacts sales outcomes

Hypothesis Generation (Problem Clusters → Product Hypotheses)

• The assistant outputs 4 problem clusters, each mapping to a product hypothesis.
• Top hypotheses explicitly described:
  1. Mandatory “Sales readiness indicator”
     • show whether a new salesperson reaches standard sales milestones
     • milestones listed: first call, first demo, first pipeline, first deal
     • framing: “alert instead of dashboard”
  2. Push-pull email system to sales managers + replace tests with exercises/verification
     • positioned as potentially “two layers of the same solution” with #1

Prototype Validation Workflow

• They build a prototype (no production code) by translating the hypothesis into:
  • Lovable (from an existing React app scaffold)
  • design in Figma
• They “publish” the prototype and plan customer feedback questions like:
  • “Does this solve your problem?”
• Example feedback signals:
  • “a third box missing”
  • “don’t care about first pipeline”

Business Execution Patterns Emphasized

• Early warning beats postmortem
  • Quarterly reviews are too late (“you’re 8 weeks too late” as stated)
  • Aim: weekly/fast hypothesis validation + iteration cycles
• Align “who reports the problem” with “who owns the solution”
  • HR wants visibility; real impact lies with sales managers and sales readiness
• Measure impact via production experiments
  • Run A/B tests / feature flags to confirm effect on churn/retention and engagement
  • Posthog mentioned for:
    • feature flags
    • session replay
    • A/B testing
    • AI analysis over event data (as described)
• Time compression
  • Claimed sprint pace: analysis → prototype → implementation in about 60 minutes (excluding user interviews)
  • Compared to typical “old world” 4–6 weeks
  • New AI-enabled loop can be hours to days (but user research still takes real time)

“Product Builder” Concept (Organizational Tactic)

• Claim: with AI tooling, teams can shift from separated roles to end-to-end builders.
• Product builder definition
  • A person with a core specialization (engineering/design/PM/marketing/etc.) plus adjacent skills enabled by AI
  • Requires an “agency mindset”: can act without waiting for other specialists
• Team sizing concept:
  • Small product-builder teams can deliver roughly “twice as much as a bigger team” via fewer handoffs (“one box of pizza” analogy)
• Market claims/examples:
  • Quotes attributed to industry leaders about moving to “full-stack builders” / reduced siloed PM roles (names referenced but not used as a detailed strategy plan)

Operational / Program Structure and Milestones (AI Product Heroes 2)

• Program duration: 5 weeks
• Live sessions:
  • Two live meetings per week, each ~2 hours (webinars) + Q&A
  • recorded sessions available
• Week-by-week modules:
  • Week 1: AI Product Sprint + “Superhero Formula”
  • Week 2: Identify & reconnaissance + decide what to build
  • Week 3: Prototyping + Cloud Code masterclass
  • Week 4: Release product + testing + learning from production
  • Week 5: Roadmap-building strategies
• Pricing/offer mentioned:
  • regular: 2990 PLN
  • special 20% discount to ~2390 PLN (deadline “until midnight tonight”)
  • corporate/team discounts and “bonuses” mentioned (exact quantities not provided)

Concrete Actionable Recommendations Extracted

• Replace “feature factory” with the loop:
  • Discovery (interviews/qual) → hypothesis → prototype → user validation → production build → analytics + experiments
• Avoid building dashboards “because HR asked” if the underlying issue is readiness/performance
• Prototype to validate:
  • does it solve the real job-to-be-done and improve measurable outcomes (e.g., sales milestones leading to churn reduction)?
• Use analytics to close the loop:
  • feature flags + A/B tests + session replay to see whether users engage with the new “readiness” signals

Presenters / Sources Mentioned

Presenters

• Piotrek (presenter)
• Wojtek (presenter)

Company / Program / Team References

• Cloud Code (referenced by Boris Czerny, founder—mentioned as a source of the viewpoint)
• Andreesen Horowitz founder Mark Andersen (mentioned)
• Andrew Chen (mentioned in context of generalists; speaker referenced)
• Satia Nadella / Microsoft (CEO referenced)
• Kuba from Google / Mondeo (interview guest referenced)
• Mateusz Chrobok (referenced; interviews/webinar guest context)
• Martin Kegen (quote referenced about iterative solutions/prototypes)

Tools / Data Sources Cited (as stated)

• GitHub report (AI-generated code %)
• Pendo report (80% unused functionality claim)
• Y Combinator (startups code generation claim)
• Google/Bing/Microsoft (experiment success rate claim)