Latest / Tech Leadership with Fexingo: Engineering Managers, CTOs, and Technical Leadership Conversations
How One CTO Cut Decision Debt With RFCs
Lucas and Luna break down how a CTO at a mid-stage SaaS company used lightweight Request for Comments (RFCs) to eliminate decision debt. They walk through a real example from a team that was paralyzed by recurring architecture debates until they enforced a written proposal process. The hosts discuss why RFCs force clarity, how to keep them short (under 500 words), and why the best RFCs include a concrete 'no' section. They also share a simple rule: any decision involving more than two engineers requires an RFC. No consultants, no tools — just a habit that saved one engineering org roughly 200…
The skinny
The skinny isn't ready yet — notes appear once the transcript is processed.