Experience architecture
Cross-product integrations
Interaction design
Concept testing
Workflow optimization
tldr;
35
%
50
%
9
%
We treat these numbers as signals of more connected workflows and stronger shared momentum.
More same-day decisions
Continuous collaboration
Fewer follow-ups needed
Teams use Aha! to innovate and build products but they use Slack to communicate about them. Those conversations often spark the need to capture ideas, detail requirements, or comment on roadmap plans.
– CS Manager
what we built
We shipped an integration that keeps conversation and product strategy in sync.
Teams can now subscribe to strategic updates from Aha! to be delivered directly into Slack channels. Everyone can stay aligned without leaving the place where product conversations are already happening.
– Principal PM
Users can post comments to Aha! directly from Slack to keep discussions tied to the right records. This ensures context is preserved and decisions stay actionable.
The drop in stranded comments reflected a boost in engagement and responsiveness.
STRANDED COMMENT DROP RATE
9.4
%
before Slack integration
2.1
%
after Slack integration
We also looked at comments in Aha! that took 24+ hours to receive a reply.
SPEED TO COMMENT IMPROVEMENTS
25
%
before Slack integration
12
%
after Slack integration
Team communication had become more connected with fewer messages left unaddressed.
– Customer
Users can quickly create Aha! records right from Slack using slash commands or message shortcuts, capturing insights in the moment without interrupting the conversation.
– Senior PM
how we got there
12
user interviews
Curious if customers faced the same challenge, we reached out to some of our more active users and confirmed that Slack was central to how their teams discuss product work.
3
key insights
2k
comment threads analyzed
discovery goal
Identify where teams felt the most friction when moving between conversations and structured product work
PRODUCT GOAL
Identify which gaps were worth closing first
We focused on three core problem areas.
01
Context switching weakened the connection between conversations and the product work they referenced.
Observed friction
Discussions about product work were split across Aha! and Slack. This forced users to jump between tools, breaking focus.
Design intent
Reduce switching and its costs. Keep product context embedded directly in the conversation.
what we delivered
An integration that posts Aha! record updates and enables in-thread record creation, reducing switching and keeping teams aligned in one place.
Our focus was on intentional mappings to Aha! from the Slack interface.
02
Critical updates competed with high-volume, low-context messages.
Observed friction
Important product updates were buried in busy Slack channels, making it difficult for teams to align on what had changed or what required attention.
Design intent
Increase the visibility of key changes by delivering structured updates that stand out in busy channels.
what we delivered
A high-signal update feed with distinct notification posts for key changes.
03
Stranded comments were a visibility failure. It was as simple as that.
Observed friction
Asynchronous comments fragmented conversation across teams and time zones, leaving threads unanswered and decisions delayed.
Design intent
Encourage teams to contribute to product conversations directly from Slack without losing context.
what we delivered
A streamlined reply flow that keeps threads moving, alerting users in Slack and allowing them to respond to Aha! comments.
next steps
We heard feedback that the integration added more noise than expected. That matters — attention is finite, and good integrations should reduce cognitive load, not add to it. It reinforced a familiar lesson: even thoughtful design choices come with tradeoffs, especially in complex B2B workflows. Sometimes it takes more than one pass to land on the right defaults for most teams.
I've proposed granular notification controls so teams can fine-tune what posts to Slack and when. I believe this would provide the flexibility to reduce noise while preserving the product context that makes the integration valuable.
reflection
Collaboration as core to the design process
Building an integration that spanned product, engineering, security, and co-founders took more than polished UI. It required steady alignment, clear communication, and shared clarity on what mattered most. By partnering closely with each team, we delivered a solution that met user needs while respecting technical constraints, security requirements, and business priorities.