Index of every page on this site: llms.txt
All skills
deanpeters avatar

/usage-data-investigation

@476ae12
Run it yourself

Investigate what customers actually do from product analytics, with every claim labeled Fact, Inference, or Assumption. Use when you need behavior evidence, not opinions, before deciding.

Use this Skill: https://skilld.dev/gh/deanpeters/product-manager-skills/usage-data-investigation

Nothing lands on disk. Nothing to clean up.

Fork this Skill

Edit a local copy. It keeps the author and licence.

examplessample.md

≈538 tokens on demand. Your agent reads this file only when SKILL.md points to it.

Usage Data Investigation Example: SaaS

Question: trials of the Route Optimizer start, but few reach a first optimized route. Where do they stall, and who? Unit: trial account · Window: March trials · Decision: where to focus onboarding work

Why this example exists: the funnel showed one step, but the segment cut showed it was really one kind of account, and the data had nothing to say about why.


## Data check
- Tracking: "first optimized route" fires on route save; verified on three test accounts.
- Definition: unchanged in window.
- Missing: 6 internal test accounts removed; 3 trials from a partner API not tracked (noted).
- Sample: 212 trial accounts. Enough to read the funnel; thin for segments under 20.

## Funnel (March trials, N = 212)
| Step | Count | To next |
|---|---|---|
| Trial started | 212 | 78% |
| Dispatcher invited | 165 | 71% |
| Day loaded | 117 | 42% |
| First route optimized | 49 | n/a |
**Biggest drop:** day loaded → first optimized (117 → 49).

## Segments
| Segment | N | Reached first route |
|---|---|---|
| 50-100 technicians | 88 | 24 (27%) |
| 101-300 technicians | 84 | 22 (26%) |
| Over 300 | 40 | 3 (8%) |

## Findings
1. **Fact:** 49 of 212 trials (23%) reached a first optimized route within 7 days.
2. **Fact:** the biggest drop is between loading a day and optimizing it (117 to 49).
3. **Fact:** accounts over 300 technicians reached it at 8% (3 of 40) vs about 27% elsewhere.
4. **Inference:** large accounts may need a configuration step the smaller ones skip. (Not shown.)
5. **Assumption:** dispatchers don't see value. (The data can't show this.)

## What people must answer
| Question | Who | Ask |
|---|---|---|
| Why do large accounts stop after loading a day? | Dispatchers at 5 large trial accounts | "Walk me through what you did after the day loaded." |

What to learn from this

  • The average (23%) hid a segment (8%). The finding was in the cut.
  • Finding 4 is labeled an Inference, and finding 5 an Assumption nobody should act on.
  • The investigation ends with five phone calls, which is what the data pointed toward.

Source: SKILL.md on GitHub

No rule matched.

skilld matched fixed text patterns in SKILL.md and file names. Patterns miss obfuscated code.

skilld run checks every file with the same patterns. It asks for approval before it loads a Skill with a behavior marked Needs approval.

1 warning6d3 checks · Risk SAFE
  • Gen Agent Trust Hub6d

    This skill is a collection of markdown-based workflow instructions for analyzing product usage data. It contains no executable code, scripts, or network-capable operations and is safe to use.

  • Socket6d

    No alerts

  • Snyk6d

    Risk: MEDIUM · 1 issue

Signed by skilld at 476ae12. This ties the file your Agent reads to that commit on GitHub. It does not review the instructions.

Last checked against GitHub last week.

Activeupdated last week
argument-hint
[the question about customer behavior, and what data you can reach]
type
workflow
theme
discovery-research
Other metadata
intent
Turn a question about customer behavior into a disciplined read of product usage data: define the question and the unit of analysis, check the data's trustworthiness, look at funnels, cohorts, and segments, separate what the data shows from what you conclude, and name the follow-up that qualitative research must answer. Quantitative discovery that points to the "why" without claiming it.
best_for
[
  "Finding where customers drop off, and who, before deciding what to build",
  "Checking a belief about behavior against what the product data shows",
  "Reading a launch or trial funnel, cohorts, and segments honestly",
  "Knowing which question the numbers can't answer and a conversation must"
]
scenarios
[
  "Trials start but few reach a first optimized route. Where do they stall?",
  "Leadership says feature X is popular. What does the usage data actually show?",
  "Do customers who onboarded after the fix retain better than those before?",
  "Commissioned units report faults early. Which unit configurations, and when?"
]
estimated_time
45-90 min

README badge

README badge for deanpeters/product-manager-skills/usage-data-investigation