Case Study
Apple Maps Survey Creation Tool
Designing an internal survey creation experience that helped Apple’s Maps QA team move from fragile third-party workflows to faster, more structured, and more reliable survey authoring.
Apple Maps Survey Creation Tool
Internal QA Tooling
Apple’s Maps QA team relied on third-party survey tools to validate geo updates, identify map bugs, and capture structured feedback from real-world review workflows. Those tools were workable, but they were never designed for the logic, metadata, and quality controls required by Apple’s internal QA process.
I led the end-to-end UX design of a custom internal survey creation tool that made survey setup faster, reduced authoring errors, improved data quality, and gave QA teams a more reliable path from project creation to survey launch to project-level monitoring.
Background
Replacing a generic survey workflow with one built for Apple Maps QA.
For the Maps team, surveys were more than simple forms. They were part of a larger QA validation workflow used to review geo updates, evaluate tasks, and capture structured findings that could be routed into downstream systems. That meant the authoring experience needed to support more than content entry. It needed to support logic, preview, metadata structure, and launch control.
The challenge was not just replacing a third-party tool. It was creating an internal workflow tailored to Apple Maps QA while establishing stronger UX foundations for future internal tooling.
So how might we design a survey creation experience that helps Apple Maps QA teams work faster, reduce setup errors, and launch more reliable surveys without forcing them through generic tools?
Problem
The existing workflow created friction at nearly every stage.
Existing project setup and upload flows revealed inefficiencies in survey creation, structure, and validation.
- Third-party tools were not designed for Apple’s QA logic or data requirements
- Manual survey creation was slow, repetitive, and prone to setup mistakes
- Validation and preview controls were limited, making broken survey paths easier to publish
- Metadata and tagging gaps weakened bug triage, reporting, and downstream QA workflows
- No reusable internal patterns existed to support consistency or future scale
The problem was not basic capability. Teams could create surveys. The problem was that the workflow lacked the fit, structure, and quality controls needed for a complex internal QA environment.
Discovery
Understanding how QA teams actually built, reviewed, and launched surveys.
Survey Creation Tools
I worked with QA engineers and partner stakeholders to understand how surveys moved from raw data and project setup into reviewable, launch-ready experiences. The goal was to identify not just where the process was slow, but where it was fragile.
- Interviewed QA engineers to understand end-to-end authoring workflows
- Audited exported surveys and setup files to identify recurring pain points
- Observed workarounds that increased the risk of setup errors and inconsistent logic
- Mapped metadata tagging gaps affecting Radar and related QA systems
- Reviewed where preview, validation, and launch configuration needed stronger support
The key insight was that survey quality was being determined too late in the workflow. A better product had to bring structure, validation, and review confidence earlier into the creation process.
Strategy
Designing a purpose-built internal authoring workflow around Apple Maps QA needs.
Rather than forcing QA teams to adapt to a generic survey builder, the strategy focused on creating a lightweight internal workflow tailored to how surveys were actually structured, reviewed, and launched inside Apple Maps.
The product direction centered on a few priorities: create clearer project setup, make survey authoring more modular, introduce preview and validation before launch, and support better tagging and metadata structure for downstream tools.
Just as important, the tool needed to establish reusable patterns so future internal QA products would not need to start from scratch each time.
Solution
A clearer end-to-end flow connected project setup, survey authoring, launch controls, and project monitoring in one internal system.
The final experience gave QA teams a more reliable path from project creation to survey launch. Instead of stitching together disconnected tools and manual steps, teams could build, preview, validate, and configure surveys inside a workflow designed for their needs.
The system included a custom survey builder UI with modular building blocks for rows, questions, images, and maps. A stronger component model made it easier to create structured survey content while maintaining consistency across projects.
Built-in preview and validation helped teams catch issues before launch, while clearer metadata structure and project configuration supported more reliable QA reporting, tagging, and downstream workflows.
System Foundations
Creating reusable patterns beneath the product.
A major part of this work was not just the screen-level UX, but the system beneath it. I designed reusable interaction patterns and UI structures for project setup, content blocks, survey components, preview states, launch configuration, and post-launch visibility so the product could scale more effectively over time.
That included modular patterns for survey rows, question types, map-based content, image handling, launch controls, and project status views. The result was a more coherent authoring experience and a stronger internal foundation for future QA tools.
Impact
Improving speed, accuracy, and confidence across Maps QA workflows.
- Reduced survey creation time by 60%
- Improved confidence by catching logic and setup issues earlier in the workflow
- Increased consistency in bug tagging, metadata structure, and escalation support
- Helped standardize survey workflows across global QA teams
- Created a stronger internal foundation for future QA tooling and reusable design patterns
Beyond efficiency gains, the product improved trust in the survey creation process itself. Teams could move faster while producing cleaner, more reliable outputs that better supported the broader Maps QA ecosystem.
My Role
Leading the UX for a purpose-built internal Maps QA workflow.
- Led end-to-end UX for the internal Apple Maps survey creation tool
- Conducted research, workflow analysis, and heuristic evaluation
- Defined information architecture, authoring flows, and validation patterns
- Designed scalable components and interaction patterns for creation, preview, and launch
- Collaborated closely with QA leads, PMs, and engineers to validate and ship the tool
Credits / Team: QA Leads, Internal Tools PM, Engineering, Research
Tools: Sketch, InVision, workflow mapping, heuristic audit