Apple
Two internal tools, one idea: make a huge relational dataset legible from the top all the way down.
As a UX consultant inside Apple’s IS&T org, I designed two intranet applications that shared a spine. Both had to take an enormous, nested dataset — devices across an org chart, or meeting rooms across campuses — and let very different users each drill to exactly the level that mattered to them.
Internal software, at Apple scale.
These weren’t SaaS products — they were intranet web tools built inside Apple’s own IS&T environment and design systems, which I didn’t get to move. Both projects turned out to be the same problem wearing different clothes: a dataset far too large to show all at once, a set of roles who each needed a different slice of it, and a real-world hierarchy the interface had to honor rather than flatten.
Prove your own devices. See your whole team’s.
Employees were bringing their own phones, tablets, and laptops onto the corporate network, and no one could tell whether those devices were safe. I designed the dashboard that let individuals prove their own compliance and gave managers a live view down their entire reporting chain — a tree that survived org charts that fold back on themselves.
The full story — defining what “compliant” even means, and cracking the nested reporting tree:
Read more about Security ComplianceOne platform, from a global view down to one room.
Apple’s facilities team managed meeting-room health and utilization across many buildings on many campuses — with three roles who each needed a different altitude. I designed a single drill-down platform (region → location → building → room → device) so one dataset could serve a facilities manager, a building lead, and check-in staff, each stopping at the depth that was meaningful to them.
The full story — the requirements research, the mobile-on-iPad constraint, and the drill-down that resolved three roles:
Read more about Facilities ManagementStart from the true structure of the data. Then design the drill-down.
Both tools resolved the same way — a hierarchy that mirrored reality (an org chart; a physical campus), and a drill-down that let each role descend to exactly their level and stop. This was my real education in data-driven design, and the instinct I carried into every role after. Structure first; screens follow.
Both engagements ended before measured outcomes were in — Compliance shipped as my contract wrapped; Facilities reached validated requirements and wireframe journeys but didn’t launch. Any figures shown in the Facilities wireframes are illustrative sample data, not results.