Architecture Discussion is not Design Review

From today nows on, Site-Infra want to call Design Review as Architecture Discussion. Lolwat, what is the difference?

We want to rebrand the image to be more positive. Because many think design review is ritual to get approval to do something, to proceed to implementation. But, instead of viewing this activity as approval request, we want you to view this activity, Architecture Feedback Session, as opportunity to discuss, get feedback, gather common issue across teams, improve the design, and learn together.

By renaming this ritual, hopefully no more misleading pressure.
Reviewers from our team are also volunteers, no more pressure to reviewer as well.
Let's learn together during the session. Invites us! No pressure!


Interested to have discussion?

Here is the document on How to request architecture feedback session. Take a look inside, we changed the process a little bit, no more than 2 minute reading, I swear.

What to prepare for discussion?

To get architecture feedback, people would love to have requirement listed in a document. You can follow design document template in #design-review channel. Pssst, we need your contribution to improve that template.

Have a thought to improve this activity? Something to improve in this post?

We would love to get your feedback. Send us your feedback to #site-infra-channel or send it to one of site-infra member, including me as well.