techbullion.com

What Working Across Engineering, Product, and Customer Teams Taught Sapna Baalwan About Leadership

By Victor Miller·Published November 16, 2026·Business news, Technology

Sapna Baalwan — leadership across engineering, product and customer teams

Technology projects rarely fail because of one bad decision. More often, trouble builds slowly as different teams make reasonable choices based on different priorities.

An engineering team can deliver a technically sound solution while customers still struggle to adopt it. Product managers can prioritize features that fit the long-term roadmap while customer-facing teams fight immediate operational problems. A project can hit every implementation milestone and still fall short of the business value it promised.

These situations point to a persistent challenge in technology organizations: the gap between technical execution and what customers actually experience.

Sapna Baalwan, a technology and project management professional with more than a decade of experience across enterprise software, AI-driven SaaS platforms, and healthcare technology, has spent much of her career working in that gap. Coordinating engineering, product, business, and customer-facing teams has given her a practical view of leadership. In her experience, the greatest value often comes from spotting the problems that form between teams, more than from managing any one team more closely.

“Most of the problems I’ve seen weren’t inside any one team,” Baalwan says. “Each group had done its part well. The trouble was in the handoffs, in the assumptions nobody had checked with the other side.”

When Every Team Is Right, but the Outcome Is Still Wrong

One of the harder realities of cross-functional work is that every team can do its job well while the project as a whole falls short.

Engineering optimizes for performance and stability. Product focuses on scalability and the roadmap. Customer-facing teams care about adoption, usability, and what clients need right now. Each of these priorities is legitimate. Problems start when decisions are made in isolation, without enough thought about their effect on everyone else.

Baalwan has worked through these competing expectations many times, especially during customer onboarding, product implementations, and conversations about technical delivery commitments. That work taught her to separate communication from alignment. Communication means information gets exchanged. Alignment means each team understands how its decisions affect the others, and which trade-offs are needed to reach a shared goal.

In practice, an urgent customer request shouldn’t automatically become an engineering priority. A technical limitation shouldn’t end the conversation either, before anyone has looked at the business problem behind the request. The more useful questions are what the customer is trying to accomplish, whether the current product can support it, and what change would create real value.

Why Customer Problems Are Often Misdiagnosed

Enterprise software companies invest heavily in building products, yet some of the most important challenges show up after implementation. A deployment can succeed technically and still struggle because employees weren’t trained, business processes didn’t change, or the tool doesn’t fit how people already work. These issues are easy to mistake for product gaps.

In her customer-facing roles, Baalwan focused on finding the barriers that hold back engagement and continued use. That meant assessing adoption risks, building mitigation plans, turning customer feedback into product recommendations, and working with technical teams during testing and feature rollouts.

The core skill is separating symptoms from causes. Low adoption doesn’t necessarily mean the software is missing features. It can reflect unclear expectations, resistance to change, thin onboarding, or trouble fitting the platform into existing processes. Each cause needs a different fix. New features won’t solve a training problem, and more support staff won’t fix a technical limitation.

“When a customer tells me the product isn’t working, my first question is what they were hoping it would let them do,” she says. “Often the answer points to a process or a training gap rather than a missing feature.”

At one previous company, that approach contributed to a [X]% improvement in [customer adoption / retention] over [timeframe].

The Hidden Cost of Knowledge That Lives Only in People’s Heads

Some of the costliest inefficiencies in technology organizations never show up in a project plan or a budget. They appear when employees hunt for documentation, wait on one particular colleague for routine answers, or rebuild knowledge that already exists somewhere else. As teams grow, these small frictions become real constraints.

Baalwan has tackled this through process standardization, technical documentation, and knowledge sharing. At one enterprise technology company, she led the creation of a centralized knowledge base that opened specialized technical information to a much wider group of employees. At another, she helped set up standard procedures for key stages of the customer success journey, which made day-to-day operations noticeably more efficient.

The principle behind both efforts is the same: knowledge becomes more valuable when people can find and use it without tracking down whoever created it. Leaning on the same few experts to solve familiar problems often signals that important knowledge hasn’t been shared widely enough. Good standardization doesn’t replace professional judgment. It strips away needless complexity so people can save their expertise for the work that really needs it.

Why Healthcare Technology Raises the Stakes

The need to align technical execution with operational reality is especially clear in healthcare. Healthcare technology often handles information that feeds quality reporting and administrative processes and, ultimately, supports care delivery. A successful integration is only part of the job. The information also has to be accurate, consistent, available when it’s needed, and fit for its purpose.

Baalwan’s healthcare technology work has included supporting data integration and software implementation efforts and aligning technical and business stakeholders around shared requirements. She has also worked with healthcare quality data, where accuracy directly affects how organizations measure and improve care.

Across the industry, data-intensive projects show why leadership here goes beyond managing timelines. Different groups may supply, process, validate, and use the same information. Finishing a technical integration doesn’t prove the data meets every operational need. Data definitions, validation steps, clear ownership, and readiness for ongoing use all have to be addressed too.

The lesson applies well beyond healthcare: finishing the technical work is not the same as proving a system delivers the value it was built for.

“A go-live date tells you the systems are connected,” Baalwan says. “It doesn’t tell you whether people can trust the data coming through. That second part is where the real work is.”

Leadership Also Means Reducing Dependence on the Leader

Technology organizations rely on experienced people who know the history behind decisions, the details of customer relationships, and the quirks of internal systems. They’re valuable because they can solve problems others can’t. Yet relying on a handful of people also limits how far an organization can scale. When knowledge stays concentrated, routine decisions get escalated, onboarding slows down, and continuity gets harder.

Throughout her career, Baalwan has trained technical professionals, helped new employees step into customer-facing roles, and mentored teams on complex operational projects. The goal isn’t to remove oversight or accountability. It’s to make sure people know which decisions are theirs to make, what information they can draw on, and when to bring in more expertise.

That matters most in cross-functional settings, where progress depends on people working across departmental lines. Leaders who invest in sharing knowledge and making operations clear can cut recurring bottlenecks and build a stronger base for growth.

“I know I’ve done my job when the team stops calling me for the routine questions,” she says. “They still bring me the hard ones, and that’s how it should be.”

AI Makes Cross-Functional Judgment More Important

The spread of AI into enterprise software has renewed interest in automation and productivity. Still, the challenges that slow ordinary software adoption don’t go away when AI is added. A system can look impressive in testing and still struggle once it meets a real organization. Employees may not know how to fit it into their work, product teams may underestimate integration needs, and customer expectations may outrun what the technology can reliably do.

Those problems don’t necessarily mean the technology is weak. Often they reflect a mismatch between what a tool can do and how an organization actually runs. Engineering teams need to understand the environments their systems will live in. Product teams need insight into real user needs, not assumed ones. Customer-facing teams need to describe both the possibilities and the limits honestly.

Baalwan’s background across AI-driven SaaS, enterprise adoption, and healthcare gives her a practical lens on these questions. As AI becomes part of more business processes, leaders will increasingly need to tell the difference between what a technology can do and whether an organization is ready to use it.

“Organizations spend a lot of time evaluating the tool and much less evaluating themselves,” she says. “The technology is often ready well before the workflows, the training, and the expectations are.”

Rethinking What Effective Technology Leadership Looks Like

Traditional ideas of leadership stress authority, strategic vision, and managing teams. Those still matter. Modern technology organizations, though, increasingly depend on a different skill: working across specialized functions and catching the problems that belong to no single team.

Across enterprise software, customer-facing operations, and healthcare data work, Baalwan’s career has centered on that skill. She has identified adoption barriers, reconciled technical and business requirements, strengthened operational processes, and built team capability. The common thread is no single product or company. It’s the recognition that success depends on how well an organization connects specialized expertise to practical outcomes.

As companies invest in more complex platforms and AI-enabled systems, building sophisticated technology is only half the question. The other half is whether they have the processes, accountability, and shared understanding to use it well. The leaders who matter most in that environment may be the ones who improve how decisions get made across the organization, rather than the ones who make the most decisions themselves.

Her advice to new technology leaders is simple. “Spend time in the meetings that aren’t yours,” she says. “You’ll learn more about where a project is going wrong from the people downstream of it than from any status report.”