Skip to main content

Module 5: Technical Leadership & Strategy: Worked Examples

Example 1: Replace a Goal List With Strategy​

Weak strategy: migrate to Kubernetes, improve reliability, and ship faster.

Coherent strategy: Diagnosis—deployments are slow because six tightly coupled services require a synchronized release and rollback. Guiding policy—reduce release coupling before changing orchestration. Coherent actions—measure coupling, establish contract tests, separate two highest-change capabilities, automate rollback, then reassess platform needs.

Tools are actions, not diagnoses.

Example 2: Write a Now/Next/Later Roadmap​

“Now” contains funded outcomes with owners and evidence. “Next” contains sequenced options whose discovery is underway. “Later” communicates direction without pretending commitment. Publish assumptions and movement criteria so the roadmap is a decision instrument, not a disguised deadline chart.

Example 3: Influence Without Authority​

Map decision owner, affected teams, incentives, objections, and evidence. Seek early dissent, run a reversible experiment, write the result, and give stakeholders a clear decision point. Repeating the technically correct answer louder is not influence.

Completion Standard​

  • Write a diagnosis/policy/actions strategy memo.
  • Build an outcome roadmap with movement criteria.
  • Facilitate and document one cross-team decision.