Niko Heikkilä

October 8, 2022

V for Vulnerability

Effective teams are made stronger by nurturing safe environments where people can become vulnerable.

No vulnerability, no psychological safety. No psychological safety, no experimentation of new ideas. No new experiments, no continuous improvement. No continuous improvement, no mastery. No mastery, no purpose, nor motivation. No motivation and you might as well switch companies or careers.

Here's some homework for your next working day. First, admit to your team and colleagues something where you are bad at, or confess that one moment you screwed up. The "worst" consequence is that people smile and nod at you; the best is that people are encouraged to share their own experiences, and you have already contributed towards a stronger team.

The more vulnerable we allow ourselves to be, the fewer ego games there are in play. So it's a win-win situation for everyone.

About Niko Heikkilä

Software Craftsman and Extreme Programmer. Currently shipping quality code at Futurice. Building proprietary software for a living and loving it as much as free and open-source software. Linux, Windows, and macOS user. Follow this blog for insights on TDD, BDD, DDD, mob programming, technical agility, lean software development, continuous integration, and delivery.

For shorter posts, check my account on Mastodon.