Back to Details

marketplace-liquidity

Compare original and translation side by side

🇺🇸

Original

English
🇨🇳

Translation

Chinese

Marketplace Liquidity Management

平台流动性管理

Scope

适用范围

Covers
  • Defining liquidity as reliability: how often a user can complete the marketplace’s core action (find → match → transact) within an acceptable time and quality threshold
  • Measuring liquidity where it actually happens (by “local markets” like geo × category × time window), not just in global averages
  • Diagnosing liquidity failure modes: fragmentation, supply–demand imbalance (“flip-flop”), matching/mechanics issues, and quality/trust breakdowns
  • Designing a practical liquidity operating system: scorecards, weekly review cadence, and a “whac-a-mole” rebalancing plan (move attention/inventory/incentives)
  • Producing an actionable experiment backlog to improve liquidity (supply, demand, matching, pricing/incentives, trust & safety)
When to use
  • “We need to improve marketplace liquidity / match rate / fill rate”
  • “Time-to-match is too slow” / “buyers can’t find availability”
  • “Supply and demand are imbalanced across cities/categories”
  • “Our marketplace feels unreliable” / “conversion drops due to no availability”
  • “We need a liquidity dashboard + operating cadence + experiments”
When NOT to use
  • You don’t operate a two-sided marketplace (no matching between supply and demand).
  • The primary problem is value proposition / ICP (use 
    problem-definition
    or 
    measuring-product-market-fit
    ).
  • You only need pricing changes (use a pricing strategy skill) without a liquidity diagnosis.
  • You need a general growth plan unrelated to matching reliability (use 
    designing-growth-loops
    / 
    retention-engagement
    ).
涵盖内容
  • 将流动性定义为可靠性：用户在可接受的时间和质量阈值内完成平台核心动作（发现→匹配→交易）的频率
  • 在流动性实际发生的场景（按“本地市场”维度，如地域×品类×时间窗口）度量流动性，而非仅看全局平均值
  • 诊断流动性失效模式：碎片化、供需失衡（“交替受限”）、匹配/机制问题、以及信任与质量崩塌
  • 设计实用的流动性操作系统：评分卡、周度复盘节奏、以及“打地鼠式”再平衡方案（调配注意力/库存/激励资源）
  • 产出可落地的实验待办清单以提升流动性（涉及供给、需求、匹配、定价/激励、信任与安全等维度）
适用场景
  • “我们需要提升平台流动性/匹配率/成交率”
  • “匹配时长过长” / “买家找不到可用资源”
  • “不同城市/品类的供需失衡”
  • “我们的平台看起来不可靠” / “因无可用资源导致转化下降”
  • “我们需要流动性仪表盘+运营节奏+实验方案”
不适用场景
  • 你运营的不是双边平台（无需供需匹配）。
  • 核心问题是价值主张/目标客户群体（ICP）（请使用
    problem-definition
    或
    measuring-product-market-fit
    ）。
  • 你仅需调整定价（请使用定价策略相关工具），无需进行流动性诊断。
  • 你需要与匹配可靠性无关的通用增长方案（请使用
    designing-growth-loops
    / 
    retention-engagement
    ）。

Inputs

输入要求

Minimum required
  • Marketplace type + sides (who are “buyers” and “sellers”)
  • The core action you consider a successful outcome (e.g., request → booked; search → purchase; message → hire)
  • Top 1–3 priority segments (geo/category/user cohort) and the time window you care about
  • Best-available baseline metrics (even if rough): demand volume, supply availability, match/fill rate, time-to-match, cancellations/quality
  • Constraints: budget, incentives you can/can’t use, policy/brand/trust, engineering capacity, timebox
Missing-info strategy
  • Ask up to 5 questions from references/INTAKE.md, then proceed.
  • If data is missing, proceed with explicit assumptions and label confidence.
  • Do not request secrets or PII; prefer aggregated metrics or redacted examples.
最低必填项
  • 平台类型及双边角色（谁是“买家”，谁是“卖家”）
  • 你定义为成功结果的核心动作（例如：请求→预订；搜索→购买；发消息→雇佣）
  • 1-3个优先级最高的细分领域（地域/品类/用户群体）及你关注的时间窗口
  • 现有基准指标（即使是粗略数据）：需求规模、供给可用性、匹配/成交率、匹配时长、取消率/质量数据
  • 约束条件：预算、可使用/不可使用的激励手段、政策/品牌/信任要求、工程资源、时间限制
缺失信息处理策略
  • 可从references/INTAKE.md中选择最多5个问题询问用户，然后推进工作。
  • 若数据缺失，基于明确假设推进，并标注置信度。
  • 不得索要机密信息或个人可识别信息（PII）；优先使用聚合指标或脱敏示例。

Outputs (deliverables)

输出成果（交付物）

Produce a Marketplace Liquidity Management Pack (Markdown in-chat; or as files if requested) containing:
  1. Context snapshot (goal, timebox, segments, constraints, decision this informs)
  2. Liquidity definition + thresholds (reliability definition and “good enough” targets)
  3. Liquidity metric tree (north-star + driver metrics, with event definitions)
  4. Fragmentation map + segment scorecard (where liquidity is weak/strong; the “local markets” that matter)
  5. Bottleneck diagnosis (supply vs demand vs matching/mechanics vs quality; include “flip-flop” state)
  6. Intervention plan + prioritized experiment backlog (including reallocation/“whac-a-mole” plan)
  7. Measurement + instrumentation plan (dashboards, alerts, tracking gaps)
  8. Operating cadence (weekly liquidity review agenda + owners)
  9. Risks / Open questions / Next steps (always included)
Templates and expanded guidance:
  • references/TEMPLATES.md
  • references/WORKFLOW.md
  • references/CHECKLISTS.md
  • references/RUBRIC.md
产出一份平台流动性管理包（聊天内以Markdown格式呈现；若有需求可保存为文件），包含：
  1. 上下文快照（目标、时间限制、细分领域、约束条件、本次工作支撑的决策）
  2. 流动性定义与阈值（可靠性定义及“达标”目标）
  3. 流动性指标体系（北极星指标+驱动指标，含事件定义）
  4. 碎片化地图+细分领域评分卡（流动性强弱分布；关键“本地市场”）
  5. 瓶颈诊断（供给侧vs需求侧vs匹配/机制vs质量；含“交替受限”状态）
  6. 干预方案+优先级实验待办清单（含资源再分配/“打地鼠式”方案）
  7. 度量+埋点方案（仪表盘、告警、跟踪缺口）
  8. 运营节奏（周度流动性复盘议程及负责人）
  9. 风险/待解决问题/下一步行动（必须包含）
模板及扩展指引：
  • references/TEMPLATES.md
  • references/WORKFLOW.md
  • references/CHECKLISTS.md
  • references/RUBRIC.md

Workflow (7 steps)

工作流程（7个步骤）

1) Intake + define the decision and local market(s)

1) 需求收集+定义决策与本地市场

  • Inputs: User context; references/INTAKE.md.
  • Actions: Clarify the goal (metric + target + by when), define the core action, pick the “local market” unit (e.g., city × category × week), and decide the decision this work will inform (what you’ll do differently).
  • Outputs: Context snapshot + local market definition.
  • Checks: A stakeholder can answer: “Which segment(s) improve by how much, by when, and what will we change based on the result?”
  • 输入：用户上下文；references/INTAKE.md
  • 动作：明确目标（指标+目标值+时限）、定义核心动作、确定“本地市场”单元（如城市×品类×周）、明确本次工作支撑的决策（后续将做出哪些调整）。
  • 输出：上下文快照+本地市场定义。
  • 校验：相关利益方可明确回答：“哪些细分领域将提升多少，何时完成，我们将据此做出哪些改变？”

2) Define liquidity as reliability + set thresholds

2) 将流动性定义为可靠性+设置阈值

  • Inputs: Core action, time sensitivity, quality constraints (cancellations, refunds, etc.).
  • Actions: Define liquidity as the probability of success within thresholds (time-to-match, quality). Choose 1 north-star liquidity metric and 3–6 drivers (fill rate/match rate, time-to-match, availability, acceptance, cancellation).
  • Outputs: Liquidity definition + “good enough” targets + metric tree outline.
  • Checks: The definition is measurable, segmentable, and aligned to the user’s experience (“reliability”).
  • 输入：核心动作、时间敏感度、质量约束（取消率、退款率等）。
  • 动作：将流动性定义为在阈值内（匹配时长、质量）成功完成动作的概率。选择1个北极星流动性指标及3-6个驱动指标（成交率/匹配率、匹配时长、可用性、接受率、取消率）。
  • 输出：流动性定义+“达标”目标+指标体系框架。
  • 校验：定义可度量、可细分，且与用户体验（“可靠性”）对齐。

3) Build a segment scorecard + diagnose fragmentation

3) 构建细分领域评分卡+诊断碎片化问题

  • Inputs: Baseline data by geo/category/time window (best available).
  • Actions: Create a segment scorecard for each local market: demand, supply, matching, and quality metrics. Identify fragmentation (thin markets, long tail categories, uneven geo distribution) and “uniform needs” vs heterogeneous needs.
  • Outputs: Fragmentation map + ranked list of worst segments (where liquidity blocks growth).
  • Checks: The scorecard avoids global averages and includes enough volume to be meaningful (or flags low-confidence segments).
  • 输入：按地域/品类/时间窗口划分的基准数据（现有最优数据）。
  • 动作：为每个本地市场创建细分领域评分卡，包含需求、供给、匹配、质量指标。识别碎片化问题（小众市场、长尾品类、地域分布不均）及“统一需求”vs“差异化需求”。
  • 输出：碎片化地图+流动性最差的细分领域排名列表（这些领域阻碍增长）。
  • 校验：评分卡避免使用全局平均值，且包含足够样本量以确保数据有意义（或标注低置信度细分领域）。

4) Diagnose bottlenecks (flip-flop + mechanics + quality)

4) 诊断瓶颈（交替受限+机制+质量）

  • Inputs: Segment scorecard; any qualitative evidence (support tickets, user feedback, ops notes).
  • Actions: For each priority segment, label the primary failure mode:
    • Supply-limited (not enough availability/inventory)
    • Demand-limited (not enough intent/requests)
    • Matching/mechanics-limited (ranking, discovery, response time, pricing friction)
    • Quality/trust-limited (cancellations, no-shows, fraud, low ratings) Also check for the “flip-flop” dynamic (which side is currently the constraint) and the graduation problem (top suppliers leaving).
  • Outputs: Bottleneck diagnosis per segment + evidence notes.
  • Checks: Each diagnosis includes at least 1 metric signal and 1 plausible causal story you can test.
  • 输入：细分领域评分卡；任何定性证据（客服工单、用户反馈、运营记录）。
  • 动作：为每个优先级细分领域标注核心失效模式：
    • 供给受限（可用资源/库存不足）
    • 需求受限（意向/请求不足）
    • 匹配/机制受限（排序、发现、响应时长、定价摩擦）
    • 质量/信任受限（取消率、爽约、欺诈、低评分） 同时检查“交替受限”动态（当前哪一侧是约束因素）及流失问题（头部供给方离场）。
  • 输出：各细分领域的瓶颈诊断+证据记录。
  • 校验：每个诊断至少包含1个指标信号及1个可测试的合理因果假设。

5) Generate interventions + experiment backlog (including reallocation)

5) 生成干预方案+实验待办清单（含资源再分配）

  • Inputs: Bottleneck diagnosis; constraints; available levers.
  • Actions: Create intervention options for each bottleneck type (supply, demand, mechanics, quality). Include a “whac-a-mole” plan: how you will reallocate attention/inventory/incentives across segments weekly. Convert interventions into experiments with clear hypotheses and success metrics.
  • Outputs: Prioritized experiment backlog + reallocation playbook.
  • Checks: Every experiment has (a) a segment, (b) a primary metric, (c) a target effect size or directional expectation, and (d) a plausible cycle time.
  • 输入：瓶颈诊断；约束条件；可用手段。
  • 动作：为每种瓶颈类型（供给、需求、机制、质量）制定干预选项。包含“打地鼠式”方案：如何每周在各细分领域间调配注意力/库存/激励资源。将干预方案转化为实验，明确假设及成功指标。
  • 输出：优先级实验待办清单+资源再分配手册。
  • 校验：每个实验均包含（a）细分领域，（b）核心指标，（c）预期影响规模或方向，（d）合理周期。

6) Design measurement + liquidity operating cadence

6) 设计度量方案+流动性运营节奏

  • Inputs: Chosen metrics and experiments.
  • Actions: Specify dashboards/alerts, event definitions, and instrumentation gaps. Create a weekly liquidity review agenda and decision log (what gets rebalanced, what gets shut down, what gets scaled).
  • Outputs: Measurement plan + operating cadence (owners if known).
  • Checks: Each key metric is tied to a data source and update frequency; the cadence produces concrete decisions, not status updates.
  • 输入：选定的指标及实验。
  • 动作：明确仪表盘/告警、事件定义及埋点缺口。创建周度流动性复盘议程及决策日志（哪些内容需要再平衡、哪些需要终止、哪些需要规模化）。
  • 输出：度量方案+运营节奏（若已知则标注负责人）。
  • 校验：每个关键指标均关联数据源及更新频率；运营节奏需产出具体决策，而非仅状态更新。

7) Quality gate + finalize the pack

7) 质量校验+最终整理管理包

  • Inputs: Draft pack; references/CHECKLISTS.md and references/RUBRIC.md.
  • Actions: Run the checklist and score with the rubric. Tighten the pack until it is specific, segment-aware, and testable. Always include Risks / Open questions / Next steps.
  • Outputs: Final Marketplace Liquidity Management Pack.
  • Checks: The next 2 weeks of work are unblocked (data pulls, 1–3 experiments, cadence).
  • 输入：管理包草稿；references/CHECKLISTS.md及references/RUBRIC.md
  • 动作：执行校验清单并按评分标准打分。优化管理包直至内容具体、细分领域明确且可测试。必须包含风险/待解决问题/下一步行动。
  • 输出：最终版平台流动性管理包。
  • 校验：未来2周的工作无阻碍（数据提取、1-3个实验、运营节奏落地）。

Quality gate (required)

质量校验（必填）

  • Use references/CHECKLISTS.md and references/RUBRIC.md.
  • Always include: Risks, Open questions, Next steps.
  • 需使用references/CHECKLISTS.md及references/RUBRIC.md。
  • 必须包含：风险、待解决问题、下一步行动。

Examples

示例

Example 1 (services marketplace, geo fragmentation):
“Use 
marketplace-liquidity
. We run a home cleaning marketplace across 12 cities. Goal: increase booking fill rate from 62% → 80% in 8 weeks in our bottom 4 cities. We suspect supply is thin and response times are slow. Output a Marketplace Liquidity Management Pack with a segment scorecard, bottleneck diagnosis, and a prioritized experiment backlog.”
Example 2 (B2B marketplace, category imbalance):
“Use 
marketplace-liquidity
. We match startups with freelance designers. Liquidity is strong in ‘logo design’ but weak in ‘product design’ and ‘brand refresh.’ Goal: cut median time-to-first-qualified-match from 5 days to 2 days for product design in 60 days. Provide a liquidity metric tree, fragmentation map, and operating cadence.”
Boundary example (not a liquidity problem):
“Write Google Ads copy to get more buyers.”
Response: this is primarily acquisition/copy. If marketplace reliability is already strong, use 
copywriting
/ channel-specific growth work. If reliability is unknown, start with an intake to confirm a liquidity bottleneck first.
示例1（服务类平台，地域碎片化问题）：
“使用
marketplace-liquidity
工具。我们在12个城市运营家政服务平台。目标：8周内将底部4个城市的预订成交率从62%提升至80%。我们怀疑供给不足且响应时长过长。产出包含细分领域评分卡、瓶颈诊断及优先级实验待办清单的平台流动性管理包。”
示例2（B2B平台，品类失衡问题）：
“使用
marketplace-liquidity
工具。我们对接初创企业与自由设计师。‘Logo设计’品类流动性良好，但‘产品设计’和‘品牌升级’品类流动性薄弱。目标：60天内将产品设计品类的首次合格匹配中位时长从5天缩短至2天。提供流动性指标体系、碎片化地图及运营节奏方案。”
边界示例（非流动性问题）：
“撰写谷歌广告文案以获取更多买家。”
回应：这主要属于获客/文案范畴。若平台可靠性已达标，请使用
copywriting
/渠道增长相关工具。若可靠性未知，请先通过需求收集确认是否存在流动性瓶颈。