![](data:image/svg+xml,<svg display="block" role="presentation" viewBox="0 0 24 24" xmlns="http://www.w3.org/2000/svg"><path d="M 3.234 10.567 L 0.598 10.567 L 0.044 0 L 3.788 0 Z M 0 14.267 C 0 13.588 0.185 13.115 0.554 12.849 C 0.923 12.569 1.374 12.428 1.905 12.428 C 2.422 12.428 2.865 12.569 3.234 12.849 C 3.604 13.115 3.788 13.588 3.788 14.267 C 3.788 14.917 3.604 15.39 3.234 15.685 C 2.865 15.966 2.422 16.106 1.905 16.106 C 1.374 16.106 0.923 15.966 0.554 15.685 C 0.185 15.39 0 14.917 0 14.267 Z" fill="rgb(255, 255, 255)" height="16.105846188517717px" id="d8ocSgdvf" transform="translate(20.148 3.872)" width="3.7883077087402377px"/><path d="M 3.146 2.171 L 0 2.171 L 0 0 L 3.146 0 Z M 3.079 14.156 L 0.066 14.156 L 0.066 3.655 L 3.079 3.655 Z" fill="rgb(255, 255, 255)" height="14.156313890536383px" id="Q86BCRZI9" transform="translate(14.648 5.534)" width="3.1458461538461666px"/><path d="M 11.897 13.292 L 8.706 13.292 L 8.706 8.108 L 3.19 8.108 L 3.19 13.292 L 0 13.292 L 0 0 L 3.19 0 L 3.19 5.25 L 8.706 5.25 L 8.706 0 L 11.897 0 Z" fill="rgb(255, 255, 255)" height="13.292307692307693px" id="gBNeo28SG" transform="translate(0.543 6.398)" width="11.896608000000015px"/></svg>)
MY ROLE
Lead Product Designer
DELIVERABLES
Wireframes
High Fidelity Screens
Responsive Design
Design System
Prototype - Interaction Design
Handoff Documentation
TEAM
Accurate Voting Services
Project Manager
Front-end & Back-end Developers
QA
YEAR
2024
What Was the Problem?
Accurate Voting Services (AVS) runs legally binding elections for Homeowners and Condominium Owners Associations. Everything was on paper, which meant:
printing, mailing and hand-counting hundreds of ballots for every election;
counting errors, especially in cumulative voting weighted by units, that could invalidate an election;
no way to know if quorum was reached until the envelopes were opened;
owners away from the property effectively losing their vote.
The Challenge
A ballot is a legal document, so the platform couldn’t simplify its wording, structure or counting rules. It had to reproduce them exactly for admins and owners with very different levels of digital comfort. It also had to keep votes secret while recording who voted, and accept mail-in ballots without breaking anonymity.
Building a Ballot That Matches the Law
I designed a ballot builder where admins create each measure with the rule it requires: multiple select with a vote limit, select one, text answer, cumulative voting by units, and abstention. The system does the math and enforces the limits for the voter. Ballots can be saved as drafts, reused as templates, previewed and exported as PDF, with a separate set of text styles made for print.
A Voting Experience That Reads Like the Legal Document It Is
The digital ballot keeps the structure and language of the paper version, so it feels just as official. Owners don’t need an account: they get a passcode by email, confirm their units and vote. A live counter prevents invalid ballots, and a confirmation step shows every choice before the vote is final.
Anonymity and Accountability at the Same Time
Admins need to know who voted, but never how. I separated the two everywhere: one view lists who voted, when and how (online or mail), and another shows only the totals per measure. Mail-in votes go into the same anonymous pool, and a vote can be revoked without ever being revealed.
Getting Messy Real-World Data Into the System
Voter lists come as spreadsheets full of duplicates and missing data. Instead of rejecting the file, the CSV import shows which records conflict before anything is saved. Deleting anything tied to an active ballot requires typing a confirmation word.
Creating a System - and Making It Work on Every Screen
The platform works on desktop, tablet and mobile for admins and voters. I built a design system with every recurring element and defined responsive behavior inside each component. Modals, for example, are centered on desktop and anchored to the bottom on mobile, with different ways to close them.
Developer Handoff Documentation
Much of this product’s behavior isn’t visible in a static screen, like vote limits, anonymity rules and error states. I documented every feature with front-end notes, plus a general page for repeated patterns, and marked each error found in client interviews where it happens.
Conclusion
I turned a legally binding paper process into a digital platform without bending any of its rules. Admins do much less manual work, owners vote from anywhere, and every ballot stays secret and auditable.
Disclaimer: some client data has been replaced for confidentiality