Visualizer — map the case

Each node represents a stakeholder concern, constraint, or design decision. Connections show how they relate. Select a node to read it, or add a concern missing from the original case.

How to read this map

Each case is a design problem viewed by teachers, students, EdTech, and administration. Switch perspectives to see the same tension differently. These perspectives affect one another, so no single view tells the whole story.

  • TeacherWhat is planned and decided.
  • StudentWhat learners actually experience.
  • IT SystemsWhat tools enable and constrain.
  • AdministratorWhich policies and resources shape the design.

Start here

Create or Choose a Case

Instructor

System topology

Proposal network

Teacher perspective Needs attention
Perspectives

D3 force-directed graph

Live network structure Hover over a node to explore its tension. Select a stakeholder node to change perspective.
Instructional signals The teacher's intended learning goals, teaching strategies, and design intentions.
Constraint friction Where practical constraints such as time, tools, policy, and workload conflict with teaching intentions.
Aligned evidence Evidence that supports or challenges design choices from teacher, student, and EdTech perspectives.
Stakeholder interplay A dashed line connects related tensions across stakeholders, where one person's decision may become another's burden.

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

Activity history

0

Perspectives — Read the case through one person's eyes

Choose a stakeholder to explore their perspective. Their concerns appear on the left, related tensions in the orbit on the right, and simulated responses below. Switching perspective updates all three areas.

Current result Review the main concerns of the selected perspective. Switching perspective updates the cards and orbit below.

People in the case

Key concerns

How are these scores calculated?

Each score (0–100) combines four base indicators — personalization, teacher workload, privacy, and accessibility — using fixed weights. For example, Feasibilityincreases with lower workload and higher privacy and accessibility. Treat these as relative discussion signals, not precise measurements.

Current focus

Teacher perspective orbit

school
Classroom management and facilitation demands are high.
LMS
Peer feedback
Assessment

Trade-offs — what moves together

Instructional design involves trade-offs. More personalization may increase workload; stronger privacy may limit personalization. The radar shows how five indicators interact. The decision log records which adjustments changed them.

Current result Start with the balance between indicators and the largest conflicts. Review the effects of adjustments in the radar and decision log.

Trade-offs

Interacting indicators

Balance
Personalization
Privacy
Accessibility
Feasibility
Teacher load

Sandbox — test a what-if

Drag a slider to push one dimension and see what breaks elsewhere. Turn autonomy on to let the system propose moves. Changes here are exploratory — nothing is committed until you confirm.

Current result Changes from the sliders are summarized here. Experiments let you explore before saving; they do not immediately change the case.

Experiment with changes

Adjust the case

Autonomous iteration

Allow the system to suggest redesign directions for instructor review.

Stress scenario

System response

Effects of your adjustments

Stable
hub 81%

Alignment cohesion

psychology High

Cognitive load

speed 14ms

Response time

Report — Bring your learning together

Bring your case together here. Summaries, evidence, and reflection prompts draw on the nodes and decisions from other views. Write your reflection and export a copy. Instructors can also review class progress here. Confirm your course's submission requirements with your instructor.

Case report

Draft the summary

Executive summary

Priority tensions

Suggested redesign directions

Evidence trail