Business & Operations

Use when a customer is in the post-sales customer-success phase and the rep+CS need to run a recurring business review / value review meeting (QBR/EBR) with the customer's decision-makers — align goals & baseline pre-meeting, score progress evidence red/yellow/green in-meeting, set next-quarter joint plan, and plant renewal/expansion/referral triggers post-meeting. Triggers: '业务回顾', '复盘', 'QBR', 'EBR', '季度回顾', '价值回顾', '续约前复盘', '客户回顾会', 'quarterly business review', 'executive business review',...

Use when the rep has an upcoming on-site or virtual client visit/meeting where they need to present a proposal or solution to one or more stakeholders — and they need help preparing before, navigating during, and following up after. Triggers include '下周要去客户拜访', '帮我准备提案演示', '客户约了 30/60 分钟会', '怎么准备拜访', '拜访现场怎么应对反对', '临走怎么定下一步', '拜访完怎么复盘', 'visit proposal', 'customer pitch meeting', 'on-site presentation', 'executive briefing prep', 'pre-visit brief', 'field presentation'. Do NOT use for product...

Use when 存量客户合同临近到期（180/120/90/60/30 天节点）需要系统化推进续约——判断健康/风险档位、按档位走续约动作、出续约方案、开续约对话、收续约成交。Triggers: '续约','续费','合同到期','续约风险','续约预测','续约方案','续约对话','save 计划','续约健康分','renewal','renewal playbook','churn prevention','续约率','NRR','GRR','多年期续约'. Do NOT use for new-deal pricing (clinch-negotiation-pricing), account expansion (success-expansion; only renews existing contract), or lost-customer win-back (churn-recovery).

Use when a customer is in the post-sales customer-success phase and the rep+CS need to run a recurring business review / value review meeting (QBR/EBR) with the customer's decision-makers — align goals & baseline pre-meeting, score progress evidence red/yellow/green in-meeting, set next-quarter joint plan, and plant renewal/expansion/referral triggers post-meeting. Triggers: '业务回顾', '复盘', 'QBR', 'EBR', '季度回顾', '价值回顾', '续约前复盘', '客户回顾会', 'quarterly business review', 'executive business review',...

Use when the rep has an upcoming on-site or virtual client visit/meeting where they need to present a proposal or solution to one or more stakeholders — and they need help preparing before, navigating during, and following up after. Triggers include '下周要去客户拜访', '帮我准备提案演示', '客户约了 30/60 分钟会', '怎么准备拜访', '拜访现场怎么应对反对', '临走怎么定下一步', '拜访完怎么复盘', 'visit proposal', 'customer pitch meeting', 'on-site presentation', 'executive briefing prep', 'pre-visit brief', 'field presentation'. Do NOT use for product...

**Situation.** Fieldbook has been live for two quarters in Central, East, South, and West. You're deciding at the quarterly meeting whether to extend it to North and Islands in Q1. **Complication.** The four live regions split sharply in outcome: Central and East reached full adoption within six weeks and paid back Fieldbook's running cost by the second quarter; South and West took two to three times as long to adopt and are only at break-even. That gap traces to three specific, already-diagn...

Fieldbook has improved scheduling, productivity, travel time, overtime and fuel costs in the four live regions. But the rollout will be uneconomic if North and Islands repeat South and West’s slow adoption pattern. Approve a gated Q1 extension: restructure onboarding and assign integration ownership before launch.

Legend: ▲ top / answer · ● first-level group · ○ supporting detail · ⚠ violation · ↑ promote · ⇄ wrong order type · ⊗ overlap · ⊕ gap · ✂ cut or move to appendix Annotated text ```text ⊕ Subject: Period Graph Books [topic label; no answer to the request for corrective proposals] ○ Since Period 5, Financial Analysis has been responsible for producing four graph-presentation books previously handled by Corporate Planning. [situation] ⊕ This memo describes issues that appeared after the transfer...

**Reader:** senior management, who asked for corrective proposals. **Question they hold:** *What should we do about the errors in the graph books?* **Kind of answer that belongs on top:** actions — the changes to make and who makes them. The document delivers a process description and a diagnosis instead, and ends by asking for a meeting.

Legend: ▲ top / answer · ● first-level group · ○ support · ⚠ structural violation · ↑ buried conclusion · ⇄ wrong order · ⊗ overlap · ⊕ gap · ✂ cut or move to appendix ```text Subject: Period Graph Books [⚠ topic label, not an answer] Since Period 5, Financial Analysis has been responsible for producing four graph-presentation books previously handled by Corporate Planning. This memo describes issues that appeared after the transfer. [⚠ states purpose, but does not establish the decision to b...

**Legend:** ▲ top/answer · ● first-level group · ○ support · ⚠ mixed kinds/false grouping · ↑ buried conclusion · ⇄ wrong order · ⊗ overlap · ⊕ gap · ✂ cut/appendix --- Subject: Period Graph Books Since Period 5, Financial Analysis has been responsible for producing four graph-presentation books previously handled by Corporate Planning. This memo describes issues that appeared after the transfer. [Situation given; Complication only implied — no line states what specifically changed for the wo...

Legend: ▲ top / answer ● first-level group ○ supporting detail ⚠ violation ↑ promote ⇄ wrong order type ⊗ overlap ⊕ gap ✂ cut, or move to an appendix ```text Subject: Period Graph Books [⚠][⊕] Since Period 5, Financial Analysis has been responsible for producing four graph-presentation books previously handled by Corporate Planning. This memo describes issues that appeared after the transfer. [⚠] Production [●][⚠] 1. Gather data from divisional forms, internal documents, and telephone calls. ...

| Marker | Meaning | |---|---| | `▲` | top / answer | | `●` | first-level group | | `○` | supporting detail | | `⚠` | violation (mixed kinds, unexplainable order, false grouping) | | `↑` | conclusion buried lower than it belongs — promote it | | `⇄` | wrong order type here | | `⊗` | overlap (ME broken) | | `⊕` | gap (CE broken) | | `✂` | cut, or move to an appendix | Subject: Period Graph Books Since Period 5, Financial Analysis has been responsible for producing four graph-presentation books...

**Reader's question:** management asked for corrective proposals, so the question is *"What should we do to stop the errors in the graph books?"* The answer must therefore consist of **actions** — the changes to be made, who makes them, what it costs. The memo supplies a process description and a diagnosis of causes instead, and never reaches an action.

Legend: ▲ top / answer · ● first-level group · ○ support · ⚠ structural violation · ↑ promote · ⇄ wrong order · ⊗ overlap · ⊕ gap · ✂ cut or move to appendix ```text Subject: Period Graph Books [▲ topic, not an answer] Since Period 5, Financial Analysis has been responsible for producing four graph-presentation books previously handled by Corporate Planning. This memo describes issues that appeared after the transfer. [⚠ purpose statement; it does not state the reader’s decision or the answer...

Subject: Recommendation to reduce composing costs and restore competitiveness Composition accounts for 40–55% of production costs, and TTW is currently uncompetitive on simple titles. Productivity trails industry benchmarks by 20–50%, manual capacity is critically constrained with overtime exceeding budget by 50%, and the union is pressing new claims, yet management lacks clarity on whether costs are excessive or how to resolve them. TTW should simplify the workflow for inexpensive titles and...

Fieldbook has been live for two quarters in Central, East, South and West, and you asked for this review before the quarterly meeting. In that time the platform delivered the scheduling gains it was bought for — but only in the two regions where technicians were properly onboarded, and the program office has no mechanism to stop the same failures repeating in the next region. North and Islands are next, in winter, at £13,500 a month. **Extend to North and Islands in Q1 — but commit the two go...

**Legend:** ▲ top/answer · ● first-level group · ○ support · ⚠ violation · ↑ buried conclusion · ⇄ wrong order · ⊗ overlap · ⊕ gap · ✂ cut/appendix

| Marker | Meaning | |---|---| | `▲` | top / answer | | `●` | first-level group | | `○` | supporting detail | | `⚠` | violation (mixed kinds, unexplainable order, false grouping) | | `↑` | conclusion buried lower than it belongs — promote it | | `⇄` | wrong order type here | | `⊗` | overlap (ME broken) | | `⊕` | gap (CE broken) | | `✂` | cut, or move to an appendix | ```text ⚠ [Topic label, not answer] Subject: Period Graph Books ● [Context] Since Period 5, Financial Analysis has been respons...

**Reader:** senior management, who asked for corrective proposals. **Reader question:** *What should we change so the graph books stop coming out wrong?* **Kind of answer required:** actions/changes — not a description of the process, not reasons the process is bad.

**Markers:** | Marker | Meaning | |---|---| | ▲ | top / answer | | ● | first-level group | | ⚠ | violation (mixed kinds) | | ↑ | conclusion buried lower than belongs | | ⊕ | gap — missing element | --- ▲ [*missing: no answer at top*] Subject: Period Graph Books Since Period 5, Financial Analysis has been responsible for producing four graph-presentation books previously handled by Corporate Planning. This memo describes issues that appeared after the transfer. ● Production 1. Gather data from...

Legend: ▲ top / answer · ● first-level group · ○ support · ⚠ structural violation · ↑ buried conclusion · ⇄ unclear order · ⊗ overlap · ⊕ gap · ✂ cut or move to appendix ```text Subject: Period Graph Books [⚠ topic label, not an answer] Since Period 5, Financial Analysis has been responsible for producing four graph-presentation books previously handled by Corporate Planning. This memo describes issues that appeared after the transfer. [⚠ states purpose, not the reader’s decision question] Pr...

Legend: `▲` top/answer · `●` first-level group · `○` supporting detail · `⚠` violation · `↑` buried conclusion, promote · `⇄` wrong/unexplainable order · `⊗` overlap · `⊕` gap · `✂` cut or move --- ```text Subject: Period Graph Books ⚠ [topic label, not an answer] ○ Since Period 5, Financial Analysis has been responsible for producing four graph-presentation books previously handled by Corporate Planning. This memo ✂ describes issues that appeared after th...

Legend: ▲ top / answer · ● first-level group · ○ support · ⚠ structural violation · ↑ buried conclusion · ⇄ wrong order · ⊗ overlap · ⊕ gap · ✂ cut or move to appendix ```text Subject: Period Graph Books ⚠ Topic label; it does not answer management’s question. Since Period 5, Financial Analysis has been responsible for producing four graph-presentation books previously handled by Corporate Planning. This memo describes issues that appeared after the transfer. ⚠ Purpose statement, not an SCQ i...