Product Documentation Illustrations Refresh

Cross-Functional Alignment

Challenge: Updating technical illustrations meant working with multiple teams—engineering, marketing, and technical documentation—each with different priorities and workflows. Managing feedback and ensuring alignment across these groups introduced complexity and slowed momentum.
Solution: I initiated a centralized feedback process using shared design files, versioning protocols, and scheduled review checkpoints. This approach ensured timely, actionable feedback and kept all teams aligned without overloading any one group. It also built trust and created a repeatable process for future content updates.

Balancing Technical Accuracy with User Clarity

Challenge: Many of the illustrations depicted complex networking configurations. Including every technical detail risked overwhelming users, while oversimplifying could lead to misunderstandings or misuse of the product.
Solution: I worked closely with engineers to deeply understand each feature, then used UX principles like visual hierarchy and progressive disclosure to simplify without losing accuracy. I prioritized clarity and ease of scanning, so users could quickly interpret each visual and understand how it connected to their workflow.

Outdated Visual Standards and Lack of Style Guide

Challenge: The original documentation illustrations were over 15 years old. They varied widely in design, lacked consistency, and didn’t align with Infoblox’s current brand identity. Additionally, there was no existing illustration style guide, which made it difficult to ensure uniformity across product visuals and complicated efforts to scale improvements across other teams.
Solution: I created a new illustration style guide from the ground up. It included updated color palettes, iconography, line weights, layout grids, and usage guidelines—all aligned with Infoblox’s brand standards. This not only guided my refresh of the NIOS 9.0 illustrations but also provided a reusable framework for other teams to ensure consistency across all product documentation moving forward.