· Systems & power
I Had Never Done This Before. But I've Totally Done This Before.
TL;DR: JPACT was my first time addressing a regional committee as an independent resident. It was not my first time learning a complicated system, translating it under pressure, or performing confidence. I got my three minutes. What happened after taught me more.
A little after six this morning, I was awake, preparing to speak for three minutes at a regional transportation committee meeting. This is not a sentence I ever expected to write about myself.
I am not someone whose lifelong passion is public transportation policy. Transportation happens to be one place where, right now, I can see a gap between what institutions say they are doing and what an ordinary person can actually see, understand, and follow. Once I notice a gap like that, I have a hard time leaving it alone. So transportation is my thing right now, and I am going 100 on it.
That is how I ended up giving public comment this morning to JPACT, the Joint Policy Advisory Committee on Transportation. JPACT is a 17-member regional body made up of elected officials and transportation-agency representatives that makes recommendations to Metro Council on the region's transportation needs. It was the first time I had ever addressed a regional committee as an independent resident. It also wasn't the first time I had done the work required to survive a room like that.
That distinction is what finally made the title of this piece make sense to me.
Long before I was sitting in front of a webcam talking about regional transportation accountability, I worked at Disneyland. One day, a literal mouse-in-a-salad situation unfolded on the patio. An emergency was happening a few feet away from people still trying to enjoy their nice Disney meal.
My job did not suddenly become reacting exactly the way I felt about a mouse in somebody's salad. Many audiences were in the same room. One was having an objectively terrible experience. The others were still sitting inside the carefully constructed reality they had paid to experience.
I had to understand both at the same time. I had to manage something genuinely bad while preserving enough normalcy that the entire room didn't collapse into chaos. It was an absurdly literal lesson in performance, and in the strange requirement to hold many realities in your head at once.
Years later, the stakes and setting looked different. I spent much of my career in public-safety technology and NG9-1-1, where part of my job involved demonstrating complicated systems to public-safety officials and procurement decision-makers considering contracts worth millions of dollars.
Those rooms also had multiple audiences. Some people were evaluating the technology. Others were thinking about operations, procurement, risk, budgets, implementation, or whether the demonstration landed at all. Sometimes people in the room knew the system deeply. Sometimes I knew considerably more about the particular thing I was demonstrating than people much more senior than me.
That was partly because of how I approached systems. When I owned a product, I wanted to know every nook and cranny of it. I wanted to understand not just the intended workflow, but the edge cases, the weird questions, the places where something broke, and the reason the system behaved the way it did. I tended to go farther into the machinery than my role strictly required because surface-level knowledge never felt sufficient.
That depth mattered when I had to perform competence in front of people with more senior titles, more institutional authority, or more purchasing power than I had. My job was to know the system well enough that, when someone asked a question I had not anticipated, I could understand what they were really asking and translate the answer into the version that mattered to them. The confidence I projected did not come from pretending to know more than I did. It came from having done enough work underneath the surface that I could usually reason my way through the question in real time.
That is a very specific kind of pressure. You can know exactly what you are doing and still be nervous. You can be competent while your nervous system is doing something completely different.
I learned how to appear calm while those two realities existed at once. Sometimes I would finish a demonstration, hold myself together through the whole thing, and cry afterward. For a long time, I treated that as evidence that the confidence in the room might have been fake.
I do not anymore.
Confidence comes from being comfortable. Another kind comes from knowing what you are doing well enough to keep functioning while you are deeply uncomfortable. I have spent a lot of my career practicing the second kind.
So when I woke up this morning to memorize three minutes of testimony for a government committee I had never addressed before, the situation was new, but the muscles were not. I knew how to learn the system, know the material, understand the audience, translate the complicated part, stay inside the time, and keep going without confusing nervousness with incompetence.
Public participation was a new room, not a new set of muscles.
That is why I memorized my three-minute comment. I wanted to look into the camera when I spoke. I wanted to know my request well enough that I did not need to hide inside a document. I researched the committee, figured out how public testimony worked, rehearsed what I wanted to say, and woke up early enough to be ready for a 7:30 a.m. government meeting. Metro's published process gives individual speakers three minutes unless otherwise stated, which is exactly the window I was preparing for.
Here is the full public comment I delivered.
Then I intentionally stopped talking before my time ran out.
That mattered to me because I wasn't there to educate them about regional transportation. JPACT includes elected officials and transportation agency representatives. They have professional staff, policy expertise, institutional knowledge, and access to information I do not have.
I am the resident in this equation.
My responsibility was to explain what I needed from the system clearly enough that there could be no confusion about the request.
Through Portland TRAP, the Portland Transportation Recovery Accountability Plan, I asked for basic visibility into implementation. If the region says it is working on transportation recovery, I want residents to see what action is being taken, who owns it, what can happen under existing authority and funding, what requires something new, what happens next, and when the public should expect to see that work again.
I asked for an initial ownership and follow-up structure within 60 days.
Then my public comment ended, the meeting moved on, and nobody substantively responded to what I had asked. There was no referral, no staff assignment, no follow-up commitment, and no explanation of whether the request belonged somewhere else. My three minutes existed, and then the agenda continued.
I want to be precise about what I mean by that because I am not interested in manufacturing a scandal where none exists. Public comment is not designed as a guaranteed question-and-answer period. The committee was not procedurally required to stop the meeting and engage with me. I received my opportunity to speak.
The process worked.
That is exactly why the experience interested me so much.
I am much less sure that being given a process and being meaningfully represented are the same thing.
I stayed for the rest of the meeting, probably another hour and a half, and that changed the way I understood my own three minutes. The meeting did not become silent after public comment. People interacted. Agency representatives were acknowledged. Officials thanked one another. People referred back to things others had said. There were moments of warmth and professional familiarity.
I was simply not part of it.
Nothing procedurally wrong with that, and maybe nothing unusual about it. Somehow that made it more jarring rather than less.
Very few members of the general public spoke this morning. The meeting itself included a much larger group of elected officials, agency representatives, and staff. Throughout the call, people regularly thanked one another for participating and acknowledged the institutions they represented.
That is normal professional behavior. I am not offended that they thanked one another.
What struck me was the contrast.
The person in the meeting with probably the least institutional authority had used the formal mechanism specifically designed for the public to speak, and there was no comparable human acknowledgment of the substance of what I had brought into the room.
I did not need praise or agreement. I did not need them to turn my three-minute comment into the centerpiece of the agenda. A sentence would have been enough. Even, “That belongs somewhere else, and here is where.”
Instead, the experience felt remarkably transactional: you have your allotted time, your time is complete, next item.
That felt unbelievably familiar.
If you have spent enough time in corporate America, you probably know this meeting. Everyone is busy. Everyone has a title. Workflows, priorities, road maps, governance structures, SOPs, and calendars are packed with evidence that activity is happening.
Eventually somebody has to ask whether the activity is fixing anything.
That was one reason I appreciated some of the questions Clackamas County Commissioner Paul Savas asked during the meeting. Metro lists Savas as the Clackamas County member of JPACT. He wasn't responding to me or to Portland TRAP, and I don't know enough about his broader record to endorse him. I simply appreciated hearing practical questions.
At several points, his questions sounded closer to the way my own brain works: What are we actually trying to accomplish? Is this the right thing to be working on? What problem does this fix?
It felt like an attempt to pull the conversation back to what's underneath the process.
Those are also variations of the questions underneath Portland TRAP. What are we doing? Who owns it? What happens next? Does this actually improve the problem residents are experiencing?
At times during the meeting, I felt like I was watching two different kinds of participation happen at once. Some people were participating from inside the machinery. They knew the language, the relationships, the agenda's sequence, and their role in it. I was participating from outside of it.
That brought me back, strangely enough, to the mouse in the salad. Many audiences. Many realities. One room.
Except this time I wasn't the employee standing between them, trying to preserve the experience. I was the person on the outside trying to figure out whether the institution could see the reality I was describing at all.
Near the end of the meeting, Chair Christine Lewis made another comment that lodged itself in my brain. Lewis is JPACT's current chair. I am deliberately paraphrasing because I do not want to turn my memory into an exact quotation. The basic point was that it was already the middle of September; the work being discussed would take time to get started, which would push things toward the end of the year; and at some point, the realistic conversation becomes the new year.
I know this logic extremely well. Corporate America runs on it. Q4 gets strange. Calendars disappear. Holidays arrive. Budgets close. Someone suggests picking it back up in January.
When the thing being delayed is another internal corporate initiative somebody invented in a conference room, I am not losing sleep over it.
Government has a different customer.
People are still alive in November. The bus still has to arrive in December. Someone still has to reach chemotherapy, get to a night shift, get their child to school, buy groceries, or get across town to care for somebody they love.
The calendar flipping from 2026 to 2027 may have enormous organizational meaning. It does not mean very much to the person waiting at the bus stop, especially when they didn't get the memo that the bus stop was closed last month and they are waiting for nothing.
That is one place where institutional timelines and human timelines stop matching.
It is also one reason I am not especially interested in carrying the burden of excusing government institutions for how hard their jobs are. I understand that the people on JPACT work inside complex systems. Transportation governance is complicated. Regional coordination is complicated. Their jobs may be difficult.
That is not my responsibility to carry into the room for them.
I do not think a resident should have to preemptively excuse an institution because institutional work is hard. My role was to bring the lived experience. Their role is to figure out what to do with it.
I left the meeting feeling two things at once.
The first was pride. I did something I had never done before. I learned the process, prepared, memorized three minutes because I cared enough to speak directly rather than stare at a page, and entered a formal government process without a company, organization, campaign, or professional title giving me permission to be there.
I made something I cared about part of the record.
That feels powerful.
The second feeling was much stranger. My public comment was, in its own small way, another performance of usefulness. I completed my part of the procedure. The institution completed its part. Everything technically happened.
I am still sitting here asking what happens now.
That may be the most useful thing I learned this morning, because I think more people should pick a committee.
Not necessarily a transportation committee. You do not need to care about my issue. Your thing might be housing, public health, schools, emergency services, utilities, libraries, land use, disability access, parks, budgets, or something completely different.
There are bodies like this everywhere. Most of us do not know their names. We usually do not know when they meet, who sits on them, or what they are discussing until one of their decisions reaches far enough into our lives that we suddenly have to care.
That absence is understandable. People are working, raising children, caring for family members, attending school, looking for jobs, and trying to keep themselves afloat.
But the meetings still happen when we are not watching them.
I have been thinking particularly about people who are unemployed right now. Unemployment is frightening and exhausting. It can leave you with an enormous amount of anger without anywhere useful to put it. It can make you feel like your usefulness disappeared when your job did.
It can also leave people with something our institutions quietly depend on most of us not having: time.
Maybe some of us can spend a little of it watching.
Not because everybody needs to become obsessed with local government. Not because sitting through committee meetings cures unemployment or despair. But because anger can become information.
Pick a thing. Find the committee. Read the agenda. Watch what they talk about when almost nobody else is watching. Notice which questions get answered and which ones disappear. Learn who actually owns the thing you care about.
You do not have to become a policy expert. You do not need to run for office. You do not need to turn yourself into a professional activist.
You can just become annoyingly familiar with one corner of your own community.
One person appearing for three minutes is not going to transform an institution. I knew that before I spoke this morning.
Accountability requires something much less cinematic and much more annoying: repetition.
Someone has to remember what was promised three meetings ago. Someone has to notice when 60 days becomes six months. Someone has to compare the presentation to the lived experience. Someone has to ask why a responsibility keeps moving between agencies without becoming an action. Someone has to remember the comment after the commenter disappears from the Zoom screen.
Institutions have institutional memory.
The public needs some too.
That brings me back to the word representation.
I pay taxes. I live with the consequences of public decisions. The government provides a procedure through which I can speak. This morning I used it exactly as designed.
I still left wondering where, in that process, I was actually represented.
Maybe public comment was never supposed to accomplish everything I wanted it to accomplish. That is a perfectly reasonable answer.
Then I want to know where the next door is.
Who actually owns this request? Which body can respond to it? Which staff can implement it? Which elected officials should hear it? Where does a resident go after the microphone shuts off?
That is what I am doing next.
And this is where the title comes back around.
Yesterday, I did not know how to testify at JPACT. Today I do. I had never done this before, and I had absolutely done this before.
Different room. Different acronym. Different stakes.
At Disneyland, I learned how to hold many realities in my head while a mouse sat in somebody's salad. In public-safety technology, I learned how to walk into rooms where millions of dollars could be attached to the quality of my performance, understand several audiences at once, and translate a complicated system clearly while my own nervous system did whatever it was going to do.
This morning, I used those same muscles as a resident.
The difference now is that I am not doing it on behalf of an employer. There is no contract at the end, no customer to close, and no corporate logo giving me authority.
I am doing it because I live here.
When the room gives me nothing back, I don't have to pretend nothing happened.
I can document that too.
Then I can figure out who comes next.
And come back.