Week 2 · Production Python · about 3 minutes
What you will be able to do
Write an executive update that starts with the decision, then up to three reasons with numbers.
The idea
Engineers tell stories in order: what we checked, what we found, what we suggest. Executives stop reading before the end.
Flip it. Start with the recommendation or the decision you need. Follow with up to three reasons, each one line with a number. Put the detail below, or offer it on request.
This is the Pyramid Principle. If they read only the first line, they still know what to approve.
Recommendation: approve a one-week index fix on the risk database.
Why:
1. The daily report drops from 8 hours to under 15 minutes.
2. Two missing indexes cause 90% of the query time.
3. No new hardware or licences are needed.
Detail: query plans attached.If they read one line, make it the one they need to decide.
Key takeaways
- Open with the decision you need.
- Give up to three reasons, each with a number.
- Offer detail; don't lead with it.
Part of the Forward Deployed Engineer roadmap. New to the role? Start with what a Forward Deployed Engineer does.