When the first phase of discovery closed, the client and my own team were ready to call it finished, with patient and provider needs fully mapped and ready to hand to build. I saw it differently. We’d captured a snapshot of a relationship that would keep moving the moment we improved it, because better experiences raise expectations rather than settle them. The findings were never the real deliverable. The client needed a way for those findings to keep evolving once my team moved on.

The Lesson I Had to Learn Twice

Patients were navigating dense, regulation-heavy content to make decisions about their own care, while providers were losing hours to authorization friction the system itself created. Neither problem was going to resolve with a single round of research, however thorough, and ours was thorough. It spanned six states, 14 provider organizations, and 92 distinct feature requests and challenges surfaced through interviews and a structured survey. That scale is exactly what made the client’s instinct to call it done so understandable. A dataset that size feels conclusive. It isn’t, when the population it describes keeps changing in response to the very product you’re about to ship.

That’s where I found the real gap. Personalization containers were enabled platform-wide, but only a fraction of the zones on any page were configured to actually surface them. That meant every recommendation coming out of our research was landing on content creators with no map of what was actionable.

I reversed course and had my team build a content-to-zone mapping document instead. It specified which containers were live where, what development still needed to configure, and how content creators should use personalization from that point forward. The cost was polish on the enrichment work itself. What we got back was the one artifact that let the client run the feedback loop themselves, which had been the point since the first engagement.

Whiteboard session with sticky notes mapping provider portal information architecture

The dev-to-content-creator handoff blueprint that closed the container and zone gap.

Where the Evidence Ends

The perspective we were designing under wasn’t abstract. Limited health literacy affects up to 36% of adults, and patients who struggle to parse complex healthcare information consistently see worse outcomes. In that context, plain language and side-by-side plan comparisons weren’t cosmetic choices. They were the difference between a patient understanding their options and guessing at them. Providers navigating fragmented systems report real increases in cognitive load and burnout, which is the same reason workflow alignment mattered on the other side of the platform. Those are field-level findings, not claims about what this specific project measured.

Health literacy sourced: National Assessment of Adult Literacy, National Center for Education Statistics, 2003

The Practice This Project Started

The feedback mechanism should have been contracted into the first engagement, priced and staffed like any other deliverable, not offered as a recommendation and left to survive a delivery schedule on its own. Non-negotiable scope, not aspiration. The rework we absorbed afterward wasn’t bad luck. It was the direct cost of treating governance as optional.

The larger shift was in how I categorize deliverables. A document that lets another team maintain quality after mine has rolled off isn’t a courtesy attached to the design work. It is the design work, the part that determines whether everything else holds up once attention moves elsewhere. I didn’t have that distinction sharp enough to defend on this engagement. I do now, and it’s changed how I scope every engagement since. The feedback and handoff mechanism gets negotiated into the statement of work at the outset, not pitched once the team’s already moved on to the next thing.