"Lead without authority. You may not have direct reports, yet you shape architecture, quality and the roadmap. Your leverage comes from artifacts, reviews and clear standards, not from title.I started by publishing a lightweight architecture template and a rollout checklist that the team could copy. That reduced ambiguity during design and cut review cycles by nearly 30 percent"
"Hold a high bar with clarity. Give specific, timely feedback on code and designs. When timelines are tight, present options with explicit tradeoffs and risks and recommend a path. I learned to stop saying "we'll figure it out later." Instead, I started offering two plans: plan A holds the date with reduced scope and known risks; plan B holds scope with a later date. That framing helped leadership make tradeoffs without surprise."
"Build in quality and operational excellence. Treat code quality, test coverage, observability, error budgets, release safety and rollback readiness as part of the definition of done. I wired these into code reviews and on‑call routines, so they persisted under pressure. Observability is not a feature; it's a nonfunctional requirement that must be planned and reviewed."
Lead without formal authority by shaping architecture, quality, and the roadmap through artifacts, reviews, and clear standards rather than title. Publish lightweight architecture templates and rollout checklists to reduce ambiguity and shorten review cycles by nearly 30 percent. Provide specific, timely feedback on code and designs and present options with explicit tradeoffs and risks when timelines are tight, offering a plan that preserves a date with reduced scope and a plan that preserves scope with a later date. Treat code quality, test coverage, observability, error budgets, release safety, and rollback readiness as part of the definition of done and embed them into code reviews and on-call routines. Run office hours, brown-bag sessions, post-incident lessons, and onboarding checklists to make learning routine. Allocate time across delivery, architecture, reviews, mentoring, and operational work to avoid burnout and cultural drift.
Read at InfoWorld
Unable to calculate read time
Collection
[
|
...
]