It's Always Your Fault (Even When It Isn't)

Did you bake the cake?

Months before an important meeting, I sent an extensive document outlining expectations for my team. To keep it simple, let’s say I asked everyone to bake a cake and explained what I would offer them in return if their cake was delicious (aka incentive).

Two days before the meeting, I asked one of my team members what kind of cake they were planning and was met with a blank stare.

"Oh... I didn't realize that was expected of me."

Their reaction sent me into an angry panic and I went straight to my laptop and into evidence-gathering mode; my knee-jerk reaction to this disappointment was to shift the blame. I started pulling up emails, preparing screenshots of the memo and building my case for why this was absolutely, definitively, one hundred percent not my fault.

I started drafting a frustrated response when it hit me.

None of that, the blame, the explanations, mattered. On the day our clients walked in, there would be no cake and they wouldn't be looking at my inbox, they'd be looking at me.

So, late into the night the day before the meeting, I baked the cake.

The Founder's Accountability Paradox

Here's the brutal truth nobody tells you when you start a company: you are accountable for everything, including the things you delegated.

And yet, I was treating accountability as something I needed to extract from my team when really it was my responsibility to build it.

Researchers Dose and Klimoski (1995) identified something they called felt responsibility, the internal sense of genuine ownership over an outcome, and suggested that this is very distinct from simply being assigned a task. As my personal and painful story illustrates, you can hand someone a task and still have them feel zero ownership over the result.

But that’s only half the story because the gap between assigned responsibility and felt responsibility is your problem to solve as a leader.

Why Conventional Accountability Backfires

When many of us think about accountability, we think about systems: reporting structures, documentation, and performance reviews. The research calls this "conventional accountability" and despite looking good on paper (literally) it turns out it's not really effective at getting people to care because it acts more like surveillance than meaningful engagement with a task or mission. And when it comes to surveillance, humans tend to respond in predictable ways: they optimize for looking good, they cover their tracks and wait to be told what to do next.

The screenshot I was about to send was conventional accountability in its purest, ugliest form. It was about me establishing that it wasn’t my fault. Meanwhile, it did absolutely nothing to get the cake baked.

Three Levers for Accountability

So what does it actually look like to lead in a way that creates genuine ownership? My experiences with the cake and the science point to three conditions that help convert assigned tasks into genuine ownership.

1. Significance

Most accountability failures are actually meaning failures. I tried to incentivize my team member rather than help them understand what cake meant for the business. That's on me. When someone understands how their piece connects to the larger mission the task becomes personal.

2. Personal control

People take responsibility for things they have real agency over. If your team is executing instructions, they're contractors, not owners. Ownership requires some discretion over how the work gets done. The moment you strip that away with over-specified processes and micromanagement you're also stripping away the psychological conditions for anyone to actually care about the outcome.

3. Trust

The research is clear that significance and agency alone aren't enough if the underlying relationship is transactional. When your team senses that your systems exist to protect you rather than support them, ownership evaporates.

After my cake incident, I considered having my team sign contracts and agreements to monitor if they read the memo BUT before I got around to it, I realized that once again this is not real accountability, it’s an erosion of trust and a scapegoat for me to transfer the blame later. Thus, real accountability will always be on me/us as leaders to create the conditions for our teams to actually care.

ONLY when you take ownership over these conditions, does ownership from your team become possible. Neither replaces the other.

The Quick n’ Dirty

When your company is your baby, blame is a luxury you can't afford. The clients don't care about your documentation trail. They care about the cake. The real accountability when it comes to delegation starts with asking: Have I made this matter to the people I'm counting on? If the answer is no, that's not a performance problem within your team, it's a leadership opportunity you can address.

What's your instinct when something falls through the cracks, do you reach for evidence, or do you reach for a mirror?

References

Dose, J. J., & Klimoski, R. J. (1995). Doing the right thing in the workplace: Responsibility in the face of accountability. Employee Responsibilities and Rights Journal, 8(1), 35–56.

Goncharenko, G. (2023). The role of accountability in workplace democracy. Business Ethics Quarterly, 33(2), 381–393. https://doi.org/10.1017/beq.2022.3