Archive · Operating case

One idea,built threetimes.

Accountability through shared data. First in a city hall, then across a 400,000-member service operation, and now on a pool deck. Each time the tools changed. The discipline did not.

Period
2007 to now
Arenas
Municipal government, member services, youth sport
Roles held
Chief of staff, Vice President of Operations, founder
Evidence
Dated primary documents, 2006 to 2026

The discipline is older than the software.

Most organizations fail the same way. Every department holds one piece of the picture, nobody holds all of it, and the people closest to the work carry the rest in their heads. The fix is never a dashboard on its own. It is an agreed set of measures, a standing meeting where people answer for them, and one system of record everyone can see.

2007

Bayonne, New Jersey

CitiStat brought into a city hall of roughly 60,000 residents.

  • Site visit to the departments running Baltimore's program
  • Recommendation carried to the mayor
  • Launched in three departments plus the municipal utilities authority
  • Metrics reported every two weeks

2010–2016

AAA North Jersey

Member relationship management across roughly 400,000 members in Passaic, Hudson, and Bergen counties.

  • Audit of every member touch point
  • Definition and vision adopted club-wide
  • System proposal carried to the board of directors
  • Results benchmarked against peer clubs nationally

Now

Ridgewood YMCA Breakers

The same problem on a pool deck, solved in software this time.

  • Registration and billing stay with the system of record
  • Practice planning, attendance, and communication become one layer
  • Coaches and families see the same information
  • Shipped to real users, then measured

Baltimore, first thing in the morning.

In late 2006, a New Jersey city needed a way to hold department directors accountable, and the mayor wanted a recommendation before the end of the year. Rather than buy a reporting tool, the team went to see a working program: CitiStat, the data-driven management system built in Baltimore under Mayor Martin O'Malley. The point of going was never the software. It was to watch directors answer for their own numbers in a room, in front of their peers.

The record

Each entry below is a dated document held in a private archive, except the launch announcement, which is public record.

  • Nov 29, 2006

    Dates requested from the Baltimore office that ran CitiStat, to go down and see it.

    A recommendation had been promised to the mayor before the end of the year.

    Internal email
  • Jan 8, 2007

    Internal sessions scheduled on Baltimore's departmental model, starting with General Services and Health Administration.

    Meeting invitation
  • Mar 1, 2007

    Baltimore. 8:30 to 10:00, General Services. 10:30 to 12:00, Human Services.

    Two department sessions observed back to back in a single morning.

    Itinerary email
  • Mar 22, 2007

    Presentation on CitiStat and a citizen request system circulated to the quality of life office and city hall staff.

    Presentation
  • Apr 4, 2007

    Peer research added to the file: Syracuse's version of the program and the savings it was credited with.

    Research memo
  • May 1, 2007

    Decision meeting set with the mayor on purchasing the citizen request system.

    Internal email
  • Jun 20, 2007

    The City of Bayonne announces CitiStat, effective July 1, in three municipal departments and the Bayonne Municipal Utilities Authority, with each unit reporting metrics every two weeks.

    Mayor Joseph V. Doria, Jr.: the taxpayers expect productivity and accountability from their municipal government.

    Public press release
  • Sep 4, 2008

    The published CitiStat model circulated again from a New Jersey Department of Community Affairs address, a year after launch and one job later.

    Internal email

Four months from one morning in Baltimore to a live program reporting every two weeks.

Then the same problem, at ten times the size.

AAA North Jersey served roughly 400,000 members through branches, a call center, a travel agency, roadside assistance, insurance, and financial services. Six business lines, one member, and no shared view of the relationship. The internal audit named the cause without softening it: decisions are made independently for each business line.

The record

Internal documents, dated, from the audit through the board proposal to the role written to make the work permanent.

  • Sep 2010

    Implementation plan mapped as before and after. A member joining in a branch travels through counselor, cashier, a second office, data processing, and a fax to the call center. The proposed flow posts the payment in real time.

    Process flowcharts
  • 2011

    Audit completed. Pre-visit interviews, an executive session to define the program's role, interviews with executives and mid-level managers, and observation of the workflow alongside associates at every member touch point.

    Ends in a gap analysis and an explicit go or no-go decision for the club.

    Audit report
  • Aug 2012

    System proposal prepared for the AAA North Jersey Board of Directors, with a two-year cost profile and a phased rollout: membership, then travel, then auto routing, then roadside assistance.

    Board proposal
  • 2013

    Vision statement adopted: strengthen member relationships one interaction at a time, speak as one voice to the member, make it easy for members to get what they need in one place.

    Success criteria defined before deployment. Frontline surveys and branch feedback collected during it.

    Vision statement, success criteria
  • 2014

    Club results benchmarked against every other AAA and CAA club, and reported at the chief executive level.

    Association performance index
  • 2015–2016

    A permanent role written and posted to own the program, so it would outlast the person who started it.

    Position description

It is more than a database. People, process, and technology. Managers and executives will be able to create performance targets for staff and departments.

Board proposal, August 2012

The same room, now in code.

A competitive swim program runs on the same fracture. Registration and billing live in one platform, practice plans live in spreadsheets, changes travel by text message, and the rest lives in a coach's memory. The work is identical to 2007 and 2012. Decide what stays in the system of record, build the smallest useful layer for everything that falls between the tools, and put it in real hands before claiming it works.

Keep

The system of record

Registration, billing, rosters, and official meet commitments stay where they already work.

Add

The operating layer

Practice planning, attendance, role-aware communication, family access, and performance insight become one focused surface.

Prove

In production

Shipped to coaches and families on web and mobile, then measured by use and trust rather than by feature count.

What carried forward.

Three arenas, twenty years apart, and the same four moves in the same order every time. It is the method on the home page, and this is where it came from.

01

Go and watch

A morning observing two Baltimore departments taught more than a year of vendor demos. The AAA audit started by standing next to associates at every touch point.

02

Name the measures first

Bayonne defined metrics per department before the first meeting. AAA defined success criteria before deployment. Neither waited for the software to suggest them.

03

Put it in a room

Every two weeks in a city hall, at the executive table in a club, on the deck in a swim program. A dashboard nobody has to answer for changes nothing.

04

Build it to outlast you

A task force in one, a permanent posted role in the next, documented and handed-off systems in the third. The work only counts if it survives the person who started it.

About these sources

This page is assembled from dated primary documents rather than recollection: internal email, meeting invitations, itineraries, presentations, process flowcharts, an audit report, a board proposal, an adopted vision statement, benchmarking reports, and one public municipal press release. A few details are worth stating plainly.

  • The Bayonne CitiStat launch is public record, announced by the City of Bayonne on June 20, 2007 and effective July 1, 2007.
  • The March 1, 2007 visit date comes from an itinerary email sent Monday, February 26, 2007, confirming Baltimore for that Thursday with the morning departmental schedule.
  • CitiStat was created and run under Martin O'Malley as Mayor of Baltimore, and the visit was arranged through the office that operated it while he held that office. By the date of the visit itself he had been sworn in as Governor of Maryland. This was a working session with the departments, not a meeting with the mayor.
  • Internal cost figures, vendor terms, colleague names, and any member or family data are deliberately withheld.

If your organization has this problem, the pattern is usually the same one. So is the way out.

Connect on LinkedIn Return to the story