The final lesson from Chapter 2 is subtle: the danger was not being a hero. The danger was assuming the system would always want one.
In fragile environments, hero behaviour can be adaptive. In mature environments, the same behaviour may raise questions. Why did the process need rescuing? Why was knowledge concentrated? Why did delivery depend on one person absorbing the risk?
Different systems value different signals
A fragile system may reward the person who can carry more. A mature system may reward the person who designs so less has to be carried by any one individual.
This can feel disorienting for capable professionals. What once created influence may now look like a design smell.
Moving from hero to architect
The shift is not to become passive. It is to move from rescue as identity to architecture as contribution. Step in when needed, but leave behind clearer ownership, better documentation, and less dependency.
That is how the strength travels without the old pattern becoming a ceiling.
Career lesson: Mature systems do not always need a hero. Often, they need someone who can make heroics unnecessary.