Workshops
Focused enablement, not a training catalogue.
Training and e-learning were once a larger part of InnovaTeQ. The practice has shifted toward investigation, design and decision support. Workshops remain where a team needs to work through a real situation together: the same session sequence, tailored to the client’s services and constraints.
They are useful for smaller organisations preparing for slowdowns and outages, and for larger ones that need the same clarity on a critical service.
Looking for self-paced courses? They are at academy.innovateq.io.
Discuss a workshopAt a glance
Four working sessions.
Start from the situation closest to yours. Each card opens the session: who it is for, and the sequence the team works through.
When a critical service slows down
A working session for teams who need to separate capacity assumptions from evidence before they scale, replace or add tools.
See the session →02When the same incident keeps returning
A working session to compare a small set of incidents and see whether the next change is a fix, a control or clearer detection.
See the session →03When users report the failure first
A working session on one high-impact journey: how a failure becomes visible today, and where earlier detection would change the outcome.
See the session →04Preparing for slowdowns and outages
A working session that leaves a short readiness picture: which services matter, how an outage would be noticed, and what to improve first.
See the session →When a critical service slows down
A working session for teams who need to separate capacity assumptions from evidence before they scale, replace or add tools.
Who it is for. Leadership and engineering teams responsible for a service that is slow, unstable or unpredictable — in a smaller organisation or a larger one.
How the session runs
- Name the service, who feels the impact, and what stable enough means.
- List the explanations already in play, and the evidence for each.
- Walk one critical path: application, data, integrations and infrastructure assumptions.
- Mark what production can show today, and what it cannot.
- Agree the smallest next step: investigate, instrument, optimise, or pause a scaling decision.
Tailored to the client
The sequence stays the same. The examples, telemetry and constraints come from the client’s service.
When the same incident keeps returning
A working session to compare a small set of incidents and see whether the next change is a fix, a control or clearer detection.
Who it is for. Teams that restore service repeatedly without a shared view of the cause, the critical path or the missing preventive control.
How the session runs
- Choose a few representative incidents, not the whole backlog.
- Compare what was fixed with what returned.
- Separate the shared condition from one-off symptoms.
- Identify the missing control, owner or detection point.
- Agree what to change first, and what still needs evidence.
Tailored to the client
The comparison uses the client’s incidents, ownership and operating constraints. The sequence of the session does not change.
When users report the failure first
A working session on one high-impact journey: how a failure becomes visible today, and where earlier detection would change the outcome.
Who it is for. Operations, engineering and business owners who hear about disruption from users or customers before their own checks do.
How the session runs
- Select one journey whose failure has a clear business consequence.
- Map how that failure is noticed today: user, business team, then IT.
- Mark the checks that stay green while the journey is already impaired.
- Name the earliest useful signal, and who should act on it.
- Agree what to monitor or test first, and what can wait.
Tailored to the client
The journey, the tools already in place and the escalation path are the client’s. The sequence is the reusable part.
Preparing for slowdowns and outages
A working session that leaves a short readiness picture: which services matter, how an outage would be noticed, and what to improve first.
Who it is for. Smaller organisations preparing for slowdowns and outages, and larger ones that need the same clarity without a broad monitoring programme.
How the session runs
- List the few services whose failure would stop the business.
- For each, describe how a slowdown or outage would be noticed today.
- Separate what is already known from what is only assumed.
- Mark blind spots that would matter in the first hour.
- Leave with a short order of improvements, not a tool shortlist.
Tailored to the client
The services, the current checks and the people who would respond come from the client’s context. The session does not assume a large operations team.