Contemplating the floating of things
In 1620, Francis Bacon published Novum Organum Scientiarum — a new instrument of science. His argument was that humanity had been doing knowledge wrong. The Aristotelian method started with principles and deduced conclusions. Bacon proposed the reverse: start with observation, identify patterns, and only then derive the governing laws. Inductive reasoning. Study what actually happens before theorising about what should.
Thomas Troward captured the implication in a line that has stayed with me for years: "The law of floatation was not discovered by contemplating the sinking of things, but by contemplating the floating of things which floated naturally, and then intelligently asking why they did so."
Until the mid-nineteenth century, boats were made of wood — because wood floats. That was observation without understanding. Once naval architects studied why things float — buoyancy, displacement, density ratios, hydrostatic pressure — they could build ships from iron and steel. Materials that sink on their own, engineered into structures that float by design. The understanding of the law made it possible to work with materials the law would otherwise prohibit.
Bacon's own formulation is sharper still: "We must obey the forces we wish to command."
That sentence is the entire thesis of the Critical Path Layers framework, compressed into nine words.
The Forces Most Founders Ignore
Startups operate within forces — market dynamics, buyer psychology, competitive pressure, organisational constraints, capital structures. These forces are not obstacles. They're physics. They govern what works, what scales, and what collapses under its own weight. The founders who build lasting companies are not the ones who fight these forces or ignore them. They're the ones who study them with enough precision to work with them.
The problem is that most startup advice treats these forces as a flat landscape. "Find product-market fit." "Build a sales engine." "Scale your team." Each piece of advice is correct in isolation and useless without sequencing — because the forces have a dependency structure. Some must be resolved before others become meaningful. Working on the wrong force at the wrong time doesn't just waste effort. It produces misleading signals that compound into strategic errors.
A founder who builds a sales team before validating who they're selling to will conclude that "sales is hard" or "the team isn't good enough." The actual problem is upstream: the ICP isn't defined, the value proposition hasn't been tested against real buyer alternatives, and the pricing model doesn't match how the buyer budgets. The sales team is executing against a hypothesis that nobody validated. The force that governs whether pipeline converts — Layer 1 Market Clarity — hasn't been obeyed. And no amount of downstream effort will overcome that.
This is what the Critical Path Layers framework calls downstream gravity: the pull toward later-stage work before earlier-stage dependencies are resolved. Founders gravitate toward activity that feels productive — pipeline, marketing, hiring, fundraising — because that's where the energy is. The upstream work — problem definition, ICP validation, competitive positioning, pricing — feels slower, less tangible, harder to show on a slide. But it's the buoyancy calculation. Skip it, and the ship sinks regardless of how impressive it looks above the waterline.
The Dependency Structure
The CPL framework organises the forces into five sequential layers, each with gate criteria that must be genuinely met before the next layer's work becomes productive.
Layer 0 — Foundations. Is the problem worth solving, and can you articulate it in the buyer's language rather than your own? Does the product demonstrate basic problem-solution fit? Is the strategic thesis explicit and testable — or does it live as an intuition in the founder's head? This is Bacon's starting point: observe the phenomenon. Understand what actually happens before building a theory about what you'll sell.
Layer 1 — Market Clarity. Who is the buyer — specifically, by name, by role, by budget authority? Why would they choose this solution over every alternative, including doing nothing? What will they pay, and does that price make the economics work? These three questions — ICP, competitive positioning, pricing — form a triangle that resolves together. Movement on any one forces reassessment of the other two. This is the buoyancy calculation: the relationship between displacement and density that determines whether the structure floats.
Layer 2 — Validation. Can this be proved in a real context? In enterprise and corporate settings, this means a pilot with pre-defined success criteria, a technical integration that works within the partner's infrastructure, and a stakeholder map that accounts for who decides, who influences, and who can kill the deal. The pilot is the experiment — Bacon's "artificial experimentation to provide additional observance of a phenomenon." It generates evidence, not just results.
Layer 3 — Commercial Engine. Can demand be generated repeatably? Can the sales process be taught to someone who wasn't in the room when it was invented? Is the marketing connected to pipeline with measurable attribution? This layer is where most founders want to start — and the entire point of the framework is that starting here, before Layers 0–2 are resolved, produces activity that looks like progress but isn't. Pipeline built on an unvalidated ICP is a list of people who won't buy. Content marketing amplifying an unclear value proposition is noise at scale.
Layer 4 — Scale Readiness. Can the organisation, operations, and finances support what Layers 0–3 have unlocked? Are processes documented, are roles designed for the next stage of growth, are unit economics proven at the current scale and plausible at the next? Scaling prematurely — before the upstream layers are resolved — is how startups burn cash on infrastructure for a business that hasn't been validated.
The layers are sequential. The gates are real. And the diagnostic question at every stage is the same: are the upstream prerequisites actually resolved, or is this founder working on a downstream symptom?
The Multi-Stage Rocket
Robert Goddard — the physicist who made space travel mechanically possible — understood dependency structures intuitively. His two breakthrough inventions in 1914, the multi-stage rocket and a viable rocket fuel design, solved the problem of escaping Earth's gravity not through brute force but through sequencing. Each stage fires in order. Each depends on the one before it. No stage can be skipped, and the sequence is non-negotiable. A second stage that ignites before the first stage has completed its burn doesn't accelerate the rocket — it destroys it.
The parallel to startup scaling is exact. Each CPL layer is a stage. Each must complete — gate criteria met with evidence, not assumption — before the next stage's work becomes productive. A founder who "ignites" Layer 3 (commercial engine) before Layer 1 (market clarity) has completed its burn isn't accelerating growth. They're burning fuel in the wrong direction and interpreting the motion as progress.
Corporate innovation operates under the same physics, with additional forces. The corporate CPL adds Layer -1 (Problem Classification — is this an optimisation, an adjacency, or a transformation?) and replaces the startup's external market with an internal one. The "buyer" is an internal stakeholder. The "pilot" must navigate organisational politics. The "scaling mechanism" is an adoption playbook, not a sales process. But the dependency logic is identical: each layer must be resolved before the next becomes meaningful, and the most common failure mode is working on the wrong layer.
What Bacon Understood
Bacon's insight was not that observation is better than theory. It was that theory built on insufficient observation is worse than no theory at all — because it creates false confidence. The founder who has a strategy deck, a sales team, and a marketing budget feels like they're building a company. The corporate innovation leader who has a pilot, a budget, and executive sponsorship feels like they're driving transformation. Both may be building on sand — constructing elaborate downstream structures on top of upstream assumptions that have never been tested.
The "Uber for X" pattern that proliferated across a decade of startup culture is the perfect illustration. Copying a surface pattern — marketplace dynamics, network effects, platform economics — without understanding the underlying forces that made those dynamics work in a specific context. It's building boats from wood because wood floats, without understanding why wood floats, and therefore without the ability to build from steel when the context demands it.
The Critical Path Layers framework is an attempt to move from wood to steel. To replace intuition-based sequencing ("it feels like we should be selling now") with evidence-based sequencing ("the gate criteria for Layer 1 are met; Layer 2 work is now productive"). To give founders, corporate innovators, and the investors who back them a diagnostic that identifies which force is actually binding — not which activity feels most urgent.
Bacon wrote that we must obey the forces we wish to command. The forces governing startup growth and corporate innovation are not mysterious. They're structural, sequential, and diagnosable. The work is studying them with enough honesty to build on what's real rather than what's convenient.
The law of floatation is knowable. The question is whether you'll study it before you build the ship — or discover it after.
