This is the story of how we took OpenPolicy from a messy, unusable app to a clean, powerful platform that puts people closer to their government.
Content
Quick Overview
01
Research and Insights
02
Design and Features
03
Next Steps
04
Product Overview
OpenPolicy was designed to bridge the gap between the people and the government. Currently, there isn't an official platform that allows citizens to voice their concerns,
vote, or engage with bills being passed. OpenPolicy changes that.
My Role
I led the product design and oversaw development to ensure the app aligned with both user needs and business goals. My responsibilities included:
- Full UI/UX Redesign: Transforming the app into a clean, user-friendly experience.
- Website & Dashboard Design: Expanding the platform beyond mobile for broader accessibility.
- Development Oversight: Ensuring that the app was built according to the design vision.
I worked closely with developers, solving design challenges in real time and ensuring a seamless implementation.
The Problem
The idea for OpenPolicy came from recognizing a major gap: there was no structured, official platform for public participation in governance. The goal was simple: give people a way to follow what’s happening in Parliament and have a say in the process. There was an existing app when I joined the project, but it had major usability issues. The design was cluttered, confusing, and didn’t fully support the app’s mission. My task was to completely redesign the experience while keeping the core functionalities intact, making it more intuitive and accessible for users.
Challenges and Key Decisions
- 1 Redesigning Without a PRD When I stepped in, there was no Product Requirements Document (PRD), making it difficult to understand the full scope of the project. I had to reverse-engineer the previous app, speak with stakeholders, and map out the entire system myself.
- 2 Navigating an App Store Rejection One of the biggest hurdles was that the original app had been rejected by iOS. A key reason? Comment moderation. Allowing users to comment freely on political issues could lead to toxicity, misinformation, and even legal concerns. I made a major design decision to remove the comment section entirely. This would prevent unregulated debates while keeping the platform professional and constructive.
Challenges and Key Decisions
- 3 Creating a More Engaging Interface The old app lacked structure and visual clarity, making it difficult for users to navigate. I focused on three key areas to improve usability:
- Simplifying Navigation: Ensuring key sections (Bills, Debates, Committees) were easily accessible.
- Clear Information Hierarchy: Using typography and spacing to highlight key actions.
- Aesthetics & Accessibility: A minimal, readable design with high-contrast elements for better usability.
Key Features and Innovations
- Vote on Bills: Users can actively express their stance on proposed laws.
- Contact Representatives: Direct communication with MPs for feedback and concerns.
- MP Engagement: Future updates will allow MPs to have verified accounts to interact with the public.
- Issue Raising: MPs will be able to post public issues to gauge citizen reactions before submitting them to Parliament.
- No Comment Section: To avoid political toxicity, we removed unmoderated discussions.
- MVP Focus: Instead of launching with all planned features, we are starting with core functions for Canada, then expanding based on feedback.
Restructuring the Foundation
When I took over the design of OpenPolicy, the existing app was in rough shape. The user experience was cluttered, unintuitive, and ultimately rejected by iOS for multiple reasons. My first challenge was to untangle the chaos and bring clarity to the experience. Since there was no PRD (Product Requirements Document), I had to reverse-engineer the app’s core functionalities, understanding what worked, what didn’t, and what needed a complete overhaul. Rather than start from scratch, I focused on refining the navigation, improving hierarchy, and eliminating friction points. I began by mapping out the new user flow, ensuring that every interaction felt logical and purposeful. The goal was simple: Make it effortless for users to stay informed, vote on policies, and contact representatives.
Wireframing and UX Improvements
With the user flow defined, I sketched out low-fidelity wireframes to visualize how users would navigate through the app. Some of the key UX improvements included:
- A cleaner home dashboard that summarizes key updates at a glance.
- Simplified navigation with clear categories (Bills, Debates, Committees) to avoid information overload.
- A seamless voting system that allows users to express their stance on bills without unnecessary steps.
After validating the wireframes, I transitioned into high-fidelity designs in Figma, refining typography, spacing, and accessibility to create a layout that feels modern yet authoritative.
Visual Aesthetics and Interaction Design
Since OpenPolicy is a government-related platform, the design needed to feel professional yet approachable. To achieve this, I focused on:
-
A neutral, minimal color palette to keep the interface clean and distraction-free.
-
Bold, easy-to-read typography for quick scanning of policies and bills.
-
Microinteractions and smooth transitions to make interactions feel intuitive and engaging.
High-Fidelity Designs and Final Touches
Once the UI was polished, I worked closely with developers to ensure pixel-perfect implementation. I provided detailed annotations, interactive prototypes, and component-based designs, making the handoff smooth and efficient. As the MVP rolls out to beta testers, I'll be monitoring feedback and iterating based on real-world usage. This first phase will shape the next version, ensuring that OpenPolicy isn't just functional, but a game-changer in how people engage with their government.
Current Status and Next Steps
With the MVP set to launch, the next steps focus on refining and expanding the platform:
-
Beta Testing: Releasing the app to a small group of users to gather feedback.
-
Iterating Based on Feedback: Using real-world insights to improve the experience.
-
Government Adoption: Engaging with multiple government bodies to establish OpenPolicy as an official platform.