⚠️Disclaimer: This case study showcases early-stage designs. The platforms might have since evolved.
Product Manager, Lead LXD, Lead UX/UI Designer
Figma, Articulate Rise 360, Miro, Jira, WordPress, AWS, Google Analytics, xAPI/SCORM
Podcasting was growing rapidly in consumer markets, but schools couldn't safely adopt it, existing tools weren't designed for minors, assessment, or curriculum alignment. I founded Playpod.Education to close that gap: a multilingual, classroom-safe podcasting ecosystem combining a purpose-built web app, a comprehensive educator onboarding course, and an AI-powered content moderation layer. The result was a product that turned passive audio into a measurable learning tool — and won two international EdTech competitions in the process.
Playpod.Education is an award-winning EdTech startup I founded and led as Product Manager, and Lead UX/UI and Learning Designer. I owned the product vision, roadmap, and delivery of a multilingual podcasting platform designed for K–12 and higher education environments.
The goal was not simply to build a podcasting tool, but to enable safe, curriculum-aligned podcast creation in schools by addressing the real barriers to adoption: educator confidence, time constraints, and lack of institutional support. The platform combined a classroom-ready web app, educator onboarding through eLearning, and analytics-driven iteration. Pilot programs showed a 25% increase in engagement, validating the product direction.
Podcasting was rapidly growing in the consumer market, but educational institutions lacked the tools, training, and confidence to adopt it meaningfully in classrooms. Existing platforms were not designed for minors, assessment, or curriculum alignment, and professional development offerings were fragmented or overly technical.
Research across surveys, interviews, and pilot schools revealed that the biggest blockers were not feature gaps, but adoption friction and lack of structured guidance.
Key insights included:
70% of educators reported low confidence and limited time to adopt new technology
Schools wanted podcasting aligned to learning objectives and assessment, not just content creation
85% of parents wanted greater visibility into classroom projects and student learning
The insight that shaped everything: the biggest barriers weren't feature gaps. They were adoption friction and lack of structured pedagogical guidance. Building a better audio player wasn't the answer. Building a full learning ecosystem was. So rather than shipping a single tool, I defined an end-to-end product ecosystem that supported educators and students from first exposure to sustained classroom use.
The solution included:
A classroom-safe web app for recording and publishing podcasts
A self-paced eLearning course focused on pedagogical use, not just tooling
Job aids and support resources to reduce dependency on the platform
This approach intentionally prioritized activation and retention over advanced production features in early releases.
I led end-to-end learner and stakeholder research across K–12 and higher education contexts (surveys, educator interviews, and focus groups with school administrators and parents).
Key findings that directly shaped product and learning design decisions:
Educators needed clarity and confidence more than customization or advanced features. Overwhelming them with options during onboarding would replicate the same problem they had with existing tools.
Multi-device access was non-negotiable. Most educators engaged with professional development in fragmented windows (between classes, during lunch, on their phones). A desktop-only experience would fail before it launched.
Assessment integration was the critical differentiator. Teachers didn't just want students to make podcasts, they needed a way to connect the activity to curriculum standards and evaluate it. Without that, the tool was a hobby, not a classroom resource.
Delay advanced features until engagement metrics validated readiness
These findings led directly to a strategic decision: delay advanced production features until engagement metrics validated readiness, and invest first in the pedagogical framework and onboarding experience.
Strategy
Rather than shipping a single tool, I defined an end-to-end product ecosystem with three interconnected layers — each one designed to remove a specific adoption barrier:
A zero-install, classroom-safe platform for recording, publishing, and managing student podcasts. Privacy-by-design architecture meeting COPPA (U.S.) and GDPR (EU) requirements from day one. Automated word-by-word transcript synchronization turns passive listening into an active literacy tool — a UDL-aligned intervention that supports language acquisition and comprehension for diverse learners.
A self-paced onboarding course focused on pedagogical use, not tooling. Not "how to use the app" but "how to integrate podcasting meaningfully into your curriculum." Bite-sized learning architecture, a mentor character, gamified feedback, and a community forum — all designed to build educator confidence before they ever entered a classroom with the tool.
Automated content moderation that flags inappropriate material before it reaches students. This addressed the single biggest administrative barrier to school-wide adoption: the liability risk of unmoderated student-created content. By solving this at the infrastructure level, the platform became viable for institutional pilots where safety is non-negotiable.
Playpod's early website design
Snippet of the app's early flowchart and wireframes
Action Mapping
The design process began with action mapping, identifying the specific behaviors educators needed to perform in the classroom, not the information they needed to receive. This distinction is critical: most EdTech onboarding fails because it teaches the tool, not the practice. However, each layer of the learning ecosystem needed its own success metrics and goals. For this reasons, different Action Maps were developed to make sure progress and milestones would be accordingly placed to each layer
The mapping revealed three priority behavioral outcomes: launching a classroom podcasting project with confidence, integrating podcasting into existing curriculum structures, and evaluating student work against learning objectives. Every module in the course was traced back to one of these outcomes. Content that didn't directly support a behavior was removed or moved to optional resources.
Storyboard
A text-based storyboard served as the structural blueprint, capturing content, interactions, media notes, and feedback mechanisms before any development began. As the storyboard developed, I added multimedia links, scenario branches, and visual design notes.
A key storyboard decision: where in the course the learner would encounter challenge versus support. Cognitive load was managed deliberately — dense conceptual content was followed by scenarios and practice, never stacked consecutively.
Visual Design
After research and testing, I decided on cartoon-style visuals and characters, which were appropriate for both educators, and the student-facing product, which needed to feel school-friendly and approachable. But the eLearning course was targeted exclusively at adults.
Early user testing of visual concepts revealed a clear preference for learning "mentors characters". I responded by introducing a cartoon mentor characters to guide learners through the course, while retaining brand-consistent color and typography. The mentors created a sense of guided, personal learning in what could otherwise feel like an isolated self-paced experience, it also allowed users to see themselves in the process, as the mentors looked like they were either school learners or teachers.
The visual design followed the full Playpod brand system I had designed, colors, fonts, iconography, and component guidelines, ensuring coherence across the web app, the eLearning course, and supporting materials.
Development of the eLearning Course
The course was built in Articulate Rise 360, a deliberate choice over Storyline for this specific context. The course had substantial content across multiple modules, and Rise's responsive, mobile-first architecture was the right match for learners accessing it across devices on fragmented schedules. Storyline's greater customization wasn't needed here; what was needed was a clean, intuitive experience that didn't add friction on top of an already demanding learning task.
Engagement strategies embedded throughout:
Bite-sized sections with clear progress indicators
Scenario-based interactions requiring application, not just recall
Gamified feedback loops with visual rewards at module completion
Peer forum integration for sharing course outputs and building cross-school connections
Job Aid
A downloadable job aid was designed as a standalone classroom resource, available once learners completed the course. It contained step-by-step podcasting process guides, checklists, worksheets, and reference cards formatted for printing and classroom use.
The design decision here was deliberate: support materials that live outside the platform reduce dependency on it. An educator who can manage the process with a printed checklist is more confident, more autonomous, and more likely to sustain the practice. The goal was always capability, not platform reliance.
Final Deliverables & Results
Final deliverables: A live website, a web app, an eLearning course, job aids, and a branding kit.
Product outcomes:
25% increase in engagement metrics during pilot programs
Validated product-market fit across K–12 and higher education contexts in Europe
Awards:
1st Prize Winner in international startup competition Explorer by Santander X.
1st Prize Winner in national startup competition StartUB by University of Barcelona.
Semifinalists in national startup competition SpinUOC by Open University of Catalonia.
Awarded individual full-tuition scholarship from Babson College to complete a program in Business and Startup Management
Press Recognition
Here are a few national newspapers and magazines in Spanish that featured the project:
Key Takeaways
Three design decisions that shaped the outcome and that I carry into every project since:
Behavior before content. Action mapping revealed that most of the originally planned course content didn't connect to a specific classroom behavior. Cutting it made the course shorter, more focused, and significantly more effective. The instinct to add more is almost always wrong.
The ecosystem over the tool. The web app alone would not have driven adoption. The combination of a safe platform, a pedagogically grounded course, and self-sufficient job aids created conditions where educators could succeed without depending on ongoing support. Designing the full system, not just the product, was the strategic difference.
Safety as a design principle, not a compliance checkbox. The AI moderation layer and the privacy-by-design architecture weren't features added late to satisfy legal requirements, they were foundational decisions made at the product strategy stage. In institutional EdTech, trust is the product. Anything that threatens it fails, regardless of how good the learning experience is.