About Me
About Me
mifan.contact@gmail.com
Hi, I'm Mi Fan.
In front of my desk there’s a small command center: a monthly calendar with post-its, a handwritten weekly list, and a daily notebook for time and tasks.
I design experiences that turn complex goals into something people can actually run, in learning contexts and beyond. Modules, activities, evaluation tools, workflows. Different outputs, same obsession: clarity and real-world practice.
A quick story that explains how I work
I learn fast when the stakes are real. During the 19th Asian Games, I stepped into a stakeholder-heavy role with almost no runway. Requirements kept shifting, and “special requests” kept appearing outside the guidebook.
So I did what I always do: listen, map the system, and write it down. I built a shared ops plan to make ownership visible, plus a team-size calculator to turn changing demands into staffing decisions.
I enjoy learning new little skills.
I collect hobbies the way some people collect souvenirs, a little proof I was there and tried.
· Currently: tennis
· On the shelf: drums
· Small obsession: penguin plushies
In another life, I’m an Overcooked strategist
I’m the planner and the loud one. I call plays, keep timing tight, and try to keep the kitchen from exploding without ending the friendship.
That's also me.
That‘s me.
If you work with me…
Week 1 looks like this
☐Day 1: Learn the system
People, processes, tools, constraints
☐Day 2: Listen + define success
Align on the outcome and priorities.
☐Day 3: Draft the plan
Workflow, milestones, owners, timeline.
☐Day 4: Reflect + refine
Align on the outcome and priorities.
☐Day 5: Week 1 packet
Recap, confirm priorities, 30-60-90 plan
Hi, I'm Mi Fan.
In front of my desk there’s a small command center: a monthly calendar with post-its, a handwritten weekly list, and a daily notebook for time and tasks.
I design experiences that turn complex goals into something people can actually run, in learning contexts and beyond. Modules, activities, evaluation tools, workflows. Different outputs, same obsession: clarity and real-world practice.
In another life, I’m an Overcooked strategist
I’m the planner and the loud one. I call plays, keep timing tight, and try to keep the kitchen from exploding without ending the friendship.
That's also me.
That‘s me.
A quick story that explains how I work
I learn fast when the stakes are real. During the 19th Asian Games, I stepped into a stakeholder-heavy role with almost no runway. Requirements kept shifting, and “special requests” kept appearing outside the guidebook.
So I did what I always do: listen, map the system, and write it down. I built a shared ops plan to make ownership visible, plus a team-size calculator to turn changing demands into staffing decisions.
If you work with me…
Week 1 looks like this
☐Day 1: Learn the system
People, processes, tools, constraints
☐Day 2: Listen + define success
Align on the outcome and priorities.
☐Day 3: Draft the plan
Workflow, milestones, owners, timeline.
☐Day 4: Reflect + refine
Align on the outcome and priorities.
☐Day 5: Week 1 packet
Recap, confirm priorities, 30-60-90 plan
I enjoy learning new little skills.
I collect hobbies the way some people collect souvenirs, a little proof I was there and tried.
· Currently: tennis
· On the shelf: drums
· Small obsession: penguin plushies
Hi, I'm Mi Fan.
In front of my desk there’s a small command center: a monthly calendar with post-its, a handwritten weekly list, and a daily notebook for time and tasks.
I design experiences that turn complex goals into something people can actually run, in learning contexts and beyond. Modules, activities, evaluation tools, workflows. Different outputs, same obsession: clarity and real-world practice.
In another life, I’m an Overcooked strategist
I’m the planner and the loud one. I call plays, keep timing tight, and try to keep the kitchen from exploding without ending the friendship.
That's also me.
That‘s me.
A quick story that explains how I work
I learn fast when the stakes are real. During the 19th Asian Games, I stepped into a stakeholder-heavy role with almost no runway. Requirements kept shifting, and “special requests” kept appearing outside the guidebook.
So I did what I always do: listen, map the system, and write it down. I built a shared ops plan to make ownership visible, plus a team-size calculator to turn changing demands into staffing decisions.
If you work with me…
Week 1 looks like this
☐Day 1: Learn the system
People, processes, tools, constraints
☐Day 2: Listen + define success
Align on the outcome and priorities.
☐Day 3: Draft the plan
Workflow, milestones, owners, timeline.
☐Day 4: Reflect + refine
Align on the outcome and priorities.
☐Day 5: Week 1 packet
Recap, confirm priorities, 30-60-90 plan
I enjoy learning new little skills
I collect hobbies the way some people collect souvenirs, a little proof I was there and tried.
· Currently: tennis
· On the shelf: drums
· Small obsession:
penguin plushies