Speaker numbers apply only to this recording.
On October 21, 2026, the Saint Paul City Council held two sessions: the Budget Committee reviewed the Office of Technology and Communications (OTC) proposed 2027 budget, followed by a City Council Policy Committee discussion of standard operating procedures for honorary street co-naming. Both were discussion and informational sessions; no formal votes were taken. The provided agenda listed only the Budget Committee item, while the raw transcript also includes the Policy Committee meeting.
Order. Roll call, please. Vice Chair Yang. Councilmember Bowie. Councilmember Coleman. Here. Councilmember Kim. Here. Councilmember Jost. Council President Naker. Here. Chair Johnson. Here. Five present. Two absent, being Vice Chair Yang and Councilmember Bowie, whom are both excused. All right. So we are continuing the budget saga. And on this episode, don't play. We have the Office of Technology and Communications, OTC. Welcome, Director. Thank you so much, Chair Johnson. Good morning, everybody. It is so great to be here. Um Council President, Council members. This has been the quickest year of my life. And um grateful for for some reasons of that, and also just life is passing by too quickly. That has been going on since July of twenty twenty-five. But part of the decision making that happened during the cyber event was the tough decision to sunset some old legacy technologies whose replacements whose modern systems weren't quite ready for prime time yet. We made that tough decision because we knew something around 60 to 70% of organizations that have a cyber attack experience another attack within six months. We wanted to make sure that that did not happen to St. Paul and that didn't happen to St. Paul. But what that meant is that we had systems that we brought in a little bit early, and so we've been working very, very hard over this past year to get those systems working for the city, streamlining our systems and supporting city service. OTC has been working so hard over 2026 that right now 30% of my staff of our staff have over 200 hours or more of vacation banked up. That was an issue that I, you know, sometimes IT people just don't want to take vacation. They really get a lot of satisfaction of their jobs. I am, I I used to be one of those. Now I know that I need to take full breaks in order to survive. But you know, as the leader of this organization, I we made progress in early in my tenure to make sure people were taking their vacations so we didn't have this end of year problem. Um that kind of went by the wayside once we had our cyber attack, and we have so much work to do. I'll say that I'm continuing continuing to work with my staff to take those vacations. We need those breaks, but let's give a quick little example of the dedication we have from this team. So one of our talented employees had a Friday blocked a couple of weeks ago on his calendar. A meeting came up, and he was at that he was invited to, even though it was shown that he had vacation on his calendar. And I told him, hey, don't worry about that meeting. I'll step in, right? I'll I'll play your role for you so you can take that day of vacation. The people who created the meeting went directly to them, him and he, they were like, Can you please be at this meeting?