Conversational analytics

Lens: Designing a standalone conversational analytics experience

Lens began as an analytics chatbot embedded within Oasis. When the product direction shifted to a standalone application, I designed a focused experience that allowed people to choose a project, understand the data in context, and bring that context into the conversation.

With a tight timeline, I established the interface foundations and developed a working prototype. The team used the prototype as a shared reference during handoff and implementation, helping move the product into its first standalone release.

Role: Product Designer
Product: Conversational analytics
Scope: Standalone direction through first release
Timeline: About one month

Before: Lens chatbot embedded within Oasis — Lens moved from a constrained embedded panel to a focused standalone experience.

After: Lens as a standalone conversational experience — Lens moved from a constrained embedded panel to a focused standalone experience.

Lens design-system components for project selection, context, buttons, cards, and the composer — I built a small design system with enough structure to move quickly without overbuilding it.

Production Lens interface showing a data-heavy conversational response

Where It Landed

Lens moved from a standalone concept to its first release within one month. The released experience remained closely aligned with the prototype, while production review identified follow-up changes for wider tables and data-heavy responses.

The project required me to set product direction before every detail was resolved, then guide the work through prototyping, handoff, and visual quality assurance.