Case study: McDonald's unfinished Black Friday tweet
A scheduled placeholder went live on one of the busiest shopping days of the year. Why the reaction stayed friendly, and the queue checks that prevent a repeat.
On Black Friday 2016, one of the most-followed restaurant brands on Twitter posted something its followers had never seen from it: an unfinished tweet. The post began with the words Black Friday and then, where the clever line and the link should have been, carried an internal note in asterisks saying that copy and a link were still needed.
It took minutes for the screenshots to start circulating.
What happened
What most social media managers assumed at the time is the likely explanation. Someone created a placeholder in a scheduling tool, a slot for the Black Friday post with a reminder to write it later, and the placeholder had a publish time attached. Nobody replaced it, so on the day the tool published exactly what was in the slot.
Big brands plan holiday content weeks ahead, and calendars fill up with reminders and half-finished drafts. The mistake wasn’t scheduling. It was letting a draft sit in a slot that could publish.
How people reacted
Mostly with jokes. Users replied with jokes about the missing copy, and the tweet was covered by marketing and news sites as a lighthearted slip. Because the placeholder contained nothing offensive, the reaction was teasing rather than outrage, and it gave McDonald’s a day of unplanned attention.
The coverage treated it as a funny mistake, not a crisis, and there was no lasting damage. That outcome was luck, not design.
Why it was luckier than it looked
A placeholder is harmless when it says “need copy”. The same failure in the process can publish something far worse: a draft price that hasn’t been approved, a joke written for internal colleagues, a post meant for the day after a tragedy, or a reply aimed at the wrong account.
McDonald’s had a very different experience on the same platform a few months later. In March 2017 its corporate account posted an insulting message about the US president, which the company later said was the result of the account being compromised. That incident was about account security rather than scheduling, but both had the same root: posts reaching the public that nobody responsible had approved.
A scheduled post is published by a machine that has no idea what the post says.
That is the point to keep. The convenience of scheduling, posting at the best time without being at a desk, comes from removing the person at the moment of publishing. So the checking has to happen before.
What a team can check before posting
Keep drafts out of publishable slots
Write drafts in a separate document, a shared Notion page or Trello card, or the scheduler’s draft state, and only move a post into the calendar once it is final. If a tool offers a placeholder or note feature that cannot publish, use that, never a real post with a note to self in it.
Require approval before scheduling
Team scheduling tools such as Hootsuite and Sprout Social offer approval workflows on their business plans. Even a small team can agree that every post is read by a second person before it gets a time slot. In a one-person business, that second reader can be you, the next morning.
Review the queue every week
Set a recurring reminder, Friday afternoon works well, to read every post scheduled for the next seven days, in full, as it will appear. Check the text, the link, the image and the date. Search the queue for brackets, asterisks, double question marks and words like insert, copy and link that only make sense to the person drafting.
Pause the queue when the news changes
A post that was fine on Monday can be wrong by Thursday. When something major happens, pause the schedule until someone has looked at what’s coming. The Celeb Boutique case study shows what happens when a brand posts into a tragedy without checking.
Secure the account
Use two-factor authentication on every social account, give access through Meta Business Suite or the scheduler rather than sharing passwords, and remove former staff and agencies the day they leave. Strong logins protect the brand from the kind of compromised-account incident that hit McDonald’s in March 2017.
Turning a slip into a reply
If an unfinished post does go out, the best response is fast and honest. Delete it or replace it with the real post, and if people are already joking about it, a light reply that owns the mistake usually lands better than silence. Avoid blaming an intern or a junior employee in public; that tends to turn a joke into a story about the company.
For other ways brands have stumbled in public and what each one teaches, browse the case studies. For planning posts that are worth scheduling in the first place, the guide on how often to post on social media is a useful start.
The simplest fix of all costs nothing: before closing the scheduler each day, open tomorrow’s posts and read the first line of each one out loud.
Quick answers
What happened with the McDonald's Black Friday tweet?
On Black Friday in November 2016, the McDonald's account on Twitter published a post that was clearly not finished: the words Black Friday followed by an internal note, in asterisks, saying the copy and a link were still needed. It looked like a placeholder in a scheduling tool that went out before anyone wrote the real post.
Did the unfinished tweet hurt McDonald's?
Not in any lasting way. The post was embarrassing rather than offensive, and most of the reaction was jokes. That is the luck of the content: a placeholder with nothing sensitive in it. The same process failure could publish an unapproved price, an internal comment or a post meant for a different day.
How do you stop a placeholder post being published by accident?
Never put a placeholder in a slot that can publish. Keep drafts in a separate document or in the scheduler's draft state, require a named person to approve each post before it is scheduled, and review the next week's queue every Friday. A simple search of the queue for brackets, asterisks and stray notes to self catches most leftovers.
What should a brand do if an unfinished post goes out?
Act quickly and honestly. Delete the post or replace it with the finished version, and if people are already joking about it, a light reply that owns the mistake usually lands better than silence. Avoid blaming an intern or a junior employee in public, because that tends to turn a harmless joke into a story about the company itself.
More in Case studies