پاسخ‌گویی از پیگیری شروع نمی‌شود؛ از توافق بر کارِ خوب شروع می‌شود

When managers speak about a lack of accountability, the common response is usually more follow-up: status meetings, reminder messages, progress reports, and repeated questions about delivery dates. These tools can sometimes be necessary, but if people do not agree on what “good work” actually looks like, more follow-up merely adds more pressure to ambiguity.

A manager may see on-time delivery as the sign of success, while the role holder prioritizes completeness and another stakeholder cares more about response speed or risk reduction. In this situation, all three may be acting in good faith, yet each is judging performance by a different standard.

Reliable accountability begins when people can refer to a shared standard that is observable and easy to revisit. That standard should clarify what output is minimally acceptable, what counts as excellent performance, which priorities require trade-offs, and which decisions require alignment before action.

This distinction matters because it turns accountability from a vague individual trait into a work-design question. Rather than asking, “Why is this person not accountable?”, a team can ask, “Have the role, criteria, and decision boundaries been designed clearly enough?”

When expectations remain only in people’s minds, feedback can easily be interpreted as subjective. A person may believe that they delivered a complete output, while the manager expected risks to be anticipated as well. Both interpretations may be understandable, but without a shared standard, the conversation moves closer to defending personal views.

Role ambiguity is not limited to incomplete job descriptions. Sometimes a job description exists but does not explain what to do when speed conflicts with accuracy, what level of quality is sufficient, or which changes must be raised before execution. In this situation, a person may do substantial work and still not be seen as accountable by others.

Greater candor does not mean greater control or harshness. A direct conversation grounded in previously agreed criteria is different from micromanagement. The first gives a person room to decide independently within a clear frame; the second usually replaces criteria with the manager’s constant supervision.

To expose the hidden gap, consider a simple but demanding test. The manager, role holder, and key stakeholders should independently write their definition of good work in that role before discussing it together. The purpose is not to test people’s knowledge or obtain a correct answer; it is to reveal hidden differences.

This independent written input should rely on specific examples, not phrases such as “be professional” or “show ownership.” Each person should explain what they would see in an actual output, what they would review, and on what basis they would judge the work acceptable, excellent, or in need of revision.

The first part of the test is the minimum acceptable output. It defines what must at least be correct, complete, and usable for work to count as delivered. This minimum should not be so general that everyone imports their own interpretation, nor so detailed that execution becomes an exhausting checklist of controls.

For a hypothetical example, in a role responsible for preparing a proposal for a decision, the minimum acceptable output might include a clear problem, understandable options, stated assumptions, and a defined next step. This does not require every proposal to look alike; it says that no usable proposal should be presented without these elements.

The second part is the evidence of excellent performance. Excellence should not simply be a label for doing more work, working longer hours, or satisfying a manager’s personal preference. It should identify behaviors or qualities that create additional value in the role, such as anticipating a relevant risk, simplifying a difficult decision, or preparing an option that reduces unnecessary back-and-forth.

In the same hypothetical example, excellent performance might appear when the person not only prepares options but also identifies key dependencies early and clarifies which assumption, if changed, would alter the decision. This level of work should be tied to the outcome of the role, not to a performance of busyness.

The third part is the role’s three main trade-offs. Nearly every role must choose between values such as speed and accuracy, independence and alignment, standardization and flexibility, or quality and cost. If these trade-offs are not stated, a person may optimize something that the manager or stakeholder does not consider the priority.

There is no need to document every possible trade-off. Selecting the three that recur most often keeps the conversation focused. For each one, the team should specify which side takes priority under normal conditions, what signal indicates that normal conditions have changed, and who has final decision authority.

The fourth part is the set of matters that require alignment before action. This is different from asking permission for every move. Its purpose is to ensure that decisions with meaningful effects on commitments, risk, resources, stakeholders, or the direction of work are surfaced at the right time, before reversing them becomes difficult.

In the hypothetical example, changing a key assumption, removing an important option, sending a version that creates a new commitment, or moving beyond an agreed deadline could belong on this list. By contrast, choosing the wording or sequence of information, when it remains within the criteria, should not normally require case-by-case alignment.

After the independent writing is complete, place the responses side by side and begin by discussing the differences, not by deciding whose answer is more correct. Differences in priorities, expected quality, or alignment boundaries often do not signal an individual weakness; they show that the role’s working agreement has not yet been formed or updated.

Hypothetical scenarios close to everyday work are useful in this conversation. A team can ask: If time is limited, which part must not be sacrificed? If information is incomplete, what action can the person take independently? If stakeholders have conflicting requests, who decides, and by what criterion? The answers need to become observable and actionable language.

The final output is best kept short and accessible: one page for each role or key responsibility that records the four elements. This page does not replace job descriptions, processes, or human conversations; it creates a shared reference that people can use while working, deciding, and giving feedback.

A manager can use this reference in performance conversations, but not as a tool for catching people out. More useful questions are: Which criterion was unclear? Where did criteria come into conflict? What changed in the role, resources, or stakeholder decisions that made the previous agreement insufficient? These questions enable learning about work design rather than individual defensiveness.

This agreement should not be treated as a fixed document. As priorities, stakeholder groups, tools, or levels of authority change, the definition of good work may need revision. Reviewing it after a difficult decision, an unsuccessful delivery, or the addition of a new responsibility helps prevent ambiguity from accumulating.

Follow-up still has a place, but it should come after the criteria are clear. It can then move beyond the vague question, “Where is the work?” and specify how the output is progressing against a standard, which trade-off has become active, and what alignment is now needed. This turns follow-up from repetitive pressure into execution support.

This analysis is produced by an AI author persona in the role of an HR analyst. Its purpose is to offer a practical framework for conversations about roles and performance, not to replace them with automated judgment. Sustainable accountability becomes more likely when people know, before they are evaluated, how good work will be recognized in practice.