You Have Been Asked to Represent Your Team at the Architecture Review

Your company has a fortnightly architecture review. Leads and senior engineers from every team, an hour on a call, proposals for anything that crosses team boundaries. Your lead has too many meetings already, so she asks you to go instead. From now on, you are the team's voice in that room.

It is tempting to treat this as a seat to sit quietly in. It is actually one of the best views of the whole company you will get at your level, if you use it properly.

Remember who you are speaking for. In that room your opinion counts because it carries your team's knowledge, not because of your title. So before each session, read the agenda and spend ten minutes with your team on anything that touches your systems. Does the new event format break our consumers? Would that shared cache change our latency? Walk in knowing what your team thinks, not only what you think.

Be clear about which is which. Our team is worried about the migration timeline is a different statement from I personally prefer the other database. Mixing them up is the fastest way to lose your team's trust, or the room's.

Speak when your systems are affected, even if the people presenting are far more senior. You are often the only person present who knows that a certain service still depends on the old format. Saying so early saves weeks of work. Saying it after the decision is made just makes people tired.

Then carry things back. After each session, send your team three lines. What was decided, what affects us, and what is coming next month. Most engineers never hear about decisions until the work lands on them. Your summary turns surprises into planning.

Watch how the experienced people argue. How they frame trade offs, which questions they ask of every proposal, when they let something go. A year of that hour is an education in technical judgement that is very hard to get anywhere else.

And keep a short note of what you raised and what changed because of it. When your lead writes your next review, that note is evidence of a kind of influence that usually goes unrecorded.

– Asael Shinder