Inheriting a legacy information system is the same ethical situation as inheriting a damaged painting: you must choose between an impossible return to the original state, a deliberate decision to stabilize without touching, or a visible, documented, reversible intervention. Art restorers formalized this choice sixty years ago. Most executives make it by accident, without knowing they are making it. The mature move is not to rebuild. It is to pick one of the three postures consciously, and to own it.
A Damaged Painting and a Legacy System Pose the Same Question
The question a restorer faces in front of a darkened canvas is not technical, it is moral: what am I allowed to change in something that was entrusted to me?
I did not expect to find the clearest framework for legacy IT decisions in an art conservation studio. But watch what happens when a seventeenth-century painting arrives on the easel. The varnish has gone amber. Paint lifts at the edges. There is a loss, a lacuna, in the lower corner. The owner wants it back “like new.”
The restorer hears that sentence the way I hear a board member say “let’s just rebuild the whole thing.” With professional patience, and a firm intention to do no such thing.
Because the restorer knows there are exactly three honest answers. Return the work to its original state: seductive, and destructive, since that state no longer exists anywhere except in imagination. Stabilize the work without intervening: control the environment, stop the decay, touch nothing. Or intervene while leaving the intervention visible: fill the lacuna with a technique a trained eye can identify, document every gesture, use materials a future restorer can remove.
Three postures. No fourth. Every legacy system decision I have reviewed in the last decade falls into one of these, or fails because it pretended a fourth existed.
The Original State Is a Myth That Destroys What It Touches
The first posture, returning to the original, is the one that ruins both paintings and companies, because the original state is a reconstruction, not a destination.
In conservation, this is settled doctrine. Strip a painting back to what you believe was its first appearance and you must scrape away layers that became part of the work: the artist’s own later revisions, historic retouches, the surface chemistry of centuries. You do not recover the original. You manufacture a clean forgery of your own assumptions.
The corporate equivalent is the full rebuild fantasy. The system is old, therefore the system must be remade, this time properly, the way it should have been built from the start. I have sat in meetings where this was presented as obvious hygiene. It rests on the same illusion as the over-cleaned canvas: that somewhere beneath the accumulated layers there is a pure design waiting to be liberated.
There is not. The accumulated layers are the system. Twenty years of pricing exceptions, regulatory adaptations, client-specific workflows, integrations born from acquisitions: this is not dirt on top of the system, this is the institution’s memory written in executable form. A rebuild does not liberate the design. It discards the memory and keeps the assumptions of whoever wrote the migration spec, who typically arrived eight months ago.
Notice also who proposes the return to origin. In conservation history, the great over-cleanings were rarely demanded by the people who lived with the works. They were sold by intervening parties with something to gain from the gesture: prestige, a signature campaign, a budget. The pattern transposes intact. The rebuild is almost never requested by the operations teams who run the system daily and know where its bodies are buried. It arrives from outside, packaged with a deck, priced with optimism, and timed to a sponsor’s tenure rather than to the system’s actual condition.
Some of that memory deserves to go. Plenty of it is genuine grime. The point is not that everything old is sacred. The point is that “back to original” is never the real choice on the table. The real choice is always between the two remaining postures.
Preventive Conservation Acts on the Environment, Not the Work
The second posture has a name in museums, preventive conservation, and it is the most underrated decision available to a non-technical CEO.
Museums learned long ago that the cheapest way to save a collection is to never let it need saving. Humidity control, stable temperature, filtered light, vibration management. The work itself is not touched. Its environment is engineered so that decay slows to a crawl. The Venice Charter of 1964, the founding international text of modern conservation, made permanent maintenance the first duty owed to a monument, before any restoration gesture.
Translate that to an information system and you get a program nobody brags about at conferences: tested backups, patched dependencies, revoked accesses, monitored performance, documented interfaces, contracts that do not silently expire. None of it changes the system. All of it changes how fast the system degrades.
Here is what I keep observing in mid-sized companies: the environment work is skipped precisely because it is invisible. A CEO under pressure wants to announce something. “We are rebuilding our platform” is an announcement. “We now test our backups weekly” is not. So capital flows to interventions while the environment drifts, and the drift quietly creates the emergency that will later justify a panicked rebuild.
Choosing preventive conservation is not refusing to decide. It is a dated, signed, active decision: this system stays as it is, and we spend our money making sure it stops getting worse while we figure out what it actually contains. For a company in M&A uncertainty, in leadership transition, or simply without the cash for a safe intervention, it is frequently the only adult choice available. It deserves to be presented to boards as a strategy, not as an absence of one.
Brandi and the Venice Charter Wrote the Rules Executives Are Missing
The third posture, intervening without erasing, was codified with a precision that puts most IT governance documents to shame, and the two founding texts are worth naming.
Cesare Brandi, first director of Rome’s Istituto Centrale per il Restauro, published Teoria del restauro in 1963. His theory holds restoration in tension between two demands that he refused to collapse into one: the aesthetic instance, the work as a thing of beauty that must remain readable as a whole, and the historical instance, the work as a document of everything that happened to it. A restoration that sacrifices either is a failure. From this tension he derived practical consequences: interventions must aim at the potential unity of the work without faking completeness, must remain recognizable on close inspection, and must stay reversible so that future knowledge can undo present error. The Italian school built on his thinking even institutionalized a technique, tratteggio, where losses are filled with fine parallel strokes: invisible at viewing distance, unmistakable up close. The repair participates in the whole and never lies about being a repair.
One year later, the Venice Charter brought the same discipline to architecture and made it international law of the profession. Its restoration articles read like a checklist I wish every CTO transition plan had to satisfy. Restoration stops where conjecture begins. Replacements must integrate harmoniously yet remain distinguishable from the original, so the restoration does not falsify the evidence. The valid contributions of all periods must be respected, because unity of style is not the aim. And every campaign of work must produce precise documentation, archived and published.
Now reread those principles as a system owner. Do not rewrite what you do not understand: stop where conjecture begins. Make every change traceable and visibly distinct from the inherited behavior: distinguishable, documented. Do not flatten the layers added by previous eras of the company in the name of stylistic purity: respect the contributions of all periods. Keep a record a successor can audit: publish the report.
Sixty years ago, a profession that handles irreplaceable objects concluded that the ethical intervention is visible, humble, documented and reversible. The software industry, which handles objects that are merely expensive, still mostly ships the opposite.
The Pentimento Always Resurfaces
Painters themselves left us the proof that buried decisions do not stay buried: conservators call it the pentimento.
The word comes from the Italian for repentance. A pentimento is a change the artist made during the painting: a repositioned arm, a hat brim moved, a figure painted over. The revision is hidden under the final layer, and for decades it stays hidden. Then the covering paint grows transparent with age, or an X-ray sweeps the panel, and the first gesture comes back, a ghost under the composition. The National Gallery’s glossary notes that these ghosts are precious: they reveal how the work was actually made, and help establish what is original.
Every information system of respectable age is full of pentimenti. The ERP rollout that stopped at sixty percent. The module built for a flagship client who left. The half-finished migration whose two halves still run side by side, reconciled nightly by a script one person understands. Each abandoned decision was painted over, not removed. And like their pictorial cousins, they resurface at the worst archaeological moments: under load, during an audit, in the data room of a due diligence.
You can read this as a horror story. Restorers read it the other way: pentimenti are evidence, and evidence is an asset if you find it before it finds you. A serious assessment of a legacy system is exactly this kind of imaging work, X-raying the layers before deciding which posture to adopt. The companies that get into trouble are not the ones with pentimenti, which is to say all of them. They are the ones that commission a rebuild without ever putting the canvas under the lamp.
A Luxury House Taught Me What Harmonizing Without Erasing Looks Like
The longest lesson I received in applied conservation did not happen in a museum, it happened inside one of the great French luxury groups, on a harmonization program whose name I will keep to myself: the mechanics matter here, not the logo.
The setting, simplified: a group whose subsidiaries had each grown their own systems, their own data habits, their own operational gestures. Years of autonomy had produced exactly what you would expect, richness and divergence in the same proportions. The group needed common ground: shared standards, interoperable data, processes that could be read across entities.
The obvious playbook exists, and every large integrator will sell it to you by the kilo: define the single target model, declare every local variation a deviation, migrate everyone onto the standard, celebrate the decommissioning count. It is the restoration equivalent of stripping every canvas in the collection back to the same bright white ground. Clean, uniform, and a massacre.
What made this program a formative experience is that it made the other choice, deliberately. The work started not with a target architecture but with something closer to a conservator’s condition report: understanding, entity by entity, what each local system actually encoded. Some divergences turned out to be accidents of history, tooling chosen because a vendor happened to call that year. Those could be harmonized without loss, the grime of the piece. Other divergences encoded the way a specific métier actually worked, constraints of a craft, of a market, of a client relationship that the local system had absorbed over years. Erase those and you would not be cleaning the subsidiary, you would be amputating it.
So the program drew the line the way Brandi drew it: harmonize what carries no identity, preserve what does, and make the interventions reversible wherever the knowledge was incomplete. Standards were introduced as layers the entities adopted, not as solvents poured over their existing operations. Where a subsidiary’s specificity was real, the standard bent around it, and the bend was documented as a conscious decision rather than hidden as a guilty exception. The intervention stayed visible: anyone reading the program’s records could tell what had been changed, what had been kept, and why.
Two things struck me from the executive side of that program. First, the discipline was harder to sell internally than a clean-slate plan would have been, because its success looked undramatic: nothing collapsed, nothing flashy got inaugurated, the singularities were still there, now legible and connected instead of opaque and isolated. Preventive conservation never photographs well. Second, the discipline aged remarkably. Decisions that bent the standard around a real specificity did not come back as regrets. The few places where uniformity had been forced for elegance were precisely where friction kept resurfacing, pentimenti of the program itself, reminders that what you paint over does not disappear.
I left with a conviction that has since survived contact with much smaller companies: the quality of a harmonization is not measured by how uniform the result is. It is measured by whether the people closest to the work still recognize their craft in the system afterwards. Uniformity is cheap to specify and brutal to live with. Legibility is the actual prize.
The CEO’s Job Is to Choose the Posture, Not to Hold the Brush
You inherited a system you did not build, the way a museum inherits a collection it did not paint, and nobody expects the museum director to retouch canvases.
What the institution does expect from its director is the ethical choice: which works get stabilized, which get restored, what the house rules of intervention are, and the budget honesty that goes with each. That is precisely the part of the legacy IT decision that cannot be delegated to vendors, because every vendor at your table earns money on exactly one of the three postures and will argue for it with conviction.
This is also why the choice has to be explicit and written down. An implicit posture is not a posture, it is a drift. The company that never formally chose conservation still practices it, badly: no environment work, no condition report, just neglect wearing the costume of prudence. The company that never formally chose intervention still intervenes, badly: a hundred undocumented patches a year, each invisible, each irreversible, none signed. The three postures exist whether or not you choose one. The only variable under your control is whether the posture was decided, by you, with the costs in front of you, or inherited from a thousand small defaults nobody owns.
What Remains When the Varnish Settles
The restorer’s ethic compresses into questions a non-technical executive can ask without writing a line of code, and they are sturdier than most steering committees.
Before any intervention on the system you inherited: do we know what is varnish and what is paint, which layers are grime and which are memory? Has anyone put the canvas under the lamp, or are we deciding on the basis of the frame? Is the proposed change reversible, and if not, who signed the sentence that says we accept never coming back? Will the intervention stay visible, documented, distinguishable, or will the next leadership team find our choices disguised as original architecture? And the question that the whole market is built to keep you from asking: is the right move, this year, to touch the work at all, or to fix the thermostat and watch it stop degrading?
On vous a dit qu’un SI vieux se refait, as I keep hearing in French boardrooms: an old system gets rebuilt, everyone knows that. The best restorers know something else. They know when not to intervene, and when intervening, how to do it without erasing the very thing they were hired to save. The maturity of a CEO in front of a legacy system is the same maturity, transposed: not mastering the brush, but owning the choice of posture, consciously, in writing, with its costs on the table.
The painting does not need you to be a painter. It needs you to decide, and to leave a trace of having decided.
Sources
- ICOMOS, International Charter for the Conservation and Restoration of Monuments and Sites (The Venice Charter), 1964. https://civvih.icomos.org/wp-content/uploads/2022/03/Charter-of-Venice_1964.pdf
- Wikipedia, Cesare Brandi, on the life and restoration theory of the author of Teoria del restauro (1963). https://en.wikipedia.org/wiki/Cesare_Brandi
- The National Gallery, London, Glossary: Pentimento. https://www.nationalgallery.org.uk/paintings/glossary/pentimento
- Chiara L. M. Occelli, The tradition of Brandi, ICCROM. https://www.iccrom.org/sites/default/files/publications/2020-05/the_tradition_of_brandi.pdf
