Addressing Complex Dependencies

Analyzing the device onboarding process revealed many dependencies, making information management complex. To proactively address this, I first created a user flow diagram and shared it with the team and our dependency teams before designing any views. This early collaboration with engineering, legal, and privacy teams allowed them to provide crucial feedback, significantly reducing rework later in the design cycle.

Meeting High Privacy and Trust Expectations

The project had strict privacy and trust requirements, which the initial product requirements didn't meet. The team struggled with the necessity of needing another person's password for device setup. I investigated our existing sharing features and found a solution in the e-book gifting feature. I met with the relevant teams to learn more and create a simple solution. The Product team was skeptical, so I created a demo for leadership, which successfully gained alignment to use my proposed experience.

Streamlining Complex Flow Reviews

The feature's end-to-end process was complicated, spanning web, email, and device interfaces, multiple users, and several internal organizations. This led to long initial presentations with many questions. To solve this, I modeled my presentations after Amazon's document-reading culture. I created a self-guided, interactive Figma prototype/presentation that covered the entire experience, accounting for different team dependencies. Attendees reviewed it independently, leaving comments like a document review. This approach significantly cut down review time, boosted the approval process's efficiency, and was later adopted by other teams for their complex flows.