Neil McKay

Granicus 2007 · Govinity 2025–2026 · Govtech

Public meetings, twenty years apart

A city council meeting is live, public and legally on the record. The clerk running it can't pause to hunt for a button. Twice, nearly twenty years apart, I've designed the tools used in that room.

Then
VoteCast Touch at Granicus: touchscreen voting for elected officials and meeting chairs
Now
Govinity clerk console: running agendas, motions, roll calls, speakers and captions live. UX designer, contract
Users
City clerks, council members, chairs, and the stenographers and shorthand writers who record them

Then: VoteCast Touch

VoteCast was an existing product that wasn't working. Its users were elected officials, often wary of technology arriving in their chamber. Rather than reskin it, we ran a full process: workflow mapping, paper prototypes, interactive prototypes, and testing with the people who'd use it on the dais.

Paper first

We started with pens. A touchscreen on the dais gets held, rested on and reached across, so the first sketches were about hands. Fingers rest on the edge of the screen, so every screen needs a margin. The status bar stays short, and the vote buttons sit where the hand already is. I mapped the easy reach for left and right hands and kept the priority controls inside it.

Hand-drawn sketches of a touchscreen with a hand resting on its edge, a reach map showing read-only and interactive areas, and a login flow
Ergonomics sketches: a margin for resting fingers, and reach zones for each hand.

Then the screens, step by step through an agenda item: review the item, start a motion, put it to a vote, show live results.

Hand-drawn layouts for current item, motion on the floor and voting screens, with notes on the steps of an item
Layout sketches for each stage of an item.

Login and navigation got the same treatment. I cut the screens out of paper, laid them on a sheet, and slid pieces in and out while a colleague tapped through. Pick your name, enter a PIN, see what happens when the PIN is wrong.

Three photos of a paper prototype: a Select User list with a finger on a name, the PIN pad after choosing a name, and a yellow wrong-PIN message
Paper prototype: choose a name, enter a PIN, recover from a wrong one.
Two photos of paper prototype screens: the current item with Request to speak and motion buttons, and the agenda with an item document expanded on a yellow sticky
The item screen, and the agenda with a document slipped in on a sticky note.

The hard part was state. A motion can be started, moved, seconded, withdrawn, stopped and reopened, in many orders. I charted every state and every move between them, first by hand, then as a clean diagram engineers could build from.

Hand-drawn state chart of numbered boxes with arrows for start motion, first, second, withdraw and reopen, above the cleaned-up digital version
Motion states, worked out on paper and then cleaned up.

The redesign made every state unmistakable. A member who made a motion sees it. A vote in progress takes over the screen. A cast vote shows clearly, with a way to withdraw it. Feedback from clerks shaped the details: always show the motion text, tie the speaker list to the current item, and keep the result visible until the next item starts.

VoteCast voting screen: motion with mover and seconder, a confirmed Yea vote with a withdraw option, and large Nay, Abstain and Recuse buttons
VoteCast, about 2007. Large targets, one state at a time, and a confirmed vote that can be withdrawn.
VoteCast redesign wireframes: a new item with motion and speakers, motion started, voting on the floor with large green, red and orange buttons, and a vote recorded showing Motion Passed with the tally
Redesign wireframes. Each state takes over the screen: motion on the floor, voting, then the recorded result, which stays until the clerk moves to the next item.

Now: the Govinity clerk console

Govinity, founded by people I'd worked with at Granicus, builds end-to-end software for public meetings. Its engineers had built the clerk's live-meeting console to meet an urgent need. It worked, but it was inconsistent, unfocused and built for the mouse.

I audited the interface and reworked it, prototyping directly in Replit so engineers had working code to build from, not static mockups.

Govinity clerk console in dark mode: agenda list with the active item highlighted, a speakers queue, presentation, video and live captions panels, and an action bar with keyboard shortcuts
The clerk console. The active agenda item and live status stand out; everything else steps back.

Design basics, applied

Consistent components, spacing and type across every panel. A clear hierarchy so the current item and live status lead, secondary tools sit one level back, and tertiary functions stay out of the way until needed.

Night mode

Meetings run for hours. A dark interface eases eye strain and lets the few things that matter, live status, the active item, a motion on the floor, stand out with real contrast.

Hands never leave the keyboard

Clerks type, and some record with steno machines that act as keyboards. Every action got a single key: N for a note, R for roll call, M for a motion, P for a privileged motion, A for an amendment. Roll call is marked with number keys, Escape cancels, and a status bar always shows which mode the clerk is in.

Roll call panel with a grid of council member initials, marked by tapping or number keys, with keyboard hints for start and cancel
Roll call: tap members or use the number keys. The status bar shows "Roll call draft".
Privileged motion composer: motion type Adjourn, motion text, mover selection, with keyboard hints to save or cancel
Privileged motion composer, opened with P and completed without the mouse.

AI in the workflow

I used Claude to research and pressure-test the keyboard-first strategy: shortcut architecture, focus management, steno compatibility (no autocorrect or smart quotes fighting the stenographer), foot pedals, and offline resilience for chambers with bad Wi-Fi. Then I built the prototypes in Replit with AI-assisted code.

Outcome

The redesign went to Govinity's engineers as working prototypes. Govinity is now rolling out to its first government clients.

Looking back

The job in the room hasn't changed in twenty years: an agenda, a motion, a mover and a seconder, a vote, a queue of speakers. What changed is how I work. In 2007 a prototype meant weeks of Flash. In 2026 it meant a working app in days, which let the design conversation happen in the product itself.

The constant lesson: in live, high-stakes operations, the interface has to show exactly one thing that needs attention, and make the next action effortless.