[{"data":1,"prerenderedAt":854},["ShallowReactive",2],{"all-projects":3},[4,227,383],{"id":5,"title":6,"body":7,"caseStudy":24,"client":210,"cover":211,"description":212,"extension":213,"featured":214,"meta":215,"navigation":214,"order":196,"path":216,"publishedAt":217,"role":218,"seo":219,"stem":220,"tags":221,"url":217,"year":225,"__hash__":226},"projects\u002Fprojects\u002Fidaho-lottery-mobile-app.md","Idaho Lottery Mobile App",{"type":8,"value":9,"toc":19},"minimark",[10,15],[11,12,14],"h2",{"id":13},"overview","Overview",[16,17,18],"p",{},"A redesign of a live, in-market lottery application — modernizing the\nexperience for thousands of daily players while laying down a scalable design\nfoundation the team could keep building on.",{"title":20,"searchDepth":21,"depth":21,"links":22},"",2,[23],{"id":13,"depth":21,"text":14},{"meta":25,"hero":42,"sections":50},[26,30,34,38],{"icon":27,"label":28,"value":29},"rh:timeline","Timeline","1–2 Weeks",{"icon":31,"label":32,"value":33},"rh:role","Role","Sole UI\u002FUX Designer",{"icon":35,"label":36,"value":37},"rh:tools","Tools","Adobe XD, Figma",{"icon":39,"label":40,"value":41},"rh:project-type","Project Type","Design Revamp & Migration",{"frame":43,"items":44},"plain",[45],{"src":46,"alt":47,"width":48,"height":49},"\u002Fimages\u002Fprojects\u002Fidaho-lottery\u002Fthumbnail.jpg","Idaho Lottery mobile app — login, home, and account screens",898,465,[51,62,73,87,110,122,140,152,177,182,186,190],{"title":52,"body":53,"figures":55},"Project Summary",[54],"The Idaho Lottery mobile app had been evolving for years before I joined the project. As new features were added over time, the design files became harder to maintain and scale. The product was still managed in Adobe XD, and there wasn't a strong system for reusable components, shared styles, or consistent design patterns. As the sole UI\u002FUX designer, I saw an opportunity to do more than just update screens. I led the migration from Adobe XD to Figma, introduced better design organization, and modernized parts of the experience while preserving the familiarity existing users relied on. Rather than treating this as a full redesign, I focused on making thoughtful improvements that balanced user expectations, development constraints, and long-term maintainability.",[56],{"frame":43,"items":57},[58],{"src":59,"alt":60,"width":48,"height":61},"\u002Fimages\u002Fprojects\u002Fidaho-lottery\u002Fproject-summary.jpg","Migrating the source of truth from Adobe XD to Figma",261,{"title":63,"body":64,"figures":66},"The Problem",[65],"When I first reviewed the project, it was clear that the product had accumulated a fair amount of design debt over the years. The design files lacked structure, repeated elements existed across multiple screens, and there was no reliable system for maintaining consistency as the product grew. Every new update required additional effort because there wasn't a strong foundation supporting the work. At the same time, the application was already live and actively used. Making dramatic changes wasn't an option. Any updates needed to respect existing user habits, fit within development timelines, and remain practical to implement. The challenge wasn't to redesign the app from scratch. It was to modernize and improve the experience while preserving the familiarity users already trusted.",[67],{"frame":43,"items":68},[69],{"src":70,"alt":71,"width":48,"height":72},"\u002Fimages\u002Fprojects\u002Fidaho-lottery\u002Fthe-problem.jpg","Design debt across the existing Adobe XD files and screens",557,{"title":74,"list":75},"Constraints",{"icon":76,"items":77},"material-symbols:event-available-outline-rounded",[78,81,84],{"title":79,"text":80},"Existing User Expectations","Users were already familiar with established navigation patterns and workflows. Any changes needed to feel intuitive without requiring users to relearn the application.",{"title":82,"text":83},"Development Effort","Design decisions needed to account for engineering resources, implementation timelines, and technical feasibility.",{"title":85,"text":86},"Limited Timeline","With a short project timeline, it was important to prioritize improvements that delivered the highest impact while remaining achievable.",{"title":88,"body":89,"list":91,"figures":103},"Migration Strategy",[90],"The migration from Adobe XD to Figma became an opportunity to improve the design foundation of the product. Rather than recreating existing files exactly as they were, I used the process to introduce better structure and consistency. However, a full design system from scratch wasn't realistic in the timeline, so I focused on the foundation that would pay off fastest:",{"items":92},[93,95,97,99,101],{"text":94},"Defined color styles",{"text":96},"Defined typography styles",{"text":98},"Converted repeated patterns into reusable components",{"text":100},"Reorganized files into a clear, navigable structure",{"text":102},"Built a foundation that could be maintained and extended",[104],{"frame":43,"items":105},[106],{"src":107,"alt":108,"width":48,"height":109},"\u002Fimages\u002Fprojects\u002Fidaho-lottery\u002Fmigration-strategy.jpg","Color styles and reusable components in the new Figma library",458,{"title":111,"body":112,"figures":114},"Process & Approach",[113],"A deliberate design decision: why I didn't redesign everything. A complete redesign may have created a more visually dramatic outcome, but it would also have increased development effort, project risk, and user adaptation requirements. Instead, I chose a more strategic approach. I focused on improving areas that would create meaningful value while preserving the patterns users were already familiar with. This allowed the product to evolve without introducing unnecessary friction for users or developers.",[115],{"frame":43,"caption":116,"items":117},"A subtle but impactful update. By elevating the bottom navigation and introducing a floating treatment, I added personality and visual polish without changing how users navigated the app.",[118],{"src":119,"alt":120,"width":48,"height":121},"\u002Fimages\u002Fprojects\u002Fidaho-lottery\u002Fprocess-approach.jpg","Before and after of the home screen's bottom navigation",259,{"title":123,"body":124,"list":126},"Design Improvements",[125],"After reviewing the application's user flows, navigation patterns, and interface components, I identified opportunities to modernize the experience without dramatically changing how users interacted with the product.",{"items":127},[128,130,132,134,136,138],{"text":129},"Refined user flows to remove friction from common paths",{"text":131},"Improved visual hierarchy and readability",{"text":133},"Modernized interface elements and styling",{"text":135},"Updated existing widgets and components",{"text":137},"Designed and integrated new features",{"text":139},"Kept the brand and core patterns intact, so the app still felt like itself",{"title":141,"body":142,"figures":145},"Challenges & Tradeoffs",[143,144],"Balancing modernization and familiarity. One of the most challenging aspects of the project was deciding how much change was appropriate. Introducing modern design patterns could improve usability, but excessive changes risked creating friction for long-time users. I approached this by focusing on incremental improvements that enhanced the experience without requiring users to relearn established workflows.","Designing within development constraints. Because the product was already live, every design decision needed to consider implementation complexity. In some cases, I intentionally prioritized solutions that delivered meaningful improvements while remaining practical for development teams to implement within existing constraints.",[146],{"frame":43,"items":147},[148],{"src":149,"alt":150,"width":48,"height":151},"\u002Fimages\u002Fprojects\u002Fidaho-lottery\u002Fchallenges-tradeoffs.jpg","Before and after of the login, home, and account screens",1002,{"title":153,"body":154,"list":156},"My Contributions",[155],"As the sole UI\u002FUX designer on the project, I:",{"icon":157,"items":158},"material-symbols:workspace-premium-outline-rounded",[159,161,163,165,167,169,171,173,175],{"text":160},"Led the migration from Adobe XD to Figma",{"text":162},"Advocated for and introduced Figma workflows within the organization",{"text":164},"Improved design file organization and maintainability",{"text":166},"Introduced reusable components and design standards",{"text":168},"Modernized the application's interface",{"text":170},"Enhanced existing user flows",{"text":172},"Designed new features and product enhancements",{"text":174},"Collaborated closely with developers to ensure implementation feasibility",{"text":176},"Established a stronger design foundation for future product growth",{"title":178,"body":179},"Outcomes",[180,181],"While business metrics cannot be disclosed, the project delivered meaningful improvements for both the product and the team. The successful migration from Adobe XD to Figma established a more scalable and maintainable design workflow, making it easier to manage updates and ensure consistency across the application. Through the introduction of reusable components, shared styles, and improved file organization, the product gained a stronger design foundation that can better support future enhancements. Alongside these structural improvements, key areas of the user experience were modernized to improve visual consistency, usability, and overall polish while maintaining familiarity for existing users.","Beyond the product itself, the project also contributed to broader team improvements. By advocating for and leading the adoption of Figma, I helped introduce more efficient design workflows and collaboration practices within the organization. The improved design structure and component-based approach created clearer alignment between design and development, reducing future maintenance effort and making it easier for teams to build, update, and scale the product over time.",{"title":183,"body":184},"Reflection & Learnings",[185],"The biggest takeaway: not every redesign should be dramatic. The strongest improvements here were the ones users would barely register. The app just felt a little more intuitive and a little more considered, without anyone having to relearn it. Some of the most valuable design work happens behind the scenes—creating systems, reducing complexity, and improving products in ways that feel natural to users. By balancing modernization, scalability, and implementation constraints, I was able to help evolve the product while preserving the experience users already trusted.",{"title":187,"body":188},"Conclusion",[189],"The Idaho Lottery Mobile App revamp was ultimately about evolution rather than reinvention. By leading the migration to Figma, improving design structure, modernizing key experiences, and working within real-world constraints, I helped create a stronger foundation for the product's continued growth. The project demonstrates my approach to product design: balancing user needs, business goals, technical realities, and long-term scalability to create solutions that are both practical and impactful.",{"title":191,"body":192,"figures":194},"Ongoing Involvement",[193],"My involvement with the product extends beyond the migration project. Today, I am responsible for designing new features and seasonal event experiences, helping shape how the application continues to grow while ensuring each addition feels cohesive, intuitive, and aligned with the overall user experience.",[195,203],{"frame":43,"columns":196,"caption":197,"items":198},1,"Event Promotion Widget. I designed this event widget to support a promotional campaign within the app.",[199],{"src":200,"alt":201,"width":48,"height":202},"\u002Fimages\u002Fprojects\u002Fidaho-lottery\u002Fdrawing.jpg","Event Promotion Widget",172,{"frame":43,"columns":196,"caption":204,"items":205},"Playslip: New Application Feature",[206],{"src":207,"alt":208,"width":48,"height":209},"\u002Fimages\u002Fprojects\u002Fidaho-lottery\u002Fplayslip.jpg","Playslip",416,"Idaho Lottery","\u002Fimages\u002Fprojects\u002Fidaho-lottery\u002Fproject1.mp4","Modernizing a live lottery application while establishing a scalable design foundation","md",true,{"thumbnail":46},"\u002Fprojects\u002Fidaho-lottery-mobile-app",null,"UI\u002FUX Designer",{"title":6,"description":212},"projects\u002Fidaho-lottery-mobile-app",[222,223,224],"Mobile","Design Systems","iOS & Android","2024 - Present","J1Np4SjO9NWRSpyxTb8i45liSgXtrhXYfvpdSpZKDN8",{"id":228,"title":229,"body":230,"caseStudy":240,"client":370,"cover":371,"description":372,"extension":213,"featured":214,"meta":373,"navigation":214,"order":21,"path":374,"publishedAt":375,"role":246,"seo":376,"stem":377,"tags":378,"url":217,"year":381,"__hash__":382},"projects\u002Fprojects\u002Finternal-cms-platform.md","Internal CMS Platform",{"type":8,"value":231,"toc":237},[232,234],[11,233,14],{"id":13},[16,235,236],{},"A greenfield internal content management platform — defining product workflows,\nthe design system, and the front-end architecture from scratch so the team had\na durable foundation to build on.",{"title":20,"searchDepth":21,"depth":21,"links":238},[239],{"id":13,"depth":21,"text":14},{"meta":241,"hero":253,"sections":258},[242,244,247,250],{"icon":76,"label":28,"value":243},"1 Month & 2 Weeks",{"icon":245,"label":32,"value":246},"material-symbols:face-4-outline","UI\u002FUX Designer & Front-End Developer",{"icon":248,"label":36,"value":249},"material-symbols:sdk-outline-rounded","Figma, Vue.js, Storybook, SCSS",{"icon":251,"label":40,"value":252},"material-symbols:tactic-rounded","System Design & Development",{"frame":43,"columns":196,"items":254},[255],{"src":256,"alt":257},"\u002Fimages\u002Fprojects\u002Finternal-cms\u002Fcms-thumbnail.jpg","Internal CMS platform login screen",[259,262,280,292,321,332,351,357,360,364,367],{"title":52,"body":260},[261],"The organization needed a centralized platform to manage and host internal projects without relying on external CMS solutions. Unlike most projects that begin with detailed requirements, this initiative started with only a list of core pages and high-level feature requests. There were no established workflows, user journeys, or functional specifications. This created an opportunity to contribute beyond interface design. I became responsible for uncovering requirements, defining user experiences, creating scalable design patterns, and helping transform a collection of ideas into a cohesive product.",{"title":63,"body":263,"list":265,"outro":278},[264],"The challenge wasn't simply designing screens. The challenge was defining how the platform should work before design and development could begin. Without established workflows, several questions needed to be answered:",{"icon":266,"items":267},"material-symbols:asterisk-rounded",[268,270,272,274,276],{"text":269},"How should users navigate between projects?",{"text":271},"What content structures are needed?",{"text":273},"What actions should be available across modules?",{"text":275},"How should future features scale within the platform?",{"text":277},"What system behaviors are required for edge cases?",[279],"Before solving usability problems, I first needed to identify them.",{"title":74,"list":281},{"icon":76,"items":282},[283,286,289],{"title":284,"text":285},"Limited Product Documentation","The project began without detailed specifications, user journeys, or established workflows. Much of the discovery work needed to happen alongside design and development.",{"title":287,"text":288},"Multiple Responsibilities","As the sole designer and front-end developer, I was responsible for product thinking, UX, UI, design systems, and implementation simultaneously.",{"title":290,"text":291},"Evolving Requirements","As stakeholders gained a better understanding of the product, requirements continued to evolve, requiring solutions that could adapt without sacrificing consistency.",{"title":293,"body":294,"list":296,"outro":312,"figures":314},"Building a Design System",[295],"One of the most important decisions was investing early in a design system. Although creating a design system requires additional upfront effort, it became the foundation that supported the entire platform. The design system included:",{"items":297},[298,300,302,304,306,308,310],{"text":299},"Color foundations",{"text":301},"Typography styles",{"text":303},"Spacing standards",{"text":305},"Reusable components",{"text":307},"Form patterns",{"text":309},"Layout structures",{"text":311},"Design documentation",[313],"As the platform expanded, the system significantly improved consistency and efficiency.",[315],{"frame":43,"columns":196,"caption":316,"items":317},"Design system foundations documented for design and engineering.",[318],{"src":319,"alt":320},"\u002Fimages\u002Fprojects\u002Finternal-cms\u002Fds-doc-1.jpg","Design system documentation — colour and typography",{"title":111,"body":322,"figures":326},[323,324,325],"Designing the product before designing the interface. One of the most important realizations early in the project was that the biggest challenge wasn't visual design—it was product definition. Before creating screens, I spent time understanding how features related to one another, identifying workflow dependencies, and uncovering missing requirements that had not yet been documented. Instead of treating design as a downstream activity, I approached the project from a product perspective, helping define how the platform should work before determining how it should look.","Creating structure through flows. User flows became one of the most valuable tools throughout the project. By mapping workflows and feature relationships, I was able to identify gaps, edge cases, and opportunities to simplify complex administrative processes before development began.","Building systems early. Because CMS platforms naturally grow over time, I invested early in creating a scalable design system. This allowed new features to be designed and implemented more efficiently while maintaining consistency across the platform.",[327],{"frame":43,"columns":196,"items":328},[329],{"src":330,"alt":331},"\u002Fimages\u002Fprojects\u002Finternal-cms\u002Fflow-pages.jpg","Content pages module",{"title":153,"body":333,"list":335},[334],"As the sole UI\u002FUX Designer and Front-End Developer, I:",{"icon":157,"items":336},[337,339,341,343,345,347,349],{"text":338},"Designed the platform from scratch",{"text":340},"Defined user flows & feature requirements",{"text":342},"Created & maintained the design system",{"text":344},"Designed a responsive web application",{"text":346},"Implemented interfaces using Vue.js",{"text":348},"Managed component documentation through Storybook",{"text":350},"Collaborated with stakeholders to translate business requirements into product solutions",{"title":352,"body":353},"Challenges & Trade-offs",[354,355,356],"Starting without detailed requirements. Working within project timelines meant balancing thoughtful problem-solving with the need to move quickly. Rather than exploring every possible direction, I focused on defining strong foundations and iterating as requirements matured.","Designing a large CMS solo. CMS platforms are inherently broad—many screens, states, workflows, and permissions. Carrying discovery, UX, UI, component creation, documentation, and development support independently meant constantly balancing depth against deadlines without letting quality or consistency slip.","Designing without direct user observation. Without direct access to user behavior, decisions were informed through research, CMS best practices, stakeholder collaboration, and continuous evaluation of workflow risks.",{"title":178,"body":358},[359],"While business metrics cannot be disclosed, the project established a strong foundation for the platform's continued growth. The creation of a design system improved consistency across the product while supporting faster feature development. Reusable components and shared patterns strengthened alignment between design and development, reducing duplication and improving maintainability. Beyond interface design, the project transformed a collection of loosely defined requirements into a structured product experience, providing a scalable framework for future enhancements and expansion.",{"title":183,"body":361},[362,363],"The biggest lesson from this project was that successful product design often begins long before screens are created. Requirements are rarely complete. A large part of the work was actively identifying gaps, asking the right questions, and anticipating future needs rather than waiting for a finished brief.","It also deepened how I think about design systems—not as a collection of UI components, but as a shared foundation that connects design and development. Working across UX, UI, QA, and front-end strengthened my ability to think beyond individual screens and treat the product as a complete system. Most of all, it reinforced the value of ownership, adaptability, and proactive problem-solving when building a product from the ground up.",{"title":187,"body":365},[366],"The Internal CMS Platform was more than a design project—it was an opportunity to help define a product from the ground up. By combining product thinking, UX design, design systems, and front-end development, I helped transform broad business requirements into a scalable platform foundation. The experience strengthened my ability to navigate ambiguity, create systems that scale, and contribute across the full product development lifecycle.",{"title":191,"body":368},[369],"My involvement with the platform continues today. As new business requirements emerge, I remain responsible for designing new features, refining existing workflows, expanding the design system, and supporting front-end implementation.","Internal","\u002Fimages\u002Fprojects\u002Finternal-cms\u002Fcms.mp4","Defining product workflows, design systems, and front-end architecture from scratch",{},"\u002Fprojects\u002Finternal-cms-platform","2023-09-01",{"title":229,"description":372},"projects\u002Finternal-cms-platform",[379,223,380],"Web App","Front-End","2025 - Present","y3eF0-2szdF9R0M0gOSj030I0XnfhmrXh9vW_6Qh2xY",{"id":384,"title":385,"body":386,"caseStudy":396,"client":840,"cover":841,"description":842,"extension":213,"featured":843,"meta":844,"navigation":214,"order":845,"path":846,"publishedAt":847,"role":246,"seo":848,"stem":849,"tags":850,"url":217,"year":381,"__hash__":853},"projects\u002Fprojects\u002Fcourt-websites.md","Supreme Court & District Court Website",{"type":8,"value":387,"toc":393},[388,390],[11,389,14],{"id":13},[16,391,392],{},"Redesigning the Idaho Supreme Court and District Court websites — modernizing a\nlarge public-information ecosystem with a clearer information architecture and a\nmore accessible experience across desktop and mobile.",{"title":20,"searchDepth":21,"depth":21,"links":394},[395],{"id":13,"depth":21,"text":14},{"meta":397,"hero":405,"sections":409},[398,400,401,403],{"icon":76,"label":28,"value":399},"Ongoing",{"icon":245,"label":32,"value":246},{"icon":248,"label":36,"value":402},"Figma, Nuxt.js",{"icon":251,"label":40,"value":404},"Website Design & Development",{"frame":43,"columns":196,"items":406},[407],{"src":408,"alt":257},"\u002Fimages\u002Fprojects\u002Fcourt-sites\u002Fcourt-thumbnail.jpg",[410,432,505,556,704,745,765,790,812,831,835],{"title":52,"body":411,"list":416,"outro":430},[412,413,414,415],"The Supreme Court website served as a central public resource for court services, legal information, announcements, forms, and official documents. Over the years, the platform had expanded significantly, resulting in increasingly complex navigation, fragmented information structures, and inconsistent user experiences across devices.","The goal of the redesign was not only to modernize the visual experience, but more importantly, to improve how users discover, understand, and navigate large volumes of court-related information.","In addition to redesigning the Supreme Court website, I was also responsible for designing the District Court websites that existed within the same ecosystem while helping maintain consistency across the broader platform experience.","This project focused heavily on:",{"items":417},[418,420,422,424,426,428],{"text":419},"Information architecture",{"text":421},"Navigation restructuring",{"text":423},"Content discoverability",{"text":425},"Responsive usability",{"text":427},"Accessibility-minded design",{"text":429},"Scalable front-end implementation",[431],"Rather than designing purely for aesthetics, the outcome aimed to create a more intentional experience for the different types of users interacting with the platform.",{"title":63,"body":433,"subsections":435,"figures":498},[434],"The existing website had evolved over many years without a unified UX strategy, resulting in a platform that felt difficult to navigate and overwhelming for users unfamiliar with court systems.",[436,456,493],{"title":437,"blocks":438},"Navigation Complexity",[439,441,454],{"text":440},"The navigation structure had become increasingly difficult to use due to:",{"list":442},{"icon":266,"items":443},[444,446,448,450,452],{"text":445},"Crowded menu systems",{"text":447},"Overlapping categories",{"text":449},"Inconsistent hierarchy",{"text":451},"Too many competing entry points",{"text":453},"Difficult-to-find resources",{"text":455},"Users often needed to navigate through several pages before locating important information or documents.",{"title":457,"blocks":458},"Content Discovery Challenges",[459,461,474,476,491],{"text":460},"Court websites naturally contain large amounts of content intended for a wide range of audiences, including:",{"list":462},{"icon":266,"items":463},[464,466,468,470,472],{"text":465},"Legal professionals",{"text":467},"Government employees",{"text":469},"Citizens",{"text":471},"First-time visitors",{"text":473},"Users unfamiliar with legal terminology",{"text":475},"One of the biggest usability concerns was helping users quickly locate:",{"list":477},{"icon":266,"items":478},[479,481,483,485,487,489],{"text":480},"Documents",{"text":482},"Court information",{"text":484},"Forms",{"text":486},"Contacts",{"text":488},"Services",{"text":490},"Court-related resources",{"text":492},"The redesign aimed to simplify how users searched, browsed, and understood information throughout the ecosystem.",{"title":494,"blocks":495},"Outdated Experience",[496],{"text":497},"The existing experience also reflected older design standards and was not fully optimized across modern devices, leading to inconsistencies between desktop and mobile experiences.",[499],{"frame":43,"columns":196,"caption":500,"items":501},"Planning the website navigation stracture",[502],{"src":503,"alt":504},"\u002Fimages\u002Fprojects\u002Fcourt-sites\u002Fplanning.jpg","navigation planning",{"title":74,"body":506,"subsections":508},[507],"This project involved several real-world constraints that significantly influenced design decisions.",[509,529,551],{"title":510,"blocks":511},"Content-Heavy Environment",[512,514,516,518],{"text":513},"Because the platform contained large amounts of text-based information, the design needed to prioritize readability, clarity, and structure over heavy visual styling.",{"text":515},"I intentionally avoided overly graphic-heavy layouts and instead focused on creating interfaces that helped users process information more efficiently.",{"text":517},"The challenge was finding the right balance between:",{"list":519},{"items":520},[521,523,525,527],{"text":522},"Visual modernization",{"text":524},"Content clarity",{"text":526},"Accessibility",{"text":528},"Usability",{"title":530,"blocks":531},"Frequent Content Changes",[532,534,536,538,540],{"text":533},"Court-related information changes frequently, requiring the website to remain flexible and maintainable over time.",{"text":535},"To support this, I designed reusable and scalable components that could easily adapt to content updates without requiring major redesign efforts.",{"text":537},"This was especially important because revision timelines and implementation windows were often limited.",{"text":539},"The goal was to ensure that:",{"list":541},{"items":542},[543,545,547,549],{"text":544},"Future updates remained efficient",{"text":546},"Components stayed consistent",{"text":548},"Design revisions were not cumbersome",{"text":550},"The system could scale across multiple court websites",{"title":552,"blocks":553},"Balancing Consistency and Flexibility",[554],{"text":555},"Since the project included both Supreme Court and District Court websites, I needed to create a system that felt unified while still allowing each site to maintain its own structure and identity.",{"title":111,"subsections":557,"figures":697},[558,584,608,639,661,677],{"title":559,"blocks":560},"Website Audit & Analysis",[561,563,565,582],{"text":562},"Before proposing solutions, I conducted a comprehensive review of the existing experience.",{"text":564},"I analyzed:",{"list":566},{"items":567},[568,570,572,574,576,578,580],{"text":569},"Navigation structures",{"text":571},"Content organization",{"text":573},"User pathways",{"text":575},"Existing page hierarchy",{"text":577},"Searchability of information",{"text":579},"Mobile responsiveness",{"text":581},"Common usability pain points",{"text":583},"This helped identify where users were likely experiencing friction and confusion.",{"title":585,"blocks":586},"Information Architecture Strategy",[587,589,591,593,606],{"text":588},"One of the most significant parts of the project was restructuring how information was organized.",{"text":590},"Rather than immediately redesigning pages visually, I focused first on improving the underlying structure of the platform.",{"text":592},"Key objectives included:",{"list":594},{"items":595},[596,598,600,602,604],{"text":597},"Simplifying navigation",{"text":599},"Reducing cognitive load",{"text":601},"Improving discoverability",{"text":603},"Creating clearer content relationships",{"text":605},"Supporting both expert and non-expert users",{"text":607},"The goal was to design information around how users naturally search for resources rather than how the organization internally categorized them.",{"title":609,"blocks":610},"Wireframes & User Flows",[611,613,615,626,628],{"text":612},"Because navigation restructuring represented a major shift from the existing experience, wireframes became an important communication and validation tool.",{"text":614},"Wireframes helped:",{"list":616},{"items":617},[618,620,622,624],{"text":619},"Explore structural concepts quickly",{"text":621},"Compare navigation approaches",{"text":623},"Validate user journeys",{"text":625},"Align stakeholders around proposed changes",{"text":627},"Key flows focused on:",{"list":629},{"items":630},[631,633,635,637],{"text":632},"Document discovery",{"text":634},"Court resource navigation",{"text":636},"Public information access",{"text":638},"Search experiences",{"title":640,"blocks":641},"Iterative Design & Prototyping",[642,644,646,659],{"text":643},"The project involved multiple rounds of iteration and refinement.",{"text":645},"Interactive prototypes were used to evaluate:",{"list":647},{"items":648},[649,651,653,655,657],{"text":650},"Navigation hierarchy",{"text":652},"Page layouts",{"text":654},"Information prioritization",{"text":656},"Responsive behavior",{"text":658},"Content presentation",{"text":660},"This iterative process allowed the experience to evolve while balancing user needs, technical constraints, and stakeholder feedback.",{"title":662,"blocks":663},"Responsive Design",[664,666,675],{"text":665},"The redesigned experience was built to support:",{"list":667},{"items":668},[669,671,673],{"text":670},"Desktop",{"text":672},"Tablet",{"text":674},"Mobile devices",{"text":676},"Special attention was given to maintaining readability, navigation clarity, and accessibility regardless of screen size.",{"title":678,"blocks":679},"Front-End Development",[680,682,684,695],{"text":681},"In addition to design responsibilities, I also implemented front-end pages using Nuxt.js.",{"text":683},"This included:",{"list":685},{"items":686},[687,689,691,693],{"text":688},"Translating designs into production-ready interfaces",{"text":690},"Building responsive layouts",{"text":692},"Maintaining consistency across pages",{"text":694},"Supporting reusable implementation patterns",{"text":696},"Working across both design and development allowed me to ensure the final implementation closely aligned with the intended user experience.",[698],{"frame":43,"columns":196,"caption":699,"items":700},"Website Wireframe",[701],{"src":702,"alt":703},"\u002Fimages\u002Fprojects\u002Fcourt-sites\u002Fwireframe.jpg","Wireframe",{"title":123,"subsections":705},[706,713,729,736],{"title":707,"blocks":708},"Improved Navigation Structure",[709,711],{"text":710},"The redesigned navigation introduced a clearer hierarchy that made it easier for users to understand where information existed within the platform.",{"text":712},"Content was reorganized into more meaningful categories, reducing the effort required to locate resources.",{"title":714,"blocks":715},"Better Content Organization",[716,718,720],{"text":717},"Pages and resources were grouped more intentionally based on user needs and content relationships.",{"text":719},"This helped improve:",{"list":721},{"items":722},[723,725,727],{"text":724},"Information discoverability",{"text":726},"Scanability",{"text":728},"Overall usability",{"title":730,"blocks":731},"Enhanced Search Experience",[732,734],{"text":733},"One of the most impactful improvements was enhancing how users locate important documents, people, and court-related information.",{"text":735},"The redesign addressed previous usability concerns around search and discovery, making critical resources easier to access without excessive navigation.",{"title":737,"blocks":738},"More Accessible Experience",[739,741,743],{"text":740},"Legal terminology and court systems can feel intimidating for many users.",{"text":742},"Where appropriate, content structures and interface labels were designed to feel more approachable and easier to understand for non-legal audiences.",{"text":744},"The goal was to create a platform that felt accessible and welcoming to a broader range of users.",{"title":141,"body":746,"list":749,"outro":761},[747,748],"One of the biggest challenges was designing within a highly content-driven environment while avoiding interfaces that felt visually overwhelming.","Instead of relying heavily on graphics or decorative elements, I focused on:",{"items":750},[751,753,755,757,759],{"text":752},"Information clarity",{"text":754},"Layout structure",{"text":756},"Typography hierarchy",{"text":758},"Navigation simplicity",{"text":760},"Content readability",[762,763,764],"Another important tradeoff involved balancing scalability with customization.","The design system needed to remain flexible enough to support future updates and multiple court websites while still maintaining a cohesive ecosystem experience.","I also had to consider development efficiency by designing reusable components that minimized implementation overhead and simplified future revisions.",{"title":153,"list":766},{"icon":157,"items":767},[768,770,772,774,776,778,780,782,784,786,788],{"text":769},"Led the redesign of the Supreme Court website",{"text":771},"Designed the District Court website ecosystem",{"text":773},"Conducted UX audits and usability analysis",{"text":775},"Restructured information architecture",{"text":777},"Redesigned navigation systems and user flows",{"text":779},"Created wireframes and prototypes",{"text":781},"Designed responsive experiences across devices",{"text":783},"Improved document and information discoverability",{"text":785},"Enhanced search experiences",{"text":787},"Developed front-end pages using Nuxt.js",{"text":789},"Created reusable and scalable UI patterns",{"title":178,"body":791,"list":794,"outro":810},[792,793],"Although formal metrics cannot be publicly shared, the redesign successfully addressed several long-standing usability concerns across the platform.","Key improvements included:",{"items":795},[796,798,800,802,804,806,808],{"text":797},"Simplified navigation",{"text":799},"Improved information organization",{"text":801},"Easier discovery of important documents and resources",{"text":803},"Clearer user pathways",{"text":805},"Better accessibility for non-legal audiences",{"text":807},"More consistent responsive experiences",{"text":809},"Improved search and browsing workflows",[811],"The outcome was not simply a more modern-looking website, but a more intentional experience designed around the needs of different user groups interacting with court-related information.",{"title":183,"body":813,"list":819,"outro":829},[814,815,816,817,818],"This project reinforced the importance of designing for clarity, accessibility, and usability within complex information ecosystems.","Unlike many consumer-facing products, court websites serve users with very different levels of expertise and familiarity with legal systems. Designing for this audience required a strong focus on predictability, comprehension, and confidence.","One of the biggest lessons from this project was understanding how impactful information architecture can be on the overall user experience.","Improving how information is structured and discovered often creates more value than visual redesign alone.","The project also strengthened my ability to:",{"items":820},[821,823,825,827],{"text":822},"Design scalable systems",{"text":824},"Balance stakeholder and technical constraints",{"text":826},"Maintain consistency across large website ecosystems",{"text":828},"Build reusable patterns that support long-term maintainability",[830],"Most importantly, it reinforced that successful UX is not always about creating something visually bold. Sometimes the best solution is one that feels calm, intuitive, and effortless to navigate.",{"title":187,"body":832},[833,834],"This project demonstrates my ability to lead large-scale UX initiatives that extend beyond interface design into information architecture, navigation strategy, content organization, responsive usability, and front-end implementation.","By redesigning both the Supreme Court and District Court websites, I helped transform a complex public information platform into a more accessible and user-centered experience while maintaining the clarity and reliability expected from government services.",{"title":191,"body":836},[837,838,839],"I am currently continuing work within the District Court website ecosystem.","One ongoing challenge is maintaining a cohesive experience that still feels connected to the Supreme Court platform while allowing individual District Court websites to support their own unique content structures and operational needs.","This ongoing involvement continues to strengthen the scalability of the overall design system and reinforces the importance of consistency across large digital ecosystems.","Idaho Courts","\u002Fimages\u002Fprojects\u002Fcourt-sites\u002Fthumbnail.mp4","Transforming a complex public information ecosystem into a more accessible digital experience",false,{},3,"\u002Fprojects\u002Fcourt-websites","2025-01-01",{"title":385,"description":842},"projects\u002Fcourt-websites",[851,852,380],"Website","Prototype","H8SdXpSnOax9mrLj0t1dWyElHqhI6QQK2fJZ257YFAU",1781719491028]