I led stakeholder conversations, UX research, analytics and heat-map review, information architecture, UX writing, interface design, mobile-first front-end development, WordPress implementation, SEO, launch support, and behavior review. The goal was to turn a cluttered information site into a clear statewide resource for understanding opioid risk, finding naloxone, getting treatment, and helping someone else.
See the decisions behind the transformation. Urgent paths, mobile behavior, wireframes, build, SEO, and iteration.
01 People
Know the Dangers began with a narrower focus on synthetic drugs. As the opioid crisis changed, the site accumulated more facts, stories, resources, warnings, and campaign content without rebuilding the experience around the questions people were now bringing to it. The redesign had to turn that content into a usable path, especially for someone arriving worried, overwhelmed, or on a phone.
This was not a conventional marketing problem. A visitor could be trying to recognize an overdose, find naloxone, understand fentanyl, help a family member, locate treatment, read a recovery story, or share accurate information with a community. The site had to support those needs without sounding cold, alarmist, or difficult to trust.
I led the UX, UI, and front-end work from analysis through launch. I reviewed analytics, traffic paths, device use, and heatmaps; talked with stakeholders and people close to the campaign; mapped the content and navigation problems; and presented a UX direction that put urgent actions and plain-language choices ahead of the old site structure.
I stayed inside the build. I created the information architecture, wireframes, interface system, responsive behavior, UX copy, WordPress implementation, SEO foundation, accessibility and performance work, tracking, QA, and post-launch behavior review. That kept the experience connected from the first problem to the live page.
The question behind the redesign
Can someone under pressure recognize the right action before the website asks them to read everything else?
The existing site already had real traffic and important content. The work was to understand which paths people used, where the hierarchy failed, what received attention, and what disappeared as the page continued.
I reviewed entry pages, traffic sources, device use, high-volume content, exits, page movement, and the routes people took toward help, naloxone, treatment, resources, and recovery content.
I studied where people clicked, what drew attention in the header and first screen, how far they moved through long pages, and where important sections lost visibility.
I worked with campaign stakeholders to understand the public-health priorities, the language that had to remain accurate, the resources that mattered most, and the audiences the site needed to serve.
I mapped outdated emphasis, duplicate ideas, weak search entry points, buried resource content, unclear labels, and the pages that could answer common questions more directly.
They did not arrive with the same knowledge or emotional state. The shared interface needed to give each person a clear route without splitting the campaign into disconnected websites.
May be frightened, scanning quickly, and uncertain whether the symptoms they see are an overdose.
Needs to know: Is this an emergency, and what do I do now?
Needs plain guidance, naloxone access, signs to watch for, and support without judgment or medical jargon.
Needs to know: How can I help without making this worse?
May need reassurance, clear service routes, recovery stories, and a next step that feels possible rather than abstract.
Needs to know: Where can I start, and will someone meet me there?
Needs accurate facts, shareable resources, culturally relevant material, and a way to point others toward help.
Needs to know: What can I trust, use, and share?
02 Structure
The old experience exposed sections of the campaign. The new structure needed to expose useful decisions. I reorganized the site around immediate help, facts, signs and risks, naloxone, treatment and recovery, personal stories, and resources, then connected those paths instead of forcing visitors back through the homepage.
Keep the emergency instruction visible before any campaign message or educational content.
Use direct paths for facts, signs, risks, fentanyl, overdose, and changing drug conditions.
Explain what it is, how it works, and where to find it without making people search several pages.
Connect treatment, recovery, helping others, and local resources to a visible next move.
Make stories, facts, videos, and community resources easy to understand and pass along.
The rules were deliberately simple. They gave the team a way to judge every page, section, label, and call to action against the conditions in which people would actually use the site.
Emergency guidance, naloxone, and help could not compete with a campaign introduction. The first screen needed to answer the highest-risk question first.
Labels described the question or action in the visitor’s words. More clinical detail remained available after someone knew which path to take.
With 83.8% of the audience on mobile, section order, tap targets, reading length, menus, forms, maps, and CTA placement were product decisions, not responsive cleanup.
Important actions appeared again when the surrounding content created new intent. The system repeated the route, not the entire message.
The redesign did not simply modernize the campaign. It changed the site from a collection of messages into a set of connected public-health paths.
I kept the campaign recognizable while changing the hierarchy, content order, navigation, audience routes, mobile behavior, and relationship between information and action.
03 Build
I did not hand off a visual direction and hope the live site kept the logic. I carried the work through wireframes, interface design, content structure, WordPress development, responsive behavior, accessibility, SEO, analytics, and QA so the decisions survived implementation.
Analytics, heatmaps, traffic sources, device use, and stakeholder input established where the current experience was helping and where it was hiding the next move.
I grouped content around urgent questions, common risks, naloxone, treatment, recovery, stories, audiences, and resources instead of preserving the old campaign structure.
Low-fidelity flows established the emergency layer, hero message, primary paths, audience choices, supporting proof, and repeated actions before visual styling.
The interface balanced urgency and hope with high contrast, readable type, reusable cards, strong buttons, human imagery, and consistent content patterns.
I translated the system into responsive HTML, CSS, JavaScript, and WordPress components, including resource paths, the naloxone finder experience, forms, and editorial patterns.
I reviewed post-launch traffic, mobile use, page engagement, scroll behavior, CTA activity, forms, and search growth to identify where the redesign was working and what still needed attention.
Representative reconstruction
I rebuilt the original planning logic in the same visual wireframe system used across these case studies. It shows the decisions that mattered: emergency guidance first, one clear primary message, direct paths to help and learning, audience recognition, supporting content, and a final action.
The question was never “what can we fit on the homepage?” It was “what does this person need before they can safely choose the next step?”
The experience needed to remain consistent as new drug information, campaign content, stories, resources, and public-health priorities changed. I built patterns that gave editors room to work without rebuilding the hierarchy every time.
Facts, signs, risks, naloxone, treatment, resources, and stories used direct labels and predictable page relationships.
Overdose guidance and access to help stayed visible without allowing the alert treatment to overwhelm every other page.
Audience cards, resource groups, stories, educational modules, warnings, videos, and CTAs used shared rules instead of one-off page layouts.
The CMS supported updates to fast-changing content while preserving spacing, hierarchy, accessibility, and responsive behavior.
Semantic headings, readable contrast, mobile performance, metadata, crawlable resource pages, keyboard support, and alt text were built into the system.
Tracking, heatmaps, responsive testing, forms, maps, CTA paths, scroll behavior, and post-launch analytics made the redesign inspectable.
Design into code
Because I designed and developed the interface, I could protect the urgency, reading order, tap behavior, and content relationships while solving the implementation details that often weaken a redesign after handoff.
Mobile path
With 83.8% of visitors on mobile, the experience had to work in short reading windows and stressful moments. I simplified the header, increased tap space, shortened openings, moved urgent routes forward, stacked audience choices clearly, and kept calls to action near the content that explained them.
04 Behavior
I used behavior data to test the hierarchy, not to decorate the presentation. The heatmap showed concentrated attention around the emergency strip, navigation, search, and “Get Help Now,” followed by strong interaction with the first set of content choices. Scroll depth thinned as the page moved into longer sections, which reinforced the need to place high-priority routes earlier and repeat them with context.
Emergency guidance, search, navigation, and the help action drew attention before deeper campaign content.
The first clear content choices created more useful movement than a long introductory message alone.
Important resources placed too far down the page could not depend on every visitor reaching them.
High-value actions returned after relevant education so people could act when the content created readiness.
The heatmap helped separate visual preference from observed behavior. It showed which utility controls earned attention and where the information hierarchy needed to carry more of the work.
I used these patterns to strengthen first-screen choices, maintain the urgent action layer, place resource routes earlier, and judge where repeated CTAs were useful instead of redundant.
A public-health page can be accurate and still fail if the person cannot recognize the next move quickly enough.
The design had to reduce the distance between concern and action without stripping away the facts people needed to trust that action.
These were not one-time launch fixes. They became working rules for evaluating new pages, campaigns, drug information, stories, and resource updates as the site continued to grow.
Emergency instructions and help actions remain visible, readable, and distinct from campaign messaging.
Page views matter less than whether people reach naloxone, treatment, forms, maps, and the resources that answer the original question.
New desktop sections do not automatically earn the same order or length on a phone.
Growing entry pages show which questions people are bringing from outside the site and where clearer related paths can help them continue.
05 Results
The result was not caused by one screen or one channel. UX, mobile usability, SEO, content, social and cross-network campaigns, stronger resource pages, and clearer calls to action worked together. The project metrics showed large audience growth, a heavily mobile user base, deeper use of priority content, and more movement toward recovery-related actions.
+2,681.65%
Reported user growthThe campaign and redesigned experience reached a dramatically larger audience during the measured period.
7,621
New usersOptimized social and cross-network efforts brought thousands of new people into the public-health resource.
83.8%
Mobile usersThe audience confirmed why mobile order, speed, tap behavior, and short reading windows had to lead the design.
+240.79%
Resource page viewsOne of the highest-priority information paths saw a substantial increase in use after the redesign and campaign work.
Priority resource pages gained visibility, mobile visitors received an experience designed for how they actually arrived, deeper sections earned more engagement, and refined actions such as “Get Help Now” supported more form activity on recovery-related content.
Performance figures are based on the analytics summary supplied for this case study. They reflect the measured redesign and campaign period and should be read as directional outcomes, not a controlled experiment isolating one design change.
The metrics supported the main design choices while also keeping the interpretation honest. A public-health website grows through the interaction of content, search, campaigns, mobile usability, and the clarity of the action once someone arrives.
The device mix made it clear that the mobile hierarchy was the primary experience, not a secondary adaptation.
The lift on opioid resource content showed that navigation, search entry, campaign traffic, and page hierarchy were bringing people into more useful information.
Campaign growth would have been wasted if the landing experience still hid help, naloxone, treatment, and resources after the click.
Analytics and heatmaps gave the team a way to keep evaluating new content and changing public-health needs after launch.
People could recognize emergency guidance, help, naloxone, treatment, and resources without decoding the campaign structure.
The site was designed around the device most people used, with clearer order, stronger tap behavior, and less friction.
SEO, campaigns, content, and UX worked together to bring a larger audience into priority public-health information.
Heatmaps, analytics, forms, CTA tracking, and page behavior gave the team a clearer basis for future changes.
My contribution
This was a full UX, content, interface, development, search, and measurement project. I connected the research and public-health goals to the live experience instead of treating each phase as a separate handoff.
The finished experience connected urgent guidance, opioid education, naloxone, treatment, recovery, stories, and community resources inside a mobile-first system that could keep changing with the crisis. That meant more than a new visual design. It meant tying stakeholder needs, analytics, heatmaps, information architecture, writing, SEO, front-end development, accessibility, and post-launch measurement to the same question: what does this person need now?