Product Analytics
Product Analytics: Analyze a measurable outcome. Review metric definitions, source data, time window, and baseline and produce an analysis with a decision and its evidence.
--- name: product-team-product-analytics description: Use for product analytics when asked to analyze a measurable outcome; produce an analysis with a decision and its evidence. license: MIT metadata: author: Thrive category: product-team --- # Product Analytics ## When to use Use this skill for product analytics when you need to analyze a measurable outcome. The expected result is an analysis with a decision and its evidence. ## Boundaries Work within the requested task and its stated acceptance criteria. Drafting an artifact does not authorize publishing it, spending funds, changing a live system, or contacting another person. Identify any such action separately before taking it. ## Inputs Inspect metric definitions, source data, time window, and baseline. Resolve missing information that would change the method; state lesser assumptions in the result. ## Method 1. **Diagnose.** Name the user segment, unmet job, current workaround, and evidence that the problem is frequent or costly. 2. **Decide.** Choose a comparison that answers the decision question. 3. **Produce.** Build an analysis with a decision and its evidence from the inspected material; keep assumptions distinguishable from observed facts. ## Decision rules - Separate problem discovery from solution selection. Pick a small test that can disconfirm the central assumption. - When sources or constraints conflict, record the conflict and choose the path supported by the user's goal and the strongest available evidence. If neither path can be supported, identify the missing decision before changing the artifact. ## Domain rules - Ground requirements in a named user problem and measurable behavior. - Separate discovery assumptions from acceptance criteria and delivery commitments. ## Verification Show assumptions, uncertainty, and reproducible calculations. Compare the result with the user's acceptance criteria and record any unverified boundary. Write acceptance criteria as observable behavior and state the metric, baseline, owner, and review date. ## Stop conditions If a material input, required authorization, or a safe way to verify the result is absent, stop the affected action. Return the specific blocker and the smallest fact or decision needed to continue. Do not report an unrun check as passed. ## Output Provide an analysis with a decision and its evidence. Include the decisive evidence and actual verification result. Name any artifact location and unresolved issue that affects its use. <!-- MIT License Copyright (c) 2026 Thrive Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions: The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software. THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE. -->