What has been built
The current picture: systems, processes, costs, weak points, risks.
We start from what the company lives on rather than from technology. The technology is chosen afterwards, once it is clear what actually needs to change.
The current picture: systems, processes, costs, weak points, risks.
What stops the departments working. The answers regularly differ from the technical department's version.
We break down the spending and separate what delivers a return from what is simply written off.
We plot the initiatives on axes of benefit and difficulty and explain why the order is what it is.
A calendar covering one to three years with stages, amounts and the points where the next decision is taken.
We prepare the document and the presentation in a form you can put in front of the owner.
Four to six weeks; the timing depends on the size of the company and the number of departments.
We study not only the technology but how the company earns and what is holding growth back.
A technical review plus interviews with the heads of departments.
We overlay the business problems onto the state of the systems and calculate what each change would give.
A costed calendar, a presentation to the management and revisions after the discussion.
Most often we find money disappearing into thin air. Licences paid for with no users at all, a system rolled out and abandoned, two services duplicating each other. Tidying up that part often pays for the first stage of changes by itself, with no need to ask for extra budget.
A technical survey describes the current state of the equipment. Our work answers a different question: where the organisation should move. A survey can be one stage of that work, but on its own it gives neither an order of priority nor a budget.
Definitely the heads of departments and whoever controls the budget. A plan written from conversations with the technical department alone comes out competent and entirely disconnected from what the company actually lives on.
We say it as it is, including when the root of the problem is not in the technology at all but in the processes or in particular people. Such a conclusion is unpleasant to hear, but thanks to it the budget does not go on a rollout that would not have solved the problem anyway.
Tell us what worries you: costs, speed, risks. We will look into it and propose a plan with priorities.
Request received
It is already with a manager. You will get an answer within the working day, and urgent requests go to the duty engineer immediately.
There is no such city in the list. Check the spelling.