Operational Intelligence
Can your organisation see what it needs to see, at every level?
Most developer organisations are not designed to see themselves clearly.
At concept and establishing stage, governance structure is assumed rather than built: decisions travel informally and no one has designed what the organisation needs to see. At delivery stage, performance data lives in disconnected systems; cost position, stage gate status, and decision pipeline are reconstructed at month end rather than visible in real time. Post-handover, the gap between what was promised and what the community experiences is felt by residents long before it surfaces in any report.
The problem is the same at every stage: nobody designed what the organisation needed to see.
Operational Intelligence is the visibility layer built into the operating model from the outset. It is designed to show what the organisation needs to see, at every level, whether the development is at concept stage, mid-delivery, or running a live community.
The work
Many developer organisations have no designed visibility architecture at all. Those that do often measure activity rather than performance: tasks completed, documents uploaded, meetings held. Neither tells the organisation whether it is making the right decisions, delivering against its commitments, or keeping the promises it has made to residents and stakeholders.
The design work that makes this possible, defining what the organisation needs to see, at which level, at which stage, is where Cornerstone works. The output is a visibility architecture that is designed from the inside out: built around the operating model, not around available data or off-the-shelf reporting tools.
Three levels of visibility
Working level, teams and functions
The decisions, approvals, and exceptions relevant to each function are visible without manual reconstruction at the design, delivery, handover, and post-handover stages.
Management level, programme and portfolio
Portfolio status, cost exposure, and decision pipeline visible without reconstruction. Performance across projects visible in a single view, not assembled from disconnected month-end reports.
Executive and board-level view
Capital deployment, delivery progress, community performance, and risk exposure available in real time. The board sees what the organisation is doing, not what it was doing three weeks ago.
Questions developers ask about operational intelligence
At every stage. At concept and establishing stage, the visibility architecture is designed into the operating model from the outset. At delivery stage, it surfaces cost exposure, stage gate status, and decision pipeline in real time rather than reconstructed monthly. Post-handover, it covers FM service delivery, community management performance, and resident experience indicators. The framework is the same at every stage; what it measures is calibrated to the organisation’s current position.
No. Most BI and reporting tools start from available data and work outward, surfacing what the system already captures. Operational Intelligence starts from the organisation’s need and works inward: what does each level of the organisation need to see, and what data architecture makes that possible? The design work comes first. The tooling follows from it. That sequence is what most BI implementations skip, which is why most developer reporting is reconstructed rather than real-time, and activity-based rather than performance-based.
Very little. A governance foundation helps: where a POMD engagement has been completed, Operational Intelligence connects directly to the framework, and the dashboards measure what the operating model is designed to deliver. But the absence of existing governance is not a barrier. The diagnostic establishes what the organisation needs to see before any visibility architecture is designed.
The outputs are a measurement framework design, a dashboard suite specification (working-level process dashboards, management-level portfolio views, executive and board-level performance summaries), a data architecture (the data flows, integration specifications, and system usage rules that make the dashboards meaningful), and a reporting RACI. These are Cornerstone’s deliverables: the design and specification that turn a visibility requirement into a working system.
This framework connects to
