20 articles

Product Management

The mechanisms, review criteria, and decision patterns that determine how this area is underwritten, governed, and priced.

All topics
  1. 01July 16, 20268 minAssigning a Product Owner: The Gap Between the Box on the Org Chart and the Person Who Actually DecidesIn most companies product ownership exists as a title and not as decision authority. What a diligence team looks for is not the presence of the role but whether scope decisions can be made without the founder in the room; that distinction rarely shows up in the multiple, and almost always shows up in the deal structure.
  2. 02July 16, 20268 minProduct Requirements Management: Why a Diligence Team Examines the Decision Trail Before the Product ItselfHow product requirements are captured, who approves them, and what record follows them can matter more in an investment review than the product's current performance, since this mechanism is the earliest observable signal of whether the future roadmap is reproducible without the founder in the room.
  3. 03July 16, 20269 minThe Product Roadmap: A Statement of Intent, or an Institutional Record of Decisions?In most companies the product roadmap exists not as a planning instrument but as a sales narrative. What the diligence table looks for is not the features listed, but how that list came to be — who removed what, on what grounds, and whether any record of the removals survives.
  4. 04July 16, 20268 minProduct Vision: From a One-Sentence Claim to an Auditable Instrument of GovernanceIn an investment review, product vision is examined not as a slogan but as a decision regime binding roadmap choices, resource allocation, and the stated grounds for every request declined. Where the vision resides only in the founder's head, the discount arises not from product quality but from the non-repeatability of the decision.
  5. 05July 15, 20267 minCustomer Problem Validation: Where the Evidence Chain Behind a Product Decision BreaksIn most companies, customer problem validation is not a method but a silent deference to the founder's instinct. What a diligence process looks for is not conviction that the problem exists, but the record showing how that conviction was produced independently of the founder; absent such a record, the product roadmap is priced as an assumption rather than an asset.
  6. 06July 15, 20268 minMVP Scope: What a Product Decision Is Worth at the Valuation TableIn most companies, MVP scope is not a document but a story told in retrospect. What a diligence review looks for is not the product itself, but demonstrable evidence of who fixed the scope, on what basis, and against which threshold; absent that evidence, product risk is reclassified as founder dependency.
  7. 07July 15, 20268 minProduct–Market Fit: A Founder's Narrative, or a Capacity the Company Can Reproduce?In most companies product–market fit survives as a story the founder tells, while the party running the review asks who defined that fit, which records corroborate it, and whether it can be rediscovered once the founder leaves the room. The gap between those two readings is priced directly into the multiple.
  8. 08July 14, 20267 minFeature Prioritization: The Decision Record Behind the RoadmapIn an investment review, feature prioritization is measured not by the roadmap itself but by the reasoning that separated the requests that made the list from those that did not. Prioritization without a record supports the conclusion that product direction rests on founder intuition, and that conclusion is priced into the multiple.
  9. 09July 14, 20268 minProduct Release Management: Record or Recollection?In an investment review, product release management is examined not for release velocity but for verifiability. Where a company cannot show from a record which version runs at which customer, what was promised alongside it and when support ends, that uncertainty migrates into warranty scope, escrow percentage and the support cost assumption.
  10. 10July 14, 20268 minUsage Analytics: When No One Asks How the Product Is Actually UsedIn most companies usage analytics exists as a dashboard but not as a decision mechanism. What a review table looks for is not the presence of charts, but whether a specific product decision can be traced back to a specific piece of usage data; absent that trace, the growth narrative remains an unverifiable claim.
  11. 11July 14, 20267 minUser Feedback: An Institutional Capability, or One Person's Memory?In most companies user feedback survives not as a system but as intuition accumulated by a handful of people. What the diligence table looks for is not a satisfaction score but a traceable path from signal to decision; the absence of that path converts directly into valuation discount.
  12. 12July 13, 20267 minFeature Adoption Rate: The Unmeasured Half of the RoadmapHow much of a product company's engineering budget converts into functionality that is actually used is, in most organizations, a quantity nobody tracks institutionally. The absence of a feature adoption measure reads, at the diligence table, not as a reporting gap but as the conversion of engineering spend into an unverifiable cost line.
  13. 13July 13, 20268 minProduct Documentation: Where the Knowledge Actually ResidesProduct documentation is not an archival matter but a signal indicating whether product knowledge belongs to the institution or to a handful of individuals. The diligence table asks this question directly, and the shortfall is typically deducted not from price but from closing conditions and key-personnel commitments.
  14. 14July 13, 20268 minProduct Lifecycle: The Gap Between What the Catalogue Shows and What the Company Actually ManagesIn most companies the product lifecycle is not a management discipline but the passive drift of sales volume; products are born, they grow, and they age without anyone ever deciding. What the review table looks for is not the number of products, but who decides — and on what evidence — that a product has reached the threshold for retirement.
  15. 15July 12, 20268 minProduct Cost Targets: A Measure of Institutional Discipline, Not of PriceIn most companies the product cost target is not the output of a calculation but the outcome of an argument, and whoever wins that argument determines where cost is allowed to settle. What a diligence team looks for is not the number itself, but how the number was set, who was empowered to defend it, and what happened the moment it was missed.
  16. 16July 12, 20267 minProduct Profitability: What the Company Believes It Knows, and What Diligence Actually AsksMost companies know their aggregate margin and estimate their product-level margin. In an investment review, that distinction determines whether a portfolio is being managed or merely carried — and the valuation multiple separates at precisely that point.
  17. 17July 12, 20267 minProduct Quality Targets: A Verbal Standard Carries No Value at the Deal TableIn most companies the product quality target is not a written threshold but an acceptance line accumulated in the judgment of one senior individual. Under review, that distinction converts into a different question altogether — not whether the product is good, but whether quality has been constituted as a capability the company itself can reproduce.
  18. 18July 12, 20269 minProduct Standardization: Examining Repeatability Rather Than the CatalogProduct standardization is not measured by how many items appear in a company's catalog, but by whether the same product can be produced at the same cost across different periods, different teams and different customers. What the review side looks for is not a list; it is where deviation is contained and under whose authority it is released.
  19. 19July 12, 20268 minProduct Discontinuation Criteria: Portfolio Quality Is Measured by the Discipline to Remove, Not the Capacity to AddEvery company has a process for adding a product; most have only a reason for removing one, never a process. That asymmetry grows the portfolio's lower tail as an accumulation of deferred decisions rather than a decided outcome, and it is priced at the diligence table through normalized earnings and the working capital peg.
  20. 20July 11, 20268 minProduct Variant Management: The Valuation Item That Never Appears in the CatalogueVariant count gets reported as a commercial achievement, while the same number accumulates as cost inside production scheduling, inventory turnover, and post-sale obligation. What a diligence team looks for is not breadth of variation but the rule under which a variant is opened, the rule under which it is retired, and the identity of the role holding that authority.