Low diatribe

Unpolished thoughts on leadership and growth

Lead quietly, grow imperfectly

I built Low diatribe around the philosophy that leadership isn't always loud and to embrace the fact that growth isn't always pretty. The work hums at a lower frequency: steadier, truer, and easier to build trust around.

This isn't about being passive or invisible. It's about recognizing that the most powerful leadership often happens in the spaces between the grand gestures: in the daily choices, the small corrections, the willingness to show your work before it's perfect. It's about clearing space for others to find their voice and watching them discover capabilities they didn't know they had.

What has proven effective for me:

Favor presence over performance. I show up consistently rather than dramatically. I've learned to be the person others can count on to listen, to think things through, to care about getting it right. Presence builds trust; performance builds applause. Only one of those lasts. When I'm present, I notice what others need to succeed.

Show all the drafts. I let people see my thinking in progress, make my process as transparent as possible. I share the messy middle, the false starts, the "I'm not sure about this part yet." When I model vulnerability through imperfection, teams learn it's safe to iterate, to experiment, to improve rather than pretend. My willingness to be wrong gives them permission to be continuously learning, to iterate on their thinking, to treat mistakes as data rather than failures.

Build others up before building up. I look for moments to amplify someone else's idea, to give credit where it's due, to ask the question that lets them shine. The multiplier effect of a cohesive team comes from each person feeling seen and valued for their unique contribution. When people feel built up, they build up others.

Make small, reversible bets and tune forward. This has been the hardest for me. Instead of betting everything on the perfect plan, I make smaller moves I can learn from, test assumptions early, and adjust based on what I discover. Growth happens in the tuning, not in the grand reveal, and I include my team in that learning process.

Why it matters:

I've learned that trust compounds when people see process, not just polish. When my team watches me work through problems, admit uncertainties, and course-correct based on feedback, they learn that it's safe to do the same. They see that excellence comes from iteration, not just inspiration.

I've found that vulnerability becomes a leadership tool when it creates psychological safety. When I admit I don't know something, I give others permission to not know things too. When I ask for help, I model that asking for help is strength, not weakness. This creates the conditions where a team can function as more than the sum of its parts.

I don't need to have all the answers upfront. I need to be willing to find them together, to grow imperfectly in front of others, and to create environments where everyone can do their best work without the pressure of immediate perfection. I've learned that my job isn't to be the smartest person in the room: it's to make the room smarter.

In a world that celebrates the loud and the certain, I've found profound power in leading quietly and growing imperfectly. I'm not saying that all shenanigans are bad: I just prefer to save them for rollerskating around Rockefeller Plaza in a Big Red Dog costume. Spectacle burns bright for a moment, leaving briefly seared images that inevitably fade. The quiet frequency builds lasting things, cohesive teams, and the kind of trust that multiplies capability across every person who touches the work.

Silvaris. Strength in quiet. Quiet as revolution.

heart

Thoughts?

Authenticate below to join the conversation.

Erica

Yes, all of this. Thank you. I completely agree. Some points: performance is one thing, but comprehensive understanding by the team is another, yes. But when the team doesn't care about comprehending, is that my fault for trying over and over to mentor kindly, or my fault for succumbing to frustration and being less motivated to care about what others can actually understand at some point, or their fault for not paying attention and taking notes, as I've recommended many times? Complexity is necessary, more often than not, for business and technical reasons, and we try to simplify where we can, but we all know it ain't that simple to simplify, or even possible in some scenarios. Given sufficient time and resources, things can be simplified, to some degree. But there will always be complexity as businesses shift, technology shifts, etc.