Conversational analytics

Lens: Designing a standalone conversational analytics experience

Defined and prototyped Lens’s standalone experience as the product moved beyond its original role as an Oasis chatbot.

Lens standalone conversational analytics interface

Lens began as an analytics chatbot embedded within Oasis. When the product shifted to a standalone application, I designed an experience that enabled users to select projects, understand their data context, and carry that context into conversations.

With just one month to release, I established a lightweight interface foundation and built a functional prototype that guided engineering implementation. The shipped experience closely reflected that direction.

Role
Lead Product Designer
Product
Conversational analytics
Scope
Standalone direction through M1 release
Timeline
June - July 2026
Before: Lens chatbot embedded within OasisAfter: Lens as a standalone conversational experience
I redesigned the experience around project selection, data context, and conversation flow as Lens evolved from an embedded chatbot into a standalone product.
Lens design-system components for project selection, context, buttons, cards, and the composer
With one month to launch, I prioritized the core conversational experience and essential system feedback, deferring advanced chat controls and sophisticated thinking interactions until their functionality was defined.
Production Lens interface showing a data-heavy conversational response
Following stakeholder feedback during production review, I refined the chat layout with wider responses and tables, introducing contained horizontal scrolling to better support data-heavy conversations.

Where It Landed

Lens shipped as a standalone product in approximately one month. My contributions spanned experience design, functional prototyping, implementation handoff, and post-release refinement.