Space Telescope Scheduling System
(ESA / NASA level)
AN UNEDITED LIVE ARCHITECTURAL RESPONSE · TRANSLATED 1:1


01 / LAB
LIVE DESIGN TEST
Live Design Test
(ESA / NASA level)
AN UNEDITED LIVE ARCHITECTURAL RESPONSE · TRANSLATED 1:1
AN UNEDITED LIVE ARCHITECTURAL RESPONSE · TRANSLATED 1:1
LIVE ARCHITECTURAL RESPONSE · TRANSLATED 1:1
LIVE ARCHITECTURAL RESPONSE · TRANSLATED 1:1
LIVE ARCHITECTURAL RESPONSE · TRANSLATED 1:1
LIVE ARCHITECTURAL RESPONSE · TRANSLATED 1:1
INTERNATIONAL MIGRATION FUND · ARCHITECTURAL CONCEPT
A COMPLETE RESIDENTIAL CARE ARCHITECTURE FOR CHILDREN
Second Family is an architectural and operational model for replacing traditional institutional children's homes with a structured residential care system.
The reference facility is a six-storey building designed for approximately 120 children. Instead of institutional dormitories, shared sanitary facilities and rotating care organised primarily around staff schedules, it uses individual bedrooms, small residential apartments, permanently present caregivers and dedicated infrastructure for education, healthcare, transport and personal development.
The project integrates the building, staffing model, daily operations, financial structure and transition into adulthood into one reproducible system.
The building has a six-storey U-shaped layout, divided into three functional wings.
The two shorter side wings contain residential apartments for children. The long central wing accommodates two- and three-room apartments for caregivers, including space for their partners and, where applicable, their own children.
The U-shaped arrangement creates an enclosed internal courtyard, which can accommodate green areas, outdoor activities and protected recreational space.
The ground floor provides shared facilities, including:
Residential and shared functions are separated physically while remaining connected within the same building.
The basic residential unit is one apartment for three children, not an institutional dormitory.
Each standard apartment contains:
The kitchenette is intended for everyday snacks, drinks and simple food preparation. The building's main catering infrastructure remains available for regular meals.
Each child has a private room that can be furnished and decorated according to age and individual preferences. Bedrooms can be repainted, furniture adjusted and decorative elements changed as the child develops.
A dedicated maintenance and renovation team supports these adaptations alongside normal building upkeep.
This provides an individual domestic environment inside a larger residential institution, rather than expecting children to treat a shared corridor and a bed as their home.
The staffing model is differentiated by age rather than applying one universal ratio.
Children above six years old: approximately one caregiver per six children.
Children between two and six years old: approximately one caregiver per three children.
Children below two years old: approximately one caregiver per three children, with the group living directly inside the caregiver's residential household.
The youngest children therefore receive care within a stable domestic environment rather than being accommodated in conventional institutional bedrooms.
Caregivers are residential members of the building's community, not exclusively employees arriving and leaving for individual shifts.
Their apartments allow them to live with partners and their own children where appropriate. This provides a more stable adult presence within the residential environment.
Continuity of attachment is built into the operational model. A caregiver responsible for a group of three very young children should, as a principle, remain with that group through subsequent developmental stages.
When the children reach approximately six years of age, the original group may be combined with another group of three, moving toward the one-to-six staffing model without unnecessarily replacing the existing caregiver.
The objective is to organise staffing around stable relationships while retaining professional supervision and age-appropriate care ratios.
Specialist support is incorporated into the permanent operating structure.
The facility provides dedicated space and access to psychologists, psychotherapists, speech therapists, developmental specialists and medical professionals.
Children receive individual support according to their needs rather than depending exclusively on occasional external referrals.
The educational system includes school support, tutoring, extracurricular activities, mentoring, talent identification and scholarship opportunities.
A child's abilities may be developed through music, sport, science, technology, art, technical crafts or other disciplines.
These are budgeted operating functions, not optional activities that depend entirely on occasional donations.
Second Family includes specific rules for ordinary personal needs that are often overlooked in institutional operating models.
Clothing and school supplies are purchased individually. A caregiver may take two or three children shopping, allowing them to choose appropriate clothes and personal items within an established budget.
Children receive age-adjusted pocket money, giving them practical experience with financial decisions and responsibility.
At an appropriate age, children receive personal phones and connectivity. From the relevant school stage, laptops become standard personal learning equipment rather than devices available only in shared computer rooms.
A dedicated gift budget covers birthdays, Children's Day and other important occasions. Gifts are selected according to individual interests, age and needs, and may include toys, sports equipment, electronics or creative tools.
Personal possessions remain personal possessions.
These costs are included in the facility's financial planning because they are part of everyday residential care, not exceptional charitable expenditure.
Each Second Family facility has its own transport fleet.
The reference specification includes:
This fleet enables organised transport to schools, medical appointments, therapy, sports activities, cultural events, holidays, excursions and other external commitments.
The home does not need to depend entirely on third-party transport services or improvised arrangements whenever children need to leave the building.
Transport is therefore a permanent infrastructure layer with its own vehicles, personnel, maintenance requirements and operating budget.
Second Family is designed to operate through a foundation with transparent financial management.
Funding combines potential public support, recurring corporate commitments and private donations.
Corporate participation is organised around actual operating costs or designated facilities. For example:
The financing structure must also cover properly paid caregivers, drivers, psychologists, therapists, medical support, maintenance personnel and other permanent staff.
A dedicated public reporting platform provides visibility into budgets, expenditure categories, purchases, operating costs and sponsor contributions.
Reporting may document the financing of accommodation, room renovations, vehicles, education, therapy hours, gifts and scholarships without disclosing confidential information about individual children.
The objective is to make each facility financially accountable while protecting the privacy and dignity of its residents.
Support is not designed to terminate automatically when a resident reaches eighteen.
Second Family includes a separate transition-housing programme for young adults leaving residential care.
Graduates may move into affordable, supported rental apartments while studying, entering employment or establishing independent households.
During the transition period, they can continue receiving mentoring, psychological support where needed, educational assistance and practical guidance in financial management.
This creates a gradual change from residential care to independent adulthood rather than an abrupt loss of accommodation and support.
Transition housing is planned as part of the wider system, with dedicated funding and housing capacity.
The long-term reference programme envisages up to 1,000 Second Family homes across Europe.
Individual facilities follow a repeatable architecture and operating framework, with adaptation to national legal requirements.
At network scale, the system can share building templates, procurement standards, staff-training programmes, operational procedures, educational partnerships, transport standards, financial reporting and programme evaluation.
Each facility remains a functioning local residential environment, while the larger network provides organisational support, purchasing capacity and consistency.
Second Family is therefore not a proposal for one exceptional children's home.
It is a repeatable specification for residential infrastructure that combines accommodation, permanent care, education, mobility, financial accountability and long-term support.
The architectural principle is straightforward: every part of the child's daily life must have a designed solution, an operating responsibility and a sustainable source of support.
FUNCTION DEFINES SPACE
When I designed my own house, I started with how the people living in it would actually use it. I was not interested in empty space for its own sake, impressive dimensions or a layout chosen because it looked attractive on paper. Every room and every floor had to perform a function.
The ground floor is the more public and working part of the house: living space, offices and a guest room. Visitors can spend an afternoon downstairs without entering the private life of the household. The upper floor is organised around entirely different needs. My bedroom has its own bathroom, dressing room and terrace, creating a complete place to rest. My daughters have individual bedrooms with a shared bathroom between them. There is a separate room intended primarily for my parents, and a gym for me.
The division is not only vertical. A second staircase creates a private circulation route. I can leave guests having coffee downstairs, move to the gym and then reach the wellness area without crossing their space. The entrances to the wellness area and laundry are discreetly incorporated into the plan. They remain functional without becoming visual centres of the house.
The building is C-shaped. Its outward-facing elevation is closed, without windows; the inward-facing side opens towards the rear panoramas through extensive glazing. The compact rooms and deliberately restrained circulation spaces make the interior feel intimate and protective rather than monumental.
Even the dark corridor is intentional. With no windows, it becomes a gallery for my photographic work, illuminated by controlled LED lighting. Darkness is not a defect to repair when it serves the room's purpose.
The architecture is not a collection of attractive rooms. It is the relationship between privacy, movement, everyday activity, comfort and the people who will live there. The geometry is what those decisions produce.
In a modular production facility I designed, the governing requirement was a fully unidirectional material flow. A module should move from material supply, through production and testing, to final dispatch without unnecessary crossings, backtracking or interruptions to work elsewhere.
That sounds simple until the movement of large modules becomes part of the problem. An overhead crane may appear to be the conventional answer, but it also imposes structural requirements on the building and operational constraints on the plant. Moving one module can interfere with activities at other stations. The crane was therefore not something I wanted to optimise. It was a dependency I wanted to remove.
I designed a transport frame using principles borrowed from a BDF container trailer, adapted to the factory with smaller wheels and pneumatic positioning. Deployable supports raise the wheels off the ground and locate the frame securely during work. When the module needs to move, an electric industrial tug pulls the frame along its own transport lane.
That lane is separated from pedestrian circulation and workstations. Moving a module does not require operators at neighbouring stations to stop. Empty frames return along a dedicated route that does not cut across forward production flow. Material preparation, welding, painting, carpentry, assembly, testing and dispatch can therefore be organised as one directional system.
The design also incorporates industrial use of recovered and recycled materials. Material choices belong within the functional and production architecture rather than being treated as a decorative sustainability claim.
The point is not that truck-derived pneumatic equipment is universally better than a crane. It is that the required function determines the solution. If existing machinery fits, I use it. If it introduces a constraint that matters to the whole system, I modify it or design something new.
A catalogue of equipment does not define a factory. Its functions, flows and dependencies do.
Before I design software, I ask what must be digital, what the user actually needs and which technical dependencies are necessary to deliver those functions.
Digital processing does not automatically require internet access. Remote observation does not automatically require remote control. The ability to exchange information does not mean every component should be allowed to receive commands. These differences are architectural, not cosmetic.
Consider industrial refrigeration. A supermarket may need to observe temperatures, operating states and alarms remotely. That is an information function. It does not follow that an external network needs permanent access to the controller that can change the refrigeration cycle.
I can separate the two. A dedicated telemetry system reports values through a physically isolated, one-way information path. The refrigeration controller itself has no permanently available remote communication interface. If a service operation or update genuinely requires access, an authorised person connects a dedicated terminal locally. That temporary connection is removed when the task is complete.
The required digital functions still exist. A permanent path for remote intervention does not.
The next question is what happens when a communication layer is compromised. Can someone read data, modify parameters, interrupt a process or change the physical state of equipment? The severity of those consequences determines the access architecture. In a critical system, adding more monitoring products is not a substitute for questioning whether the vulnerable connection should exist at all.
But software must also fit the person using it. A system can process data perfectly and still fail its intended users through unnecessary complexity, awkward workflows or interfaces that demand attention the user cannot spare. Functional correctness and human usability must both be designed.
Sometimes software controls other software; sometimes it coordinates physical equipment or organisational processes. I can design that logic down to states, interfaces, data flows, algorithms, failures and complete end-to-end behaviour when the function requires such precision.
The order does not change: function first, user next, technology last.
A company does not operate according to the lines on its organisation chart. It operates through people, machines, materials, decisions, information, responsibility and informal relationships that cut across those lines.
That is the system I need to reconstruct before deciding what should change.
An operator knows why a station stops. A maintenance technician knows which fault returns. A warehouse employee knows where the production plan stops matching reality. An administrator sees which decisions wait for information that nobody formally owns. Each account is incomplete on its own; connected together, they begin to reveal the operating architecture.
I construct that model as a graph while the information is arriving. I do not collect an assortment of notes and try to discover the relationships later. The relationships are the analysis. As I learn more, I add, correct and reorganise the model, moving between the company as a whole and the details that actually determine its behaviour.
Imagine a warehouse with deteriorating performance. Buying a warehouse management system or replacing equipment may look like an obvious response. Yet the actual cause may lie in production sequencing, which depends on late or inconsistent information originating in another part of the enterprise. Improving the warehouse in isolation can leave the cause untouched—or remove the buffer that was absorbing the disturbance.
Reconstruction is therefore not merely a search for weak departments. It establishes the functions the enterprise needs, the people who perform them, the relationships connecting them and the conditions under which they operate.
A target architecture follows the same discipline: function, user, then technology. Some problems require new machinery or software. Others require different responsibilities, shorter information paths, removal of unnecessary operations or a better use of what already exists.
There is no fixed level at which I must stop. If the enterprise needs detailed software architecture, a redesigned production process or the functional specification of a particular component, I go to that depth.
Optimising a dashboard is not optimising a company. The operating system underneath it has to change.
I do not regard the market as a fixed environment that can only be observed before a product is introduced. A product changes the market it enters. Its price, visibility, accessibility, design and relationship with competing offers can change what customers consider possible or desirable.
For that reason, I model the market while I design the product and its surrounding system. The purpose is to understand which interventions could generate a specific response, at what scale, with what probability and under what operating risk.
My automotive analyses approach that problem from different directions. In Volkswagen, I examined the growing distance between the advertised price of a mainstream car, the price of a genuinely useful configuration and the purchasing power of its natural customers. The product had not necessarily become worse. Its position relative to the market had changed.
With Fiat, I explored a different missing function: a familiar European brand with manufacturing and distribution resources, yet without a coherent model range for much of the ordinary family and middle market it could serve. In BMW, the opportunity moves in the opposite direction. When mainstream cars become expensive enough to approach premium prices, a premium brand can reconsider which customers are actually beyond its reach.
The analysis does not produce the same solution for all three. It produces an architecture suited to each situation.
Then the relationships begin to reinforce one another. Product variability affects manufacturing cost; cost affects pricing freedom; pricing changes the addressable market; demand changes production volume and supplier economics. Visibility changes perception, perception changes behaviour and behaviour changes future demand.
Consider corporate fleets. They generate sales, but also place cars into daily public life. Employees, suppliers, customers and competitors encounter those vehicles. Years later, the same cars enter the used market and reach another group of buyers. A decision about fleet penetration can therefore influence several market layers over time.
I model these dependencies and feedback loops to determine the scale required for a desired market response to become sufficiently probable—and the level of exposure at which the risk is acceptable. Human behaviour is not deterministic, so a probability model is not a promise of a guaranteed result.
The product must still fulfil its function and serve its user. Technology, distribution and marketing follow. The market is not simply where the finished product arrives; its behaviour is part of the architecture being designed.
A factory already contains several systems: production, transport, materials, maintenance, information, energy and control. An enterprise connects still more operational, digital, organisational and economic layers. A city, national infrastructure network or continental programme multiplies those relationships further.
System of Systems Architecture is the design and orchestration of that whole. The constituent systems may have different functions, internal logic, owners, constraints and operating conditions. Their individual correctness does not guarantee that the complete architecture will function.
In a greenfield city, housing changes transport demand. Transport determines access to work and services. Industry affects energy and logistics requirements. Water, emergency response and future expansion cannot be treated as afterthoughts to a drawing of buildings. Each layer needs its own appropriate architecture, but its design must also serve the larger system.
In continental energy architecture, generating sufficient electricity on paper is not enough. Production has to be matched with transmission, storage, reserve capacity, geographic distribution, operating states and coordination between national systems. A decision that improves one subsystem may worsen the conditions of several others.
The task is therefore not to connect everything to a central hub. It is to identify the required functions and define the boundaries, dependencies, interfaces, behaviours and responsibilities of the systems that realise them.
And the phrase 'the layer above' does not mean that I stop at the highest level of abstraction.
I descend as far into any subsystem as its architecture requires. If a software component must be specified end to end, I design its complete functional logic, modules, states, algorithms, interfaces, information flows and failure behaviour. Developers then implement the prescribed architecture; they are not expected to invent the system's operating logic for me.
The same applies to physical machinery, organisational processes and other disciplines. Some components need a functional specification. Others require a much deeper, complete design. The required depth is determined by the system, not by a job-title boundary.
Specialised engineers may execute the detailed work, but the architectural decisions and the coherence of the whole remain under one design authority.
The domains change. The scale changes. The required depth changes. The function remains the starting point.
NOTHING IS UNTOUCHABLE
Nothing is untouchable. Not the process. Not the machine. Not the technology. Not the assumptions on which the organisation was built.
A factory operates two assembly lines. Management reports 95% utilisation and 15% late deliveries. The production director proposes a third line.
My first question is not how much a third line costs.
What does 95% measure?
If someone divided 2,850 orders by a nominal capacity of 3,000 units, they calculated demand against a theoretical limit. They did not measure effective machine utilisation, operator activity, downtime, actual throughput or the capacity of the complete production system.
The report is not a diagnosis. The proposed investment is not an architecture.
I need to see the factory. What does it produce? How is every operation performed? Where are the tools? How does the operator move? How does the material arrive? Which activities can run simultaneously? Where does one operation force another to wait? What exactly determines the production takt?
Management can tell me what it believes is happening. I reconstruct what is actually happening.
Suppose the factory assembles industrial pumps on pallets carried by roller conveyors.
Why should the rollers survive the redesign?
The function is to move the pump, position it accurately and provide the correct access for assembly without disrupting the production rhythm. A roller conveyor is one way of delivering that function. It is not the definition of the function.
I can examine rotating pallets and redesigned workstations. I can also examine a suspended rail system. Suspension could change access to the pump, free floor space, simplify component delivery, allow a different pressing operation and alter the way the finished product is packed.
But I have not selected a suspended line.
I have not seen the actual equipment, measured the cycle, checked the loads or reconstructed the surrounding logistics. Both architectures remain hypotheses. So do other variants that may emerge during the analysis.
An existing solution has no right to survive simply because it already exists. A new solution has no right to be selected simply because it is interesting.
The function decides what the design must achieve. The system determines which solution belongs in it.
Take a workstation where an operator installs a shaft and bearing assembly.
I want to know where the shaft is stored, how it reaches the operator, which hand takes it, how the pump is positioned, where the press stands, how long the operator spends retrieving tools and what happens before the next unit arrives.
Those movements are not incidental details. They are part of the production architecture, and they consume measurable time.
One possible design is a purpose-built mobile workstation. Its tools remain within reach. When it returns to its zero position, a semi-automatic rack feeds the next shaft and bearings into dedicated slots. The components are ready before the next pump reaches the station.
The operator aligns the assembly. A fixture locks the carrier in position. A horizontal press performs the operation. The press retracts, the station moves clear, and the product continues.
That is a complete sequence of human movement, material availability, mechanical positioning and machine operation. I can design it down to the required fixtures and interfaces.
Or consider four screws fastening one component. Why should that necessarily mean four separate fastening movements?
A compact attachment with one input and four driven spindles is a possible alternative. Gear geometry, individual fastening requirements, positioning, torque control and verification have to be engineered correctly. None of that requires treating four manual movements as an immutable part of production.
If the attachment is available, I can use it. If it needs changing, I can redesign it. If it does not exist, it can be manufactured for the application.
The same applies to material-feeding racks, tools, lifting mechanisms, carrier fixtures and packaging equipment. The fact that an exact solution is missing from a supplier's catalogue is not an architectural constraint.
I do not propose that an operator should simply work faster. I remove work that the function never required.
Changing a workstation changes its component supply. Changing component supply changes replenishment. A different transport geometry changes access, maintenance, pedestrian movement and the use of floor space. A different carrier can change the assembly sequence and the packaging operation.
A finished pump might be lowered directly into its packaging instead of being lifted and handled again. A simple mechanical switch could direct finished boxes to several collection positions. Empty carriers could be advanced into place before the previous full load is removed.
Perhaps these functions should be performed mechanically. Perhaps by pneumatics. Perhaps a small dedicated controller is justified. Perhaps the existing equipment already does the job.
I have not decided. I am constructing and comparing possibilities while reconstructing their dependencies.
This is not a linear sequence in which I finish transport, then ergonomics, then logistics. I can visualise the workstation, its operator, the moving product, material routes and connected operations at the same time. I can rearrange the geometry mentally and immediately follow the consequences into other parts of the factory.
Each hypothesis reveals another part of the system. New measurements can eliminate a promising idea. Another observation can expose a better architecture.
A hypothesis is not a design decision. And a design decision is not justified by management's preference for familiar equipment.
The original two lines have a nominal takt of twelve minutes. With 900 available production minutes per line per day and twenty production days per month, their combined nominal capacity is 3,000 pumps.
Now consider a redesigned production architecture that can sustain a nine-minute takt under those same operating assumptions.
Two lines. Same number of operators per line. Same planned operating hours. 4,000 pumps per month instead of 3,000.
That is a 33.3% increase in nominal productive capability.
At a reference price of €500 per pump, the additional 12,000 units of annual capability correspond to €6 million of potential sales value. That number describes the capability made available by the design. It is not a prediction of sales, profit or realised savings.
Whether the company sells every unit is a commercial decision. It could also use the increased capability to shorten shifts, reduce overtime, release capacity for other products or postpone expansion. My architectural work is priced for what I design and make possible, not for management's subsequent decisions about how much of it to use.
Now comes the part a simple third-line comparison misses.
Rebuilding the existing two lines may cost considerably more than installing a third conventional line. That can still be the correct architectural decision.
A third line built to the old design replicates the old production model. A reconstructed line establishes a new standard.
At 1,500 pumps per month per conventional line, three lines provide 4,500. At 2,000 pumps per month per redesigned line, three provide 6,000. Four redesigned lines provide 8,000. Every expansion inherits the improved workstation geometry, material supply, internal logistics, tooling, operating logic and productive capability.
The initial investment changes the economics of every line the company builds afterwards.
That is why I do not impose an arbitrary reconstruction budget equal to the price of another conventional production line. I evaluate the architecture across its operating life, future replication and the capabilities it establishes for the whole enterprise.
And the production line is only one part of the analysis. Procurement, planning, warehousing, quality, maintenance, information systems, labour organisation, physical infrastructure and commercial conditions remain connected to the result.
I am not selling a small local efficiency improvement. I am designing the production architecture the business can operate and replicate for years.
The same reasoning applies outside factories.
In software, I start by identifying which functions must be digital, what users need, which connections are necessary and what happens if an access layer is compromised. Remote observation does not automatically require remote control. A function that needs occasional maintenance access does not automatically justify a permanent network connection.
In enterprise architecture, a warehouse problem may originate in production planning, which may originate in information flow or an inherited organisational dependency. I do not redesign the warehouse until I understand the system causing its condition.
In market architecture, I examine and model not just existing demand but how product, price, exposure, scale and behaviour interact — including the conditions that make a desired response more likely.
At Systems-of-Systems scale, the work extends across organisations, infrastructures and technical disciplines. That does not mean I stay at the top.
If the necessary design requires the complete end-to-end logic of one software system, I can specify its functional behaviour, modules, algorithms, states, transitions, interfaces, data flows and failure conditions. Programmers implement the designed logic; they are not handed an undefined system to invent.
If a physical operation requires a custom device, I can design its functional geometry, mechanical sequence, constraints and integration with the surrounding equipment. The engineering depth follows the function. It does not stop at an artificial boundary imposed by a job title.
Implementation remains a separate responsibility unless I am explicitly engaged to direct it with the authority that responsibility requires. A completed architecture is a deliverable in its own right.
I do not treat existing processes as sacred because they have operated for twenty years. I do not select software because it is fashionable. I do not accept a management report as proof of the cause behind a reported problem. And I do not accept the catalogue of available equipment as the boundary of what can be engineered.
That does not mean replacing everything.
I preserve what performs its function properly. I adapt what can be improved. I remove dependencies that have no legitimate purpose. I design the missing capability when nothing available satisfies the requirement.
I may leave a machine untouched. I may redesign the operator's workstation. I may design a new production line, a complete software architecture or an enterprise-wide operating system.
The choice comes after the system has been understood.
Function first. The human being who must use the system. Then the architecture and the technology required to make it work.
Nothing is untouchable. Everything must justify its function.
THE BOUNDARY IS NOT THE SYSTEM
The divisions we use to organise reality are not the boundaries of reality itself.
A company has departments. A university has disciplines. Industries have names. Technologies have classifications. Organisations divide budgets, assign responsibility and establish where one person's job ends and another's begins.
Those divisions are useful. Without them, enormous parts of our world would be difficult to organise.
The problem begins when we mistake them for the boundaries of the system.
A project misses a deadline. A factory stops. A customer leaves. A department reports poor performance.
We tend to begin our analysis where the problem becomes visible. But the event may be only the final expression of an architecture that was forming long before anybody noticed the consequence.
A delayed project may have originated in the way responsibility was divided. A production failure may have begun in purchasing, planning or information flow. A lost customer may be the predictable result of decisions that individually looked reasonable.
The event is real. It is not necessarily the cause.
I do not begin by assuming that the visible failure identifies the part of the system that needs changing. I follow the dependencies backwards until the structure producing the result becomes intelligible.
That is the first change of perspective: from reacting to an output to understanding what produces it.
An organisational chart tells us who reports to whom. It does not tell us how a business actually operates.
A real operating system exists in the movement of materials, decisions, people, information, money and responsibility. A warehouse depends on production. Production depends on planning. Planning depends on information, and information may depend on human behaviour that the software never recorded.
The system lives in those relationships.
To reconstruct a company, I have to identify what happens, not merely what the process manual says should happen. I need to understand where decisions originate, what people do to make the work possible, which informal arrangements are holding the organisation together and where a change will produce consequences elsewhere.
An apparently small intervention can therefore require a broad reconstruction. The scope of understanding follows dependencies; the scope of change follows what that understanding reveals.
The result is a map of operating reality, not a polished picture of the organisation's preferred description of itself.
A dashboard can show excellent figures while concealing a fragile system.
A department may meet every target by transferring its costs and delays to another. Capacity can look sufficient in a monthly average while failing at the precise moment when the system needs it. A duplicated device can appear redundant while relying on the same power supply, control logic or unavailable operator.
Local performance does not establish global coherence.
Architecture accumulates through decisions. Some are deliberate; others are temporary workarounds that become permanent because they seem to work. Over time, the organisation begins to depend on arrangements nobody would have consciously designed as one complete system.
Then something changes. Demand rises. A supplier fails. A key person is absent. A connection disappears.
Only then does the system expose dependencies that were always there.
A system should be understood not only by how it performs when everything works, but by what happens when something does not.
The next mistake is beginning with a solution.
An organisation asks which software to buy, which machine to install or which department to create before it has established the function that actually needs to exist.
I reverse that sequence.
What must the system achieve? Under which conditions? For whom? With which constraints? How will we know that the function has been fulfilled? What has to happen before and after it?
Only then does technology enter the conversation.
An existing product may meet the requirements perfectly. It may need modification. The right answer may involve fewer systems, a different process, a physical mechanism or an entirely new component.
Availability in a supplier's catalogue is not a definition of what is possible. Equally, novelty is not an argument for replacing something that already performs its function.
The mission establishes the function. The function determines the architecture. Technology serves the architecture.
Seeing a missing function is not the same as designing the system that will deliver it.
An idea can be valuable. A concept can be the correct product when a concept is what was commissioned. But a complete architecture must resolve the relationships that allow the intended result to exist in reality.
The product itself may be only one visible component. Around it are production, logistics, software, interfaces, financing, service, user behaviour, legal conditions and the operating structure required to sustain it.
Which of those layers matters depends on the system. Their design cannot be replaced with boxes carrying reassuring labels.
If a required function involves software, its operational logic must be defined. If it requires a device, its mechanical and functional relationships must be designed to the necessary depth. If it depends on people, their actual behaviour and limitations are part of the architecture.
This does not mean that the architect personally manufactures every component or executes every activity. It means the architecture must not leave its essential decisions for the implementer to invent.
A dependency does not stop because it crosses a departmental budget, a company boundary or a national frontier.
A digital product may depend on industrial capacity. Industrial capacity may depend on energy, maintenance, workforce availability and transport. A technically successful system may fail because the organisation designed to operate it cannot make the necessary decisions.
The relevant boundary is where the function and its dependencies lead, not where an industry convention tells the analysis to stop.
This is not an argument against specialists. Their knowledge is indispensable. An operator may understand a workstation more deeply than anyone examining the complete enterprise. A maintenance technician knows failure modes that a diagram cannot reveal.
The architectural function is not to pretend to replace that knowledge. It is to recognise its significance, connect it to other knowledge and preserve the coherence of the whole.
And responsibility matters. A person cannot reasonably be held accountable for an implemented result without authority over the decisions and conditions that determine it. Designing an architecture and directing its implementation are distinct engagements.
The Layer Above is not another management tier. It is not a position from which details disappear, and it is not simply the ability to speak about many different subjects.
It is the perspective from which apparently separate systems can be recognised through their real functional relationships.
That perspective has to work in both directions. I must move far enough away from the visible event to see the architecture producing it. Then I must be able to descend into the physical operation, software function, decision, cable, tool or human action that makes the architecture real.
Scale changes the material of the problem, not the fundamental need to understand relationships. A product, a business, a city, an energy network or a continent can each be examined as a system of functions, constraints, resources, decisions and time.
This does not make complexity disappear. It does not make every outcome predictable, remove uncertainty or make specialist expertise unnecessary.
It changes the questions we are able to ask — and therefore the decisions we are able to design.
Once the architecture becomes visible, we can stop repairing isolated consequences and begin changing the system that produces them.
The divisions remain useful. The architecture exists across them.
THE ARCHITECT IS REAL. HE IS JUST NOT THE WHOLE STORY.
I take my work seriously. Myself? Considerably less.
After eleven terminals about architecture, systems and the way I think, you might reasonably expect a rather solemn man. Someone who spends his evenings contemplating diagrams, who speaks only in carefully structured paragraphs, and who regards a spontaneous joke as a failure of governance.
The diagrams are real. The solemn man is not.
I love the act of designing. But I also love photography, singing, performance, absurd humour, and the rather wonderful moment when an entire room stops knowing what to expect from me.
None of these interests is a recreational disguise worn by an architect after working hours. They are not separate characters, and I do not switch from one person to another. I am all of them, sometimes within the space of a single afternoon.
My mind rarely stops working. I see dependencies, contradictions, missing pieces, unexpected relationships and possibilities almost everywhere. A problem in one field can remind me of a mechanism from an entirely different one. I do not particularly care where the academic borders have been drawn. If the relationships are there, I want to understand them.
For me, architecture is not simply a profession or a particular kind of document. It is a way of thinking and, more importantly, something I genuinely enjoy doing. There is enormous pleasure in taking a complicated, apparently incoherent whole and discovering that it can be understood, reconstructed and made to work.
I know that my intellectual abilities are exceptional. I do not find it useful to pretend otherwise for the sake of appearing modest. I also know that unusual abilities do not magically remove the effort involved in creating something substantial. Being able to see an architecture does not mean it will design, validate and document itself.
There is another consequence to the way I think: I have a remarkably poor relationship with questions that demand a simple answer where none exists.
What is the best solution? Which car is better? What music do I prefer? Is that approach right?
It depends.
I realise how irritating that can be. Unfortunately, reality has never shown much interest in making its answers convenient.
People sometimes mistake professional precision for conventional corporate behaviour. I have very little interest in the latter.
I can discuss an architecture with absolute seriousness and explain an organisational failure using language that would never survive a communications department. I have described businesses whose dashboards are no longer green because, apparently, the dashboards have turned golden. I have written about executives drinking champagne paid for with money borrowed from the future.
That is not decorative sarcasm. It is how I sometimes express the absurdity of a situation more accurately than a polished paragraph of management vocabulary ever could.
And when somebody tries to turn a professional discussion into a contest of status, I am entirely capable of saying something like:
“Oh, I know you want to prove you have bigger balls than me. No worries. You definitely have bigger balls than me. Now, can we get back to work?”
It tends to make the point.
I am not a conventional corporate employee, and I am not a consultant who arrives to perform corporate etiquette. I am an architect. I have my own judgement, my own expertise, and a responsibility to the quality of the architecture I create. None of those things improves because I choose my words to protect somebody else's ego.
I have been a company director myself. I know perfectly well that hierarchy exists for a reason. When I am responsible for an organisation, someone must make decisions, assign responsibility and hold people accountable. If I am the boss, I am the boss.
But a client's chief executive is not my boss. They represent an organisation that wants to use my capabilities. I am there as an independent professional, not as another rung in their reporting structure. We can disagree. We can speak directly. We can even laugh. None of that prevents us from doing serious work.
I sometimes joke that my employees are welcome to dislike me, or even call me an arsehole, provided they do their jobs properly. The joke contains a very real distinction: professional roles and personal reverence are not the same thing.
I respect responsibility. I do not worship titles.
I should probably admit at this point that my sense of proportion does not always apply to humour.
One day, I want a home near the Tatras: a rather private building with a dark exterior, carefully controlled light and very little desire to announce itself to the road. Quiet. Restrained. Almost hidden.
And beside the garage, I intend to put a monumental, illuminated Archestral Studio emblem. Not a tasteful little plaque. Something several metres high, glowing electric cyan, gloriously and entirely unnecessarily conspicuous.
I originally encountered the idea while looking at an illustration that was completely unsuitable for the professional design we were working on. It made me laugh. Then I realised I genuinely wanted to build it.
Yes, I know how ridiculous that sounds.
That is precisely why I like it.
I am a sauna master. And a sauna, it turns out, can be an excellent theatre.
There is music, heat, movement, ritual, a room full of people and the opportunity to tell a story without the slightest need for a PowerPoint presentation. I love creating performances in which the ridiculous and the serious can coexist.
One of my creations is Padre Mateo.
Picture a man entering in a clerical collar and greeting the room with a hearty, rather suspiciously cheerful, “Good evening, my dear children.” There are church bells. There is electronic music, including a techno interpretation of a prayer. There is an absurdly ornate blue chalice, complete with a dragon, which looks as though it was borrowed from a particularly extravagant fantasy series. At one point, an ice sphere receives a degree of ceremonial reverence that it has done absolutely nothing to deserve.
It is deliberately excessive. That is the fun of it.
But there is another version: a three-act performance I call The Service of Burning Away Sins in a Foretaste of Hellfire.
First comes Padre Mateo, complete with his theatrical ceremony and irreverent humour. Then the bells ring again, and the priest disappears. In his place arrives the devil: horns, beard, a much more intense atmosphere, and the promise that he will return for the audience.
Afterwards comes the final act. No priest. No devil. No spectacular costume. I return as myself, with an ordinary sauna fan and quiet music.
And I ask the people in front of me to look at one another.
Here they are, without their job titles, their bank balances, their cars, their expensive possessions or the usual symbols of status. Just human beings, sitting together. Does anyone genuinely believe that they are worth more as a person than somebody else in that room?
I do not give them a speech about the answer. I continue the gentle movement of the fan until the music ends, put it down and walk out without another word.
I love the joke. I love the performance. I also love the silence that can follow it.
Theatre lets me express things that I cannot always communicate as completely through ordinary conversation. Sound, movement, timing, humour, costume, heat and silence can say something together that no individual sentence could quite contain.
Photography gives me another kind of theatre, but its most important element is not the camera.
It is the relationship with the person in front of it.
I talk. I joke. I observe. I get to know people, and I let them get to know me. Sometimes I spend so much time building a comfortable relationship that the camera eventually becomes almost irrelevant to the person I am photographing. They stop managing every expression. Something genuine appears.
I enjoy catching an unrepeatable moment: a child's expression while playing, somebody laughing without thinking about how they look, a gesture that lasts a fraction of a second. I also enjoy the opposite extreme — an elaborate scene planned down to its visual relationships and then created in the physical world for a real photograph.
I do not want to manufacture the important parts afterwards. I care about what was truly in front of the lens: the light, the person, the moment, the scene. The technical craft exists to capture it, not to replace it.
There is a photograph I want to make one day that probably explains the other side of my imagination rather well.
An enormous full moon. Black wings. Smoke. Fire tracing something close to a cross across the composition. The image must overwhelm the viewer at first glance. I want the initial response to be nothing more sophisticated than wow.
Only on a second or third look should another image emerge from within that spectacle: a woman, completely naked, with a genuinely plus-size body. Wide hips, full thighs, cellulite, tattoos, perhaps a scar from a caesarean birth. Not a digitally perfected body. A real woman with a real history.
The flames may obscure parts of her body. They are allowed to dominate the first impression. The woman is not a detail accidentally left in the background, though. She is the discovery waiting inside the spectacle.
And the decisive work will happen before the photograph is taken.
I want to know the model well enough for her to feel at ease with me and my camera. The rest of the crew will be women. The scene itself will be made physically, with professionals responsible for its effects. But what I most want to create cannot be supplied by a technician or added in editing.
I want the woman to stand there feeling beautiful, proud and entirely herself. Not acting confident. Not imitating some prescribed idea of beauty. Actually feeling it.
I know I can affect the way people see themselves. There is a particular pride in seeing somebody stand taller, smile differently or recognise something worthwhile in their own reflection. That is one of the things I love most about photographing people.
The final picture matters enormously. So does what happens to the person while we make it.
I sing. Properly. I am a baritone, and singing is not a passing hobby I mention because it sounds good in a biography.
I enjoy the craft: phrasing, control, breathing, shaping a piece of music so that it becomes a performance rather than a sequence of correctly produced notes. I also enjoy what happens once the technique is no longer the thing anybody notices.
My repertoire can move from Frank Sinatra, Dean Martin and Michael Bublé to Andrea Bocelli, songs from musical theatre, rock, and whatever else speaks to me. Then I might happily spend the evening listening to techno with an indecent amount of bass.
People occasionally expect such preferences to fit neatly into one coherent category. They do not. I have never understood why they should.
For me, music is not a list of genres I have agreed to support. It is a collection of different possibilities for expression. Sometimes I want elegance. Sometimes power. Sometimes warmth. Sometimes I just want the bass to shake something.
I have performed for people and recorded my own singing. At times I have seriously wondered whether I should pursue it much further.
I still might.
There is something slightly paradoxical about how much time I have spent learning to understand other people.
I am autistic. My mind works differently, and parts of the social and emotional world that many people seem to navigate instinctively have required deliberate study from me. I have had to examine human behaviour, motivation, reactions and psychological mechanisms with considerable care.
Over time, that conscious learning became a strength of its own.
I can be very good at reading another person's behaviour and recognising what may lie behind it. I notice patterns, contradictions, insecurities and possibilities. I can often see when a person's difficulty is not the absence of ability but the circumstances in which they are trying to use it.
I do not need to experience somebody else's emotions in exactly the way they do in order to understand what may be happening. Understanding a person's psychological processes and emotionally sharing their experience are not identical things.
None of this turns human beings into equations, and it certainly does not mean I am infallible. People are complicated. That is part of what makes understanding them interesting.
It also means that my work with people is not limited to analysing them. I am interested in what changes when somebody begins to see themselves differently.
I know I can influence people. I can teach, challenge, insist, provoke and sometimes push much harder than they expected. I am not always gentle, and I have never believed that constant reassurance is the only way to help somebody grow.
I have seen people develop abilities they once doubted they possessed. Sometimes that involves practical skills or professional judgement. Sometimes it involves the more difficult task of recognising that they are not as incapable as they have been taught to think.
I take pride in being able to recognise potential and help turn it into something concrete. It is not about collecting grateful people or having somebody admire me. The genuinely satisfying moment is when they discover that they can do something they previously believed was beyond them.
A woman feeling beautiful in front of a camera. Somebody realising that a complicated task is within their reach. A person whose assessment of their own capabilities finally begins to change.
These moments may look very different. They mean a great deal to me for much the same reason.
And I am perfectly comfortable saying that I am proud of my ability to contribute to them.
I do not believe that everyone has the same abilities. We do not. Some people can do things that others cannot, and pretending otherwise helps nobody. I know that my own intellectual profile is unusually strong, and I have no intention of apologising for recognising it.
But intelligence is not human worth.
A job title is not human worth. Neither is a bank balance, a car, a reputation or the ability to solve a problem more quickly than somebody else.
I can be the most intelligent person in a room and still be only one person among others. A chief executive can hold more organisational authority than an employee without being a more valuable human being. A person who thinks very differently from me has exactly the same claim to dignity.
Maybe this is why I like the final act of Padre Mateo so much. After the costumes, music, devil, jokes and heat, the question left in the sauna is wonderfully simple. What remains when we stop confusing status with the person?
I spend a great deal of my life building architectures, but I am not an architecture. I sing. I photograph. I make ridiculous jokes. I can be direct to the point of discomfort. I perform an outrageously theatrical parody of a religious service. I like seeing people discover their own possibilities. I plan to install a completely disproportionate neon emblem outside a very discreet house.
I contain all those things without needing them to make me consistent in somebody else's eyes.
The architect is real.
He is just not the whole story.
I am a genius. I am also human.
— Mateusz Chrzanowski