Build For Change: Revolutionizing Customer Engagement Through Continuous Digital Innovation: Summary & Key Insights

A customer rarely compares your company only with your direct competitors; they compare you with the best digital experience they had anywhere. That is one of the central realities behind Build for Change. Over the last two decades, digital technology has transformed convenience from a luxury into a baseline expectation. People now assume that services should be fast, personalized, transparent, and available across channels. If they can track a food delivery in real time, they expect similar visibility from a bank loan, an insurance claim, or a healthcare request.

Trefler explains that this shift is not simply about having a mobile app or a website. It is about recognizing that customer expectations have been permanently elevated by digital leaders that trained people to expect immediate responses and frictionless service. Traditional organizations often struggle because their internal systems were built for departmental efficiency, not for seamless customer journeys. As a result, customers encounter fragmented experiences: repeating information, waiting for approvals, and moving between disconnected teams.

A practical example is retail banking. A customer may begin opening an account online, call support with a question, and visit a branch to finish the process. If those channels are not connected, the experience feels broken. By contrast, a digitally adaptive bank can preserve context across every interaction and complete the process faster.

The lesson is clear: customer expectations are now shaped externally, but your response must be built internally. Actionable takeaway: map your top customer journeys and identify every point where delays, handoffs, or duplicated effort fall short of modern digital expectations.

The future rarely rewards what is merely efficient today; it rewards what can be changed tomorrow. Trefler’s “build for change” philosophy is the book’s defining principle. Instead of creating systems and processes optimized for a fixed set of assumptions, organizations should design them to adapt as markets, regulations, technologies, and customer needs shift. In practice, this means favoring modularity, flexibility, and rapid iteration over rigid, one-time builds.

Many companies still approach transformation like a construction project: define requirements, implement a large solution, and hope it lasts for years. Trefler argues that this mindset is outdated. Business conditions move too quickly. A regulation changes, customer behavior shifts, a new channel emerges, or a competitor introduces a new service model. Systems built for permanence become liabilities because every update is expensive, slow, and risky.

An insurance company illustrates this well. If it hardcodes policy rules, claims workflows, and customer communications into separate legacy systems, even a minor product update becomes difficult. But if it separates business rules from core infrastructure and uses adaptable workflow layers, it can launch policy changes faster and with less disruption.

This philosophy extends beyond software. Teams, governance, and strategy also need to be designed for learning and adjustment. Change should not be treated as an exception to business as usual; it should be embedded in business as usual.

Actionable takeaway: review one major process or platform in your organization and ask a simple question—how easily can it change when customer or market conditions change? If the answer is “not easily,” redesign for adaptability.

Scale without agility creates impressive-looking inertia. Trefler argues that the organizations best positioned for the digital era are not necessarily the largest or most technologically advanced, but the most adaptive. An adaptive enterprise is structured to sense change early, respond quickly, and learn continuously. It is built to coordinate data, workflows, decisions, and people around outcomes rather than around rigid silos.

In many large companies, structure becomes the enemy of responsiveness. Departments optimize their own goals, systems are fragmented, and decision-making is layered with approvals. This creates a slow-motion enterprise in a real-time market. Trefler’s answer is not organizational chaos, but a more intelligent architecture where processes can be updated rapidly, decisions can be automated where appropriate, and teams can align around customer value.

Consider a telecommunications provider handling service upgrades, billing issues, and support requests. In a conventional structure, each function may operate separately, requiring the customer to navigate multiple handoffs. In an adaptive enterprise, those interactions are orchestrated through integrated workflows and shared context, allowing the organization to resolve issues faster and more consistently.

Trefler emphasizes that adaptability depends on both technology and management design. It requires visibility into operations, flexible process management, and leadership that encourages responsiveness over bureaucracy. Agility is not only about speed; it is about reducing the friction between insight and action.

Actionable takeaway: identify where your organization’s current structure slows customer outcomes—whether in approvals, handoffs, or disconnected systems—and redesign those choke points as coordinated end-to-end workflows.

Most organizations claim to be customer-centric, but many still operate around internal convenience. Trefler makes a crucial distinction: true customer-centricity is not a slogan or a branding exercise; it is an operational discipline. It requires designing processes, systems, and decisions around what creates value for the customer, not around how departments prefer to work.

This is where process automation becomes powerful. Automation is often misunderstood as a cost-cutting tool alone, but Trefler presents it as a way to improve customer experience by reducing friction, errors, and delays. When thoughtfully implemented, automation can streamline onboarding, accelerate service resolution, personalize communications, and ensure consistency across channels. The goal is not to remove humans from every interaction, but to let technology handle repetitive coordination so employees can focus on higher-value moments.

For example, a healthcare payer processing prior authorizations might traditionally rely on manual review, multiple handoffs, and inconsistent updates to patients and providers. With intelligent workflow automation, routine cases can be processed quickly, exceptions can be escalated appropriately, and all parties can receive timely status updates. The result is not only lower administrative burden, but also a better experience during a stressful process.

Trefler warns, however, that automating a broken process only scales the problem. Customer-centric automation starts with understanding the end-to-end journey, the moments of uncertainty, and the causes of delay.

Actionable takeaway: before automating a process, step into the customer’s perspective and ask where confusion, waiting, and repetition occur. Then automate those pain points first rather than merely digitizing existing inefficiencies.

Digital transformation fails less from lack of ambition than from lack of alignment. One of Trefler’s most practical insights is that business and IT must stop operating as separate worlds. In many enterprises, business leaders define goals in broad terms while IT teams manage technical complexity in isolation. The result is a damaging gap between strategic intent and execution reality.

Trefler argues that organizations need shared language, shared priorities, and shared accountability. Business leaders should understand enough about systems and process design to set realistic transformation goals. IT leaders, meanwhile, must understand customer outcomes and business context, not just technical specifications. When these groups collaborate effectively, transformation becomes faster, more focused, and more sustainable.

A common example is a customer service modernization initiative. Business may want a “360-degree customer view” and faster response times, while IT sees fragmented databases, outdated interfaces, and compliance constraints. Without collaboration, each side becomes frustrated. With cross-functional governance and iterative delivery, however, the organization can prioritize the most valuable improvements first, integrate systems incrementally, and deliver measurable progress.

Trefler also links this bridge to cultural change. Silos are often reinforced by incentives, jargon, and habits. Leaders must create environments where cross-functional problem-solving is expected and rewarded. Technology architecture alone cannot solve a relationship problem.

Actionable takeaway: create a joint business-IT review for every major transformation effort, focused on customer outcomes, operational constraints, and near-term deliverables so that both sides co-own success.

The hardest part of transformation is not installing new technology; it is changing how people think, decide, and work. Trefler repeatedly emphasizes that lasting digital innovation depends on culture. Organizations can purchase platforms and automate workflows, but if their mindset remains risk-averse, siloed, and overly hierarchical, progress will stall.

A culture that supports continuous innovation values experimentation, transparency, and learning. It allows teams to test improvements, respond to data, and adjust without treating every deviation from plan as failure. This matters because building for change requires ongoing iteration. If employees are punished for surfacing problems or proposing alternatives, the organization becomes less adaptive no matter how modern its systems appear.

A large financial institution offers a useful example. It may invest heavily in digital channels, but if frontline staff are not empowered to resolve issues, product teams cannot act without lengthy approvals, and operations teams resist process changes, customer experience will still suffer. By contrast, a company that encourages cross-functional collaboration, rapid feedback, and process ownership can improve steadily over time.

Trefler does not suggest recklessness. Governance still matters, especially in regulated industries. But governance should enable responsible change rather than freeze the organization in place. Leaders must model curiosity, speed, and accountability if they want those qualities to spread.

Actionable takeaway: assess whether your culture rewards adaptability in practice. Look at incentives, decision rights, and response to failure, then remove one policy or habit that discourages experimentation and cross-functional improvement.

Many organizations treat innovation as a special event: a workshop, a lab, or a high-profile project. Trefler argues that this approach is too narrow. In a volatile digital environment, innovation must become an everyday organizational capability. It should be embedded in operating models, technology architecture, and management routines so the enterprise can continuously refine how it serves customers and executes work.

This means innovation is not only about breakthrough products. It also includes improving workflows, redesigning decisions, simplifying experiences, and using data more intelligently. Small, consistent enhancements often create more value than occasional big bets, especially when they compound over time. Trefler’s broader point is that organizations should be engineered to absorb feedback and turn it into action repeatedly.

A subscription business can illustrate this well. Instead of redesigning the entire customer journey every few years, it can monitor points of drop-off, automate renewal reminders, test support interventions, and refine pricing communication continuously. Each change may seem modest, but together they create a more responsive and competitive organization.

To sustain this capability, leaders need metrics that focus on responsiveness, customer outcomes, and cycle times, not just project completion. Innovation should be measured by how effectively the organization adapts, not by how many initiatives it launches.

Actionable takeaway: build a regular operating rhythm for innovation—review customer friction points, process delays, and decision bottlenecks monthly, and commit to shipping small improvements continuously rather than waiting for major transformation programs.

What slows many companies is not lack of intent, but the accumulated weight of yesterday’s decisions. Trefler highlights legacy complexity as one of the biggest barriers to modern customer engagement. Over time, organizations add systems, exceptions, workarounds, policies, and interfaces until the enterprise becomes difficult to understand and nearly impossible to change quickly.

This complexity creates costs beyond IT maintenance. It confuses employees, delays service, increases error rates, and makes every new initiative harder. A customer may experience this as contradictory information across channels, slow approvals, or being transferred repeatedly because no one sees the full picture. Internally, teams spend more time navigating system limitations than solving customer problems.

Trefler’s response is not to rip everything out at once, which is often unrealistic. Instead, he favors approaches that simplify progressively: wrapping legacy systems with more flexible process layers, centralizing rules where possible, reducing duplication, and modernizing high-friction journeys first. The priority is to reduce dependence on brittle custom code and disconnected processes that prevent adaptation.

A government agency, for instance, may rely on decades-old systems for citizen services. Full replacement could take years, but improving workflow orchestration and digital access around those systems can still deliver better service while a longer modernization path unfolds.

Actionable takeaway: identify the forms of legacy complexity that most directly harm customer experience today, and target simplification there first rather than pursuing modernization only where it is technically easiest.

Organizations often celebrate transformation milestones that customers never notice. Trefler insists that success should be measured by outcomes that reflect real improvement in customer engagement and organizational adaptability. Launching a new platform, completing a migration, or deploying automation matters only if it leads to faster service, better personalization, lower effort, and greater responsiveness to change.

This requires moving beyond purely internal metrics such as budget compliance, project deadlines, or system uptime. Those measures are useful, but they are incomplete. A company can deliver a technology project on schedule and still produce a frustrating customer experience. Trefler encourages leaders to connect operational indicators with customer-facing results: time to resolution, first-contact completion, channel continuity, exception rates, policy change speed, and customer retention.

For example, an insurer implementing claims automation should not only track processing efficiency. It should also examine whether claimants receive clearer communications, whether adjusters can focus on complex cases, and whether the business can update rules quickly when external conditions change. These indicators reveal whether transformation is creating both current value and future flexibility.

The broader message is that adaptability itself is a measurable advantage. How quickly can your organization revise a process, introduce a product change, or respond to a customer issue across channels? That speed increasingly defines competitiveness.

Actionable takeaway: add at least three customer-centered and adaptability-focused metrics to every digital initiative, ensuring that success is judged by experience and responsiveness, not just implementation completion.