Transparent, Resident-Obsessed Government
TOT-P1-C02-004Supporting programExecutive ActionFirst 100 Days

Central Performance & Delivery Unit

TOT-P1-C02-004

One delivery unit that keeps every promise on track.

Delivery conditions

Milestones are subject to the dependencies in the canonical timeline.

Executive/administrative authority; budget and classification may require Council.

The problem

Campaign promises have no delivery mechanism. Once elected, there's no dedicated team whose only job is making sure the big commitments actually happen — so they compete with daily operations and quietly fade.

The plan

One central Performance & Delivery Unit, under the Chief of Staff, owns delivery of the mayor's priority portfolio. It designs staffing and portfolio criteria during the transition, appoints its core in the first two months, and charters time-bounded delivery teams for each priority.

Never department-by-department PDUs, never a standing task force — one unit, with a charter, a budget, and an exit plan.

How you’ll know it’s working

  • Central PDU core appointed within 60 days
  • Portfolio criteria and charter template published
  • Delivery teams chartered with baselines and exit criteria

From the Blueprint

  • Phase 1 (days 0–60): reorganize Strategic Initiatives staff into the PDU, appoint portfolio Directors, name Project Leads, publish first-wave KPIs.
  • PDU Directors act as portfolio managers, each accountable for a domain and a set of measurable targets.
  • Every major department appoints an Outcomes Manager (internal KPI tracking, quarterly OCI reporting) within 60 days.
  • Every major department appoints a resident-facing Ombudsperson for complaints and escalations within 60 days.
  • Both roles report to the department head and indirectly to the Chief of Staff through the PDU.
  • Ombudsperson resolution rates, response times, and unresolved case logs publish quarterly on CitySync.
The Executive Office governs and unblocks; the PDU and CDTs deliver.
Sources and research conditions

S01 pp. 11-13, 57-67

SOURCE-SUPPORTED; POLICY DECISION APPROVED

Milestones are subject to the dependencies in the canonical timeline.

Proposal FAQ

Questions, answered from the record.

What problem does Central Performance & Delivery Unit address?

Campaign promises have no delivery mechanism. Once elected, there's no dedicated team whose only job is making sure the big commitments actually happen — so they compete with daily operations and quietly fade.

What would Central Performance & Delivery Unit do?

One central Performance & Delivery Unit, under the Chief of Staff, owns delivery of the mayor's priority portfolio. It designs staffing and portfolio criteria during the transition, appoints its core in the first two months, and charters time-bounded delivery teams for each priority. Never department-by-department PDUs, never a standing task force — one unit, with a charter, a budget, and an exit plan.

Who would own Central Performance & Delivery Unit, and what authority would it use?

Chief of Staff. Executive Action: Executive/administrative authority; budget and classification may require Council.

How would Tampa know whether Central Performance & Delivery Unit is working?

Central PDU core appointed within 60 days; Portfolio criteria and charter template published; Delivery teams chartered with baselines and exit criteria

When would Central Performance & Delivery Unit move?

Transition Period: Design central PDU staffing, portfolio criteria and initial CDT charter template. Days 31–60: Appoint central PDU core and charter initial CDT leads.

Make this real

Fund the fight for Central Performance & Delivery Unit.

Help turn a published plan into organizing, outreach, and governing capacity.

Contribute on ActBlue →