The Agile Enterprise

Introduction

In the world of software development, tales and metaphors often serve as powerful tools to communicate complex ideas. One such tale is the Brothers Grimm’s “Seven at One Blow,” the story of a humble tailor whose feat is grossly misunderstood—and whose legend is inflated through a simple misunderstanding. Surprisingly, this story mirrors a common pitfall in Agile teams: the misuse of story point estimation, especially when teams or leaders start comparing velocity across different teams or use metrics out of context. In this blog post, we’ll explore the enduring lessons from the tale and how it relates to Agile estimation, the dangers of misunderstanding metrics, and how some may even game the system to appear more successful than they really are.

The Tale of the Humble Tailor

In “Seven at One Blow,” a tailor sits down for breakfast, enjoying his bread and jam. Annoyed by the swarm of flies around him, he swats at them with a single blow and, to his delight, kills seven at once. Pleased with himself, he fashions a belt with the proud inscription: “Seven at One Blow.”

Word of the tailor’s belt spreads, but the meaning is lost in translation. People assume he has slain seven men in a single blow, not seven flies. The tailor’s reputation grows out of proportion: he is invited to undertake dangerous tasks, faces giants, and navigates court intrigue—all because of a misunderstanding. The tailor, clever and resourceful, leverages this misconception to his advantage, surviving and thriving in situations beyond his original station.

The Moral: The Power—and Danger—of Misunderstood Metrics

On the surface, the story is about cleverness and luck. But look deeper, and it’s a cautionary tale about misunderstanding, inflated reputations, and unintended consequences. The tailor never lied outright; he let others draw their own conclusions from an ambiguous metric. This is precisely the risk Agile teams face when story points are used carelessly.

The Role of Story Points in Agile

Story points are a tool for teams to estimate the relative complexity or effort of tasks. They are intentionally abstract: what matters is not the absolute value, but the shared understanding within a team. Story points help teams forecast, plan sprints, and measure improvement over time—within the same team.

However, in many organizations, leaders and stakeholders fall into the trap of treating story points as a universal metric. They start comparing velocity (points completed per sprint) between teams, or even across projects. This is where the confusion—and the problems—begin.

Misunderstanding Story Points: A Recipe for Trouble

Just as the tailor’s “seven at one blow” was misinterpreted, story points are often misunderstood:

1. Inter-team Comparisons: Team A completes 50 points per sprint, Team B only 30—does that mean Team A is more productive? Not necessarily. Each team calibrates points differently, based on its own context, skills, and working agreements.
2. The Illusion of Progress: When velocity becomes a target, teams may unconsciously (or deliberately) inflate their point estimates to create the appearance of improvement—a classic case of “gaming the metric.”
3. Loss of Meaning: Over time, if teams are pushed to “increase velocity,” the original intent of points—as a planning tool—gets lost. The number becomes a vanity metric, divorced from actual value delivered.
4. Misleading Management Decisions: Leaders may make resource allocation or performance decisions based on these flawed comparisons, leading to demotivation and poor outcomes.

Gaming the System: When Metrics Become Targets

The tailor’s story is ultimately one of gaming the system. He never corrects the misunderstanding because it brings him opportunity and status. In Agile, when teams know they’re being compared, some may consciously or subconsciously adjust their estimation practices:

• Inflating Estimates: By assigning higher points to the same level of work, a team can show increased velocity without delivering more value.
• Breaking Down Stories: Teams might split stories into artificially smaller tasks, increasing point counts without changing the actual work.
• Cherry-Picking Tasks: Focusing on easier stories with higher point values to “close the gap.”

These tactics create an illusion of improvement, but the underlying productivity remains unchanged—or even drops, as teams spend time optimizing for the metric rather than the outcome.

Lessons Learned: How to Avoid the Seven-at-One-Blow Trap

1. Context Matters: Just as the tailor’s belt meant something very different to him than to those around him, remember that story points are contextual. Never compare velocities across teams.
2. Focus on Value, Not Vanity: The goal is to deliver value to customers, not to “score points.” Use metrics as a tool for learning and improvement, not as a target.
3. Foster Psychological Safety: Teams should be able to estimate honestly, without fear that the numbers will be misused.
4. Educate Stakeholders: Leaders and managers need to understand what story points do and do not mean. Invest time in explaining the limitations of Agile metrics.
5. Look for Real Improvement: Encourage teams to reflect on their processes and outcomes, not just their numbers. Retrospectives are a better source of insight than velocity charts.

The Bottom Line: Clarity Over Illusion

The tale of “Seven at One Blow” endures because it captures the human tendency to mistake symbols for substance. In Agile, the misuse of story points is our modern-day version of the tailor’s belt: a well-intentioned tool that, when misunderstood, can inflate reputations and create confusion. Let’s learn from the humble tailor—by seeking clarity, using metrics wisely, and focusing on real improvement instead of illusion.

Key Takeaways:

• Story points are relative and team-specific; never use them to compare teams.
• Misunderstood metrics can lead to gaming and distort the truth.
• Focus on outcomes, not appearances.
• Use the tailor’s cleverness as inspiration for honest communication—not sleight of hand.

By keeping these lessons in mind, Agile teams and leaders can avoid the pitfalls of misused metrics and build a culture of genuine, sustainable improvement.

Questions for readers

·Have you ever witnessed or experienced the misuse of story points in your organization? How did it impact team morale and performance?

·What steps can leaders take to ensure Agile metrics are interpreted and used correctly rather than as tools for comparison?

·How can teams foster honest communication about their work without fear that their metrics will be misunderstood or misused?

Introduction

The classic tale of “The Emperor’s New Clothes” by Hans Christian Andersen is more than just a children’s story about vanity and deception. It’s a profound allegory about organisational change, groupthink, and the dangers of unchallenged assumptions. As organisations seek to adopt Agile practices, the lessons from this fable are more relevant than ever. This blog post explores what the emperor’s story teaches us about identifying the right problems, assessing readiness for Agile, navigating conservative cultures, and using data to measure and prove the success of an Agile transformation.

1. The Emperor’s New Clothes: A Parable for Change

In the tale, two swindlers convince an emperor that they can weave a magnificent suit of clothes that is invisible to anyone unfit for their position or “hopelessly stupid.” Everyone, including the emperor’s trusted advisers, pretends to see the clothes, fearing to be exposed as incompetent. Only a child dares to speak the truth: the emperor is, in fact, naked.

Organisations embarking on Agile transformations often fall into similar traps. Initiatives may be launched with fanfare, but uncomfortable truths about readiness, culture, or the real problems to be solved are ignored. Without honest assessment and open communication, organisations risk an “Agile theatre”, where the trappings of Agile are present but the substance is missing.

2. Clearly Identifying the Real Problem

One of the greatest lessons from the fable is the danger of groupthink and the failure to question assumptions. In the context of Agile, this manifests as jumping on the Agile bandwagon without first identifying the real business problems that need solving.

Common Pitfalls

• Adopting Agile as a goal in itself: Agile isn’t a panacea; it’s a means to an end. The real goal might be faster time-to-market, better customer satisfaction, or improved product quality.
• Ignoring the status quo: Without understanding what’s broken, you can’t seek improvement.
• Superficial buy-in: Teams may “do Agile” without believing in its value or understanding its purpose.

Key Questions to Ask

• What business outcomes are we trying to achieve?
• What pains or inefficiencies are currently holding us back?
• How will we know if Agile is working for us?

Lesson from the Tale

Just as the emperor’s advisers refused to admit what they saw, organisations must resist the urge to blindly copy Agile practices. Instead, they should clearly articulate the problems they expect Agile to solve.

3. Assessing Organisational Readiness for Agile

Before launching an Agile transformation, it’s vital to assess whether the organisation is ready for change. The emperor’s tale reminds us of the perils of proceeding without honest self-reflection.

Readiness Factors

• Leadership commitment: Are leaders willing to model new behaviours and challenge old norms?
• Cultural alignment: Is there openness to feedback, experimentation, and failure?
• Team autonomy: Do teams have the authority to make decisions and self-organise?
• Support structures: Are there Agile coaches, training, and resources in place?

Candid Conversations

Open dialogue is necessary to surface concerns, scepticism, and resistance. In the fable, the child’s willingness to speak the truth is what ultimately exposes the illusion. Similarly, organisations must create safe spaces for honest feedback about readiness and obstacles.

4. Agile Teams in a Conservative Culture: Challenges and Strategies

Implementing Agile in a conservative or risk-averse organisation is especially challenging. The emperor’s court is a metaphor for such cultures, where dissent is discouraged and conformity is rewarded.

Common Challenges

• Fear of transparency: Agile values visibility and honesty, which can be threatening in hierarchical cultures.
• Resistance to change: Employees may see Agile as a fad or fear loss of control.
• Lack of psychological safety: Teams may be afraid to speak up when things aren’t working.

Strategies for Success

• Manage Agile Transformation as a project: Define objectives, allocate resources, plan checkpoints, measure outcomes
• Start with pilots: Demonstrate value with small, cross-functional teams before scaling.
• Empower change agents: Identify and support individuals willing to challenge the status quo.
• Celebrate learning and failure: Normalise experimentation and learning from mistakes.
• Communicate relentlessly: Share wins, lessons learned, and the rationale for change.

Tale Connection

Just as the child’s voice broke the spell, so too can courageous individuals shift organisational narratives.

5. Benchmarking the Current State: You Can’t Improve What You Don’t Measure

“If you can’t measure it, you can’t improve it.” Agile transformations must begin with a clear baseline. Otherwise, improvements are invisible—much like the emperor’s supposed clothes.

Steps to Benchmarking

1. Define clear objectives: What does success look like?
2. Collect baseline data: Gather metrics on current performance (e.g., lead time, quality, customer satisfaction).
3. Establish feedback loops: Use retrospectives and reviews to gather qualitative insights.

Avoid Vanity Metrics

Like the emperor’s imaginary garments, some metrics look impressive but are meaningless. Focus on actionable, outcome-oriented measurements that align with business goals.

6. Using Quantitative Metrics to Measure the Impact of Agile

To prove the impact of Agile, organisations need rigorous, quantitative evidence. This helps cut through the illusion of progress and ensures that transformation delivers real value.

Best Practices for Metrics

• Align metrics with business outcomes: Metrics should reflect actual improvements in customer value, speed to market, and quality.
• Track trends over time: Look for sustained improvement, not just one-off gains.
• Use both leading and lagging indicators: Leading indicators (e.g., deployment frequency) predict future success; lagging indicators (e.g., revenue growth) confirm it.
• Foster transparency: Share metrics openly with all stakeholders.

Qualitative Feedback

Quantitative data should be complemented with stories and qualitative feedback from teams and customers. However, you should avoid the ‘story points’ trap. Story points are used to plan by the team that defined and understands them, not to measure output or outcome.

7. Proving Agile Transformation: Telling the Right Story

The ultimate proof of Agile’s value is not in the certifications, titles, rituals or terminology, but in tangible outcomes. To avoid the emperor’s fate, organisations must:

• Show real results: Demonstrate improvements in time-to-market, quality, employee satisfaction, etc.
• Tell compelling stories: Use case studies and testimonials to bring metrics to life.
• Adapt and iterate: Continuous improvement should be part of organisational DNA.

8. The Bottom Line: Dare to See and Speak the Truth

The tale of the emperor’s new clothes is a warning against self-deception and unquestioned conformity. In Agile transformations, it’s easy to fall into the trap of “doing Agile” without achieving meaningful change. By clearly identifying the problem, assessing readiness, confronting cultural challenges, benchmarking the current state, and rigorously measuring impact, organisations can avoid Agile theatre and realise true transformation.

Most importantly, organisations must cultivate the courage to “speak the truth”—to call out what isn’t working and to celebrate real progress. Only then will the emperor truly wear new clothes—and only then will Agile deliver on its promise.

Questions for the readers

·In your organisation, what are some unspoken assumptions or "invisible garments" that might be hindering a successful Agile transformation?

·How does your team currently measure the impact of process changes, and what metrics have been most meaningful in demonstrating real improvement?

·What cultural challenges have you faced when trying to implement Agile practices, and how did you (or could you) overcome them?

Introduction

In the world of Agile delivery, teams strive to achieve rapid, high-quality results through iterative development, collaborative work, and continuous improvement. Agile frameworks, such as Scrum and XP, champion values like transparency, adaptability, and respect for individuals. However, a persistent tension arises when teams try to balance fairness—ensuring equitable workloads, opportunities, and recognition—with optimizing for performance—delivering results quickly and efficiently. Understanding and managing this trade-off is crucial for the long-term health and productivity of Agile teams.

Challenges

1. Uneven Work Distribution

One of the most common challenges in Agile teams is the uneven distribution of work. High performers may consistently take on more complex tasks or larger workloads to maintain velocity, while others may be assigned less demanding work. While this can maximize short-term output, it can foster resentment and disengagement among team members who feel left behind or undervalued.

2. Recognition and Reward Imbalances

Performance-driven environments often celebrate those who deliver the most visible results. This can lead to unfairness when less visible but equally important contributions (like mentoring, code reviews, or documentation) are overlooked. Over time, this imbalance can demotivate team members who feel their efforts are not recognized, undermining the collaborative spirit Agile promotes.

3. Burnout and Well-Being

Pushing for maximum performance can inadvertently encourage overwork, particularly among enthusiastic or high-performing team members. When fairness is sacrificed, the risk of burnout increases, leading to turnover and loss of valuable knowledge. Conversely, a rigid focus on fairness, such as strictly equal task assignment, may slow delivery and frustrate those who wish to take on more responsibility or challenge themselves.

4. Skill Development and Learning Opportunities

Equitable distribution of challenging tasks is essential for skill development across the team. If only a few individuals are entrusted with complex work, others miss out on growth opportunities, leading to skill gaps and dependency on specific team members. Balancing fairness and performance means ensuring everyone has a chance to learn and contribute meaningfully.

Recommendations

1. Foster Open Communication

Encourage regular, honest discussions about workload, recognition, and team dynamics. Retrospectives are a core Agile practice that allows teams to reflect on fairness and performance issues openly. Creating a safe space for feedback ensures concerns are addressed before they become serious problems.

2. Define Clear Success Criteria

Set transparent and inclusive definitions of success that value both visible outputs and behind-the-scenes contributions. Recognize and reward behaviours that support team cohesion, knowledge sharing, and long-term performance, not just immediate delivery.

3. Rotate Roles and Responsibilities

Implement rotating roles or pair programming to share knowledge and spread challenging work across the team. This not only prevents burnout among high performers but also helps less experienced members grow and gain confidence.

4. Use Data Thoughtfully

Track metrics like sprint velocity and work distribution, but interpret them in context. Quantitative data can highlight imbalances, but qualitative insights from team members are equally valuable. Use data to open conversations, not to single out individuals or enforce rigid fairness.

5. Encourage Collaborative Planning

Involve the whole team in sprint planning and task estimation. This promotes a shared understanding of workload and fosters collective ownership of outcomes. Collaborative planning also makes it easier to spot and address potential fairness issues early.

The Bottom Line

Balancing fairness and performance are a continual challenge in Agile delivery. Prioritizing one over the other can lead to disengagement, burnout, or reduced team effectiveness. The most successful Agile teams recognize that fairness and performance are not mutually exclusive. By fostering open communication, sharing responsibilities, and recognizing diverse contributions, teams can build an environment where everyone grows and delivers their best work. Ultimately, the goal is to create a sustainable pace of delivery that values both individual well-being and high performance.

Questions for Readers

·How does your team currently balance fairness and performance in Agile delivery?

·What strategies have you found effective for recognizing less visible contributions?

·How do you ensure learning and growth opportunities are shared across the team?

Introduction

In today’s rapidly evolving business landscape, organizations increasingly rely on cross-functional squads to drive innovation, deliver value, and stay competitive. These Agile teams comprise members from diverse backgrounds—engineering, design, product, marketing, and beyond—working together to achieve a shared goal. Amid this collaboration, however, arises a complex and crucial question: Who owns what, and how do we ensure that ownership is exercised ethically?

Ethical ownership in cross-functional squads goes beyond task allocation and accountability. It addresses how individuals and teams make decisions, share responsibilities, and uphold values that protect stakeholders, users, and the organization itself. As organizations strive for Agility and speed, it’s vital to define clear ethical boundaries and ownership roles to avoid conflicts, reduce risks, and foster trust.

Challenges

Defining ethical ownership in cross-functional squads is not without its hurdles. Some of the most pressing challenges include:

Ambiguity in Roles and Responsibilities

With overlapping skill sets and shared objectives, it’s easy for boundaries to blur. When everyone is responsible, sometimes no one truly is. This ambiguity can lead to missed ethical considerations or, worse, the diffusion of responsibility when something goes wrong.

Conflicting Priorities

Different functions often have diverging priorities—what’s good for engineering efficiency might not align with user privacy, for example. Without clear ethical ownership, these conflicts can result in decisions that benefit one area but harm another, sometimes unintentionally crossing ethical lines.

Lack of Accountability Mechanisms

Cross-functional squads thrive on autonomy, but without transparent accountability structures, it can be difficult to trace decisions back to individuals or sub-teams. This lack of clarity increases the risk of ethical lapses going unaddressed.

 Cultural Differences

Diverse squads bring together people with different cultural norms and ethical standards. Without explicit conversations about values and expectations, misunderstandings can arise and lead to inconsistent or unethical behaviour.

Speed Over Deliberation

Agile methodologies prioritize rapid delivery and iteration. While speed is essential, it sometimes comes at the expense of thorough ethical reflection. Without explicit processes and ownership, teams may inadvertently overlook ethical implications.

Recommendations

To foster ethical ownership in cross-functional squads, organizations and leaders should consider the following strategies:

Establish Clear Roles and Ethical Boundaries

From the outset, define not only what each member is responsible for, but also where ethical accountability lies. Formalize these roles in team charters or working agreements, ensuring that every squad member knows their ethical responsibilities.

 Facilitate Open Ethical Dialogues

Regularly schedule discussions about ethical dilemmas, values, and expectations. Encourage team members to voice concerns and share perspectives, fostering a culture where ethical considerations are integral to decision-making.

 Implement Accountability Frameworks

Introduce mechanisms such as decision logs, peer reviews, or ethical checklists. These tools help trace decisions, clarify ownership, and ensure that ethical standards are maintained throughout the project lifecycle.

 Provide Ethics Training

Offer training tailored for cross-functional teams, covering topics like data privacy, user consent, and responsible innovation. Equip squad members with the knowledge and frameworks they need to identify and address ethical issues.

Empower Ethical Champions

Designate individuals or rotating roles within squads as “ethical champions.” These members are tasked with keeping ethical considerations top-of-mind and ensuring that the team’s actions align with organizational values.

 Align Incentives with Ethical Outcomes

Ensure that performance evaluations and rewards reflect not just results, but also how those results are achieved. Recognize and celebrate ethical behaviour, making it clear that ethical ownership is valued and rewarded.

Leverage Diversity as an Asset

Encourage members to bring their unique perspectives to the table, especially when considering ethical implications. Diverse viewpoints can help identify potential blind spots and lead to more robust, ethically sound decisions.

The Bottom Line

Ethical ownership is essential for cross-functional squads to operate effectively and responsibly. By proactively defining roles, fostering open dialogue, and embedding accountability, organizations can navigate the complexities of modern teamwork. Doing so not only minimizes ethical risks but also builds a culture of trust, innovation, and sustainable success.

As organizations continue to embrace agile, cross-functional ways of working, the question of ethical ownership will only grow in importance. By addressing it head-on, teams can ensure that their collective achievements are not just effective, but also ethically sound and worthy of pride.

Questions for Readers

1. How does your organization currently define and assign ethical ownership within cross-functional teams?

2. What challenges have you faced when balancing speed and ethical decision-making in agile environments?

3. What strategies or practices have been most effective in fostering ethical accountability in your squads?

Introduction

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.

Key Distinction: Technical Skills vs. Ethical Values

To understand why technical excellence is not an ethical value, let’s clarify the distinction:

Ethical values are about discerning right from wrong. They concern honesty, transparency, responsibility, and care for others. Ethical values guide a coach to report metrics truthfully, even when the numbers are inconvenient. They demand that a coach speak up when a process is harming team morale, even if it means risking their reputation or contract.

Technical skills are about competence—how well someone can perform tasks or execute methods. A coach with strong technical skills can run a smooth sprint review, facilitate retrospectives with finesse, and optimize workflow for greater efficiency. But technical skills alone do not guarantee ethical conduct. A technically excellent coach may still choose to misrepresent progress, conceal risks, or push a team past healthy limits.

The difference is not academic. It is practical and consequential. Organizations that ignore the distinction risk tolerating or rewarding unethical behaviour, so long as results keep coming. This is a slippery slope that undermines trust and long-term success.

Critical Insight: Effectiveness vs. Integrity

Technical excellence undeniably boosts effectiveness. A skilled coach can drive transformation, resolve bottlenecks, and help organizations reach ambitious goals. But effectiveness without integrity is dangerous. Ethical values determine whether a coach uses their skills for good or for harm.

Let’s explore some real-world scenarios:

• Manipulating metrics: A technically excellent coach can design dashboards and reports that obscure failures or exaggerate success. Stakeholders see progress, but the reality is hidden. This erodes trust and sets teams up for future failure.
• Enabling toxic leadership: A coach with deep technical expertise can reinforce unhealthy dynamics—such as silencing dissent, rewarding overwork, or prioritizing delivery at any cost. Their skills help toxic leaders achieve quick wins, but at the expense of psychological safety and long-term engagement.
• Delivering harmful transformations: A coach may implement Agile practices in ways that disrupt teams, ignore well-being, or marginalize diverse voices. Change is delivered efficiently, but people feel excluded, burned out, or undervalued.

Technical excellence, when divorced from ethics, becomes a tool for manipulation. Skills amplify the impact—positive or negative—of a coach’s choices. That’s why all credible ethics frameworks for coaching emphasize behaviour over capability. They remind us that what matters most is not just what a coach can do, but how and why they do it.

The Role of Ethical Frameworks in Agile Coaching

Although Agile communities know and accept these risks, there is no Agile Code of Ethics and Professional conduct endorsed by professional bodies and Agile organizations. These frameworks should not measure how many certifications a coach holds or how many sprints they have delivered. Instead, they must outline principles like honesty, respect, responsibility, and care. They should not become checklists or scripts, but guides for reasoning through ambiguous, high-pressure situations.

An Agile Code of Ethics and Professional conduct will help Agile Coaches to:

• Balance competing values: Sometimes, transparency and confidentiality conflict. For example, a team member may confide in a coach about feeling unsafe but ask for privacy. The coach must balance the duty to protect the individual with the responsibility to foster a safe environment for all.
• Recognize harm early: Ethical coaches are vigilant about the well-being of individuals and teams. They notice signs of burnout, exclusion, or unethical directives, and intervene—even when it’s uncomfortable.
• Act with courage despite pressure: Sometimes, upholding ethical values means taking risks—questioning leadership, challenging the status quo, or walking away from lucrative contracts. True courage is not about grand gestures, but about consistent integrity in the face of ambiguity and pressure.

Frameworks do not give answers; they offer principles to help coaches reason through complexity. In Agile environments where ambiguity and change are constant, this principled reasoning is essential.

Bringing It All Together

Ethical Agile coaching is not about rigid rule-following or simply complying with codes of conduct. It is a dynamic, reflective practice that demands ongoing self-awareness, principled reasoning, and moral courage. Technical excellence is an asset, but without ethical grounding, it can become a liability—enabling harm rather than creating value.

The most effective coaches are those who pair their skills with a deep commitment to doing what is right—even when it is difficult, unpopular, or risky. Agile practitioners must challenge themselves and their peers to prioritize integrity above mere capability. This means holding each other accountable, calling out unethical behaviour, and ensuring that our pursuit of excellence never comes at the expense of our values or the well-being of others.

Questions for Reflection

1. Have you encountered situations where technical excellence masked unethical behaviour? What were the consequences?
2. How do you personally distinguish between technical competence and ethical conduct in your work or team?
3. What steps can you take to ensure your pursuit of technical excellence never compromises your ethical values?