An operational guide to the updated Design Tension Studio. Students follow Home → Issue map → Reflection. This guide explains the interface; it does not establish learning effectiveness or validate the analytics.
Before class · Check the essentials
Open the service · Try the student sample · Student instructions
Prepare an instructor account, the intended course, and a case to publish. Existing accounts use the existing sign-in route. Keep shared passwords and student information out of public guides.
Current-version caution: reflection submission is coupled to research consent and event logging, so a success message alone does not establish receipt. Before class, verify a test submission on the receiving side and provide an original-copy and alternative-submission procedure. Do not require research consent as a workaround.
1 · Check the course and case
Check the course and case selections in More settings. Open My courses from the navigation or More ways to explore on Home. Available controls depend on account permissions and course state.
Share the service address, course name, join code if needed, and assigned case name. Deliver passwords separately through an appropriate private channel.
Check: verify visibility using a student account. Instructor access alone does not establish that a case is published to students.
2 · Prepare and publish the case
Use the case creation controls to provide a title and instructional brief, then review the result. If AI structures the brief, check that its goals, constraints, and stakeholders match the source. Publish only when the case is ready.
A useful starting case has one decision, at least two stakeholders, and clearly conflicting needs. Reduce unexplained jargon before asking students to analyze it.
Check: distinguish draft, published, and archived states. Do not practice deleting or archiving class material without considering the records affected.
3 · Start with one issue
Try this activity sequence. It is a proposed facilitation pattern, not an evaluated timing or effectiveness claim.
- Find the assigned case on Home.
- Select one map node and explain its content in your own words.
- Switch perspective and identify a concern you initially missed.
- Write a reflection supporting a decision with case evidence.
Welcome slides no longer run automatically for students. Offer More settings → Show Tutorial when needed. If learner views are restricted, check that a required reflection task remains accessible.
4 · Compare and discuss
Use Class view or Compare to examine recurring issues and different positions. What appears depends on sharing settings and refresh timing; do not assume every change is instantaneous.
Discussion prompts: “Which case detail supports that claim?”, “What cost does another perspective face?”, and “How would a minority concern change this decision?”
Treat AI responses as proposals to inspect. Tell students not to include personal or sensitive identifying information in nodes or questions.
5 · Verify receipt and interpret analytics
Compare the original answer and received content in a test submission. Long answers currently may lose content after 2,000 characters. Provide a copy-first and print/PDF or other alternative submission process. Do not grade from a success message or a progress checkmark.
Activity counts summarize recorded actions. Missing logs do not establish nonparticipation or weak learning: consent, connectivity, and settings can affect coverage.
Design reference indicators such as Perspective shift and Revision quality currently use settings or record counts. Do not treat them as measures of learner ability or writing quality. Repeated submission of an unchanged answer can also produce revision events; inspect the original text.
Frequently asked questions
A student cannot find the case.
Check the student’s course, the case’s publication state, view permissions, and account-to-course connection.
A student submitted, but no record appears.
Preserve the original answer and accept it through the alternative route. Report the minimum necessary information, such as case name and submission time, to the operator. Do not ask for the student’s password.
Does the public sample need student accounts?
No. It uses fictional case data without sign-in. Help learners distinguish practice from real coursework.
Can I keep using the previous videos?
They show older navigation and include outdated automatic-onboarding and saving claims. They are excluded from this version’s core guide. Use the current student guide and in-app tour first.
Ready-to-teach check
Verify student sign-in, case visibility, permitted views, receipt of a short test reflection, original-copy instructions, and an alternative submission route. Do not use the analytics as evidence of learning grades.