Accountability Structures in Projects

Accountable, Responsible, Ownership I’m back on this topic again because I think the impact of not defining these simple terms properly is significant. Too often organisations talk about responsibility, accountability and ownership as if they are interchangeable, yet they are very different. In organisations where those differences are unclear, decisions stall, projects slow down and frustration grows. Here is the simple version I use with senior leaders to get everyone aligned: Responsible The people who do the work. Execution, action, delivery. There can be several responsible. Accountable One person who is answerable for the result. They sign off, own the quality and make the final call. Only one accountable. Ownership A mindset. It is not a role. It is a personal choice to care about the outcome, step up proactively and go the extra mile. Why your team needs to agree these definitions Because ambiguity kills performance. When definitions are unclear: It becomes harder to hold people to account because no one is sure who owns what. Ownership stays optional because the emotional investment is low. Projects lose momentum because decisions keep waiting for someone to make them. Agreeing the definitions sharpens clarity. It lets you plan who does what, who signs off and who steps in when things get tough. It helps people shift from completing tasks (or not) to genuinely caring about outcomes. If you need more accountability, responsibility or ownership in your organisation, getting clear, shared definitions is a great place to start.

💡RACI & DACI: Governing Complexity and Risk in Construction In today’s mega‑projects, complexity is not an exception, it’s the rule. With EPCM structures, fast‑track schedules, and multi‑country supply chains, one blurred responsibility or a stalled decision can cascade into days of lost productivity, contractual disputes, or safety exposures. Frameworks like RACI and DACI are no longer just governance tools, they are risk‑control instruments. ♟️ Why Traditional Role Charts Fail? In the past, clear lines between engineering, procurement, and construction were enough. Today we face: ✅ Design packages split across continents ✅ Parallel construction and commissioning activities ✅ Digital tools producing more data than most teams can absorb … In such an environment, relying on a classic organigram is dangerous. Without formal responsibility and decision matrices, teams get trapped in: ⛔️ Accountability gaps on critical deliverables ⛔️ Shadow decision‑making by actors with no mandate ⛔️ Risk blind spots where no one owns the escalation … ♟️ RACI in Construction Phases Instead of using RACI as a simple spreadsheet, leading organizations embed it in high‑risk workflows. For example, in temporary works approvals or critical lift planning: 1️⃣ Every package has an A formally identified in the construction execution plan 2️⃣ Consultation (C) goes beyond discipline silos, bringing HSE, constructability, and logistics into early reviews 3️⃣ The I stream is automated through dashboards, ensuring no supervisor is unaware of constraints In my experience, this proactive RACI application is often the difference between a smooth mobilization and a late‑night firefight on site. ♟️ DACI as a Shield Against Decision Latency In modular projects or brownfield turnarounds, delays of 48 hours in a technical approval can freeze cranes, scaffolds, and crews, burning budget by the hour. Applying DACI: 1️⃣ Driver roles are pre‑assigned in the project governance, often embedded in AWP steering or Constructability Reviews 2️⃣ Approver authorities are contractually clarified in Annexes, avoiding escalation loops. 3️⃣ Contributors (cost, planning, methods) have clear SLAs for input 4️⃣ Informed streams ensure the field doesn’t learn about changes after the fact When DACI is neglected, you see decisions floating in endless Teams chats. When DACI is enforced, you see structured, timestamped approvals that stand in audits and claims. ♟️ Risk Mitigation Through Role Clarity In claims and forensic schedule analyses, ambiguity of roles often surfaces as a root cause: ✅ Who was accountable for a late vendor drawing? ✅ Who had the approver authority to release a constrained workface? ✅ Who was consulted before changing a crane configuration? A mature use of RACI and DACI transforms these questions into documented, traceable answers, reducing exposure to contractual penalties and safety incidents. #Construction #Project #RACI #DACI #JESA #AWP #Risk #TheConstructionThinkers

Accountability systems matter more than accountability talks Accountability is often addressed through conversations. Research shows it is enforced through systems. When accountability depends on reminders, escalation, or personality, outcomes vary. When accountability is embedded in structure, results are consistent. What research shows Studies in organizational design and performance management indicate that clear roles, visible metrics, and defined consequences produce higher accountability than verbal expectations alone. Teams perform better when responsibility is explicit and outcomes are observable. Research also shows that ambiguity weakens accountability even when expectations are stated repeatedly. Study-based situations Situation 1: Missed commitments Research found that teams without clear owners and deadlines missed targets more frequently. Introducing visible ownership and tracking improved follow-through without increasing pressure. Situation 2: Performance variability Studies on performance systems show that when outcomes were reviewed consistently and consequences applied predictably, variance decreased and reliability improved. Situation 3: Escalation dependence Research on managerial workload shows that accountability systems reduced the need for constant oversight. Leaders intervened less often while results improved. How effective leaders build accountability systems They assign ownership for outcomes, not tasks They make progress visible They define consequences in advance They review performance on a fixed cadence Accountability should not rely on memory or motivation. It should be automatic.

Holding someone accountable is like eating their lunch for them… because it robs them of the opportunity to take ownership and grow. Instead of doing it for them, the goal should be to create an environment where accountability is built into the culture. Here are a few ways to do that: 1. Set Clear Expectations Upfront - Ambiguity kills accountability. Make sure roles, responsibilities, and expectations are explicitly stated. - Use SMART goals (Specific, Measurable, Achievable, Relevant, Time-bound) so there’s no wiggle room for misinterpretation. 2. Encourage Ownership, Not Micromanagement - Instead of checking in constantly, ask, “What’s your plan to make sure this gets done?” - Shift the conversation from “Did you do this?” to “What’s your next step?” 3. Model Accountability from the Top Down - If leaders dodge responsibility, why would anyone else take it seriously? - Own your mistakes publicly and show what taking responsibility looks like. 4. Make Progress Visible - Use dashboards, scorecards, or shared tracking tools where everyone can see progress (or lack thereof). - Publicly celebrating wins reinforces accountability without shaming failure. 5. Normalize Constructive Consequences - If there are no consequences for failing to follow through, accountability doesn’t exist—it’s just a suggestion. - Tie accountability to outcomes: if someone drops the ball, they should be part of the solution, not just excused. 6. Ask, Don’t Tell - Instead of saying “You didn’t get this done,” ask “What got in the way?” - This keeps the focus on problem-solving rather than finger-pointing. 7. Foster Peer Accountability - When teams hold each other accountable (instead of relying on a boss to do it), things get done faster and more effectively. - Regular check-ins where team members update each other on progress create natural accountability loops. 8. Reinforce Through Recognition, Not Just Criticism - Too often, accountability is only discussed when something goes wrong. - Recognizing and rewarding people who consistently own their work reinforces the right behaviors. The key is to shift accountability from being something done to people to something they take ownership of themselves. What’s been your biggest challenge in building accountability?

Autonomy is often wrongly confused with independence. This mistake negatively affects accountability. People sometimes mistakenly think that giving people autonomy means leaving them completely to their own devices (this is independence). In the organizational sense, autonomy is not the opposite of structure—it’s the freedom to operate WITHIN a structure that supports continuous improvement and accountability. A Lean mindset and approach helps leaders to understand how to foster BOTH accountability and autonomy. Lean leaders do this by intentionally moving away from making people feel like they are "being held accountable" (which feels imposed) and inspiring them to "take accountability" (a sense of ownership that naturally fosters autonomy). Here’s how you can adopt this approach in YOUR team: 🟢 Be clear about goals, roles, and responsibilities: Use tools like RACI charts or visual management boards to clarify who does what. 🔴 Define success together: Involve the team in setting performance standards or KPIs so they have a say in what they’re working toward. 🟣 Encourage regular 1:1 check-ins and team huddles: create spaces for discussing challenges without fear. 🟡 Engage people in problem-solving: Use structured techniques and Kaizen to involve the team in addressing inefficiencies. 🔵 Ask for their ideas first: Instead of directing what needs to change, coach them with powerful questions like, “What do you think is the best next step?” 🟤 Use visual management: Team dashboards or Kanban boards make progress visible, reduce micromanagement and highlight areas needing attention. 🟠 Review metrics as a team: Make this part of regular meetings, so progress and accountability are a collective effort. ⚫ Own your commitments: If you make a mistake or miss a deadline, acknowledge it openly. ⚪ Model humility: Admit when you don’t have all the answers and seek input from the team. (This makes people feel valued!!) 🤔Reflection time for leaders... Are you balancing structure and flexibility in your team? Which of the above could you act on to shape a culture of autonomy?

Most organizations confuse #structure with #accountability. They distribute responsibility so widely that no single person truly owns the outcome, and when results fall short, there is plenty of analysis but very little consequence. This is how #strategy dies: diluted across too many stakeholders and eventually forgotten when the next priority comes. Over the years, I developed a #framework for building robust accountability: confront reality with integrity, set clear and measurable objectives, establish economic logic, align incentives with behavior, assign a single owner, and define the exit. Each step matters, but assigning a single owner is perhaps most critical because committees can advise and debate, but only individuals deliver results. Organizations that follow this sequence execute relentlessly and turn ambitious strategies into tangible results. The ones that skip steps, diffuse responsibility across committees, and allow timelines to drift are the ones wondering years later why so little has changed despite so many strategic plans. What has your experience been with accountability? Does responsibility get assigned clearly or diffused across groups?

Most digital councils look important on the org chart. In reality, many are ceremonial rubber‑stamp forums with excellent catering and zero impact. If a governing council doesn’t have three things, it will not enable real digital innovation: 1️⃣ Autonomy: the right to decide, not just “recommend” If every decision has to bounce between functional heads and the C‑suite, you don’t have governance – you have a bureaucracy. A serious council can: →Approve investments up to a clear threshold →Kill or pivot projects that aren’t working →Reallocate resources between teams No autonomy = no speed. Just more PowerPoints. 2️⃣ Accountability: Whose neck is on the line? With autonomy comes responsibility. The council must be the single point of authority for digital transformation – whether the work sits in finance, sales, IT or marketing. That means: → Defining what success looks like up front → Reviewing a balanced scorecard and milestones in every meeting → Assigning named owners to corrective actions If it’s everyone’s responsibility, it’s no one’s responsibility. 3. Structure: small enough to decide, big enough to be taken seriously! There is a simple pattern: → The bigger the council, the slower the decisions and the fuzzier the accountability. Keep it: → Lean in size → Cross‑functional enough to avoid silos → Empowered to decide in the room, without “taking it offline” to ten other executives Otherwise, you get groupthink, time‑boxed monologues, and “let’s revisit this next month”. If a steering committee can’t: ❌ Say “yes” and “no” to money, ❌ Name who owns outcomes, and ❌ Make decisions in the room, …then it’s not a governance body. It’s a very expensive calendar invite.

Most think accountability means owning mistakes. It doesn't: It's important to take ownership of mistakes - But real accountability goes beyond that. It's not what you do after things go wrong. It means owning outcomes -  Before they go wrong. 12 ways to practice proactive accountability (the kind that builds trust instead of repairing it): 1. Flag Risks Early ↳If you see a timeline or scope slipping, speak up fast ↳Say "I might need to adjust expectations here before this slips" 2. Ask for Help ↳Accountability isn't solo heroics ↳Name what you need before you hit the wall 3. Confirm Assumptions ↳Misalignment hides in what's unsaid ↳Repeat back what you think you're delivering, out loud or in writing 4. Share Progress Regularly ↳Silence breeds worry ↳Send a short update even when there's nothing "done" yet 5. Adjust Scope ↳Don't cling to the original plan if conditions change ↳Re-negotiate priorities early, not after missing them 6. Set Clear Boundaries ↳Overcommitting is under-communicating in disguise ↳Say "I can do X by Friday, not Y" 7. Document Decisions ↳Memory fades - paper doesn't ↳Capture what was agreed and who owns what 8. Clarify Ownership ↳When everyone's responsible, no one is ↳Ask "Who's driving this?" before it drifts 9. Surface Uncertainties ↳You can't manage what you hide ↳Say "I'm 70% confident in this plan, here's what's unclear" 10. Close Loops ↳Follow up on what you promised, even if it's small ↳"Quick note: that item's done" builds quiet trust 11. Reflect Publicly ↳Share lessons, not just results ↳"Here's what I'd do differently next time" 12. Model Calm Ownership ↳Accountability without blame changes team culture ↳Own outcomes without overreacting Proactive accountability doesn't make you perfect. It makes you reliable. And reliability is how trust compounds. Which of these 12 would make the biggest difference in how your team operates? --- ♻️ Repost to inspire others to speak up. And follow me George Stern for more practical tips like these.

One common frustration I hear from executives: teams start strong but lose steam as the year unfolds. Sometimes, the problem starts even earlier—teams stall on setting clear goals, half the year vanishes, and leaders end up pleading for basics like “just send me your objectives.” It’s tempting to label this a performance issue, but often the culprit is the structure the leader has built. Here’s what I see again and again: • Team governance models that, inadvertently, reinforce inconsistency • Rituals that reward short-term reactivity over long-term focus • The belief that motivation can outmuscle weak structure When this happens, leaders slip into micromanaging—or cajoling—each project forward instead of enabling true ownership.   If this sounds familiar, there are a few steps to reset your team’s rhythm.   1. Make meetings about results.  Skip round robin updates.  Go project by project.  Status, problems, and support needed.   2. Define what “done” means.  “Done” isn’t a list of things you are going to do.  It’s a measurable outcome that advances strategy.   3. Assign one owner for each project.  If ownership is fuzzy, accountability evaporates. 4. Tether long-term goals to near-term wins.  Distant goals are too abstract to sustain momentum.  Instead, celebrate progress, problem-solving, and collaboration along the way to keep energy high.  Before you blame the team’s performance, look at the structure you’ve built.  Does it sustain long-term focus or quietly undermine it?  Build the structure to create the environment for solid performance.  

Most AI initiatives look impressive at the demo. Six months later they're quietly falling apart. Same story every time. The team moved fast. Built something that looked remarkable on a slide. Leadership approved the budget. Then it hit the real organization. Messy data nobody had cleaned. No clear owner when something produced a bad output. No way to measure whether it was actually working. No governance to catch problems before they compounded. The technology worked fine. The foundation was never there. That's not an AI failure. That's what happens when an organization builds the roof before it pours the concrete. Here is what foundations first actually looks like: → Data quality before model selection Unreliable data produces unreliable outputs at scale. This step is unglamorous. It is also the step everything else depends on. Most teams skip it because it doesn't make the demo look better. It determines whether the system survives contact with reality. → Ownership before deployment One question must have a clean answer before anything goes live: Who owns this output when something goes wrong? Not "we'll figure it out." A name. A role. A defined accountability. If that requires a meeting to determine, you are not ready to deploy. → Evaluation before scale Scaling a system you cannot measure makes the problem bigger. Not better. Define what good looks like before launch. Measure it. Monitor it. Adjust before the cost compounds. → Governance before growth Guardrails and accountability structures are not bureaucracy. They are the concrete foundation that holds everything above it up. Organizations that skip this step are not moving fast. They are borrowing time. The companies that win with AI over the long term share one trait. They were willing to look slower at the start. They built what nobody could see before they built what everyone would notice. This is the center of what I call the AI Execution Gap. The distance between an AI initiative that impresses in a boardroom and one that holds up under real conditions inside a real organization. Those are not the same thing. Most budgets are allocated as if they are. One question worth bringing to your leadership team this week: If we removed the AI layer from our current initiative tomorrow, what would remain? If the honest answer is not much, that is where the work starts. Not with a new tool. With the foundation. 💾 Save this before your next AI planning session. ♻️ Repost to give someone in your network a more honest picture of what AI transformation actually requires. Follow Gabriel Millien to stay ahead in AI while everyone else plays catch-up. Image Credit: Pascal Bornet