game design kpi coverage audit

The problem

Game development teams often over-prioritize features with easy-to-track metrics like direct revenue or DAU. This leads to undervaluing critical UX improvements, infrastructure, and "connective tissue" features that lack clean attribution but are vital for long-term retention.

What it does

• Identifies the true role of a feature, distinguishing between standalone engagement, monetization, and foundational infrastructure.
• Audits current KPI frameworks to reveal measurement gaps where value is ignored by standard tracking.
• Diagnoses specific blind spots, such as when structural health is sacrificed for short-term visible wins.
• Calculates prioritization risks resulting from narrow metric framing.
• Provides concrete recommendations for mixed scorecards or alternative evaluation methods for hard-to-measure work.

Why this beats prompting it yourself

General LLMs often default to standard business metrics and struggle to justify non-attributable work. This skill uses specialized logic to identify "enabling value" and structural dependencies that generic prompts miss, preventing the systematic bias toward flashy features over sustainable design.

Use cases

• Justifying a "quality of life" (QoL) update that won't move revenue but will reduce churn.
• Auditing a roadmap to see if technical debt is being ignored due to KPI pressure.
• Reframing UX improvements from "nice-to-have" to "critical friction reduction."
• Evaluating foundational systems that support future content releases.