Large health systems depend on professional groups that see the organization from different vantage points. Physicians bring clinical judgment and specialty expertise. Valerie Powell Stafford, FACHE, who is board-certified in healthcare management and a Fellow of the American College of Healthcare Executives, has more than 25 years of healthcare leadership experience and currently serves as senior vice president and area manager for Kaiser Permanente’s Greater Southern Alameda Area. Her career provides relevant context for a broader leadership capability: working across professional boundaries without treating any one perspective as sufficient on its own.
Boundary-spanning leaders are not trying to become experts in every discipline. They create the conditions for expertise to meet. They know when a decision needs clinical input, when an operating constraint changes what is feasible, when workforce implications require attention, and when community context should alter the design. In a large health system, that connective work helps keep a technically sound decision from becoming an organizationally narrow one.
Professional Boundaries Carry Useful Expertise
Healthcare organizations are built around specialization for good reasons. Clinical disciplines require deep training. Operational functions develop expertise in finance, facilities, technology, supply chain, human resources, and service delivery. Labor representatives work within established rights and workforce structures. Community organizations often understand local conditions that a health system cannot reproduce internally.
The leadership problem begins when those boundaries become barriers to information. A service-line decision may be financially viable but difficult for nursing workflows. A clinical improvement may depend on technology capacity that was not included in the original plan. A scheduling change may appear operationally simple while affecting represented roles or creating access problems for a particular community.
Boundary-spanning leadership preserves specialized expertise while making it easier to see consequences that sit outside one function. The goal is not consensus on every issue. It is a decision process broad enough to reveal important dependencies before the organization commits.
Healthcare Teams Already Cross Disciplines
AHRQ’s TeamSTEPPS framework defines healthcare teams broadly. Teams include clinicians such as physicians and nurses as well as nonclinicians, and they may be permanent or assembled around an emerging need. That definition reflects the reality that care delivery depends on more than one profession.
TeamSTEPPS also places responsibility on leaders to establish clear goals, assign roles, allocate resources, facilitate information sharing, and foster a psychologically safe environment. Those responsibilities apply directly to senior leadership when a problem crosses departments. The larger the system, the more likely it is that no single leader owns every part of the work.
A regional access issue may require physician leaders to interpret clinical demand, nursing leaders to identify workflow implications, operational teams to examine scheduling and capacity, and technology colleagues to assess system constraints. The executive contribution is to make sure those perspectives are assembled around the same problem rather than operating as separate reviews.
Physicians and Nurses See Different Parts of the Same System
Clinical leadership itself is not one perspective. Physicians and nurses often encounter the same patient journey from different positions. A physician may focus on diagnosis, treatment decisions, specialty standards, and clinical variation. Nursing leaders may have greater visibility into care coordination, handoffs, patient education, workload, and how processes function across shifts.
Senior executives benefit when those differences are visible early. A proposed inpatient change may make clinical sense while creating new handoffs. A new ambulatory pathway may improve specialty access but increase coordination work for nursing teams. A documentation change may support one professional need while adding steps to another role.
The executive should not resolve those questions by deciding which profession is right. The leadership task is to understand the interaction and identify what the organization is trying to accomplish. Clinical leaders can then help determine which design protects professional standards while remaining workable across the full care team.
Operational Colleagues Translate Ideas Into Capacity
Large health systems rely on people whose work may be less visible to patients but essential to execution. Finance teams test resource assumptions. Information technology teams determine whether a digital change can be built and supported. Facilities, supply chain, human resources, scheduling, and other operating functions make strategic ideas possible in real settings.
Operational colleagues often identify dependencies that are easy to overlook in an executive discussion. A new service may require space, equipment, hiring, contracting, training, or schedule changes. Those dependencies affect timing and cost before the first patient is served.
Boundary-spanning leaders bring those functions into the conversation soon enough to influence design. That is different from asking them to implement a finished plan. Early operational involvement helps the organization distinguish between an attractive concept and an executable one.
Labor Partners Add a Workforce Lens
Labor relationships create another professional boundary that healthcare executives need to understand. Represented colleagues and labor partners may see how a proposed change affects job responsibilities, staffing patterns, schedules, or established working conditions across several departments.
The Federal Mediation and Conciliation Service describes labor-management forums as structures in which union members and managers meet to identify, discuss, and resolve workplace issues through a collaborative process. The model treats the labor-management relationship as an ongoing channel for problem solving, not only a mechanism that becomes relevant during formal bargaining.
For senior leaders, workforce implications should not be discovered after an operating decision has already hardened. Appropriate labor and employee-relations expertise can help leaders understand which issues require consultation, which belong in formal processes, and where joint problem-solving can improve the work itself.
Community Stakeholders Expand the Definition of Context
Health systems make decisions inside communities whose needs, resources, and histories vary. Community organizations, public agencies, schools, faith-based groups, and other local stakeholders may understand barriers that are difficult to see from inside a medical center or administrative office.
ACHE’s policy on healthcare executives’ responsibility to their communities encourages leaders to collaborate with public health agencies, community organizations, educational groups, government entities, foundations, and other stakeholders. The reason is practical: community health cannot be understood only through internal operational data.
Boundary-spanning leaders know when outside perspectives belong in the decision. A regional access strategy may need context for local transportation. A community health partnership may depend on a nonprofit that already has trusted relationships. A service change may affect one part of the region differently from another. Community input does not replace executive accountability, but it can make that accountability better informed.
Clear Roles Make Collaboration Faster
Cross-professional leadership can become slow when collaboration is mistaken for involving everyone in every decision. Large health systems need clear roles as much as they need a broad perspective. The right question is which expertise is necessary for the decision and where accountability ultimately sits.
AHRQ’s teamwork guidance emphasizes clear goals, defined responsibilities, information sharing, and shared mental models. Those principles help senior leaders structure complex decisions. Some participants may provide evidence. Others may own the implementation. A physician leader may have authority over a clinical standard, while an administrative executive controls the resource commitment. A labor issue may require a formal process that an informal working group cannot replace.
Valerie Powell Stafford recognizes that clarity protects collaboration from becoming ambiguous. People are more willing to contribute candidly when they understand why they are involved, what can still change, and who will make the final decision.
The Executive Role Is to Connect Without Flattening
ACHE’s policy on professionalism calls on healthcare executives to build cultures of trust, respect, and collaboration within their organizations and with outside organizations. That principle matters because boundary-spanning work often involves legitimate disagreement. A physician leader may challenge an operational timeline. A labor partner may raise a concern about how a change affects colleagues. A community stakeholder may question whether a planned service responds to local needs.
The value of this leadership is not that every stakeholder agrees. Complex organizations will continue to contain competing priorities and professional differences. The value is that important decisions can be made with a fuller view of the system and a clearer understanding of who will carry the consequences.
Leaders who span boundaries help physicians, nurses, administrators, operational colleagues, labor partners, and community stakeholders contribute what they know without asking them to become interchangeable. That is how specialization remains a strength while the organization still acts as a connected whole.
