Build a project presentation around the decision and verified evidence围绕决策与已核验证据创建 Project Presentation
Define the audience and decision, collect a governed evidence pack, write the storyline as assertions, select only material metrics and milestones, show risks and choices honestly, assign next actions, then validate and rehearse the exact final file. Keep detailed data in an appendix or linked source rather than shrinking it onto the main slides.
先定义受众与决策，收集受治理证据包，用可验证主张编写故事线，只选择重要指标与里程碑，诚实显示风险与选择，分配后续行动，再验证并排练确切最终文件。详细数据应放在附录或关联来源中，不要缩小后堆到主页面。
A project presentation is not a replacement for the project plan, issue log, financial system, decision register, or status report. It is a decision-oriented view of those records. Every important claim should retain a source, owner, as-of date, definition, and qualification. Design quality cannot rescue incorrect or stale evidence.
项目演示不能替代项目计划、问题日志、财务系统、决策登记或状态报告。它是这些记录的决策视图。每项重要主张都应保留来源、负责人、截至日期、定义与限定条件。设计再好也无法挽救错误或过时证据。
Define the decision, audience, meeting, and consequence first先定义决策、受众、会议与后果
Write one sentence describing what the audience should understand, decide, approve, stop, fund, escalate, or do. Name the decision owner, meeting date, deadline, affected scope, constraints, and cost of delay or error. A steering committee, delivery team, customer, regulator, sponsor, and retrospective audience need different detail and language.
用一句话说明受众需要理解、决定、批准、停止、资助、升级或执行什么。写明决策负责人、会议日期、截止时间、影响范围、约束以及延迟或错误的成本。指导委员会、交付团队、客户、监管者、发起人与复盘受众需要不同细节和语言。
Separate a status update from a decision request. If no decision is required, define what awareness or alignment should change. If several decisions compete, prioritize them or create distinct sections. A deck that asks for everything usually leaves ownership unclear.
区分状态更新与决策请求。如果不需要决策，就定义哪些认知或一致性需要改变。多个决策相互竞争时，应设定优先级或建立独立章节。一个什么都要求的文稿通常会让责任不清。
Build a source-controlled evidence pack before drafting slides起草页面前先建立受控来源证据包
Collect the charter, scope baseline, integrated plan, milestone record, budget and forecast, resource assumptions, risk and issue logs, dependency map, change decisions, benefit measures, customer or quality evidence, and prior commitments. Record source location, owner, extraction time, definition, period, units, filters, exclusions, and approval status.
收集项目章程、范围基线、集成计划、里程碑记录、预算与预测、资源假设、风险和问题日志、依赖图、变更决策、效益指标、客户或质量证据以及以往承诺。记录来源位置、负责人、提取时间、定义、期间、单位、筛选、排除项与批准状态。
Resolve conflicts before design. If two systems disagree, show which source governs the decision and document the unresolved difference. Do not average incompatible numbers or select the more favorable value. Sanitize sensitive information and follow approved access rules before placing data into a shared deck.
设计前先解决冲突。两个系统数据不一致时，说明哪个来源支配决策，并记录尚未解决的差异。不要平均不可比数字，也不要选择更有利的值。把数据放入共享文稿前，应清理敏感信息并遵循获批访问规则。
Write an assertion-led outline before choosing layouts选择版式前先编写主张驱动的大纲
Draft slide titles as complete, testable claims: “Pilot outcomes support phased rollout,” not “Pilot update.” Arrange them so titles alone form a coherent argument from context and decision through evidence, risk, options, recommendation, and action. Microsoft notes that Outline view displays titles and main text, which makes it useful for reviewing structure and global edits.
把页面标题写成完整、可检验主张，例如“试点结果支持分阶段发布”，而不是“试点更新”。排列标题，使单独阅读它们就能形成从背景与决策到证据、风险、选项、建议与行动的连贯论证。Microsoft 说明大纲视图会显示标题和正文，因此适合复核结构与全局修改。
Challenge every slide: Which question does it answer? What evidence supports the title? What decision changes if it is removed? Put supporting analysis in backup slides. A standard template is useful only when its sequence matches the real decision.
质疑每一页：它回答什么问题？什么证据支持标题？删除后哪个决策会变化？补充分析放入备用页。只有当标准模板顺序匹配真实决策时，它才有用。
Use a project presentation structure that matches the meeting使用匹配会议的项目演示结构
| Section章节 | Question answered回答的问题 | Evidence证据 |
|---|---|---|
| Executive summary执行摘要 | What changed and what is needed?发生了什么变化，需要什么？ | Decision, status, reason, action决策、状态、原因、行动 |
| Outcome and scope结果与范围 | What are we delivering and excluding?交付什么，排除什么？ | Charter, acceptance, baseline章程、验收、基线 |
| Progress and forecast进度与预测 | Are outcomes and milestones on track?结果和里程碑是否按计划？ | Actuals, forecast, variance实际、预测、偏差 |
| Risks and decisions风险与决策 | What can change the result?什么会改变结果？ | Exposure, trigger, owner, options暴露、触发、负责人、选项 |
| Next actions下一步行动 | Who does what by when?谁在何时完成什么？ | Owner, due date, success criterion负责人、截止日、成功标准 |
Make the executive summary a decision page, not a dashboard让执行摘要成为决策页面，而不是仪表盘
State the outcome, overall status with definition, material change since the prior review, top evidence, principal risk, recommendation, and requested decision. Include the reporting period and as-of date. Explain why a status is red, amber, or green; the color alone is not evidence.
说明结果、带定义的总体状态、相对上次评审的重大变化、关键证据、主要风险、建议与所需决策。注明报告期间与截至日期。解释状态为何是红、黄或绿；颜色本身不是证据。
Keep the page interpretable in under a minute but link every material statement to detail. If the project has multiple dimensions, show them separately rather than compressing scope, schedule, cost, quality, benefits, and risk into one optimistic status.
页面应在一分钟内可理解，但每项重要陈述都应链接到细节。项目包含多个维度时，应分别显示，而不是把范围、进度、成本、质量、效益与风险压成一个乐观状态。
Explain project scope through outcomes, boundaries, and acceptance通过结果、边界与验收解释项目范围
Describe the problem, target users or process, expected outcome, in-scope deliverables, explicit exclusions, assumptions, constraints, and acceptance authority. Show approved changes separately from the baseline. Avoid long task lists that reveal activity but not what the project produces.
说明问题、目标用户或流程、预期结果、范围内交付物、明确排除项、假设、约束与验收权。把获批变更与基线分开显示。避免只展示活动而不说明项目产出的长任务清单。
Use a boundary diagram, outcome map, or before-and-after process when it answers the question. Label unresolved assumptions and dependencies. Never imply that a deliverable is accepted merely because it was produced; show the agreed evidence or approval state.
边界图、结果图或流程前后对比能回答问题时再使用。标记尚未解决的假设与依赖。不要因为交付物已经产生就暗示它已被验收；应显示约定证据或批准状态。
Report project milestones with baseline, forecast, actual, and evidence用基线、预测、实际与证据汇报项目里程碑
Select milestones that mark approvals, deliveries, gates, handoffs, contractual commitments, or measurable outcomes. Preserve the baseline, show current forecast, and record actual completion. Include date precision and confidence. If a date moved, state the cause, approval, downstream impact, and recovery or decision required.
选择代表批准、交付、关口、交接、合同承诺或可衡量结果的里程碑。保留基线，显示当前预测并记录实际完成。注明日期精度与置信度。日期移动时，说明原因、批准、下游影响以及所需恢复或决策。
Use the dedicated timeline approach when chronology is decision-critical, but keep this project presentation page focused on material variance and action. Do not reproduce the whole schedule or hide long delay with equal decorative spacing.
时间顺序对决策关键时使用专门的时间线方法，但项目演示中的页面应聚焦重大偏差与行动。不要复制整份排期，也不要用装饰性等距节点隐藏长时间延期。
Measure project progress with outputs and outcomes, not activity alone用产出与结果衡量项目进度，而不只看活动
Separate work started, work completed, accepted deliverables, operational adoption, quality, and realized outcomes. Percent complete is meaningful only when the denominator, weighting, update method, and acceptance rule are defined. Compare actual against baseline or forecast and explain material variance.
区分已开始工作、已完成工作、已验收交付物、运营采用、质量与已实现结果。只有当分母、权重、更新方法与验收规则明确时，完成百分比才有意义。把实际与基线或预测比较，并解释重大偏差。
Use charts only when they reveal a relationship. Label units, period, source, sample, exclusions, and as-of date. Avoid cumulative totals that always rise when the decision concerns rate, quality, backlog, or remaining exposure.
图表能够揭示关系时才使用，并标记单位、期间、来源、样本、排除项与截至日期。当决策关注速率、质量、积压或剩余暴露时，避免使用必然持续上升的累计总数。
Present budget, forecast, capacity, and value without false precision展示预算、预测、能力与价值时避免虚假精确
Show approved budget, actual spend, committed cost, forecast at completion, variance, and the period or currency. Explain material drivers and whether figures include tax, contingency, internal labor, vendor commitments, or shared costs. Do not combine incomparable cost categories merely to create one favorable number.
显示获批预算、实际支出、已承诺成本、完工预测、偏差以及期间或币种。解释重大驱动因素，并说明数字是否包含税、预备金、内部人工、供应商承诺或共享成本。不要为得到一个有利数字而合并不可比成本类别。
For capacity, separate headcount, available time, skill coverage, throughput, and bottlenecks. For value, distinguish forecast benefits from realized outcomes and state attribution limits. A business case is not proof that benefits have occurred.
能力方面应区分人数、可用时间、技能覆盖、吞吐与瓶颈。价值方面应区分预测效益与已实现结果，并说明归因限制。商业论证并不能证明效益已经发生。
Present project risks and issues as exposure, evidence, and action把项目风险与问题展示为暴露、证据与行动
Separate a risk that may occur from an issue that has occurred. For each material item show cause, event, consequence, likelihood or confidence, impact basis, trigger, owner, mitigation, contingency, due date, residual exposure, and required decision. Rank using an agreed method rather than color chosen by intuition.
区分可能发生的风险与已经发生的问题。对每个重大事项显示原因、事件、后果、可能性或置信度、影响依据、触发条件、负责人、缓解、应急措施、截止时间、剩余暴露与所需决策。使用约定方法排序，而不是凭直觉选颜色。
A risk matrix can summarize but can also compress nuance. Pair it with concise descriptions and make thresholds visible. Do not remove uncomfortable risks because they complicate the narrative. Escalation quality is part of project performance.
风险矩阵可以摘要，但也会压缩细节。应配合简洁描述并显示阈值。不要因为风险让叙事变复杂就将其删除。升级质量本身也是项目绩效的一部分。
Show dependencies and changes that can alter the project outcome显示会改变项目结果的依赖与变更
Focus on external approvals, cross-team handoffs, vendor deliverables, environment availability, data readiness, policy decisions, and shared resources. State what is needed, by when, from whom, evidence of commitment, current confidence, fallback, and impact if late. A dependency without an owner is only an observation.
聚焦外部批准、跨团队交接、供应商交付、环境可用性、数据就绪、政策决策与共享资源。说明需要什么、何时需要、由谁提供、承诺证据、当前置信度、后备方案与延迟影响。没有负责人的依赖只是观察。
For change, distinguish requested, assessed, approved, implemented, and validated states. Show effect on scope, schedule, cost, quality, benefits, and risk. Preserve the baseline and decision record so the latest plan is not misrepresented as the original commitment.
变更应区分已请求、已评估、已批准、已实施与已验证状态。显示对范围、进度、成本、质量、效益与风险的影响。保留基线与决策记录，避免把最新计划误报为原始承诺。
Frame project decisions with comparable options and consequences用可比较选项与后果组织项目决策
State the decision, decision-maker, deadline, criteria, constraints, reversible and irreversible elements, and consequence of no decision. Present viable options using the same dimensions: outcome, time, cost, capacity, risk, dependencies, compliance, customer effect, and confidence. Include the status quo when it is genuinely available.
说明决策、决策者、截止时间、标准、约束、可逆与不可逆要素以及不决策的后果。用相同维度比较可行选项：结果、时间、成本、能力、风险、依赖、合规、客户影响与置信度。现状确实可行时也应包含。
Make the recommendation explicit and explain the evidence and tradeoffs. Do not hide unfavorable criteria, manufacture certainty, or treat a scoring model as objective when weights are subjective. Record the decision after the meeting and update the source register.
明确建议，并解释证据与权衡。不要隐藏不利标准、制造确定性，也不要在权重主观时把评分模型当成客观事实。会议后记录决策并更新来源登记。
Choose project presentation visuals by the relationship they reveal根据需要揭示的关系选择项目演示视觉
Milestones, phases, delay, and selected dependencies.里程碑、阶段、延期与部分依赖。
Actual versus baseline, forecast, target, or prior period.实际与基线、预测、目标或上期比较。
Prioritized exposure with visible definitions and ownership.带明确定义与责任的优先暴露。
Comparable options, criteria, tradeoffs, and recommendation.可比较选项、标准、权衡与建议。
Use a visual only when it makes the relationship easier to understand than concise prose or a small table. A screenshot of a project tool often contains unreadable detail, stale navigation, personal information, or irrelevant controls. Recreate only the evidence needed for the decision and cite the source.
只有当视觉比简洁文字或小表格更容易解释关系时才使用。项目工具截图常包含不可读细节、过时导航、个人信息或无关控制。只重建决策所需证据并标注来源。
Design project presentation slides for comprehension and comparison为理解与比较设计项目演示页面
Use a consistent grid, margins, title position, type hierarchy, date format, units, source notes, and status semantics. One main assertion per slide is a useful constraint, not an absolute rule. Keep labels near evidence, align comparable quantities, reserve saturated color for focus or exception, and avoid visual effects that compete with the decision.
统一网格、边距、标题位置、文字层级、日期格式、单位、来源备注与状态语义。每页一个主要主张是有用约束，但不是绝对规则。让标签靠近证据，对齐可比较数量，高饱和颜色只用于焦点或异常，并避免与决策争夺注意力的视觉效果。
Test at real viewing distance and in the meeting window, not only at authoring zoom. If viewers cannot read a label, reduce content or move detail to the appendix. Do not solve overcrowding by reducing font size below practical reading conditions.
在真实观看距离与会议窗口中测试，而不是只在编辑缩放下查看。受众无法阅读标签时，应减少内容或移到附录。不要通过把字号缩到不实用来解决拥挤。
Make every project presentation slide accessible by design从设计阶段让每个项目演示页面具备无障碍能力
Give every slide a unique descriptive title, use built-in layouts when appropriate, check reading order, add meaningful alt text, use sufficient contrast, avoid color-only meaning, write descriptive links, and keep tables simple. Provide a textual summary for complex charts, timelines, process maps, and risk matrices.
为每页设置唯一且描述性的标题，在合适时使用内置版式，检查阅读顺序，添加有意义的替代文本，使用足够对比度，避免只靠颜色表达，编写描述性链接，并保持表格简单。为复杂图表、时间线、流程图与风险矩阵提供文字摘要。
Microsoft recommends running the Accessibility Checker and testing with a screen reader. Repeat checks after layout changes, grouping, conversion, or export because semantics and order can change. Accessibility is not proved by a green checker alone; include representative user and device testing where risk warrants it.
Microsoft 建议运行无障碍检查器并用屏幕阅读器测试。版式变化、分组、转换或导出后应重复检查，因为语义与顺序可能改变。无障碍不能只靠绿色检查结果证明；风险较高时应加入代表性用户与设备测试。
Use speaker notes for context, sources, transitions, and boundaries用演讲者备注记录背景、来源、过渡与边界
Keep the visible slide concise and use notes for definitions, source details, assumptions, caveats, likely questions, transition language, and what not to claim. Microsoft documents adding and reading notes in Normal, Notes Page, and Presenter View. Notes can support delivery but should not contain secrets merely because the audience cannot see them on the main screen.
保持可见页面简洁，用备注记录定义、来源细节、假设、限定条件、可能问题、过渡语言与不得主张的内容。Microsoft 说明可在普通视图、备注页与演讲者视图中添加和读取备注。备注可以支持交付，但不能仅因主屏幕看不到就存放机密。
Inspect notes, comments, hidden slides, document properties, and embedded content before sharing the source file. Test the exact display arrangement so presenter notes do not appear on the audience screen. Prepare a notes-free fallback if the environment changes.
共享源文件前检查备注、评论、隐藏页、文档属性与嵌入内容。测试确切显示布局，避免演讲者备注出现在受众屏幕。环境变化时应准备无备注后备版本。
Rehearse the project presentation for decisions, timing, and challenge围绕决策、时间与质询排练项目演示
Rehearse aloud with the intended duration. Microsoft documents Rehearse Timings and Presenter View, including current and next slides, notes, and timing controls. Use rehearsal to detect dense slides, weak transitions, undefined metrics, missing evidence, awkward handoffs, and decision requests that arrive too late.
按预定时长大声排练。Microsoft 说明了排练计时与演讲者视图，包括当前页、下一页、备注与计时控制。用排练发现密集页面、薄弱过渡、未定义指标、缺失证据、尴尬交接以及出现过晚的决策请求。
Run a challenge rehearsal where a reviewer tests sources, assumptions, unfavorable scenarios, status thresholds, budget variance, dependencies, and option tradeoffs. Practice the concise answer and the move to appendix evidence. Record gaps rather than improvising unsupported claims.
进行质询排练，让复核人挑战来源、假设、不利情景、状态阈值、预算偏差、依赖与选项权衡。练习简洁回答以及转到附录证据的方式。记录缺口，不要即兴编造无支持主张。
Build a navigable appendix that preserves project evidence建立能够保留项目证据的可导航附录
The appendix should support likely challenges without duplicating the main story. Include metric definitions, source and refresh notes, scope detail, milestone acceptance evidence, schedule assumptions, budget reconciliation, capacity model, complete risk and issue views, dependency detail, change log, option analysis, decision history, and action register. Give each backup slide a descriptive title and stable reference so the presenter can move to it quickly.
附录应支持可能的质询，但不要重复主故事。可包含指标定义、来源与刷新说明、范围细节、里程碑验收证据、排期假设、预算核对、能力模型、完整风险与问题视图、依赖细节、变更日志、选项分析、决策历史与行动登记。每个备用页面都应有描述性标题与稳定引用，方便演讲者快速跳转。
An appendix is not a dumping ground. Remove obsolete or contradictory slides, mark sensitivity, preserve the reporting period, and make clear which records are authoritative. Test hyperlinks or section navigation and provide a manual fallback. If a supporting view cannot be explained, verified, or safely shared, it is not ready for the appendix.
附录不是垃圾场。删除过时或互相矛盾的页面，标记敏感级别，保留报告期间，并明确哪些记录具有权威性。测试超链接或章节导航并准备手动后备方案。无法解释、核验或安全共享的补充视图，不适合进入附录。
Test remote, hybrid, and room delivery as different environments把远程、混合与会议室交付当作不同环境测试
In a room, test projector resolution, aspect ratio, lighting, cables, audio, clicker, presenter display, and visibility from the back. In a remote meeting, test window sharing versus full-screen sharing, participant view, bandwidth, notifications, chat, captions, recording policy, and whether the audience can navigate independently. In a hybrid meeting, assign a facilitator to monitor remote questions and confirm that both audiences can see the same evidence.
会议室中测试投影分辨率、宽高比、灯光、线缆、音频、翻页器、演讲者显示以及后排可见性。远程会议中测试窗口共享与全屏共享、参会者视图、带宽、通知、聊天、字幕、录制政策以及受众能否独立导航。混合会议应指定协调者监控远程问题，并确认两类受众看到相同证据。
Prepare a controlled fallback: local copy, approved PDF, dial-in details, offline source summary, and a plan for unavailable links or media. Verify that the fallback contains the same approved decision request and does not expose notes or restricted appendix content. Delivery resilience should reduce interruption without bypassing security controls.
准备受控后备方案，包括本地副本、获批 PDF、拨入信息、离线来源摘要以及链接或媒体不可用时的计划。确认后备版本包含相同获批决策请求，且不会暴露备注或受限附录内容。交付韧性应减少中断，但不能绕过安全控制。
Run four review gates before releasing a project presentation发布项目演示前运行四道复核关口
- 1Evidence gate. Verify every material claim, metric, date, status, source, definition, period, and qualification.证据关口。 核验每项重大主张、指标、日期、状态、来源、定义、期间与限定条件。
- 2Owner gate. Ask accountable owners to confirm scope, milestones, budget, risks, dependencies, recommendations, and actions.负责人关口。 让责任人确认范围、里程碑、预算、风险、依赖、建议与行动。
- 3Editorial gate. Check argument, slide titles, visual hierarchy, comparisons, accessibility, privacy, and cannibalized detail.编辑关口。 检查论证、页面标题、视觉层级、比较、无障碍、隐私与过多细节。
- 4Delivery gate. Rehearse and test the exact final file, device, display, account, network, links, notes, media, and fallback.交付关口。 排练并测试确切最终文件、设备、显示、账户、网络、链接、备注、媒体与后备方案。
Close the project decision loop after the presentation项目演示结束后闭合决策循环
Record decisions, conditions, dissent, assumptions, unanswered questions, actions, owners, due dates, and the version presented. Update the decision register, plan, risk and issue logs, budget forecast, dependency record, and communications source as appropriate. Do not treat verbal agreement as a durable change until the required authority and record are complete.
记录决策、条件、异议、假设、未回答问题、行动、负责人、截止日期与已展示版本。按需更新决策登记、计划、风险和问题日志、预算预测、依赖记录与沟通来源。在所需授权与记录完成前，不要把口头同意当作持久变更。
Distribute an approved summary to authorized recipients, state where the authoritative record lives, and archive or supersede obsolete copies. Track whether requested actions happen and whether predicted outcomes occur. A presentation creates value only when its decisions and evidence remain connected to accountable execution.
向获授权收件人分发获批摘要，说明权威记录位置，并归档或替代旧副本。跟踪请求行动是否发生以及预测结果是否实现。只有当决策与证据继续连接到可问责执行时，演示才真正产生价值。
Avoid project presentation failures that weaken trust避免会削弱信任的项目演示问题
| Failure问题 | Risk风险 | Correction修正 |
|---|---|---|
| Status dump状态堆积 | No decision or priority没有决策或优先级 | Lead with change, consequence, and ask以变化、后果与请求开场 |
| Unsupported green无支持的绿色 | Optimism replaces evidence乐观取代证据 | Define thresholds and acceptance proof定义阈值与验收证明 |
| Baseline overwritten基线被覆盖 | Schedule or cost movement disappears进度或成本移动消失 | Preserve baseline, forecast, and actual保留基线、预测与实际 |
| Unreadable evidence不可读证据 | Detail appears but cannot be assessed细节存在却无法评估 | Summarize, cite, and move detail to appendix摘要、引用并把细节移到附录 |
Use Markdown to review the project story before slide production制作页面前用 Markdown 复核项目故事
Create a written brief with the decision, audience, outcome, scope, reporting period, assertion-led outline, evidence table, risk definitions, options, recommendation, actions, source owners, and unresolved questions. Stable section and evidence IDs make review comments traceable before visual production begins.
创建书面简报，记录决策、受众、结果、范围、报告期间、主张驱动大纲、证据表、风险定义、选项、建议、行动、来源负责人及未决问题。稳定章节与证据编号让评论在视觉制作前就可追溯。
decision: approve controlled next phase
reporting_period: governed source interval
claim_id | assertion | evidence | owner | verified
action_id | owner | due | success_criterionTurn the reviewed project brief into a shareable document把复核后的项目简报转换为可共享文档
After the storyline and evidence are approved, use the InfiniSynapse Markdown conversion tool to create a reviewable Word, PDF, or presentation-oriented deliverable from the written brief. The tool supports document conversion; it does not verify project data, calculate status, approve decisions, remove sensitive content automatically, or guarantee PowerPoint fidelity. Review the converted artifact and finish the deck in an appropriate presentation environment.
故事线与证据获批后，可使用 InfiniSynapse Markdown 转换工具把书面简报生成便于审阅的 Word、PDF 或演示类交付材料。该工具支持文档转换，但不会核验项目数据、计算状态、批准决策、自动删除敏感内容或保证 PowerPoint 保真度。请复核转换成品并在合适演示环境中完成文稿。
Open the Markdown conversion tool打开 Markdown 转换工具Use this project presentation release checklist使用这份 Project Presentation 发布检查清单
- The decision, decision owner, audience, reporting period, and requested action are explicit.决策、决策负责人、受众、报告期间与所需行动明确。
- Every material claim has a source, definition, owner, as-of date, and qualification.每项重大主张都有来源、定义、负责人、截至日期与限定条件。
- Scope, milestones, progress, budget, risks, dependencies, changes, and benefits retain their baselines.范围、里程碑、进度、预算、风险、依赖、变更与效益都保留基线。
- Options are comparable and the recommendation states tradeoffs and confidence.选项可比较，建议说明权衡与置信度。
- Slide titles form a coherent assertion-led storyline and detail is moved to the appendix.页面标题形成主张驱动故事线，细节移入附录。
- Charts, timelines, matrices, labels, units, legends, and source notes are readable and accurate.图表、时间线、矩阵、标签、单位、图例与来源备注可读且准确。
- Accessibility, privacy, notes, hidden content, permissions, links, media, and export behavior were tested.已测试无障碍、隐私、备注、隐藏内容、权限、链接、媒体与导出行为。
- The exact final artifact was rehearsed in the intended device, account, network, and display setup.已在预定设备、账户、网络与显示设置中排练确切最终成品。
Project presentation frequently asked questionsProject Presentation 常见问题
Start with the decision and executive summary, then cover outcome and scope, progress and milestones, budget or capacity, risks and dependencies, options and recommendation, and owned next actions. Put definitions, detailed schedules, logs, and supporting analysis in an appendix.
先说明决策与执行摘要，再覆盖结果与范围、进度与里程碑、预算或能力、风险与依赖、选项与建议以及有负责人的下一步行动。定义、详细排期、日志与补充分析放入附录。
Include the reporting period, material change, defined status by dimension, outcome evidence, baseline versus forecast, top risks and issues, dependencies, approved changes, decisions required, owners, due dates, and links to authoritative records.
应包含报告期间、重大变化、各维度定义状态、结果证据、基线与预测比较、关键风险和问题、依赖、获批变更、所需决策、负责人、截止日期与权威记录链接。
There is no universal number. Use the fewest slides that support the decision within the available time. Rehearse, remove repetition, and move evidence that is important but not essential to the main narrative into a navigable appendix.
没有统一数量。应在可用时间内使用能够支持决策的最少页面。排练并删除重复，把重要但非主叙事必需的证据放入可导航附录。
Prioritize material exposure, define the assessment method, show cause, consequence, evidence, trigger, owner, mitigation, residual risk, decision deadline, and recommendation. Connect the risk to project outcome rather than showing an isolated red box.
优先显示重大暴露，定义评估方法，并说明原因、后果、证据、触发条件、负责人、缓解、剩余风险、决策截止时间与建议。把风险连接到项目结果，而不是只显示孤立红框。
Preserve baselines, cite governed sources, define metrics and status, disclose uncertainty and exclusions, obtain owner confirmation, separate fact from forecast, review accessibility and privacy, rehearse challenges, and test the exact final artifact.
保留基线，引用受治理来源，定义指标与状态，披露不确定性和排除项，获得负责人确认，区分事实与预测，复核无障碍与隐私，排练质询，并测试确切最终成品。
Authoritative guidance used for project presentation delivery用于项目演示交付的权威指南
- Microsoft Support: Create and print a presentation in Outline viewMicrosoft 支持：在大纲视图中创建与打印演示
- Microsoft Support: Create a presentation from an outlineMicrosoft 支持：从大纲创建演示
- Microsoft Support: Use Presenter ViewMicrosoft 支持：使用演讲者视图
- Microsoft Support: Rehearse and time deliveryMicrosoft 支持：排练并计时演示
- Microsoft Support: Speaker notes and comments with a screen readerMicrosoft 支持：用屏幕阅读器处理备注与评论
- Microsoft Support: Make PowerPoint presentations accessibleMicrosoft 支持：让 PowerPoint 演示无障碍