What Your Former Boss Gave You vs. What Your New Boss Can Offer: Lessons on Leadership and Decision Power

01 Leadership Plays the "Game of Power"

After a company‑wide restructuring that merged two finance‑tech groups, the author’s team was reassigned to a different department under a new technical director. While the day‑to‑day responsibilities remain unchanged, the reporting line has shifted, prompting a deeper look at what a new direct manager means for personal development.

The author argues that changing a direct supervisor is essentially changing one’s development environment. Career prospects are not determined by company size; the organization merely provides a starting line. Even at a giant like Alibaba, an individual may still be limited to low‑level tasks, just as a founder cannot personally guide every project.

Consequently, the direct manager becomes the true "boss" whose decisions shape one’s opportunities. The author thanks the former leader for mentorship that helped him grow from a newcomer to the technical lead of the finance‑and‑payment team, collaborating with product managers across multiple business lines and overseeing dozens of product iterations.

During that period, the former leader introduced core e‑commerce concepts such as the "three‑flow order" model, illustrated in the following diagram:

The most valuable resource the former boss provided was "decision resources"—the authority to make choices. The author explains that decision resources are essentially decision‑making power: having the right to say "this is my call". However, such authority is not handed out lightly; it must be earned through competence and reliability.

To become a trusted subordinate, the author outlines three unavoidable steps:

Achieve established goals to gradually build trust.

Earn decision resources by taking on more responsibilities.

Seek regular evaluation and feedback to identify strengths and areas for improvement.

02 Management Without Technical Depth Is Counterproductive

The new leader, who rose from backend development to full‑stack expertise and now serves as a technical director, shared a "3P1T" theory comprising People, Product, Project, and Technology. The framework is described as follows:

People: Manage people by managing work; understand team needs. The leader interviewed over a hundred candidates in a year, retaining only 10% and filtering out those who entered management within five years.

Product: Know the product better than the product manager to bridge product and technology.

Project: Obtain PMP certification, systematically learn project management, and learn from mistakes to recognize pitfalls.

Technology: Master technology deeply, argue convincingly with architects, and guide the team with strong communication and a broad technical vision.

He also advises that advancing to architect before becoming a technical director is easier because technical depth is a prerequisite for senior leadership. The author likens this to running a public account: without solid content (technology), no amount of promotion (management) can succeed.

For the first five to seven years, the recommendation is to focus on expanding technical breadth and depth rather than jumping into management, because "doing management without technology is like cheating".

03 Final Thoughts

The author suggests documenting personal reflections as a "product" to hold oneself accountable and gather feedback. He shares a personal task‑management diagram:

The diagram categorizes tasks into those that can be deleted, must be done personally, can be delegated, or can be postponed, emphasizing self‑management before team management.

He concludes by urging readers to seize opportunities, improve themselves, and share feedback, reinforcing the belief that balancing technical expertise with managerial skills is essential for long‑term success.