起源故事 · 一张草图,比 40 页 PPT 管用
Origin Story · One Sketch Beats Forty Slides
皮克斯做每部动画前,先画故事板——上千张手绘小画,把整个故事一格一格钉在墙上。
为什么不直接写剧本?因为文字描述的「感动」是抽象的,画出来的「感动」是具体的,看一眼就知道这场戏成不成立。
这招后来被设计圈借了过来:一个团队向高管汇报新方案,第一次讲功能清单,被问得哑口无言;
第二次他们换成六格连环画:下班疲惫的妈妈、孩子哭闹、掏出手机、一键搞定、母子都笑了。
高管没等讲完就说「我懂了,这个要做」。同一个方案,讲成故事的那一版,让所有人瞬间站到了用户的鞋子里。
Before every Pixar feature, the team draws a storyboard — thousands of small hand-drawn panels pinned to the wall, the whole movie laid out frame by frame.
Why not just write a script? Because "emotion" described in words is abstract; "emotion" drawn on paper is concrete — one glance tells you whether the scene works.
Design teams borrowed the trick. One product team pitched a new idea to executives twice. Round one was a feature list — they got grilled into silence.
Round two was a six-panel comic: exhausted mom after work, kid crying, phone in hand, one tap, both smiling. The exec cut them off mid-sentence:
"Got it. Build it." Same solution — but the version told as a story put every listener instantly inside the user's shoes.
1 连环画故事板(点格切换 / 播放) Comic-Style Storyboard (click a panel / press play)
—2 这一幕:画面 + 旁白 This Scene: Picture + Voice-over
画面里发生什么What's happening on screen
—
旁白(讲给客户听)Voice-over (what you say to the room)
—
3 现实里的故事板 Storyboarding in the Real World
故事板:用连环画分镜把一个体验顺着时间画出来,像给方案拍一部短片的分镜稿。
Storyboard: a sequence of panels drawn along a time axis — the shot list for the short film your solution wants to be.
场景化沟通:不讲功能清单,讲「谁在什么情境下用它」,让听众秒进入用户视角。
Scene-based pitching: skip the feature list, anchor on "who is in what situation," and the audience drops into the user's perspective immediately.
方案叙事:场景→问题→方案→结果的叙事结构,比平铺直叙的需求文档更有说服力。
Narrative arc: Scene → Problem → Solution → Outcome — a structured story persuades far better than a flat requirements doc.
打动干系人:高管和客户记不住参数,但记得住一个具体的人、一个被解决的难题。
Move the stakeholders: execs and customers forget specs — they remember a real person with a real problem solved.
一句话In One Line
一个方案有没有被真正听懂,区别往往不在内容,而在载体。
功能清单调动的是听众的「分析脑」,要费力把抽象映射回现实;故事板调动的是「画面脑」,
一组画面让人不假思索就站进了用户的处境。当对方能在脑子里看见「那个疲惫的妈妈被你的方案救了」,
说服就已经完成了一大半。记住:用场景讲方案——你卖的从来不是功能,而是一个被你改写的、更好的故事。
Whether a solution actually lands has less to do with the content than with the vessel.
A feature list activates the audience's analytical brain — they have to translate abstractions back into reality. A storyboard activates the picture brain —
a few panels and listeners step into the user's shoes without thinking. The moment they can see "that exhausted mom rescued by your solution" in their head,
half the persuading is already done. Remember: pitch the solution as a scene — you were never selling features, you were selling a better version of someone's story.
常见误用Common Mistakes
纠结画功,画得不好看就不敢画。火柴人就够了,故事板要的是叙事清晰,不是美术水平。
Sweating the art and refusing to draw because it won't look good. Stick figures are enough — a storyboard is judged on narrative clarity, not draftsmanship.
每格都堆满功能细节。一格只讲一个意思,围绕「用户的处境与感受」展开。
Cramming every panel with feature details. One panel, one beat — keep the camera on the user's situation and feelings.
只画方案多牛,不画用户原本的痛。先铺场景与问题,方案才有对照,结果才有冲击力。
Only drawing how great the solution is, never the original pain. Set up the scene and the problem first — only then does the solution have contrast and the outcome have impact.