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

Cross-Department Delivery Teams

TOT-P1-C02-005

Small cross-department teams with a deadline and an exit.

Delivery conditions

Milestones are subject to the dependencies in the canonical timeline.

Executive/administrative authority; organizational, staffing and records review apply.

The problem

The hardest city problems live between departments — and permanent committees are where urgency goes to die. Problems that need three departments get three excuses.

The plan

Cross-Department Delivery Teams (CDTs) are time-bounded strike teams: a charter, a named owner, a baseline, a budget, and exit criteria. The first three to five launch between Days 61 and 100, only after a readiness test.

When a CDT's job is done, it exits — its work handed back to departments, its lessons published. No permanent bureaucracy.

How you’ll know it’s working

  • First 3–5 CDTs launched with full charters
  • Each CDT has baseline, budget and exit criteria
  • Completed CDTs publish handoff reports

From the Blueprint

  • Phase 2 (days 60–180): launch 3–5 initial teams on zoning reform, homelessness coordination, and procurement modernization.
  • Teams run on a 60–120 day mission cadence with clear deliverables, exit criteria, and biweekly CitySync briefings.
  • Phase 3 standardizes a team charter template and deployment playbook; pilots transition into long-term programs.
  • A standing Cross-Departmental Task Force meets monthly, chaired by the Chief of Staff, with department heads as members.
  • Task Force meeting notes and action items publish publicly through CitySync within 10 business days.
In the Henderson Administration, ‘that’s another department’s problem’ is not an acceptable answer.
Sources and research conditions

S01 pp. 11-13, 63-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 Cross-Department Delivery Teams address?

The hardest city problems live between departments — and permanent committees are where urgency goes to die. Problems that need three departments get three excuses.

What would Cross-Department Delivery Teams do?

Cross-Department Delivery Teams (CDTs) are time-bounded strike teams: a charter, a named owner, a baseline, a budget, and exit criteria. The first three to five launch between Days 61 and 100, only after a readiness test. When a CDT's job is done, it exits — its work handed back to departments, its lessons published. No permanent bureaucracy.

Who would own Cross-Department Delivery Teams, and what authority would it use?

Chief of Staff / PDU. Executive Action: Executive/administrative authority; organizational, staffing and records review apply.

How would Tampa know whether Cross-Department Delivery Teams is working?

First 3–5 CDTs launched with full charters; Each CDT has baseline, budget and exit criteria; Completed CDTs publish handoff reports

When would Cross-Department Delivery Teams move?

Days 61–100: Launch first 3–5 CDTs only with charter, owner, baseline, budget, dependencies and exit criteria.

Make this real

Fund the fight for Cross-Department Delivery Teams.

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

Contribute on ActBlue →