Usage Pattern Interpreter

Translates raw usage data into account intelligence. Most CSMs have access to product analytics dashboards but struggle to move from "what is the data showing" to "what should I do about it." This skill bridges that gap.

How to Use

Provide whatever usage data you have:

• Dashboard exports (active users, sessions, feature usage, workflow completions)
• Spreadsheet data (CSV or pasted tables)
• Screenshots of analytics with numbers you can describe
• Specific metrics you are trying to understand ("DAU dropped 30% this month -- what does it mean?")

Also provide:

• Account context (segment, product tier, tenure, number of licensed seats)
• Any known context for the data (did they just onboard a new team? Did they lose a key user? Is this a seasonal business?)
• What you are worried about or trying to understand

Pattern Recognition Framework

Step 1: Classify the Data

Organise whatever data you have into these categories:

Step 2: Identify Patterns

Step 3: Contextualise

Raw patterns become actionable when matched to account context:

Step 4: Generate Insights and Recommendations

For each significant pattern detected:

## Usage Pattern Interpretation: [Account Name]
**Data period:** [date range]
**Prepared by:** [CSM name]

### Headline
[One sentence: the most important thing the data is telling you]

### Patterns Detected
| Pattern | Metric | Detail | Confidence | Urgency |
|---------|--------|--------|-----------|---------|
| [pattern] | [metric and values] | [what you observed] | [H/M/L] | [Immediate/This week/This month/Monitor] |

### Context Assessment
[How the account context (seasonal, personnel, strategic) affects the interpretation]

### Recommended Actions
1. [Action tied to a specific pattern]
2. [Action tied to a specific pattern]

### Questions for the Customer
[Specific questions to ask that would confirm or refute your interpretation]

### Watch Signals
[What to monitor in the next 2-4 weeks to see if the pattern continues, reverses, or accelerates]

Common Misinterpretations to Avoid

Quality Gates

• Are you interpreting patterns, not individual data points? A single day's DAU drop is noise. A 3-week declining trend is a signal. The distinction is critical
• Have you considered at least two explanations for each pattern? The first explanation is not always correct. Usage declining could be seasonal, personnel-related, competitive, or product-related. List the possibilities before concluding
• Are your recommendations specific to the pattern? "Schedule a check-in" is not a recommendation for a cliff drop. "Call the customer today to ask about the 40% usage decline and whether it correlates with the champion's departure last month" is
• Have you accounted for known context? A usage decline during December at a retail customer is expected. The same decline in March is not

Principles

• Data tells you what happened. It does not tell you why. Your job as a CSM is to find the why. The data narrows the search space; the conversation with the customer provides the answer
• Trends matter more than snapshots. A health score of 65 is concerning. A health score of 65 that was 78 three months ago is alarming. A health score of 65 that was 52 three months ago is encouraging. The direction is more important than the position
• Not every change is a signal. Usage data is noisy. Holidays, vacations, product releases, and random variation all create fluctuations that look like trends but are not. Apply the "2+ consecutive periods" rule before classifying a change as a trend
• The most dangerous data pattern is the absence of data. An account with no usage data is not healthy by default -- it is invisible. The accounts you cannot see are the accounts you cannot save