MBTI性格タイプに基づく面接対策
MBTI性格タイプに基づく面接対策

[Complete Guide] Learning Zappos’ “Delivering Happiness” Customer Experience — 10 Core Values / No-Script Service / Self-Organization (Holacracy → MBD) Made Practical


Key Points First (Summary)

  • The core of Zappos is its 10 Core Values (e.g., Deliver WOW Through Service, Create Fun and A Little Weirdness), which permeate daily decisions, hiring, and evaluation. They are not slogans but a decision-making yardstick.
  • Customer experience is designed by reverse-engineering from the purpose of “delivering happiness” before selling. 365-day returns, free shipping both ways, 24/7 support, and no-script phone calls are hallmark practices that entrust discretion to people.
  • On organization, since 2013 Zappos introduced Holacracy, later evolving into Market-Based Dynamics (MBD). It preserved the strengths of self-organization while tuning for stronger customer focus.
  • Who benefits? Any frontline where human discretion creates value (retail/D2C/SaaS/CS & call centers/back office). If you assume accessibility, even no-script service can remain consistent in quality.
  • What this article enables: evidence-based operating templates (rituals instead of scripts), KPI design, and a 30-60-90 day rollout so first-timers can reproduce the model safely.

Introduction — Design “Delivering Happiness” Before Selling

Zappos codified its 10 Core Values in 2006 and since then has unified hiring, training, evaluation, and daily decisions around that yardstick. Rather than being swayed by discounts and efficiency debates, these values are behavioral norms for nurturing long-term customer relationships. Representative examples include Deliver WOW Through Service, Create Fun and A Little Weirdness, and Pursue Growth and Learningten actionable items that become the common language that underpins frontline discretion.

CX is built on two wheels: low-friction mechanisms like 365-day returns, free round-trip shipping, and 24/7 support, and trust in people that enables no-script, heartfelt conversations. The stance of not cutting customers off or forcing time limits produces not just surface satisfaction but memorable experiences.


1. Zappos’ “10 Core Values” — Plain-English Summary and Frontline Imagery

How to use them: In meetings, hiring, and evaluations, actively ask “Which core value does this decision align with?” Doing this out loud reduces doubt and raises the quality of discretion.

  1. Deliver WOW Through Service
    Example: Even at the last minute of the return window, gladly accept; add a handwritten note of thanks when appropriate.
  2. Embrace and Drive Change
    Example: From the frontline, propose a better FAQ → ship same day.
  3. Create Fun and A Little Weirdness
    Example: Small talk has value. Touch on anniversaries or hobbies—the human touch is key to no-script.
  4. Be Adventurous, Creative, and Open-Minded
    Example: Send a return label proactively—an anticipatory kindness.
  5. Pursue Growth and Learning
    Example: Share one learning weekly; self-review call recordings.
  6. Build Open and Honest Relationships With Communication
    Example: If out of stock, it’s okay to refer customers to other companies.
  7. Build a Positive Team and Family Spirit
    Example: Make the “warmth of handoffs” a KPI (not just info, but feeling).
  8. Do More With Less
    Example: Build re-commerce pathways for returns to minimize waste.
  9. Be Passionate and Determined
    Example: Strive for First Contact Resolution on complex cases.
  10. Be Humble
    Example: Don’t paraphrase the customer’s words; respect their phrasing when summarizing.

2. The Design Behind “No-Script Service” — Systems × People × Guardrails

Systems: 365-day returns, free two-way shipping, 24/7. The lower the friction, the more you can focus on the quality of conversation.
People: So that no script doesn’t mean “no guidance,” standardize core values as the decision compass, visibility of customer history, and sharing of prevention learnings.
Guardrails: Clearly mark red lines around law, safety, ethics. Present them in words (not colors) and ensure operations are keyboard-completable.

Point: Freedom maximizes within a frame of safety. Rather than adding bans, codify what’s allowed, and creative proposals will increase.


3. The Path of Self-Organization — From Holacracy to MBD

  • 2013–: Introduced Holacracy. Weakened titles; distributed authority via roles × circles to standardize decision-making patterns.
  • After running it: Meeting load and inward complexity sometimes became issues. Zappos later evolved to MBD (Market-Based Dynamics)—a customer-centric internal market for allocating resources. The adjustment combined the strengths of self-organization with a sharper customer focus.
  • External observations: Some reports/analyses note stepping away from pure Holacracy. Zappos continues pursuing its own form of self-organization. What matters is purpose over form: keep checking whether the design brings you closer to the customer.

4. Use It Now — Templates for Rituals, Not Scripts

4-1. A “Zappos-style” 2-minute Communication Flow (No-Script in Practice)

  1. Summarize (20s): “So your concern is ___; I’ll stay with you through to resolution today.”
  2. Empathize (20s): “It’s understandable that ___ was frustrating.”
  3. Options (40s): Openly present return / exchange / pre-arrival cancel / referring other vendors.
  4. Agreement (20s): Echo the chosen path in one sentence.
  5. Anticipate (20s): Offer return labels / back-in-stock alertsnext-step reassurance.
  6. Room for human touch (20s): A dash of “fun and a little weirdness”—hobbies, occasions.

Note: No judging personalities; facts + feelings are fine. Short polite sentences; use plain language. For accessibility, record the intended reading order in conversation notes.

4-2. “Decision Guardrail” Pocket Card (A6)

  • Top priority: Safety / law / anti-discrimination
  • Core values: Which value does today’s decision align with? (circle one)
  • Spend discretion: Necessary customer-satisfaction costs are OK; leave a one-line rationale
  • Referrals: If out of stock, referring other companies is allowed (trust is built by honesty)

4-3. 365-Day Return & Repurchase “Experience Design” Checklist

  • Ease of return: Pre-printed labels; nearby drop-off flows
  • Information clarity: Not color-dependent; short sentences/bullets; screen-reader order
  • Anticipation: Back-in-stock alerts / size comparison tables / “If this didn’t work, try this” suggestions

These are CX costs and simultaneously investments in churn prevention & LTV lift.


5. By Role — Small Implementations for Tomorrow

5-1. CS / Contact Center

  • Goal: Marry human conversations with first-contact resolution
  • Ops: No-script + 2-minute ritual + guardrail card. Don’t chase a blanket AHT reduction; focus on FCR / re-open rate.
  • Accessibility: Standardize recordings → transcripts, and tag (issue / remedy) for reuse.

5-2. E-commerce / Store Ops

  • Goal: “Zero friction” returns → repurchase
  • Ops: A/B the 365-day, free round-trip return flows to minimize friction.
  • KPIs: Not just return rate—add repurchase within 30 days post-return and share of “kindness” mentions in open-text NPS.

5-3. HR / Hiring

  • Goal: Assess fit with core values
  • Ops: Use behavioral interviews (STAR) to surface honesty examples (e.g., “Have you ever referred a competitor?”).
  • Onboarding: Create and agree on “tomorrow’s action” one-liners for each of the 10 values.

6. KPI Design — “Outcome × Speed × Learning × Fairness”

  • Outcome (lagging): LTV / repurchase / retention after returns / CSAT / NPS
  • Speed (process): First Contact Resolution (FCR) / return→refund lead time
  • Learning (reuse): Searches of conversation summaries / downloads of best replies
  • Fairness: Speaking-time distribution (by agent/attribute) / adoption rate of anonymous proposals
  • Experience metric: Don’t measure “no-script compliance rate”; measure completion of “summary → agreement → anticipation.”

No color-only visualizations. Use color + labels + icons with a textual synopsis, and specify screen-reader order.


7. 30-60-90 Day Rollout

Days 1–30: Align language

  • Create an A4 “frontline translation” of the 10 Core Values (one action example each).
  • Share the no-script ritual (2-minute flow) via training + recording.
  • Build a friction map for returns & shipping and remove the first hotspot.

Days 31–60: Get the engine running

  • Run a weekly “CX showcase” (5 minutes × many). Share great conversations via transcripts + alt text.
  • Distribute guardrail cards; collect and standardize one-line rationales for exception decisions.
  • Pilot a small MBD-style internal contract (allocate a micro-budget to a returns-experience improvement team).

Days 61–90: Turn learning into assets

  • Publish a color-independent, screen-reader-ordered KPI dashboard.
  • Hold blameless postmortems; convert them into recurrence-prevention templates.
  • Decide on continue / stop / expand.

8. Common Misconceptions — Gentle Workarounds

  • “No-script = do whatever you want.”
    • Fix: Use the ritual (summary → empathy → options → agreement → anticipation → human touch) instead of a script, with clear guardrails.
  • “More returns = red ink.”
    • Fix: Make “repurchase after return” visible; judge investments by long-term LTV.
  • “Self-organization = chaos.”
    • Fix: Adjust form to purpose, e.g., from Holacracy’s “form” to MBD’s “customer focus.” Avoid form worship.
  • “Core values belong on posters.”
    • Fix: In hiring/evals/meetings, say out loud which value a decision aligns with.

9. Case Studies (Mini-Stories)

Case A: Honesty when out of stock

  • Situation: Popular color is out of stock.
  • Action: In a no-script manner, refer other vendors, set back-in-stock alerts, and offer second-best suggestions.
  • Result: Lost the same-day sale, but next-month repurchase rises; “honesty” appears more often in NPS open text.

Case B: The value of a long call

  • Situation: A senior customer seeks size advice.
  • Action: No time limit, include light small talk; mail a size comparison chart.
  • Result: AOV near average, but family referrals occur. The conversation summary becomes a best reply used company-wide.

10. Accessibility-First CX — Make “Anyone Can Buy Comfortably” the Default

  • Inverted pyramid: Summary → body → details so the whole picture is clear in 1 minute.
  • Not color-dependent: Show return terms, ETA, and stock with color + labels + icons.
  • Reading order: Define heading hierarchy and reading order for product pages/return forms.
  • Keyboard-only: Let apply → return → refund complete without a mouse.
  • Plain Japanese / simple language: Returns in short bullets with furigana where needed.
  • Recordings & transcripts: Turn great conversations into learning assets.
    These are not just compliance—they translate the core values of “honesty & humility” into lived experience.

11. Who Especially Benefits? (Concrete Personas)

  • D2C / E-commerce leads: Make investment calls on repurchase after return; optimize the “cost of happiness” via friction maps + A/B tests.
  • CS / Contact center heads: Balance humanity × FCR through the no-script ritual; prioritize re-open rate over raw AHT.
  • HR / Org development: Embed the 10 Core Values in hiring and evaluation; build a library of behavioral examples.
  • Executives: Treat self-organization as a means; use MBD-style allocation to secure customer-centric speed and learning.

12. Summary — Operationalizing “Delivering Happiness”

Zappos’ lessons are simple:

  1. Run the 10 Core Values in frontline language.
  2. Make no-script into freedom with safety via rituals + guardrails.
  3. Shave return & shipping friction with experience metrics and cultivate stories of repurchase.
  4. Keep self-organization tuned to the customer (signal from Holacracy → MBD).

Starting today, use the 2-minute ritual, the guardrail card, and visibility of repurchase after returns to nurture a quiet but powerful “flow of happiness” on your frontline. I’m cheering you on.


Primary Grounds (First-Party Info & Trusted Explanations)

By greeden

Leave a Reply

Your email address will not be published. Required fields are marked *

日本語が含まれない投稿は無視されますのでご注意ください。(スパム対策)