Brainstorming Better Together, Alone

Pain points, efficiencies, problems, desires. Opportunities come in all shapes and sizes. Regardless of what they look like or what we call them, it's our job to figure out the best ways to tackle them.

Brainstorming is common practice in the workplace. You get a group together and rapidly come up with ideas. In theory, this is a dynamic affair where folks are engaged and all voices are heard, tapping into everyone's unique perspectives and talents. A lot of ideas are generated, refined through debate, and the best ones bubble to the top.

In practice, this is a dull affair. The most vocal and the most senior dominate. The junior and the introverted passively nod along. And everyone else, simply coasts through. We wrap with a measly number of ideas, stemmed from a concentrated perspective, untested by challenge.

To avoid this trap, turn brainstorming on its head. Start alone.

Instead of starting cold with everyone, warm up solo. Have each participate generate an individual set of ideas. Give them the space to tap into and explore their unique points of view first. Then when coming together, have everyone present. This will paint a much richer picture of the solution space. It will eliminate the social loafing and deference to authority that is so common with groups. It will drive up engagement and debate, sparking more ideas of higher quality.

Comments

Today's Special: Humble Pie

You champion a project, fight for an idea, and then...reality sets in. That churning in your stomach isn't butterflies, it's the realization you've missed the mark. Pride will puff up your chest, and kick in the "defend at all costs" instinct. But arguing with the umpire never changed a call. Admitting you're wrong isn't a sign of weakness. It can strengthen your professional standing. In a world obsessed with the illusion of infallibility, the courage to adjust course is a breath of fresh air. It shows you're confident enough to be wrong, and adaptable enough to learn from it. Do your research, think critically, and stand behind your decisions. But when the data whispers (or screams) otherwise, don't be afraid to swallow that slice of humble pie. Be the first to acknowledge. Don't wait for someone to point out your mistake. Be open, take responsibility, and most importantly, focus on what you're going to do to address it. Don't dwell ...

Starting Really Really Small

On your desk is one of the most intimidating sights known to man. A blank page. The prospect of filling it up with anything resembling decent seems insurmountable. Staring at the long road ahead fills you with anxiety and dread. The first step is the most difficult. So we procrastinate. We " research ", we " prep ", we " plan ". We do everything except tackling the problem. We avoid the pain for as long as we can. To make a blank page less intimidating. Tear it in half. There, half as scary, twice as easy. Still too much? Do it again. And again. Keep doing it until the task is so small that it's too easy not to do. Getting starting is the hardest part. So make the hardest part as easy as possible. This doesn't guarantee amazing results, but it gets you in the game. You can't win if you don't play.

Why We Shouldn't Be Afraid of Ambiguity

Ambiguity. That fuzzy monster that chases us down darkened hallways, whispering doubts about our roadmap and feature sets. You know the feeling. You constantly wrestle with unknowns: Will users like this? Is this the right direction? Frankly, if you had a nickel for every time the answer wasn't crystal clear, well, you might actually want to chase that ambiguity down the hall. But here's the thing: ambiguity isn't your enemy. It's your dance partner. Innovation rarely happens in a land of perfect clarity. Sure, there's a time for well-defined processes. But when you're creating something new, there are bound to be more questions than answers. The key is to learn to waltz with the unknown . Embrace the experiment. Don't be afraid to throw some spaghetti at the wall and see what sticks. Focus on outcomes, not outputs. Don't get hung up on features. What problem are you trying to solve? How will you measure success? Get comfortable with "go...

Herman Ye

Search