Set a ten-minute timer and produce ten distinct approaches to the same problem, banning self-editing until the bell. Start each line with a verb to force momentum. After the timer rings, circle two wild entries that feel risky yet intriguing. Expand each into three bullet points specifying audience, channel, and measurable outcome. The quota counters perfectionism while the clock keeps energy high, making surprise your most reliable collaborator today.
Set a ten-minute timer and produce ten distinct approaches to the same problem, banning self-editing until the bell. Start each line with a verb to force momentum. After the timer rings, circle two wild entries that feel risky yet intriguing. Expand each into three bullet points specifying audience, channel, and measurable outcome. The quota counters perfectionism while the clock keeps energy high, making surprise your most reliable collaborator today.
Set a ten-minute timer and produce ten distinct approaches to the same problem, banning self-editing until the bell. Start each line with a verb to force momentum. After the timer rings, circle two wild entries that feel risky yet intriguing. Expand each into three bullet points specifying audience, channel, and measurable outcome. The quota counters perfectionism while the clock keeps energy high, making surprise your most reliable collaborator today.
Write a one-paragraph brief that guarantees failure: confuse users, waste budget, and delay launch. List three decisions that cause the disaster. Now invert each decision into a protective rule, converting mistakes into guardrails. This playful reversal surfaces practical constraints worth adopting immediately. Share your before and after briefs with teammates, vote on the sharpest guardrail, and codify it into your checklist so good intentions become repeatable, observable behaviors on every project.
Choose one absurd requirement, like instant global delivery with no cost. You cannot build it, yet you can map a flow that moves closer. Sketch a three-step workaround leveraging partnerships, sequencing, or clearer expectations. The impossible target clarifies trade-offs and highlights where communication beats code. Present your flow to a skeptic and refine based on their toughest question. Constraints become guides, pointing to practical paths that still delight users meaningfully.
Take an existing design, script, or plan and remove one major component you believe is essential. Now recompose the system so the promise still holds. This forces compact narratives, resilient architectures, and elegant defaults. Track what improved when the clutter vanished and where pain emerged. Decide whether to keep the subtraction, replace it with a simpler element, or restore selectively. The discipline of less often reveals a more persuasive core.
All Rights Reserved.