Diagnosis
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
write a diagnosis that names the few problems that matter most.
Planned topics
- Gather evidence: incident history, delivery data, cost, obsolescence calendar, team interviews, business plans.
- Name the critical challenges in plain language and rank them; not every problem is a strategic one.
- Separate causes from symptoms: slow releases may come from coupling, not from slow engineers.
- A good diagnosis lets readers predict the policies.
Draft outline details
Demonstration
a diagnosis outline for Commerce 2030: three challenges (end-of-life core services, coordination load at 25 teams, marketplace load and compliance), each with evidence.
Check your understanding
Why separate causes from symptoms in a diagnosis?
Show answer
Policies aimed at symptoms do not fix the underlying problem.
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.