The Portal Is Not the Service

A portal is an interface. A service is the full set of people, policies, data, processes, and decisions that make an outcome possible. That distinction matters whenever a portal asks a customer to do something the operation cannot see, support, or complete reliably. A polished dashboard does not help if the status behind it is stale. A useful form becomes frustrating when a representative cannot see the submission. A self-service task fails when an exception has nowhere to go. The most useful question is not “What features should the portal have?” It is “Which customer task are we making easier, and what must be true behind the screen for it to work?” That question exposes the dependencies feature roadmaps routinely hide: data quality, eligibility rules, staff context, exception handling, accountability, and measurement. A portal is valuable when it makes a real service more understandable, more predictable, or easier to complete. It is not valuable simply because it moves an interaction onto a screen.

A portal can hide organizational fragmentation

The GOV.UK Service Standard argues that digital services should solve a whole problem for users, work across organizational boundaries, and join related interactions into a coherent journey. A portal designed around internal departments does the opposite: it exposes the organization chart as navigation. (GOV.UK Service Standard, 2019) A stronger portal roadmap starts with task evidence. For each major task, document:

• the customer’s intended outcome;
• the systems and teams required to fulfil it;
• the common failure and recovery paths;
• the status information the customer needs; and
• the operational measure that indicates whether it worked. This creates an important separation between portal performance and service performance. Page views, logins, and form submissions describe use of the interface. Completion, resolution, repeat contact, and cycle time describe the service. Both sets of measures are useful. Confusing them is how organizations end up with a successful portal and an unchanged customer problem.

Sources

• GOV.UK Service Standard, “Solve a whole problem for users,” 2019