CJW–05
technical credibility · people · systems
management without losing the craft
guide
V.0.1.0
my leadership approach is rooted in technical credibility, accountability, clarity, and development of people. i manage engineers spanning sre and software disciplines while staying close enough to the technology to evaluate risk and set direction.
philosophy
1.1
give engineers ownership
create context, remove barriers, establish expectations, and let engineers own technical solutions. management should amplify ownership, not absorb it.
1.2
understand the technology
a technical manager does not need to be the strongest engineer on every stack, but should understand architecture deeply enough to ask useful questions and judge risk.
1.3
build systems, not heroics
reliable organizations should not depend on a few people remembering how everything works. invest in automation, documentation, standards, runbooks, observability, and clear ownership.
1.4
develop people
leadership means creating opportunities for engineers to grow into larger technical and organizational responsibilities — coaching, performance, and career paths included.
platform ownership vs application ownership
a recurring leadership objective is clarifying boundaries. the platform organization provides secure, reliable, documented, reusable platforms and supported patterns. application teams remain responsible for understanding, configuring, and operating their workloads.
platform owns
- —platform products and paved roads
- —reliability and lifecycle of shared services
- —security and governance integrations
- —documentation, onboarding, and supported patterns
application owns
- —workload design and configuration
- —application-level reliability
- —consuming platform patterns correctly
- —operating what they ship
platform philosophy
standardization
documented, supported patterns instead of solving the same problem differently for every customer.
self-service
paved roads that let developers accomplish common tasks without a platform engineer performing every deployment.
gitops
desired platform state in version control, reconciled through automation wherever practical.
automation
reduce human variation by automating repetitive operational work.
reliability
observability, alerting, slos, capacity, lifecycle, and incident learning as continuous improvement loops.
security by design
integrate security into platform architecture rather than bolting it on later.
developer experience
documentation, examples, templates, onboarding, and developer hub capabilities are part of the platform itself.