Putting Customers Before Politics and Building an Integrated Customer Operations Model

Introduction

The Chief Operating Officer faced a problem that initially appeared technological but was fundamentally organizational. Sales orders repeatedly contained incorrect customer information, unsuitable products, incomplete service details, and inaccurate item specifications. These mistakes frustrated customers, increased the amount of rework required from employees, delayed order fulfillment, and weakened confidence in the company.

The organization attempted to solve the problem by investing in technology. However, the new tools failed to produce the expected results because employees continued following inconsistent processes. Departments collected information differently, interpreted policies according to their own priorities, and transferred incomplete orders to other teams. Instead of designing one reliable process around the customer, the company attempted to automate several conflicting ways of working.

This situation illustrates why organizations must put customers before internal politics. The expression does not mean that legal requirements, financial controls, technical limitations, or departmental expertise should be ignored. Rather, it means that decisions should be evaluated according to their contribution to customer value and the organization’s long-term performance, instead of being controlled by departmental competition, personal influence, or the desire to protect existing practices.

Customer centricity requires more than a friendly attitude toward buyers. Shah et al. (2006) argue that becoming customer-centered requires leadership commitment, organizational realignment, supportive processes and systems, and performance measures that reward customer value. Technology is important within this model, but it should support a clearly designed operating process rather than determine how the organization treats its customers.

This essay argues that the company should replace its technology-first response with an integrated customer operations model. Such a model requires an end-to-end view of the sales process, cross-functional stakeholder involvement, evidence-based customer personas, realistic service scenarios, explicit process ownership, value-based prioritization, aligned technology, and a structured approach to organizational change.

The Customer Problem Behind the Sales Errors

The reported mistakes should not be viewed as isolated employee failures. When the same types of errors appear repeatedly, they usually indicate weaknesses in the system through which work is performed.

A salesperson may enter incorrect customer information because mandatory data fields are unclear. An operations employee may provide the wrong service because product definitions differ across systems. A finance team may reject an order because pricing rules were not communicated to sales. The legal department may request changes after the customer has already approved the transaction. In each case, an employee may appear responsible for the immediate error, but the wider problem involves fragmented procedures, ownership, and information.

The company’s difficulty can be understood as an end-to-end process failure. A customer does not experience the organization as separate departments. The customer experiences one relationship that may include advertising, an initial inquiry, a sales conversation, contract approval, payment, delivery, customer support, and renewal. Lemon and Verhoef (2016) explain that customers interact with organizations through numerous touchpoints and that delivering a positive experience requires coordination among several business functions and external partners.

As the authors observe, “understanding customer experience and the customer journey over time is critical for firms” (Lemon & Verhoef, 2016, p. 69). The quotation is especially relevant because the company’s errors cannot be corrected by concentrating only on the moment when a salesperson enters an order. Management must examine the complete journey through which customer expectations are created, translated into internal requirements, fulfilled, and evaluated.

Why the Technology-First Solution Failed

Technology can automate data entry, validate required fields, improve reporting, and reduce repetitive work. Nevertheless, automation does not automatically create a good process. When an organization digitizes a poorly defined process, it may simply produce mistakes more quickly and on a larger scale.

The company’s technology initiative failed because the business had not agreed on a standard way of working. Different departments maintained their own definitions, approval rules, customer records, and performance priorities. The system was therefore expected to reconcile disagreements that management had not resolved.

For example, sales may have prioritized rapid order submission because employees were rewarded for closing transactions. Finance may have prioritized payment security and margin. Operations may have focused on delivery capacity, while legal personnel concentrated on contractual risk. Each priority was reasonable within its own department, but the organization had not established a shared mechanism for balancing them.

Information technology and business processes must be aligned dynamically. Research on IT–business alignment emphasizes that technology creates value when technological decisions are connected with organizational strategy, process requirements, leadership, and changing business conditions.

The correct sequence is therefore:

1. Understand what customers require.
2. Map the existing end-to-end process.
3. identify recurring failure points.
4. Define the desired process and decision rules.
5. Assign clear accountability.
6. Configure technology to support the redesigned process.
7. Train employees and monitor adoption.

Beginning with software selection reverses this sequence. It encourages departments to debate technical features before they have agreed on the problem they are attempting to solve.

Putting Customers Before Internal Politics

Organizational politics arises when individuals or departments use influence, information, relationships, or authority to protect preferred outcomes. Politics is not always dishonest. Departments may genuinely disagree because they have different professional obligations. Legal personnel must consider regulatory exposure, finance must protect profitability, and operations must avoid promising services that cannot be delivered.

The problem occurs when departmental interests become more important than the organization’s shared purpose. A manager may oppose a process change because it reduces departmental control. Another may hide performance problems to protect a budget. Teams may blame one another rather than investigate how the complete process is failing.

Putting customers before politics creates an external reference point for resolving these disagreements. Instead of asking which department should win, leaders ask which option delivers the greatest sustainable value while satisfying legal, ethical, financial, and operational requirements.

Customer centricity does not mean agreeing to every customer request. Some requests may be unsafe, unlawful, unprofitable, or inconsistent with the company’s strategy. A customer-centered organization understands customer needs, makes deliberate promises, communicates limitations honestly, and fulfills approved commitments reliably.

Shah et al. (2006) identify several barriers to customer centricity, including organizational culture, functional structures, processes, financial measures, and information systems. They conclude that the path toward customer centricity requires coordinated changes rather than an isolated marketing initiative.

The company should therefore define a shared purpose such as:

To deliver accurate, appropriate, and timely customer solutions through one accountable end-to-end process.

This purpose should guide decisions concerning procedures, systems, staffing, performance measures, and departmental responsibilities.

Developing an End-to-End Customer Operations Process

The company should map the full sales order process from the customer’s first contact through delivery, invoicing, support, and renewal. This process may be called lead-to-order, order-to-cash, or customer-to-fulfillment, depending on the organization’s terminology.

A traditional functional structure divides work according to departments. Sales completes its task and passes the order to operations. Operations passes information to finance, legal, logistics, and support. Every transfer creates the possibility that data will be lost, misunderstood, duplicated, or delayed.

End-to-end process management treats the entire sequence as one connected system. Hammer (2007) argues that strong organizational processes require appropriate design, capable performers, clear ownership, supporting infrastructure, and reliable performance measures.

The organization should appoint a senior process owner with authority to oversee the complete sales order journey. This person should not replace functional managers. Instead, the process owner should ensure that all departments contribute to the shared outcome.

Responsibilities would include:

• defining process standards;
• resolving cross-departmental disagreements;
• approving changes to customer data requirements;
• monitoring errors and delays;
• coordinating training;
• reviewing technology requests;
• evaluating customer feedback; and
• reporting performance to senior leadership.

Without process ownership, every department may improve its individual activities while the overall customer experience remains poor. Sales may reduce call time, finance may reduce approval risk, and operations may increase capacity utilization, but customers may still receive inaccurate or delayed orders.

Involving the Right Stakeholders

A customer operations redesign requires representation from every function that creates, approves, delivers, controls, or supports the customer promise. Relevant stakeholders may include:

• customers and customer representatives;
• sales;
• customer service;
• marketing;
• operations;
• logistics;
• finance;
• legal and compliance;
• internal audit;
• information technology;
• data management;
• human resources; and
• senior leadership.

Customer participation is essential because internal employees may misunderstand which failures matter most to buyers. Sales representatives may believe that speed is the highest priority, while customers may prefer a slower process that guarantees accuracy and clear communication.

Internal participation is equally important. Markus and Mao (2004) explain that participation in information-system development and implementation is more complex than merely asking users for opinions. Participation should be connected to influence, implementation activities, and the outcomes different stakeholders value.

Stakeholder involvement should begin before the preferred solution has been selected. Asking employees for feedback after management has finalized the system creates the appearance of participation without providing meaningful influence.

However, involvement does not mean that every stakeholder receives equal authority over every decision. A governance model should clarify who recommends, approves, performs, and reviews each change. For example, legal personnel should approve mandatory contractual requirements, but they should not control the design of every customer interaction. IT should advise on feasibility and security, but it should not independently define business policy.

A cross-functional customer operations council can provide ongoing governance. It should meet regularly to review process performance, customer complaints, unresolved risks, and proposed improvements. Its decisions should be documented so that employees understand why one requirement was prioritized over another.

Using Customer Personas Responsibly

A customer persona is a structured representation of a significant customer type. It may include the customer’s objectives, responsibilities, behaviors, concerns, decision criteria, service expectations, and common difficulties.

For example, the company might develop separate personas for:

• a small-business owner requiring a simple and rapid purchase;
• a corporate procurement manager requiring formal approvals;
• an existing customer requesting a service change;
• a customer with limited technical knowledge;
• an internal account manager responsible for order accuracy.

Personas can help employees move beyond abstract statements such as “the customer wants convenience.” They encourage teams to consider how different customers interpret the same process.

Research suggests that personas and customer journey maps can help organizations identify system requirements and represent patterns in users’ experiences. However, they should be grounded in evidence rather than created entirely from assumptions.

A poorly designed persona may reinforce stereotypes. For example, assuming that all older customers dislike digital services or all small businesses prioritize low prices can lead to inaccurate decisions. Personas should therefore be based on interviews, customer-service records, behavioral data, complaint analysis, surveys, and direct observation.

They should also be revised when customer behavior changes. A persona is a decision tool, not a permanent description of every person within a customer category.

Using Scenarios and Customer Journeys

A scenario describes how a persona attempts to achieve a particular goal. It places the customer within a realistic situation and illustrates the actions, decisions, information, systems, and emotions involved.

One scenario might involve an existing customer ordering an additional service. The journey could include:

1. discovering the service online;
2. requesting information;
3. speaking with a sales representative;
4. confirming technical compatibility;
5. receiving a quotation;
6. approving contractual terms;
7. entering payment information;
8. waiting for delivery;
9. receiving installation support; and
10. resolving an initial service problem.

The organization should identify what the customer expects at each stage, which department is responsible, what information is required, where delays occur, and how failures are corrected.

Journey maps combine visual representation and storytelling to help teams understand customer needs across multiple interactions. They are especially useful when no single employee can see the complete experience.

For example, a salesperson may believe that an order was successful because the customer signed the contract. Operations may later discover that the requested configuration is unavailable. Finance may issue an incorrect invoice, and customer service may receive the complaint. Each department sees one piece of the problem, while the journey map reveals how the failures are connected.

The process should also include internal customers. Sales depends on pricing, legal, product, and operations teams for accurate information. Operations depends on sales for complete customer requirements. Treating these internal relationships seriously improves the final experience delivered to the external customer.

Prioritizing Requirements According to Value

Customer operations programs often produce long lists of requirements. Some changes are inexpensive and highly valuable, while others require extensive investment but produce little improvement. Without a prioritization method, decisions may be controlled by the most influential department or the loudest participant.

Each proposed requirement should be evaluated according to common criteria:

• customer impact;
• error reduction;
• revenue or retention impact;
• legal and regulatory necessity;
• operational feasibility;
• implementation cost;
• time required;
• data and security risk;
• employee effort; and
• strategic alignment.

A simple value-prioritization matrix can support transparent decision-making:

The matrix prevents the company from attempting to satisfy every request. It also provides evidence for decisions that might otherwise become political.

Prioritization should remain dynamic. A requirement initially judged unimportant may become urgent because of a regulatory change, customer complaint trend, competitive development, or operational failure.

Aligning Performance Measures With Customer Value

Employees behave according to the outcomes that leaders measure and reward. A company cannot realistically promote customer accuracy while rewarding sales representatives only for the number or value of orders submitted.

If speed is measured but accuracy is not, employees may rush. If individual departmental cost is emphasized while total process cost is ignored, managers may transfer work and expense to other teams. If IT success is measured by delivering a system on schedule rather than improving business outcomes, the organization may celebrate implementation while customers continue experiencing the same problems.

Performance measures should include a balanced set of customer, operational, financial, risk, and employee indicators.

The most important measure may be first-time-right performance: the proportion of orders completed without correction, re-entry, credit adjustment, customer callback, or operational exception.

Metrics should also be shared across departments. A common scorecard encourages teams to solve problems together instead of optimizing separate targets.

Managing the Organizational Change

Redesigning the process will affect responsibilities, habits, authority, and possibly compensation. Employees may resist not because they oppose customers, but because they fear losing expertise, status, control, or job security.

A credible change program must therefore address both process design and human adoption. Errida and Lotfi (2021) reviewed numerous change-management models and identified recurring success factors, including a clear vision, leadership, stakeholder engagement, communication, readiness, resistance management, measurement, and reinforcement.

The COO should begin by creating a shared understanding of the problem. Employees should see evidence of customer complaints, rework, delays, lost revenue, and repeated errors. The purpose should not be to shame departments but to establish why the current system cannot continue.

A cross-functional leadership coalition should then guide the transformation. Kotter’s change framework emphasizes urgency, a guiding coalition, a clear vision, broad participation, early achievements, and the incorporation of new practices into organizational culture (Kotter, 1996). Contemporary applications likewise stress that complex change requires collaboration and stakeholder commitment.

Early wins might include eliminating a duplicate form, establishing one definition of an active customer, or correcting a frequent pricing error. These improvements demonstrate that the program is producing practical value.

Communication should continue throughout the change. Employees need to know what is changing, why it is changing, how their work will be affected, what support is available, and how success will be measured.

Technology as an Enabler

Once the organization has defined its desired process, technology can provide significant support. Appropriate capabilities may include:

• one reliable customer record;
• standardized product and service information;
• automated validation of required fields;
• workflow-based approvals;
• pricing and discount controls;
• contract templates;
• integration among sales, finance, operations, and support systems;
• real-time order status;
• exception alerts;
• audit trails; and
• performance dashboards.

Technology should reduce unnecessary effort without removing appropriate human judgment. A system can prevent submission when a required field is missing, but a trained employee may still need to determine whether a proposed service genuinely fits the customer’s circumstances.

The organization should test new tools with actual users before full implementation. Pilot testing can reveal confusing fields, unrealistic workflow assumptions, and unintended workload increases. Employees who will perform the process should participate in testing, training, and post-implementation review.

The company should also avoid assuming that every failure requires a new application. Some problems can be corrected by simplifying a policy, clarifying decision rights, removing duplicate approval, or improving employee knowledge. Technology investment should be justified by the value it adds to the redesigned process.

A Practical Transformation Roadmap

The COO can organize the transformation into the following stages:

The roadmap should not be treated as completely linear. Testing may reveal the need to revise personas, requirements, or process steps. Continuous learning is part of the transformation.

Expected Organizational Benefits

An integrated customer operations model should reduce incorrect orders, duplicated work, approval delays, billing disputes, service failures, and customer complaints. Employees should spend less time correcting avoidable mistakes and more time delivering useful services.

The organization may also experience improved customer retention and trust. Customer experience management research emphasizes that customer value is created through coordinated cultural mindsets, strategic direction, and organizational capabilities, not through a single campaign or department (Homburg et al., 2017).

Clear process ownership can improve accountability because problems are no longer abandoned at departmental boundaries. Shared metrics can reduce blame by giving teams one view of performance.

Stakeholder participation can also increase commitment. Employees are more likely to support a new process when they understand its purpose, have influenced its design, and believe that management has considered its practical effects.

Nevertheless, improvement should not be assumed. The company must measure actual outcomes. A transformation that creates attractive journey maps and new software but does not improve accuracy, timeliness, customer effort, or employee adoption has not succeeded.

Risks and Limitations

Customer-centered transformation carries its own risks. Excessive standardization may make it difficult to respond to unusual but legitimate customer needs. Leaders should standardize routine work while providing controlled procedures for exceptions.

Customer personas may become stereotypes if they are based on assumptions rather than research. Journey maps may oversimplify complex relationships. Cross-functional committees may create additional meetings without clear decisions. Technology may introduce privacy, cybersecurity, or dependency risks.

There is also a danger that “putting customers first” could be used to pressure employees into accepting unreasonable workloads or inappropriate customer behavior. Sustainable customer value depends on trained, respected, and adequately supported employees. The organization should not promise experiences that its workforce cannot deliver safely and consistently.

Internal politics cannot be removed entirely because organizations naturally contain different interests. The aim is to manage those interests through transparent governance, shared evidence, and agreed decision criteria.

Conclusion

The company’s sales errors were not primarily caused by inadequate technology. They resulted from fragmented processes, inconsistent information, unclear ownership, conflicting incentives, and weak coordination among departments. The unsuccessful technology initiative treated the symptoms while leaving the operating system of the business unchanged.

Putting customers before politics requires the organization to view sales, delivery, billing, service, and support as one connected customer journey. Sales, operations, legal, finance, marketing, audit, and IT must contribute their expertise without allowing functional priorities to overwhelm the shared outcome.

Personas and scenarios can help the company understand who its customers are, what they are trying to achieve, and where the existing process creates difficulty. These tools should be based on evidence and connected to an end-to-end process map.

Requirements should be prioritized according to customer impact, risk, value, cost, and feasibility. This approach replaces political influence with transparent decision criteria. A process owner and cross-functional governance council should then maintain accountability across departmental boundaries.

Technology remains essential, but it must be introduced after the business has defined a consistent and valuable process. The correct role of technology is to standardize data, automate appropriate controls, connect functions, and provide visibility. It cannot independently resolve disagreements about policy, ownership, or customer value.

Finally, lasting transformation requires effective change management. Stakeholders should be involved early, employees should receive practical support, leaders should communicate honestly, and progress should be reinforced through shared performance measures.

A customer-centered culture is created when departments stop asking how to protect their individual procedures and begin asking how they can collectively fulfill the organization’s promises. By placing customer value ahead of internal competition, the COO can reduce errors, improve productivity, control costs, rebuild trust, and create a more resilient organization.

References

Bradley, C., Oliveira, L., Birrell, S., & Cain, R. (2021). A new perspective on personas and customer journey maps: Proposing systemic design perspectives. International Journal of Human-Computer Studies, 148, Article 102583. doi:10.1016/j.ijhcs.2021.102583

Errida, A., & Lotfi, B. (2021). The determinants of organizational change management success: Literature review and case study. International Journal of Engineering Business Management, 13, 1–15. doi:10.1177/18479790211016273

Hammer, M. (2007). The process audit. Harvard Business Review, 85(4), 111–123.

Homburg, C., Jozić, D., & Kuehnl, C. (2017). Customer experience management: Toward implementing an evolving marketing concept. Journal of the Academy of Marketing Science, 45(3), 377–401. doi:10.1007/s11747-015-0460-7

Kotter, J. P. (1996). Leading change. Harvard Business School Press.

Lemon, K. N., & Verhoef, P. C. (2016). Understanding customer experience throughout the customer journey. Journal of Marketing, 80(6), 69–96. doi:10.1509/jm.15.0420

Markus, M. L., & Mao, J.-Y. (2004). Participation in development and implementation: Updating an old, tired concept for today’s information systems contexts. Journal of the Association for Information Systems, 5(11), 514–544. doi:10.17705/1jais.00057

Shah, D., Rust, R. T., Parasuraman, A., Staelin, R., & Day, G. S. (2006). The path to customer centricity. Journal of Service Research, 9(2), 113–124. doi:10.1177/1094670506294666

Wang, Y., Shi, S., Nevo, S., Li, S., & Chen, Y. (2021). IT–business process alignment: Examining the mediating role of systems integration. Information, 12(6), Article 237.

Editorial Staff

Academic Master Education Team is a group of academic editors and subject specialists responsible for producing structured, research-backed essays across multiple disciplines. Each article is developed following Academic Master’s Editorial Policy and supported by credible academic references. The team ensures clarity, citation accuracy, and adherence to ethical academic writing standards

Content reviewed under Academic Master Editorial Policy.

This author does not have any more posts.