AMA Program Design
An AMA (Ask Me Anything) program is a structured, recurring forum where leaders take questions directly from employees with no pre-screening, no curated softballs, and no PR filter. Done well, AMAs become the highest-trust channel in a company — the place where the hardest questions get answered first. Done badly, they devolve into rehearsed exchanges that destroy trust faster than no AMA at all. The design choices: anonymous submission, public upvoting, leader commitment to take the top questions in order, and the discipline to answer the spicy ones honestly. Google's TGIF tradition (later renamed) was the canonical version of this format at scale.
The Trap
The trap is the slow drift toward question curation. Year one: a leader gets blindsided by a hard question and answers awkwardly. Year two: the comms team starts 'helping' by reordering questions to ease the leader in. Year three: questions are pre-screened for 'tone.' Year four: the AMA is dead — employees know it's not real and stop submitting the questions they actually have. The unglamorous truth is that the value of an AMA is exactly the discomfort of taking a question you didn't choose. The moment you remove that, you've removed the program's reason to exist.
What to Do
Build the AMA with these non-negotiables: (1) Anonymous question submission via a tool that supports public upvoting (Slido, Pigeonhole, internal equivalent). (2) Leaders take questions in upvote order — top-voted first, no exceptions. (3) Minimum 30 minutes live, no time-cutting the queue. (4) Questions that can't be answered live get a written follow-up published to the whole company within 7 days. (5) Track the 'avoided question' — every quarter audit whether any top-5 question was skipped or punted. Zero is the only acceptable count. (6) Quarterly cadence; if leaders can't sustain monthly with quality, drop to quarterly rather than degrade.
Formula
In Practice
Google's TGIF tradition (Friday all-hands with open Q&A founded by Larry Page and Sergey Brin) became famous as a high-trust AMA format in tech. For nearly two decades, anyone could submit questions and the most-upvoted ones got asked, including uncomfortable topics about strategy, leadership decisions, and ethics. The format was celebrated as a cultural cornerstone. Its eventual evolution and reduction (around 2019, when TGIF moved to monthly business-only Q&A after leaks and contentious topics) is itself a case study in what happens when AMA discipline degrades. (Source: New York Times reporting on Google's all-hands changes, November 2019.)
Pro Tips
- 01
Leaders need rep to handle hard questions well. If your CEO has never been blindsided by a tough question publicly, the first time will be ugly. Practice with a 'red team' session before each AMA — have a trusted group submit the worst questions they can think of so the CEO can rehearse honest answers.
- 02
Track the gap between AMA submissions and other anonymous channels (engagement surveys, eNPS comments). If the same concerns appear in surveys but not in AMA submissions, your AMA isn't trusted — employees believe the channel will punish them, so they vent only where they're truly anonymous.
- 03
The most powerful AMA answer is 'I don't know yet, here's what we're going to do to figure it out, I'll report back at the next AMA.' Honest uncertainty plus a commitment beats a confident non-answer every time.
Myth vs Reality
Myth
“AMAs are about answering every question”
Reality
AMAs are about taking the questions employees most want answered, in the order they want them answered. You can't possibly answer every question in 30 minutes — but you must answer the top-voted ones, in order, including the spicy ones. Skipping the top question to take an easier one further down the list is the single fastest way to destroy AMA credibility.
Myth
“Anonymous questions enable bad behavior”
Reality
Anonymous submission with public upvoting filters the bad behavior automatically — toxic questions don't get upvoted because the audience itself is the moderator. The actual risk is the opposite: non-anonymous submission discourages the most important questions, especially from junior employees and people on visa-dependent statuses who can't afford to be associated with hard questions.
Try it
Run the numbers.
Pressure-test the concept against your own knowledge — answer the challenge or try the live scenario.
Scenario Challenge
You're the CHRO. Your CEO did a recent AMA where the top-upvoted question was about a controversial layoff decision. They visibly skipped it and took question #4 instead. Engagement scores for the next quarter dropped 8 points. The CEO wants to do another AMA next month and asks you to 'pre-vet questions to avoid surprises.'
Real-world cases
Companies that lived this.
Verified narratives with the numbers that prove (or break) the concept.
1999-2019
Google's TGIF tradition — a Friday all-hands with open Q&A founded by Larry Page and Sergey Brin in the company's earliest days — became the canonical AMA format in tech for nearly two decades. Anyone could submit questions through the internal Dory tool; questions were ranked by employee upvotes, and the top-voted ones were asked live, including uncomfortable topics. The format was widely celebrated as a cultural cornerstone of the company's openness. In November 2019, after years of leaks and increasingly contentious internal debates, Google announced TGIF would shift to monthly cadence focused on business-and-product topics, signaling a pullback from open Q&A on broader topics. The arc — from celebrated openness to deliberate scope reduction — is itself a case study in the difficulty of sustaining AMA discipline at scale.
Founding Era
1999
Question Tool
Dory (employee-upvoted)
Format Change
Nov 2019
Post-Change Cadence
Monthly, scoped
AMA culture is fragile at scale. When the org grows past the size where every employee feels personal stake, leak risk and topic breadth start working against the format. The choices: scope down, slow down, or accept the friction. Pretending none of these tradeoffs exist eventually breaks the program.
Related concepts
Keep connecting.
The concepts that orbit this one — each one sharpens the others.
Beyond the concept
Turn AMA Program Design into a live operating decision.
Use this concept as the framing layer, then move into a diagnostic if it maps directly to a current bottleneck.
Typical response time: 24h · No retainer required
Turn AMA Program Design into a live operating decision.
Use AMA Program Design as the framing layer, then move into diagnostics or advisory if this maps directly to a current business bottleneck.