Alvin Lopes monogram
← Selected work
Work
Enterprise Customer Success
Enterprise accounts, multi-year

The Recurring Business Review System

A repeatable way to tell a large organization the truth about its own performance, every month, without starting from a blank page.

Business ReviewsKPI StorytellingAccount Health

Sanitized for publication. Company names, customer identities, and proprietary figures have been removed.

01

Purpose

A portfolio of enterprise accounts needed a regular, honest read on how their programs were performing. Each account had different stakeholders, different maturity, and different appetite for detail. Writing every review from scratch was slow and produced inconsistent quality. The system existed so the format could be reliable and the thinking could be the variable part.

02

The problem

Reviews had drifted into data dumps. Charts were included because they were available, not because anyone would act on them. Different accounts got different framing for the same question, which made it impossible to compare performance across the portfolio or to hold anyone accountable to a number they had seen the month before. Meanwhile the sections that actually mattered, the recommendations, kept ending up last and rushed.

03

The thinking

  • Fix the structure so the argument can vary. A stable spine means the reader spends attention on what changed rather than on finding their way around the document.
  • Separate performance from experience. One answers whether the program is being used. The other answers whether people like using it. Mixing them hides both.
  • Every metric needs a comparison. A number with no prior period and no benchmark is trivia.
  • The review ends in recommendations or it should not have been scheduled.
  • Match the cadence to the decision. Post-launch reviews answer did this land. Monthly reviews answer what do we adjust. Quarterly reviews answer should the plan change.
  • Write the headline first. If the one sentence at the top is not obvious, the analysis is not finished.
04

What was created

  1. 01

    A master review template

    A fixed spine, performance, then experience, then recommendations, then resources, with a defined slide for each idea. New accounts inherited it on day one instead of inventing a format under deadline.

  2. 02

    Three cadence variants

    Post-launch, monthly, and quarterly versions of the same structure, differing in time horizon and in the type of decision each was built to produce.

  3. 03

    A standard metric set

    Adoption, active usage, retention by cohort, event mix, referral and conversion, ratings and sentiment, support volume. The same definitions used across every account so the portfolio could be compared honestly.

  4. 04

    A recommendations discipline

    Every review closed with specific actions, an owner, and a benchmark to measure against. Where an account was behind a known standard, the gap was stated plainly rather than softened.

05

Selected artifacts

Figure 01 — The review spine
ONE STRUCTURE, THREE CADENCESPost-launchMonthlyQuarterlyPerformanceAdoption, usage, retentionExperienceRatings, sentiment, supportRecommendationsWhat to do next monthResourcesAssets, owners, timingTHE REVIEW EXISTS TO PRODUCE A DECISION, NOT A REPORT.
One structure carried across three cadences. Redrawn from the format rather than from any account's material.
Figure 02 — Cadence, audience, purpose
CADENCE · AUDIENCE · PURPOSEDailyOperationsUnblock what is stuckWeeklyFunction leadsSpot the pattern earlyMonthlyAccount and leadershipDecide the next moveQuarterlyExecutiveChange the planIF A READ HAS NO DECISION ATTACHED, RETIRE IT.
Each read exists for a different decision. When a read has no decision attached, it should be retired rather than reformatted.

Shared framework · The same structure also supports Service Level Framework and Operating Dashboard Redesign.

06

Key decisions

  1. 01

    Lead with usage, not downloads

    Download counts made every account look successful. Usage rate did not. Putting the harder number in front made the conversation useful and, in practice, made accounts more willing to act.

  2. 02

    Keep a resources section

    Recommendations fail when the receiving team has to build the assets. Ending with what already exists and who owns it removed the most common excuse for inaction.

  3. 03

    State benchmarks out loud

    Naming the standard turned a subjective review into a measurable one, and made the gap the topic instead of the tone.

07

What it informed

  • Gave a distributed account team one format to write against, which cut preparation time and raised the floor on quality.
  • Made performance comparable across a portfolio instead of account by account.
  • Turned the review from a status update into a recurring decision forum.
  • Set the reporting habits I have carried into every operations role since.
08

Reflection

The template mattered less than the rule that every review ends in a recommendation. Formats are easy to copy. The discipline of committing to a next step in writing, in front of the people who have to do it, is the part that changes anything. The version of this I would build now would be shorter, with fewer charts and a stronger first page.

09

Related work

Next

Incident Communication Strategy

A repeatable way to explain a live product problem to enterprise customers: what is broken, what is being fixed now, what is being fixed properly, and who tells whom.

Continue →