/ Service
Services
Between those who own the business and those who build and operate the systems, we align — at the level of concrete work — three states: decide, drive, and carry forward to the next phase. Our support covers the following three areas.
/ Topics
What you can bring to us
We are glad to talk through situations like these.
- You want to pin down the features and requirements a system needs
- You want support with design, implementation and testing after requirements are set
- You want progress, issues and open decisions laid out clearly
- You need to coordinate several people involved in a rollout
- You want to talk through pre-tender groundwork or how to run procurement
- You want support building and running a system used at an event
- You want to discuss maintenance, monitoring or improvement of a live system
- You want the handover from the build team to the operations team organised
Depending on what is needed, we judge what we take on ourselves and where we work with partner companies, and assemble the right team for each engagement.
-
01
IT System Development
Supporting every phase of IT system development — from requirements and design through implementation and testing.
We confirm the business goal, the users, the required features, the constraints and the open questions, and set the scope of what is to be built. After implementation we verify against the agreed requirements through testing.
What this covers
- Confirming the purpose of the system and who uses it
- Setting out required features and constraints
- Listing open decisions and points to confirm
- Design
- Infrastructure build
- Implementation
- Preparing and running test cases
- Recording what was built and what remains
-
02
Project Management
PMO and PM support for large-scale system rollouts and event infrastructure projects.
We lay out the plan, progress, issues and open decisions, and make clear what stakeholders need to decide and what happens next. The aim is not that a meeting took place, but that after it everyone knows who does what.
What this covers
- Setting out work items and schedule
- Checking progress
- Managing issues and open decisions
- Budget, contract, vendor and quality management
- Organising what needs confirming with stakeholders
- Recording meeting agendas and decisions
- Naming owners and deadlines for the next round
- Reporting project status
-
03
System Operations
Maintenance, monitoring, and continuous improvement for live production systems.
We record incidents, user enquiries and change requests, and set out what needs action and in what order. Rather than closing tickets one by one, we check whether the same problem keeps recurring and consider what should be improved.
What this covers
- Checking and monitoring how the system is running
- Recording incidents and enquiries
- Responding when something fails
- Tracking the state of each response
- Carrying out or supporting maintenance work
- Organising change requests
- Prioritising improvements
- Keeping operating procedures and response history current
Monitoring hours, response times for incidents, and which systems are covered are agreed on a per-engagement basis.
/ Engagement
How we actually work
Where we come in and how much we carry varies by engagement. These are the shapes that recur.
-
Joining the team, from coordination through to implementation
We join the project team, handle specification alignment and delivery management with the companies involved, and carry out development, testing and a phased move into production.
We give everyone one list of the decisions still waiting and who owns them by when. Where requirements diverge because practice on the ground differs from the rules, we frame it as a choice — unify the rule, or work around it in practice — so the client has something they can actually decide on.
After go-live we hand the reasoning and the remaining open points to whoever takes on maintenance.
-
Coming in before the contract, assembling a team, and carrying it to launch
We get involved as early as the proposal and procurement stage, bring together a project manager and engineers, and carry the work from build through to launch.
We prepare the acceptance-test angles and scenarios, and a list of what must be cleared before launch with owners and deadlines, and share it across stakeholders. At launch we hand over operating procedures and unresolved points in a form the support desk can act on.
-
Designing the post-launch desk and holding the operating team together
We take on everything from standing up operations after launch to day-to-day first-line response and regular reporting, designing the first-line desk and holding together the team that staffs it.
We build the procedures for each intake channel, the criteria for escalating to the responsible department, and the format for operational reporting. Putting procedures and report formats in writing means the same standard holds even when the company staffing the desk changes.
/ Value
Decide. Drive. Continue.
Decide, drive, carry forward — at the level of concrete work we align these three states, so work that had stalled starts moving again.
-
01
Decide
Surface the right questions and material so the right things actually get decided.
-
02
Drive
Make it concrete — what, who, by when, and how far — so the team can reach the next goal without hesitation.
-
03
Carry forward
Leave the reasoning and the path taken in a form the next phase can pick up and act on.
/ Process
Step by step, steadily forward.
From understanding the current state through to ongoing execution support, we make what needs to be decided concrete, step by step.
-
01
Understand
We confirm the goal, the scope, the deadline, who is involved, what is going wrong now, and what material already exists.
-
02
Identify
We separate what must be decided, what needs confirming, and what can wait.
-
03
Plan
We write down and agree what we will do, what we will not do, what we will deliver, and how we will work.
-
04
Execute
We work within what was agreed, sharing progress, issues and anything needing a decision as it comes up.
-
05
Report
We report what was done, what was decided, what remains open, and what needs to happen next.
/ Before
Before you get in touch
These details help us move faster, but tell us only what you know.
- The system or project in question
- Where things stand now
- What is giving you trouble
- The kind of support you are looking for
- Your preferred timing
- What has already been decided
- What has not been decided yet
From early-stage thinking to projects in motion and live services seeking improvement — whatever the phase, please get in touch.