Visualizer — map the case

Every node is a stakeholder concern, constraint, or design move. Edges show which concerns pull on each other. Click a node to read it; add a new node to extend the case with a worry the original doesn't capture. Nodes connected by an edge are the ones you need to think about together.

How to read this map

Each case is a design problem viewed through three stakeholders. Switch lenses (Teacher → IT Systems → Students) to see how the same tension looks from each side — they pull on each other, so no single view is enough.

  • Teacherwhat they plan and decide.
  • Studentswhat learners actually experience.
  • IT Systemswhat the tools allow or block.
  • Administrationwhat policy and resources allow.

Start here

Create or Choose a Case

Instructor

System topology

Proposal network

Teacher focus Needs attention
관점

D3 force graph

Live swarm topology Hover a node to inspect an issue. Click a stakeholder node to shift the active lens.
Instructional signals What the teacher intends — objectives, lesson moves, pedagogical goals.
Constraint friction Where real constraints — time, tools, policies, workload — collide with that intent.
Aligned evidence Evidence from teachers, students, or IT systems that supports (or challenges) a design move.

Your question will be added to the cohort graph. Your instructor and classmates can see it.

Swarm activity

0

Perspectives — read the case through one person's eyes

Pick a stakeholder pill (teacher, student, administrator, parent, etc.). Everything on this page re-reads the case as that person: the left panel lists what they are worried about, the orbit on the right shows which concerns circle their attention, and the chat on the bottom-right lets you ask a question and get an answer framed in their voice — "what would the teacher say about this?" Switching the lens changes all three at once. Use it to find who you're designing against.

People in the case

Key concerns

점수는 어떻게 나오나요?

각 숫자(0–100)는 케이스의 네 가지 기본 지표 — 개인화·교사 업무 부하·프라이버시·접근성 — 를 정해진 가중치로 합친 추정값이에요. 예를 들어 실행 가능성은 업무 부하가 낮고 프라이버시·접근성이 높을수록 올라가요. 정밀한 측정이 아니라, 어디를 더 깊이 논의하면 좋을지 가리키는 상대적 신호로 봐 주세요.

Current focus

Teacher orbit

school
High instructional load and facilitation burden.
LMS
Peer review
Assessment

Trade-offs — what moves together

Instructional design moves are almost never free. Push personalization up, and teacher load usually goes up with it. Tighten privacy, and personalization often drops. This radar shows the five dimensions locked together in this case. The decision log on the right records every adjustment you made and which dimensions shifted as a result — so you can see the cost of each decision.

Trade-offs

What changes together

Balanced
Personalization
Privacy
Accessibility
Feasibility
Teacher Load

Sandbox — test a what-if

Drag the sliders to push a single dimension and see what breaks elsewhere. Turn autonomy on to let the system suggest redesign moves before you accept them. Changes here are for exploration — nothing is committed to the case until you confirm. Use this when you want to try a bolder design move without rewriting the whole case first.

Test changes

Adjust the case

Autonomous iteration

Allow the system to suggest redesign moves before instructor review.

Stress scenarios

System response

What changes after the adjustment

Stable
hub 81%

Alignment cohesion

psychology High

Cognitive load

speed 14ms

Response time

Report — write up what you learned

This is where you pull the whole case together. The summary, evidence list, and reflection prompts are generated from the nodes and decisions you made in the other views. Your written reflections are submitted to your instructor and shape how they read your module design. If you are an instructor, you'll also see the class cohort panel here to watch who's moving through the case.

Case report

Draft the summary

Executive summary

Priority tensions

Recommended redesign moves

Evidence trace