• Customer Experience
• Uploaded In: 2022

Why Constraints Drive Superior Customer Experience

Why does a remote control have 60 buttons and we consume less than 10, which are too small and hard to find? Why do many restaurants have lengthy menus, but most customers order the same five dishes, which end up tasting bland or are unavailable?

We all have experienced products or services with countless options and permutations while we struggle to discover and operate the features we are using most frequently. We often wonder why products remain relatively unchanged for long periods despite all of us experiencing the same friction. Digital products, such as websites or apps, suffer from the same issue.

We primarily use them for one singular purpose or a fairly streamlined journey. Yet, we often struggle to find these interactions - nestled between other, rarely used elements. The costs of wrongly or excessively scoped experiences are manifold. They include a frustrating customer experience, high maintenance costs, security risk, and slow time to market.

How can such "feature waste" be avoided? If the answer was clear, and straightforward, we would have outstanding user experiences in our daily lives. Yet, this still doesn't happen, even though the prize is evident, as companies with exceptional focus on customer experiences, such as Netflix, Apple, or Amazon, are collecting outsized rewards.

Does this apply to government interactions as well? Taking the premise that governments operate with limited competition, one could believe that this challenge is irrelevant, as a customer doesn't have a choice. This train of thought, however, obscures the actual cost of a bad customer experience. To start with, governments do not operate as monopolies. In a connected world, residents can walk away and change location - not just on a communal but also on a national level. Even more importantly, sub-standard customer experiences hamper economic well-being.

Accepting the importance and urgency of the issue, why do we often appear to get stuck, taking one step forward and two steps back? Several dynamics are at play:

• Organisational cultures that fear change or favour exhaustiveness over focus. Often, stakeholders mistake deprioritising features with rejecting customers' needs instead of realising that accommodating exceptions impact the delivery of services catering to the majority. Governmental structures are often more prone to this dynamic, as equally serving all requests is perceived as a mandate.
• Engineering teams embrace complexity and do not contribute to simplification. It is commendable that engineers are assigned to tackle the most complicated problems, as they are the most challenging intellectually. However, often what appear to be simple problems are the most relevant to solve.
• Financial policies that are risk averse and prefer gradual improvements over bold new approaches. This position naturally favours incremental improvements and restricts radical simplifications as their risks outweigh the benefits.
• The misguided notion that digitisation is favourable in all cases. The benefits of digitisation are declining with a reduced frequency of interaction.

Over the past decade, the default answer to overcome these challenges has been "customer-centricity." In the wake of this trend, customer insight and analytics disciplines have been sprawling, both in qualitative and quantitative areas.

Listening and acting on customers' feedback is helpful. To date, however, it hasn't fully succeeded. Often, customer insight is only intensifying the dynamics outlined above, as stakeholders introduce even more requirements. "Customer X is asking for this feature" is often used as a convenient argument in negotiations related to product scope.

While customer insight is one of the significant constituents of successful product and services design, it can't unleash its potential without the definition of constraints in advance, such as:

• Time to market: Which customer insights can we accommodate if a release needs to happen in X weeks? Which ones can we tackle later as they are less relevant, handled manually, or ignored?
• Costs: How much should we reasonably spend for product/service/website app, given potential benefits (revenues, savings, satisfaction)?
• Features: What do we believe is the maximum acceptable scope of design? E.g., the number of boxes, number of web pages, and number of buttons that we can expose to a customer for optimal customer experience.
• Duration: What's the maximum acceptable duration of a customer experience (in steps or minutes)?
• Scope: Which group of customers will be in scope? How much of the total share of interactions can we accommodate?

It is paramount that all stakeholders agree upon such constraints before consulting customer insight to specify a product and stick to it. Understanding that the most significant threat to the project would be feature waste, the supervisory team defined several constraints at the beginning of the project, in particular:

• A non-negotiable date for the first production release and subsequent release cycles
• A cost and development capacity ceiling
• A time limit for the duration of main interactions, such as the process of booking an appointment for visa submission
• The rollout velocity across global operations.

After agreeing on these constraints, we launched the discovery phase to assess requirements, dependencies, and performance parameters. As expected, they were regularly challenged, especially with new requirements raised in line with business development. However, it was clear to all stakeholders that constraints would take precedence over any other factor impacting the project. As a result, the project - after a Covid-induced hiatus - will see its completion in 2022.

If you have any feedback on this article or would like to reach out to our team to know more, please email us at
communications@vfsglobal.com

---