Filling the Gap Between Knowing and Doing
Most leaders didn’t get to where they are by accident. Years of hard work and consistency got them there. More training and more practice is never a bad thing, but many have seen the same pattern play out. Participants attend workshops, receive coaching, complete assessments, and leave energized with new insights and intentions. Weeks later, many can describe what they learned but haven’t put any of it into action. Months later, far fewer have meaningfully changed how they lead because of it. This challenge is not unique to any one organization, industry, or leadership program. Leadership development is still one of the top organizational investments, but transferring that one-off training into sustained behavioral change continues to be a persistent struggle.
That gap isn’t about motivation, commitment, or intention. It comes down to structure.
The reasons are typically pointed at the individual: distraction, competing priorities, a return to old habits. There’s some truth in that, but it misses something more fundamental: a gap between knowing what to do and doing it, consistently. That gap isn’t about motivation, commitment, or intention. It comes down to structure.
Most leaders already understand the behaviors that would make them more effective. The harder part is making those practices hold up against the competing demands of everyday work and life.
This is where accountability comes in. An unaccountable leader is easy enough to picture. Commitments made in a meeting quietly disappear. Feedback gets acknowledged but never acted on. The same gaps show up review after review, with little change in between.
The effect rarely stays contained to one person. Direct reports stop expecting things to change. Peers start working around the gap instead of resolving it. Someone else ends up covering the difference, and over time, that adds up.
Accountability is often framed as a requirement to be upheld or a trait to be developed. For those being held accountable, it can feel like punishment. That impression sticks when leaders get praised for showing accountability and criticized when they don’t. The problem with this framing is that it puts the weight entirely on the individual instead of looking at the system around them.
But accountability is more than a personal characteristic or a box to check. It functions as a mechanism that shapes how people think, make decisions, and follow through on commitments. When accountability is built into the environment deliberately, it helps bridge the gap between knowing what to do and consistently doing it.
This shows up in practice through peer accountability, self-accountability, structured follow-up with stakeholders, and accountability partnerships. Each is a different form of the same underlying mechanism. The goal isn’t obedience to a process. It’s behavior change that holds up after a program ends. That means understanding not just that accountability works, but what makes it work and what makes it fail.
Not All Accountability Feels the Same
Before exploring accountability as an organizational system, it helps to understand how it’s actually experienced by the people inside it. Researchers call this felt accountability: the expectation that one’s actions will be evaluated by someone, and that the evaluation might carry real consequences (Hochwarter et al., 2005).
How that expectation feels depends on who’s doing the evaluating, what’s being evaluated, and when. A performance review carries a different weight than a passing comment from a peer. A commitment made publicly in a meeting feels different than the same commitment made privately.
Someone can feel highly accountable to their team and barely accountable to a process that exists only on paper.
It’s also rarely coming from just one direction. Hochwarter et al. (2005) note that employees are often accountable to supervisors, colleagues, team members, and customers all at once. Frink and Klimoski (2004) describe this as a “web of accountabilities” rather than a single reporting line. Someone can feel highly accountable to their team and barely accountable to a process that exists mostly on paper.
Feeling responsible for something is not the same as feeling accountable for it. Someone can feel deeply responsible for getting a project done and still not feel accountable for it, since accountability only enters the picture once there’s a real chance someone else will evaluate the outcome (Hochwarter et al., 2005). Chen et al. (2016) found that felt accountability fully explained the link between transformational leadership and how employees performed their core job duties, across a sample of supervisor-employee pairs. Leadership behavior didn’t shape performance directly so much as it shaped how accountable people felt, which then shaped performance.
None of this registers as neutral. Hochwarter et al. (2005) found that felt accountability functions as a stressor, with higher levels associated with greater job tension. It’s something carried internally, often well before any actual evaluation takes place.
How Leaders Shape Accountability
The environment a leader creates determines how accountability is experienced. Wallace et al. (2011) found that psychological empowerment improved performance in store sales and customer service, but only among managers who also reported high shared felt accountability. A manager who tells their team to take ownership but never checks in on what they actually do with it doesn’t see the same results. Stewart et al. (2021) found a related pattern: teams with higher shared accountability showed measurable increases in effort over time.
Expectations have to be clear and reasonable, or there’s nothing for accountability to attach to. A leader who sets standards that fit the role and the person in it, then actually follows up, builds trust. A leader who skips that step ends up with a list of requirements people quietly ignore.
The goal isn’t simply more accountability. It’s building a system that promotes the right behaviors.
Not all accountability systems produce positive outcomes. When accountability is excessive or punitive, it increases job tension and contributes to burnout instead of better performance (Hochwarter et al., 2005). This shows up as constant check-ins, public call-outs, or measures that exist mainly to catch failure rather than support success. Hall, Frink and Buckley (2017) point to earlier work finding that autonomy alongside accountability neutralized those negative effects (Hall et al., 2006). The goal isn’t more accountability. It’s a system that promotes the right behaviors: transparency and feedback that helps, not fear and blame that doesn’t.
Why Feedback Alone Doesn’t Work
Feedback processes tend to fail before they begin, not because of bad data or poor design, but because of how feedback is understood in the first place. In many organizations, feedback is associated with something going wrong. It arrives as correction, not development, and that framing shapes how people give it, receive it, and act on it. Smither et al. (2005), in a meta-analysis of multisource feedback across multiple organizations, found that feedback alone produced only modest performance improvement. What made the difference was not the quality of the feedback but what happened around it: the expectations, the structure, and the follow-through.
What made the difference was not the quality of the feedback but what happened around it: the expectations, the structure, and the follow-through.
Buy-in starts with understanding the purpose behind the process. Before any feedback is collected, employees and managers need to know what’s expected of them and how the results will actually be used. When that context is missing, people fill the gap with assumption, and assumption in a feedback process usually defaults to suspicion. Bracken and Rose (2011) describe this as an Acceptance problem: a person who doesn’t trust the process will read even accurate feedback as unfair, and feedback that gets read as unfair rarely leads to any real change. For feedback to be worthwhile, the person receiving it has to first decide that it’s fair and relevant, and only then is it worth acting on.
Follow-through is where most feedback processes break down. The survey is completed, the report is delivered, and the conversation ends. Bracken and Rose (2011) point to follow-up as one of the more powerful levers available: discussing results with raters demonstrates real commitment to change, gives raters a chance to clarify what the feedback actually meant, and draws raters into the action-planning process itself. Without a structured follow-up process, feedback becomes a one-time event rather than the beginning of a development process. Over time, consistent follow-through creates the conditions for something more useful: a planning process that individuals can build from and a development path that is genuinely their own.
The Trust Behind the Feedback
Feedback lands differently depending on who delivers it. Peer feedback tends to feel less emotionally loaded and less like a judgment than feedback from a manager. Accountability from a manager can carry a parent-child quality, even unintentionally, and an employee may comply because they have to, not because they’re convinced the manager is right.
Trust is a big part of why peer feedback feels different. Two colleagues working side by side tend to see each other as equals with shared stakes, so accountability between them is easier to accept at face value. A manager doesn’t start in that position. Trust has to be earned first. Once it is, the effect is similar either way: people stop bracing for the worst and start treating feedback as something worth acting on.
Relational accountability can be cultivated, but it can’t be mandated.
Stewart et al. (2021) found that early in a team’s life, accountability is closely tied to trust, commitment, and a shared sense of collective capability. In established teams, that same accountability translated into greater effort and a stronger willingness among team members to keep working together. There’s often a mutual understanding among peers, even if not fully conscious, that the team is in it together and wants the best for each other.
This has a real implication for leaders. Stewart et al. also found that meaningful differences in accountability still showed up between teams with the same managers, the same location, the same tasks, and the same formal structure. If accountability were something leaders could simply install through policy, those differences shouldn’t have existed. What separated the teams was the relationship between the people in them, not the system they were operating under. Relational accountability can be cultivated, but it can’t be mandated. A leader can create the conditions where trust and peer accountability are more likely to take root, things like consistent follow-through, fair treatment, and giving credit where it’s due, but they can’t issue trust as a directive.
Follow-Through and the Power of Reflection

Feedback and peer accountability are essential for any team to make real progress on performance, productivity, and communication, but they aren’t sufficient on their own. Feedback by itself moves performance only slightly. Reflection by itself moves it even less. It only helps when it’s anchored to something specific, and when the person engages with it rather than going through the motions. The chart below shows exactly how much that combination changes the outcome.
The same pattern shows up at a much larger scale outside the lab. Bracken and Rose (2011) point to data reported by Goldsmith and Morgan (2004), spanning more than 11,000 leaders and 86,000 raters: leaders who followed up with raters after receiving feedback were seen as more effective over time, while failing to follow up was one of the strongest predictors of being seen as less effective. This reflects rater-reported perceptions of change, not directly observed behavior, but it points in the same direction as the experimental results above.
Done consistently, that step turns a one-time response into a habit that holds up over time.
Accountability systems that stop at delivering feedback are leaving the most effective part of the process unused. A structured reflection step closes the loop between receiving feedback and actually changing. Done consistently, that step turns a one-time response into a habit that holds up over time.
When More Isn’t Better
Accountability links individual consistency to organizational expectations, but more of it doesn’t simply mean better outcomes. Accountability works in relationship to trust. The right amount depends on how much trust already exists between the people involved.
Accountability’s effects aren’t simply additive, either. Hall and Ferris (2011) found a U-shaped pattern between accountability and performance. Both too little accountability and too much of it were associated with worse outcomes, with the best results landing somewhere in the middle. The sample was small and the effect modest, but it points toward something worth taking seriously: accountability doesn’t just need to exist, it needs to be set at the right level.
Accountability doesn’t just need to exist, it needs to be set at the right level.
Trust and accountability can substitute for each other to some degree. When trust is already high, a leader doesn’t need to lean as hard on formal structure, the relationship is already doing some of that work. When trust is low, organizations tend to compensate by adding more oversight, more check-ins, more sign-offs, more reporting. That tends to backfire. Piling on accountability to make up for a lack of trust can end up eroding trust further, since it can read as a sign that someone isn’t believed to be capable or reliable in the first place.
Part of designing accountability well is knowing who it’s actually for. People often answer to more than one audience at once, a supervisor, a team, a client, sometimes all three on the same task. A leader building an accountability system has to think about which of those audiences actually matters for the behavior they’re trying to change. Treating accountability as one-size-fits-all misses that difference entirely.
None of this means accountability should be minimized. It means matching the amount of structure to the relationship at hand, the same judgment good leaders already apply elsewhere.
From Insight to Action: The Ascent Diagnostics Difference
Accountability is not one single change, expectation, or request. It’s a system made up of several distinct, working pieces: how accountability is felt, how feedback delivers it, how peers extend it, how reflection completes it, and how leaders adjust it to fit the situation. Building any of this starts with understanding that accountability is felt differently by different people.
Feedback carries most of that weight. It needs to be clear and direct, since it remains the primary way accountability gets delivered in most organizations. Who delivers it matters as much as what is said. Peer feedback works differently than feedback from a manager, and a system that treats every relationship the same misses something real.
Training and development is forever, not because the work never ends, but because the behaviors in this paper have to be practiced and reinforced long after any single program wraps up.
Across both the research and the real-world patterns in this paper, one thing holds: structure is what separates accountability that works from accountability that doesn’t. And the caution from earlier still holds with it: more accountability is not automatically better accountability.
This is where most development efforts stop, and it is where Ascent Diagnostics begins its accountability work. A diagnostic can name the gap between how a leader sees themselves and how they actually operate, but naming it changes nothing on its own. What closes it is the structure this paper describes: accountability partnerships that make commitments real, structured follow-up with the people the change actually affects, and a deliberate reflection step that turns a single feedback cycle into a behavior that holds. Each is calibrated to the trust already in the room, because the research is clear that accountability set too high erodes the very trust it depends on.
Accountability is the third of the five drivers in the Ascent Behavior Change model, and it is the one that makes the others last. Self-awareness surfaces the gap and emotional fluency changes the response in the moment, but without a system holding those changes in place, they fade when the program ends. None of this works as a one-time fix. Training and development is forever, not because the work never ends, but because the behaviors in this paper have to be practiced and reinforced long after any single program wraps up.


