The 10-Dimension Product DNA Self-Audit

Most product strategy conversations happen in the wrong register. Teams debate positioning before they've agreed on what kind of growth they're actually running. They argue about pricing tiers before the retention model is understood. They ship activation flows optimized for a user journey that doesn't match how buyers actually buy. The confusion isn't a communication problem. It's a structural one: the assumptions underneath the product decisions have never been made explicit.

The 10-Dimension Product DNA audit is designed to fix that. It takes 45 to 90 minutes. It produces a score across ten structural dimensions of your product and surfaces where those dimensions conflict, where they compound, and which strategic choices are actually available given your current configuration. The audit doesn't generate answers. It generates questions your strategy must be able to answer.

Why "product strategy" keeps failing in practice

Strategy documents get written, reviewed, and ignored. The reason isn't lack of effort. It's that most product strategy documents describe what a team wants to do without grounding it in the structural characteristics of the product itself. You can't make a credible pricing decision without knowing your expansion model. You can't design activation without knowing your complexity and time-to-value profile. These aren't isolated choices. They're a system, and systems have internal consistency requirements.

The audit framework below forces consistency. Each dimension gets scored from 1 to 5. A score of 1 means you're fully at the low end of that spectrum. A score of 5 means you're fully at the high end. Most products sit at 2, 3, or 4. The score isn't right or wrong. What matters is whether the scores across dimensions are coherent with each other and with the market you're in.

Run this with your product team, your growth lead, and ideally your best customer-facing person. Do it separately first, then compare. Divergence between scores is data.

The 10 Dimensions: Questions, Spectrums, and Implications

Dimension 1: Competitive Positioning

The question is: where does your product sit on the spectrum from "category leader / only credible option" to "challenger / clear alternative to an established player"?

• Score 1-2 (Challenger): You win by being faster, cheaper, or more focused on a segment the incumbent underserves. Your positioning is defined in relation to someone else. Sales cycles include "why not X?"
• Score 4-5 (Category leader / creator): You define the category frame. Competitors are positioned against you. You bear the education cost for the category but capture the category premium.

Low scores on this dimension require a sharper ICP and a harder "who we're not for" statement. High scores require genuine category defense: content, community, integrations, or switching costs that make the position real rather than aspirational. Claiming category leadership without those mechanisms is a brand position, not a product strategy.

Dimension 2: Complexity and Time-to-Value

The question is: how long does it take a new user to get a meaningful result, and how much configuration or expertise does that require?

• Score 1-2 (Low complexity, fast TTV): A user can get a real result in minutes with no configuration. Self-serve is viable. Churn often comes from the product being too simple for growing use cases.
• Score 4-5 (High complexity, slow TTV): Meaningful value requires integration, customization, or a learning curve measured in days or weeks. Churn comes from failed onboarding. CAC must be high enough to justify white-glove support.

This dimension is frequently underscored. Teams rate themselves a 2 or 3 because the product is technically easy to start. They forget that "starting" and "getting value" are different events. Score this on the basis of when users get a result they would pay for, not when they finish signup.

Dimension 3: Activation Pattern

The question is: what triggers a user's "aha" moment, and does that trigger require the user to act or the product to act?

• Score 1-2 (Product-initiated activation): The product pulls the user toward value. It shows them something useful on first login, makes a recommendation, or surfaces a result before they've set anything up. Activation rates tend to be higher.
• Score 4-5 (User-initiated activation): The user must configure, connect, import, or explore before value appears. Activation rates depend heavily on onboarding quality and user intent at signup.

High-complexity products (Dimension 2 score of 4-5) cannot have a user-initiated activation pattern without paying for it in onboarding conversion. The combination forces either a sales-assisted model or a fundamentally redesigned first-use experience.

Dimension 4: Growth Motion

The question is: how does the product grow, primarily through product behavior or primarily through sales and marketing effort?

• Score 1-2 (Product-led growth): Acquisition, conversion, or expansion happens because of what users experience inside the product. Viral loops, usage-based upgrade prompts, or network effects do the heavy lifting.
• Score 4-5 (Sales-led growth): Deals are closed by sales people. The product supports the deal but doesn't drive it. Growth is a function of pipeline volume and rep efficiency.

Neither end of this spectrum is better. But PLG and SLG have completely different operational requirements, cost structures, and team compositions. Mixed-motion products (hybrid PLG/SLG) work, but they require explicit boundaries: which customer segment gets which motion, and who owns the handoff. Most teams that claim hybrid are actually running SLG with a free trial grafted on.

Dimension 5: Expansion Model

The question is: how does revenue per account grow over time, and what drives that growth?

• Score 1-2 (Seat expansion / head count driven): More users at the account means more revenue. Expansion requires spreading adoption internally. Champions become internal sellers.
• Score 4-5 (Usage or outcome driven expansion): Revenue grows as the customer does more with the product. This is the foundation of usage-based pricing models and the reason median NRR for usage-based SaaS hits 108% (OpenView, 2024).

Expansion model determines your NRR ceiling before pricing conversations begin. A seat-based expansion model in a market where buyer organizations are shrinking their headcount is a structural NRR problem, not a sales problem.

Dimension 6: Retention Moat Type

The question is: why do customers stay, and what would they lose if they left?

• Score 1-2 (Workflow lock-in): Customers stay because the product is embedded in daily processes. Switching requires re-training and re-tooling. This moat is real but fragile if a competitor offers a migration path.
• Score 4-5 (Data or network lock-in): Customers stay because their data lives in the product, their team's activity is recorded there, or the network value requires other users. The moat compounds over time.

Workflow lock-in and data lock-in are both legitimate moats. The mistake is assuming you have one when you have the other. If your users could export everything and re-import it to a competitor in a day, your moat is switching cost, not data lock-in. That's a weaker moat, and your retention investment should reflect that.

Dimension 7: User Topology

The question is: who uses the product within an account, and how do those users relate to each other?

• Score 1-2 (Individual users, no interdependence): Each user gets value independently. There's no collaboration surface, no shared workspace. Expansion happens by adding users, not by deepening network effects.
• Score 4-5 (Team-dependent, network effects present): Value increases as more users from the same team or organization use the product. A single user churning doesn't kill the account. A team abandoning the product does.

High scores on User Topology change your churn model fundamentally. You're not tracking individual user health, you're tracking team-level adoption depth. Products that score 4-5 here should have account health metrics that measure breadth of usage across roles, not just engagement from the primary user.

Dimension 8: Buyer vs. User Map

The question is: how far apart are the buyer and the user, and does that distance create misalignment in what the product must do?

• Score 1-2 (Buyer and user are the same or closely aligned): The person who pays is the person who uses. Feedback loops are short. Value is self-evident to the decision-maker.
• Score 4-5 (Buyer and user are structurally separate): A manager or executive buys. An individual contributor uses. The product must serve both audiences with different value propositions. ROI metrics matter to the buyer. Ease of use matters to the user. Failing either is a churn risk.

This dimension drives your product's reporting and administrative surface requirements more than any other. A product scoring 4-5 here that doesn't have strong admin dashboards, ROI reporting, and user management is selling to buyers who are making blind purchasing decisions.

Dimension 9: Value Delivery Model

The question is: is value delivered primarily through the product itself, or through the outcomes the product enables?

• Score 1-2 (Product delivers value directly): Users take an action in the product and value is immediate. A Loom video recorded and shared. A spreadsheet calculated. A report generated. The product is the value.
• Score 4-5 (Value is downstream of the product): The product enables a process that creates value. The product's contribution to that value is indirect and measured over time. Revenue attribution, pipeline influence, team performance improvements are examples.

High scores on this dimension create a retention risk: if outcomes don't materialize, customers blame the product even when the product performed correctly. Success teams, onboarding for the outcome not just the feature, and clear success metrics at contract signing are the operational response to a Score 4-5 here.

Dimension 10: Pricing Architecture

The question is: how is pricing structured, and does that structure align with how customers perceive value?

• Score 1-2 (Flat or seat-based pricing): Predictable for the customer. Predictable for the vendor. Limited NRR expansion potential. Works well when usage is relatively uniform across accounts.
• Score 4-5 (Usage-based or outcome-based pricing): Revenue scales with customer success. Higher NRR ceiling. More complex to forecast and manage. Requires customers to understand the value metric clearly before they commit.

Pricing architecture should follow Expansion Model (Dimension 5), not precede it. If your expansion model is usage-driven but your pricing is seat-based, you're leaving NRR on the table. If your expansion model is seat-driven but your pricing is usage-based, you're creating procurement friction and forecast risk with no compensating benefit.

The 4 Most Common Contradiction Pairs

Most product teams can score each dimension in isolation. The harder work is reading the score sheet as a whole. These four contradiction pairs appear most often in the audits I run, and each one has a consistent structural explanation.

Contradiction 1: High Complexity + Self-Serve Activation

A Dimension 2 score of 4-5 combined with a Dimension 3 score of 4-5 (user-initiated activation) is a math problem, not a product problem. High-complexity products have long time-to-value curves. Self-serve activation requires users to find value without assistance. Put them together and activation rates collapse unless the onboarding sequence is doing the work a sales engineer would otherwise do. Teams that find themselves in this pair have three options: invest heavily in guided onboarding (interactive walkthroughs, pre-configured templates, immediate demo data), add a sales-assisted layer for high-intent signups, or simplify the initial experience to reduce complexity before first value.

Contradiction 2: PLG Motion + Seat-Based Pricing

A Dimension 4 score of 1-2 (product-led growth) combined with a Dimension 10 score of 1-2 (seat-based pricing) creates a fundamental misalignment between the growth motion and the revenue model. PLG works by letting users experience value before committing to paying. Seat-based pricing charges per person up front. The two don't cohere unless the product has a genuinely compelling free tier, meaning one where the free user gets enough value that they bring in paying colleagues. Freemium-to-seats works at Slack's scale. Most products don't have Slack's viral coefficient. If your growth motion scores PLG but your pricing is seat-based without a strong free tier, you're running SLG with a free trial, and you should budget for it accordingly.

Contradiction 3: Network-Effect Retention + Individual User Topology

Claiming a network-effect retention moat (Dimension 6 score of 4-5) while having an individual user topology (Dimension 7 score of 1-2) is a story that doesn't hold. Network effects require interdependence. If each user gets value independently and doesn't need other users to get more value, there is no network effect. What you probably have is workflow lock-in or data accumulation, which are legitimate moats. Name them correctly, because they require different defensive investments. Workflow lock-in is defended through integrations and migration friction. Data accumulation is defended through analytics, insights, and making the data increasingly useful over time.

Contradiction 4: Separate Buyer/User Map + Weak Reporting Surface

A Dimension 8 score of 4-5 (buyer and user are structurally separate) requires the product to speak two languages simultaneously. The user needs a great daily-use experience. The buyer needs proof that the investment is working. Products that score high on Buyer/User Map and don't have strong administrative dashboards, ROI reporting, and aggregated usage visibility are selling on faith. Buyers renew on proof. If the product can't show a VP or a CFO what the team is doing and what value that maps to, renewal conversations become uncomfortable negotiations rather than straightforward continuations.

How to use the output to make an actual decision

The score sheet produces two types of output: a picture of your current structural configuration, and a map of which changes are available to you without changing the product itself.

Start with the contradiction pairs. If you have one or more, each one is a specific structural bet you're implicitly making. The question isn't whether the bet is wrong. It's whether it's deliberate. A high-complexity product with self-serve activation might be a deliberate bet that your onboarding investment will compensate. That's a valid strategic choice. The problem is when teams discover the contradiction pair during a churn postmortem rather than during a strategy session.

Next, read the dimensions that cluster at the same end of the spectrum. A product that scores 1-2 across Competitive Positioning, Growth Motion, and Pricing Architecture is configured for a specific kind of market: challenger, product-led, usage-based. That configuration has coherence. The strategic questions become about execution: how fast can you grow the user base, and when does the usage-based pricing switch from a discount to a premium?

A product that scores 4-5 across Complexity, Buyer/User Map, and Value Delivery Model is configured for a different market: enterprise, sales-assisted, outcome-oriented. Again, coherent. The strategic questions are about the sales motion: what does the enterprise sales cycle look like, how do you prove ROI before and after purchase, and what's your champion development strategy?

The products that are hardest to run are the ones with mixed configurations. They're not incoherent by definition. But they require explicit operational decisions for each contradiction: which motion applies to which segment, who owns which journey, and how do you avoid the worst of both worlds rather than getting the benefits of both. Use the score sheet to name those decisions explicitly before the next planning cycle.

Running the audit in practice

Score independently before discussing. Every participant writes their own scores for all ten dimensions before the group meets. Divergence across participants is the point. A score spread of 3 on a single dimension means your team has fundamentally different mental models of what product you're building. That's a more important finding than any individual score.

Time-box the scoring at 20 minutes. If a dimension takes more than 2-3 minutes to score, that's a signal in itself: you don't have clear enough signal from the market to score it confidently. Mark it as uncertain rather than forcing a number.

When the group compares scores, start with the dimensions where there's the most spread. Those are the conversations that need to happen. Work through each contradiction pair last. The contradiction pairs are structural claims that need either a decision to resolve them or a deliberate choice to hold the tension.

Document the final scores, the divergent scores, and the contradiction pairs you identified. That document is your strategic checkpoint. Re-run the audit when you enter a new market, after a significant product pivot, or when growth stalls and you're not sure whether it's a product problem, a positioning problem, or a motion problem. The audit won't tell you which it is, but it will tell you which ones are structurally possible given your current configuration.