Redesigning
Redesigning
Redesigning

Campus
Campus
Campus
Studio
E-Bike
E-Bike

Charging Experience
Charging Experience
Charging Experience
Redefining a campus e-bike charging system to address overcrowding, long wait times, and inefficient resource use.
Redefining a campus e-bike charging system to address overcrowding, long wait times, and inefficient resource use.

Problem
Problem
Problem
300M+ e-bikes are used daily in Chinese cities for commuting. On my university campus, the existing charging infrastructure created significant friction for students.
300M+ e-bikes are used daily in Chinese cities for commuting. On my university campus, the existing charging infrastructure created significant friction for students.
300M+ e-bikes are used daily in Chinese cities for commuting. On my university campus, the existing charging infrastructure created significant friction for students.
Details
Details
Details
Role: Product Designer (solo)
Duration: 8 weeks
Scope: Research, System mapping, UX, Interaction, UI
Role: Product Designer (solo)
Duration: 8 weeks
Scope: Research, System mapping, UX, Interaction, UI
Tools
Tools
Tools
Chapter 1
Chapter 1
Discovery
Discovery
Discovery
Obsevation
Interviews
System Mapping
ZOOM IN_USER BEHAVIOR
User Journey Map
I conducted four 30-minute field observations and mapped the end-to-end charging journey to identify the core problems.

Observations
Interviews
System Mapping

ZOOM IN_USER BEHAVIOR
User Journey Map
I conducted four 30-minute field observations and mapped the end-to-end charging journey to identify the core problems.
Observations
Interviews
System Mapping
ZOOM IN_USER BEHAVIOR
User Journey Map
I conducted four 30-minute field observations and mapped the end-to-end charging journey to identify the core problems.

Chapter 2
Chapter 2
Ideation
Ideation
Ideation

Chapter 3
Chapter 3
Design Development
Design Development
Design Development
User Flow
Sketch
Wireframes

User Flow
Sketch
Wireframes

User Flow
Sketch
Wireframes

Chapter 4
Chapter 4
Final Design
Final Design
Final Design


Chapter 5
Chapter 5
Business
Business
Business
Business Model
Service Blueprint
Stakeholder Map


Business Model
Service Blueprint
Stakeholder Map

Business Model
Service Blueprint


(What I learned)


The biggest challenge wasn't designing the solution, it was finding the right problem to solve.
I initially spent weeks analyzing individual user behaviors: when students charge, which stations they prefer, how long they stay. I had detailed personas and journey maps but no clear design direction.
The breakthrough came when I stepped back. Instead of optimizing user behavior, I mapped the entire campus charging system. The problem became obvious: 40% of stations sat idle in remote areas while students competed for central locations. The issue wasn't user behavior it was information distribution.
This taught me to always validate my problem frame before diving deep. Now I start every project by asking: "Am I solving the right problem at the right level?"

The biggest challenge wasn't designing the solution, it was finding the right problem to solve.
I initially spent weeks analyzing individual user behaviors: when students charge, which stations they prefer, how long they stay. I had detailed personas and journey maps but no clear design direction.
The breakthrough came when I stepped back. Instead of optimizing user behavior, I mapped the entire campus charging system. The problem became obvious: 40% of stations sat idle in remote areas while students competed for central locations. The issue wasn't user behavior it was information distribution.
This taught me to always validate my problem frame before diving deep. Now I start every project by asking: "Am I solving the right problem at the right level?"

The biggest challenge wasn't designing the solution, it was finding the right problem to solve.
I initially spent weeks analyzing individual user behaviors: when students charge, which stations they prefer, how long they stay. I had detailed personas and journey maps but no clear design direction.
The breakthrough came when I stepped back. Instead of optimizing user behavior, I mapped the entire campus charging system. The problem became obvious: 40% of stations sat idle in remote areas while students competed for central locations. The issue wasn't user behavior it was information distribution.
This taught me to always validate my problem frame before diving deep. Now I start every project by asking: "Am I solving the right problem at the right level?"
(Project)






