Elevation is a change in altitude, not a change in loyalty to craft. You still care whether the system is right. You now also care whether it is the right system. That sounds obvious. In practice, most strong engineers still optimize the local maximum they can see from the pull request.
This chapter teaches you to zoom out on purpose: customer, constraint, cost, and second-order effects. You will learn to sit in rooms that used to feel like a distraction and treat them as data. Elevation is how an engineer becomes someone an executive can think with.
The work is uncomfortable because it makes you a beginner again. That is the point. Leaders who refuse to be beginners stay specialists — valuable, and eventually boxed in.
Lessons
- Altitude is a skill. Practice it like a language.
- The system is larger than the service you own.
- If you cannot explain the work to a non-engineer, you do not yet own the work.
Questions
- What would a skeptical CFO ask about your current project?
- Which meetings do you avoid, and what information lives only there?
- What are you optimizing that the customer cannot feel?
One-page altitude
- Take a current initiative and write: customer, revenue or risk, time, and the technical bet.
- Cut it to 150 words.
- Read it to someone outside engineering. Revise until they can repeat the bet.