Technical knowledge base with categorization and versioning · SharePoint

The pain

What it costs you today

In an IT operation running 40 critical services in production, the runbook for recovering the SAP system from a Sunday outage lives in Pedro's head, the senior who configured it in 2019, and when Pedro goes on vacation the system crashes and nobody knows what to do. The team loses 8 to 16 hours per critical incident reconstructing steps from collective memory, while the SLA with the business is missed and the escalation reaches the executive level. When Pedro resigns six months later the runbook is lost with him and the next incident is resolved in 14 hours instead of 2. Key-person dependency is the leading cause of severe incidents in mature operations, and the continuity audit marks it as a critical finding. What is the cost of knowledge that lives in one head?

The value

What changes when you have it

Runbooks, postmortems and technical FAQs live in a SharePoint organised by service and system, each with explicit owner, last-validation date, links to monitoring and operational dashboards, and a workflow that fires an alert when a runbook goes 6 months without an update. The new engineer opens the service site, reads the runbook step by step and executes the recovery without having to escalate to anybody's memory. The Site Reliability team sees a runbook-coverage and obsolescence dashboard per critical service. The visible output is the living runbook catalogue with per-service, per-owner and per-criticality search, connected to Dataverse and to monitoring. The solution is in production at a fintech running 35 services in production where Sev-1 MTTR fell 58%. The investment pays back with the first Sev-1 incident resolved on time.

Stack

Technologies we touch in the implementation

SharePoint OnlineSPFxPnP PowerShellDataverseMarkdown