Place Operating Model Design
Is the organisation built to perform at every level?
“The best playbooks we have ever seen from any developer client.”
An independent assessment by the ERP platform selected by one of our clients. A claim about our methodology.
Most operating model work produces governance documents that describe how an organisation should work.
Correct on paper. Ignored in practice.
The gap is rarely talent. It is structure: overlapping responsibilities, fragmented information, and decisions that take too long to travel from the top to the teams that need to act on them. The same structural problem surfaces in operations: an operations director approaching handover without a defined accountability framework, without community governance documents, and without performance standards against which to hold FM and CM contracts cannot run a place to the standard it was designed to deliver.
Place Operating Model Design produces something different: tools that change how an organisation actually works, and the information architecture that gives every level, from working team to board, the visibility it needs to perform. It covers both the development model (how the organisation plans, delivers, and hands over) and the operator model (how it runs the place and governs the community post-handover).
The work
Every POMD engagement is calibrated to where the organisation actually is, whether it is building a development operating model from scratch, consolidating a fragmented portfolio, or standing up the operator model that will run the community post-handover. The outputs are tools, not documents: governance frameworks, playbooks, and information architectures designed for the way the organisation works, built for digital execution from the outset.
The framework applies across four stages of organisational development.
Each stage requires a fundamentally different calibration. The diagnostic determines which stage applies before any design begins.
Two contrasting engagements
A contractor establishing a development arm across three geographies simultaneously. Zero existing governance infrastructure.
Complete operating model, DOA, and digitally-optimised playbook suite built from scratch and operational from day one. With the foundation layer in place, the next phase builds the reporting and visibility architecture that connects performance from working team to board.
An established master developer with a fragmented portfolio.
18 operating model recommendations across six challenge areas, delivered alongside a full single source of truth architecture and embedding programme. The result: one governance framework, one source of truth, and a stage gate structure that makes decisions visible before they become problems.
If your operating model is not keeping pace with your portfolio, or you’re building one from scratch, we should talk
Let's talkQuestions developers ask about place operating model design
The difference is where the knowledge comes from. Cornerstone’s frameworks were built from inside developer organisations: on the developer side, the operator side, and the advisory side. We know what a governance framework looks like when it lands in an organisation under pressure, and what gets used versus what gets filed. That shapes two things. The outputs are tools designed for digital execution, not documents produced for sign-off. And the methodology is calibrated to the specific organisation and its stage.
Yes. POMD is applied as a standalone frequently, particularly for developers who have a clear strategic intent but need the governance, processes, and operational infrastructure to execute it. Where PED or PID outputs exist, POMD builds on them. Where they do not, the diagnostic step establishes what the operating model needs to deliver before design begins.
It means every process step is designed with its execution environment in mind: which steps are candidates for automation, which require human judgement, and how the two connect. Each playbook is mapped against the tools the organisation actually uses, so the process and the system are designed together rather than retrofitted. The result is a playbook that teams use as a live working document.
The diagnostic assesses where the existing model is working, where it is not, and why. The framework calibrates to what exists; it does not require starting over. The most common pattern is consolidation: an established developer with capable teams but fragmented governance, where the work is identifying the specific gaps, redesigning those elements, and embedding the changes without disrupting what is already functioning.
Yes. POMD covers two distinct operating models across the development lifecycle. The development model addresses how the organisation plans, delivers, and hands over. The operator model addresses how the organisation runs the place post-handover: governing the community, managing service providers, holding FM and CM performance to account, and sustaining the experience the development was sold on. These are typically separate engagements commissioned at different moments. The framework, diagnostic logic, and methodology apply to both.
The foundational steps produce a functioning operating model. A mature engagement goes further: the Operational Intelligence layer connects everything built in the foundation steps into real-time visibility across the organisation. At working level, dashboards surface exceptions and route approvals without manual chase. At management level, programme and portfolio status is visible without reconstruction. At board level, capital deployment, delivery progress, community performance, and risk exposure are available in real time, not assembled from disconnected month-end reports.
