Customer-Driven Innovation: Or Why Iteration is the Validation
Is “Unfinished” the New Perfect?
A series of fascinating encounters during my sabbatical in China — ranging from whole-day meetings in international companies to deep-dive dinners with local general managers in Shanghai — has left me thinking deeply about what “customer orientation” and “error culture” actually mean. Coming from the structured, precision-driven world of a Swiss software services company, the hyper-speed Chinese market feels like stepping into an alternate business reality.
In this article, I share my observations on the extreme operational customer centricity of Chinese companies, contrast it with traditional Western product development mindsets, and outline what this means for mid-sized, quality-focused software firms like ours. I look forward to discussing these perspectives with you in the comments!
The Stereotypes — and Our Western Blind Spot
The classic stereotype of “Swiss Precision” suggests that true customer-centricity means talking to your customer, understanding needs, defining requirements collaboratively, and then shipping a thoroughly vetted, highly reliable, near-perfect product. In Western management training, we are taught to spend months validating concepts on paper and running rigorous post-mortems whenever issues occur, designed to eliminate recurrence entirely.
At our 60-person Swiss software services firm, we have long seen the limits of this approach and actively tried to evolve. We map detailed user journeys, implement modern agile frameworks and even run Design Thinking workshops. Yet in all honesty, these initiatives too often remain too theoretical, because they are conducted from corporate ivory towers. They produce strong internal alignment but rarely penetrate the operational reality of end customers. Our biggest Western blind spot is this: we optimize agility for internal process, not for real-world customer iteration. The actual end user is frequently locked out of the feedback loop entirely.
In China’s digital and tech sectors, this logic is completely flipped. As Walter Wang, General Manager of Leister China, put it bluntly during a two-hour conversation: “In China, you design for testing, not for perfection.” Here, perfect is the enemy of fast. Waiting for full pre-launch validation in a vacuum is a luxury the market cannot afford.
Rethinking Customer Orientation: The Ultimate Buyer’s Market
When I observe how Chinese enterprises engage with their customers, several structural insights stand out — ones that meaningfully challenge our traditional Western approach to B2B software product development and service delivery.
Insight 1: A fierce buyer’s market demands real-time response
In a market with 1.4 billion potential users, B2C product testing operates like a real-time playground for iteration. But even in enterprise B2B contexts, the difference in speed and responsiveness is striking. Bruno Kunz, a long-time product leader at Schindler, emphasized that the true market differentiator lies in the supplier-customer relationship: Chinese suppliers operate with a genuine service-first mindset and near real-time response expectations.
Crucially, this relentless speed is highly contextual. It defines consumer tech, digital services, tech hardware, and light manufacturing. Heavily regulated, resource-heavy, or state-controlled industries remain traditional seller’s markets with rigid pre-launch compliance requirements. Industrial manufacturing, medical devices, and automotive B2B still demand exhaustive validation and near-perfect initial deliverables. But outside these highly regulated verticals, the fastest adaptive solution consistently wins market share.
This contrast hit me sharply in a recent meeting with a software leader from one of China’s largest financial institutions. He was complaining about the pace of their traditional Western-style software delivery workflow:
Customer submits formal requirements documentation
Internal team creates a detailed Product Requirements Document (PRD)
Solution architects finalize integration and production architecture documentation
Developers complete coding and unit development
Integration teams execute system integration work
QA teams conduct formal testing cycles
Final handover and customer user acceptance testing
This textbook Waterfall process is familiar to every Western software team. What shocked me, however, is that this full enterprise-grade, regulation-compliant cycle only takes two months for this large Chinese financial firm — lightning-fast by global enterprise standards. And yet, by local market rules, this timeline is still too slow. Customers now demand maximum delivery timelines of 4 weeks, with a strong preference for functional iterations within just two weeks.
The takeaway is clear: Western teams optimize for process certainty; Chinese market players optimize for customer speed and iterative alignment.
Insight 2: “Good enough” wins when backed by instant service resolution
Chinese business customers demonstrate remarkable tolerance for unfinished, imperfect first-version solutions — but only when suppliers deliver instant, reliable resolution to emerging issues. Walter Wang shared a striking example of this operational service philosophy:“If there is a problem, we sometimes just give the customer a new machine — it is cheaper.”
Customer tolerance is never for bugs themselves; it is for slow resolution. As long as suppliers maintain immediate physical or digital proximity to fix issues rapidly, customers actively participate in real-world product testing. A large industrial machinery company confirmed this approach is standard practice: they ship core equipment first, then finalize on-site software configuration and iteration at the customer’s location.
From a Swiss operational lens, this feels inefficient and costly. In the Chinese market logic, it enables faster delivery, tighter real-world product alignment, and hyper-targeted customization that remote, pre-planned development simply cannot match.
Insight 3: To understand users, your engineers must work directly with users
This customer-embedded operational mindset is deeply institutionalized across Chinese tech teams. Yao, Office Manager at Swissnex Shanghai, shared a compelling practice from e-commerce giant Pinduoduo: all software developers are required to complete months of frontline customer support rotations.
This is no symbolic HR exercise. It ensures every engineer writing code possesses visceral, unfiltered, first-hand experience of real user pain points, edge cases, and everyday operational struggles — eliminating the corporate disconnect between internal development teams and end customers that plagues so many Western software firms.
Public accountability further reinforces this standard. Shanghai’s citywide 12345 Citizen Hotline (市民热线) escalates commercial service disputes with extreme urgency, often driving full customer refunds within a week for unresolved service failures. While this mature service benchmark is concentrated in tier-1 coastal cities, it establishes a nationwide cultural expectation of rapid supplier accountability.
The Chinese Error Culture: MTTR Over Perfectionist Post-Mortems
These customer-centric operational norms create an entirely different approach to handling mistakes and product errors — one that stands in stark contrast to traditional European quality culture.
In Europe and Switzerland, our error culture centers heavily on rigorous post-mortem analysis: we pause operations, conduct deep root-cause analysis, and build new procedural safeguards to prevent identical issues from recurring indefinitely. The goal is zero recurrence, achieved through extensive upfront risk mitigation.
In China’s fast-moving commercial tech market, the operational priority is fundamentally different.
Insight 4: Iteration itself becomes your validation
Western quality strategy prioritizes eliminating risk before launch. Chinese market strategy prioritizes MTTR — Mean Time to Resolution above pre-emptive perfection. Product launches are not final milestones; they are live extensions of the R&D process.
Minor post-launch errors are not heavily penalized if engineering teams can deploy OTA (over-the-air) fixes within hours. Months of theoretical pre-launch validation are replaced with rapid, real-world iteration. Iteration is the validation. Live customer feedback becomes the most reliable quality and requirement check available.
Insight 5: The Agile Vicious Cycle — and its brilliant Chinese workaround
This hyper-iterative model carries a structural software engineering tradeoff that Western agile teams often overlook, which Bright at Morimatsu articulated clearly. For early-stage projects with vague or evolving requirements, teams leverage agile workflows to build fast demos and prototypes for customer validation.
The downside is an agile vicious cycle: continuous, unplanned customer changes accumulate endless technical debt, gradually degrading system stability and architectural integrity.
Their solution is sophisticated and highly instructive for B2B software firms: agile for discovery, Waterfall for stabilization. Once rapid iterative prototyping clarifies true user requirements and validates product-market fit, teams deliberately shift back to structured, rigid Waterfall delivery to rebuild, standardize, and stabilize the system architecture. This captures the speed of agile while preserving long-term structural quality — a hybrid approach Western teams rarely implement intentionally.
Insight 6: Error tolerance is situational, not universal
Crucially, China’s iterative error tolerance is not uniform across the market — a critical nuance for foreign software suppliers. Private tech startups and digital platforms embrace small, fast failures as part of iteration, with high tolerance for real-time fixes.
By contrast, state-owned enterprises (SOEs) and government-linked bodies operate under entirely different risk logic. Bureaucratic reputation risk creates near-zero tolerance for visible mistakes, regardless of how fast suppliers resolve issues. For foreign firms partnering with Chinese SOEs, a highly risk-averse, process-heavy, pre-validated delivery model remains mandatory.
Cutting the Food While Cooking: The Power of Radical Customer Proximity
My most foundational takeaway from this sabbatical is a meta-insight with direct strategic implications for our software business: true customer understanding requires radical operational proximity. You cannot deeply grasp real-world user needs, contextual challenges, and business pressures through internal workshops, proxy research, or remote documentation alone.
For a Swiss software team building solutions for Chinese or Asian end customers, distance creates fatal friction: cultural nuance gaps, language barriers, misaligned business context, and punishing time-zone differences eliminate the possibility of fast, informed iteration.
Walter Wang’s culinary metaphor perfectly captures this cultural divide: “Europeans want to sell knives and forks — but the Chinese cut the food while cooking.”
Remote, geographically detached teams cannot replicate the adaptive, in-market iteration that defines successful Chinese product delivery. The most viable strategic path for global software firms is a hybrid operating model: centralize core, culture-agnostic technology development and foundational R&D at headquarters, while empowering autonomous local teams to handle market-specific integration, localization, and customer-facing iteration.
This new operational reality renders two traditional management assumptions obsolete:
The Friction of Distance: Autonomous local teams positioned close to end customers are inherently faster and more operationally effective than distributed global teams. Language, cultural, and timezone fragmentation kill iterative speed. Distributed teams are only justified for highly specialized, protected IP — they should be the exception, not the standard model.
The Death of Traditional Offshoring: Legacy offshoring models were built mostly on labor cost arbitrage. Generative AI is now absorbing the routine coding, testing, and documentation tasks that once justified offshore delivery teams. The old cost-arbitrage model no longer delivers competitive value. The new competitive advantage is customer proximity and iterative speed — something remote offshore teams cannot provide. In fact, I asked several large companies in China about this. Not one of them uses an offshoring model in order to try to save cost, although labor cost in China has not been cheap for several years now.
But what about Chinese products in western Countries?
All the above observations paint a compelling picture: Chinese companies win domestic market share through radical customer proximity, iterative speed, and tolerance for in-market iteration over pre-launch perfection. Yet this raises a provocative, counterintuitive question that challenges my core argument: if on-the-ground customer proximity and localized iteration are non-negotiable for market success, how do Chinese products thrive in Western markets — where most Chinese firms lack local embedded teams, cultural immersion, and real-time user feedback loops?
There is no definitive answer, but cross-market observations reveal three targeted, context-specific strategies that allow Chinese brands to succeed in Western markets without the radical local iteration they rely on domestically — alongside clear limitations that align with my original customer-proximity thesis.
First, standardized commodity products eliminate the need for cultural localization. Mass-produced consumer goods such as small home appliances and daily commodities feature universal functionality and uniform global user demands. For these standardized, low-complexity products, regional cultural nuances and personalized user expectations are negligible. Competitive pricing and consistent basic functionality become the sole purchasing criteria, allowing Chinese manufacturers to capture Western market share without local market adaptation or real-time user iteration.
Second, global tech ecosystem standards override localized user iteration. For high-end consumer tech like smartphones, Western markets are dominated by centralized, globally unified product standards set by industry leaders such as Apple and Google. Chinese tech brands competing in this space do not need to iterate based on regional user feedback; instead, they align with established global UI/UX norms, technical protocols, and feature roadmaps. Compliance with universal industry standards replaces localized customer iteration as the core competitive driver.
Third, imitative benchmarking bridges cultural and contextual gaps for complex hardware. For sophisticated consumer hardware such as new energy vehicles, Chinese brands accelerate Western market adaptation by benchmarking proven Western product design and user experience. For instance, BYD’s vehicle UI/UX closely mirrors Tesla’s established interface logic and interactive paradigms. This mimicry eliminates the need for trial-and-error local iteration, letting Chinese products match Western user expectations from launch.
Crucially, the limits of this model further validate my core thesis — most Chinese industrial B2B products expose clear weaknesses in Western markets precisely due to insufficient customer proximity. Specialized industrial equipment like injection molding machines faces persistent adoption barriers: non-intuitive user interfaces, regionally mismatched operational workflows, incomplete localized documentation, and uncertain after-sales service and spare part support. Western customers accept these frictions only for substantial price advantages, not because of superior customer-centric design or iterative optimization. These products fail to deliver the adaptive, user-aligned experience that defines Chinese domestic market success, precisely because they lack embedded local teams for continuous customer iteration.
In short, Chinese firms’ Western market success is conditional: it works for standardized, rule-bound, or benchmarkable products that negate the need for contextual iteration. It fails for high-context, user-centric, customized B2B solutions — exactly the category our Swiss software firm operates in. This contrast reinforces the core argument: customer proximity and iterative localization are irreplaceable for high-value, context-sensitive B2B services and software solutions.
And exactly this is the reason that leading Chinese consumer brands are now adopting my proposed hybrid model (centralized R&D + local iteration teams) in Europe to solve localization pain points.
My Conclusion: What This Means for Our Swiss Software Firm (Cudos)
Reflecting on these on-the-ground observations and benchmarking them against our 60-person Swiss software services operation, I am convinced: we gain significant competitive advantage by selectively adopting China’s operational speed and customer iteration — without abandoning our Swiss quality heritage.
We must move beyond ivory-tower design exercises that generate internal alignment but no real customer validation. Our unique sweet spot as a mid-sized Swiss firm is clear: we can blend rigorous Swiss precision with modern, AI-powered execution speed to outcompete slow enterprise incumbents and low-cost offshore providers alike.
We do not need to sacrifice high-end reliability, architectural stability, or compliance rigor. Instead, we can supercharge our quality model through fully optimized Continuous Delivery pipelines, enabled by modern engineering tooling and AI agents. What was once a slow, expensive, manual process of building exhaustive automated test coverage is now fast, scalable, and maintainable with AI support.
The core leadership lesson is situational flexibility:
For regulated core backend systems, security-critical architecture, and compliance-heavy client deliverables, we preserve our rigorous Swiss pre-launch precision and zero-failure discipline. For customer-facing digital services, web applications, and new market feature testing, we move decisively into the fast lane: AI-automated quality guardrails, continuous deployment, frontline customer feedback loops, and iteration-first validation.
The brutal, essential truth is this: for fast, competitive global markets, product ownership must shift toward local teams. Local-for-local iteration creates the speed, contextual awareness, and customer alignment that remote Swiss headquarters teams simply cannot replicate.
Discussion Question: Many Western software teams prioritize zero-defect pre-launch validation over iterative customer learning. Is your team’s quality culture slowing your market adaptation, or enabling safe speed? Can your organization adopt a hybrid model — rigorous pre-launch precision for core systems, and iterative, MTTR-driven validation for customer-facing innovation? Let’s discuss in the comments!