Functional programming: tailored usage-constraint trade-offs

Any functional programming reveals structural tensions that the Kytom method resolves consciously rather than by default.

• Flexibility versus density: a modular floor plate consumes more surface area than a fixed one, due to clearances, removable partitions and oversized networks. The surface-area cost overrun must be arbitrated explicitly during the programme phase.
• Collaboration versus concentration: open configurations encourage informal exchanges but can weigh on individual productivity for cognitive tasks, particularly because of perceived noise in open-plan areas.
• Accessibility for people with reduced mobility versus flow optimisation: compliance with the regulatory obligations applicable to workplaces and universal pathways mechanically lengthens circulation routes; this impact must be integrated from the master plan stage.
• Scalability versus immediate performance: anticipating several business transformations over ten years requires oversized technical grids whose initial cost must be weighed against future reconfiguration savings.

Each trade-off is documented in the programme with a measurable criterion: m² per workstation ratio, target acoustic level (NF S 31-080:2006, « standard » level at 40 dB), targeted occupancy rate. This traceability allows the project owner to validate each compromise with its own business indicators.

Our reading diverges from the industry consensus on flexibility. The « flex office everywhere » doctrine underestimates a fact our sensor measurements confirm: beyond a high pooling threshold, the technical cost overrun (networks, zoned HVAC, dedicated furniture) exceeds the surface-area savings, and the effective occupancy rate plateaus well below commercial assumptions. On the Kytom floor plates audited, the sweet spot sits around 1.1 workstations per 1 employee, not below. Maximum flexibility is not the economic optimum, it is a sales argument.

When this trade-off framework does not apply. On small floor plates (under 250 m², limited team), the flexibility/density trade-off becomes theoretical: configuration variability is illusory for a homogeneous team, and the cost overrun of removable partitions is never recouped. On R&D sites constrained by processes (laboratories, clean rooms, data centres), it is the technical programme that dictates the grid, not human usage.

For the CFO and the Asset Manager: what programming does to cash flow and asset value

Functional programming is rarely presented as a financial lever, even though it is more of one than works negotiation. Three mechanisms demonstrate this.

Rent avoided through controlled density. On an office headquarters at 450 EUR/m²/year excl. tax in the Paris CBD zone, saving 8% of usable surface area on 3,000 m² thanks to a calibrated programme represents 108,000 EUR/year of avoided rent, or 540,000 EUR over the term of a firm 3/6/9 lease. The cost of a Kytom programming mission is recouped in less than a year.

OPEX controlled over 5 years. A programme that ignores operating constraints generates significant OPEX overruns: forced HVAC reconfigurations, multiplied maintenance contracts, non-standardised consumables. On an operating budget of 80 EUR/m²/year, that is 12 EUR/m²/year, or 36,000 EUR/year on 3,000 m².

Asset value at refinancing. For the Asset Manager, an office asset programmed for modularity supports two to three reconfigurations over the holding period without structural works. On the headquarters we have reconfigured several times, the cumulative cost of reconfigurations remains significantly lower than that of an asset not programmed from the outset. This difference is reflected in the DCF at the time of disposal.

For the office sector decision-maker, the question is not « how much does programming cost » but « how much does its absence cost ». On the non-programmed projects in our comparison sample, the cumulative 5-year CAPEX + OPEX gap represents a substantial share of the initial budget. The French tertiary decree and its 2030/2040/2050 obligations reinforce this challenge: a programme that does not incorporate the energy trajectory imposes heavy remediation works mid-lease.

Programme and specifications: the initial confusion, leading cause of dysfunction

A recurring error consists in merging the functional programme and the technical specifications. The programme describes the target usage (who does what, with whom, under what conditions); the specifications then translate these usages into measurable technical requirements. On the recovery projects we have audited, a significant share of dysfunctions at delivery stems from this initial confusion between programme and specifications.

Second pitfall: underestimating interfaces. Transition zones (reception, circulations, storage, technical rooms) represent a significant share of gross usable surface areas, often between a quarter and a third, but are treated as an adjustment variable.

Third pitfall: ignoring operating constraints. A theoretically modular open space may be locked in by HVAC networks, zoned lighting or maintenance contracts.

Three recurring errors structure these failures: confusing programme and specifications, underestimating technical interfaces, and ignoring operating constraints. Each generates costly remediation during the works phase or in OPEX. The Kytom safeguard consists of a function/constraint compatibility matrix tested on a 3D model with the operators. This cross-validation avoids, across the monitored portfolio, a large share of the adaptations usually endured during the works phase.

When separating the programme and the technical specifications is not a priority. On light refurbishment operations (under 500 m², no structural modification), the formal separation of the two deliverables weighs down the mission without measurable gain: a condensed usage brief is enough. The programme/specifications formalism becomes relevant beyond 1,000 m² or when multi-year operating stakes are present.