A former Meta engineering director who had testified before Congress about child safety on Instagram told jurors Wednesday at a landmark trial that the company took a “don’t ask, don’.
The testimony opened a window into how decisions were framed inside the company, with engineers and managers describing trade-offs between growth and safety. Jurors heard about internal conversations, priorities and what one witness portrayed as a permissive mindset toward potential harms. That mix of testimony is central to a case many see as probing whether a tech giant put engagement ahead of vulnerable users.
The witness, previously called to speak on Capitol Hill, brought those same concerns into the courtroom, recounting how teams interpreted product choices and enforcement practices. He described a pattern that, according to his account, discouraged digging into certain risks. The phrase he used to capture that approach was the now-highlighted “don’t ask, don’.
Legal teams framed the trial as a test of corporate responsibility, pressing on whether internal knowledge translated into action to protect younger users. Plaintiffs argued that warnings and research were not followed by meaningful fixes, while defense counsel emphasized complex engineering constraints and shifting priorities. The courtroom debate focused less on abstract ethics and more on what engineers and managers actually did day to day.
Witnesses described meetings where metrics guided road maps and where possible harms were weighed against product goals and engagement targets. Those conversations are familiar to anyone who has watched social platforms scale: decisions cascade from product choices into user experience and, potentially, into real-world effects. In this case, jurors were asked to consider whether those cascades reached a level that the company should have anticipated and mitigated.
Outside experts and former employees have long warned about risks tied to algorithmic amplification and design choices that favor longer sessions and more interactions. In court, that context was used to explain how features intended to connect people can also surface disturbing content or encourage risky interactions. Testimony explored both the intended outcomes engineers sought and the unintended behaviors those features sometimes produced.
Legal strategy in the case leaned on internal documents and testimony to build a timeline showing what the company knew and when it knew it. Plaintiffs sought to link those internal findings to the experiences of real users, especially younger ones who might be more susceptible to harms. The defense pushed back by highlighting the uncertainty inherent in predicting human behavior and the rapid pace of product development.
Observers watching the trial noted how the proceedings spotlight broader questions about regulation, corporate culture and the limits of voluntary industry action. Some argued that courtroom scrutiny may lead to tighter oversight or new expectations for transparency in tech development. Others warned that litigation-driven fixes can be slow and might not address systemic design challenges without clearer policy guidelines.
The former engineering director’s account underscored how cultural norms within a large organization can shape technical choices and risk assessments. Jurors were left to weigh testimony, documents and expert analysis as they determine whether those norms crossed a line. The outcome could influence how platforms balance growth with safety going forward, but the path to change remains complex and uneven.
