Strategic leadership is what turns city AI work from staff interest into city direction.

Staff can surface the work, but leaders still have to set the direction. Before the city can finalize an AI policy package, executives need to settle scope, risk posture, approval authority, public expectations, and who owns updates after launch.

What executive leadership should decide early

Executive leadership should decide what the city is trying to do with AI, what is out of bounds, how much risk the city is willing to accept, who can approve different kinds of use, what residents should expect, and who owns updates after launch. Staff can turn those decisions into working materials, but leadership needs to set them early so the repo can help carry the work forward.

Set scope and priorities

Decide which AI uses, departments, or service areas matter first so staff are not building around a moving target. A city does not need to solve everything at once, but it does need to say what matters now.

See what the city needs first

Set limits and risk posture

Decide what is off limits, what requires extra review, and how much risk the city is willing to carry. This is where leaders decide how strict or flexible the policy should be.

Open rules and review

Assign approval authority

Name who can approve different categories of use, who can pause or escalate them, and what still needs legal, procurement, departmental, or executive sign-off before launch.

See the review path

Set public expectations

Decide what the city wants residents, council, and frontline staff to understand about AI use. If the leadership team cannot explain the direction simply, the draft will not hold up publicly.

Open public explanation

Key consideration

Name the sponsor and the owner after launch

Strategic leadership is not just first approval. The city still has to name who sponsors the work, who owns updates, and what triggers a new review when tools, vendors, or use cases change later.

See the full program package

Use the repo when leadership is ready to give staff real direction.

The repo should help the city turn these executive choices into working drafts, decision templates, and review materials. Once the sponsor, scope, limits, and approval path are clear enough to act on, stop circling the issue and move into the working files.

  • Use the leadership templates to structure scope, authority, and risk decisions.
  • Use the prompts and examples to turn those decisions into real policy materials.
  • Use the review path when the city needs sign-off discipline before approval.

Before staff treat the direction as settled, make sure these are true

These checks keep the city from calling the direction clear when it is still mostly implied.

  • The city has said what AI work is in scope now and what can wait.
  • The city has said what kinds of uses are off limits or require extra review.
  • The city has named who can approve, pause, or escalate different categories of use.
  • The city has said what it wants staff, council, and residents to understand about AI use.
  • The city has named who owns updates and maintenance after launch.

Once leadership has set the direction, move the work into the repo.

The best use of this page is to get the executive questions onto the table. The best next step is to use the repo to turn those decisions into working materials. If your city still cannot settle the sponsor, scope, or authority after that, get help at the end of the process.

Open leadership working files

Use the templates, prompts, and review materials that support leadership decisions and policy drafting.

Open leadership working files

Get help

If the city has surfaced these questions and still needs help aligning leadership around the answers, get help here.

Get help