Creator: Enrico Tartarotti · Published: 2026-08-19 · Length: 14:30 · Watch on YouTube

That tiny freeze when a punch lands in Super Smash Bros has a name, a purpose — and a near-identical twin inside Notion. — video description

1) Detailed outline

[0:00] Cold open: hit stop, boss stop, kill stop… and their software twins

• Hit stop (Super Smash Bros.): after a heavy attack, designers freeze everything for a fraction of a second because this is a big attack. Notion does the same with a toast when you do a large action (e.g., archiving a page) instead of a routine block move.
• Boss stop (Kirby): beating a boss gives a pause and a screen flash because you completed something big. In Enrico's own product Flask, finishing an important onboarding step triggers an attention-grabbing onboarding callout.
• Kill stop: dying is the biggest thing that can happen in a game, so designers add an even bigger freeze (plus camera shake and slow motion) to show where you died and what killed you. Footage credits Masahiro Sakurai on Creating Games, with GTA death-cam clips. The software version: Vercel blocks everything else when you delete a project and makes you type the project's full name to confirm.
• Thesis [1:00]: "What if all products are secretly games?" Zelda ↔ Google Chrome, GTA ↔ iPhone, managing HP in Skyrim ↔ managing tokens in Claude. Game design and product design rest on the same six principles. This is not surface "gamification" (points, mascots). It's deeper: playing with human psychology.

[1:30] Principle 1: Tutorials and onboarding (teach without telling)

• Plants vs. Zombies, level 1 has no on-screen instructions. Yet by the end, players know zombies walk in straight lines, peashooters fire in straight lines, and it takes about 10 peas to kill a zombie. Ask players about the tutorial and most say there wasn't one.
• In playtesting, players didn't understand the importance of planting lots of sunflowers early, and on-screen text didn't fix it. The fix (shown in archival talk clips): change the Sunflower's cost to 50 and the starting sun to 50. At level start the Peashooter is greyed out, so the only possible move is a Sunflower. Moving that cost from 100 to 50 meant rebalancing and retesting the whole game: "dozens of hours of work in different versions."
• Software parallels [2:33]:
  • Notion: new accounts land on a page of example blocks you can drag around and turn into pages. You learn by doing.
  • ChatGPT: no instructions and no checklist, just a prompt box. In April 2024 OpenAI removed the last step left, creating an account, so the only thing to do is start prompting, or rather start playing.
• Two rules shared by the best games and products [3:05]:
  1. Speak only when the user is stuck or doing something wrong. Example: Gmail's forgotten-attachment warning appears only if you write "attached" and attach nothing.
  2. Use visuals instead of text. Long text onboarding screens get rage-clicked away. Visual ones actually teach.

[3:35] Principle 2: What a game is made of (the core loop)

• Source: the book Game Feel (shown with charts of Mario's jump arcs and Tekken hitboxes). It contains a loop at the heart of what makes a game a game:
  • Context: the space where things happen (starting as "just a rectangle").
  • Input: buttons, a motion remote, tilting a phone, or making the input itself the centerpiece (a Guitar Hero-style guitar controller is shown).
  • Response: press a button and the character jumps.
  • Metaphor: it's not a rectangle, it's a plumber in the Mushroom Kingdom rescuing a princess.
  • Rules: green pipes may lead somewhere. You can smash bricks only when big.
  • Polish: dust under Mario's feet when he lands, simulated jump gravity, animations.
• [4:38] Applied to AI coding agents: Claude Code and Codex, "hooking millions of people into building apps… and reconsidering their life while they wait for the limits to expire":
  • Input: a typed prompt and Enter. Response: the app or system you're building changes.
  • Rules: one main chat, and the chat can spawn agents. You choose a model, and the smarter it is, the slower and more expensive it gets. Resources to manage: tokens.
  • Context: it can build for the browser and edit files on your computer.
  • Metaphor: talking to a robot assistant that can do anything (games are more creative here, with no princesses).
  • Polish: running animations, Claude's playful status verbs and keywords, shimmering "working" text.
  • Conclusion: Claude Code is addictive because it's built exactly like a game. Instead of "one more level/turn" it's "one more prompt." That's real gamification: making the whole product feel like a game, not bolting on points or mascots.

[5:55] Principle 3: Juice (what tech calls "craft")

• A dull Breakout clone used by game developers to prove a point (the classic "juice it or lose it" demo). The game underneath stays identical while they layer on color → tweening (easing instead of teleporting) → bounce sounds → particles when a brick breaks → screen shake. Now it feels good. Game developers call this juice: "makes your game better 100% of the time."
• Juice = "craft" in the tech-bro vocabulary. Examples from Flask:
  • Dropdowns appear with a slight spring animation that originates from the button that opened them.
  • A subtle dark overlay focuses attention on the open menu.
  • Buttons press down while the mouse is held, so it feels physical.
  • Animated tag add/remove on comments. Deleting a comment animates in place with a shimmer to draw attention.
  • Each one is insignificant alone. Together they give the product juice.

[7:15] Sponsor segment: Cursor (cloud agents)

• Mountain-biking downhill, Enrico gets a Slack request from a big Flask customer: bulk feedback extraction across multiple videos/assets for analytics. He pastes the conversation into Cursor. Cloud agents pull the Flask codebase, spin up a cloud virtual environment, implement the change, and prepare a PR.
• They also run the product in a full Linux instance with a UI, operate it to check the front end, and record a video of the agent using Flask to show the changes. Enrico reviews it on his phone. The description link offers 50% off the first month.

[8:17] Principle 4: Easy to learn, hard to master (progressive disclosure)

• Computer Space, the first commercial video game, flopped because nobody understood its four buttons. The next game printed one instruction on the cabinet, "Avoid missing ball for high score": that was Pong, one of the most iconic games ever. This gave rise to Bushnell's Law: the best games are easy to learn and difficult to master.
• Civilization: turn one gives you one settler, one warrior and about three possible actions. New things unlock every few turns (technology, a second city, trade, diplomacy, religion, war). 300 turns later you run an empire through a tech tree with dozens of branches. The whole game exists from second one but is designed to be discovered progressively.
• [9:19] Figma is a prime example of progressive disclosure. It looks weirdly simple next to panel-heavy pro tools, yet the first rectangle can grow into a full design system with variables, motion design and deep control.
  • Demo: build an iOS icon. Round the corners, but iOS icons aren't rounded squares. They're squircles (continuous-curvature corners). That advanced control (corner smoothing) appears only when you dig into the setting, along with a marker for the exact iOS value. Deselect, and you're back to the simple UI.
  • Making a presentation? Conditional variables and advanced components stay hidden.

[10:23] Principle 5: Multiplayer (designing for the behavior of others)

• 2b2t, a Minecraft server running since 2010 with no rules: a barren wasteland where you're killed on spawn and most of the first million blocks have been destroyed. The hard part of multiplayer isn't the networking. It's predicting, or designing, how people will behave in a shared world.
• Journey: designers built a physics system so players could help each other climb ledges. Instead, players pushed each other into danger (archival developer clip).
• Google Docs: an "anonymous capybara" joins your doc and your behavior instantly changes. What happens to the part my friend is editing? Is there version history? What does undo do? Multiplayer breaks basics you take for granted.
• Ctrl+Z problem: if I type "Obi-Wan Kenobi" exactly where Sarah types "Frodo Baggins" and we both undo, whose change disappears? The answer is Operational Transformation (OT), from a paper on synchronizing concurrent edits and making multi-user undo work.
• Why it matters: a system where you trust every change is undoable makes people take more risks. That trust creates the magic of real-time collaboration and can make a product "10× better" than competitors.

[11:58] Principle 6: Monetization (the free-to-play playbook)

• Bartle types, the four kinds of players, each with a different monetization angle: Achievers (progress), Socializers (talk to people), Killers (compete/dominate), Explorers (stories and experiences).
• The F2P playbook (archival clips from a mobile-games talk):
  1. The icebreaker: a deal too good to refuse. After the first purchase, people see themselves as spenders.
  2. Sell faster progress.
  3. Consumables for maxed-out players, basically unlimited spend (no ceiling in Clash of Clans).
  • The sharpest trick: sell the exact second they lose, not while they're thinking. Example: Temple Run's "Save Me", a few seconds to spend hard currency and continue.
• Software does the same [13:02]:
  • Google Meet doesn't upsell on a pricing page. It ends your free meeting after a time limit and asks you to upgrade a few minutes before, mid-conversation.
  • $1 trials create that first small purchase, and now you're a spender.
  • Whales: in games, a small group of players generates most revenue while the majority play free. In tech, a big free tier builds adoption, and the real money comes from companies and large teams buying enterprise plans at hundreds of thousands of dollars a year.

[14:06] Outro / teaser

• Notifications may be even more powerful than social media because they proactively influence behavior, and they're designed to. This links to Enrico's video on notifications.

Key takeaways

• Feedback weight should match action weight (hit stop ↔ toast, kill stop ↔ destructive-action confirmation).
• Teach by constraining choices, not by explaining (PvZ's 50-sun Sunflower ↔ Notion's starter page, ChatGPT's bare prompt box).
• Real gamification = the core loop (context, input, response, metaphor, rules, polish), not points and badges.
• Juice/craft is a pile of tiny, individually insignificant touches that change how a product feels.
• Easy to learn, hard to master via progressive disclosure (Pong, Civilization, Figma).
• Multiplayer is behavior design. Trustworthy undo (OT) encourages risk-taking.
• Monetization psychology is shared: icebreakers, selling at the moment of loss, whales ↔ enterprise.

2) Things mentioned

Tech products, companies and tools

Design concepts and terminology

• Hit stop / hitlag, boss stop, kill stop: frame-freeze feedback, scaled to the importance of the event.
• Toast notification, onboarding callout, destructive-action confirmation (type-to-confirm).
• Tutorial-less onboarding / teaching through constraints, contextual help ("speak only when stuck"), visual over textual onboarding.
• Game Feel loop: context, input, response, metaphor, rules, polish.
• Real gamification vs. PBL gamification (points, badges, leaderboards, mascots).
• Juice (color, tweening/easing, sound, particles, screen shake) = craft / micro-interactions.
• Bushnell's Law ("easy to learn, difficult to master") and progressive disclosure.
• Squircle / continuous corners (Apple's iOS icon shape).
• Operational Transformation (OT): algorithm family for concurrent edits and multi-user undo in collaborative editors.
• Bartle taxonomy of player types: Achievers, Explorers, Socializers, Killers.
• F2P monetization: icebreaker offer, selling progression, consumables, hard currency, selling at the moment of failure, whales, freemium → enterprise plans, $1 trials.
• Notifications as behavior-shaping tech (teaser for another video).

Games referenced

• Super Smash Bros. (hit stop), Kirby (boss stop), Grand Theft Auto V (death-cam footage), The Legend of Zelda, The Elder Scrolls V: Skyrim (HP management).
• Plants vs. Zombies (PopCap Games, 2009): tutorial-less level 1 and the Sunflower cost change.
• Super Mario Bros. (core loop and polish), Tekken (hitboxes in Game Feel), a Guitar Hero-style controller (input as centerpiece).
• Breakout clone (the "juice" demo).
• Computer Space (1971) and Pong (1972).
• Sid Meier's Civilization (Civilization VII footage): progressive unlocks and the tech tree.
• Minecraft: 2b2t anarchy server (since 2010), Journey (thatgamecompany, 2012).
• Clash of Clans (Supercell), Temple Run (Imangi Studios): monetization examples.

Books, talks and sources

• Game Feel: A Game Designer's Guide to Virtual Sensation by Steve Swink: the core-loop chart, Mario jump arcs, Tekken hitboxes.
• Masahiro Sakurai on Creating Games (YouTube series): credited for the kill-stop/hit-stop footage.
• Archival Plants vs. Zombies design talk (PopCap's George Fan, who has discussed this onboarding approach at GDC): the 50-sun Sunflower change.
• "Juice it or lose it"-style Breakout demo (Martin Jonasson & Petri Purho's well-known talk): the "juice" segment.
• Operational Transformation paper (OT originates with Ellis & Gibbs, 1989).
• Bartle player types (Richard Bartle, 1996 paper on MUD players).
• Developer clips about Journey and a mobile-game monetization talk (speakers not named on screen in the captions).

3) Biographies

Enrico Tartarotti (host)

Italian-born tech creator and designer behind the YouTube channel Enrico Tartarotti (about 255K subscribers at the time of this video). The channel goes "behind the scenes of the tech products you use every day" with heavily designed video essays on UX, product design and tech culture. He founded and builds Flask (flask.do), a review/feedback tool for video and creative assets that he uses to make his own videos. His company Rakugo Media handles sponsorships (enrico@rakugomedia.com). This video was written by Enrico, produced by Enrico and Bartek Malinowski, and edited by Seequence. Find him on X as @EnriTarta and on Instagram as @enritarta.

People and figures referenced

• Masahiro Sakurai: Japanese game director, creator of Kirby and director of the Super Smash Bros. series. His YouTube channel Masahiro Sakurai on Creating Games breaks down game-design techniques like hit stop. His footage illustrates the kill stop here.
• George Fan: creator and lead designer of Plants vs. Zombies at PopCap Games. Known for talks on teaching players without explicit tutorials, including the Sunflower and starting-sun rebalance described in the video. (The captions don't name the speaker. This attribution is context.)
• Nolan Bushnell: co-founder of Atari, co-creator (with Ted Dabney) of Computer Space (1971), and the executive behind Pong (1972, engineered by Allan Alcorn). Bushnell's Law, "easy to learn, difficult to master," is named after him.
• Steve Swink: game designer and author of Game Feel (2008), which formalized "game feel" and the input–response–context–polish–metaphor–rules model the video uses.
• Richard Bartle: British game researcher and co-creator of MUD1. His 1996 taxonomy (Achievers, Explorers, Socializers, Killers) is the "Bartle types" used for monetization segmentation.
• Martin Jonasson & Petri Purho: indie developers whose "Juice it or lose it" talk popularized "juice" with a Breakout-clone demo, the style of demo shown here. (Context attribution. The video doesn't name them in the captions.)
• Clarence "Skip" Ellis & Simon Gibbs: authors of the 1989 paper that introduced Operational Transformation for real-time group editors. Later Google products (Wave, Docs) built on OT.
• Sid Meier: designer of the Civilization franchise, the video's model of progressive discovery.
• Bartek Malinowski: co-producer of the video. Seequence: editing studio.