Translate highly technical and content-heavy information into a clear experience understandable by non-technical users.
Public infrastructure projects involve long technical reports, environmental assessments, and timelines written for specialists.
• Does this affect my home or community?
• When is the next public meeting?
• How can I submit feedback?
Before the redesign, important information was buried inside document libraries and long pages.
Users often contacted the project team directly because they could not quickly find answers online.
Quickly determine whether the project impacts them
Find meeting dates and locations
Submit questions or feedback
Access reports without feeling overwhelmed
I reorganized the site based on user questions instead of project structure:
About the Project
Cumulative Effects
The Environment & PTE
Timelines, Documents & Reports
Updates & Notices
This reduced cognitive load and allowed users to navigate without understanding technical terminology.
I designed mobile-first wireframes to ensure:
Readable text size
Accessible interaction patterns
Logical reading order
Accessibility considerations included:
High contrast text
Clear headings
Structured content for screen readers
Instead of long, unstructured PDF listings, documents were:
Categorized by relevance
Organized with a side navigation system
Presented in scannable groupings
This improved information hierarchy and reduced the cognitive effort required to locate specific files.
The homepage communicates project status immediately and surfaces participation opportunities. Users can quickly see updates and upcoming engagement events without reading long descriptions.
Content is structured to present essential information first, using plain language summaries before directing users to technical documentation. This layered approach reduces cognitive load while still maintaining transparency.
For users seeking additional clarification, users can easily contact the organization directly through a dedicated contact page, ensuring a clear path from information to action.
All engagement-related content, including meeting schedules, environmental assessment updates, PTE registration details, and contact methods are organized within one dedicated participation hub.
By centralizing participation-related information, users can quickly understand how to get involved and take action without navigating across multiple pages.
Instead of presenting users with long, unstructured lists of PDFs, documents are organized into clear categories with a supporting side navigation menu.
This structure helps visitors quickly understand which documents are relevant to their needs, reducing the effort required to scan and locate specific information.
To support clarity and accessibility, I developed a simple and structured visual system.
The goal was not to create a visually complex interface, but to ensure consistency, readability, and trust.
Typography
Clear heading hierarchy to guide scanning
Generous line spacing for long-form content
Consistent sizing between desktop and mobile
Color & Contrast
High-contrast combinations to support WCAG standards
Limited accent colors to highlight actions (meetings, feedback, updates)
Avoided decorative colors that could distract from content
Components
Standardized document cards
Consistent button styles for participation actions
Structured content blocks to reduce visual clutter
• Improved clarity for non-technical audiences
• Reduced confusion when navigating reports
• Supported accessible public participation
• Provided stakeholders with a reliable communication platform
Designing for public audiences is different from designing for internal stakeholders.
Clarity, trust, and transparency matter more than visual complexity. I learned how to balance both when
Good UX in civic projects is not about aesthetics, it is about helping people understand decisions that affect their lives.