EdTech Hub Redesign
Redesign the Community Feature for a Tech Learning Platform
Redesign the Community Feature for a Tech Learning Platform
Role
Role
UX Strategy · Research
Task Management
Profile Page, Chatroom and Challenge Board Design
Final Pitch Deck
Tools
Tools
Figma
Discord
Asana
Zoom
Miro
Team
Team
Aurora zhang
Da Eun (Grace) Sim
Elisha Park
Liz Little
Tanmayee pemmaraju
Timeframe
Timeframe
Feb 2024
EdTech Hub Redesign
Redesign the Community Feature for a Tech Learning Platform
Role
UX Strategy · Research
Task Management
Profile Page, Chatroom and Challenge Board Design
Final Pitch Deck
Tools
Figma
Discord
Asana
Zoom
Miro
Team
Aurora zhang
Da Eun (Grace) Sim
Elisha Park
Liz Little
Tanmayee pemmaraju
Timeframe
Feb 2024
SkillSpace Hackathon
Our team of 6 professionals was spread across two North American time zones, meeting for the first time at this hackathon.
Our team of 6 professionals was spread across two North American time zones, meeting for the first time at this hackathon.
SkillSpace Hackathon
Our team of 6 professionals was spread across two North American time zones, meeting for the first time at this hackathon.
450+
Participants
Global Reach
450+
Participants
Global Reach
34
Teams
Fierce Competition
34
Teams
Fierce Competition
11
Mentors
Expert Feedback
11
Mentors
Expert Feedback
48
Hours
Tight Excution Timeline
48
Hours
Tight Excution Timeline
"Constraints are where creativity thrives. Great design happens when we focus on solving the right problems with clarity, strategy, and teamwork."
"Constraints are where creativity thrives. Great design happens when we focus on solving the right problems with clarity, strategy, and teamwork."
Key Takeway
Key Takeway
Aurora
"Constraints are where creativity thrives. Great design happens when we focus on solving the right problems with clarity, strategy, and teamwork."
Key Takeway
Aurora
In a 48-hour Hackathon by Liftyz and Design Buddies, we chose SkillSpace, a platform for tech professionals, as our challenge. Our mission: Redesign the Community Page to enhance user engagement, connection, and collaboration.
In a 48-hour Hackathon by Liftyz and Design Buddies, we chose SkillSpace, a platform for tech professionals, as our challenge. Our mission: Redesign the Community Page to enhance user engagement, connection, and collaboration.
Problem
236 Tech Professionals from survey shared their struggles：
Learning alone left users disconnected.
Problem
236 Tech Professionals from survey shared their struggles：
Learning alone left users disconnected.
Problem
236 Tech Professionals from survey shared their struggles.Learning alone left users disconnected.
0%
Feeling disconnected
Prefers interactive & gamified participation.
0%
Feeling disconnected
Prefers interactive & gamified participation.
0%
Lack of networking
Needs community-driven engagement.
0%
Lack of networking
Needs community-driven engagement.
0%
Wanted real-time collaboration
Wants live discussions & immediate feedback.
0%
Wanted real-time collaboration
Wants live discussions & immediate feedback.
0%
Feeling disconnected
Prefers interactive & gamified participation.
0%
Lack of networking
Needs community-driven engagement.
0%
Wanted real-time collaboration
Wants live discussions & immediate feedback.
I learn better with others. But right now, I feel isolated.”
I learn better with others. But right now, I feel isolated.”
I learn better with others. But right now, I feel isolated.”
Key Needs: Networking opportunities, engaging community, and professional growth.
Key Needs: Networking opportunities, engaging community, and professional growth.
Key Needs: Networking opportunities, engaging community, and professional growth.
Annie Bassett
Annie Bassett
Annie Bassett
Project manager
Project manager
The Challenge
What We Faced
Our constraints became our design drivers: speed, clarity, and adaptability.
The Challenge
What We Faced
Our constraints became our design drivers: speed, clarity, and adaptability.
48 hours
48 hours
Completing research, ideation, and design in just 48 hours.
Collaboration Limits
Collaboration Limits
Only 4 overlapping hours per day
Only 4 overlapping hours per day
Feature Scope
Feature Scope
We risked shipping more
We risked shipping more
48 hours
Completing research, ideation, and design in just 48 hours.
Collaboration Limits
Only 4 overlapping hours per day
Feature Scope
We risked shipping more
From my audit, I found 4 friction points limiting engagement: Discoverability, Collaboration, Personalization, and Course Structure
Feature and Design System Audit
Feature and Design System Audit
Post-hackathon clarity (Future Pro Plan)
Post-hackathon clarity (Future Pro Plan)
We generated many ideas, but not all fit a clear flow. After the event, I re-evaluated features using a behaviour model and business value.
The Workplace Tool had long-term value but was too complex and costly for the short term, better suited for a future Pro Plan.
In the 48h sprint, we should have focused more on community-driven engagement.
So I clarified priorities:
So I clarified priorities:
From my audit, I found 4 friction points limiting engagement: Discoverability, Collaboration, Personalization, and Course Structure
Feature and Design System Audit
Post-hackathon clarity
(My Reflection)
During the sprint we generated many ideas, but not all fit into a clear flow. After the event, I re-evaluated features using a behaviour model and business value. I realized:
The Workplace Tool showed long-term value, but I deprioritized it due to technical complexity and cost. It didn’t align with short-term business goals and was better suited for a future Pro Plan.
But in the 48h sprint, we should’ve focused more on community-driven engagement
So I clarified priorities:
Loading...
How we collaborate
From Chaos to Clarity
How we collaborate
From Chaos to Clarity
Adapting Fast to a Live Design System
Adapting Fast to a Live Design System
Adapting Fast to a Live Design System
We didn’t design a new system. We adapted to SkillSpace’s existing component library for speed and clarity.
We didn’t design a new system. We adapted to SkillSpace’s existing component library for speed and clarity.
Small Changes. Big Alignment
Small Changes. Big Alignment
Small Changes. Big Alignment
In the first 12 hours, we struggled with misalignment and big discussions.
To move forward fast, we introduced three clear steps:
In the first 12 hours, we struggled with misalignment and big discussions.
To move forward fast, we introduced three clear steps:
Messaging for quick updates
Messaging for quick updates
Messaging for quick updates
Daily check-ins on Zoom for team-wide clarity
Daily check-ins on Zoom for team-wide clarity
Daily check-ins on Zoom for team-wide clarity
Calendly syncs for uninterrupted focus blocks
Calendly syncs for uninterrupted focus blocks
Calendly syncs for uninterrupted focus blocks
Remote Execution. Maximum Impact.
Remote Execution. Maximum Impact.
Remote Execution.
Maximum Impact.
We structured our sprint using agile practices:
We structured our sprint using agile practices:
Asana Plugin to split tasks into Backlog, In Progress, Review, and Completed
Figma to co-design directly and speed up decision-making
Clear ownership for each deliverable ensured rapid, efficient handoffs
Asana Plugin to split tasks into Backlog, In Progress, Review, and Completed
Figma to co-design directly and speed up decision-making
Clear ownership for each deliverable ensured rapid, efficient handoffs
My solution
Translating Insights Into Design
Translating
Insights Into Design
My solution
Translating Insights Into Design
New Feature Video Made By Myself
New Feature Video Made By Myself
Learn. Build. Thrive
Learn. Build. Thrive
Learn. Build. Thrive
Join events, take on challenges, and collaborate in real-time.
Track your career progress with gamified milestones, peer reviews, and project showcases—stay engaged and grow your skills.
Join events, take on challenges, and collaborate in real-time.
Track your career progress with gamified milestones, peer reviews, and project showcases—stay engaged and grow your skills.
Join events, take on challenges, and collaborate in real-time.
Track your career progress with gamified milestones, peer reviews, and project showcases—stay engaged and grow your skills.
01
01
Discover
Discover
Discover
02
02
Join
Join
Join
03
03
Collaborate
Collaborate
Collaborate
04
04
Submit
Submit
Submit
05
05
Feedback
Feedback
Feedback
Community Challenges/Gamified Profiles
Seamless Learning with Live Interaction
Seamless Learning with Live Interaction
Seamless Learning with Live Interaction
Why it matters?
Why it matters?
Why it matters?
For learners : Build skills, grow network, get recognition
For business : Increase retention & monetization through engagement
For learners : Build skills, grow network, get recognition
For business : Increase retention & monetization through engagement
My Reflection
My Reflection
This sprint taught me more than just fast design.
We were six people who had never worked together, and had only 48 hours. So at the beginning, it got a bit messy, too many ideas, unclear roles, and lots of open discussion.
Midway, we realized we needed structure.
We set up a task board, checked in daily, and made sure everyone had a clear part to lead. That helped us move forward faster.
We delivered a working solution.
But after the event, I looked back and realized some features didn’t connect well. So I mapped out a clearer task flow, re-prioritized what really mattered, and proposed a future direction (like the Pro Plan).
One thing I’d do earlier next time?
Spend more time at the start to understand how everyone works, and what they’re good at. That small step would’ve saved us time and stress later on.
In the end, we didn’t just build a demo.
We learned how to work better as a team.
This sprint taught me more than just fast design.
We were six people who had never worked together, and had only 48 hours. So at the beginning, it got a bit messy, too many ideas, unclear roles, and lots of open discussion.
Midway, we realized we needed structure.
We set up a task board, checked in daily, and made sure everyone had a clear part to lead. That helped us move forward faster.
We delivered a working solution.
But after the event, I looked back and realized some features didn’t connect well. So I mapped out a clearer task flow, re-prioritized what really mattered, and proposed a future direction (like the Pro Plan).
One thing I’d do earlier next time?
Spend more time at the start to understand how everyone works, and what they’re good at. That small step would’ve saved us time and stress later on.
In the end, we didn’t just build a demo.
We learned how to work better as a team.
