Like many early-career designers, I spend most of my time thinking about projects in terms of design, coordination, and construction. What I didn't fully appreciate when I entered the profession was how much happens before a project ever reaches those stages.

Over the past year or so, as I've become more involved in municipal work, I've had the opportunity to attend City Council meetings and see firsthand how public projects move from ideas to reality. What started as away to better understand the projects I was working on became one of the most valuable learning experiences of my career so far.

Sitting in council chambers and listening to conversations about funding, community priorities, long-term planning, and the concerns of residents introduced me to an entirely different side of the built environment.

There Are A Lot More People Behind a Project Than YouThink

One of the first things that surprised me was just how many people are involved in moving a public project forward.

As designers, it's easy to focus on what eventually gets built: a renovated facility, a new public space, or a civic building. What you don't always see are all the people and decisions that got it there.

Long before construction begins, a project has likely moved between City staff, project managers, consultants, finance teams, legal counsel, city administrators, elected officials, and the community itself. Each brings a different responsibility and perspective to the table. A project that might look straightforward from the outside can represent months, or even years, of conversations and compromises behind the scenes.

Seeing that process changed the way I think about communication as a designer. Our ideas have to make sense beyond the design team and establish a common understanding. Clear design intent gives everyone involved a framework to return to as questions arise, circumstances change, and decisions have to be made.

There Is a Process Behind the Process

I was also surprised by how much work happens before something ever appears on a council agenda.

From the outside, it can seem simple: an item comes before Council, there's a discussion, and a decision is made. Sitting in those meetings taught me that the public vote is often just one visible moment in a much longer process.

By then, City staff may have spent considerable time studying the issue, reviewing its financial and legal implications, gathering public notices, conducting workshops, and preparing a recommendation. That work isn't always visible from the audience, but it's what allows decisions to be made transparently and responsibly.

It also gave me a different perspective on why municipal projects sometimes take time. A City isn't making a decision only for the people who need something today. It has to consider how that decision will affect the community years from now.

Good Design Still Has to Work on a Real Budget

Learning how public projects are funded has probably changed my perspective the most.

Every project exists within a much larger financial picture. A community may want a new facility, but that need exists alongside every other responsibility the City has. They could also be discussing about Capital Improvement Programs, operating budgets, bond funding, maintenance costs, long-term fiscal planning, infrastructure improvements, and countless other needs. There is only so much funding to go around.

Hearing those conversations firsthand made the phrase "designing to a budget" mean something different to me. It's not simply about reducing cost. It's about understanding where an investment will have the greatest impact and thinking beyond what it costs to build something today.

A decision that makes sense during construction might create an operational or maintenance burden years later. On the other hand, spending more upfront might create better long-term value. Those tradeoffs are very real for municipalities, and understanding them has made me think more critically about the recommendations we make as designers.

Sometimes the Smallest Comments Matter Most

Perhaps the most meaningful part of attending council meetings has been hearing directly from residents.

Designers can study a site, review codes, and analyze technical requirements. All of that matters. But none of it can completely tell you what it's like to live somewhere every day.

Residents can.

Sometimes a person speaks for only a few minutes about something that seems relatively small on paper: a difficult intersection, a place that doesn't feel safe, or a part of their neighborhood they don't want to lose. But to that person, it isn't a small issue. It's part of their everyday life.

Those moments have stayed with me.

They've reminded me that a project can check every technical box and still miss something important. Ultimately, the people who live with our decisions will experience them very differently than those of us looking at drawings on a screen.

The People Keeping a City Running

Council meetings also introduced me to people whose work I hadn't fully understood before.

City staff are constantly balancing immediate problems with long-term needs. I've watched department directors, engineers, planners, public works staff, and administrators present recommendations, answer difficult questions, and work through issues that most residents will never see.

That gave me a much greater appreciation for what happens behind the scenes of a functioning city.

It's easy to notice a finished park or public building. It's much harder to see all the people whose work made it possible. Municipal work has taught me that almost nothing meaningful gets done by one person or one profession alone.

Why Young Designers Should Pay Attention

For young professionals, especially those in the design industry, I think there's tremendous value in sitting through a local council meeting.

You begin to see where your work actually fits.

A drawing is only one piece of a much larger system shaped by public priorities, available resources, regulations, politics, and the experiences of the people who live there. Understanding that context doesn't make design less important. I think it makes us better designers.

The more we understand about what surrounds a project, the better equipped we are to create solutions that are functional, aesthetic, and actually work for the people we're designing for.

Before attending these meetings, I understood that public projects affected communities. What I didn't understand nearly as well was how many individual voices, decisions, constraints, and responsibilities shape those projects before we ever begin drawing.

Now, when I look at a municipal project, I see more than the building.

I think about the City staff who have spent years working toward it. The residents who stood up to explain what matters to them. The people responsible for making the budget work. And ultimately, the community that will inherit whatever we design.

As an early-career designer, that perspective has been invaluable. It's made me more curious, more empathetic, and much more aware of the responsibility that comes with putting something into a community that maybe there for decades.