奇创岛

From «Essentialism: The Disciplined Pursuit of Less»

Design an 'Essentialism' Book Club Event Plan

You'll design a 1.5–2 hr co-reading event around *Essentialism*: each participant brings a 'too-much list,' scores each other's items with the 90% scorecard, cuts non-essential items, and rewrites an essential list — producing a ready-to-run event plan you can execute directly.

Final work

An *Essentialism* Book Club Event Plan

Estimated time

1.5–2 hr (design) + event execution

Submitted

…

Your final work

Purpose:Transform the core tools of *Essentialism* — the 90% rule, the subtraction-contrast method, and the 'why are you keeping this?' inquiry — into a structured, output-driven, community-building offline or online book club event, so every participant leaves with an essential list that has been collectively reviewed.

Parts:

  • Event framing: target audience + context description (friend gathering / company mid-year review / university student group, etc.)
  • Timeline: 1.5–2 hr segmented schedule (warm-up → list submission → mutual scoring → cutting → rewriting → sharing → closing commitment)
  • Toolkit: 90% scorecard template + subtraction-contrast method guide + facilitator question script
  • Deliverable description: one 'post-event essential list' per participant (with reasons for what was kept)
  • Community-feeling mechanism: how to maintain a lightweight mutual-accountability commitment after the event ends
  • Facilitator notes (including how to handle common sources of resistance)

Use cases:

  • · Use it to organize a real friend gathering / company mid-year review / university book club
  • · Use it as an event planning proposal for a project-manager meetup or interdisciplinary book club
  • · Use it as an embedded 'subtraction segment' for a team's quarterly retrospective

Pick a topic

Pick the topic closest to you, or write a custom one when you submit.

Personal Life

Family / Parenting

Work / Projects

Communication & Relationships

Tools you'll use from the book

90% Scorecard (Live Scoring)

The core tool from *Essentialism*: score each item on your list from 1–100; any candidate scoring below 90 goes straight onto the 'cut' list.

How to use it here:

Prepare one scorecard per participant (paper or shared doc). After listing their 'too-much items,' each person's list is scored by others: 'If this item disappeared tomorrow, would this person's overall situation be better or worse?' Items below 90 are flagged. Having someone else do the scoring breaks the owner's 'maybe it'll be useful someday' defense.

Boundaries:

Scores should reflect understanding of the person's context, not the scorer's personal preference. No one may challenge a score on the spot; questions are reserved for the 'why are you keeping this?' segment.

Subtraction-Contrast Method

Place 'reasons to keep it' and 'benefits of cutting it' side by side, helping the owner see the true difference in weight between the two columns.

How to use it here:

After scoring, for each item below 90, the facilitator guides the owner to fill in two columns: 'My reasons for keeping it' vs. 'What I gain by cutting it.' Once both columns are written, in 85% of cases the 'cutting' side is more concrete and more compelling — and the owner reaches the conclusion on their own. No value judgments are made during the activity; only the contrast is presented.

Boundaries:

The contrast method helps the owner see clearly — it does not make the decision for them. The facilitator must never say 'you should cut this.'

'Why Are You Keeping This?' Inquiry

Through successive questions, expose the real fear behind 'just in case it's useful someday' — this is the conversational implementation of essentialism's 'explore' step in a group setting.

How to use it here:

The facilitator uses up to 2–3 rounds of inquiry per owner: 'Why are you still keeping this?' → 'If it still hasn't been used a year from now, what happens?' → 'Is that fear real, or is it an assumption?' Three rounds of questions are usually enough for the owner to identify loss aversion rather than genuine need. Keep the inquiry pace to 3–5 minutes to avoid spiraling into self-analysis.

Boundaries:

The inquiry is for support, not interrogation. If the owner signals they don't want to go deeper, the facilitator stops immediately and respects personal boundaries.

Community Witnessing

At the close of the event, each participant publicly states 'what I'm cutting today,' using collective witnessing to reinforce the commitment to subtraction.

How to use it here:

In the final 15 minutes: each person says in one sentence 'I'm cutting [X] from my list today,' and the other participants offer a simple 'I witnessed that' response (a nod, applause, or written note). Collective witnessing transforms a private decision into a social commitment and significantly increases the execution rate of the subtraction. A lightweight 2-week follow-up mechanism can be added after the event (e.g., a WeChat message or a single check-in question).

Boundaries:

Community witnessing is support, not surveillance. Follow-up participation must be voluntary; no one is required to report results.

KPT Retrospective (Post-Event)

Keep–Problem–Try: a quick three-box retrospective at the end of the event to capture 'what worked / what had friction / what to change next time,' making each event better than the last.

How to use it here:

In the last 5 minutes, the facilitator guides everyone to write three lines: K (Keep) = which segment was most valuable and worth preserving; P (Problem) = which segment had friction or felt stuck; T (Try) = what you'd like to change if you ran it again. The KPT also becomes the 'self-iteration record' for the event plan, written into the final work.

Boundaries:

The KPT is feedback on the event design, not an evaluation of individual participants. The facilitator collects and organizes the responses without publicly naming anyone in criticism.

Work rules

Your work MUST include

  • A clearly defined target audience (specific participant profile + shared pain points)
  • A detailed 1.5–2 hr segmented timeline (each segment includes: duration / goal / facilitator action / participant deliverable)
  • A ready-to-use 90% scorecard template (with scoring-dimension descriptions and facilitator prompts)
  • A 'why are you keeping this?' inquiry script (at least 3 levels of questions)
  • A post-event community commitment mechanism (specifying at minimum the duration and follow-up method)
  • A KPT retrospective record (based on design assumptions or actual execution)

Your work CANNOT just be

  • Don't make it just a book summary or reading-response sharing session — the event must have a hands-on, do-something segment
  • Don't include only process descriptions without tool templates — the scorecard and question script must be ready to use as-is
  • Don't treat 'everyone takes turns sharing impressions' as the core of the event — impression sharing is not a practical application of the essentialism toolkit
  • Don't skip the community mechanism — participants must leave with some form of mutual witnessing or follow-up arrangement
  • Don't design an event longer than 3 hours — the book club itself should practice 'less but better'

AI can help you here

Round 1: Help me choose an event scenario

When to use: You want to host an Essentialism book club but aren't sure which audience or scenario to design for.

I'm using *{{Book title}}* to complete the '{{Route name}}' project. My goal is to design an Essentialism book club event plan. Based on my situation, please help me choose the 1 most suitable event scenario from the list below and explain your reasoning.

My situation:
[Fill in: What type of participants can you gather? What are their shared pain points? How much time and space do you have? Do you have facilitation experience?]

Available scenarios:
[Paste the scenario list from the page]

Please output:
1. The most recommended scenario and why
2. Which segment of this scenario will deliver the most value to participants
3. Three things I need to prepare in advance as facilitator
4. The 1–2 most common failure modes for this scenario

Yellow placeholders need you to fill in before using the AI.

AI can help you organize ideas, but cannot make final judgments for you. Don't let AI fabricate experiences, cases, or misleading content.

Round 2: Help me strengthen the flow and tools

When to use: You've chosen an event scenario and want to make the process design and tool templates more solid.

I'm working on the '{{Route name}}' project using *{{Book title}}*.

My event scenario is:
{{Topic}}

My current flow draft:
[Paste your timeline draft, or describe your initial ideas]

Please help me:
1. Check whether the flow correctly applies the core essentialism toolkit logic (90% rule → subtraction contrast → inquiry → community commitment)
2. Identify any segment with an unrealistic time allocation or wrong sequence
3. Help me improve the 90% scorecard's facilitator prompts (so participants find them easy to understand without feeling judged)
4. Add any levels I may have missed in the 'why are you keeping this?' inquiry script

Please output:
- Flow improvement suggestions (segment by segment)
- Revised facilitator prompts
- Supplemented version of the inquiry script

Yellow placeholders need you to fill in before using the AI.

AI can help you organize ideas, but cannot make final judgments for you. Don't let AI fabricate experiences, cases, or misleading content.

Round 3: Help me review the event plan

When to use: You've finished a draft of the event plan and want one final check before submitting or executing it.

I'm submitting my Shufang Island project work.

Book: *{{Book title}}*
Project route: {{Route name}}
Event scenario: {{Topic}}

My event plan draft:
{{Draft work}}

Please check my draft against these criteria:
1. Does the event flow genuinely apply the core tools from *Essentialism* (the 90% rule, subtraction-contrast method, inquiry) rather than just being 'everyone discusses the book together'?
2. Are the scorecard and inquiry script usable as-is, or are they only directional descriptions?
3. Is the community commitment mechanism specific (with a defined time, method, and concrete follow-up question) rather than just 'create a group chat'?
4. Is the timing realistic — can all segments be completed within 1.5–2 hr?
5. Do the facilitator notes cover the most common friction points?
6. Is this ready to submit?

Please output:
- Overall assessment
- What is already done well
- What must be revised
- What could be strengthened
- Suggested structure for the revised event plan

Yellow placeholders need you to fill in before using the AI.

AI can help you organize ideas, but cannot make final judgments for you. Don't let AI fabricate experiences, cases, or misleading content.

Submit my work