Conceptual Pillars

A confirmed concept is hundreds of pages of evidence, models and specifications; the organisation that must live it can hold perhaps eight ideas. Conceptual Pillars is the disciplined compression: the concept's governing principles, each carrying real decision content, each traceable to evidence, each usable as a test when the thousand small decisions of implementation arrive. Pillars are not slogans — a pillar that cannot reject a design option, a policy proposal or a procurement choice is decoration, and decoration is what value engineering eats first.

• At the opening of Deliver, immediately after concept confirmation, while the reasoning is fresh
• Before change communication drafting — the pillars are its source language
• As the standing test during design development, fit-out decisions and operational policy-making

• Strategist drafting from the concept record
• Leadership team validating that the pillars carry their accepted decisions and sacrifices
• Change lead and communications, for whom the pillars become the narrative spine
• Design team confirming the pillars are designable tests, not abstractions

• Confirmed workplace concept with criteria verification and accepted sacrifices
• Ranked key criteria from Workshop II
• Vision framework and resolved tension register
• Behavioural assumption register
• Sustainability and identity commitments

1. Extract the concept's governing logic into candidate pillars across the required families: workplace narrative, strategic principles, design principles, experience principles, behavioural principles, technology principles, operational principles, sustainability principles.
2. Write each pillar with three components: the principle (one declarative sentence), its evidence lineage (which findings and decisions it carries), and its decision content (what it accepts and what it rejects — with at least one concrete example of each).
3. Apply the rejection test to every candidate: name a plausible design option, policy or purchase this pillar would rule out. A pillar that rejects nothing governs nothing; cut it or sharpen it.
4. Encode the accepted sacrifices: at least one pillar must carry what the organisation chose against, so the sacrifice remains a decision rather than becoming an accusation.
5. Hold the count ruthlessly: six to nine pillars total. Beyond that, none will be remembered, and unremembered principles do not govern.
6. Validate with leadership (do these carry our decisions?), the community group (is this recognisably our workplace?) and the design team (can we be tested against these?).
7. Publish the pillars as the concept's public face — the version of the strategy the whole organisation will actually read.

• Poster language: 'collaborative, flexible, human-centred' — pillars that every workplace on earth could claim govern nothing
• Pillars that restate criteria without their trade-off content, quietly un-deciding the decided
• The missing sacrifice: pillar sets that promise everything signal that the hard decisions have been laundered out
• Family padding: forcing a pillar per required family when the concept's logic concentrates in five
• Drafting by committee smoothing every pillar into agreeable vagueness

• Pillar set (6–9) with principle, evidence lineage and decision content each
• Rejection-test record per pillar
• Validated public-facing concept narrative
• Pillar-to-criteria traceability map

The pillars structure the Workplace Strategy document's narrative and the change programme's communication. Design reviews and procurement decisions in implementation are tested against them alongside Architectural Guidance criteria. In Recalibrate, the pillars define what the workplace claimed to be — the reference against which the Workplace Behaviour Review and Post-Occupancy Evaluation judge whether it became it.

Compression is judgement: deciding which of a hundred decisions are the eight that govern, and finding language that is memorable without becoming marketing. The rejection test is mechanical; knowing which rejections the organisation must be able to cite in two years is strategic foresight.

• Writing values instead of principles — pillars must decide, not inspire
• Omitting evidence lineage, so the pillars float free of the diagnosis and drift with opinion
• Producing twelve pillars because every stakeholder wanted one
• Excluding the sacrifices, converting future friction into betrayal narrative
• Treating pillars as a communications deliverable rather than a governance instrument

A utilities company distilled its concept into seven pillars. One read: 'Focus is provided, not found' — carrying the measured focus deficit, the enclosure investment, and the rejection of open-plan densification as a future cost lever. Eighteen months into implementation, a cost review proposed converting focus rooms to additional desks; the pillar was cited in the rejection, with its evidence chain attached. The principle did in one sentence what the 200-page strategy would have done in a meeting nobody scheduled.