solving context switching at sketchnote by bringing conversations into workspaces
user surveys highlighted chat as the most requested feature. users wanted discussions inside projects, not scattered across other tools.
timeline
2 months
team
1 design manager
1 ux designer
1 product manager
disciplines
product thinking
visual design
rapid prototyping
design system
context
sketchnote helped users manage tasks, docs and projects
slowed progress
constant context switch between tools
lost focus/context
flood of pings and scattered updates caused confusion
delayed decisions
wasted hours pushed users behind schedule
how we tackled it
chat view inside projects
dedicated chat tied to each project,
real-time updates that synced with tasks and docs,
markdown and file embeds to keep context intact,
mentions and notifications so critical updates reached the right people
before v/s after for bin charter in client dashboard
impact
+xx% engagement (confidential)️
validated user demand and improved satisfaction
reduced reliance on external messaging apps
positioned sketchnote as a more complete workspace
🌻 reflections
the strongest features come from listening to users. chat was not a reinvention but a clear response to a need.
listen → prioritize → ship → ++adoption
🌻 reflections
the strongest features come from listening to users. chat was not a reinvention but a clear response to a need.
listen → prioritise → ship → ++adoption
solving context switching at sketchnote by bringing conversations into workspaces
user surveys highlighted chat as the most requested feature. users wanted discussions inside projects, not scattered across other tools.
timeline
2 months
team
1 design manager
1 ux designer
1 product manager
disciplines
product thinking
visual design
rapid prototyping
design system
context
sketchnote helped users manage tasks, docs and projects
slowed progress
constant context switch between tools
lost focus/context
flood of pings and scattered updates caused confusion
delayed decisions
wasted hours pushed users behind schedule
how we tackled it
chat view inside projects
dedicated chat tied to each project,
real-time updates that synced with tasks and docs,
markdown and file embeds to keep context intact,
mentions and notifications so critical updates reached the right people
before v/s after for bin charter in client dashboard
impact
+xx% engagement (confidential)️
validated user demand and improved satisfaction
reduced reliance on external messaging apps
positioned sketchnote as a more complete workspace
🌻 reflections
the strongest features come from listening to users. chat was not a reinvention but a clear response to a need.
listen → prioritize → ship → ++adoption
🌻 reflections
the strongest features come from listening to users. chat was not a reinvention but a clear response to a need.
listen → prioritise → ship → ++adoption
solving context switching at sketchnote by bringing convos into workspaces
user surveys highlighted chat as the most requested feature. users wanted discussions inside projects, not scattered across other tools.
timeline
2 months
team
1 design manager
1 ux designer
1 product manager
disciplines
product thinking
visual design
rapid prototyping
design system
context
sketchnote helped users manage tasks, docs and projects
slowed progress
constant context switch between tools
lost focus/context
flood of pings and scattered updates caused confusion
delayed decisions
wasted hours pushed users behind schedule
how we tackled it
chat view inside projects
dedicated chat tied to each project,
real-time updates that synced with tasks and docs,
markdown and file embeds to keep context intact,
mentions and notifications so critical updates reached the right people
before v/s after for bin charter in client dashboard
impact
+xx% engagement (confidential)️
validated user demand and improved satisfaction
reduced reliance on external messaging apps
positioned sketchnote as a more complete workspace
🌻 reflections
the strongest features come from listening to users. chat was not a reinvention but a clear response to a need.
listen → prioritize → ship → ++adoption
🌻 reflections
the strongest features come from listening to users. chat was not a reinvention but a clear response to a need.
listen → validate -> prioritise → ship → ++adoption
other projects
simplifying complex fintech dashboards at vegapay for real banking impact
helping facebook sellers scale faster at springo by removing manual chaos
simplifying complex fintech dashboards at vegapay for real banking impact
helping facebook sellers scale faster at springo by removing manual chaos