Jenise
Absher
I own information architecture and systems structure for complex products — the person other teams call when their own IA falls apart. Nine-plus years in healthcare and clinical software.
Title says designer.
Work says architect.
I translate fragmented, conflicting requirements into unified structures and service blueprints — documentation thorough enough to run vendor and stakeholder conversations without hand-holding. Healthcare and clinical software background, where systems carry real operational consequences.
Three ways I've architected order out of chaos
Untangling the information architecture of [Product Name]
The product had grown section by section with no one owning how it all fit together. Structure had drifted — [duplicate paths, inconsistent nesting, whatever was true] — and other teams were starting to hit the same wall.
Took ownership of the sitemap end-to-end: audited the existing structure, rebuilt it around [the organizing principle you used], and documented it so it wasn't just in my head.
From stalled to shipped in two weeks
A notification initiative touching four internal teams had been stuck for a month — everyone had a different mental model, nobody had mapped the actual end-to-end flow.
Led cross-functional discovery to pull the real workflow out of four teams' heads and onto paper, then built a service blueprint showing exactly how the notification needed to move — who triggers it, who owns each handoff.
Planning capacity before committing to a roadmap
Design, product, and research were operating on different assumptions about designer bandwidth and priorities — leading to friction before any roadmap commitments were even made.
Designed and ran a facilitation bringing all three teams into one room to surface real capacity constraints and dependencies — not just what people wanted to build, but what was actually feasible.