Designing Around the Human Experience, Not Institutional Boundaries
THE FUTURE OF GLOBAL PILGRIMAGE INFRASTRUCTURE
A Research Essay Series by Dhian Arinofa
GPI Research Essay 006 of 52
Systems • Governance • Digital Infrastructure • Knowledge • Human Experience
Executive Summary
A pilgrimage is experienced as one human journey, yet the infrastructure supporting it is distributed across many organizations, technologies, locations, and institutional responsibilities.
Airlines manage flights. Government authorities oversee regulatory processes. Accommodation providers manage hotels. Transportation operators coordinate mobility. Digital platforms facilitate access to information and services. Human service providers assist travelers through unfamiliar environments.
Each participant has a legitimate and necessary role.
But the pilgrim does not experience these institutional boundaries as separate journeys.
The pilgrim experiences preparation, departure, arrival, movement, worship, assistance, uncertainty, and return as parts of one continuous experience.
This creates an important design question:
What changes when we design the system around the pilgrim rather than asking the pilgrim to navigate the system?
In GPI-004, I introduced the Pilgrimage Infrastructure Stack, a conceptual framework describing six interconnected infrastructure layers.
In GPI-005, I explored how those layers can become connected ecosystems through governance, information, operations, knowledge, and human continuity.
GPI-006 moves the perspective from the ecosystem to the individual traveling through it.
This essay proposes that the future of pilgrimage infrastructure should be evaluated not only by how effectively individual services operate, but by how clearly, responsibly, and continuously those services support the human journey.
The pilgrim should experience the journey, not carry the architecture behind it.
The Big Question
What if the journey—not the institution—became the starting point for infrastructure design?
Most complex systems are organized around institutional responsibilities.
An airline is responsible for aviation.
A hotel is responsible for accommodation.
A transportation company is responsible for mobility.
A government authority is responsible for its regulatory mandate.
A technology provider is responsible for its digital capabilities.
These boundaries are necessary.
They establish specialization, operational control, accountability, and governance.
But human experiences rarely follow organizational charts.
A traveler moving through an international pilgrimage journey may interact with many institutions without understanding how their responsibilities are divided.
And they should not need to understand every institutional boundary simply to complete a coherent journey.
This leads to a fundamental distinction.
Institutions organize services. People experience journeys.
A well-designed ecosystem must account for both realities.
The objective is not to eliminate institutional boundaries.
It is to prevent those boundaries from becoming unnecessary burdens for the people they serve.
- A Journey Is Not Simply a Collection of Transactions
A pilgrimage journey is often represented through a series of transactions.
A flight is booked.
A travel authorization is processed.
Accommodation is confirmed.
Transportation is arranged.
A digital account is created.
A service is delivered.
Each transaction has a defined process, responsible organization, and completion status.
From an operational perspective, these milestones matter.
They allow institutions to measure performance and fulfill obligations.
Yet successful transactions do not automatically produce a successful journey.
Consider a hypothetical traveler whose flight, accommodation, and transportation have all been confirmed.
Every service may be functioning as expected.
But if the traveler does not know where to meet the transportation provider, cannot understand the instructions, or receives conflicting information, the experience remains fragmented.
The issue is not necessarily a failed transaction.
It is a failure of continuity between transactions.
Transaction completion is not the same as journey continuity.
This distinction invites us to reconsider what system performance should mean.
Instead of evaluating only whether each service has been delivered, we should also examine whether the person can move between services with clarity and appropriate support.
- The Institutional View and the Human View
There are two ways to understand a complex journey.
The Institutional View
Organizations typically focus on operational milestones:
Documentation processed
Reservation confirmed
Vehicle assigned
Accommodation allocated
Service delivered
Transaction completed
These measures help maintain operational discipline and accountability.
The Human View
The person moving through the journey may ask very different questions:
Am I prepared?
What happens next?
Where should I go?
Can I understand the instructions?
Who can help me?
What happens if the plan changes?
Will I need to explain my situation again?
These are not merely emotional questions.
They represent practical needs involving information, coordination, accessibility, and decision-making.
The institutional view describes what organizations have completed.
The human view reveals whether the person can successfully navigate the experience those organizations collectively create.
Both perspectives are essential.
But the second is often less visible in conventional operational reporting.
Operational completion should contribute to human clarity—not exist independently of it.
- The Journey Begins Before Departure
The physical journey may begin at an airport.
But the human journey begins much earlier.
It begins when someone decides to undertake pilgrimage.
From that moment, the person enters an environment of decisions, information, expectations, documentation, and preparation.
They may need to understand travel requirements, coordinate with family members, assess accessibility needs, prepare documents, and learn how unfamiliar processes work.
This is why pre-departure preparation should be understood as part of infrastructure design.
It is not simply an administrative phase.
It shapes the traveler's ability to navigate subsequent experiences.
Reliable guidance can reduce avoidable uncertainty.
Clear documentation processes can improve readiness.
Accessible information can support informed decisions.
And appropriate preparation can help travelers understand where assistance will be available.
The system does not begin supporting the person only when they arrive at the destination.
The quality of a journey is influenced long before the traveler begins moving.
This principle builds on the discussion introduced in GPI-003, Before the Journey Begins.
- The Journey Is a System of Transitions
When we examine complex journeys, we often focus on the major services involved.
Flights.
Hotels.
Transportation.
Digital platforms.
Government processes.
But some of the most important experiences occur between these components.
A traveler moves from preparation to departure.
From arrival to immigration.
From immigration to transportation.
From transportation to accommodation.
From accommodation to local mobility.
From planned activities to unexpected changes.
From the destination to the return journey.
Every transition introduces potential needs for information, coordination, assistance, and reassurance.
This suggests that the quality of a journey cannot be understood only through the quality of its individual components.
We must also examine the connections between them.
Does the traveler understand where the next service begins?
Is the necessary information available to the responsible provider?
Can changes be communicated before they create confusion?
Is assistance accessible when something unexpected happens?
These questions reveal an important principle:
The quality of a journey often depends on what happens between services.
And what happens between services is frequently where institutional complexity becomes a human experience.
- Introducing the Pilgrim Journey Continuity Framework
To examine the journey more systematically, I propose a conceptual model:
THE PILGRIM JOURNEY CONTINUITY FRAMEWORK
PREPARE → NAVIGATE → TRANSITION → EXPERIENCE → ADAPT → RETURN
These six stages represent recurring human needs across a pilgrimage journey.
They are not intended as a rigid sequence.
Real journeys involve overlapping activities, repeated transitions, changing circumstances, and different individual needs.
The framework provides a lens for understanding how infrastructure can support continuity across those conditions.
01 — PREPARE
Readiness before movement.
Preparation includes gathering information, understanding requirements, making decisions, completing documentation, and developing expectations.
The infrastructure challenge is to make preparation understandable, accessible, and coordinated.
Design question: Does the traveler understand what is required before the journey begins?
02 — NAVIGATE
Clarity in unfamiliar environments.
Travelers move through airports, institutions, digital platforms, transportation systems, and physical environments that may be unfamiliar.
They need reliable instructions, language support, accessible communication, and identifiable points of assistance.
Design question: Can the traveler understand where they are, what comes next, and how to obtain help?
03 — TRANSITION
Continuity between services.
A journey requires movement between organizations, locations, responsibilities, and processes.
These transitions should preserve relevant information and reduce unnecessary repetition.
Design question: Can the traveler move between services without repeatedly reconstructing their situation?
04 — EXPERIENCE
Supporting the purpose of the journey.
Pilgrimage is not simply about reaching a destination.
It involves worship, reflection, community, personal meaning, and human connection.
Infrastructure should support these experiences without unnecessarily dominating them.
Design question: Does the infrastructure create space for the purpose of the journey?
05 — ADAPT
Continuity when circumstances change.
Journeys rarely unfold exactly as planned.
Schedules change.
Services may become unavailable.
Travelers may require additional assistance.
A resilient system must support informed decisions, clear communication, and appropriate human intervention.
Design question: Can the system respond to change while preserving clarity, dignity, and human agency?
06 — RETURN
Supporting the journey through completion.
The journey does not end simply because the main destination has been visited.
Departure coordination, return transportation, documentation, communication, and outstanding service issues may still require attention.
Design question: Does the system maintain appropriate support until the journey is genuinely complete?
Together, these six stages encourage a shift from service-centered delivery toward journey-centered infrastructure.
- Designing for Continuity, Not Just the Ideal Plan
Many journey maps appear as clean, linear sequences.
One step follows another.
Every transition occurs on time.
Every service performs as expected.
But real journeys are dynamic.
Flights may be delayed.
Weather may affect transportation.
Digital platforms may become temporarily unavailable.
A traveler may require additional assistance.
Different members of the same group may have different needs.
This means infrastructure must be designed for adaptation rather than only for ideal conditions.
We can distinguish between two forms of continuity.
Planned continuity describes how services are expected to connect under normal conditions.
Resilient continuity describes how support is maintained when circumstances change.
Both are necessary.
A system that functions only when everything goes according to plan is not necessarily a resilient system.
The quality of journey-centered infrastructure becomes especially visible when the original plan no longer works.
This is why exception management, escalation procedures, and human assistance should be considered part of the architecture rather than temporary solutions added after a disruption occurs.
- The Problem of Repeated Context
One symptom of fragmented systems is the repeated need to explain the same situation.
A traveler provides information to one organization.
Then provides it again to another.
They explain a change to a coordinator.
Then repeat the explanation to a service provider.
They receive instructions through one platform.
Then must verify those instructions through another.
Some repetition is necessary.
Organizations have different legal responsibilities, and privacy requirements may restrict how information can be shared.
But unnecessary repetition can reveal gaps in coordination.
A journey-centered system should consider how relevant context can follow the person through authorized and appropriately governed processes.
This does not require every organization to access every record.
It requires clarity about which information is needed, who is authorized to access it, and how it should be protected.
The person should not become the permanent messenger between systems that could coordinate more responsibly.
This is not only a technology challenge.
It is a governance, information architecture, and operational design challenge.
- Knowledge Is Infrastructure, Not Just Information
Digital access does not always produce understanding.
A traveler may receive a notification without knowing what action it requires.
A translated instruction may be grammatically correct but lack necessary context.
A digital platform may contain accurate information that is difficult to locate or interpret.
This is where knowledge infrastructure becomes essential.
Information provides content.
Knowledge provides context.
Understanding supports action.
And action enables people to navigate unfamiliar environments more effectively.
For multilingual and cross-border journeys, this distinction is especially important.
Knowledge design must consider language, terminology, accessibility, cultural context, and the practical circumstances in which guidance is used.
The relevant question is not simply:
Has the information been delivered?
It is:
Can the person understand what it means and what they should do next?
This is why knowledge should be treated as part of the infrastructure supporting the journey.
- Human-Centered Does Not Mean Technology-Free
Human-centered design is sometimes misunderstood as a preference for human assistance over digital technology.
That is not the argument here.
Technology can improve accessibility, coordination, and continuity.
Automation can reduce repetitive administrative work.
Digital platforms can make information easier to access.
Artificial intelligence may support multilingual guidance, contextual knowledge retrieval, and operational assistance.
But technology should be evaluated by the human outcomes it enables.
Does it reduce unnecessary effort?
Does it improve clarity?
Does it support informed decisions?
Does it preserve meaningful choices?
Can the traveler reach human assistance when necessary?
Does the system respect privacy and accountability?
These questions are more important than the number of applications or AI features introduced.
Technology should strengthen human capability, not transfer more complexity to the people using it.
The objective is not to make the journey more technological.
It is to make the journey more coherent.
- Designing for Human Variation
There is no single universal pilgrim experience.
Travelers differ in age, language, mobility, digital literacy, prior experience, family responsibilities, and support needs.
Some travel independently.
Others travel in groups.
Some are experienced international travelers.
Others may be navigating unfamiliar institutions for the first time.
A system designed around one idealized user may work well for that user while creating barriers for others.
Human-centered infrastructure must therefore recognize variation as a normal design condition.
This may involve accessible information, alternative communication channels, multilingual guidance, appropriate human assistance, and flexible operational processes.
It also requires avoiding the assumption that everyone should interact with technology in the same way.
The objective is not identical experiences.
It is equitable access to the support needed to navigate the journey.
Human-centered infrastructure should accommodate human variation rather than treating it as an exception.
- Measuring the Journey, Not Only the Services
Traditional performance indicators remain important.
Flight punctuality.
Accommodation readiness.
Transportation availability.
Document processing times.
Service completion rates.
But these indicators do not fully describe the experience across organizational boundaries.
Journey-centered infrastructure requires additional analytical dimensions.
Transition Clarity
Can travelers understand what happens between one service and the next?
Information Consistency
Do authorized participants provide compatible and current instructions?
Context Continuity
How often must travelers repeat information that could appropriately be shared?
Assistance Accessibility
Can travelers obtain support when they need it?
Adaptation Capacity
Can the ecosystem respond coherently when circumstances change?
Journey Completion
Are responsibilities maintained through the final stages of the journey?
These dimensions are proposed for further research rather than presented as a validated measurement instrument.
Their purpose is to shift attention from isolated service completion toward continuity across the entire human experience.
A journey-centered system should be evaluated not only by what its components accomplish, but by what the person can successfully experience between them.
- From Journey Mapping to Journey Architecture
Journey mapping helps us understand what people experience.
It identifies activities, transitions, questions, and potential difficulties.
But mapping the journey does not automatically improve the systems behind it.
Meaningful improvement requires translating those observations into architectural decisions.
If a transition creates confusion, the solution may require clearer communication.
If information must be repeatedly provided, the solution may involve more responsible information exchange.
If operational changes produce conflicting instructions, the solution may require better governance and escalation procedures.
If digital guidance is difficult to understand, the solution may require improved knowledge design.
This reveals an important distinction.
Journey mapping makes the experience visible.
Journey architecture redesigns the systems that shape it.
The first helps us understand.
The second helps us improve.
Both are necessary.
- Human Experience Is an Outcome of Infrastructure
In GPI-004, I introduced six interconnected infrastructure layers:
Physical • Institutional • Operational • Digital • Knowledge • Human
The experience of the pilgrim should not be treated as a seventh infrastructure layer.
It is the outcome of how these six layers interact.
Governance affects clarity.
Operations affect continuity.
Digital infrastructure affects accessibility.
Knowledge affects understanding.
Physical infrastructure affects movement.
Human infrastructure affects assistance and adaptation.
If we treat human experience as an isolated feature, department, or application, we risk reproducing the fragmentation we are trying to address.
Experience is shaped throughout the architecture.
It cannot simply be added at the end.
Human experience is not another component of the system. It is what the system collectively produces.
- The Pilgrim Should Not Carry the Architecture
Complex journeys require complex infrastructure.
That complexity cannot simply disappear.
Institutional responsibilities, operational processes, digital systems, safety requirements, and governance structures remain necessary.
But the person moving through the journey should not be required to understand every organizational boundary behind it.
They should not need to reconcile conflicting information between unrelated platforms.
They should not have to identify which institution owns every operational transition.
They should not become the primary coordinator of services that have already been arranged.
This does not remove the traveler's own responsibilities.
People still make decisions, provide necessary information, and participate actively in their journeys.
The distinction is between meaningful human participation and avoidable administrative burden.
A well-designed system supports agency without transferring unnecessary institutional complexity to the individual.
The pilgrim should experience the journey, not carry the architecture behind it.
The Conceptual Model
THE PILGRIM JOURNEY CONTINUITY FRAMEWORK
PREPARE → NAVIGATE → TRANSITION → EXPERIENCE → ADAPT → RETURN
Supported by:
Physical Infrastructure
Institutional Infrastructure
Operational Infrastructure
Digital Infrastructure
Knowledge Infrastructure
Human Infrastructure
Together, these layers should support:
Clarity • Continuity • Accessibility • Adaptability • Human Agency
The framework does not assume that every journey follows a fixed sequence or that all institutions should operate through a single platform.
It proposes a shared design orientation:
Organize infrastructure around the continuity of the human experience.
Implications for the Future
For policymakers and institutions: Regulatory and administrative processes should be examined in relation to the full human journey, including transitions between organizations.
For operators: Journey continuity, communication, and exception management deserve attention alongside traditional service delivery metrics.
For technology developers: Digital tools should be evaluated partly by whether they reduce unnecessary effort and improve clarity across service boundaries.
For knowledge designers: Information should be organized around decisions people need to make, rather than only around the structures of the institutions producing it.
For researchers: Pilgrimage offers a valuable context for studying complex human systems, cross-border coordination, institutional design, and digital infrastructure.
For ecosystem leaders: Long-term improvement may depend on aligning specialized services around shared human outcomes.
These implications extend beyond pilgrimage.
Healthcare, education, transportation, public services, and other complex environments face similar challenges.
Many organizations contribute to one human experience.
The quality of that experience depends on how well their responsibilities connect.
Reflection
GPI-004 mapped the invisible infrastructure behind the journey.
GPI-005 examined how its components could become a connected ecosystem.
GPI-006 brings the human being back to the center of the architecture.
Because the purpose of infrastructure is not simply to organize institutions more efficiently.
It is to enable people to navigate complex environments with greater clarity, dignity, and confidence.
A pilgrim does not need to see every system working behind the journey.
They need to understand what comes next.
They need reliable information.
They need coordinated support.
And when circumstances change, they need a system capable of responding without making them carry every operational consequence alone.
The future of pilgrimage infrastructure may therefore depend on a fundamental shift:
From designing services around institutional boundaries—
to designing infrastructure around the continuity of the human journey.
The pilgrim should experience the journey, not carry the architecture behind it.
Key Insights
A pilgrimage is one human journey supported by multiple institutional systems.
Transaction completion does not necessarily guarantee journey continuity.
Transitions between services deserve as much attention as individual services.
The Pilgrim Journey Continuity Framework proposes six stages: Prepare, Navigate, Transition, Experience, Adapt, and Return.
Journey-centered infrastructure must support both planned and unexpected circumstances.
Relevant context should move responsibly across services without unnecessary repetition.
Knowledge infrastructure transforms information into practical understanding.
Human-centered design must accommodate different languages, abilities, and support needs.
Journey mapping identifies experience gaps; journey architecture addresses the systems producing them.
Human experience is an outcome of infrastructure, not an additional infrastructure layer.
Coming Next — GPI-007
WHEN DIGITAL BECOMES INFRASTRUCTURE
Why Digital Transformation Must Move Beyond Applications and Platforms
GPI-006 examined the human journey as a system.
GPI-007 will explore when digital technology becomes essential infrastructure rather than simply another service channel.
If digital systems increasingly shape identity, access, information, coordination, and decision-making, the next question is no longer simply:
How do we digitize more services?
It becomes:
What makes digital systems dependable enough to function as infrastructure?
THE FUTURE OF GLOBAL PILGRIMAGE INFRASTRUCTURE
A Research Essay Series by Dhian Arinofa
GPI Research Essay 006 of 52
Systems • Governance • Digital Infrastructure • Knowledge • Human Experience
Author's Note: The frameworks presented in this essay are conceptual research propositions intended to support further observation, discussion, and validation. Illustrative scenarios are hypothetical and are not presented as documented empirical research findings.
Top comments (0)