INTEGRATORS

Design measures whether solutions are architected from the client's operating model or assembled from the product catalogue: solution design quality, user journey mapping, needs analysis depth, and whether discovery interrogates how the client actually works before deciding what to build. The evidence is in the artefacts. A design that opens with room types and hardware schedules was designed backwards; a design that opens with the workflows the environment must serve, the collaboration patterns it must support, and the outcomes it will be measured on is delivery-grade before a single device is specified. Design is where the integrator either enters the client's operating model conversation or stays permanently outside it, because whoever frames the problem owns the relationship, and the framing happens here.

Deploy measures whether delivery quality is a property of the system or of individuals: engineering depth, configuration capability, platform integration, and installation reliability, scored for repeatability. Most integrators score highest on Deploy, and that is precisely the problem: being good at it is assumed, so it rarely differentiates, and being good at it heroically, through the best engineer on a good day, does not scale, transfer, or survive that engineer's resignation. The diagnostic distinguishes repeatable Deploy from heroic Deploy: whether quality holds when the A-team is on another project, whether configuration knowledge lives in documentation or in heads, and whether the tenth deployment is as clean as the first. Heroic Deploy wins projects. Systematic Deploy wins the account.

Deliver measures whether the relationship survives handover: support quality, monitoring, responsiveness, service level discipline, and lifecycle maturity beyond the snag list. The dimension exists because integration economics are shifting from projects to relationships, and most delivery organisations are still built for the project: intensity through commissioning, then a helpdesk. The diagnostic scores what happens in month seven, whether monitoring is proactive or complaint-driven, whether service levels are managed or merely contracted, and whether the integrator knows the environment is degrading before the client does. Deliver is where recurring revenue is earned or forfeited, because clients renew the partner who runs the environment, not the one who once installed it.

Differentiate measures whether the market can tell the integrator apart without reading the reference list: consulting capability, advisory depth, innovation, and positioning that survives comparison. The evidence test is unforgiving: remove the logo from the website and the capability statement, and if the copy could belong to any competitor, the dimension has scored itself. Differentiation in the Intelligent Workplace™ era is not a claim about quality, everyone claims quality, it is a position in the client's operating model conversation: assessment capability the competitor does not have, advisory the client will pay for separately, and a delivery methodology with a name and a track record. Undifferentiated integrators compete on price by default, whatever their proposals say. The dimension measures the distance between what the integrator is and what only the integrator is.

The value shows up in which deals an integrator wins, not just which ones it completes cleanly. A strong Deploy score wins the project. A strong Differentiate score is what gets the integrator into the conversation before the RFP is written, where margin actually lives. Integrators who run the 4D diagnostic before a growth push find out whether their constraint is capability, delivery consistency, or positioning, which are three different problems with three different fixes, and building the wrong one first is how a capable delivery organisation stays undifferentiated for another year.

The 4D Assessment fits a specific integrator, not every integrator. It fits delivery organisations pursuing Intelligent Workplace™ certification who need an evidence baseline to build from. It fits integrators whose Deploy capability is strong but whose win rate on strategic accounts isn't moving, who need to know whether Design or Differentiate is the actual constraint. It fits leadership teams inheriting a delivery organisation who need to separate what's systematic from what's carried by a handful of senior engineers. It is not built for integrators still deciding whether to pursue Intelligent Workplace™ delivery capability at all; that decision precedes the diagnostic.