TutorialsGeneral PPT Workflow
A complete flow from receiving materials and confirming requirements to analyzing, reviewing logic, generating, and accepting.
Making a PPT goes through eight stages: receiving materials, confirming requirements, analyzing, discussing key findings, confirming the outline, planning design, reviewing logic, and generating with acceptance. Each stage has a clear output and confirmation point.
Receive materials
First register the material type and name. This stage only receives and identifies; do not process materials early.
Confirm these details:
Material format
Excel, documents, images, or an old deck.
File count
Which files exist and what is missing.
File purpose
How each material will be used.
Version conflicts
Whether multiple versions coexist.
Sensitive data
Whether anything needs anonymizing.
Received the following materials:
1. survey-data.xlsx
2. course-background.md
3. brand-visual-reference.pdf
Next, confirm the PPT purpose, audience, style, and delivery format.Confirm requirements
Use a requirement planning card to pin down the goal and avoid rework later.
## Requirement Planning Card
- PPT purpose:
- Target audience:
- Presentation scenario:
- What the audience should understand:
- What the audience should do:
- Estimated pages:
- Style:
- Speaker notes needed:
- Editable version needed:
- Key page screenshots needed:
- Delivery format:Analyze materials
Analysis covers data findings, content trade-offs, risk and gap identification, and separating conclusions from evidence.
Analysis must go beyond a simple summary. At minimum, answer:
- Which findings matter most
- Where these findings come from
- How they affect the PPT thread
- Which conclusions need careful wording
- What information is still insufficient
Discuss key findings
After analysis, discuss the key findings first. Do not jump to the outline.
Each finding should include six elements:
### Finding name
- Finding:
- Data source:
- Judgment:
- Meaning for the PPT:
- Possible counterexample:
- Whether it enters the main thread:Distinguish three kinds of information:
Fact
Information directly in the material.
Judgment
An interpretation of a fact.
Suggestion
An action proposed from a judgment.
Fact: The top three pain points account for 58.2% combined.
Judgment: Users' main resistance to AI is concentrated in the starting stage.
Suggestion: The first half of the course should focus on questioning, privacy, and tool choice.Confirm the page-by-page outline
The outline should state, per page: title, page type, core point, materials used, visualization, and relation to surrounding pages.
## Page 1: Cover
- Page type: Cover
- Core point: Course theme and research basis
- Materials: course name, survey sample notes
- Visual: large title + sample number
- Narrative role: build credibility
## Page 2: Core user pain points
- Page type: Data page
- Core point: High-frequency pain points cluster in three directions
- Materials: survey pain point field
- Visual: horizontal bar chart
- Narrative role: lead into the course design logicCheck at this stage:
- Is there a clear thread
- Does each page carry one core job
- Are there duplicate pages
- Are there jumps
- Can every important conclusion go back to the materials
- Are any pages just padding
- Does the ending form an action loop
Plan the design
After the content outline is confirmed, plan the design so it stays on topic.
## Global Design Plan
| Item | Plan |
| --- | --- |
| Recommended style | Data professionalism + community warmth |
| Primary color | Deep red |
| Secondary colors | Light red, orange |
| Body color | Dark gray |
| Data pages | Bar charts, donut charts |
| Course pages | Module cards |
| Images | Community image on cover, tool screenshots on course pages |
| Editability | All text, shapes, charts editable |
| Revision order | Content first, then layout, then visual details |Review the logic
Before generating, check whether the PPT holds together: the thread, order, evidence, and loop.
Data
→ User pain points
→ Typical scenarios
→ User personas
→ Course plan
→ Course schedule
→ Course features
→ Call to actionGenerate and accept
After all prerequisites are confirmed, generate the PPT. Delivery requirements may include:
Editable
Text, shapes, and charts can be changed.
Exportable
Output in the needed formats.
Screenshottable
Key pages can be captured for acceptance.
Iterable
Keep revising from feedback.
Traceable
Data sources can be traced back.