Can You Accept the Three Grievances Before Becoming a Manager?

First grievance: You’re responsible for outcomes you didn’t directly create

As an individual contributor you have a clear safety boundary: you own a module, write code, deliver a task, and feel secure if you complete your part. A manager, however, must answer for mistakes made by sub‑team members, missed tests, optimistic schedules, or misaligned cross‑team collaboration, even though they didn’t do the work themselves. The article stresses that management is about building mechanisms—clear acceptance criteria, checkpoint reviews, capability assessments, and early risk communication—rather than merely avoiding personal errors.

Second grievance: Team achievements are credited to others, not you

Technical veterans often expect praise for their own technical output. After moving to management, the most frequent compliments target the growth of subordinates, the quality of their solutions, or the overall team performance. This can feel like a loss of personal glory, but the article argues that true managerial maturity means measuring success by how many people have become stronger because of your guidance, not by personal heroics.

Third grievance: You see problems but can’t bluntly call them out

Engineers tend to be direct—"the code is broken," "the design has holes." In a managerial role, such bluntness can damage relationships, morale, or future collaboration. The article illustrates scenarios (repeated missed deadlines, shifting product requirements, aggressive executive goals) where a manager must translate raw observations into facts, risks, options, and constructive recommendations, balancing honesty with diplomatic delivery.

Turning grievances into growth

The piece warns that accepting these frustrations does not mean endless tolerance. Persistent blame‑shifting or a toxic environment signals a deeper problem. Properly embraced, the three grievances become structural pressures that drive the manager to design better processes, develop independent team members, and convert emotion into decision‑making language.

Self‑assessment before stepping into management

Three quick questions help gauge readiness:

When a subordinate errs, do you instinctively blame or examine the underlying mechanism?

When a subordinate receives praise, do you feel genuine happiness or discomfort?

When you spot an unreasonable situation, can you turn your frustration into a concrete proposal?

If you answer affirmatively, you are more prepared to shift from an individual contributor mindset to a managerial one that balances truth‑telling with forward‑moving action.

Conclusion

Management is not a more prestigious path nor a fallback for engineers who can’t code; it is a role that demands continual handling of grievances, conflicts, and uncertainty. Accepting responsibility for outcomes you didn’t directly produce, celebrating team success over personal credit, and communicating truth constructively are the hallmarks of a mature technical manager.