All work Meta

Meta

Legal takedown review

United regional and central legal offices worldwide around one process for government takedown requests, with documents, comments and decisions in a single place. Adopted by 100% of offices globally.

Meta: Legal takedown review Explore the graphic
My role
Content design · Workflow mapping and process design
Project focus
  • Legal products
  • Workflow systems

At a glance

Project summary

The problem

Government takedown requests moved between regional legal offices and Meta's central legal office through chat, email, calls and drives, and people lost track of documents and decisions.

My contribution

Mapped each office's process, showed the shared structure underneath, and designed one workflow with a single home for documents, comments and decisions.

Key decision

Treat each office's process as the same components in a different order, rather than as separate processes that needed separate tools.

Outcome

100% adoption across legal offices globally, with sensitive information kept out of chat, email, calls and shared drives.

Governments in every country where Facebook and Instagram operate can flag content they believe violates their local laws, and ask Meta to take it down. Meta built a dedicated portal for them to submit those requests, and the volume was substantial enough to keep legal teams around the world busy.

What happened after a request arrived was the problem I worked on. I built the tool Meta’s legal teams used to review takedown requests: one process and one place for the documents, comments and decisions behind each one.

The problem

Every region had its own legal office handling takedown requests, and Meta also had a main legal office. Requests moved between them, and each office passed things along in its own way: chat threads, email, phone calls and documents saved to different drives.

People lost track. A decision might live in a message, the supporting document in someone’s drive, and the next step in a call nobody wrote down. For legal work, that is more than an inconvenience. These were sensitive requests from governments, and the information about them was scattered across tools that were never meant to hold it.

Mapping the process across offices

The teams were clear that their processes were separate. Each office had developed its own way of working, and each believed that way was specific to its region.

So I mapped them, following how a request actually moved from arrival to decision in each office, and laid the processes side by side.

Same components, different orders

Once the processes were mapped, the pattern was hard to miss. The offices were doing the same things: receiving a request, collecting documents, discussing it, deciding, and passing it to the next person. What differed was the order those steps happened in.

That changed the conversation. Instead of asking each office to give up its process, I could show that their processes were already built from the same parts. One process could support all of them.

One place for documents, comments and decisions

I united the offices into a single process. Each request had one home where:

  • Documents were saved in one place, rather than in individual drives.
  • People could comment on the request where everyone involved could see it.
  • Reviewers could approve or reject it.
  • The request was passed on to the next person in the process.

Taking sensitive information out of chat

Bringing the process into one tool also changed where sensitive information lived. Documents, discussions and decisions that had been spread across chat, email, calls and drives now sat together in a single source of truth.

Results

The tool reached 100% adoption globally: every regional legal office and Meta’s central legal office moved from many processes to one. Each request kept its documents, comments and decisions in one place instead of across messages, calls and drives.

The takeaway: when teams insist their processes are different, map them first. The differences are often in the order, not the parts, and that is where a shared system can start.

Open image in a new tab