← ALL WORK

A project operating system for a city-backed Black housing initiative.

Client
A housing and community development consultancy
Partners
Public funder and community-facing partners
Year
2026
Status
Active

THE DECISION

How should the funded mandate be organized so that the project team could manage delivery, maintain partner alignment, and meet funder obligations without relying on undocumented knowledge?

THE MANDATE

The funder-backed initiative had a clear mandate: move from research and engagement into a structured body of work on Black housing, neighbourhood conditions, and public-system response.

The missing layer was operational.

The initiative required timelines; workstreams; partner roles; decision points; documentation; reporting; risk management; and coordination across organizations.

THE COMPLEXITY

The initiative combined public funding requirements; community-facing engagement; research; data; analysis; knowledge products; partner coordination; and reporting.

These activities moved at different speeds and depended on different people, evidence, and approvals.

THE BUILD

Project delivery plan
A structure separating funder obligations; partner activities; research milestones; engagement requirements; knowledge products; and reporting deadlines.
Five-workstream structure
Engagement; data; analysis; partner coordination; knowledge products.
Meeting and decision cadence
A rhythm for weekly project management; partner alignment; review; decision escalation; and funder reporting.
Documentation system
A structured approach to agendas; decisions; action items; risks; dependencies; source files; and version control.
Reporting structure
A system connecting daily delivery to funder-facing progress reporting.

THE OPERATING VALUE

The project team can manage the initiative without carrying the whole structure in individual people’s heads.

The funder and delivery partners can see:

  • what is moving
  • what is delayed
  • what depends on another workstream
  • and what requires a decision

How the work moved

  1. The mandate was structured as a multi-partner delivery system spanning engagement, research, data, analysis, knowledge products, coordination, and funder accountability.

    Mandate framing · multi-partner delivery design · accountability definition

  2. Funding obligations, partner commitments, research milestones, engagement requirements, and reporting deadlines were converted into concrete delivery requirements.

    Contract-to-delivery translation · requirement mapping · obligation management

  3. Five workstreams and a documentation architecture were established to manage decisions, risks, actions, dependencies, source files, and version control.

    Project architecture · information governance · workstream design

  4. The workstreams were tested against timing constraints, partner capacity, evidence dependencies, approval requirements, and funder deadlines.

    Dependency modelling · schedule-risk analysis · delivery scenario testing

  5. The project operating system is coordinating weekly delivery, partner alignment, decision escalation, documentation, risks, and reporting.

    Delivery management · portfolio visibility · decision escalation

  6. The delivery team will retain a documented system connecting workstreams, funder obligations, partner roles, risks, reporting, and source documentation.

    Delivery-system transfer · knowledge continuity · funder accountability

The funded mandate was already there. The build made it governable.