Frequently asked questions.

Yes. Evolving existing systems can form part of the scope. The starting point is to understand what works, where the problems are and what changes are needed.

It can. Assessment, architecture, development and integration can be combined according to the project and the agreed terms.

No. A description of the problem, the systems involved and what you want to achieve already helps guide the initial conversation.

No. The structure can serve to present an initiative, a programme or a set of content. The cultural proposal guides the choice.

Those responsible for the project define the content and its permissions. Technology support organizes its presentation and the agreed publishing workflow.

There is no single package in this presentation. Pages, functions and operating conditions are defined based on each project's needs.

That depends on the problem. The assessment should consider existing tools, integration, data, costs and limitations before choosing a solution.

No. The pilot is used to evaluate the application against defined criteria. Any gain needs to be measured in the context where it will be used.

The level of review depends on the task and its risks. The approach starts with human oversight and explicit limits on actions.