返回提示词目录第 1385 页

审计日程负荷与团队容量

核对实际可用工时、已承诺工作与缓冲空间,输出容量缺口和约束矩阵,安排调整及升级机制。

完整提示词

Main objective:

> Build Calendar Load Audit as an operating system with a clear purpose, ownership, inputs, outputs, triggers and evidence that the system actually reduces friction.

## 1. CONTEXT
Define people/teams involved, work type, current tools/channels, cadence, volume, constraints, failure modes and success criteria.

## 2. DOMAIN STANDARD
Capacity planning must start from realistic available capacity rather than nominal headcount or calendar hours. Protect buffers for uncertainty, support work and unplanned demand.

## 3. INTEGRITY CHECKS
- available capacity excludes known overhead
- workload is sized consistently
- buffers are explicit
- critical constraints are visible
- resource conflicts use priority criteria
- deadlines are checked against dependencies
- utilization does not target 100% by default
- scenarios define trigger/actions

## 4. SYSTEM CARD
```text
Purpose:
Owner:
Trigger:
Inputs:
Process:
Output:
Consumer:
SLA/cadence:
Failure mode:
Escalation:
Review metric:
```

## 5. REQUIRED MATRICES
### Capacity Matrix
| Resource/team | Available | Committed | Buffer | Gap | Action |
|---|---:|---:|---:|---:|---|

### Constraint Matrix
| Constraint | Affected work | Severity | Owner | Option | Trigger |
|---|---|---|---|---|---|

## 6. FAILURE MODES
Avoid meetings without decisions, notes without actions, unclear ownership, overloaded capacity, hidden queues, status duplication, knowledge trapped in people, and systems that require heroic memory.

## 7. REQUIRED OUTPUT
1. Current system map.
2. Purpose and owner.
3. Trigger/input/output logic.
4. Risks/failure modes.
5. Required matrices.
6. Operating cadence.
7. Escalation.
8. Improvement criteria.

End with **System Integrity Check** confirming the workflow reduces ambiguity and has measurable evidence of usefulness.

分类与标签

办公效率、日程审计、容量规划、资源冲突、工作负荷

前往 AI 图片创作