From MVP to Ecosystem: Redesigning the Oscr AI Experience
Streamlining the research-to-publish workflow for global content creators through a three-tiered UX strategy.
My Role
UX Design Intern (End-to-End: User Research, Strategy, UI Design)
Team
1 Designer (Me), Founder (PM/Stakeholder), Engineering Team
Company
Oscr AI: Transform Any Content into a Blog or Social Post in Seconds.
Tools
Figma, Google Meet (Remote Testing), Notion
Introduction
Evolving an AI MVP into a Professional Workflow Tool
Oscr AI is a generative AI platform that empowers influencers and professionals to turn raw research into polished LinkedIn and blog posts. Following a successful launch and rapid user growth, the platform faced a critical challenge: the initial MVP features could no longer support the complex, evolving needs of its power users. My mission was to reimagine the user experience, transforming Oscr AI from a simple writing tool into a comprehensive content intelligence platform.
Stakeholder and Problem Statement
When User Demands Outpace Usability
As the user base expanded, so did the feedback. Users loved the core technology but found the workflow fragmented. They needed more than just text generation; they needed better ways to source data, manage references, and structure their arguments. The challenge was to integrate the new demands without overwhelming the user, specifically catering to professional influencers who prioritize accuracy and speed.
My Role and Responsibility
Bridging User Insights and Product Strategy
As the sole UX Designer on this project, I owned the entire design lifecycle. My responsibilities ranged from conducting international user research and defining the product roadmap with the founder to executing the final UI design. I acted as the bridge between client feedback and actionable development tasks, ensuring business goals aligned with user needs.
Process
Triangulating Insights through Global Contextual Inquiry
To truly understand the friction points, I employed a mixed-method research approach.
Stakeholder Interviews
I aligned deeply with the Founder, a super-user herself, to define the long-term product vision.
Qualitative Data Analysis
I analyzed hundreds of user support emails to identify recurring pain points and feature requests.
Remote Contextual Inquiry
I conducted screen-sharing sessions with users across Mexico, China, and Japan. By observing them perform real-world tasks, I uncovered unvoiced needs.
Design Goals & Solution
A Three-Tiered Strategy: Value, Architecture, and Interaction
To tackle the complexity of the platform, I categorized the design problems into three distinct scopes:
Tier 1
Strategic Value:
Jobs to be Done
Focused on the "Discovery Page" to help users manage RSS feeds and select multiple sources for synthesis, ensuring the output is always professional and current.
Tier 2
Information Architecture:
The Workflow
Redesigned the site structure to create a "One-Stop Service." I mapped the user flow to allow content collection, drafting, and publishing to happen seamlessly within a single interface, reducing context switching.
Tier 3
Interaction Design:
Usability
Improved the visual hierarchy of the "Create Blog Post" flow. I utilized Progressive Disclosure to keep the main interface clean, placing essential features front-and-center while tucking optional settings into intuitive menus.
Testing and Iteration
Rapid Validation with Power Users
Given the tight summer timeline, iteration happened in real-time. I used the Founder and a select group of beta users to validate the new "Knowledge Base" and "Search" flows immediately after wireframing. This allowed us to quickly pivot on feature prioritization, focusing on the "RSS Feed Management" which was crucial for influencers, while simplifying less critical UI elements to meet engineering deadlines.
Results and Impact
A Streamlined Ecosystem for Professional Creators
The redesign successfully shifted Oscr AI from a utility tool to a workflow hub. By reorganizing the information architecture, we significantly reduced the number of clicks required to go from "research" to "published post." The new UI establishes a professional visual language that builds trust with our B2B clients, and the modular design system allows the engineering team to scale new features without breaking the user experience.
Conclusion
Designing for Scalability under Technical Constraints
This project was a masterclass in balancing user desires with technical reality. For instance, while users requested "auto-updating" articles, technical constraints made this unfeasible for the sprint. Instead of ignoring this, I designed the UI layout to be "future-proof," reserving space for this feature to be easily added in later versions. This experience taught me that great UX isn't just about solving today's problems, but laying the groundwork for tomorrow's growth.
