Dmitri Erchov rips operator playbooks’ blind spots

- On May 3 Dmitri Erchov publicly criticized standard operator playbooks for overlooking trade-offs like slower decision-making and hidden maintenance burdens. (x.com) - He recommended a staff-engineer mindset: clarify requirements, propose two to three architectures with explicit trade-offs, then build modularly to preserve options. (x.com) - The takeaway for founders: don’t treat playbooks as one-size-fits-all — surface trade-offs early and keep architectural options open while you scale. (x.com) (x.com)