Home     Resume     About




Responsibility PathfinderThe Responsible Innovation and Ethics team at Meta was formed to ensure that product are built responsibly and prevent harm. Traditionally we’ve acted as thought partner to teams, spread resources, run office hours, and taught classes. 

In 2022, we began building Responsibility Pathfinder, an internal tool to help teams at Meta navigate the complex process needed to launch responsibly. 
Timeline
Feb 2022 — Sept 2022 

RoleSole Product Designer

CompanyMeta


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

    As of February 2022, there were over 25 possible review processes a team might have to consider and engage in before launch.
     
    Quotes pulled our Product Foundation Research team



    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
    • Provide visibility to organization leads
    • Host all the relevent developoment processes accross the product
    • Collect public insight


    Personalized intake form
    Planning and management features for each project
     MVP ProcessSince this internal tool was to be the first of its kind, we set out to build an basic MVP to test with and get early validation. The MVP took about 3 months to develop with included the following activities: 

    1. Journey mapping
    2. Feature prioritization
    3. Concept testing
    4. Rapid prototoyping and validation.

    01 Journey MappingMy 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:
    • Content and design prepared a draft journey map
    • I crafted the agenda and activities ahead of time and facilitated day of
    • Goal of the workshop was to align on users goals




    02 Feature PrioritizationWhen 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 TestingBefore 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. 

    Summarized results:
    • Users cited the timeline view as one of the advantages of using this tool over any existing productivity tool
    • “this view is something we’re always trying to figure out ourselves with a lot of effort”
    • People weren’t sure if the time estimates would be trust worthy, very concerned on how long some actions will take
    • In general users are worried about stale or outdated information






    04 Rapid Prototyping and ValidationWith 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: Project ViewFrom our research we saw that each team is unique in how they function at Meta. With this in mind we made the Project View and flexible and exportable as possible. 

    It can integrate with our internal Tasks tool and export timelines directly to our Calendar tool or CSV. 






    Prototype: Intake FormI worked directly with my content designer to source and map out all the possible pathways and questions for our intake form in order to reduce it’s length. 

    Some key decisions we made were to add certain features such as:
    • “I’m Not Sure” as an answer for tougher questions
    • A stopping point to finish early and get recommendations or dive deeper


    Conclusion
    Due to confidential company reprioritization efforts, this work was put on pause. I choose to hand off this project voluntarily and move teams. 

    My next steps would have been to iterate on designs after research and plan the implementation with engineers.