Product Line Systems
The Archetype Sets What’s Possible
Every product line inherits a basic build. Know yours before you commit to a transformation, a pivot, or a recast.
The first form decides the end form.
Product Line Systems
Every product line inherits a basic build. Know yours before you commit to a transformation, a pivot, or a recast.
The first form decides the end form.
The First Form
A product line archetype is the “first form” of a product line as a system (PLaaS) — the basic build from which everything else grows.
End-form systems come later, laying out the detail by adding all the parts and forces. The archetype is simpler and more consequential: it is anchored by a platform-lever, or by its deliberate absence, and that anchor decides what the system can become.
Platform-levers are the critical parts that deliver significantly more bang-for-the-buck than anything else in the line — the reactor, the core design, the operating system, the formula. Organizations drive performance by focusing intensely on this limited set of parts, and that requirement of intense focus sets up a working principle: three or fewer platform-levers when creating a new product line, fewer than seven for a large existing one. Spread the label across every building block and the intensity that makes a lever a lever disappears.
A product line is a complex adaptive system, and the archetype is where its dispositions get set. (See product lines as systems.)
Platform-Lever Types
Nearly any technology building block or module can serve as a platform-lever — but they don’t all deliver the same leverage, and declaring one is a strategic choice, not a given.
| Platform-Lever Type | Platform-Lever Example | Leverage Source |
|---|---|---|
| Production Asset | A chemical reactor, paper-making machine, just-in-time automation | Scale or flexibility |
| Hardware Design | A computer motherboard, a system’s core controller | Design reuse |
| Service System | An automated bank teller, an automated car wash | Automation, speed |
| Software Systems | A software operating system, integrated application software | Versatility within the intended domain |
| Proprietary Formula | A unique pharmaceutical, molecular structure, formula, complex system | Uniqueness |
| Embedded Infrastructure | An optical fiber network, social network | Connectivity |
| Modular Systems | A roofing system, a closet connection system, integrated automation equipment | Adaptability in use, multiple uses |
| Algorithms, Artificial Intelligence, and Machine Learning | Bank loan screening models, search engines, voice recognition | Rules, judgment, analysis, decision acceleration, understanding |
| Connected Integration (IoT) | Intelligent and integrated HVAC controls | The data structure, stack, queues |
| Blockchain | An NFT that assigns certification to a tangible or intangible product or object | Scale and meta transfer |
| Hybrid and Combination | An automotive assembly (with engine and frames as separate platform-levers) | Multiple |
Table 1 — The platform-lever types that create the foundation for the various PLaaS archetypes.
The table tells a story of evolution. Through the industrial revolution, the production asset was the primary lever — scale production, lower unit costs, win on price and margin. Henry Ford coupled a design lever to production levers, and once companies saw that the platform and the product were not the same thing, one lever could carry many products with unique modules on top. The late twentieth century matrixed levers together — powertrain levers coupled to chassis levers. Then software and the internet let external forces — third-party buyers and sellers, users and contributors — drive enormous power into the line, forcing businesses to rethink their business models around it.
Expect the list to keep evolving as companies apply creative and strategic thinking — and remember that the theory of a new platform is of little value until a company employs it and it works.
Codification
How you describe an archetype reflects your vantage point. Every function sees the product line differently, and customers see it differently than competitors do. Codifying the archetype is like designating the DNA of a product line: it looks complicated until you learn the code — and like DNA, each archetype can mutate into unexpected variants.
The codification runs at two levels: the core orientation states what the line offers, who it serves, and which platform-levers anchor it; the advancement orientation states where the initiative stands and how ready the markets, the technology, and the competencies are.
Table 2 — Orientation and platform-levers (up to three during the initial product line build stage).
| Element | Codes |
|---|---|
| Offering type | OT1 Tangible · OT2 Service · OT3 Combination · OT4 Unknown |
| Customer set | B2 B2B · CG Consumer · M Combination · U Unknown/Unsure |
| Platform-levers (up to 3) | PA Production Asset · TD Tangible Design · SV Service System · SS Software Systems · PF Proprietary Formula · EI Embedded Infrastructure · MS Modular Systems · AI Algorithms/AI/ML · CI Connected Integration (IoT) · BL Blockchain · HY Hybrid and Combination |
Table 3 — Market segments and technology building block readiness.
| Element | Codes |
|---|---|
| Initiative status | Conceptual/Forming · Testing Validation · Existing–Incremental Advancement · Existing–Next Generation · Existing–Pivoting · Unknown/Unsure/Unclear |
| Market segments — noun | N4 Well understood · N3 Somewhat understood · N2 Somewhat unknown · N1 Unknown |
| Market segments — verb | V4 Well understood · V3 Somewhat understood · V2 Unknown · V1 Unknown |
| Technology readiness | TR4 Fully Ready · TR3 Nearly Ready · TR2 More Needed · TR1 Much More Needed |
| Competency (skill) | SC4 Fully Capable · SC3 Some Improvement Needed · SC2 More Needed · SC1 Much more is needed |
Before You Move
Transformations, pivots, and recasts all begin from the same place: the archetype you already have.
The beginning state matters a great deal. Consider an existing refrigerator line anchored on a core design lever. Bolting a new platform-lever type onto it is fraught, because the company didn’t design the original system with the new lever in mind — the integration turns kludgy, and data-generating sensors become an afterthought. It might work as a proof of concept; it’s unlikely to be a great product.
That is why the codes force the question early. “Existing–Pivoting” is an initiative status, not a slogan — and the noun, verb, technology, and competency codes tell you whether the move you’re contemplating is supported or wishful. A transformation that fights the archetype fails slowly and expensively. A move that fits it — or that honestly recasts the archetype first — compounds.
The Shift
Strategic question for the boardroom: Which platform-levers anchor our product line’s archetype today — and does the move we’re funding fit that archetype, or fight it?
Takeaways
Name the anchor
Identify the platform-lever, or its deliberate absence, that your product line archetype is built on. Everything else is build-out.
Guard the count
Three or fewer levers on a new line, fewer than seven on a large existing one. Intense focus is what makes a lever a lever.
Code before you commit
Run the orientation and readiness codes before any transformation, pivot, or recast. They tell you whether the move fits the archetype or fights it.
Go Deeper
Book 2 of the trilogy — leading product line change when the archetype, the markets, and the technology are all in motion.