KT Intake

Capture incident context, sync updates, and export crisp summaries without leaving the bridge.

Problem Summary

Evidence & Affected Object

Detection Source
Evidence Collected
Which alerts, observations, measurements, reports, or reproducible results demonstrate the deviation?
Which service, process, tool, machine, model, or configuration details distinguish the affected object?

Baseline vs Current Behavior

Which expected behavior, measure, or prior condition provides the normal baseline?
Which current observations or measurements show how actual behavior differs from that baseline?

Describe The Problem

Impact

What is the current impact?

Who or what is affected now, and how large or severe is the impact?

What future impact is likely if the issue remains unresolved?

What downstream effect is likely if the deviation continues unresolved?

By what specific deadline or timeframe does resolution become difficult, expensive, impossible, or meaningless?

When does a deadline, dependency, or decision point make resolution difficult, expensive, impossible, or meaningless?
Current Service Recovery Stage

Problem Analysis

KT Question IS — facts only IS NOT — similar & reasonable and could be but is not occuring Distinctions — Unique characteristics about the IS Changes — Changes that happened in on around or about each Distinction

Possible Causes

Capture hypotheses and pressure test them against the KT IS / IS NOT evidence. Start with the suspect, accusation, and impact; then walk each cause through the table.

Decision AnalysisChoose and authorize the recovery path
Potential Problem AnalysisMake implementation and rollback risk explicit