A Culture Of Accountability Is A Non-Negotiable In AI Land

Usually it goes something like this: task completion is rewarded over critical thinking, hand-offs feel more like a game of “hot potato” than pro league footie, chaos is normalized throughout, and then crossing the finish line creates immediate amnesia that erases the trauma.

That was fine before, but when you combine those gaps with higher pace and higher pressure, you’re suddenly driving an F1 car with no steering and no brakes. 

So let’s unpack what’s really needed to get your project teams and project leaders functioning like a well-oiled machine in the age of AI.

The Fog Of Accountability

The reality is that accountability and ownership gaps are often insidious and invisible. In fact, most of the time they get masked by the very way the team has been trained to work. 

Sometimes it gets masked by a few team members doing the messy problem-solving behind closed doors in DMs or sidebar conversations. 

Sometimes it gets masked by silent rescuers — senior leaders who quietly step in to nudge a project back onto rails without drawing attention to themselves.

Sometimes it’s masked simply through the euphoria of getting a project across the finish line, even if it was a dumpster fire the whole way through. 

Sometimes it’s masked by a culture of dishonesty and “cover your butt” grandstanding, showing up as dishonest reporting, as performative project retrospectives with no follow-through, and as rose-coloured retellings of the project in performance reviews.

But at the heart of it is the fact that most teams are trained to execute steps in a process instead of being trained to have the instinct and judgment to drive an outcome. And as a result, it’s actually quite rare to find a team with a shared definition of accountability and ownership. 

Most teams are trained to execute steps in a process instead of being trained to have the instinct and judgment to drive an outcome.

The Correct Definition Of Accountability (And 3 Incorrect Ones)

Accountability is a word that most people think they understand, but few people are actually aligned on.

For some, accountability means being accountable for getting a task done, and nothing more.

For some, accountability means being the one who will get blamed if it goes wrong, so being ready to shift the blame to someone else is the best strategy.

For some, accountability means having the entire project on their shoulders to the point where you should be able to do everything yourself if someone drops the ball.

All of these definitions have an element of truth, but ultimately fail to capture the essence of accountability. So in an attempt to make things more clear, we often add the word “ownership”. But that often falls flat, too.

For some, ownership means that they have to do something alone and can’t ask for help.

For others, ownership means having total dictatorial control over a thing and having the privilege of ignoring all other feedback and input on the matter.

For others still, ownership means being stuck holding the bag on the pieces that fall through the cracks. 

And once again, these definitions capture a piece of the puzzle but still miss the forest for the trees. 

Here’s my take: accountability means owning the outcome, and ownership means understanding the bigger picture and being willing to take action to make that outcome happen — even if it’s not what it says to do in the manual.

Let’s look at an example. Let’s say your Marketing team is responsible for setting up an email automation workflow, and you are ultimately accountable for generating leads for a paying sponsor. 

You could just assume that the team gets it and hope they’ll deliver something perfect. But instead you don’t leave it to chance. You confirm the end-to-end flow is working. You ask questions you know you’ll get asked by your bosses and your client if things go sideways. You confirm the content is correct and that the automation will send emails on the correct day. You prime the pump to secure the right resources to make corrections and last-minute fixes if needed.

You anticipate as many possible angles and defuse as many possible risks as you can. 

Because if there’s a problem with the email workflow, you can blame your team all you want, but you still failed to do everything you reasonably could to deliver the desired outcome by letting important details slip by you. 

And in fact, even if you did hit your project KPIs, you’re still going to be held to account for why there were missteps along the way. 

That’s accountability to me. That’s the mindset and behaviour that is thorough and proactive enough to move at speed instead of reactively pausing to circle the wagons when surprises happen.

So how do we build team culture around that definition of accountability?

Accountability means owning the outcome, and ownership means understanding the bigger picture and being willing to take action to make that outcome happen — even if it’s not what it says to do in the manual.

Lead Smarter in the Age of AI

Join the DPM community for access to exclusive content, practical templates, member-only events, and weekly leadership insights - it’s free to join.

Sign up with LinkedIn

Or sign up with email:

Comments

This field is for validation purposes and should be left unchanged.

Name*

First name Last name

Business email*

This field is hidden when viewing the form

Free Account Module

Bottom BarLanding PageFooterInlinePop UpSidebarSSO

LinkedIn profile

Seniority*

Select an optionExecutive / C-suiteVPDirectorManagerIndividual ContributorOther

Company's AI adoption maturity*

Select an optionExploring opportunitiesRunning pilotsScaling adoptionEmbedded in the business model

5 Ways To Build A Culture Of Accountability

I could stand here and tell you to hire a coach, or to bring on a consulting firm, or to plan a big company retreat to develop a culture of accountability. And that might be the right answer for you. But I think the raw ingredients are within reach of most teams.

Here’s 5 practical ways leaders can start building a culture of accountability.

Casting A Big-Picture Vision

I see a lot of leaders get into the weeds when briefing teams. On the one hand, leaders are often expected to know the finer details of how their plan achieves its goals. I get it. But on the other hand, it’s a great way to miss the broader context of a project. 

So instead of starting in the trenches and doling out tasks, start by painting a picture of what the future looks like after the project completes, how the project adds value, and why it’s important to the business strategy. 

Simple is better. What future does the project enable and for who? 

And crispness is golden, too. Get the message tight enough that you can communicate it in a few sentences to anyone who joins up along the way. Then let people ask questions that pull you into the details.

The result will be a team that can rally behind a cause instead of putting their blinders on and focusing only on the tasks with their name on them. 

Instead of starting in the trenches and doling out tasks, start by painting a picture of what the future looks like after the project completes

Celebrating Outcomes, Not Task Completion

Your project’s vision should also carry through into what gets rewarded on the project. If your teams are incentivized to get a task done on time without understanding what that task unlocks, that sets up the trap of prioritizing execution over impact. 

So instead of asking “how much more time do you need to get this done?” or “what’s blocking you?”, consider asking “how could we still achieve the same or better impact from where we stand on the playing field?” or “is this still the most valuable thing we could be doing?”

And when celebrating wins with the team, aim to reward impact and bigger-picture understanding. For example, call out the fact that Anuj added a LinkedIn poll on top of an email survey to gather richer audience insights, or the instances where Ralitsa’s team increased ICP signups for a live webinar by assessing ICP traffic trends to determine the best time to host it. 

Or, at the very least, contextualize the recognition against the project vision. Point out that by finishing the research questionnaire early, Sasha added 3 more days for customer interviews, effectively tripling the insights. 

Remind them what it’s all for. Otherwise folks will just execute tasks and move on with their lives.

Modeling Honesty

Honesty is arguably the most impactful cornerstone of team culture. But while a lot of leaders demand honesty from their teams, most choose not to be fully honest themselves. They feel that it shows weakness or limits career growth. And they might be right. Regardless, leaders set an example, and teams will follow that example even if they’re told otherwise. 

So, as leaders, we need to strike the balance between holding our teams accountable and holding ourselves accountable. That doesn’t mean falling on your sword or taking all the bullets. It also doesn’t mean being performative and making up fake reasons to look like you’re taking accountability for something you don’t need to take accountability for. 

Instead, it’s a mix: it’s asking tough questions of the team while recognizing your role in it all. And it’s about doing it in public spaces — to set an example of what honesty looks like in practice, and to provide an opportunity for the team to learn those leadership skills.

Because when honesty is not present at the leadership level, projects become more about optics than truth. And that’s what trickles down into dishonest status updates, dishonest project retrospectives, and dishonest performance reviews.

And that’s exactly the drag that will prevent a team from reaching its full potential. 

When honesty is not present at the leadership level, projects become more about optics than truth.

Separating Accountability From Blame

A lot of teams draw a connection between accountability and blame. You hear it all the time: the accountable person is “the throat to choke” when things go wrong. The problem is no one likes getting blamed, and that in turn leads to a resistance to accountability. 

I’d hazard to say that this connection is the most severe barrier to achieving psychological safety: if people can’t trust that they won’t get thrown under a bus, they’ll stay away from buses altogether. And that leads to a team that isn’t willing to open the throttle more than halfway.

Unfortunately, many leaders don’t know the difference between holding someone accountable and blaming them. There’s the classic “why didn’t you catch this?” or the “if you hadn’t done x, then we wouldn’t be here”. Even if you make the tone polite, they still don’t become constructive. 

The accountability question is different. It’s more like “walk me through the decisions based on our goal” or “where did our process break down?”, followed by a solutions-oriented posture, like “how can we still hit our target outcome?”

Blame cuts people down, makes things personal, and keeps people living in the past. Accountability looks forward and reinforces ownership. 

If people can’t trust that they won’t get thrown under a bus, they’ll stay away from buses altogether.

Looking Beyond Job Titles

Clusters of flat teams will win in the age of AI. Not because they’re modern and nimble and progressive. They’ll win because speed doesn’t care about hierarchy and job titles. There’s simply no time for ego battles when the work is moving with a multiplier like AI. 

This might sound counter-intuitive based on highly vertical organizational structures like the military or Hollywood filmmaking, but those are structures that rely on centralized decision-making that aren’t interested in building a culture of widespread judgment, ownership, and accountability. 

Instead, make role clarity crisp, contextual, and specific to your project. Even if you don’t want to build a RACI matrix, start speaking the language of RACI to map out who is responsible or authorized to make a decision versus who is simply consulted or informed. That might mean that the intermediate dev is accountable for something instead of a tech director. If you’ve been successfully building a culture of accountability and ownership, it’ll likely be fine. 

There’s simply no time for ego battles when the work is moving with a multiplier like AI.

Where AI Can Help

AI tools and technology won’t build your accountability culture. You probably knew that. But it can play a part in how that culture is reinforced.

For example, we built a Project Outcomes Navigator that uses an interview format to get to the heart of the project’s purpose to create briefs that are outcomes-oriented, not task-oriented. 

In the same vein, members of my community have been creating AI agents that act as coaches to track what somebody is accountable for and make suggestions accordingly when reviewing work-in-progress. 

And we’re also working on a status update coach that helps team members frame their progress in the context of the broader project to avoid having every status update saying “on track” until it becomes “off track” or “done”. 

The reality is that this is not a tech-heavy endeavour, and therefore the support infrastructure doesn’t need to be complex. You likely don’t need to build a centralized ownership map that integrates with all the tools across your enterprise. A light nudge for your already very talented team might be all it takes. 

Your First Steps

Okay, so maybe you’re ready to build up your culture of accountability and ownership. Maybe you’ve been ready for years. Where should you start?

I would start with the simple (but not easy) stuff — language, learning, and levity.

The language we use is so important. It is literally the verbal manifestation of our team culture. So watch for where you and the team have been saying things like “are we going to be able to deliver on time” and shift that ever so slightly to something like “is what we’re doing on track to achieve our goals?”. 

But of course, that’s a slow process without some kind of formal learning. It doesn’t have to be a 3-day retreat to learn the meaning of accountability, but you do need some kind of baseline material to set and reinforce expectations. Maybe write a working agreement with the team or a company manifesto. Gather examples of people modeling good behaviour and broadcast public kudos around instances that fit your criteria. 

And then there’s levity. I added levity because I think it’s the antidote to the notion of accountability being boring, intimidating, and terrifying all at once. (Also, I needed another word that starts with ‘L’.) Most of us in the digital space don’t work in life and death situations, so what’s at stake for us is efficiency, comradery, and opportunities for personal and professional growth. In other words, I think it’s okay to have fun with it. No one said being accountable means becoming a stone-faced assassin. 

What do you think? 

But with all that, I’m interested to know what you think. Have you built a culture of accountability and ownership in a different way? Or where does this model break down? Let me know in the comments!