Some roadmap meetings are saved by the quietest person in the room. Design wants a better experience, engineering is worried about technical debt, sales is carrying a promise made to a customer, and support brings in complaints that arrived that morning. Everyone has a point. Without someone calmly pulling the conversation back to the original question, planning can turn into a marketplace of reasonable distractions.
Reading the material on Tang Sanzang in Journey to the West, I found him more interesting than the familiar image of a weak monk who keeps getting captured. Through a workplace lens, he is not the strongest fighter, not the fastest incident responder, and not the person who understands every operational detail. But he is the one who keeps the final destination alive. In a long project, that ability is not glamorous, but it is hard to replace.
At work, a leader does not have to be the best coder, the best seller, the best designer, or the person who knows every corner of the operation. If they pretend to be all of that, the team becomes cramped. But if they cannot hold the direction, the team becomes scattered. A product team full of strong people without a shared goal is like a car where everyone touches the steering wheel a little. It may move, but each turn pulls it somewhere else.
What I want to keep from Tang Sanzang is the discipline of holding the mission. When the team is tired, this person reminds everyone why the work is worth doing. When too many options appear, this person helps remove what is attractive but off-track. When a big customer asks for a custom feature that could break the roadmap, this person asks a quieter question: does this serve the long road, or does it only make this week less uncomfortable?
The material also points to three very practical leadership habits: understand capability, delegate decisively, and trust while verifying. Tang Sanzang knows that Sun Wukong handles crisis, Zhu Bajie is more useful in social and practical tasks, Sha Wujing keeps the team steady, and the White Dragon Horse carries the infrastructure quietly. Modern teams are similar. Some people open the path, some guard quality, some calm stakeholders, and some keep operations moving without much noise. Assigning work without respecting real strengths is a fast way to make a good person look weak.
I have seen small versions of this mistake at work. A brilliant debugger gets assigned to write a long onboarding guide, then everyone is disappointed that the document feels dry. A strong communicator is made owner of a deep architecture decision, then has to depend on others at every step. A QA teammate who sees edge cases sharply is brought in only at the end of the sprint, when most decisions are already locked. Sometimes the person is not the problem. The problem is that the role was placed on the wrong shoulders.
Delegation does not mean disappearance. If a lead engineer is handling a production incident, the manager should not stand behind them and comment on every command. But the manager still needs visibility: which customers are affected, what the rollback plan is, who is communicating with stakeholders, and whether a postmortem will happen. Trust is not the absence of questions. Trust is asking questions that keep the system safe, not questions that prove the manager is still in control.
The difficult part is knowing when to protect a strong person and when to protect the shared standard. A star performer may save the team many times, but if they repeatedly make others afraid to speak, ignore process, or solve problems by hurting another team, their talent begins to create debt. Tang Sanzang needs Sun Wukong, but he still has lines that should not be crossed. Work is the same: gratitude for excellence does not mean placing someone outside the values of the group.
This note leaves me with a simple thought: a vision-holding leader is not always the person who says the biggest words. Sometimes they are the person in a tense meeting who can ask what the goal is, who should own which part, where delegation is needed, where verification is needed, and which boundary should remain intact even under pressure. A team on a long road may not only need more strong people. It may need someone calm enough to help strong people keep walking in the same direction.