November 16, 2026
Recommended Blogs
Quality is shaped by the decisions we make every day, from understanding customer needs and addressing risks early to taking ownership of delivery outcomes. It must be built into how teams think, work and improve, rather than treated as a final checkpoint.
Opus Senior Director Debashis Bhattacharyya (Deb) talks to Sabeeka Lambe, Delivery Excellence Head, about making quality a shared responsibility. They explore how AI can improve delivery, why building quality in from the start makes teams more agile, and how continuous improvement can translate into measurable business outcomes and stronger customer trust.
Deb: What does quality mean to you, beyond the traditional definition?
Sabeeka: I see quality as a mindset, not just a measure of whether something meets a defined standard. It is reflected in how we think, the decisions we make, the questions we ask and the ownership we take for the outcomes we deliver.
Quality cannot be inspected into a product at the end or delegated to a particular team. It has to be built into the way we work, from understanding customer needs to designing, developing, and delivering the solution.
Ultimately, quality is about consistently delivering outcomes our customers can trust. And that starts with each of us taking responsibility for the quality of our own work.
Deb: How do you see AI and automation transforming quality and Delivery Excellence?
Sabeeka: AI gives us a real opportunity to rethink how we deliver, not just how fast we code.
While there is a lot of emphasis on AI in software engineering, I see equal potential in project and delivery management: sharper estimation, earlier risk signals and faster analysis of delivery trends. Take a delivery manager who spends half a day pulling together a status report. AI can automate much of the data gathering, leaving more time to act on what the data is telling us.
The bigger opportunity, though, is questioning whether some of today’s work needs to exist at all. We need to look at the system as a whole, challenge how work flows across teams, identify inefficiencies and rethink processes end to end. AI and automation can be catalysts for this, helping us move beyond making individual tasks faster to fundamentally improving how we work and deliver.
Deb: How does building quality in from the beginning help organizations become more agile?
Sabeeka: Quality and speed are not rivals. How we approach quality determines how quickly we can deliver and adapt.
When we invest early in understanding requirements, getting the design right and addressing risks, we avoid expensive rework later. A requirement clarified in week one costs a conversation. The same gap discovered in UAT can cost a sprint or a PI.
One of the Agile principles puts it well: “Continuous attention to technical excellence and good design enhances agility.” That applies well beyond engineering. Clear requirements, sound planning, and good delivery practices let us respond to change without constant firefighting.
Shifting quality left is about making the right investments early so we can move faster and with more confidence.
Deb: How do you connect quality with business performance and financial outcomes?
Sabeeka: Quality has a direct business impact, and we need to make it far more visible.
The cost of poor quality goes well beyond fixing defects. It includes rework, repeated testing, missed commitments, extended timelines and, eventually, lost customer confidence. Much of it stays hidden because it gets absorbed into “normal” delivery. A team that routinely spends the last week of every release fixing defects rarely records that as a cost, but it is one.
That is why quality should be measured not only through defect counts, but also through productivity, predictability, cost and customer satisfaction.
Deb: How do you keep quality closely aligned with customer expectations?
Sabeeka: We can meet every internal process requirement and still fall short if the outcome does not solve the customer’s problem. That is why customer expectations have to shape how we measure quality.
It means understanding what matters most to each customer, translating that into clear delivery outcomes, and checking regularly whether we are meeting them. It also means looking beyond individual incidents to the recurring feedback and root causes behind them.
Predictability matters too. Customers need confidence not only in what we deliver, but in our ability to meet commitments, flag risks early and respond well when things change.
For me, customer centricity is about closing the gap between what we promise and what customers experience. That is where lasting trust and relationships are built.
Deb: Quality is often seen as one team’s responsibility. How do you build a culture where everyone owns it?
Sabeeka: It starts with a shift in mindset. Every individual and function shapes the outcome through their decisions, commitments and how they work with others.
Delivery Excellence enables this through the right practices and capabilities, but accountability for quality stays with the people closest to the work.
At Opus, we want to build a culture where everyone feels empowered to speak up, challenge existing practices, and contribute ideas. We should be willing to experiment, fail fast, learn fast and use those learnings to improve and focusing on finding better ways forward rather than assigning blame.
Ultimately, quality needs to be part of how we think, work and improve every day, not a checkpoint at the end.
Deb: How do you make continuous improvement translate into measurable results?
Sabeeka: Continuous improvement only works when it stops being an initiative and becomes part of everyday work.
That starts with questioning why we do things the way we do, spotting waste and looking at the system rather than just the individual issue. But spotting an opportunity is the easy part. The value lies in turning it into a measurable result: less rework, faster turnaround, better predictability or a stronger customer outcome.
Data makes the difference. It gives us a baseline, shows whether an intervention is working and tells us where to look next. If an intervention does not deliver a measurable improvement, we need to question whether it is working. AI and automation can make that analysis faster.
The real measure is not how many initiatives we launch, but the difference they make.
Deb: How do you know whether Delivery Excellence itself is adding value?
Sabeeka: The same way we would judge any team: by the difference it makes, not the activity it generates.
If teams see us as reporting overhead, we have missed the point. The questions I ask are simple. Are risks being caught earlier? Is delivery more predictable? Are customers raising fewer recurring issues? Are teams spending less time on rework?
A framework, template or review is only worth keeping if it changes a decision or improves an outcome. Holding ourselves to that standard keeps us honest and ensures we remain useful.
Deb: On a more personal note, what has shaped your philosophy on delivery and excellence?
Sabeeka: Over the years, I have come to see that many delivery challenges are not purely process or technology problems. They have a human side: how we think, how we collaborate, how we make decisions, and how willing we are to own outcomes beyond our immediate role.
The same process can produce very different results depending on the mindset behind it. That idea shapes how I approach Delivery Excellence, and it is also a theme I am exploring in a book I am currently writing.
For me, sustainable excellence comes from combining strong practices, the right capabilities, and a mindset of ownership. The goal is to create an environment where doing better is simply how we work, not something we pursue only when a problem arises.
Deb: Looking ahead, what are your priorities for Delivery Excellence at Opus?
Sabeeka: My focus is on building the capabilities, practices and culture that help Opus deliver with greater quality, predictability and efficiency.
That means identifying delivery risks earlier, embedding quality from the start, using data more effectively, and applying AI and automation where they simplify work and improve decisions. It also means challenging unnecessary complexity so that every process we introduce helps teams deliver better.
Strong partnerships across Engineering, Delivery Management and Account Management matter just as much. Delivery Excellence creates impact by enabling others, not by working in isolation.
Above all, I want us to spend less time reacting to issues and more time preventing them. The goal is simple: consistent excellence, predictable delivery and improvement built into how Opus works.
Accountability and empathy are not opposites. You can hold people to high standards and still make it safe for them to raise problems early. Clear ownership is not the same as blame.


