Summary
I led research into how teams shared wireframes and managed feedback, then worked with product, design, and engineering to prioritise and refine commenting improvements. After the April 2026 launch, a higher share of active editors created comments or replies.
The challenge
Internal analysis found longer retention and higher average revenue among team accounts. With unlimited seats and pricing based on project capacity, the team saw an opportunity to make the product more useful to customer teams. We wanted to understand what prevented people from involving colleagues and keeping feedback connected to their designs.
Participants described manually connecting discussions across tools. Inside the editor, comments could be difficult to find, follow, and relate to the relevant part of a wireframe.
My approach
I conducted eight discovery interviews and reviewed customer evidence and analytics, alongside competitive analysis and a heuristic evaluation. The research identified needs across sharing, component reuse, navigation, and feedback management. I brought these findings into team discussions, where we prioritised comments as an opportunity to make feedback easier to follow and encourage teammate participation.
I brought recommendations into team discussions throughout development. Testing successive versions let me assess how the experience was changing and work through findings with design and engineering.
One example concerned locating a comment on the canvas. Persistent callouts improved visibility, but users still had a small target inside each comment to select its position. I raised the problem; engineering proposed making the whole comment clickable, design agreed, and the change appeared in the next feature preview.
Usability testing also exposed confusion about resolved-comment filters. I worked through those observations with the team to inform revisions to the controls. In 2026, I evaluated the evolving experience through five prototype sessions and collaborated with the team to interpret findings and explore design changes.
This work connected the broader collaboration problem with specific interface behaviour. Research identified the difficulties; design and engineering contributed solutions and implementation choices.
Results
The team implemented changes to comment visibility, navigation, and management informed by the research. The findings also informed work on a project-wide comments panel and notification system in 2026.
These post-launch figures describe a shared product outcome. They do not isolate research’s contribution or establish an effect on retention or revenue.
In future work, I would distinguish creators from reviewers more explicitly in recruitment, keep a clearer record of tested versions and decisions, and agree measures of teammate participation alongside delivery.