Hi. I’m Jax.
Senior Product Designer · Enterprise UX · Headless CMS · Brand & Creative Strategy · Bilingual EN/ES
Senior Product Designer · Enterprise UX · Headless CMS · Brand & Creative Strategy · Bilingual EN/ES
The Short Version
320 pages of dense clinical and scientific content for healthcare practitioners. A very particular author. Constant edits right up to publication. The system I built at the start is what made it manageable at the end.
How I Approached It
I start every large document project the same way — before any design work begins I build the template system first. Section templates, heading hierarchies, figure and graphic placement rules, table styles. The upfront investment in structure pays back every time an edit comes in.
On this project that investment was critical. The author had strong opinions about how graphics should be presented and where they should sit on the page relative to the content they supported. Every graphic placement became its own puzzle — fitting the author's vision into a layout that stayed consistent, readable, and printable across 320 pages.
Edits kept coming right up until publication. Because the file was built correctly from the start, those edits were manageable. A poorly built file at that scale would have been chaos.
Why This Matters for Data-Heavy Work
Healthcare content is dense, precise, and unforgiving. Hierarchy isn't aesthetic — it's functional. A practitioner reading clinical content needs to find information quickly and trust that the structure guiding them is consistent throughout. Designing for that level of complexity and precision is the same muscle I use when designing data-heavy enterprise interfaces, internal tools, and content systems where clarity and consistency aren't optional.
