Digitizing Democracy in 24 Hours
Influenced Parliament rule change
Brief lands at 09:00. Finland is in COVID lockdown, 200 Members of Parliament can't be in the same room, and the existing rules require in-person voting. The artefact has to be in front of decision-makers by 05:00 the next morning. Twenty hours, end-to-end, for a prototype that Parliament will take seriously enough to consider rule-changing legislation around. The clock starts.
How do you enable democratic processes when MPs can't physically gather, fast enough to maintain government continuity, against a regulatory framework that doesn't yet allow what you're building? The honest answer is you don't — unless you've already compressed the validation methodology enough times to know which 80% of a typical sprint is scaffolding you can skip.
The shape of the week
- 01
Hours of regulatory and compliance research with parliamentary advisors before touching pixels
- 02
Wireframes and evening check-in with feedback
- 03
Overnight Figma prototype with two user paths: technical staff and representatives
- 04
Research into actual Parliament voting panels and dials for familiar visual language
- 05
Initial design system for scalability if the project moved forward
Visma Solutions / Parliamentary advisor
“A viable, carefully considered solution. A complete UI prototype with processes, incorporating all Parliament feedback.”
The moment that surfaced
The prototype was comprehensive enough that Parliament took it seriously. Speed came from structure, not shortcuts. The same sprint methodology refined over dozens of engagements, compressed to 24 hours.
What the week bought
A complete UI prototype with processes, incorporating all Parliament feedback. Never deployed due to regulations, but influenced Parliament's October 2020 decision to amend rules and permit remote voting.
- Complete Figma prototype delivered in under 24 hours
- Two user paths: session management and vote casting
- Strong authentication and real-time vote tracking designed
- Influenced Parliament's rule change permitting remote voting
Why the sprint earns its week
Speed comes from structure. The reason I could deliver in 24 hours is the same method refined over dozens of sprints. Understanding the problem deeply before touching pixels.
Want this kind of result? Start with the version that matches your situation
These pages break the work down by the problem teams usually feel first, before they know what kind of engagement they actually need.
Design & Validate
Design Sprint for B2B Teams
For teams dealing with long sales cycles, messy workflows, and too many stakeholders to rely on guesswork.
Service Transformation
Service Blueprinting Consultant
Map what really happens across teams, systems, and touchpoints, then redesign the parts that keep the service from working.