Project Management

Home / Discussions / Project Management Central /

Have you encountered situations where technical excellence masked unethical behaviour?

Agile Ethics Leadership

Stelian ROMAN Project Manager| MicroSafety Carlingford, New South Wales, Australia

In today’s complex and fast-moving business world, the demand for Agile transformation has never been higher. Organizations are investing heavily in Agile coaches—individuals who can accelerate change, foster collaboration, and unlock team potential. Often, the search for the “right” coach centres around technical credentials: certifications from respected bodies, years of experience, and proven mastery of frameworks. This focus on technical excellence is understandable. After all, technical skills are necessary to navigate the intricacies of Agile methods and deliver tangible results.

Yet, there is a critical oversight lurking beneath this obsession with skill: technical excellence is not the same as ethical value. A coach can be highly skilled, highly experienced, and highly certified—and still behave unethically. This is not just a theoretical concern. Across industries, there are countless stories of brilliant coaches who, despite their abilities, enabled toxic cultures, manipulated results, or prioritized delivery over people’s well-being.

Why does this happen? Because technical prowess and ethical integrity operate on fundamentally different axes. Mastery of Agile, Lean, or organizational change is about competence—doing things right. Ethics, on the other hand, is about doing the right thing. When organizations conflate these two, they risk empowering coaches who deliver impressive results at the cost of trust, transparency, and long-term health. This blog post explores why technical excellence should never be mistaken for ethical value, especially for Agile coaches. We will examine the crucial differences, reflect on the dangers of technical ability without ethical grounding, and offer practical guidance for coaches and organizations alike.

- Have you encountered situations where technical excellence masked unethical behaviour?

- What were the consequences?

- How do you personally distinguish between technical competence and ethical conduct in your work or team?

- What steps can you take to ensure your pursuit of technical excellence never compromises your ethical values?

Blogpost: Why Technical Excellence Is NOT an Ethical Value for Agile Coaches

ProjectManagement.com - The Agile Enterprise

Posted: Jun 19, 2026 1:27 AM

Sort By:

Luis Branco CEO| Business Insight, Consultores de Gestão, Ldª Carcavelos, Lisboa, Portugal

An important distinction.

Technical excellence does not guarantee ethical behavior.
A highly skilled coach can still make decisions that undermine trust, transparency or team well-being.

At the same time, ethical intentions alone do not guarantee responsible outcomes. Good intentions without sufficient competence can also create harm.

Perhaps the deeper challenge is not choosing between technical excellence and ethics, but integrating competence, judgment and integrity.

Sustainable leadership requires all three.
Technical skill determines what we are capable of doing. Ethics helps us decide what we should do. Judgment helps us navigate the complex space between them.

Posted: Jun 19, 2026 6:51 AM

Sreesudha Ayyalasomayajula Software Project Manager| ZF group New Hudson, MI, United States

Interesting blog

Posted: Jun 19, 2026 9:04 AM

Zeinab Abdraboh Complex Program Manager| CoorB

This is a critical question that touches on one of the most insidious risks in technology-driven projects. Technical excellence can indeed mask unethical behavior, and the mask is often invisible to those not looking for it.

I have seen this pattern in several forms. Beautifully engineered recommendation systems that optimize for engagement while exploiting addictive behaviors. Technically flawless data pipelines that process personal information without meaningful consent. Elegantly designed algorithms that perpetuate discriminatory patterns because the training data reflected historical biases.

The common thread is that when a system works perfectly from a technical standpoint, there is a strong organizational tendency to not question its ethical implications. Teams celebrate the engineering achievement and the business metrics without examining who is being harmed.

Project managers play a crucial role in breaking this pattern. We need to create space in our project processes for ethical reflection that is separate from technical review. A system can pass all quality gates and still be ethically problematic. This means adding ethical review as a distinct checkpoint, not bundled into technical review where it gets overshadowed.

The antidote is cultivating what I call ethical curiosity within project teams: a habit of asking not just does it work but should it work this way, and who bears the cost of its success. When technical excellence and ethical awareness work together, we build systems that are truly worthy of pride.

Posted: Jul 18, 2026 1:18 PM

Sayed Zaidi Kashif Mekhdi Architect Projects Engineer| Kuwait Oil Company Salmiya, KU, Kuwait

This is a massive blind spot in enterprise transformations. When organizations prioritize delivery metrics above all else, they inadvertently create air cover for brilliant but toxic behavior.

The "High-Performer" Trap: We frequently see "toxic geniuses" tolerated because their teams hit sprint goals or clear backlogs quickly. The short-term consequence is an impressive dashboard; the long-term consequence is cultural bankruptcy, psychological unsafety, and high turnover.

Separating Competence from Conduct: Competence is capability (can they do the job?); ethics is intent and impact (how do they treat people while doing it?). In performance reviews and hiring, we must elevate cultural and behavioral alignment to the exact same weight as technical certifications.

Guardrails for Leadership: Ensure your definition of success includes how goals are achieved, not just if they were met. If a coach accelerates delivery but leaves a trail of high turnover and low trust, they haven't transformed the organization—they've compromised it.

Posted: Jul 19, 2026 8:49 AM

Robert Snyder Founder & President| Innovation Elegance, LLC Chicago, Il, United States

We formulated, implemented, and continue to execute software methodologies.
I love the idea of formulating, implementing, and executing a trustworthiness methodology.

A new buzzword is "AI native."
I wonder if any company likes the idea of being "trustworthiness native."

Trustworthiness feels like CHI ... "Collective Human Intelligence."

Where would you prefer the hype be? AI or CHI?

Posted: Jul 19, 2026 3:08 PM

Robert Snyder Founder & President| Innovation Elegance, LLC Chicago, Il, United States

Ethics. Trustworthiness.

Trustworthiness = Competence AND Honesty AND Dependability AND Benevolence.

Untrustworthiness = Incompetence OR Dishonesty OR Low Dependability OR Malevolence.

Many organizations have systemic tolerance for untrustworthiness.

I wish more of us had systematic intolerance for untrustworthiness.

Imagine language, templates, and habits to ...

Minimize the cost to detect untrustworthiness

Minimize the cost to reassign for untrustworthiness

Minimize the cost to change expectations

Minimize the cost to realign on new expectations

Methodical Trustworthiness.

High Discipline.

High Empathy.

I think it's possible, it's compelling, and it would be disappointing to not pursue it.

Posted: Jul 19, 2026 3:15 PM (Updated by author: Jul 19, 2026 3:16 PM)

Please login or join to reply

Have you encountered situations where technical excellence masked unethical behaviour?

Sponsors

Newsletters