Recognising your own contribution to a problem can be useful and uncomfortable. A manager may realise that the way they assign work is leaving the team overloaded. A process owner may see that their approvals are delaying delivery. An engineer may understand that a design they maintain is becoming difficult to change safely.
That recognition creates a responsibility to examine what can be done. It does not establish that the person can resolve every condition behind the problem. The manager may control task allocation while another leader controls commitments and staffing. The process owner may administer a requirement they cannot remove.
Personal accountability sayings often leave this distinction unresolved. They encourage action but rarely help separate a change in behaviour from a change in policy, resources, or decision rights. A more useful approach identifies the person’s contribution precisely, acts within the available scope, and makes the remaining decisions visible to those who can take them.
Replace the Global Judgement With a Specific Account
“You are the problem” is too broad to guide a correction. It can describe an observed action, a repeated behaviour, a role conflict, or another person’s frustration. Before accepting or rejecting it, establish what the claim refers to.
Consider a manager whose team repeatedly misses delivery commitments. Staff say that work arrives without clear priorities and that the manager asks for new tasks without discussing what should move. Leadership says the manager needs to improve execution. The manager knows that the team is carrying more work than it can reliably complete.
The manager’s contribution might include assigning requests too quickly, treating tentative dates as promises, or failing to explain the consequences of additions. Those actions deserve examination even if the wider commitment was unrealistic. A specific account creates opportunities for improvement that a judgement about personal inadequacy does not.
Other factors may sit elsewhere. A commercial leader may promise dates before consulting delivery. An executive may require several initiatives to proceed at once. A specialist dependency may have no agreed capacity. The manager needs to distinguish these conditions from their own actions without using them to dismiss legitimate feedback.
Evidence helps. Compare recent requests, the priorities communicated, changes to the workload, and the decisions that followed. Ask colleagues for examples and check whether the accounts agree. The purpose is to identify a pattern that can be changed, rather than collect evidence for a predetermined conclusion about who is at fault.
“Change Yourself” Needs a Defined Scope
Advice to change your own behaviour is valuable where that behaviour contributes to the difficulty. The overloaded manager can stop presenting every request as equally urgent, clarify which dates are estimates, and make competing commitments visible. They can involve the team before promising work within their remit.
These changes may improve the situation without resolving the whole capacity problem. Clearer priorities can reduce unnecessary switching, but they do not create an additional specialist or remove a contractual deadline. The manager should assess the effect of the change without claiming more than it can accomplish.
There may also be a need to repair earlier communication. If staff were told that all deadlines were firm, the manager should clarify which commitments are being reviewed and explain what happens next. Acknowledging their contribution gives colleagues a more credible basis for working with the correction.
A bounded change can be tested. For the next planning period, the manager might require every new request to identify its intended outcome and proposed priority. Requests that exceed available capacity would receive an explicit discussion of what moves. The team can then examine whether priorities became clearer and whether important work was still displaced without agreement.
The test should remain feasible within the role. A manager cannot unilaterally rewrite every organisational commitment, but they can often improve the accuracy of the account presented to decision-makers. That is a meaningful contribution even when the final allocation remains outside their authority.
“Be Part of the Solution” Requires a Decision Path
A proposed solution can depend on several decisions. The manager might recommend reducing the initial scope, moving a date, obtaining specialist support, or pausing another initiative. Each option affects people beyond the immediate team and needs an authorised response.
The request should explain the problem and the choice required. For example, the current plan may depend on one specialist completing two overlapping pieces of work. Leadership can decide which comes first, obtain additional support if feasible, or change the commitment. Asking the manager to improve coordination does not settle that allocation.
Identify who can make each part of the decision. A budget owner may approve expenditure without controlling the availability of a particular person. A programme sponsor may set priorities while another service owner controls a technical change. A workable proposal needs those responsibilities connected.
Atlassian’s DACI framework distinguishes the driver of a decision from its approver and contributors. It is a useful prompt for this conversation: the person preparing the recommendation need not be the person authorised to choose. The framework only helps if those roles match the organisation’s actual arrangements.
The proposal should also preserve uncertainty. Additional staffing may not solve the immediate problem if recruitment and preparation take longer than the available window. A reduced scope may leave an essential customer need unmet. Presenting these limitations helps the decision-maker compare real options instead of approving a solution that exists only in the plan.
“Be the Change” Can Leave a Role Conflict Untouched
Some workplace friction comes from a responsibility that the organisation still needs. An approval owner may delay a launch because required evidence is missing. A delivery manager may decline a date because capacity is already committed. Removing the visible obstacle would not necessarily remove the underlying requirement or constraint.
The person should still examine how they perform the role. Could the requirement have been explained earlier? Are requests reviewed promptly? Are similar cases treated consistently? Is there an opportunity to simplify the work without weakening the purpose of the control?
These questions separate an avoidable delay from the legitimate time needed to make a decision. They also prevent the role from becoming an excuse for poor service. A necessary review can still be badly organised or communicated.
For the overloaded manager, the conflict may be between accepting more work and maintaining a reliable plan. They need leadership to decide what commitment should take precedence. Quietly agreeing to everything transfers the unresolved choice to the team. Refusing everything without explaining the consequences would also be an inadequate response.
An explicit account makes the conflict easier to address: the manager can organise delivery within the approved capacity, while a change to that capacity or the overall commitment requires another decision. This is a practical distinction between responsibility and authority, rather than a claim that influence is impossible without formal power.
When the Required Change Is Not Approved
An escalation may produce an unwelcome decision. Leadership may decline more resources, retain the scope, or accept a risk the manager has raised. The next step is to establish what has actually been decided and how the team is expected to proceed.
A useful record includes the recommendation, the decision, its assumptions, and the resulting commitment. It should help the participants coordinate their work. Recording a disagreement does not remove every responsibility from the person who raised it, and a decision-maker’s acceptance of risk does not make every possible consequence acceptable.
The manager can continue to report progress accurately, identify material changes, and make improvements within their remit. If a decision depended on an assumption that later proves false, that is a reason to return with the new evidence. Repeating the same argument without new information is different from explaining that the basis of the approval has changed.
There are limits to what a local change can achieve. The manager should avoid disguising the unresolved gap through unrecorded overtime or increasingly optimistic forecasts. Those responses can make an infeasible plan appear workable and reduce the information available for the next decision.
If the arrangement remains persistently unworkable, a broader discussion about the role may be necessary. That can concern its scope, the authority attached to it, or whether someone else needs to own the unresolved decisions. The appropriate response depends on the circumstances; a quotation cannot settle it.
Judge Progress Through the Change You Can Explain
Self-awareness becomes more useful when it leads to a specific action and a check on its effect. For the manager, useful questions include whether staff now understand the priority order, whether new requests receive an explicit capacity decision, and whether leadership receives an accurate account of what remains feasible.
The wider outcome may still be disappointing. That should prompt examination of the remaining causes without erasing improvements already made or treating them as sufficient. Better communication is valuable, but it should not be presented as a complete remedy for an unresolved workload commitment.
Likewise, structural constraints should remain open to challenge. A process described as outside the manager’s control may be changeable through an existing route they have not yet used. Feedback from colleagues may reveal further behaviour within their remit. Accountability includes being willing to revise that assessment.
The cost of blame without authority is partly the loss of this precision. People are judged either as the whole problem or as powerless participants, when their actual responsibilities are more specific. A sound response recognises the contribution, changes what is reasonably within reach, and seeks explicit decisions on the conditions that require wider authority.
