Peter Yang - Commentify

Product StrategyWeb AppCollaboration ToolsAI WorkflowsProduct Design

Overview

Where I Started

Problem Statement

Product decisions often happen inside comments rather than formal project documents. As conversations spread across Figma, Jira, and multiple projects, teams lose track of feedback, unanswered questions, and emerging delivery risks.
Existing collaboration tools organize conversations around individual files or issues. They rarely provide a unified view of what needs attention across the team’s entire workflow.

Context

Commentify began from a problem we experienced directly while working across product design and development: important feedback was easy to receive but difficult to track through completion.
We explored how comments from different tools could become a shared operational layer without forcing teams to replace the platforms they already use.

What I Did

Responsibilities & Contributions

Defined the product strategy and designed a unified workflow for managing conversations across Figma and Jira.
Designed comment triage, completion, saving, tagging, filtering, and AI-assisted summarization experiences.
Extended the experience from a comment inbox into an intelligence dashboard for activity, sprint health, risks, and emerging patterns.
Created the product identity, responsive interface, design system, prototypes, and product website in collaboration with the team.

Impact

2 integrated work platforms

Unified conversations from Figma and Jira in one operational view.

1 shared comment workflow

Turned incoming feedback into trackable items that teams can review, complete, save, and organize.

Real-time synchronization

Kept conversations current without requiring teams to collect updates manually.

AI-assisted team awareness

Transformed conversation activity into summaries, sprint-health signals, risk indicators, and emerging patterns.

What I Learned

Key Insights

Aggregation alone does not resolve communication overload. Teams need a clear way to distinguish actionable feedback, reference material, unanswered questions, and broader delivery signals.
AI became more useful when applied across many conversations to reveal patterns and risks, not only when summarizing a single thread.
Integrations should preserve the context of their source tools. Figma and Jira comments can share a workflow while still representing different types of work.

Critical Constraints

Figma and Jira use different authentication models, data structures, webhook behavior, and token-expiration policies.
Real-time updates needed to remain reliable across synchronization delays, duplicate events, edits, and deletions.
AI-generated signals had to remain traceable to actual team conversations so users could understand and verify the underlying context.