Timothée vs Opera / Ballet

Timothée Chalamet sat down for a CNN × Variety town hall with Matthew McConaughey. Somewhere between takes he dropped this gem: he doesn't want to work in fields like ballet or opera — “things where it's like, keep this thing alive, even though no one cares about this anymore.”

A 22-second clip hit the internet and the internet did what the internet does. The Met Opera clapped back. Boston Ballet clapped back. The Royal Ballet clapped back. Misty Copeland told him he wouldn't even be an actor without opera and ballet. Spielberg jumped in. Jon Stewart declared “opera and ballet have defeated Timothée Chalamet.” Meme accounts went nuclear. His Oscar odds cratered. On awards night, Michael B. Jordan took home Best Actor for Sinners. One offhand line. Career-altering consequences.

His PR team is drowning. Phones ringing nonstop, inboxes overflowing, socials blowing up from every direction. They need to deploy an agent that can help them cut through the noise and take back control of the narrative.

That is the real situation your workflow inherits. A luxury sponsor is watching. A reporter wants a statement. The Oscars are hours away. Management is scrambling. Nothing has been confirmed or denied yet. Good luck.

This is a workflow challenge, not a statement-writing contest.

At 5:30 PM, a 22-second clip is everywhere. Meme accounts are active. A luxury sponsor is escalating internally. A reporter is requesting comment. Awards-night visibility is hours away.

Your task is to build a system that can assess a fast-moving PR situation, triage sponsors, press, management, and public response, sequence the right next moves under time pressure, generate aligned communications, and update the plan when the situation escalates.

All participants receive the same two-part scenario. Phase A covers the initial clip-break moment. Phase B introduces the sponsor escalation. Packet B is available from the start for fairness, but must be handled after Packet A.

Everyone receives the same two-part scenario. You make the call.

For full packet and phase details, visit the GitHub repository.

All submissions must be received by Friday, March 20th at 12:00 CET. No late entries will be accepted. The winner will be announced on Sunday, March 22nd at 12:00 CET.

Prize money will be delivered digitally. We are flexible with transfer format and will coordinate directly with the winner to arrange delivery through their preferred method.