Personal insight: how I balance autonomy and alignment

By Václav’s request, I’m pulling together these points from a recent discussion in a closed Discord channel with @arseniy and @roxanneen on the balance of autonomy and alignment in the decentralized org we’re building together.

:brain::sparkles::point_up: These are my personal insights, shaped over three years of contributing here. They reflect my own perspective, don’t represent any group, and are open for forking, remixing, and thoughtful pull requests—signal, not doctrine.

1. I don’t wait for clarity from above.
I don’t ask for permission to begin. If I have to ask, I’ve already surrendered to a hierarchical mindset—trading agency for paralysis. That doesn’t mean acting alone. It means moving with clarity and letting alignment catch up.

2. If I see meaning—I say it. Align. Move.
Leadership for me isn’t about relaying messages up and down. It’s what we do when things get blurry. It’s turning conviction into action—anchored in shared purpose. I move first, but I stay open to course correction. That’s how I stay responsive and grounded.

3. Leadership isn’t granted—it’s earned.
I don’t follow job titles. I follow behavior. I join people whose actions resonate with me. And I try to be someone others can join—not by holding a role, but by holding a direction.

4. I shape my behavior to be joinable.
I move in line with our shared values—because I need allies to shift the stone in a direction that matters. I’m lucky: the org’s manifesto isn’t just something I respect—it’s a compass I already carried. If I want support, I make it easy for others to align.

5. The contract is the floor, not the ceiling.
That’s where I draw the line between being an employee and being a contributor. The contract provides structure so things don’t fall apart. Contribution adds motion so they don’t stand still. I choose to move with intention beyond the structure—without breaking it.

6. Be visible.
Like @arseniy said, every project deserves a single, clear doc. I treat myself as project. My skill matrix entry is my personal landing page.

I keep it updated with:
– What I do and who I am (project description)
– Where I’m heading (personal roadmap)
– Working agreements across the org (partnerships)
– Quotes from feedback (testimonials)
– Ways to connect and contribute (CTAs)

:bulb: Visibility isn’t ego-play—it’s infrastructure.

7. I strive for signals I’m off—not for signals I’m in.
If I believe something is meaningful and aligned, I move. I don’t wait for green lights. I move in public, leave a trail, and invite input. If someone thinks I’m off-track—we talk. Until then, I walk.

8. My motto this year:

Balancing autonomy and alignment is heavy lifting — if you want to lift, you have to pull that barbell from the center. :man_lifting_weights:

Sharing mine insights in case it helps others shape their own :brain: :sparkles:

5 Likes

Thank you for this write up! I had this in mind for a very long time - before IFT even:) But never really got to put it on paper:-) And you are way better with words than I am:)

I’ve been operating in this mode since my first proper IT job - I was supposed to maintain and implement some features into their app, but I got bored, so I spent a few days refactoring it to make it do stuff in parallel/pre-load (they worked with large images/scans ~100MB each -and loaded everything “on-demand” and it took ages) and everyone was excited. Same during my years at Red Hat - I just did things that seemed needed based on my experience and feedback from others and it worked great.

I’ve changed my role in Waku on LinkedIn to “Chaos Agent” after talking to Jazz and my ex-boss’s-boss’s-boss from Red Hat commented about how fitting that is:).

I think especially in Open Source world, the approach of “just do it as long as it benefits the project/team/org” is extremely important. My best example for this is when I asked someone from different team back at Red Hat to fix a bug I found and the reply was: “It’s open source, free to fix it yourself”. I took it as an insult back then, but I would take it as an opportunity today.

Jacek talks about this too - if you see something not being right in a library/project you depend on, it is partially your job to help make it better.

To sum up my random train of thoughts - 100% agree on all points:) As long as your goal in whatever you are doing is to make the whole org better, just do it and share the journey and outcomes!

5 Likes

Love this @Alisher & @vpavlin!

Fully agree: in open source and decentralized spaces, ownership starts when you care enough to act, not when someone hands you permission. Thanks again for sharing this!

4 Likes

:yellow_heart: Love this share, @vpavlin — your “just do what makes the whole org better” instinct hits home hard. I really felt the dancing star behind the Chaos Agent move.

“I tell you: one must have chaos in oneself to give birth to a dancing star.”
— From Thus Spoke Zarathustra, Nietzsche

4 Likes