Choose the first improvement from the evidence already available

A request for “a better system” can conceal several different needs. The information may be unclear, the relationships between records may be missing, or two otherwise useful applications may not exchange an agreed result. The right starting point depends on which problem the evidence supports.

Use the questions below to identify a sensible first delivery for a Norway-connected project. The service directory describes the areas of development; this page helps decide which kind of intervention is justified.

Is the answer known but difficult to find?

A product owner can explain which drawing belongs to a configuration, but buyers cannot see that relationship on the website. In that situation, the initial work may be a content and catalogue improvement. The organisation already has the answer; the public journey needs to present it and preserve it in the enquiry.

A useful scope can cover one product family, its approved documents and the editor's ordinary update. Search filters or a customer account may be unnecessary at first. The decisive evidence is whether a buyer can distinguish the relevant choices and whether sales receives the context needed to respond.

If the product team itself disagrees about the applicable drawing, resolve that source question first. A redesigned selector would otherwise make an unsettled claim look more authoritative.

Does the staff task need relationships the current record cannot express?

An equipment history may combine asset details, visits and component changes in one repeatedly edited row. Staff can remember what happened while the original colleague is available, but the record does not explain it to someone new.

Here, a focused internal application may be appropriate. Begin with the records that have different lifetimes and the people who may change them. The first delivery might cover one equipment group and a reviewable handover from observation to authorised action.

A wider dashboard is not the first acceptance criterion. Ask whether another colleague can identify the relevant component, the earlier observation and the decision still outstanding. That result provides a reason to expand the system later.

Is repeated entry hiding an unresolved business decision?

Two systems may require similar information without using it for the same purpose. An internal request, an invoice draft and an issued document are related, but they are not interchangeable. Connecting them automatically before agreeing those meanings can accelerate the wrong operation.

Inspect the source of each field, the owner of the receiving account and the response the provider makes available. If those conditions are settled, a supported integration may remove unnecessary re-entry. If they are not, the first deliverable may be a documented process with a deliberate staff review.

The intended next action matters more than a general aim to automate. Staff need to understand what has been established and which decision remains theirs.

Would a repair restore a useful existing task?

A fault in a document link or a specific deployment step does not by itself justify replacing an application. Reproduce the problem, establish available access and examine the affected dependency. A bounded correction may preserve a system people already know how to use.

Replacement becomes a separate proposal when the evidence shows that a necessary capability cannot be supported, the source cannot be maintained or the operating arrangement cannot be continued. Its scope must account for data, useful routes, permissions and staff practice, not only new screens.

Is a prerequisite missing?

Content rights, provider facilities, professional decisions and account authority can determine whether a proposed tool should proceed. A search assistant cannot establish permission to process a procedure collection. A commerce demonstration cannot create a merchant arrangement. Treat those as questions for their responsible owners.

A first phase should leave a usable result or resolve a meaningful uncertainty. Record what it will demonstrate, who will review it and what remains outside it. The planning guide covers audience and operating dependencies; pricing and scope explains their effect on a proposal.

Describe the evidence behind your proposed change. We can then choose an investigation or delivery that answers the actual question.