CityScore: Big Data Comes to Boston Custom Case Solution & Analysis

1. Evidence Brief

Financial Metrics

• Operating Budget: The City of Boston operates with an annual budget exceeding 2.8 billion dollars.
• IT Investment: The Department of Innovation and Technology (DoIT) manages a multi-million dollar portfolio, but specific CityScore development costs are absorbed within existing headcount and software licenses.
• Performance Targets: A score of 1.0 represents meeting the established target. Scores above 1.0 indicate performance exceeding expectations; scores below 1.0 indicate underperformance.

Operational Facts

• Metric Composition: CityScore aggregates 24 distinct metrics across categories including Public Safety, Economic Development, Education, and Public Works.
• Data Sources: Inputs include 311 service requests, police incident reports, emergency medical services response times, and library usage statistics.
• Frequency: Data is updated at varying intervals: daily, weekly, monthly, and quarterly, depending on the source system capabilities.
• User Interface: An executive dashboard provides the Mayor with a real-time view of the aggregate score and the ability to drill down into individual departmental performance.

Stakeholder Positions

• Marty Walsh, Mayor: Views the tool as a primary mechanism for accountability and a way to communicate city health to residents.
• Jascha Franklin-Hodge, Chief Information Officer: Focuses on data integrity and the technical challenge of integrating disparate legacy systems.
• Howard Lim, Program Manager: Responsible for the day-to-day refinement of the scoring algorithm and managing departmental feedback.
• Department Heads: Express concern regarding the fairness of metrics and the potential for the score to overlook nuances in operational reality.

Information Gaps

• The specific weighting formula for how each of the 24 metrics contributes to the final aggregate score is not detailed in the case.
• Long-term maintenance costs for data pipelines are not projected.
• The impact of external factors such as extreme weather or state-level policy changes on the score is not quantified.

2. Strategic Analysis

Core Strategic Question

• How can the City of Boston utilize a composite performance index to drive operational efficiency without incentivizing departmental gaming or oversimplifying complex urban challenges?

Structural Analysis

Applying the Value Chain lens to municipal services reveals that CityScore acts as a management overlay across primary activities like public safety and infrastructure maintenance. The structural problem is that municipal output is often qualitative, while CityScore is strictly quantitative. There is a high risk of the measurement-to-management gap where departments optimize for the metric rather than the underlying service quality.

Strategic Options

Preliminary Recommendation

Boston should adopt the Contextualized Management model. A single number cannot capture the complexity of a city. The score must serve as a conversation starter for the Mayor and department heads rather than a final verdict. This approach mitigates the risk of departments ignoring critical but unmeasured tasks.

3. Implementation Roadmap

Critical Path

• Month 1: Establish a data governance committee to audit the 24 metrics for accuracy and relevance.
• Month 2: Automate data feeds for the 10 most volatile metrics to ensure the dashboard reflects current reality.
• Month 3: Conduct the first round of Performance Stat meetings using CityScore as the primary agenda-setting tool.
• Month 4: Launch a public-facing version of the dashboard with clear explanations of what the numbers represent.

Key Constraints

• Data Latency: Manual data entry in certain departments creates a lag that makes the daily score misleading.
• Cultural Resistance: Veteran department heads may view the score as a threat to their autonomy or a tool for punishment.

Risk-Adjusted Implementation Strategy

To ensure success, the city must implement a grace period where scores are tracked but not used for formal evaluations. This allows for the calibration of targets. Implementation will focus on data reliability first, then management integration, and finally public disclosure. This sequence prevents the spread of inaccurate information that could damage the credibility of the administration.

4. Executive Review and BLUF

BLUF

CityScore is a powerful diagnostic tool that must not be mistaken for a definitive grade of municipal health. The administration should institutionalize it as a management framework that triggers deeper operational inquiries. Success depends on moving beyond the aggregate number to address the specific departmental failures the data reveals. The score is a means to an end, not the end itself. The Mayor must lead a culture shift where data is used for continuous improvement rather than static reporting.

Dangerous Assumption

The most consequential unchallenged premise is that all 24 metrics are equally indicative of the quality of life of a resident. By aggregating these into a single number, the city assumes that an improvement in library attendance can offset a decline in emergency response times, which is a false equivalence in municipal priority.

Unaddressed Risks

• Gaming the System: Department heads may prioritize tasks that move the score, such as closing easy 311 tickets, while neglecting complex, long-term infrastructure needs that are not captured in the 24 metrics.
• Political Weaponization: Inaccurate or poorly contextualized scores could be used by political opponents or the media to create narratives of failure that do not reflect operational reality.

Unconsidered Alternative

The team failed to consider a decentralized scoring model where each neighborhood has its own CityScore. Boston is a city of distinct neighborhoods with different needs. A city-wide average might mask severe service disparities between affluent and underserved areas. A localized score would provide more actionable insights for resource allocation.

Verdict

APPROVED FOR LEADERSHIP REVIEW