Office PPT 技能培训

PPT常见现象
1. No Structure 没有清晰的架构
2. Messy 思路不清晰
3. Too Simplified 过于简单
4. Confusing 观众看不懂

High Quality Technical Papers Features （BLAS）

• 1. Brief 简洁 （稀释效应/）

快速销售(Elevat Pitch)：30s之内表达关键信息。

• 2. Logic Sequence 逻辑顺序

Primacy Effect 首因效应
https://wiki.mbalib.com/zh-tw/%E9%A6%96%E5%9B%A0%E6%95%88%E5%BA%94

• 3. Accurate 准确

A+B=C

4*(A+B - C) = 3 * (A+B -C)

→ 4 = 3 ？

• 4. Technical Sharp 技术犀利性

Google provides wordwide internet access in just on click.
[Google拉红杉资本投资，一句话表达信息]

Steps of Writing a Technical Paper
1. Audience Analysis 读者分析
   ① Obejective 演讲目标
    Report
    Update
    Discussion 
    Problem Solving
    Proposal 说服别人
    Advice
    Approval 向上汇报
    Sharing
    
    ② Scope
    Core Audience
    Extended Audience
    
    ③ Expertise 专业度划分
    Strong
    Weak
    Mixed
    
    ④ Value 价值观
    Input
    Output
2. Sketch 架构
3. Content Creation 素材
4. Revision 修改

Technical Paper Components

呈现架构的重要性

PSI 架构

Problem Statement

1. Industry Backgound 场景具体化，与读者关联
2. Problem Scenarios
3. Impact of Problems
4. Exsting Soluction
5. Technical Modelling: 抽象出数据模型

Implentation

Example
Results 
Benefits/Advatages
...

钻石模型

Revision

Refine 、 Vision: 文章立意、Review、Repeat

Title

你和马云相差的6步

火星上现在是几点？

NPS

Novelity: Abstract the novieity of your idea 1-4 words

Problem: Summarize the pro to resolve in 1-4 words

System/Scenario: System envir or Scenario applied into your system.

Positioning

定位理论：杰克·特劳特

品牌定位：

日本：消费电子
美国：创新
Volovo：安全

PSB Structure for Abstract

Abstract, Summary, Executive Summary

Abstract：比较正式
Executive Summary: 面向高层，专业度低

缩写会引起误解

background

让读者与作者保持信息一致。

如何写Backgund

Problem Statement

SIM

Scenario -> Impact -> Technical Modelling
场景 -> 影响 -> 技术建模

Example: 手机抢红包

Solution Description

Create Your Theory

Result

4C for Data Selection

Crital/Connecting/Comparable(香蕉和苹果没有可比性)/Convincing

Result: PFEV Flow

Parameters-Figures-Explanation-Verification

Tips for Results

1. Lead readers to discover advantages and draw their conclusion
2. Link the figures with texts
3. Not to cover disadvantages but to explain
[这个缺点是可接受的，因为能够减少成本。]

Conclusion DNA Format

Training Process as Below

Module 1: BLAS Criteria for High-Quality Technical Writing

Module 2: Technical Writing Steps
1. Why do people read your technical writing?

Tool: Problem Mapping

2. Structure your writing using analytical thinking

- Main components for a technical paper

- PSI Structure

- Tool: Diamond Blue Print

- Case Study

- Game

3. The art of addition and deletion

4. 3R Rules

Module 3: Main Components of Technical Writing

1. Create a novel and attractive Title

- NPS model to write titles

- Common Mistakes

- Exercise: Evaluate powerful or weak titles

2. Attract attentions by Abstract

- PSB Structure for Abstract

- Example Analysis & Group Exercise

3. Profound Background to sync-up with audience

- Funnel model

- Example Analysis & Group Exercise

4. Articulate a valuable Problem

- SIM model to discover a valuable problem

- Tool: “5-Why” Analysis & Common mistakes

- Exercise: Re-identify problems

5. Systematically provide technical Solutions

- WIFI mode to describe logical solutions

- How to highlight the novelty? How to create feasible 
working flow

- Case Study

6. Prove your idea by convincing Results

- 4C rule for results selection

- PFEV flow to present convincing results

- Case Study & Exercise

7. Reinforce the novelty in Conclusion

- DNA tool to create a powerful conclusion

- Examples

8. Profound literature review with Citations

- Professional reference format

- Exercise: Fun reference citation

9. Group Exercise