When Customer Requirements Change, Keep the Handoff Clear with ZGI

说明与用途

当客户需求变更时，使用 ZGI 比较基线简报和更新，分类变更并生成带有未决决策的草稿供人工审核。

问题

Customer updates change scope, audience, and timing, risking loss of earlier requirements and misinterpretation of commitments.

结果

A clear, traceable change brief that maintains baseline requirements, flags new and deferred items, and keeps unresolved decisions visible for human approval.

工作流

• 1. Identify and label baseline brief (B1) and customer update (U1).
• 2. Paste both texts into ZGI agent with instruction to compare and classify changes.
• 3. Request a comparison table first to catch misinterpretations.
• 4. Review table for correct classification and missing dates or scope.
• 5. Ask agent to produce a concise revised draft brief, keeping unresolved items and source labels.
• 6. Perform human review of the draft, confirm dates, audience, and open decisions.
• 7. Approve or reject the revised brief; if approved, replace baseline version.
• 8. Store both versions and record review notes for traceability.

证据

Use an agent in ZGI with a model available in your deployment and instructions focused on one task: prepare a reviewable account of what changed.

来源

Ask for the comparison table first. It is easier to catch a bad interpretation there than inside a smooth paragraph.

来源