Black Jacket AI Intelligence
PreviewThe four questions.
Black Jacket AI Intelligence is built on a single analytical framework. Every communications analysis answers four questions, in order. The framework is designed for the operating reality of a senior executive.
Decision-Bearing Communication
Definition
A communication containing an explicit or implicit request for a decision — directive, approval, or confirmation — from the executive.
Why it matters
Decision requests that are not visible are decision requests that are missed. The first step in managing the operating load is an accurate count. Without it, the executive operates on instinct rather than evidence.
What it detects
- Direct asks: explicit approval requests, directives awaiting sign-off, confirmation requests.
- Implied asks: communications presenting options without a stated decision, stalled projects awaiting the next move.
- Escalated asks: third or fourth follow-up in a thread on the same decision point.
Decision Bottlenecks
Definition
A Decision-Bearing Communication that has not received a response within the executive's normal operating cadence — typically 48 to 72 hours.
Why it matters
Unanswered decisions do not disappear. They accumulate. Decision Bottlenecks quantifies where the executive is the constraint in the organization's delivery chain — a direct measure of throughput risk.
What it detects
- Decision requests older than the response threshold, ranked by elapsed time.
- Counterparty clustering: multiple pending decisions from the same person or team.
- Organizational impact scoring: decisions that touch delivery commitments weighted higher.
Service Pressure Curve
Definition
The aggregate intensity of service-related communications over a rolling window, expressed as a normalized score.
Why it matters
Escalation events are rarely sudden. They are preceded by a sustained increase in communication frequency and urgency. The Service Pressure Curve makes this pattern visible before the escalation occurs — giving the executive a meaningful lead time to intervene.
What it detects
- Increasing volume from a specific counterparty over the analysis window.
- Shifting language patterns: words indicating urgency, dissatisfaction, or repeated attempts.
- Cross-thread references to the same issue — an indicator that the problem has not resolved.
Rework Density
Definition
The proportion of communications that reference a previous decision, deliverable, or action item being corrected, modified, or relitigated.
Why it matters
Rework is not a project management failure in isolation. It is a structural signal. High Rework Density in a communications window indicates that decisions are not landing with sufficient clarity — or that the organization lacks the capacity to execute them. Neither is a resource problem.
What it detects
- Language indicating revision: "please revise," "that's not what I asked for," "we need to revisit."
- Thread patterns where closed topics reopen within the same analysis window.
- Cross-counterparty rework clustering: the same deliverable being questioned by multiple parties.
In private preview.
Access opens in a later version. Request a slot for the preview cohort.