Comments and Review

Comments are a feature that attaches feedback to specific locations in the skeleton and final deck. Instead of long messenger conversations, you can clearly record which block of a slide needs to be changed within the project.

Targets that comments attach to

• Entire slide
• Specific content block
• Skeleton canvas
• Final deck canvas

Comments store the canvas position and can be distinguished between open and resolved comments.

Leaving a comment

1. 1

   Open the slide to review

   Select the exact section in the skeleton or final deck.

2. 2

   Choose the comment location

   Decide whether the comment is for the whole slide or a specific block, then add the comment at that location.

3. 3

   Write in actionable sentences

   State the problem, the reason, and the desired change. Example: "The reference period for a 18% conversion rate is not visible. Please add Q2 2026 below the card."

4. 4

   Continue the context with a reply

   Instead of creating a new comment repeatedly, reply to the existing thread on the same topic.

5. 5

   Mark as resolved after editing

   Once the change is reflected and the reviewer confirms, change the comment to resolved status.

Criteria for good comments

• The slide number or block is clear.
• Explain what is wrong instead of saying "odd".
• If possible, state the desired outcome.
• Separate fact-checking from style preferences.
• Include priority and deadline if needed.
• Do not mix multiple issues into one comment.

Good example:

In slide 6’s sales chart, the units for May and June differ. Standardize to ten‑thousand‑won units based on the original financial report, and add a source below the chart.

Less good example:

Please redo the chart.

Managing comment messages

In a comment thread, you can add replies. Depending on permissions and author conditions, you can edit or delete messages, and the thread itself is managed as open or resolved.

• When correcting misinformation, inform that the original meaning has changed via a reply.
• For core comments already answered by someone else, prefer a correcting reply over deletion.
• Before marking resolved, have the reviewer confirm the final result.
• If the UI allows reopening resolved comments, reuse them when new issues are found.

Team review operation examples

• Storyline review: check messages, order, and missing justifications.
• Skeleton review: verify information density, chart/table structure, and wording.
• Final deck review: check style, trimming, images, and presentation quality.
• Focus on one level of issue per review round.
• The final approver checks all resolved and remaining open comments.