What a loading dock taught me about City Hall

Before I entered public service, I spent years building a manufacturing company in Green Bay.

Running a small company made government decisions tangible. A rule was not an abstract paragraph. It could affect whether a truck reached the loading dock, whether equipment could be installed, whether an employee had work to do, or whether a customer received an order on time.

One summer day, a city inspector delivered a notice saying the turning radius at our loading dock did not meet city requirements.

That was serious for our business. The dock was part of how materials arrived and finished products left. If trucks could not get in and out, production schedules, customers, employees, and cash flow could all be affected.

We pulled the paperwork, checked the measurements, and worked through the requirements. The dock complied. Resolving the notice still took far more time and effort than it should have.

I tell this story as I remember it. I am not naming the employee or quoting a section of code because those details have not been independently verified. The part of the experience approved for public use is the practical dispute: the notice threatened an essential business function, the facts showed compliance, and the correction process was harder than it needed to be.

The lesson was not that inspections are unnecessary or that every business owner is right.

Rules protect workers, customers, neighbors, property, and the public. Inspectors have to identify real problems, document them, and require corrections. A city that ignored safety or applied standards only when convenient would fail both residents and responsible businesses.

The lesson was that accuracy and responsiveness are part of enforcement.

An official looking at one file may see a notice that can be revisited later. The owner sees deliveries, payroll, customer commitments, and employees waiting to learn whether work can continue. A delay that appears routine inside a system can become expensive outside it.

That difference in perspective stayed with me.

When a resident or employer challenges a conclusion, government does not have to accept the challenge automatically. It does have to review the relevant facts, explain the standard, correct an error when the evidence requires it, and close the loop clearly.

The experience also changed how I thought about frustration with City Hall. Complaining to other business owners might have felt justified, but it would not change the process for the next person. I became more interested in how public systems were designed, who made the decisions, and what responsibility citizens had to participate.

That interest helped move me toward service on the Brown County Board and later toward running for mayor. The loading-dock dispute was not the only reason. It was one concrete moment that connected business experience with questions about public administration.

As mayor, I worked with city employees who handled difficult responsibilities every day. Many brought deep knowledge and a strong commitment to the public. My earlier experience did not teach me to distrust them. It taught me that leaders have to design systems in which good employees can respond to facts and residents can receive a clear answer.

The standard I took from the loading dock was practical: apply rules fairly, get the measurements right, listen when evidence challenges the first conclusion, explain the decision, and follow through.

That standard began with a truck route into a Green Bay manufacturing business. It remained relevant in every part of City Hall where one notice or one file could carry much larger consequences for the person waiting outside the office.