top of page
VISION_2050_LOGO_BLUE.png

Vision 2050 Website Redesign

New Vision Page.jpg

Overview

Team & Role

Create a user-friendly, visually consistent, and accessible website that introduces Vision 2050 and the Orange Code clearly, while consolidating a large volume of complex content into one streamlined, action-oriented page.
Did it in-house, on a tight timeline, and with limited resources.

​

* Vision 2050 is the proposed comprehensive plan for Orange County, FL- USA

* Orange Code is the proposed land use regulations for Orange County, FL- USA

Team: 2 web developers, Public Relations and Outreach Specialist, (Planning Division in-house staff)
 

My Role:

​

  • Led UX strategy, content structure, and visual design

  • Introduced Figma to the team and coached developers in using prototypes

  • Facilitated stakeholder discussions to define branding and messaging

  • Advocated for user-centered language and accessibility

  • Balanced executive needs with realistic development capacity

​

Timeline: 6 weeks

Tools: Figma; Teams; Box

UX Issues

Key UX Issues:

  • No clear branding or visual hierarchy

​

  • Overloaded pages with little scannability​

​​

  • Accessibility concerns (contrast, structure, text)

​

  • Excessive use of technical language

​

  • No guidance for different user types (residents vs. developers vs. staff)

​

  • Confusing navigation and outdated layout

old page.jpg

Challenges

The existing  Vision 2050 Initiative website lacked a clear identity and overwhelmed users with dense, jargon-filled content, inconsistent visual design, and minimal user engagement. Residents, developers, and stakeholders struggled to find relevant information about Vision 2050 and the Orange Code: two major new planning initiatives in Orange County.

​

Additional constraints:

​

  • Limited design/development resources

​

  • No formal UX workflow or toolset in place

​​

  • Very short timeline (6 weeks)

​​

  • Need to introduce new tools (Figma) and agile methods to internal teams

Challenges
Process & Approach

 Process and Approach

1. Tool & Workflow Adoption

​

  • Introduced Figma to the in-house dev team, unfamiliar with modern prototyping tools.

  • Adapted a light agile workflow to accommodate internal process limitations.

  • Focused on speed: moved from rough content to high-fidelity prototypes to secure early buy-in.

​​

2. Branding & Visual Direction

​

  • Facilitated meetings with department leadership to define a visual identity for Vision 2050 and the Orange Code.

  • Created a brand system that reflects county values and improves credibility.

​​

3. Content & Language Redesign

​

  • Audited all existing pages and removed redundant content.

  • Translated complex policy and planning language into clear, user-friendly content.

  • Educated staff on writing for public-facing users and avoiding internal jargon.

​​

4. Information Architecture & Layout

​

  • Reduced four fragmented subpages into one cohesive, scrollable landing page.

  • Organized content by user type (residents, developers, internal) and key questions.

  • Prioritized mobile responsiveness and readability.

​​

5. Accessibility & Technical Workarounds

​

  • Improved contrast, alt text, and headings for WCAG compliance.

  • Used existing PDF documents as a temporary solution for resource pages (due to time/resource limits), with plans to replace them with fully designed subpages once initiatives are adopted.

Results:

  • One unified page with clear structure, brand alignment, and improved engagement
     

  • Simplified, public-facing language and scannable design
     

  • Leadership buy-in achieved early through high-fidelity prototypes
     

  • Internal teams adopted modern UX practices and tools
     

  • Set the foundation for future expansion and full subpage migration

Results
Screenshot 2025-07-28 154550.jpg

Key Learnings

Key Learnings

  • User-centered content can happen even in policy-heavy, resource-limited environments

​​

  • Rapid prototyping is a powerful tool for gaining stakeholder support

​​

  • Introducing new tools (like Figma) and methods (like agile) requires patience and advocacy, but pays off

​​

  • Working within constraints (PDFs, limited tech) is okay, as long as there’s a plan to evolve

bottom of page