Explain your decisions and their results

Explain your decisions and their results

Lesson 4 of 12~4 min readPremium lesson preview
In this lesson3 sections

Your listener needs enough background to understand a decision, then enough detail to understand why you made it. A chronological account of every meeting usually gets in the way.

Build around the decisions

Use four checks while drafting: context, actions, results, and learning. Often called CARL, this is a way to inspect an answer, not a script you need to recite. STAR, which separates situation and task before actions and results, can serve a similar purpose. Whichever you use, make your responsibility and reasoning explicit.

Keep the context brief: the problem, its consequence, your role, and the constraint. Spend more time on what you investigated, considered, decided, communicated, and changed. Report the outcome with the limits of your evidence. Finish with a specific lesson and, where possible, its later application.

Practice 07: Explain a technical decision through its trade-offs

Choose a project where more than one approach was reasonable. What did you compare, which constraint determined your choice, and what did you give up?

Follow-ups: Which assumption was least certain? What did a teammate contribute? What would have made the rejected option preferable?

A worked answer

The following fictional example concerns a support-reporting workflow:

The rest of this lesson is for Premium members

Premium opens every lesson in this course, along with all questions and solutions on PracHub.