制定团队时间与资源容量预算
根据实际可用工时、已承诺任务和缓冲空间评估团队容量,整理资源缺口、约束影响与应对行动。
完整提示词
Main objective: > Build Time Budget Builder 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.
分类与标签
办公效率、团队排期、工时预算、资源规划