The instruction came from the Chief Information Officer during the Chief Technology Officer tenure: manage by influence rather than by managing people. That is what the following fourteen years were, deliberately.
It matters that this was a direction rather than a limit. The line organization had already been run — up to 89 staff as Network Infrastructure Manager, before the CTO post — so the move out of headcount was a decision about where the leverage was, not a ceiling anyone had reached. In an estate where five constitutional officers — the Sheriff, the Clerk of the Circuit Court, the Property Appraiser, the Tax Collector and the Supervisor of Elections — were elected independently of the Mayor, where the State Attorney and Public Defender answered to the state and the courts to nobody in the executive, and where Fire and Rescue, Public Works and the library system each held their own budget and IT staff inside the City, the leverage was never going to come from a reporting line. It came from the charter and from the estate: a governance remit over all of them on paper — the independent authorities aside — and some part of every one of them running on shared infrastructure in practice. There was no reporting line to be had.
What it actually requires
Authority makes a bad standard survivable, and its absence is what makes a good one necessary. Working this way changes the job in three specific ways.
The evidence has to be in the room before the opinion is. An agency that can decline a standard will decline one supported by preference. The cost model, the propagation study run over the city’s own GIS data, the packet capture platform that could answer what was actually on the wire — these were instruments of persuasion as much as engineering, because they replaced an argument about who was more senior with an argument about what was true.
The review board has to be able to outvote its chair. The Enterprise Security Committee charter was written that way on purpose. A body whose chair always wins is an approval queue, and the organizations outside the room can tell the difference immediately.
The people who have to live with a pattern have to help write it. Which is why the Architecture Technology Governance Committee carried operations, delivery, helpdesk and QA rather than architects alone. Governance that only involves architects produces standards architects like.
Why it is worth stating plainly
A career record that shows a line organization early and none later invites the reader to supply the usual explanation. The usual explanation is wrong here. The technical authority grew as the headcount fell, which is an unusual trajectory and a deliberate one — and the practice it produced transfers to every environment where an architect has to move an organization they do not control: post-merger estates, multi-agency programs, federated enterprises, and any consultancy where the client owns every decision.
Outcome
Standards adopted by agencies free to refuse them, on evidence rather than authority.