Video summary

顧客経験価値③ 顧客経験価値のための商品開発の全体設計と準備、事業企画開発フェーズ

Main summary

Key takeaways

Business

Business-focused summary (Customer Experience Value product development)

1) Product development is different—design it around uncertainty & customer subjectivity

Product development for customer experience value differs from production/logistics/sales because success factors often appear unexpectedly. The work must be driven by customer experiential insights, not only internal logic.

Playbook-style characteristics:

  • Customer needs/trends can be “incidental success factors”: what looks like societal coincidence from the outside can be discovered and turned into winning products.
  • Occasionally one strong person can drive an “idea hit” (more people isn’t always the answer).
  • Iterative experiments matter: repeated trial-and-error can make “coincidental-seeming” discoveries feel inevitable later.
  • Customer feelings/emotions/values dominate: focus on experiential value beyond standard marketing logic or strategy-only reasoning.
  • Past failures can become future hits: changes in context can invert what was “conventionally failing” into success.

Core reminder: Output isn’t maximized by steadily increasing input. It often comes from small experiential insights + dialogue + rapid conversion into hypotheses.

2) Use hypothesis-driven development with strong hypothesis quality

Verification comes later (logical or empirical), but verification is ineffective if the hypothesis is weak.

Hypothesis playbook:

  • Invest heavily upfront in formulating hypotheses (to avoid wasting time/money later).
  • Treat verification as part of a fast learning loop; correct quickly if evidence contradicts assumptions.
  • After proof of concept, revise hypotheses quickly and accurately instead of forcing the original plan to fit.

Operational risk to avoid:

  • “Confirm too roughly → verification gets distorted → go straight ahead → fail.” Countermeasure: immediately correct hypotheses when evidence disagrees.

3) Business development comes before (or runs in parallel with) product development

The speaker separates:

  • Product development: building the product itself.
  • Business development: designing the broader business model and ecosystem that can support multiple products.

Guideline: If you realize business-level work is necessary during product development, switch quickly (or run in parallel) and do business development first.

4) End-to-end “overall development picture”: preparation → hypotheses → testing → business plan

The described process moves through sequential phases:

  1. Preparation phase
  2. Business development hypothesis phase
  3. Product development hypothesis phase
  4. Hypothesis testing phase
  5. Assemble output as a business plan (including the product description)

Testing elements inside the process:

  • Marketing research (assumed familiar)
  • Proof-of-concept experiments
  • Test hypotheses, then roll learnings into revisions

Process principle: Demand is developed first, then product development hypotheses are created from that demand, then tested.

5) Project start-up discipline: define purpose, background, governance, and schedule

The preparation phase includes concrete “must-do” tasks.

A) Define project background & objectives (avoid a common failure mode)

Many teams fail by not clarifying the project’s purpose and target outcome—then they “just start investigating.”

Clarify:

  • Main purpose
  • Expected results and extent/level
  • Prioritize customer experience value (optionally include social issues)

B) Establish a “system” (org structure + decision-making)

Even if top management urges action (“the product is weak, try it”), teams often fail when they:

  • don’t appoint the right department heads,
  • don’t set up an official secretariat,
  • don’t formally assign members.

The speaker emphasizes a solid organizational structure:

  • members + a clear decision-making system

C) Create an action plan with a “project constitution” (team operating system)

Guiding principles:

  • Free thinking and open discussion
  • Take action and learn from mistakes
  • Speed/productivity in writing down ideas
  • Learn from each other’s individuality and expertise

If fear of failure causes slowdowns or criticism: enforce positive thinking and open discussion to reset team behavior.

D) Meeting structure clarity

Decide in advance:

  • meeting length
  • participants

Rationale: without structure, decisions become unclear, forums vanish, and progress slows.

E) Schedule using backcasting + short verification cycles

Avoid year-long planning. Target a cycle like:

  • Plan + complete verification within ~6 months
  • Or at most 4 months before moving to the next stage

Backcasting requirement: understand which tasks occur in each phase to build a realistic timeline.

6) Macro-environment & competitive analysis before articulating the business (use PESPEST)

Before writing hypotheses, derive macro trends from:

  • project objectives
  • expected outcomes
  • background issues

Framework explicitly named: PESPEST (“Global Economy, Socialism, and Technology,” as referenced in the subtitles)

Steps:

  • List main trends relevant to the planned product/business
  • Analyze quantitative impacts if possible (or at minimum list impacts)

7) Competitor analysis beyond “current state”: include substitutes from other industries

Two competitor categories are highlighted:

  1. Strategic groups / same-industry competitors
    • Companies in the same industry under close scrutiny.
  2. Alternatives and new products (not necessarily in your industry)
    • The biggest threat is substitutes from different industries.

Example: Automobile market disruption via “alternatives to mobility,” such as entertainment experiences (e.g., “fun games” replacing the “getting a license and driving” experience).

Additional warning: Don’t analyze competitors only as they are now (or previously). Evaluate the future—forward-looking competitor dynamics.

8) Build business articulation with 4 perspectives (hypothesis-level, quick & brief)

Before committing to a product, articulate business direction using four hypothesis-level perspectives:

  1. Customer experience value offered
  2. Business model / ecosystem that can emerge
    • Ecosystem includes relationships and competitive “battle-through” structures among companies, not just one firm.
  3. Product(s) that fit those perspectives
    • Include core and additional functions that drive experiential value.
  4. Company core competencies/strengths
    • What the company can uniquely leverage across products.

Execution format:

  • Keep it brief, e.g., “five lines in each box”
  • Create milestones like: “Let’s stop here for now” (to prevent endless planning/research)

9) Broaden the hypothesis lens: society-wide, paradigm shifts, new values

The speaker recommends going beyond narrow company/industry challenge frames:

  • Think from society, not just the company.
  • New values and paradigms emerge (examples: space exploration via satellites, DNA-based medicine, AI).
  • Strong hypotheses start from different assumptions—a paradigm shift mindset.

Key metrics / KPIs / targets mentioned

No explicit business KPIs (e.g., revenue, CAC, LTV, churn, margins) are stated.

Timeline targets mentioned:

  • Plan + verification deliverable within ~6 months
  • Or no more than ~4 months before moving to the next stage

Concrete actionable recommendations captured

  • Start with business development, because the product may require an ecosystem/business model to function.
  • Create high-quality hypotheses first, then verify—don’t rely on verification to “save” a bad hypothesis.
  • Revise hypotheses immediately when evidence shows you’re off track.
  • Define purpose/target outcomes up front (avoid investigating without success criteria).
  • Build formal governance: appoint leadership, set up secretariat, assign members, define decision-making.
  • Establish a team constitution and meeting structure to prevent fear-driven slowdowns/criticism.
  • Use backcasting and aim for short verification cycles (4–6 months).
  • Perform competitor analysis including substitutes from other industries, not only same-industry rivals.
  • Use PESPEST to identify macro trends and link each to business/product impact.
  • Articulate the business with the 4 perspectives (CX value, business model/ecosystem, product concept, core competencies) as short hypotheses.

Presenters / sources mentioned

  • No specific presenter name is provided.
  • Framework/tools referenced: PESPEST (spelled out conceptually in the subtitles).
  • No other external organizations are explicitly named.

Original video