How Product Managers Compare Product Versions Across Eras
For Product managers comparing software or hardware across versions · Based on Cricket Ball Era Performance Evaluation Framework
// TL;DR
Product managers can adapt the Cricket Ball Era Performance Evaluation Framework to compare product versions across release cycles. Instead of bowler and batter, use a power user and a casual user as dual-perspective evaluators. Score each version independently on specialist control (the power user's 'something to work with') and intuitive ease (the casual user's 'ping'). The balance gap between scores reveals which version best served both audiences—and where your current version may be failing one side.
Why should product managers evaluate versions across eras?
Product teams often assume the latest version is the best. The Cricket Ball Era Performance Evaluation Framework challenges this assumption by requiring you to test older versions alongside current ones, scored independently from two opposing perspectives. A power user who configures and builds (the bowler equivalent) and a casual user who consumes and interacts (the batter equivalent) often have conflicting needs. This framework surfaces exactly where and how each version serves or betrays each audience.
The result is not a feature-count comparison. It is a balance assessment that tells you whether your product's evolution has drifted toward one user type at the expense of the other.
How do you map cricket ball concepts to product evaluation?
The Seam-as-Anchor Principle becomes the core structural element of your product—the single feature most determinative of both user types' experience. For a SaaS dashboard, this might be navigation hierarchy. For a hardware device, it might be the primary input mechanism.
The Ping Test becomes the casual user's satisfaction checkpoint: does using this version produce a clean, satisfying interaction, or does it feel dead and effortful? If the ping is absent—if casual users struggle to find basic value—cap the casual-user score regardless of power-user enthusiasm.
Hardness-Inside vs. Hardness-Outside maps to surface polish vs. underlying architecture. A product can look modern and slick (external hardness) but have a sluggish or unintuitive backend (soft core). Test both dimensions separately.
How do you run the evaluation step by step?
Sequence your product versions chronologically—V1, V2, V3, etc. Brief both evaluators on the design philosophy and constraints of each version before testing. Then have the power user assess control density, customisation latitude, and workflow efficiency. Independently, have the casual user assess navigation intuitiveness, task completion ease, and satisfaction feel.
Score each version out of 10 from both perspectives. Do not average. A version scoring 9 for power users and 4 for casual users has a gap of 5—flagged as a contest-breaking design under the Bat-Ball Balance Standard.
What does the balance gap tell you about your product roadmap?
If the gap has widened over recent versions, your product is drifting toward one audience. The framework's reform recommendation step forces you to identify the single structural change that would most restore balance. Frame it using the Seam-as-Anchor Principle: what is the one core element you need to standardize or redesign to serve both audiences?
This is not a feature request list. It is a structural diagnosis that grounds your next product cycle in balance rather than feature accumulation.
Next step: Pull three to five historical versions of your product, recruit one power user and one casual user, and run a half-day evaluation session using the nine-step workflow.
// FREQUENTLY ASKED QUESTIONS
How do I find the right power user and casual user for product version testing?
Select a power user who has used your product daily for configuration or building tasks and a casual user who interacts with it occasionally for consumption or simple actions. They should represent opposite ends of your user spectrum. Avoid selecting two similar users—the framework's value depends on the tension between perspectives.
Can I use this framework for comparing competitor products instead of my own versions?
Yes. Hold era constant and vary by competitor. Brief evaluators on each competitor's design philosophy instead of era context. The dual-perspective scoring, Ping Test equivalent, and balance gap analysis apply identically. You trade inflection-point analysis for a cross-competitor balance comparison, which is equally valuable for positioning decisions.
What if my product only has two versions to compare?
Two versions is the minimum viable comparison. You can still apply dual-perspective scoring and calculate the balance gap. However, you lose the ability to identify inflection points or trajectories. If possible, add a competitor's product as a third item to create a more meaningful comparison baseline.