In Software Planet Group we conduct a large number of interviews for managerial positions across different types of IT projects. Over time, a pattern has become increasingly clear. Many candidates arrive with impressive CVs, certifications, frameworks and metrics at their disposal. Yet during deeper conversations, the same structural weaknesses appear again and again. These are not minor gaps in knowledge. They are recurring positioning errors that reflect how people understand the role of a manager in the first place. We also observe the same anti-patterns in managers who join us from other organisations: strong process vocabulary, weak systemic control; polished dashboards, fragile decision-making. This article is an attempt to articulate those patterns clearly and to contrast them with what we believe constitutes effective managerial positioning in complex IT environments.
One of the most common misconceptions is the belief that tools define the manager. Candidates often describe their achievements through the processes they introduced: Scrum adoption, KPI systems, reporting transparency, improved velocity tracking. These are not irrelevant achievements, but they are not the essence of management. Process is an instrument. Metrics are sensors. Dashboards are visualisation layers. None of them take responsibility for outcomes. When a project enters turbulence, frameworks do not make trade-offs, and charts do not absorb accountability.
Effective management begins with ownership of results within constraints of time, budget and quality. A mature manager understands that process is adjustable. If it stops serving the objective, it must be redesigned. The role is not to defend a framework but to ensure that the system produces value. Instruments amplify capability, but they do not substitute judgement. In the hands of a weak manager, KPIs create bureaucratic comfort. In the hands of a strong one, they function as early-warning mechanisms that inform timely intervention.
Another recurring anti-pattern concerns the notion of strategy. Many managers speak about “project strategy” as though it were a single coherent direction that satisfies all stakeholders simultaneously. This assumption is structurally flawed. Strategy is never universal. It is always addressed to a specific group and shaped by its interests.
There is a strategy from the company’s perspective, where profitability, risk exposure and long-term positioning matter. There is a strategy from the client’s perspective, where value delivery, speed and reliability dominate. There is a strategy from the team’s perspective, where sustainability, cognitive load and professional growth determine viability. These strategies do not automatically align. In fact, they often conflict.
The immature manager attempts to blur these tensions into a diluted compromise so that everyone remains partially satisfied. The result is predictable: reduced margin, diluted client value and gradual team fatigue. The mature manager recognises that management is the continuous alignment of competing priorities. At different moments, decisions may legitimately favour one side over another. What matters is that these choices are conscious, explicit and grounded in a clear understanding of systemic consequences. Project success is not universal happiness. It is the dynamic equilibrium of business outcome, client value and team sustainability.
Closely related to this is the overemphasis on communication as the core managerial competence. Many candidates highlight their ability to facilitate discussions and build rapport. Communication is important, but it is secondary. Projects rarely fail because people refuse to speak. They fail because decisions are postponed, avoided or softened to the point of ineffectiveness.
Management requires decision-making under uncertainty. Information is always incomplete. Data is always partially ambiguous. Waiting for perfect clarity is, in practice, a decision to allow entropy to accumulate. Strong managers do not confuse ambiguity with paralysis. They evaluate signals, assess risk exposure and act before deterioration becomes irreversible. Communication supports decisions; it does not replace them.
At the foundation of all these capabilities lies what is often vaguely described as “analytical ability”. In interviews this term appears frequently, yet it is rarely defined precisely. In the context of management, analytical capability is not about processing spreadsheets or generating reports. It is the capacity to assemble fragmented signals into a coherent causal model and to anticipate likely consequences.
Most managers operate at the level of observable facts. Velocity fluctuates. Client requests increase. Tension emerges in the team. Each element is treated separately. A manager with developed analytical synthesis sees patterns instead of isolated events. He recognises expectation misalignment before open conflict occurs. He detects scope drift before margin erosion becomes visible. He anticipates quality degradation before defects accumulate beyond control.
This ability is partially built through exposure to diverse scenarios and rigorous post-mortem analysis. Experienced PMO professionals often demonstrate stronger pattern recognition precisely because they have observed multiple project trajectories and their outcomes. They intervene earlier not because they possess privileged information, but because they identify structural similarities across cases. Managers who lack this capability frequently react too late. By the time a problem becomes obvious to everyone, corrective action is already costly.
When we ask candidates to define project success, the difference in cognitive maturity becomes explicit. A superficial answer frames success as stakeholder satisfaction. A more grounded answer recognises structural constraints. Project success means achieving business objectives while delivering measurable client value and preserving the team’s long-term capacity to perform. This definition accepts tension as inherent rather than accidental. It acknowledges that trade-offs are unavoidable and that short-term discomfort may be necessary to protect systemic viability.
These distinctions become particularly visible during interviews. Weaker candidates focus on activities: ceremonies conducted, tools implemented, frameworks followed. Stronger candidates describe decisions made under pressure, conflicts between stakeholder interests, trade-offs accepted and risks mitigated. They speak not about how smoothly everything proceeded, but about when plans failed and what intervention prevented systemic breakdown. The contrast is not stylistic. It reflects fundamentally different mental models of management.
Ultimately, the difference between administrative coordination and real management lies in positioning. A manager is not a guardian of process purity, nor a spokesperson for a single stakeholder group. A manager is a system integrator operating under uncertainty. He aligns competing strategies, interprets weak signals before they escalate into crises and takes responsibility for outcomes rather than activities.
In our experience at Software Planet Group, the most damaging anti-pattern is mistaking instrumentation for leadership. Tools increase efficiency, strategy defines direction and analytical synthesis enables foresight. Responsibility binds them together. Without that foundation, management becomes performance theatre. With it, management becomes leverage capable of sustaining complex IT systems in volatile environments.
