Our most critical habit is a "write-first" culture driven by lightweight requests for comments. Our team is too distributed for synchronous meetings to be the primary alignment tool. Before building new services or features, engineers write a brief technical proposal and circulate it for async feedback.
Crucially, this format democratizes the conversation. It gives everyone the space to digest information and contribute feedback on their own time, rather than only hearing the loudest voices in a meeting. It might sound counterintuitive, but slowing down to write actually speeds us up.
Once aligned, these proposals graduate into architecture decision records, creating a permanent history of our choices. By solving architectural debates during the design phase rather than during the build, we avoid mid-sprint blockers and costly rework.
We measure success through team velocity and delivery timelines. While no timeline is perfect, the RFC process has effectively eliminated the massive, late-stage rewrites that used to jeopardize our release dates and cause frustration.