Most commercial flooring jobs are playbook work. The brief comes in, you match it to a product and install method that fits the category, and the job runs to plan. The value of a good contractor on that kind of work is mostly in the execution, because the thinking has already been done by someone else, often a long time ago.

The jobs that actually test a business are the ones where the playbook doesn’t fit. A site constraint rules out the obvious product. A compliance requirement cuts across the usual install method. A customer has three non-negotiable outcomes that seem, on first read, to be in direct conflict with each other.

The instinct in that situation is to reach for the nearest close-enough playbook and hope the edges don’t fray. That’s where most contractors quietly fail. It’s also where the most interesting work happens if you’re willing to think differently about how to solve it.

The approach we’ve found works, and it’s the thing worth writing about at a business leadership level, is to strip the problem back to what’s actually known to be true and reason forward from there.

Facts versus assumptions

The distinction matters more than it sounds. A fact, in the sense I’m using the word, is a constraint you can verify. The existing floor is 17mm tall. The landlord has written that access panels must not be damaged during the works. The tenant’s operating hours are 7am to 7pm.

The building has an access floor system with a specific load rating. Each of these can be measured, documented, or confirmed with a phone call. They aren’t going anywhere.

An assumption is a belief you’ve inherited and never actually tested.

“Everyone uses hot water extraction for a restoration clean.” “Access panel floors always get replaced with the same modular product that came out.” “A full replacement is always more expensive than a patch.”

These can all turn out to be true in specific situations, but they carry no authority on their own. The trap is that assumptions look like facts if you don’t inspect them closely, and most contractors build their scopes on a mix of the two without noticing.

First-principles reasoning, which is what this is, just means refusing to treat assumptions as facts. You write down what’s actually true about the job, you write down what’s actually required as an outcome, and you build a scope from the intersection. Anything that makes it into the scope needs to map back to a fact or a verified requirement. Nothing gets specified because “that’s how we always do it.”

A recent example that made the point well

We ran a flooring replacement project recently on a commercial site with a loose-laid tile system installed over an access floor. The tenant wanted the tile replaced. The tile was at end of life and no longer performing. Everything about the surface change was straightforward. What made the job interesting was everything underneath.

The known facts, as we documented them: The existing floor finish, including the loose-laid tile, sat at exactly 17mm above the access floor deck. Any replacement had to match that 17mm height, because the floor transitioned into adjacent finishes (stone, carpet, timber) at thresholds that couldn’t be moved.

Miss the height by even a few millimetres and you’d have lips and trip hazards at every doorway.

The landlord’s written requirement was that access panels below the floor must not be seriously damaged during works. The access floor system was the building’s service distribution path, and preserving the ability to service and eventually reinstate those panels was a condition of the works. A full bonded installation that glued the new finish directly to the access panels was out of the question, because at defit when the tenant eventually vacates the make-good would destroy the panels underneath.

The works had to happen out of hours. Business continuity during the day was a tenant requirement. The operational spaces needed to be ready for 7am every morning, including functional flooring, safe transitions, and no setup remnants from the overnight crew.

Everything had to comply with Australian standards. No shortcut products, no improvised adhesive systems, no installation technique that would fail a compliance check twelve months later.

Those four facts, taken together, rule out most of the standard replacement approaches before you even start shopping for a product.

A direct-stick vinyl tile of the same gauge as the original is the obvious move, except it doesn’t match 17mm and bonding it to the access panels would destroy them at defit. A full floated floor fails on stability under commercial traffic. A thicker single-product solution fails either on height or on install time. ‍

So we reasoned from the facts

The math is almost embarrassingly simple once you’ve named the constraints honestly. 12mm of structural plywood mechanically fixed with screws to the access panels below. 4.5mm luxury vinyl plank bonded to the ply above. Total finish height brought to 17mm within the tolerance needed for smooth threshold transitions.

Every layer installed to Australian standards. Vinyl plank installed overnight in sequenced zones so the tenant was trading the next morning. The key design call, the one that makes the whole thing work for the landlord, is that the plywood is screwed but not glued.

At defit and make-good when the tenant eventually vacates, the plywood boards can be unscrewed and lifted. The access panels beneath will have screw holes and will have been hard-worked by the fixings, but they’ll be fundamentally intact. The building keeps its service distribution system. The panels are reinstatable. Glue would have turned this into a destructive install; screws alone make it a reversible one.

This is not a clever trick. It’s what happens when you write the facts down, stop pretending the standard playbook covers the case, and let arithmetic do the work.

Why most businesses won’t do this

Reasoning from facts is slower than reaching for the playbook. It requires someone senior enough to write the facts down, interpret the customer’s real constraints, and take the commercial risk of specifying something outside the standard menu.

It requires a team that can actually install the result without dropping the detail. And it requires a business culture that rewards solving the problem correctly rather than closing the quote quickly.

Most contractors in this industry don’t operate that way, and I don’t think it’s because the people are lazy. It’s a structural thing. A large operator with many layers of middle management processes jobs through a template system.

The template handles the 80% of work that fits the playbook. The 20% that doesn’t fit gets either forced into the template (and fails) or priced so high that the customer walks. Neither outcome rewards the kind of slow, first-principles thinking that the access floor job needed.

The irony is that first-principles work isn’t actually more expensive to deliver once you’ve built the habit. It’s more expensive to start doing, because the first few jobs take longer while the team gets used to thinking this way. After that, it’s just how the business operates, and the margin on those jobs is usually better than the playbook work because the customer has fewer alternatives and understands why.

The business leadership implication

The practical takeaway for any leader reading this is to notice how often decisions in your business get made on assumptions rather than facts, and to ask whether that’s actually serving the organisation. This applies to more than flooring.

“We always source from this supplier” is an assumption. Is it still true that they’re the best choice, or is it just the path of least resistance?

“This client wants it fast, not right” is an assumption. Have you actually asked them, or are you scoping to a story you’ve told yourself about what they want?

“The standard approach will be fine here” is an assumption.

What would you specify if you started from the actual constraints rather than the template?A lot of business decisions are just inherited defaults with a veneer of analysis over the top. Separating the facts from the inheritance, and reasoning from the facts, tends to produce better outcomes, fewer regrets, and more interesting work for the team doing it.

The Premrest version of this

We’ve built the team, the scoping process, and the customer conversations around this way of thinking. When a brief comes in that doesn’t fit an obvious category, we don’t force it into one. We walk the site, write down what’s actually true, talk to the customer about what they actually need as an outcome rather than what product they think they need, and come back with a scope that maps to the facts.

Sometimes the resulting scope is the standard playbook product, because that’s what the facts support. Sometimes it’s 12mm of ply and 4.5mm of vinyl plank, or a bespoke cleaning chemistry for a heritage carpet, or a cleaning regime handed over to a general cleaner who was in place before we arrived. The scope fits the job rather than the other way around.

None of this is a business trade secret.

It’s just a habit of mind that most operators haven’t built, because the industry doesn’t really ask them to. The facilities managers and property leaders who’ve worked with us on the jobs where this approach mattered tend to bring us back for the next job that doesn’t fit the playbook, which is how the business has grown over the years.

‍

‍P.S. The starting question on almost every difficult job we’ve run isn’t “how do we usually do this?” It’s “what do we actually know to be true?” The order of those two questions changes everything that happens after.

‍