I want residents to know two things right away: I take the role seriously, and I intend to explain the work in plain English as I go.
As with most council meetings, some agenda items moved quickly. That does not mean the items were minor. Consent items still involve real contracts, real spending, and real policy consequences. I read the packet closely before the meeting, and I plan to keep doing that for every agenda item, not just the controversial ones.
What I'm watching most closely right now is the set of issues that shape affordability and trust in city government over time: utility rates, development rules, infrastructure planning, and whether major governance decisions are being made in a way residents can actually follow.
I also want staff to know early what they can expect from me. I am going to ask for the backup. If a recommendation depends on assumptions, I want to see them. If a contract creates long-term obligations, I want those implications stated clearly. That is not about performative skepticism. It is about doing the job carefully.
I'll keep posting after meetings so residents can track what happened, what mattered, and what comes next without having to sit through hours of video.
From the start, I treated the seat like a working job, not a ceremonial transition. I read the packet, tracked the fiscal and policy implications of agenda items, and set an early focus on the areas that most directly affect affordability and trust: utility rates, development rules, infrastructure accountability, and city governance. I also made clear, both publicly and internally, that I would be asking for backup on assumptions, contract terms, and long-term impacts rather than just taking recommendations at face value.