Strategy at organization scale
On This Lesson 4 topics
This lesson is planned. The outline below lists the topics it will cover. The full lesson has not been published yet.
In this lesson
define technical strategy as a short, evidence-based argument about where engineering effort goes.
Planned topics
- A strategy has three parts: a diagnosis of the situation, guiding policies, and coherent actions.
- It is not a list of projects or a wish list of technologies.
- Its value is in the choices it rules out as well as those it makes.
- Good strategy is short enough that every team lead can explain it.
Draft outline details
Demonstration
a one-page skeleton with headings Diagnosis, Guiding policies, Actions, Trade-offs, filled with one line each for Platform 2.0.
Check your understanding
What separates a strategy from a roadmap?
Show answer
A strategy explains why and what is excluded; a roadmap only lists what and when.
Practice
Apply this lesson with the module's lab, exercises and quiz.
Marking a lesson complete is optional and you can undo it any time. Your progress stays in this browser.