Exploring active learning systems for professional growth

5-Day Design Sprint · Research, concept development & validation

Challenge

Professional learning often remains theoretical and disconnected from real workplace situations.
The team explored how active learning experiences could help professionals apply learning more effectively within the context of their daily work.

Sprint Goal

Explore and validate a hands-on learning concept that could help professionals apply learning through real-world work.

Role

UX Researcher & Product Designer

Team

Cross-functional Design Sprint team

My Contribution

Ideation · Concept development · Pilot testing · User interview · Research Created the initial concept that the team refined and selected for prototyping.

Sprint Structure

BACKLOG → PLAN → UNDERSTAND → BRAINSTORM → CREATE → TEST → DEMO → ANALYSIS

DAY 1 — UNDERSTAND

To align the team around the problem space, we translated the broader vision for the MX Phase 2 initiative into a set of “How Might We” prompts designed to spark exploration and discussion.

These prompts focused on understanding how active learning could support professionals in real workplace situations.

PRIORITIZATION

Narrowing the focus

We first prioritized the problem areas using a Risk vs. Certainty matrix to identify which opportunities had the greatest strategic potential.
After selecting the research direction, we identified the underlying assumptions and prioritized which were most important to test.

RESEARCH QUESTION

How might we help professional members apply active learning in their unique work situations?

RESEARCH GOAL

Define how active learning experiences could better support professionals in real-world work environments.

FROM ASSUMPTIONS TO A TEST PLAN

We surfaced the assumptions behind the selected opportunity and prioritized those that posed the greatest risk.

2. For each priority assumption, we defined what it would mean if true or false, then translated it into questions and test activities.

DAY 2 — Brainstorm

To rapidly expand the solution space, the team focused on generating a wide range of possible approaches before narrowing into a single concept direction.

Rather than optimizing early, the sprint emphasized speed, divergence, and individual ideation to uncover unexpected opportunities around active learning in professional environments.

Framing the opportunity

Using the selected “How Might We” question as a foundation, the team explored different ways active learning could become more practical, collaborative, motivating, and relevant to workplace situations.

Sprint question

How might we help professional members apply active learning to their unique situations at work?

Divergent ideation

To encourage fast thinking and reduce attachment to initial ideas, each team member completed a rapid sketching exercise inspired by the Crazy 8s method.

The process was intentionally structured to prioritize quantity, variation, and momentum over polish.

Round 1. Initial exploration

Each participant generated:

8 unique concepts in 8 minutes
focused on different approaches to active learning experiences

The concepts explored themes such as:

collaborative learning
peer accountability
real-world practice
workplace simulation

Identifying promising directions

Instead of immediately converging as a group, participants first evaluated their own ideas individually.

This helped preserve originality and prevented stronger voices from influencing the direction too early in the process.

Selecting high-potential concepts

Each participant selected their top 3 concepts based on:

strategic potential
uniqueness
feasibility within the sprint
relevance to workplace learning behaviors

Rapid concept exploration focused on uncovering multiple approaches to active learning in workplace environments.

Rapid iterations based on the strongest emerging concepts from the first exploration round.

Expanding stronger ideas

Using the selected concepts as creative anchors, the team completed a second rapid ideation round.

Round 2. Iteration & amplification

Each participant generated:

8 additional concepts in 8 minutes
building upon their strongest previous ideas

This phase shifted the process from broad exploration into deeper concept development, allowing stronger patterns and themes to emerge across the team.

Converging on a concept direction

After reviewing the expanded concept set, the team evaluated recurring themes, strategic opportunities, and overall resonance with the sprint goal.

My initial concept became the foundation for the direction the team collectively refined and selected for prototyping.

Concept voting

The team voted on the concepts that demonstrated the strongest potential to:

support real-world active learning
create meaningful engagement
encourage collaboration and accountability
fit naturally into professional environments
provide enough depth to prototype and test within the sprint timeline

The selected concept became the foundation for the prototype explored in the following stages of the sprint.

The team evaluated concept potential based on engagement, feasibility, and relevance to professional learning behaviors.

DAY 3 — Define

With a concept direction selected, the sprint shifted from exploration into structure.

The team focused on defining how the experience would function, how members would interact with the system, and how active learning could translate into practical workplace application.

Rather than designing polished interfaces immediately, the priority was establishing the underlying logic, workflows, and learning experience framework needed to support the prototype.

Concept direction

Real-World Challenge Marketplace

The selected concept explored a collaborative learning environment where professionals could bring real workplace challenges into a shared active-learning system, apply their skills, and learn through solving problems together.

Members would:

submit real workplace situations
collaborate with others through guided exercises and workshops
explore alternative decisions and outcomes
reflect on previous experiences
document growth over time

The goal was to connect learning directly to real professional situations rather than isolated educational content.

Rapid prototype

The prototype was generated rapidly in Lovable to test the interaction model and workflow. Some sample challenge content extended beyond the intended workplace context; testing focused on the underlying marketplace and active-learning experience rather than the specific challenge topics.

Defining the experience framework

To prepare the concept for prototyping, the team translated the idea into a structured participation model and defined the core system requirements needed to support the experience.

The platform was intentionally designed to feel lightweight, collaborative, and continuously active.

Participation model

To reduce friction and encourage exploration:

users could browse challenges immediately
the prototype avoided mandatory login requirements
members could quickly enter active learning experiences without complex onboarding

The marketplace acted as a public space where professionals could:

explore workplace challenges
submit new problems
observe ongoing sprint activity
join collaborative learning experiences

Challenge lifecycle

The experience centered around a structured challenge workflow designed to support collaborative active learning.

Challenge submission

Members submit real workplace problems they want help solving.

Community voting

Community members vote on which challenges should move forward into active learning sprints.

Team formation

Once activated, members of the community can join a sprint team.

The system supported:

up to 5 participants per team
one or two teams working on the same challenge simultaneously

This created opportunities for multiple perspectives and parallel problem-solving approaches.

Sprint framework

Once a team reached capacity, the sprint officially began.

Each team moved through a simplified Google Design Sprint structure:

Understand
Brainstorm
Create
Test
Demo

This framework transformed workplace learning into an active, participatory process grounded in real professional situations.

Reflection & visibility

A major focus of the concept was making learning visible over time.

Teams could post:

reflections
learnings
progress updates
evolving ideas throughout the sprint

These reflections became visible to the broader community, allowing others to learn from active challenges and observe different approaches to problem-solving.

The platform also tracked challenge iterations, showing how ideas evolved across multiple sprint cycles.

Challenge statuses

To support transparency and participation, the system required clear challenge states from the end-user perspective.

Users could view:

challenges open for voting
team formation stages
active sprints in progress
testing and demo phases
completed challenges
current iteration numbers

This helped position the platform as a living ecosystem of continuous collaborative learning rather than a static educational experience.

Rapid prototyping

With the experience framework established, the team moved into rapid prototyping.

Using Lovable, the team quickly translated the concept, flows, and participation model into an interactive prototype that could be tested within the sprint timeline.

The prototype focused on validating:

challenge discovery
participation flow
sprint progression
visibility of collaboration and reflection
overall understanding of the active learning model

Rather than building a polished production-ready product, the prototype prioritized speed, clarity, and concept validation.

Interactive prototype

We translated the selected concept into an interactive prototype to test the challenge workflow, participation model, and active-learning experience.

View interactive prototype

Strategic direction

The concept reframed professional learning as:

collaborative rather than isolated
action-oriented rather than passive
iterative rather than one-time
grounded in real workplace experiences

By connecting learning directly to real professional situations, the platform aimed to make active learning more practical, contextual, and immediately applicable.

DAY 4 — Test

With the prototype defined, the sprint shifted into validation.

The focus of Day 4 was understanding whether the concept could realistically support active learning behaviors in professional environments and whether participants understood the value of the experience.

Rather than evaluating visual polish, the team focused on:

usability
clarity of the concept
participation flow
perceived value
alignment with real workplace behaviors

Building the research framework

Before testing the prototype, the team developed a structured research plan to guide the sessions and ensure findings could be consistently documented and evaluated.

The research plan included:

research goals
research questions
assumptions
participant criteria
testing methodology
facilitator scripts
observation measurements
task structure

The goal was to create a repeatable framework for evaluating whether the concept effectively supported active learning within professional contexts.

Pilot testing

Before launching live sessions, the team conducted pilot tests to refine:

task clarity
facilitation flow
interview pacing
observation methods
prototype interactions

This helped identify areas where instructions, questions, or flows needed adjustment before testing with real participants.

User testing sessions

The team then conducted moderated usability and concept-testing sessions with four participants using the interactive prototype.

Participants were guided through realistic scenarios designed to evaluate:

understanding of the marketplace concept
willingness to participate in collaborative challenges
perceptions of active learning
motivations for joining workplace sprints
reactions to public reflection and collaboration features

The sessions combined:

task-based usability testing
generative research questions
behavioral observation

This allowed the team to evaluate both:

interaction usability
broader perceptions of the learning model itself

Structured observation tracking

To capture patterns consistently across sessions, the team developed a combined Questions / Tasks / Observation Measurements framework.

This system helped document:

participant behaviors
confusion points
expectations
reactions to challenge workflows
interpretation of active learning concepts
motivation and engagement signals

The framework created a structured way to compare observations across participants and identify recurring themes throughout the testing process.

Research focus areas

The testing sessions explored several critical questions:

Marketplace understanding

Did participants understand the purpose of the challenge marketplace and how challenges progressed through the system?

Active learning perception

Did the experience feel collaborative, practical, and connected to real workplace situations?

Participation motivation

Would professionals feel motivated to join active learning challenges with other community members?

Reflection & visibility

How did participants respond to visible reflections, public collaboration, and iteration tracking?

Workflow clarity

Could participants understand challenge statuses, sprint progression, and participation flow without heavy onboarding?

DAY 5 — Demo

Synthesizing the findings

Following user testing, a team member used AI-assisted analysis to synthesize findings across participants, evaluate the assumptions we tested, and identify implications for the concept.

Sharing the outcome

The synthesis was presented during the final Demo, giving the team an early view of which assumptions showed strong support, which remained uncertain, and which required reconsideration.

Post-Spint-UX Synthesis and recommendations

After the sprint, I revisited the original participant data through a UX and product-design lens, focusing on concept comprehension, project workflow, professional relevance, active-learning value, and barriers to participation.

Key Findings

Concept comprehension
The concept was not immediately clear; participants often needed to explore the site before understanding how it worked.
Active-learning value
Only 2/4 participants clearly connected the concept to active learning. The hands-on learning value was present but not communicated explicitly.
Professional relevance
Participants saw potential value, but none viewed the current experience as highly relevant to their own professional development. Relevance depended on skills, roles, interests, and career needs.
Project workflow
Participants generally understood the workflow after exploration, but terminology, statuses, and transitions created confusion.
Trust & commitment
Participation depended not only on finding an interesting project but also on confidence that teams would stay committed and projects would lead to real outcomes.

Design Recommendations

Clarify the value proposition
Explain what Test Track is, who it is for, and how participation works immediately on entry.
Make professional learning visible
Show the skills participants will use, develop, and demonstrate through each project.
Improve project matching
Allow people to discover projects by skills, role, professional area, topic, and project stage.
Make the workflow explicit
Clarify how problems progress from submission and voting through team formation, active work, testing, and completion.
Build trust through evidence
Show project ownership, completed projects, outcomes, success stories, and evidence of follow-through.

Strategic outcome

The concept showed potential as a project-based learning model, but testing revealed that professional value, project relevance, workflow, and evidence of outcomes need to be clearer before expanding the experience to experienced professionals.

Next Steps

Next, I plan to translate the research findings and recommendations into an updated prototype and conduct a second round of testing. The study will retain key benchmark tasks from Round 1 while introducing targeted scenarios to evaluate concept comprehension, professional relevance, workflow clarity, and trust.

Page updated

Google Sites

Report abuse