The quickest way to kill a team is by setting a bar where ideas are "good enough" to share.
What I mean is that, if you don't encourage people to share ideas, they will stop.
Today it might be an idea you think is dumb. Tomorrow it could be an idea that saves your ass.
Always "yes, and" every suggestion. The "yes" validates their contribution, the "and" lets you expand and start a conversation. This conversation is where you improve the idea until it's good. Together.
Do not superficially "yes and" when you want to judge or critique. Even a 12 year old can see through your bullshit.
You have to actually engage every idea constructively. This is hard. You have to try.
A good trick is to ask questions. Try to learn more about the idea and how it works. Keep asking until the pieces fit together in your mind. If they don't, ask for a concrete example.
Asking for examples gives people the opportunity to try their idea. If it works, you'll be surprised. If it doesn't, everybody learns.
Great success either way.
If the result is catastrophic, just don't merge the code ¯\_(ツ)_/¯
Yes this approach can be exhausting. And it doesn't always work. You don't have time to discuss every idea when the patient is bleeding out on the table.
But even then, a team that's not afraid to say "Yo you're standing on the tube, no wonder the patient can't breathe" is your greatest asset. Don't be like those airplanes that crashed because the captain is always right.
Cheers, ~Swizec
PS: I like to start discussions by suggesting the dumbest idea possible. Rip the bandaid off and get things started. Now everything's an improvement 🤘
Continue reading about The quickest way to kill a team
Semantically similar articles hand-picked by GPT-4
- Let juniors speak first
- 5 tips for effective standups
- The art of the cowboy merge 🤠
- Coordinating at the end is too late
- What's more productive, a team or a talented soloist?
Become a *true* Senior Engineer
Get promoted, earn a bigger salary, work for top companies
Getting that senior title is easy. Just stick around. Being a true senior takes a new way of thinking. Do you have it?
The Senior Minset email crash course
Get a free chapter from the Senior Engineer Mindset book and a sample audiobook chapter, followed by a Senior Mindset 101 email course.
You'll get insights to apply at your work right away.
Have a burning question that you think I can answer? Hit me up on twitter and I'll do my best.
Who am I and who do I help? I'm Swizec Teller and I turn coders into engineers with "Raw and honest from the heart!" writing. No bullshit. Real insights into the career and skills of a modern software engineer.
Want to become a true senior engineer? Take ownership, have autonomy, and be a force multiplier on your team. The Senior Engineer Mindset ebook can help 👉 swizec.com/senior-mindset. These are the shifts in mindset that unlocked my career.
Curious about Serverless and the modern backend? Check out Serverless Handbook, for frontend engineers 👉 ServerlessHandbook.dev
Want to Stop copy pasting D3 examples and create data visualizations of your own? Learn how to build scalable dataviz React components your whole team can understand with React for Data Visualization
Want to get my best emails on JavaScript, React, Serverless, Fullstack Web, or Indie Hacking? Check out swizec.com/collections
Did someone amazing share this letter with you? Wonderful! You can sign up for my weekly letters for software engineers on their path to greatness, here: swizec.com/blog
Want to brush up on your modern JavaScript syntax? Check out my interactive cheatsheet: es6cheatsheet.com
By the way, just in case no one has told you it yet today: I love and appreciate you for who you are ❤️