OPERATEOngoing Development & Application Responsibility
Launch changes the responsibility. It does not end it.
A live product needs maintenance, releases, documentation and clear ownership. Further development belongs to the same relationship but not to the same commitment. It is defined and agreed on its own.
Where this usually starts
- 01
The first version is live, and it is teaching.
- 02
The next step is wanted. The evidence for what it should be is not yet in one place.
- 03
Ownership of what happens after launch is unclear.
- 04
Improvements are accumulating as a list, not as a sequence with reasons.
What we take on
Nordleid can carry contracted responsibility for a live application or platform: maintenance, dependency and compatibility updates, release management, store releases, documentation, transition and handover, with monitoring and incident handling where contracted. Further development and product evolution are defined as separate work when change is justified.
- We establish what the live system has proved, where it is strained, and what must stay stable.
- We define what is included: maintenance and releases are not the same commitment as further development, and each is scoped and priced separately rather than bundled into open-ended support.
- We keep the system current, controlled and documented, and develop it further in defined windows.
What changes
The next step starts from what the last one learned. Context is kept. Continuation becomes a deliberate decision, and responsibility after launch has a name.
What continues after the first delivery.
01What the last version taught
Use, support, strain and surprise: the evidence that should shape the next commitment.
02Releases
A live product keeps changing. Each release is prepared, published and verified afterwards.
03Documentation and enablement
The system stays understandable, and the people who use and administer it get the material the work requires.
04What must stay stable
The parts that cannot move while the next change is made.
05What deserves the next window
The improvement with the strongest reason behind it.
06Ownership and handover
Who runs the live work day to day, and how understanding is transferred to the team that owns it next.
07When to stop
The point at which more change is a new decision, not an open-ended continuation.
Ongoing development is Chain Development after the first delivery: evidence, then the next decision, then the next window.
Across Nordic markets
If continuation has to hold across Nordic markets
Operating conditions, language and market-specific requirements can change what the next development window should inherit from the last one.
- Operating conditions
- Language
- Market-specific requirements
Before the work begins
What happens after the first release?
The first release is a version, not a finish line. Releases continue and are verified after publication. Documentation and instructions are kept current, the people who operate the system are enabled to run it, and understanding can be transferred to whoever owns it next. What the live work teaches decides whether a further window is warranted and what it should prove.
How Nordleid approaches this
Continuation should stay a choice the business makes.
Whoever carries that responsibility, a live system does not need an open commitment that blurs ordinary maintenance with new development, so that continuing becomes the default rather than a decision.
Nordleid separates the two: maintenance and releases are scoped as running responsibility, and further development is defined and agreed as its own work when change is justified. The client retains ownership and the right to transition or take the system over at any point, and the documentation and transfer of understanding that make that possible are planned as part of the work.
If the system is live and responsibility after launch is still unnamed, show us where you are.