ViralAnatomy
Get started →
8:08

Plays here · Open on youtube ↗

organic“Tally was not involved in the creation of this video, it's all me.” The channel bio names “tool comparisons,” and only 1 of 11 independently scanned recent uploads mentioned Tally — https://www.youtube.com/watch?v=jT57uCPr7p88:08 · on_screen hook

“2022 DESIGN TOOLS SURVEY”

The opening line · 0:00 · move: story

Grounds the tutorial in a 4,000–5,000-response annual UX survey, explicitly discloses Tally was uninvolved, and demonstrates logic, calculations, embeds, and Notion routing.

4.6Kviews121likes↑0.4×vs their usual post · 11K views3creators ran this script

@UX Tools · 29.9K followers · 1 of 11 recent posts mention Tally · creator page →

Playbook · Make the form an input, not the outcome →
The script, step by step10 steps
1Call out the practitionercreator-claim0:00–0:05
Call out the practitioner at 0:000:00
Call out the practitioner at 0:000:00
Call out the practitioner at 0:010:01
Call out the practitioner at 0:020:02
Call out the practitioner at 0:030:03
Call out the practitioner at 0:040:04
0:00As a UX or product designer,

The opener names a narrow audience whose survey pain the creator has lived.

0:02there's a really good chance
0:03that you have probably made a survey before.
2Price the bad experience0:05–0:20
Price the bad experience at 0:050:05
Price the bad experience at 0:060:06
7 lines · members
3Supply lived-use proof0:20–0:54
Supply lived-use proof at 0:090:09
16 lines · members
4Disclose independence0:54–1:30
Disclose independence at 1:211:21
17 lines · members
5Teach the document model1:30–2:43
Teach the document model at 2:432:43
33 lines · members
6Demonstrate branching2:43–3:55
Demonstrate branching at 4:454:45
30 lines · members
7Add survey intelligence3:55–6:22
Add survey intelligence at 6:066:06
67 lines · members
8Put feedback in context6:22–7:11
Put feedback in context at 7:277:27
22 lines · members
9Route the response onward7:11–7:50
Route the response onward at 0:080:08
17 lines · members
10Return to the use casecta · follow7:50–8:08
Return to the use case at 0:070:07
7 lines · members
216 more linesmembers read and copy every script on the site
Where this post sitsthe repetition is the proof
Anchors the playbook
Make the form an input, not the outcome

Start with a lived workflow, capture structured input in Tally, then visibly route it into Airtable, Make, Notion, or an embedded product surface until useful work appears downstream.

Workflow educators embedding Tally inside agency, research, and personal operating systems · 3 creators · 3 posts

Capture context, then hand off the work
Open the full playbook →
4.6K@UX Toolsaffiliate636@Dan and Nath2.9K@Jenna Redfield (Red Thread Toolbox 🧰 )

this post · other creators who ran it

Who made ittheir public relationship signal, and the receipt for it
@UX Toolsyoutube · 29.9K followers · median 11K views · n=22best post4.6K0.4×views · for Tallyorganic “Tally was not involved in the creation of this video, it's all me.” The channel bio names “tool comparisons,” and only 1 of 11 independently scanned recent uploads mentioned Tally — https://www.youtube.com/watch?v=jT57uCPr7p8Open creator →

Views and likes are public counts at capture time. The multiple compares this post with the creator’s own recent median, not a claim about what caused its reach. Read the methodology →