Slack Synthesis

3 feedback channels collapsed into 1 prioritized read

ROLE

Creator and Product Designer

SCOPE

Slack ingestion, LLM synthesis, prioritization model, evidence log, and project handoff

TEAM

Design, Product, Engineering

Reframing the problem

Reframing the opportunity

Slack feedback was scattered across three channels, three perspectives that almost never met. By the time a pattern was obvious it had already cost us. No one owned the synthesis.

At-a-glance view with chat and channel receipts. This turns feedback decision-ready views.

User: feedback and watchdog flags
Business: leadership priorities and roadmap signals
Support: bugs and tickets

Approach

I built this on my own time, tested it against real feedback channels at work, and shared it with the team. Connected the Slack API, designed the synthesis model, and shipped the whole thing.

01

Sweep by window

Period-bounded sweeps (7, 14, or 30 days) per channel. You pick the window, the system fetches only that slice. No firehose, no runaway token costs.

02

Synthesizes in priorities

Themes sorted into Act Now / Watch / Quiet, each with sentiment, area, and a next step. Every theme expands to its source messages so any claim traces back in one click.

03

Keep the receipts

Any theme pushes straight into a product project. At Raptive it let me create JIRA tickets from findings and surface what members were responding to.

Results

SHIPPED 2026

CHANNELS UNIFIED

3 to 1

TIME TO SIGNAL

Minutes vs Hours

CROSS FUNCTIONAL REACH

Design, product, and engineering on one source of truth

LLM COST

Limited by window caps and on-demand runs