Some decisions feel solid when you make them.

Far fewer feel solid when they get challenged.

And that’s the real test.

If you work in local government, you know decisions don’t live quiet lives. They get revisited in public meetings. Questioned by residents. Appealed by applicants. Scrutinized by new leadership. Pulled back up months later by people who weren’t even in the room the first time. 

A decision that felt obvious internally can look thin later if the “why” is hard to find, overly technical, or living in somebody’s head instead of in the record.

That’s why durable decision-making isn’t just reaching a conclusion.

It’s building a record that can survive pressure. 

Because if the recommendation is good but the reasoning is vague, the work isn’t finished.

If the choice is defensible but nobody can explain it plainly, it’s still vulnerable.

And if staff keep changing direction every time the heat rises, that’s not responsiveness.

That’s reactivity. 

‍

The Real Work is Documenting the “Why”

Most departments are pretty good at recording outcomes.

The vote gets recorded.

The conditions get added.

The memo gets filed.

But the reasoning often lives in fragments: hallway conversations, email threads, verbal explanations at the dais, someone’s personal notes, or the institutional memory of the one person who led the case. 

That’s risky.

Because when the rationale is hard to reconstruct, everyone fills in the gaps differently. Staff remembers one thing. Elected officials remember another. The public assumes something else entirely. That’s how trust erodes and avoidable conflict grows. 

‍

A better standard is simple:

Every significant planning decision should leave behind a plain-language explanation of why it was made. 

Not pages of legal hedging.

Not a list of procedural steps.

A clear chain of reasoning that answers:

What decision was made?

What options were considered?

What criteria was used?

What tradeoffs mattered most?

Why this option over the others?

What concerns were raised, and how were they addressed?

What uncertainty remains? 

‍

That kind of record protects everybody.

It helps residents see the decision wasn’t arbitrary.

It helps elected officials explain their votes.

It helps future staff avoid re-litigating the same issue from scratch.

‍

Plain Language is Not A Style Choice. It’s a Resilience Tool.

People sometimes treat plain language like  it’s a communications preference.

It’s more than that.

Plain language is what helps a decision survive outside the room where it was made. 

Appeals, public records requests, media scrutiny, leadership transitions, and social media controversy all have one thing in common: they pull decisions out of their original context. And when that happens, technical shorthand stops working. 

“Inconsistent with the comprehensive plan” might be accurate.

It’s rarely enough.

Which policy? In what way? What conflict mattered? Why did it matter more than competing considerations?

Plain language doesn’t mean casual language.

It means precise language that ordinary people can follow.

‍

Design the Decision for Scrutiny, Not Just Approval

A lot of staff writing is shaped by a silent hope: get through the meeting.

I get it.

But if your documentation is optimized only for the first hearing, it may fail the second, third, or fourth moment of review. 

Before finalizing a major recommendation, ask one question:

How would this hold up if it were read six months from now by someone skeptical, rushed, and unfamiliar with the case? 

That question forces clarity.

It exposes missing steps.

It shows where you’re relying too much on shared internal context.

And it makes appeals less likely to succeed on technical weakness instead of substantive merit. 

‍

Responsive is not Reactive

This distinction matters.

Responsive government listens, adapts, and stays open to new information.

Reactive government lurches. 

The healthiest way to stay responsive without getting pulled around is to decide in advance what kinds of input can change the outcome:

New factual information should matter.

Evidence staff misapplied a standard should matter.

A previously overlooked operational impact should matter.

A better mitigation strategy should matter.

Volume alone should not.

Status alone should not.

Political anxiety alone should not. 

That’s not stubbornness.

That’s integrity.

And it’s how you keep the process from becoming a fresh referendum every meeting.
‍

Reframe to Restructure

Pressure doesn’t create the cracks.

It reveals them. 

It reveals whether rationale lives in documents or in people’s heads.

It reveals whether standards are truly standards or just habits.

It reveals whether the organization can absorb criticism without abandoning its method.

The goal isn’t invulnerability.

The goal is durability.

A good decision should be understandable to the public, usable by staff, legible to leadership, and sturdy under review. 

If it only works when the original people are there to explain it, it’s not finished.

And unfinished decisions rarely age well.

‍