Support and Maintenance en Copenhagen
How we work in Copenhagen
Visual drift is counted, not argued about
Two years after launch somebody counts: eleven greys where there should be four, six button sizes and a typeface that came in for one campaign and stayed. It is a number, not an impression, and it is the first symptom that the system stopped being one. We measure it and pull it back.
Somebody has to be able to say no
A shared library only survives if it has an owner. Every rush job brings its exception and each exception, on its own, is reasonable. Twenty reasonable exceptions are a system that no longer exists. Part of maintenance is that uncomfortable conversation, and we have it so you do not have to.
The fix goes into the part, not the page
When somebody reports a fault on one screen, the easy move is to patch that screen. If the fix goes into the shared component, the other twenty with the same fault are corrected at once, including the ones nobody had reported yet. It costs a few more hours and saves the rest of the year.
Update before it turns into a migration
A design system whose dependencies have gone two years untouched turns a routine update into a project with its own budget and its own timetable. Small, regular and boring works out far cheaper than large and urgent. Security updates go in there too, and those cannot be postponed.
Answering your questions
What people ask us about Support and Maintenance in Copenhagen.
If your question is not here, tell us about the project and we will answer with real context.
Ask us directlyReal work
Projects we have built
Full service · All the detail
Support and Maintenance: stack, process, use cases and FAQs