<aside> 🌟 Due to an NDA during my time at Apple, deliverables in this case study are limited. Please contact me for a better understanding about my responsibilities.

</aside>

Map editor processes reimagined.

Process

1. Background
2. Design Process
3. Research
4. Prototype
5. Retrospective

Background

In mid- to late-2010s, Apple Maps began using its own data as its source. This meant new workflows needed to be made for map editors to address common issues.

Link to article

<aside> ❓ Problem: HMW address issues regarding missing barriers on new Maps data?

</aside>

<aside> 🤔 Hypothesis: Issues can be addressed via Maps editors

</aside>

<aside> 👤 Users: QA Editors

</aside>

<aside> ⛳ Goal: Build and improve current Maps processes to address Maps issues regarding mislabeled barriers.

</aside>

Design Process

Each project saw its own features go through their own multi-week sprint. Each underwent their own research, development, documentation, and collaboration efforts.

For the pilot “Barriers” project, I ensured editors labeled barriers properly so that cars would not be directed to drive through them.