CoinDock Community · How to
How to Host a Project AMA That Is Worth Attending
AMAs are usually run as promotion. Run as accountability they are far more valuable, and considerably harder.
Direct answer
To host a worthwhile AMA: collect questions in advance, answer the hardest ones first, prepare answers to what you hope nobody asks, say "I do not know" when true, make no claim about price, and publish a transcript afterwards. The value comes from questions being genuinely answered — an AMA that dodges the difficult ones actively damages trust.
Step 1 — Collect questions in advance
Open submissions several days ahead, in a thread where questions are publicly visible.
Two reasons. It gives you time to prepare properly rather than improvising under time pressure. And public submission means the community sees which questions were asked — so skipping the awkward one is visible, which is a useful constraint on yourself.
Step 2 — Prepare for what you hope nobody asks
List the questions you would least like to be asked. Then prepare answers.
Typically: the missed timeline, the token unlock schedule, the treasury, the departed team member, why the price is down, the audit finding, the competitor doing it better.
You will be asked at least one of them. Preparing an honest answer in advance is the difference between a considered response and a defensive one.
Step 3 — Answer the hard questions first
Counterintuitive and effective.
Leading with difficult questions signals you are not managing the session, and it stops the whole event being read as an exercise in avoidance. It also gets the tension out of the way early, which makes the rest more productive.
Saving hard questions for the end — where they may be missed for time — is a transparent tactic and read as one.
Step 4 — Rules for answering
"I do not know" is a complete answer. Followed by "I will find out and post by Friday" — and then doing it — builds more credibility than any confident answer you could have improvised.
Do not answer a different question. Everyone notices. An evasion costs more than the honest answer would have.
Do not promise dates you cannot commit to. An AMA is exactly where projects generate commitments they later miss.
Say nothing about price. No targets, predictions, or explanations of price movement. "We do not comment on price" is sufficient. See how to promote responsibly.
Do not announce anything unconfirmed. AMAs create pressure to have news. Resisting it prevents the unsigned partnership announcement you regret.
Step 5 — Handle hostile questions well
Some will be hostile. A few will be bad-faith. Both are worth answering calmly.
Answer the substance, ignore the tone. If someone asks aggressively whether you are dumping tokens, the answer is the vesting schedule and the treasury address — not a comment on their manner.
Do not ban critics during an AMA. Whatever the provocation, it will be the thing people remember.
A bad-faith question with a good answer is a gift. You get to address a concern others held quietly, with a specific answer, publicly, on the record.
Step 6 — Publish a transcript
Within a day, publish the questions and answers somewhere permanent on a domain you control.
- Makes the AMA useful to people who could not attend.
- Creates a record you can point at later.
- Means commitments made are written down — which is a discipline on you, in a good way.
- Includes the questions you were asked, not only the ones you liked.
An AMA that vanishes into a chat scroll delivers a fraction of its value.
Step 7 — Follow up on commitments
Whatever you said you would do, do it, and say when you have.
The AMA's value is not the hour. It is whether the things promised in it happen. A project that follows up converts a session into credibility; one that does not has taught its community that AMA commitments are theatre.
The checklist
- Questions collected in advance, publicly visible
- Hardest questions identified and answers prepared
- Hard questions answered first
- "I do not know" used where true, with a follow-up commitment
- No price commentary
- No unconfirmed announcements
- Hostile questions answered on substance
- Transcript published within a day
- Commitments tracked and followed up
Common mistakes
- Screening out difficult questions. Visible, and read correctly.
- Improvising on the unlock schedule. Prepare it; the numbers should be at hand.
- Making commitments to fill silence.
- Answering a nearby question instead of the one asked.
- No transcript, so the session evaporates.
- No follow-up, which converts the whole thing into theatre.
Related
Step-by-step
How to Host a Project AMA
Run an effective AMA without surprises.
-
Schedule and announce
Pick a time and broadcast it well in advance.
-
Collect questions
Open a question form ahead of time.
-
Bring data
Have metrics and roadmap on hand.
-
Publish transcript
Post a recap for anyone who missed it.
Related on CoinDock Community
-
Transparency FAQ
What to publish, what publishing costs, and where the line between privacy and accountability sits.
-
How to Launch a Token Community
Set up the security rules before the members arrive. Retrofitting them after an impersonation incident is much harder.
-
How to Write Project Updates
The update that determines your credibility is the one reporting something going wrong. Most projects have not planned h...
-
How to Educate Token Holders
Ordered by how much damage ignorance causes, not by what is easiest to write.
-
Build a Healthy Token Community
Almost all content on this subject is written by agencies selling growth services. This is not, and the advice differs s...
Build Your Coin Community
Continue your CoinDock journey.
Go