Key Principle
The RPV framework is a diagnostic tool for understanding organizational capability and -- critically -- organizational disability. It identifies three categories that determine what an organization can and cannot do:
Resources are the most visible and flexible factor: people, technology, cash, brand, relationships, equipment. Resources can be hired, bought, and transferred. When managers ask "do we have what it takes?", they typically inventory resources. But resources alone are insufficient to predict success.
Processes are the patterns of interaction, coordination, communication, and decision-making through which resources are transformed into products and services. They include formal processes (product development, budgeting, market research) and informal ones (how decisions really get made, how priorities are set day-to-day). Processes are designed to perform a specific, repetitive task reliably. A process that is highly capable at one task is, by definition, incapable at a different task. This is why processes define both capability and disability simultaneously.
Values are the criteria by which employees make prioritization decisions -- what gets funded, what gets attention, what gets killed. In a well-run company, values are consistent across the organization so that employees at every level make decisions aligned with the firm's strategic direction. A company that requires 40% gross margins will systematically deprioritize opportunities offering 18% margins. This is not a bug; it is the value system working correctly. But it means the organization is structurally disabled from pursuing low-margin disruptive opportunities.
The central insight: as companies mature, the locus of capability migrates from resources (startups depend on key people) to processes (mid-stage firms develop reliable methods) to values (large firms run on decision criteria). This migration makes organizations more predictable and efficient -- and simultaneously more rigid against disruptions that do not fit the established value filters.
Why This Matters
Without the RPV framework, managers misdiagnose organizational failure as a people problem. They assume that putting good people on a disruptive project is sufficient. But the processes those people use and the values by which their work is judged will filter out the disruption. The framework reveals that you cannot solve a process-and-values problem by reassigning resources.
This explains why even well-funded corporate ventures fail when housed within the parent organization's processes and values. The venture has the resources (engineers, capital, technology) but is evaluated by the wrong criteria and forced through workflows designed for a different type of innovation. The prescription -- which follows directly from the diagnosis -- is that disruptive efforts need their own processes and values, which typically means a separate organizational unit.
Good Examples
Processes as both capability and disability: A company with a finely tuned stage-gate product development process can reliably deliver sustaining innovations on schedule. That same process will kill a disruptive project because it requires market size quantification, margin analysis, and customer validation that are impossible for a market that does not yet exist. "Companies whose investment processes demand quantification of market sizes and financial returns before they can enter a market get paralyzed or make serious mistakes when faced with disruptive technologies." (Introduction) The process is not broken -- it is doing exactly what it was designed to do, which is the problem.
Values as decision filters in steel: Integrated steel mills required margins that rebar could not deliver, so they rationally ceded it. Minimills, with lower overhead and values calibrated to lower-margin business, found rebar attractive. Each company's values correctly filtered opportunities according to its cost structure -- but this meant integrated mills could not pursue the disruptive path even when they recognized the threat. (Chapter 4)
The capability migration lifecycle: A startup's capability resides in its founders -- specific people with specific knowledge. As the firm grows, it develops processes that encode that knowledge into repeatable systems. As it matures further, those processes harden into values (margin thresholds, market-size minimums, planning horizons). The organization becomes more capable at its core task and less capable at anything outside the scope of those values. The very success of the maturation process creates the disability. (Chapter 8)
Counterpoints
Resources are necessary but not sufficient: Seagate had the engineers, the manufacturing capability, and the capital to lead in 3.5-inch drives. It had approximately 80 working prototypes. The resources were present. The processes (market validation through existing customers) and values (margin requirements set by the mainframe-to-minicomputer value network) killed the project. Diagnosing this as a resource problem would have led to the wrong intervention -- hiring more engineers or allocating more budget. (Chapter 1)
The CEO override fails at the process and values level: A major disk drive CEO personally championed four generations of 1.8-inch drives; none sold. The CEO controlled resource allocation at the top, but the hundreds of daily micro-decisions made by salespeople, engineers, and middle managers -- all governed by established processes and values -- redirected effort toward mainstream customers. Honda was buying 1.8-inch drives from a Colorado startup while the CEO's own salesforce ignored the opportunity. (Chapter 4)
Acquiring resources does not acquire processes or values: When a large firm acquires a small disruptive company and integrates it into the parent organization, it gets the resources (people, technology, IP) but destroys the processes and values that made the acquisition successful. The acquired team is now evaluated by the parent's margin thresholds and managed through the parent's stage-gate process. The capability that justified the acquisition evaporates. (Chapter 8)
Key Quotes
"Companies whose investment processes demand quantification of market sizes and financial returns before they can enter a market get paralyzed or make serious mistakes when faced with disruptive technologies." — Clayton M. Christensen, Introduction
"It is very difficult for a manager to motivate competent people to energetically and persistently pursue a course of action that they think makes no sense." — Clayton M. Christensen, Chapter 4
"Good management itself was the root cause." — Clayton M. Christensen, Part Two Introduction
"The most formidable barrier the established firms faced is that they did not want to do this." — Clayton M. Christensen, Chapter 2, quoting Richard Tedlow
Rules of Thumb
- When assessing whether your organization can pursue a disruptive opportunity, audit processes and values -- not just resources
- If your company's margin threshold would cause it to reject the disruptive opportunity, no amount of executive enthusiasm will overcome the structural filter
- Separate organizational units need their own processes and values, not just their own budget and headcount
- Do not integrate acquisitions of disruptive companies into the parent organization; doing so preserves resources but destroys the processes and values that made the acquisition valuable
- The more mature and efficient your organization, the more its capabilities have migrated from flexible resources to rigid processes and values -- and the more vulnerable it is to disruption outside those parameters
Related References
- The Innovator's Dilemma: Core Thesis - The overarching thesis that RPV helps diagnose at the organizational level
- Value Networks and the Six-Step Failure Pattern - How value networks impose the cost structures that become organizational values
- Asymmetric Mobility and the Northeast Pull - The upmarket drift that RPV's values component mechanistically explains