How Poor Influence Skills Reinforce Organizational Silos
Learn how weak influence behaviors can reinforce organizational silos and resistance, and how teams can clarify priorities, trade-offs, ownership, and decisions.
Functional silos develop for many reasons, including organizational structure, specialized responsibilities, incentives, governance, resource constraints, and reporting lines.
Every silo is not evidence of poor behavior. Functions need boundaries, specialist knowledge, decision rights, and accountability. Problems arise when those boundaries prevent relevant information, decisions, resources, or concerns from moving across the organization.
Weak influence skills can reinforce these barriers. Professionals may advocate only for local priorities, involve stakeholders too late, avoid necessary disagreement, communicate without a clear request, or use authority they do not hold. These patterns can make cross-functional coordination more difficult.
What Are Organizational Silos?
Organizational silos are boundaries that limit the useful exchange of information, expertise, decisions, resources, or coordinated action between teams, functions, business units, locations, or professional groups.
Some boundaries are necessary. Legal, finance, technology, operations, HR, risk, and commercial functions have distinct responsibilities that should not be blurred indiscriminately.
A boundary becomes problematic when it contributes to conditions such as:
- Important information remaining within one function
- Teams optimizing local targets while transferring costs or risks elsewhere
- Cross-functional dependencies having no clear owner
- Decisions being made without relevant operational or specialist input
- Stakeholders being involved only after an approach is effectively final
- Different functions using incompatible assumptions or success criteria
- Conflicts remaining unresolved because decision authority is unclear
- Commitments being discussed but not documented or completed
Influence skills cannot remove every structural barrier. Some problems require changes to governance, incentives, resources, systems, processes, roles, or decision rights. Influence can help professionals identify and address the interpersonal and cross-functional behaviors that contribute to the problem.
Why Silos Persist in Modern Organizations
Functions are responsible for different outcomes, risks, resources, and measures of success.
Finance may protect investment discipline and financial exposure. Operations may prioritize service continuity, feasibility, and capacity. Technology may focus on architecture, integration, security, and support. HR may consider workforce impact, capability, and organizational responsibilities. Commercial teams may focus on customers, revenue, commitments, and timing.
These differences are legitimate. Cross-functional tension may reflect real trade-offs rather than a failure of collaboration.
Silos become stronger when teams:
- Treat their own function’s priorities as the only relevant criteria
- Assume other functions understand information that has not been shared
- Interpret challenge as obstruction or lack of commitment
- Protect relationships by avoiding unresolved issues
- Request support without explaining the effect on another team
- Use different data, definitions, or assumptions
- Fail to identify who can make a cross-functional decision
- Leave dependencies and commitments without clear ownership
The organizational structure may create the boundary, but everyday communication and influence behaviors affect whether the boundary becomes an obstacle.
How Weak Influence Skills Reinforce Silos
Advocating Only for a Local Priority
Professionals may present their function’s objective as though other teams should automatically support it.
A technology team may emphasize technical risk without addressing operational timing. Operations may prioritize continuity without considering long-term system constraints. Finance may focus on cost without examining implementation consequences.
A stronger influence approach makes the enterprise issue visible, acknowledges the effect on each function, and presents the trade-offs requiring a decision.
Relying Only on Evidence or Technical Detail
Evidence and expertise are important, but they may not address every stakeholder concern.
A proposal can be technically sound while creating workload, service disruption, legal exposure, financial pressure, or implementation risk elsewhere. Additional data will not resolve a concern that is fundamentally about capacity, authority, timing, or operational consequences.
Evidence becomes more useful when it is connected with the stakeholder’s responsibilities and combined with questions that reveal concerns, constraints, and missing information.
Engaging Stakeholders Too Late
Teams sometimes request input after the recommendation, implementation approach, timing, and major trade-offs have already been decided.
This can create the appearance of participation without giving stakeholders a meaningful opportunity to contribute expertise or identify implementation requirements.
Late engagement may be appropriate when a decision has legitimately been made and the purpose is to communicate it. In that case, leaders should not imply that the decision remains open. Leaders can still invite input on implementation issues that have not been resolved.
Using Authority That Does Not Exist
Cross-functional professionals may communicate requests as though the recipient reports to them or has already accepted the priority.
This can obscure the actual decision route and the stakeholder’s competing responsibilities.
When formal authority is limited, professionals should identify who can decide, explain why the contribution is required, and make a clear request without implying a mandate they do not hold.
Avoiding Necessary Disagreement
Some professionals avoid discussing missed commitments, unclear ownership, competing priorities, or conflicting assumptions because they want to protect the relationship.
The immediate conversation may remain comfortable, but the issue can return later as delay, duplicated work, escalation, or frustration.
Constructive influence allows professionals to discuss difficult issues directly while maintaining respect and the conditions required for future cooperation.
Using the Same Approach With Every Stakeholder
A senior sponsor, technical specialist, operational manager, affected employee, and external partner do not need the same information or type of participation.
The underlying facts should remain consistent, but the level of detail, evidence, questions, requested contribution, and form of engagement should reflect the stakeholder’s role.
Seeking Agreement Without Commitment
A meeting may end with positive comments while no decision, resource, owner, or action has been confirmed.
This creates the appearance of alignment without the behavior required for implementation.
Before closing an important conversation, confirm:
- The decision made
- The contribution agreed
- Actions and owners
- Resources or capacity committed
- Dependencies and deadlines
- Unresolved issues
- Escalation requirements
- Review points
How Weak Influence Can Increase Resistance
Resistance is sometimes described as a negative personal attitude. In practice, resistance may reflect uncertainty, previous experience, limited capacity, competing priorities, inadequate information, weak trust, or a legitimate concern about the recommendation.
Weak influence can intensify resistance in two opposite ways.
Too Much Direction
Stakeholders receive a solution, deadline, or request without enough context, relevant evidence, or opportunity to raise concerns.
This can be particularly problematic when stakeholders possess expertise required for implementation or will experience significant consequences from the decision.
Too Little Direction
The conversation remains open and participative, but no one states the recommendation, expectation, decision boundary, or action required.
Stakeholders may leave without understanding what has been decided, who owns the work, or how competing priorities will be resolved.
Effective influence does not eliminate disagreement or resistance. It helps professionals understand what is driving the response and select an appropriate combination of direction, inquiry, listening, acknowledgment, and involvement.
Why Communication Alone Is Not Enough
Clear communication is necessary, but collaboration requires more than the transmission of information.
A well-written message may still fail to create coordinated action if:
- The stakeholder does not understand why the request is relevant
- The proposal overlooks material concerns
- The stakeholder lacks the required capacity or authority
- The decision process is unclear
- The requested contribution remains implicit
- Another priority has not been resolved
- No one owns the dependency
- Commitments are not reviewed
Influence adds stakeholder judgment and behavioral flexibility to communication. Professionals need to understand the situation, select appropriate behaviors, communicate a clear position, explore relevant perspectives, and confirm follow-through.
For a broader cross-functional process, read Communication and Collaboration Across Teams.
A Practical Process for Working Across Silos
1. Define the Shared Organizational Outcome
Before advocating for a functional solution, clarify the result that requires several teams to contribute.
A useful outcome should be specific enough to guide evaluation and decisions.
“Improve collaboration” is too broad. A more useful outcome might be:
- Reduce customer handoff delays while maintaining compliance and service quality
- Implement the new system without interrupting critical operations
- Resolve a resource dependency before the next project milestone
- Standardize a process while permitting defined local adaptations
A shared outcome does not eliminate functional responsibilities. It provides a common reference point for discussing the options and trade-offs.
2. Identify Stakeholders and Dependencies
Determine who can decide, advise, contribute resources, provide expertise, affect implementation, or experience the consequences of the work.
Identify dependencies such as:
- A required decision or approval
- Specialist expertise
- Operational capacity
- Technology integration
- Funding or procurement
- Legal, risk, or compliance review
- Local implementation support
- Communication or sponsorship
Use APRENDA’s Stakeholder Management Framework to connect identification, analysis, prioritization, engagement, communication, relationship ownership, and review.
3. Understand Functional Priorities and Constraints
Explore what each stakeholder is accountable for delivering or protecting.
Consider:
- Performance measures and obligations
- Current commitments
- Available resources and capacity
- Operational risks
- Customer or user impact
- Implementation requirements
- Decision authority
- Previous experiences
- Evidence required for confidence
Do not assume that resistance to the proposed approach means opposition to the overall objective.
4. Communicate the Recommendation With Relevance
Explain the proposal in terms that each stakeholder can evaluate.
A relevant recommendation should make clear:
- The issue or opportunity
- The proposed action
- The available evidence
- The organizational relevance
- The effect on each function
- The risks and trade-offs
- The alternatives considered
- The decision or contribution required
The facts should remain consistent across audiences. Relevance should not become selective disclosure or a different version of the proposal for every team.
5. Balance Direction With Participation
Some situations require a clear recommendation, expectation, boundary, or decision. Others require questions, listening, acknowledgment, consultation, or involvement before a viable approach can be defined.
The Positive Power & Influence® model provides a practical framework for balancing complementary Push and Pull behaviors:
- Push behaviors provide direction through expectations, recommendations, positions, evidence, and reasoning.
- Pull behaviors create understanding and participation through inquiry, listening, acknowledgment, and appropriate involvement.
The appropriate balance depends on the issue, available expertise, relationship, authority, urgency, and organizational context.
6. Make Trade-Offs Explicit
Cross-functional decisions often involve real trade-offs among speed, cost, risk, capacity, service, customer impact, compliance, and long-term value.
A useful decision discussion should identify:
- The available options
- What each option achieves
- What each option gives up
- The evidence available
- The assumptions involved
- The consequences of delay or inaction
- Who holds final decision authority
Influence cannot remove every trade-off. It can help stakeholders evaluate the trade-off using relevant information and shared decision criteria.
7. Clarify Decision Rights
Make clear who:
- Recommends
- Provides specialist input
- Controls resources
- Approves
- Makes the final decision
- Implements
- Monitors progress
- Escalates unresolved issues
Participation should not obscure authority. If a leader is responsible for the final decision, that responsibility should remain visible.
8. Confirm Ownership and Follow-Through
After the decision, document:
- Actions and owners
- Resources committed
- Dependencies
- Deadlines
- Support requirements
- Unresolved concerns
- Escalation routes
- Review points
Alignment becomes observable through coordinated behavior, not meeting attendance or verbal agreement.
9. Revisit the Agreement During Implementation
Cross-functional coordination can weaken after the initial decision. Priorities change, barriers emerge, and assumptions may prove inaccurate.
Continue to:
- Monitor commitments
- Communicate material changes
- Close feedback loops
- Address new constraints
- Escalate unresolved issues appropriately
- Adjust responsibilities or sequencing when necessary
Influence does not finish when the meeting ends.
A Cross-Functional Example
An organization is preparing to introduce a shared customer platform across sales, service, and technology.
Sales wants an early launch to support commercial commitments. Service is concerned about workload, training, and customer disruption. Technology needs additional time to resolve an integration dependency.
The initial discussions reinforce the functional boundaries. Each team presents its own priority and treats the other concerns as obstacles.
The program leader reframes the discussion around a shared outcome: improve customer visibility without creating unacceptable service or technical risk.
The stakeholders compare three implementation options using the same criteria:
- Customer impact
- Operational capacity
- Integration risk
- Cost
- Time to value
- Support requirements
The decision is a phased implementation. Sales accepts a narrower first release. Service protects capacity for testing and preparation. Technology commits to a defined integration review.
The outcome is not universal preference for the same option. It is a documented decision with visible trade-offs, responsibilities, dependencies, and review points.
What Influence Skills Cannot Fix Alone
Influence development should not be presented as the complete solution to organizational silos.
Cross-functional problems may also require:
- Changes to incentives or performance measures
- Clearer governance and decision rights
- Additional resources or capacity
- Redesigned processes
- Improved systems or data access
- Changes in organizational structure
- Executive prioritization
- Resolution of conflicting mandates
- Formal escalation or risk management
If teams are rewarded for contradictory outcomes or no person has authority to resolve a priority conflict, communication training alone will not correct the underlying system.
Influence skills are most useful when they help people identify these conditions, discuss them constructively, and prepare the issue for a responsible decision.
How to Evaluate Influence Across Organizational Boundaries
Do not evaluate influence development only through participant satisfaction or broad organizational results.
Use indicators connected with the specific cross-functional situations and behaviors the organization is addressing.
Possible measures include:
- Clarity of shared outcomes
- Quality of stakeholder and dependency analysis
- Visibility of trade-offs
- Clarity of decision rights
- Completion of agreed cross-functional actions
- Resolution of defined dependencies
- Closure of questions and feedback loops
- Use of targeted influence behaviors in observed practice
- Manager or stakeholder feedback on specific behaviors
- Appropriate escalation of unresolved issues
Measures require interpretation. Faster decisions are not always better decisions. Fewer escalations may indicate improved coordination, but they may also mean important issues are not being raised.
Distinguish participant reaction, self-reported application, observed behavior, operational indicators, and verified organizational effects.
Develop Influence as an Organizational Capability
Working across organizational boundaries requires more than reminding people to collaborate.
Professionals need opportunities to practice how they:
- Clarify the shared outcome
- Analyze stakeholder priorities and dependencies
- Communicate a relevant recommendation
- Ask purposeful questions
- Listen for concerns and constraints
- Balance direction with participation
- Respond to disagreement without becoming defensive
- Make trade-offs visible
- Clarify authority and decision rights
- Confirm commitment and follow-through
Effective development uses realistic workplace situations, focused behavioral feedback, workplace application, and continued reinforcement.
Organizations seeking structured, behavior-based development can explore APRENDA’s Influence Skills Training, which connects practical influence behaviors with current cross-functional challenges, stakeholder relationships, and organizational priorities.
Frequently Asked Questions
Do Poor Influence Skills Cause Organizational Silos?
Poor influence skills can reinforce silos when teams advocate only for local priorities, engage stakeholders too late, avoid necessary disagreement, or fail to clarify decisions and ownership. Silos can also result from structure, incentives, governance, systems, resources, and reporting lines.
Is Resistance Always a Negative Response?
No. Resistance may reveal legitimate concerns about risk, workload, capacity, timing, evidence, fairness, authority, or implementation. Professionals should understand the reason for the response before deciding how to address it.
Why Is Communication Alone Not Enough?
Communication can share information clearly, but cross-functional work also requires stakeholder understanding, appropriate participation, clear decision rights, specific requests, ownership, and follow-through.
Can Influence Training Eliminate Silos?
No. Influence training can help people work more effectively across boundaries, but structural problems may also require changes to incentives, governance, resources, processes, systems, roles, or authority.
How Can Teams Improve Cross-Functional Influence?
Teams can clarify the shared outcome, understand functional priorities, make dependencies and trade-offs visible, balance direction with participation, define decision rights, and confirm ownership and follow-through.
Conclusion: Work Constructively Across Functional Boundaries
Organizational silos do not disappear simply because teams communicate more often or are told to collaborate.
Influence skills can help professionals work more constructively across different priorities, responsibilities, and decision-making roles. These skills support clearer recommendations, purposeful listening, visible trade-offs, appropriate participation, and explicit follow-through.
Influence is not a substitute for sound structures, governance, incentives, systems, or resources. It is one practical capability that helps people identify and address barriers before those barriers become entrenched in cross-functional work.






