Rands 1.0 Hierarchy

Core Idea

The 1.0 Hierarchy is a four-level diagnostic pyramid — Product, Process, People, Pitch — ordered by dependency: each layer must be genuinely present before the layer above can function, and the inverted shape means every intervention at the top amplifies instability at the base.

Lopp’s 1.0 Hierarchy is a Maslow-inspired diagnostic pyramid describing what a product team must have in place to ship a first version. The four levels — Product, Process, People, Pitch — are ordered by dependency. Lopp presents it as an inverted pyramid: shipping a 1.0 is inherently precarious.

The Four Levels (Base to Apex)

1. Product — You must know what you are building.

• Validated by a neutral external party — the team has lost perspective through proximity
• Failure symptom: building in a vacuum, internal validation substituting for customer contact

2. Process — You must have a visible way to build it.

• Process defines communication. It need not be perfect; it must be visible to everyone
• Failure symptom: decisions made invisibly, Information-Starvation spreading silently

3. People — You must have the right team with the right urgency.

• Everyone must be working with urgency; those who are not are passengers — see Players-vs-Pawns
• Failure symptom: misaligned chemistry, protected underperformers

4. Pitch — You must be able to explain it and earn organisational support.

• The shared north star the team must internalise deeply enough to make decisions without you
• Failure symptom: no one can explain what the product is for, scope creep, inability to say no

Diagnostic Principle

Locate the lowest broken level and repair it first. Fixing Pitch without fixing Process leaves decisions invisible; fixing Process without fixing People leaves communication hollow. The inverted pyramid means every intervention at the top amplifies instability at the base.

The framework applies beyond initial products — engineering reorgs, pivots, and large feature bets share the same dependency structure.

Related Concepts

• Managing Humans - Lopp - 2019
• Information-Starvation
• Players-vs-Pawns
• Hacker-Culture-Growth-Paradox

Sources

• Lopp, Michael (2019). Managing Humans: Biting and Humorous Tales of a Software Engineering Manager. 3rd ed. Apress. ISBN: 978-1-484-23712-4.

  • Chapter 19: “1.0” — Primary formulation of the Rands 1.0 Hierarchy
  • Available: https://link.springer.com/book/10.1007/978-1-4842-2158-7

• Lopp, Michael (writing as “Rands”) (circa 2006). “1.0.” Rands in Repose (blog).

  • Available: https://randsinrepose.com/archives/1-0/

• Maslow, Abraham H. (1943). “A Theory of Human Motivation.” Psychological Review, Vol. 50, No. 4, pp. 370–396.

  • Theoretical foundation for the prepotency hierarchy Lopp adapts
  • Available: https://psycnet.apa.org/record/1943-03751-001

• Wasserman, Noam (2012). The Founder’s Dilemmas. Princeton University Press. ISBN: 978-0-691-14913-4.

  • 65% of high-potential startups fail due to co-founder conflict and team problems — empirical validation of the People level

• Brooks, Frederick P., Jr. (1995). The Mythical Man-Month (Anniversary Edition). Addison-Wesley. ISBN: 978-0-201-83595-3.

  • Communication overhead grows as O(n²) with team size; without visible process, team scaling destroys coordination

Note

This content was drafted with assistance from AI tools for research, organization, and initial content generation. All final content has been reviewed, fact-checked, and edited by the author to ensure accuracy and alignment with the author’s intentions and perspective.