The post has been translated automatically. Original language: English
Across both the financial industry and public sector, digital systems are often designed around internal processes rather than user experience. The result is a growing gap between how services are formally structured and how they are actually used.In practice, many systems reflect the needs of internal process owners more than end users. Workflows are built to match organisational structures, approval chains, and control requirements. This often leads to interfaces that are logically consistent from an internal perspective, but unnecessarily complex for users.Common outcomes include:Repetitive data entry even when information already exists in the systemMultiple unnecessary steps for simple actionsFragmented user journeys across different screens or systemsIncreased workload caused by procedural rather than functional requirementsWhile each individual step may be justified internally, the cumulative effect at scale is significant: reduced efficiency, higher operational load, and poorer user experience.This creates a fundamental question in system design:What should take priority — user friendliness, or internal process efficiency for organisations and government operations?In many cases, the answer is not clearly balanced. Systems tend to evolve toward internal convenience and control structures, while user experience becomes secondary. Over time, this can reduce overall system effectiveness, as inefficiencies on the user side translate into increased workload on the operational side.A more effective approach may require treating user experience and internal process design not as competing priorities, but as equally important constraints that need to be aligned from the start of system design.
In the financial industry, it is not uncommon for software design decisions to be strongly influenced by management layers whose primary background is in regulation, compliance, and operational control rather than information technology or product design. While this perspective is essential for governance and risk management, it can also lead to situations where system functionality is shaped more by procedural and regulatory interpretation than by usability or modern digital design principles. As a result, newly developed systems may, in practice, resemble outdated software paradigms, with interface logic and user flows reflecting approaches that are decades old rather than contemporary standards of digital interaction.
What has been your experience with this challenge in digital systems? Where have you seen the biggest friction between internal processes and user experience, and what obstacles do you think prevent better alignment?
Across both the financial industry and public sector, digital systems are often designed around internal processes rather than user experience. The result is a growing gap between how services are formally structured and how they are actually used.In practice, many systems reflect the needs of internal process owners more than end users. Workflows are built to match organisational structures, approval chains, and control requirements. This often leads to interfaces that are logically consistent from an internal perspective, but unnecessarily complex for users.Common outcomes include:Repetitive data entry even when information already exists in the systemMultiple unnecessary steps for simple actionsFragmented user journeys across different screens or systemsIncreased workload caused by procedural rather than functional requirementsWhile each individual step may be justified internally, the cumulative effect at scale is significant: reduced efficiency, higher operational load, and poorer user experience.This creates a fundamental question in system design:What should take priority — user friendliness, or internal process efficiency for organisations and government operations?In many cases, the answer is not clearly balanced. Systems tend to evolve toward internal convenience and control structures, while user experience becomes secondary. Over time, this can reduce overall system effectiveness, as inefficiencies on the user side translate into increased workload on the operational side.A more effective approach may require treating user experience and internal process design not as competing priorities, but as equally important constraints that need to be aligned from the start of system design.
In the financial industry, it is not uncommon for software design decisions to be strongly influenced by management layers whose primary background is in regulation, compliance, and operational control rather than information technology or product design. While this perspective is essential for governance and risk management, it can also lead to situations where system functionality is shaped more by procedural and regulatory interpretation than by usability or modern digital design principles. As a result, newly developed systems may, in practice, resemble outdated software paradigms, with interface logic and user flows reflecting approaches that are decades old rather than contemporary standards of digital interaction.
What has been your experience with this challenge in digital systems? Where have you seen the biggest friction between internal processes and user experience, and what obstacles do you think prevent better alignment?
Share
