how do i choose a design partner for infrastructure and systems?
infrastructure and system design are not about a single object, but rather about interconnected usage processes, information, spaces, and technical components. a suitable design partner must be able to identify these interdependencies and coordinate them with architecture, engineering, operations, and communication.
scope of services and delimitation
infrastructure projects involve many touchpoints: entrances, wayfinding, waiting areas, service points, information, and technical installations. therefore, clarify which parts of the system the design partner will handle and which will remain the responsibility of the specialized planners. the design should organize these interfaces, not mask unclear lines of responsibility.
from a single point of contact to the entire system
a good design begins with the paths and tasks of different user groups. consider arrival, orientation, use, and onward movement as a coherent sequence. this reveals what information is needed and when, and where spatial or technical decisions conflict with one another.
four criteria for choosing a partner
- understanding of the system: the partner should be able to structure the relationships between space, information, and product components.
- coordinate stakeholders: operations, planning, safety, and branding all require transparent decision-making processes.
- develop scalable principles: recurring elements should be adaptable to different locations or situations.
- test real-world usage: walking routes, sightlines, and information hierarchies should be tested in realistic situations as early as possible.
project process and decisions
start by analyzing user flows, site conditions, and existing standards. this process identifies prioritized problem areas and design principles. only then are individual elements worked out in detail. for complex systems, prototypes, mock-ups, or test installations are particularly helpful because it is difficult to fully assess scale and visibility on screens.
example of a train station area
suppose a train station area is being equipped with new information and waiting area elements. a standalone design for the signs may fail if sightlines, lighting, or pedestrian flow are not taken into account. a more effective approach is a cohesive system that integrates spatial positioning, an information hierarchy, and recurring design elements.
common mistakes in selection and contracting
solutions that work only in an idealized visualization are problematic. furthermore, too many custom solutions developed in parallel complicate operation and maintenance. therefore, ensure that the system follows a clear logic and define which exceptions are truly necessary. accessibility and safety requirements must be coordinated with the relevant specialist planners.
compare costs and schedules effectively
for infrastructure systems, the scope of work is determined by the number of locations, stakeholders, prototypes, and coordination meetings. compare proposals based on the analysis, system development, detailed planning, and implementation support they include. also, clarify who will maintain the data and standards after the project ends.
the briefing for an initial meeting
compile a list of locations, user groups, existing standards, and known problem areas. identify technical and structural constraints, as well as the responsible discipline specialists. plans, photos, and existing usage data are helpful. also specify which parts of the system should be standardized and which should remain location-specific.
frequently asked questions about infrastructure and system design
what distinguishes system design from individual product design?
system design takes into account multiple elements and their interactions. a single object may be well-designed but still fail to function within the overall process. that is why interfaces and recurring rules are defined early on.
when should the design partner be brought on board?
before key spatial and technical interfaces have been defined. this allows user flows and information needs to be incorporated into the planning process.
how are different locations taken into account?
through shared fundamental principles and clearly defined variables. not every deviation requires a new design; at the same time, local structural or operational conditions must not be ignored.
is wayfinding part of system design?
it can be an important part of it. however, wayfinding is not only provided by signs, but also by spatial structure, sightlines, light, and recognizable elements.
how can a system be tested before implementation?
depending on the task, this may involve scale mock-ups, digital simulations, temporary markings, or test installations. it is important that the testing method accurately reflects the relevant usage scenario.
who coordinates the specialized planners?
this must be explicitly specified in the project model. the design partner may coordinate design interfaces; formal technical responsibility remains with the planners commissioned for that purpose.
the perspective of f/p design
with the üstra train station, f/p design has worked on a project that brings together architecture and transportation design. projects like this illustrate that spatial, technical, and design decisions must be viewed as a system. you can find out more about the studio at about f/p design.
in addition: design consulting and completed industrial design projects.
