Skip to content
On this page

Technical Leadership: A Chapter Meeting Should Build Something That Lasts

Technical Leadership: A Chapter Meeting Should Build Something That LastsAI-generated image

In a recurring engineering chapter meeting I lead, I prepare topics, bring questions, and create space for discussion. Sometimes that leads to a useful exchange. Other times, I end up carrying most of the conversation.

The obvious response is to improve the facilitation. Better questions, stronger topics, a clearer agenda, more deliberate invitations to contribute. All of these can help. But there is a limit to what facilitation can fix when the meeting itself depends on the facilitator to generate most of its value.

That creates a subtle feedback loop. Participation is low, so the lead prepares more. The next meeting may improve, but it also becomes more dependent on the lead. Over time, the group can become accustomed to receiving a prepared conversation rather than shaping what happens in the room.

This is where meeting design becomes a leadership question. If the goal is greater ownership, asking people to participate more may have limited effect when the structure works perfectly well without their participation.

I am considering a different format.

Instead of using every recurring slot as another sync, I want to test focused workshops where the chapter works on a concrete problem together. The topic could be a recurring technical issue, a shared guideline that needs improvement, a framework capability worth exploring, or an architectural approach that several teams need to understand.

From a meeting that only shares information to a workshop where the same group of engineers works together on a concrete outcomeAI-generated image

Move the Work Into the Room

A sync and a workshop ask different things from the people attending.

A sync is useful when the main purpose is exchanging information or aligning on context. People can listen, respond when something touches their area, and leave better informed.

A workshop creates a different condition. The group has something to investigate, decide, test, or build together. Contribution becomes necessary to reach the outcome.

That difference matters because ownership is shaped partly by the environment in which we ask for it. If one person can prepare the agenda, provide the context, drive the discussion, and summarize the result, everyone else can remain relatively passive without preventing the meeting from succeeding.

I want to test whether changing the format reduces that dependency.

Chapter members can bring problems from their teams, organize sessions, compare alternatives, and contribute knowledge that others may not have. The chapter lead still provides direction, helps select problems worth spending time on, clarifies boundaries, and protects the purpose of the chapter. The aim is for the group to create more of the value while the lead continues to provide direction.

The principle is similar to giving a team a clear outcome and time boundary: leadership keeps the direction explicit while leaving more of the approach with the people doing the work.

A useful diagnostic follows from this:

If the person leading this meeting stopped preparing most of its content, could the group still create value together?

The answer says something about the structure, not simply about the motivation of the participants.

Test the Format Before Expanding It

Workshops are only a hypothesis. A workshop can be highly interactive and still accomplish very little.

The experiment therefore needs evidence beyond participation.

I want to start with one chapter and replace selected syncs with focused workshops. The interesting signals will appear after the sessions: whether an example gets reused, a guideline influences implementation, a decision prevents repeated debate, knowledge spreads beyond the people who originally held it, or chapter members begin bringing and organizing useful topics themselves.

These outcomes have something in common. They show that the value of the meeting escaped the meeting.

That is a stronger measure than whether the room was active for thirty minutes. It also gives us a reason to adjust or abandon the format if little carries into the work afterward. A workshop commitment, like a deadline, is real only when the group carries it after the session ends (A Task Has an Assignee. The Commitment Belongs to the Team).

What Should Exist Afterward?

Before each workshop, I want to define the expected value with one question:

What should exist after this meeting that did not exist before it?

The answer could be a decision, a tested approach, reusable knowledge, a shared technical understanding, or enough clarity for more people to act independently. The form matters less than whether it becomes useful afterward.

For me, that is becoming a useful test for recurring engineering forums more generally. If we keep asking people to spend time together, something should accumulate because those meetings continue to happen.

If you lead an engineering chapter, community of practice, or technical forum, what have you changed in its structure that helped the group create more of the value itself? I would be interested to hear what worked in practice.