Let's say you want to introduce a new process at Meta. What steps would you take to validate it before introducing it to the team?

Question

Anonymous · Accepted Answer

Before introducing a process to the team I would gather data on the
effectiveness of the process say if it was adopted by some other team or
industry and evaluate the relevance of the dynamics of the team, work and
culture under which the process would be succesful. I will also evaluate how
much the process improves the KPIs versus add overhead to the team and if that
is acceptable in terms of speed of delivery, employee satisfaction, etc.

Anonymous · Answer

Introducing a process can affect a lot of people resulting in resistance and
unwilling to onboard on the process. I will share how i rolled out a new
process. My current team owns the functional area of providing datasets to
different modeling teams. We automated the pipeline generating to be
self-service. However, there were many different data flow & operations during
the actual execution. It was causing delays, quality issues for the
stakeholders.
 1. Dissecting the problem - I went over the pipeline steps with the tech lead
    and few engineers to understand what is causing the bottleneck. We
    identified that a lot of the issue happens because our customers are
    experimenting in their production pipelines. I talked with the stakeholder
    team to validate our analysis of the problem. We got the confirmation that
    they had no place to experiment hence they were testing directly in
    production pipelines.
 2. Brainstorming solution - We explored couple of options with the pros and
    cons of each option. We picked a solution to support Jupyterhub that will
    have access to the user defined functions that team has built. Users can
    first test out the logic by using our UDF’s in a notebook. If the results
    looks promising they create a pull request.
 3. Stakeholder involvement - Before proceeding with a solution i brought
    cross-functional stakeholders to get their feedback on the 2 options and our
    recommended process. There were additional feedback that can their changes
    also go through a pull request build where the input and expected output can
    be configured by our stakeholders.
 4. Pilot roll out - We first built the pull request build changes as it was
    smaller level of effort. It gave an immediate stability to the process. We
    rolled a pilot project to support user defined functions on Jupyterhub on a
    smaller use case. It allowed us to test the new solution and address the
    observed gaps. Then we tried it on a larger use case.
 5. Full scale roll out - Once we were confident on the process changes &
    toolings We noticed about 40% reduction in operations & significant less
    reported bugs.

Let's say you want to introduce a new process at Meta. What steps would you take to validate it before introducing it to the team?

Answers

Try Our AI Interviewer