Home    About    Resume

Responsibility Pathfinder

March 2022 — Ongoing

Responsibility Pathfinder is an internal tool that helps teams at Meta navigate the various development processes and quality activities needed to launch responsible products. 

As the Product Designer working on this brand new product, I was responsible for designing our Northstar vision prototype for leadership reviews, while also developing the actual MVP designs. All the following designs are made solely by me. 

Northstar wireframes

The Problem

We know that product teams are struggling to keep up with the ever-expanding set of requirements, reviews, and considerations. 



Solution

An internal tool to act as a single source of truth that has tracking, planning, and management features:
  • Personalize a project plan and timeline for you based off your project details
  • Provide visibility to organization leads
  • Host all the relevent developoment processes accross the product
  • Collect public insight




The MVP Process


Team: Product Design, Content Design, Research, and Program Management

01 | Journey Mapping

My first activity after joining the team was take our prior research, consolidated Jobs to Be Done, and MVP definition to form a journey map of the product. 


This final journey map was completed after a team workshop in Figjam where content, research, and design prepared a basic journey map and sourced feedback and comments from our broader XFN team and stakeholders.

We prepared homework before the workshop


The FigJam board after our 1.5hr workshop

02 | Feature Prioritization

When I joined the team, most of the documentation was done in monthly leadership update slides and used as the source of truth. While I created basic documents like a product brief, my most important document for me was my requirements and features document. 



I organized features into major categories, gave each feature a priority, and sized each item for the design team and also in preparation for engineering.

03 | Concept Testing

Before I joined, a brief round of concept testing was done with low-fi prototypes. To continue the concept test with higher effectiveness, I created higher fidelity prototypes based on our journey map and feature prioritization. 

Note: While these appear high fidelity, these were made for illustrative research purposes only and were not meant to be fully functioning. 



04 | Rapid Prototyping and Validation

With the insights from all the prior research, journey map, and our feature prioritization doc, we set out to finally build the MVP product. We decided to build feature by feature while validating in parallel with research. 

Example:
Week 1: Design and Content create Project View
Week 2: Research validates the Project View, Design and Content create Intake Form. 


Prototype 1: Project View



Prototype 2: Intake Form



Prototype 3: Browse Experience



05 | Conclusion

Due to confidential company reprioritization efforts, this work has been put on pause. My next steps would have been to complete the third prototype, iterate on all the prototypes based off of research results, and then hand off to engineering. Once a base MVP was built, we planned to pilot test with teams from Facebook and Reality Labs.