<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>Accountability &amp; Leadership Archives - Kieran Engels</title>
	<atom:link href="https://www.kieranengels.com/category/accountability-leadership/feed/" rel="self" type="application/rss+xml" />
	<link>https://www.kieranengels.com/category/accountability-leadership/</link>
	<description></description>
	<lastBuildDate>Tue, 31 Mar 2026 14:08:54 +0000</lastBuildDate>
	<language>en-US</language>
	<sy:updatePeriod>
	hourly	</sy:updatePeriod>
	<sy:updateFrequency>
	1	</sy:updateFrequency>
	<generator>https://wordpress.org/?v=6.9.4</generator>
	<item>
		<title>Empathy and Accountability Are Not a Trade-Off: Building Governance That Works</title>
		<link>https://www.kieranengels.com/empathy-accountability-governance/</link>
					<comments>https://www.kieranengels.com/empathy-accountability-governance/#respond</comments>
		
		<dc:creator><![CDATA[Kieran Engels]]></dc:creator>
		<pubDate>Tue, 28 Oct 2025 07:49:17 +0000</pubDate>
				<category><![CDATA[Accountability & Leadership]]></category>
		<category><![CDATA[accountability]]></category>
		<category><![CDATA[empathy]]></category>
		<category><![CDATA[governance]]></category>
		<category><![CDATA[leadership]]></category>
		<category><![CDATA[vendor relationships]]></category>
		<guid isPermaLink="false">https://www.kieranengels.com/?p=58</guid>

					<description><![CDATA[<p>Empathy and accountability are complementary forces. Learn how to build governance that is clear, fair, and human-centered.</p>
<p>The post <a href="https://www.kieranengels.com/empathy-accountability-governance/">Empathy and Accountability Are Not a Trade-Off: Building Governance That Works</a> appeared first on <a href="https://www.kieranengels.com">Kieran Engels</a>.</p>
]]></description>
										<content:encoded><![CDATA[
<p>There is a false choice in organizations: be empathetic or be accountable. This choice is manufactured. Empathy and accountability are complementary. Empathy prevents misinterpretation and breakdown in trust. Accountability prevents drift and ambiguity. Both have been distorted: accountability has become associated with blame, empathy with softness. The problem with shared accountability is that it means no one is accountable. Clear accountability means clear ownership. When empathy and accountability work together, trust emerges. This is the foundation for the best vendor relationships. Not soft. Not harsh. Clear and human.</p>



<h2 class="wp-block-heading">KEY TAKEAWAYS</h2>


<div class="ogs-takeaways"><h3 class="ogs-takeaways__title">Key Takeaways</h3><ul class="ogs-takeaways__list"><li>Empathy and accountability are complementary, not opposing forces.</li><li>Empathy ensures mutual understanding; accountability creates clear expectations.</li><li>Shared accountability erodes clarity. Clear ownership strengthens it.</li><li>The best governance is neither soft nor punitive. It is transparent and human-centered</li></ul></div>



<h2 class="wp-block-heading">The False Binary That Breaks Teams</h2>



<p>Leadership teams often believe they must choose. Be empathetic and risk unclear accountability. Or be accountable and risk appearing harsh. This binary is false. It persists because organizations have historically distorted both concepts. Accountability got weaponized into blame. Empathy got reduced to conflict avoidance. Kieran Engels has seen this dynamic destroy vendor relationships within weeks. A team that lacks empathy becomes a team that does not listen. A team that lacks accountability becomes a team with unclear expectations. The result: mutual frustration and escalating conflict.</p>



<p>The truth is: empathy is the precondition for clear accountability. If a vendor does not believe you understand their constraints, they will interpret accountability conversations as punishment. If they do not see empathy, they default to defensive postures. Similarly, if you are empathetic but never clarify what accountability looks like, you are being kind in the moment and cruel later, when misaligned expectations unravel the relationship.</p>



<h2 class="wp-block-heading">What Empathy Really Means in Governance</h2>



<p>Empathy in governance is not softness. It is clarity about context. It is understanding that your vendor has constraints you may not see. They have competing priorities from other clients. They have resource limitations. They have knowledge gaps about your program. Empathy means articulating these constraints explicitly so neither party misinterprets the other. It means asking why before assuming incompetence. It means understanding that when a vendor misses a deadline, the explanation matters because it informs how you course-correct.</p>



<p>Seuss+ builds governance that starts with empathy. Before you set expectations, understand what your vendor is working with. Before you hold them accountable, make sure you have given them the information they need to succeed. Before you escalate a miss, understand whether it is a capability gap or a resource allocation problem. These are not soft conversations. They are clear and direct. They prevent misinterpretation. They build trust.</p>



<h2 class="wp-block-heading">What Accountability Really Means in Practice</h2>



<p>Accountability is not punishment. It is clarity about consequences. It is defining upfront what will happen if expectations are not met. It is measuring progress against those expectations. It is giving feedback when performance drifts. It is following through when adjustments are needed. Accountability becomes harsh only when it arrives as a surprise. When it is expected and consistent, it is experienced as fair.</p>



<p>The core problem with many governance structures is distributed accountability. &#8220;We all own this.&#8221; &#8220;It is on all of us.&#8221; These statements sound collaborative and empathetic. They are actually the death of accountability. When everyone is accountable, no one is. When a program misses a milestone, unclear accountability means unclear corrective action. Vendors experience this as arbitrary. Sponsors experience this as evasion. Redesign accountability to be clear and specific. This vendor owns this deliverable. This sponsor leader owns this decision. This timeline is non-negotiable unless jointly agreed otherwise.</p>



<h2 class="wp-block-heading">Three Scenarios: What Happens When You Get the Balance Right</h2>



<p>Consider a scenario where a CRO misses an enrollment milestone. Without empathy, the response is punitive: escalate, audit, threaten replacement. The vendor becomes defensive. Collaboration ends. Enrollment actually slows because the vendor is protecting itself. With empathy alone, the response is understanding: &#8220;We get it, enrollment is hard. No worries. Let us adjust the timeline.&#8221; Expectations fade. The vendor has no incentive to course-correct. Timeline keeps slipping.</p>



<p>Now consider the third path: empathy and accountability working together. The conversation is direct but human. &#8220;We understand you are experiencing site recruitment challenges. That changes our view of the root cause but not our accountability expectation. We will adjust timeline by two weeks based on your revised recruitment plan. If that plan misses, we need to discuss replacement options. But we want to solve this together first.&#8221; The vendor is heard. But expectations are clear. This conversation is harder than either extreme. It is also the only one that builds sustainable relationships.</p>



<h2 class="wp-block-heading">Three Approaches to Governance: Comparison</h2>



<figure class="wp-block-table"><table class="has-fixed-layout"><tbody><tr><td>Dimension</td><td>Accountability Without Empathy</td><td>Empathy Without Accountability</td><td>Both Combined</td></tr><tr><td>Team Behavior</td><td>Defensive, risk-averse, blame-focused</td><td>Conflict-avoidant, unclear, drifting</td><td>Transparent, corrective, collaborative</td></tr><tr><td>Vendor Response</td><td>Disengaged, minimally compliant</td><td>Complacent, unaware of issues</td><td>Committed, responsive, proactive</td></tr><tr><td>Decision Quality</td><td>Fast but brittle, rework-prone</td><td>Slow, consensus-based, unclear</td><td>Informed, decisive, well-documented</td></tr><tr><td>Trust Level</td><td>Low, transactional</td><td>Low, unclear</td><td>High, reciprocal</td></tr><tr><td>Conflict Resolution</td><td>Escalation, replacement</td><td>Avoidance, resentment</td><td>Direct problem-solving, relationship preserved</td></tr><tr><td>Program Outcome</td><td>Met timeline, damaged relationships</td><td>Missed timeline, drained trust</td><td>Met timeline, strengthened partnerships</td></tr></tbody></table></figure>


<figure class="ogs-quote"><blockquote class="ogs-quote__text"><p>Empathy is the glue. Accountability is the structure. Both are required for governance that works.</p></blockquote><figcaption class="ogs-quote__caption"><cite class="ogs-quote__attribution">Kieran Engels, CEO</cite></figcaption></figure>



<h2 class="wp-block-heading">Key Industry Data</h2>



<p>Retention improves measurably in organizations that invest in customized onboarding, mentorship programs, and inclusive leadership development. (Source: Industry retention analysis)</p>



<p>Senior executive turnover costs 213% of the departing leader&#8217;s annual salary when accounting for recruitment, onboarding, lost productivity, and institutional knowledge gaps. (Source: Leadership development research)</p>



<p>The cost to replace a specialized pharmaceutical or biotech professional ranges from 100% to 200% of annual salary, with senior roles exceeding $500,000 per replacement. (Source: Talent management research)</p>



<p>CRO voluntary separation rates have historically run at 12.5%, compared to a national average of 1.5% across industries. (Source: Industry benchmarks)</p>



<p>Pharmaceutical sales sector average annual turnover is 35%, with 44% of sales representatives leaving within their first two years. (Source: PharmExec)</p>



<h2 class="wp-block-heading">Frequently Asked Questions</h2>


<div class="ogs-faq-block"><div class="ogs-faq-item"><button class="ogs-faq-question" aria-expanded="false" aria-controls="ogs-faq-1">How do I demonstrate empathy without softening accountability expectations?</button><div class="ogs-faq-answer" id="ogs-faq-1"><p>Lead with understanding. Ask questions about constraints, context, and challenges before you respond. Use that information to inform your accountability conversation, not to lower your expectations. For example: &#8220;I understand you faced unexpected site delays. Given that context, here is what we need from you going forward.&#8221; Empathy does not mean accepting underperformance. It means understanding why it happened so you can course-correct effectively.</p>
</div></div><div class="ogs-faq-item"><button class="ogs-faq-question" aria-expanded="false" aria-controls="ogs-faq-2">What does clear accountability look like in a vendor contract?</button><div class="ogs-faq-answer" id="ogs-faq-2"><p>Clear accountability is written into the statement of work as specific deliverables, timelines, success criteria, and consequence management. It defines what happens if a deliverable misses the mark: rework without additional payment, revised timeline with sponsor approval, or if serious, termination for cause. This clarity is empathetic because it prevents surprises.</p>
</div></div><div class="ogs-faq-item"><button class="ogs-faq-question" aria-expanded="false" aria-controls="ogs-faq-3">How do I handle a situation where a vendor blames external factors for missed deliverables?</button><div class="ogs-faq-answer" id="ogs-faq-3"><p>Listen first. Understand what factors they faced. Then distinguish between factors that justify timeline adjustment and factors that do not. External challenges are real. But they are also common in clinical development. The question is whether your vendor was prepared to manage them. If not, that is a capability gap. If yes, that is a planning issue. Either way, accountability remains. The conversation is about shared problem-solving, not blame.</p>
</div></div><div class="ogs-faq-item"><button class="ogs-faq-question" aria-expanded="false" aria-controls="ogs-faq-4">Can shared accountability ever work well?</button><div class="ogs-faq-answer" id="ogs-faq-4"><p>Shared accountability on outcomes can work. Shared accountability on deliverables cannot. For example: both the sponsor and vendor share accountability for program success. But the vendor owns specific deliverables and the sponsor owns specific decisions. Clarity at the task level prevents ambiguity at the outcome level.</p>
</div></div><div class="ogs-faq-item"><button class="ogs-faq-question" aria-expanded="false" aria-controls="ogs-faq-5">What if a vendor needs empathy but refuses to accept accountability?</button><div class="ogs-faq-answer" id="ogs-faq-5"><p>That is a sign the vendor is not right for your program. Empathy is not infinite. If a vendor interprets empathy as acceptance of underperformance and refuses to engage in accountability conversations, the relationship is not salvageable. Your next conversation should be direct: clarify what accountability looks like, and if they cannot operate within it, plan for replacement.</p>
</div></div></div><script data-no-optimize="1" data-no-defer="1" data-no-minify="1">(function(){function ogsFaqInit(){document.querySelectorAll(".ogs-faq-question").forEach(function(btn){if(btn.dataset.ogsBound)return;btn.dataset.ogsBound="1";btn.addEventListener("click",function(e){e.preventDefault();var item=this.closest(".ogs-faq-item");var isOpen=item.classList.contains("is-open");item.classList.toggle("is-open");this.setAttribute("aria-expanded",!isOpen);});});}ogsFaqInit();if(document.readyState==="loading"){document.addEventListener("DOMContentLoaded",ogsFaqInit);}document.addEventListener("rocket-allScriptsLoaded",ogsFaqInit);})();</script><script type="application/ld+json">{"@context":"https://schema.org","@type":"FAQPage","mainEntity":[{"@type":"Question","name":"How do I demonstrate empathy without softening accountability expectations?","acceptedAnswer":{"@type":"Answer","text":"Lead with understanding. Ask questions about constraints, context, and challenges before you respond. Use that information to inform your accountability conversation, not to lower your expectations. For example: &#8220;I understand you faced unexpected site delays. Given that context, here is what we need from you going forward.&#8221; Empathy does not mean accepting underperformance. It means understanding why it happened so you can course-correct effectively."}},{"@type":"Question","name":"What does clear accountability look like in a vendor contract?","acceptedAnswer":{"@type":"Answer","text":"Clear accountability is written into the statement of work as specific deliverables, timelines, success criteria, and consequence management. It defines what happens if a deliverable misses the mark: rework without additional payment, revised timeline with sponsor approval, or if serious, termination for cause. This clarity is empathetic because it prevents surprises."}},{"@type":"Question","name":"How do I handle a situation where a vendor blames external factors for missed deliverables?","acceptedAnswer":{"@type":"Answer","text":"Listen first. Understand what factors they faced. Then distinguish between factors that justify timeline adjustment and factors that do not. External challenges are real. But they are also common in clinical development. The question is whether your vendor was prepared to manage them. If not, that is a capability gap. If yes, that is a planning issue. Either way, accountability remains. The conversation is about shared problem-solving, not blame."}},{"@type":"Question","name":"Can shared accountability ever work well?","acceptedAnswer":{"@type":"Answer","text":"Shared accountability on outcomes can work. Shared accountability on deliverables cannot. For example: both the sponsor and vendor share accountability for program success. But the vendor owns specific deliverables and the sponsor owns specific decisions. Clarity at the task level prevents ambiguity at the outcome level."}},{"@type":"Question","name":"What if a vendor needs empathy but refuses to accept accountability?","acceptedAnswer":{"@type":"Answer","text":"That is a sign the vendor is not right for your program. Empathy is not infinite. If a vendor interprets empathy as acceptance of underperformance and refuses to engage in accountability conversations, the relationship is not salvageable. Your next conversation should be direct: clarify what accountability looks like, and if they cannot operate within it, plan for replacement."}}]}</script>



<h2 class="wp-block-heading">About the Author</h2>



<p><a href="https://www.linkedin.com/in/kierancanisius/">Kieran Engels</a> is CEO and Co-Founder of <a href="https://www.seuss.plus/">Seuss+</a>, a strategy and execution partner helping <a href="https://www.seuss.plus/who-we-help/">biotech sponsors</a> optimize vendor relationships across clinical development. With more than a decade of experience in <a href="https://www.seuss.plus/clinical-trial-vendor-optimization-services/">vendor governance</a>, <a href="https://www.seuss.plus/risk-management-setup-for-biotech-clinical-trials/">risk management</a>, and <a href="https://www.seuss.plus/stage-4-optimization/">clinical trial execution</a>, Kieran works with biotech leadership teams to build the oversight systems that protect timelines, budgets, and data integrity. Learn more at <a href="https://www.seuss.plus/">seuss.plus</a>.</p>
<p>The post <a href="https://www.kieranengels.com/empathy-accountability-governance/">Empathy and Accountability Are Not a Trade-Off: Building Governance That Works</a> appeared first on <a href="https://www.kieranengels.com">Kieran Engels</a>.</p>
]]></content:encoded>
					
					<wfw:commentRss>https://www.kieranengels.com/empathy-accountability-governance/feed/</wfw:commentRss>
			<slash:comments>0</slash:comments>
		
		
			</item>
		<item>
		<title>Failure Isn&#8217;t Always Scientific</title>
		<link>https://www.kieranengels.com/failure-isnt-always-scientific/</link>
					<comments>https://www.kieranengels.com/failure-isnt-always-scientific/#respond</comments>
		
		<dc:creator><![CDATA[Kieran Engels]]></dc:creator>
		<pubDate>Tue, 16 Sep 2025 07:44:56 +0000</pubDate>
				<category><![CDATA[Accountability & Leadership]]></category>
		<category><![CDATA[clinical trial failure]]></category>
		<category><![CDATA[execution failure]]></category>
		<category><![CDATA[governance]]></category>
		<category><![CDATA[program management]]></category>
		<category><![CDATA[scientific failure]]></category>
		<guid isPermaLink="false">https://www.kieranengels.com/?p=52</guid>

					<description><![CDATA[<p>Most clinical failures attributed to science originate in execution gaps: unclear requirements, poor handoffs, unexamined assumptions. Learn to distinguish scientific failure from execution failure.</p>
<p>The post <a href="https://www.kieranengels.com/failure-isnt-always-scientific/">Failure Isn&#8217;t Always Scientific</a> appeared first on <a href="https://www.kieranengels.com">Kieran Engels</a>.</p>
]]></description>
										<content:encoded><![CDATA[
<p>When clinical programs fail, the default assumption is science. The molecule did not work. The patient population was wrong. The design was flawed. But failure is rarely caused by science alone. It happens in the gaps between intent, decision, and execution. A vendor does not understand the requirement and builds the wrong thing. A handoff between teams loses critical context. An assumption about feasibility or timeline was never tested. Leadership makes a decision based on incomplete information and nobody says so. Accountability for execution failure is unclear, so the failure gets attributed to science. If we misdiagnose execution failure as scientific failure, we repeat the pattern. We optimize the wrong thing. We change the protocol instead of the execution system. We blame the science when the problem is in the delivery.</p>



<h2 class="wp-block-heading">Key Takeaways</h2>


<div class="ogs-takeaways"><h3 class="ogs-takeaways__title">Key Takeaways</h3><ul class="ogs-takeaways__list"><li>Most clinical failures attributed to science actually originate in execution gaps: unclear requirements, poor handoffs, unexamined assumptions, or missing accountability for decisions.</li><li>Execution failure happens at the intersection of intent (what we said we would do), decision (what we committed to), and delivery (what actually happened).</li><li>Kieran Engels and Seuss+ help biotech teams distinguish execution failure from scientific failure by building clarity into governance before programs launch.</li><li>Misdiagnosing execution failure as scientific failure leads teams to optimize the wrong variables and repeat the same execution patterns.</li><li>Distinguishing failure types requires clarity in documentation: decision rationale, assumptions tested, accountability assigned, and execution criteria defined.</li></ul></div>



<h2 class="wp-block-heading">The Default Attribution Problem</h2>



<p>When something fails in a clinical program, the first place people look is science. Did the drug work? Was the population right? Was the endpoint sensitive? These are important questions, but they are not the only questions.</p>



<p>The problem is that execution failure and scientific failure look similar from the outside. Both result in a program that does not work. But they require different solutions. If you misdiagnose, you will solve for the wrong problem and repeat the failure.</p>



<h2 class="wp-block-heading">Where Execution Failure Lives</h2>



<p>Execution failure happens in three places. Between intent and decision: leadership decides on a timeline without asking if vendors can deliver it. Between decision and delivery: a vendor understands the requirement differently than leadership intended. In delivery itself: unclear accountability means nobody catches the drift.</p>



<p>These failures are not bugs. They are features of systems that do not have clear governance.</p>



<h3 class="wp-block-heading">Scientific Failure vs. Execution Failure</h3>



<figure class="wp-block-table"><table class="has-fixed-layout"><tbody><tr><td>Dimension</td><td>Scientific Failure</td><td>Execution Failure</td><td>How to Distinguish</td></tr><tr><td>Root Cause</td><td>Drug or biology did not work as expected</td><td>Unclear requirement, poor handoff, missing accountability</td><td>Review decision documentation and assumption testing</td></tr><tr><td>Indicators</td><td>Data shows lack of efficacy or safety signal</td><td>Delivery does not match what was promised or agreed</td><td>Check vendor communication, requirement clarity, handoff records</td></tr><tr><td>Solution Path</td><td>Protocol refinement, patient population adjustment</td><td>Governance improvement, clarity in requirements, accountability assignment</td><td>Trace execution gaps during post-mortem</td></tr></tbody></table></figure>



<h2 class="wp-block-heading">Building Systems to Prevent Misdiagnosis</h2>



<p>The fix is not process. The fix is clarity. Before a program launches, document the intent. What are we trying to prove? What assumptions are we making? What happens if those assumptions break? Who is responsible for each decision? What are vendors committing to?</p>



<p>This documentation serves two purposes. First, it prevents execution failure by making intent explicit. Second, if failure happens anyway, it provides the diagnostic framework to distinguish execution failure from scientific failure.</p>



<p>Kieran Engels and Seuss+ work with biotech teams to build this diagnostic clarity through vendor governance and execution planning. Learn more at seuss.plus/about-us/.</p>


<figure class="ogs-quote"><blockquote class="ogs-quote__text"><p>If we misdiagnose execution failure as scientific failure, we repeat the pattern. We optimize the wrong thing. We change the protocol instead of the execution system.&quot;</p></blockquote><figcaption class="ogs-quote__caption"><cite class="ogs-quote__attribution">Kieran Engels, CEO</cite></figcaption></figure>



<h2 class="wp-block-heading">Key Industry Data</h2>



<p>FDA issued 303 warning letters in FY2025, a 59% increase from FY2024, with 135 directly based on inspection findings. (Source: FDA)</p>



<p>The most frequently cited inspection findings involve safety documentation delays, sponsor failure to monitor, and failure to select qualified monitors. (Source: EMA/FDA analysis)</p>



<p>Responses to Form 483 observations must be submitted within 15 business days. (Source: FDA)</p>



<p>The FDA issues Establishment Inspection Reports within 45 days of completing an inspection, and these become publicly available 3 to 6 months after the conclusion. (Source: FDA)</p>



<p>Inspection readiness planning should begin 6 to 12 months before regulatory submission to ensure all systems, documentation, and personnel are audit ready. (Source: Regulatory affairs guidance)</p>



<h2 class="wp-block-heading">Frequently Asked Questions</h2>


<div class="ogs-faq-block"><div class="ogs-faq-item"><button class="ogs-faq-question" aria-expanded="false" aria-controls="ogs-faq-6">How do we know if a failure is execution-based rather than scientific?</button><div class="ogs-faq-answer" id="ogs-faq-6"><p>Look for patterns in the documentation trail. Is the requirement clear in writing? Did the vendor sign off on feasibility? Are handoffs documented? If the documentation is vague or missing, execution failure is likely. If the documentation is clear and was followed, the failure is more likely scientific.</p>
</div></div><div class="ogs-faq-item"><button class="ogs-faq-question" aria-expanded="false" aria-controls="ogs-faq-7">Can a failure be both scientific and execution-based?</button><div class="ogs-faq-answer" id="ogs-faq-7"><p>Yes. A program can fail because the science does not work and because the trial was not executed properly. But you have to distinguish between them to learn from the failure correctly.</p>
</div></div><div class="ogs-faq-item"><button class="ogs-faq-question" aria-expanded="false" aria-controls="ogs-faq-8">What is the cost of misdiagnosing execution failure as scientific failure?</button><div class="ogs-faq-answer" id="ogs-faq-8"><p>High. You change the protocol instead of fixing the execution system. You repeat the same governance failures on the next program. You lose the learning you should have gained.</p>
</div></div><div class="ogs-faq-item"><button class="ogs-faq-question" aria-expanded="false" aria-controls="ogs-faq-9">Should we always document our assumptions before a program starts?</button><div class="ogs-faq-answer" id="ogs-faq-9"><p>Absolutely. Documented assumptions serve two purposes. They prevent execution failure by making implicit thinking explicit. They enable accurate diagnosis if failure happens anyway.</p>
</div></div><div class="ogs-faq-item"><button class="ogs-faq-question" aria-expanded="false" aria-controls="ogs-faq-10">How does governance prevent execution failure?</button><div class="ogs-faq-answer" id="ogs-faq-10"><p>By embedding clarity into decision-making. Clear requirements mean vendors understand what they are building. Clear accountability means someone is responsible for catching drift. Clear assumptions mean teams test what matters before committing to execution.</p>
</div></div></div><script data-no-optimize="1" data-no-defer="1" data-no-minify="1">(function(){function ogsFaqInit(){document.querySelectorAll(".ogs-faq-question").forEach(function(btn){if(btn.dataset.ogsBound)return;btn.dataset.ogsBound="1";btn.addEventListener("click",function(e){e.preventDefault();var item=this.closest(".ogs-faq-item");var isOpen=item.classList.contains("is-open");item.classList.toggle("is-open");this.setAttribute("aria-expanded",!isOpen);});});}ogsFaqInit();if(document.readyState==="loading"){document.addEventListener("DOMContentLoaded",ogsFaqInit);}document.addEventListener("rocket-allScriptsLoaded",ogsFaqInit);})();</script><script type="application/ld+json">{"@context":"https://schema.org","@type":"FAQPage","mainEntity":[{"@type":"Question","name":"How do we know if a failure is execution-based rather than scientific?","acceptedAnswer":{"@type":"Answer","text":"Look for patterns in the documentation trail. Is the requirement clear in writing? Did the vendor sign off on feasibility? Are handoffs documented? If the documentation is vague or missing, execution failure is likely. If the documentation is clear and was followed, the failure is more likely scientific."}},{"@type":"Question","name":"Can a failure be both scientific and execution-based?","acceptedAnswer":{"@type":"Answer","text":"Yes. A program can fail because the science does not work and because the trial was not executed properly. But you have to distinguish between them to learn from the failure correctly."}},{"@type":"Question","name":"What is the cost of misdiagnosing execution failure as scientific failure?","acceptedAnswer":{"@type":"Answer","text":"High. You change the protocol instead of fixing the execution system. You repeat the same governance failures on the next program. You lose the learning you should have gained."}},{"@type":"Question","name":"Should we always document our assumptions before a program starts?","acceptedAnswer":{"@type":"Answer","text":"Absolutely. Documented assumptions serve two purposes. They prevent execution failure by making implicit thinking explicit. They enable accurate diagnosis if failure happens anyway."}},{"@type":"Question","name":"How does governance prevent execution failure?","acceptedAnswer":{"@type":"Answer","text":"By embedding clarity into decision-making. Clear requirements mean vendors understand what they are building. Clear accountability means someone is responsible for catching drift. Clear assumptions mean teams test what matters before committing to execution."}}]}</script>



<h2 class="wp-block-heading">About the Author</h2>



<p><a href="https://www.linkedin.com/in/kierancanisius/">Kieran Engels</a> is CEO and Co-Founder of <a href="https://www.seuss.plus/">Seuss+</a>, a strategy and execution partner helping <a href="https://www.seuss.plus/who-we-help/">biotech sponsors</a> optimize vendor relationships across clinical development. With more than a decade of experience in <a href="https://www.seuss.plus/clinical-trial-vendor-optimization-services/">vendor governance</a>, <a href="https://www.seuss.plus/risk-management-setup-for-biotech-clinical-trials/">risk management</a>, and <a href="https://www.seuss.plus/stage-4-optimization/">clinical trial execution</a>, Kieran works with biotech leadership teams to build the oversight systems that protect timelines, budgets, and data integrity. Learn more at <a href="https://www.seuss.plus/">seuss.plus</a>.</p>
<p>The post <a href="https://www.kieranengels.com/failure-isnt-always-scientific/">Failure Isn&#8217;t Always Scientific</a> appeared first on <a href="https://www.kieranengels.com">Kieran Engels</a>.</p>
]]></content:encoded>
					
					<wfw:commentRss>https://www.kieranengels.com/failure-isnt-always-scientific/feed/</wfw:commentRss>
			<slash:comments>0</slash:comments>
		
		
			</item>
		<item>
		<title>The Age of Accountability</title>
		<link>https://www.kieranengels.com/age-of-accountability/</link>
					<comments>https://www.kieranengels.com/age-of-accountability/#respond</comments>
		
		<dc:creator><![CDATA[Kieran Engels]]></dc:creator>
		<pubDate>Tue, 02 Sep 2025 07:43:09 +0000</pubDate>
				<category><![CDATA[Accountability & Leadership]]></category>
		<category><![CDATA[accountability]]></category>
		<category><![CDATA[biotech leadership]]></category>
		<category><![CDATA[clinical development]]></category>
		<category><![CDATA[featured]]></category>
		<category><![CDATA[governance design]]></category>
		<category><![CDATA[vendor governance]]></category>
		<guid isPermaLink="false">https://www.kieranengels.com/?p=50</guid>

					<description><![CDATA[<p>The Age of Accountability resets biotech priorities: clarity of intent, explicit ownership, delivery that matches promise. Speed without control is crash risk. Accountability builds confident acceleration.</p>
<p>The post <a href="https://www.kieranengels.com/age-of-accountability/">The Age of Accountability</a> appeared first on <a href="https://www.kieranengels.com">Kieran Engels</a>.</p>
]]></description>
										<content:encoded><![CDATA[
<p>The biotech industry has optimized for speed, for optics, for reassurance. We have built systems that prioritize the appearance of progress and the promise of delivery over the clarity of intent and the accuracy of execution. The Age of Accountability is a reset. It demands clarity of intent: what are we actually trying to achieve? It demands explicit ownership: who is responsible for what? It demands delivery that matches promise. Speed without control is not acceleration. It is crash risk. Many failures are not scientific failures. They are execution failures in the gaps between intent, decision, and delivery. Accountability and empathy are complementary, not opposed. Tools are inputs to judgment, not substitutes for it. Governance is a design system, not a bureaucratic obstacle.</p>



<h2 class="wp-block-heading">Key Takeaways</h2>


<div class="ogs-takeaways"><h3 class="ogs-takeaways__title">Key Takeaways</h3><ul class="ogs-takeaways__list"><li>The biotech industry has optimized for speed and optics at the cost of clear intent and executable strategy. The Age of Accountability resets these priorities.</li><li>Clarity of intent means knowing what you are building and why. Explicit ownership means assigning responsibility for execution. Delivery that matches promise means doing what you said you would do.</li><li>Speed without control is crash risk, not acceleration. Kieran Engels and Seuss+ help teams align pace with capability and build controls that enable confident decision-making.</li><li>Many clinical failures attributed to science are actually execution failures: unclear accountability, poor handoffs, unexamined assumptions, gaps between decision and delivery.</li><li>Governance enables accountability by creating clarity in decision-making, responsibility assignment, and delivery verification.</li></ul></div>



<h2 class="wp-block-heading">The Illusion of Speed</h2>



<p>We have been taught to optimize for speed. Faster timelines. Faster decisions. Faster approval. But speed without control creates risk. A trial that moves fast but loses data integrity is not a success. A program that accelerates but loses track of what was promised is not progress. The illusion of speed comes from decoupling pace from accountability.</p>



<p>Accountability requires clarity. What are we committing to? Who is responsible if we miss? What are we assuming will go right? What is our contingency if assumptions break?</p>



<h2 class="wp-block-heading">Execution Failure vs. Scientific Failure</h2>



<p>When clinical programs fail, the default assumption is science. The drug did not work. The design was flawed. But many failures are execution failures. Poor handoffs between teams. Unclear accountability for decisions. Vendors operating without clear requirements. Requirements that vendors cannot actually meet.</p>



<h3 class="wp-block-heading">What We Optimized For vs. What Accountability Requires</h3>



<figure class="wp-block-table"><table class="has-fixed-layout"><tbody><tr><td>What We Optimized For</td><td>What Accountability Requires</td></tr><tr><td>Speed</td><td>Pace aligned with control capability</td></tr><tr><td>Optics (appearance of progress)</td><td>Accuracy of execution</td></tr><tr><td>Reassurance</td><td>Clarity of intent and explicit ownership</td></tr><tr><td>Avoiding difficult questions</td><td>Examining assumptions before execution</td></tr><tr><td>Tools as substitutes for judgment</td><td>Tools as inputs to judgment</td></tr></tbody></table></figure>



<h2 class="wp-block-heading">Building for Accountability</h2>



<p>Accountability starts with clarity. What is the decision? Who made it? On what basis? What conditions would make us revisit it? These questions are not obstacles to speed. They are the foundation of confident speed.</p>



<p>Kieran Engels works with sponsors to build systems that embed accountability into governance. Not as punishment, but as clarity. When roles are explicit, decisions are documented, and assumptions are tested, teams move faster because they move with confidence.</p>



<p>Learn more about how Seuss+ helps teams build governance systems at seuss.plus/clinical-trial-vendor-optimization-services/.</p>


<figure class="ogs-quote"><blockquote class="ogs-quote__text"><p>Speed without control is crash risk. Accountability is not an obstacle to progress. It is the foundation of confident acceleration.</p></blockquote><figcaption class="ogs-quote__caption"><cite class="ogs-quote__attribution">Kieran Engels, CEO</cite></figcaption></figure>



<h2 class="wp-block-heading">Key Industry Data</h2>



<p>The FDA formally adopted ICH E6(R3) on September 9, 2025, replacing the previous Good Clinical Practice framework with a risk based, proportionate oversight model. (Source: FDA)</p>



<p>The MHRA has classified ICH E6(R3) adoption as a major event in GCP, signaling that inspection criteria will shift toward Quality by Design assessment. (Source: MHRA)</p>



<p>Only 11.8% of drugs entering clinical testing ultimately receive regulatory approval, underscoring the cost of governance failures compounding scientific uncertainty. (Source: Tufts CSDD)</p>



<p>FDA warning letters surged 59% year over year in FY2025, from 190 to 303, reflecting heightened regulatory enforcement across the industry. (Source: FDA)</p>



<p>Trial delays cost sponsors $600,000 to $8 million per day, making accountability gaps not just a compliance risk but a direct financial exposure. (Source: Tufts CSDD)</p>



<h2 class="wp-block-heading">Frequently Asked Questions</h2>


<div class="ogs-faq-block"><div class="ogs-faq-item"><button class="ogs-faq-question" aria-expanded="false" aria-controls="ogs-faq-11">Is accountability the same as blame?</button><div class="ogs-faq-answer" id="ogs-faq-11"><p>No. Blame is backward-looking and punitive. Accountability is forward-looking and clarifying. It assigns responsibility for decisions and delivery so teams know what to expect and what is expected of them.</p>
</div></div><div class="ogs-faq-item"><button class="ogs-faq-question" aria-expanded="false" aria-controls="ogs-faq-12">How do we build accountability without creating blame culture?</button><div class="ogs-faq-answer" id="ogs-faq-12"><p>By making accountability about clarity, not consequences. Document the decision, the assumptions, the rationale. When something breaks, learn why. Did the assumption fail? Did the execution miss? Was the decision wrong? This investigation is diagnostic, not punitive.</p>
</div></div><div class="ogs-faq-item"><button class="ogs-faq-question" aria-expanded="false" aria-controls="ogs-faq-13">Does accountability slow down decision-making?</button><div class="ogs-faq-answer" id="ogs-faq-13"><p>No, it accelerates it. When people know the decision will be documented and assumptions will be tested, they make decisions faster and more confidently. They do not second-guess as much because the framework is clear.</p>
</div></div><div class="ogs-faq-item"><button class="ogs-faq-question" aria-expanded="false" aria-controls="ogs-faq-14">What role does empathy play in accountability?</button><div class="ogs-faq-answer" id="ogs-faq-14"><p>Empathy means understanding the constraints and pressures people face. Accountability means being clear about expectations despite those constraints. They are complementary. You can be empathetic about challenges and accountable about delivery.</p>
</div></div><div class="ogs-faq-item"><button class="ogs-faq-question" aria-expanded="false" aria-controls="ogs-faq-15">How does Seuss+ help build accountability systems?</button><div class="ogs-faq-answer" id="ogs-faq-15"><p>Through governance design. We help teams clarify decision criteria, assign responsibility, document assumptions, and create verification points. This creates the structure in which accountability can flourish.</p>
</div></div></div><script data-no-optimize="1" data-no-defer="1" data-no-minify="1">(function(){function ogsFaqInit(){document.querySelectorAll(".ogs-faq-question").forEach(function(btn){if(btn.dataset.ogsBound)return;btn.dataset.ogsBound="1";btn.addEventListener("click",function(e){e.preventDefault();var item=this.closest(".ogs-faq-item");var isOpen=item.classList.contains("is-open");item.classList.toggle("is-open");this.setAttribute("aria-expanded",!isOpen);});});}ogsFaqInit();if(document.readyState==="loading"){document.addEventListener("DOMContentLoaded",ogsFaqInit);}document.addEventListener("rocket-allScriptsLoaded",ogsFaqInit);})();</script><script type="application/ld+json">{"@context":"https://schema.org","@type":"FAQPage","mainEntity":[{"@type":"Question","name":"Is accountability the same as blame?","acceptedAnswer":{"@type":"Answer","text":"No. Blame is backward-looking and punitive. Accountability is forward-looking and clarifying. It assigns responsibility for decisions and delivery so teams know what to expect and what is expected of them."}},{"@type":"Question","name":"How do we build accountability without creating blame culture?","acceptedAnswer":{"@type":"Answer","text":"By making accountability about clarity, not consequences. Document the decision, the assumptions, the rationale. When something breaks, learn why. Did the assumption fail? Did the execution miss? Was the decision wrong? This investigation is diagnostic, not punitive."}},{"@type":"Question","name":"Does accountability slow down decision-making?","acceptedAnswer":{"@type":"Answer","text":"No, it accelerates it. When people know the decision will be documented and assumptions will be tested, they make decisions faster and more confidently. They do not second-guess as much because the framework is clear."}},{"@type":"Question","name":"What role does empathy play in accountability?","acceptedAnswer":{"@type":"Answer","text":"Empathy means understanding the constraints and pressures people face. Accountability means being clear about expectations despite those constraints. They are complementary. You can be empathetic about challenges and accountable about delivery."}},{"@type":"Question","name":"How does Seuss+ help build accountability systems?","acceptedAnswer":{"@type":"Answer","text":"Through governance design. We help teams clarify decision criteria, assign responsibility, document assumptions, and create verification points. This creates the structure in which accountability can flourish."}}]}</script>



<h2 class="wp-block-heading">About the Author</h2>



<p><a href="https://www.linkedin.com/in/kierancanisius/">Kieran Engels</a> is CEO and Co-Founder of <a href="https://www.seuss.plus/">Seuss+</a>, a strategy and execution partner helping <a href="https://www.seuss.plus/who-we-help/">biotech sponsors</a> optimize vendor relationships across clinical development. With more than a decade of experience in <a href="https://www.seuss.plus/clinical-trial-vendor-optimization-services/">vendor governance</a>, <a href="https://www.seuss.plus/risk-management-setup-for-biotech-clinical-trials/">risk management</a>, and <a href="https://www.seuss.plus/stage-4-optimization/">clinical trial execution</a>, Kieran works with biotech leadership teams to build the oversight systems that protect timelines, budgets, and data integrity. Learn more at <a href="https://www.seuss.plus/">seuss.plus</a>.</p>
<p>The post <a href="https://www.kieranengels.com/age-of-accountability/">The Age of Accountability</a> appeared first on <a href="https://www.kieranengels.com">Kieran Engels</a>.</p>
]]></content:encoded>
					
					<wfw:commentRss>https://www.kieranengels.com/age-of-accountability/feed/</wfw:commentRss>
			<slash:comments>0</slash:comments>
		
		
			</item>
	</channel>
</rss>
