WEBVTT

1
00:00:01.400 --> 00:00:10.506
Design thinking is often presented as a cycle of understanding users, defining a problem, generating ideas, making prototypes, and testing them.

2
00:00:10.506 --> 00:00:20.308
Equity asks harder questions before that cycle begins: who framed the problem, whose experience is treated as expertise, and who controls the final choice?

3
00:00:20.308 --> 00:00:28.529
This episode adapts Kristine Miller's chapter What Is Design Thinking and What Does It Have to Do with Equity, licensed CC BY 4.0.

4
00:00:28.529 --> 00:00:35.864
It paraphrases Miller's work and excludes the chapter's third-party article, graphics, quotations, and linked media.

5
00:00:35.864 --> 00:00:39.458
A technical solution can miss a political or economic cause.

6
00:00:39.458 --> 00:00:45.210
If healthy food is unaffordable, redesigning a store interface does not solve income inequality.

7
00:00:45.210 --> 00:00:54.915
If a dangerous street reflects repeated budget priorities, a temporary demonstration may reveal an option but cannot substitute for durable authority and funding.

8
00:00:54.915 --> 00:00:57.011
Add four gates to the design cycle.

9
00:00:57.011 --> 00:01:00.606
Reflection asks what assumptions and limits the team brings.

10
00:01:00.606 --> 00:01:04.620
Context asks how history, policy, and power produced the condition.

11
00:01:04.620 --> 00:01:09.472
Shared definition asks affected people to shape the problem and success measures.

12
00:01:09.472 --> 00:01:14.205
Accountability asks who owns the decision, resources, data, and follow-through.

13
00:01:14.205 --> 00:01:17.799
Prototypes can reduce risk, but experimentation has burdens.

14
00:01:17.799 --> 00:01:24.150
Do not test on a community without consent, safeguards, a way to stop, and a commitment to report results.

15
00:01:24.150 --> 00:01:27.145
Compensate expertise where appropriate and lawful.

16
00:01:27.145 --> 00:01:29.816
Write a problem statement with three layers.

17
00:01:29.816 --> 00:01:33.214
Describe the observed condition without assigning cause.

18
00:01:33.214 --> 00:01:36.310
Identify systems and decisions that may contribute.

19
00:01:36.310 --> 00:01:39.284
Then state whose desired outcome defines success.

20
00:01:39.284 --> 00:01:41.651
Revisit the statement after engagement.

21
00:01:41.651 --> 00:01:46.142
Compare alternatives with distributional measures, not only total benefit.

22
00:01:46.142 --> 00:01:50.937
Record who gains, who pays, who may be displaced, and who maintains the result.

23
00:01:50.937 --> 00:01:52.579
Torrance application segment.

24
00:01:52.579 --> 00:02:01.069
This original exercise is separate from Miller's chapter and cites the City of Torrance General Plan page, checked October seventh, twenty twenty-six.

25
00:02:01.069 --> 00:02:04.352
Imagine a design sprint about access to a public facility.

26
00:02:04.352 --> 00:02:07.409
Begin with a reflection memo and a local decision map.

27
00:02:07.409 --> 00:02:11.938
Invite affected users to revise the problem statement before generating options.

28
00:02:11.938 --> 00:02:16.806
Test accessible, low-cost prototypes only after explaining what can and cannot change.

29
00:02:16.806 --> 00:02:19.523
Publish the evaluation criteria before choosing.

30
00:02:19.523 --> 00:02:24.108
Include access, safety, maintenance, displacement risk, and community assessment.

31
00:02:24.108 --> 00:02:28.806
This is independent study, not a report on Torrance practice or a legal conclusion.

32
00:02:28.806 --> 00:02:39.603
Design thinking becomes more equitable when it exposes assumptions, places the problem in history, shares definition and power, and remains accountable after the prototype.

33
00:02:39.603 --> 00:02:48.517
This adaptation credits Kristine Miller under CC BY 4.0, excludes third-party chapter items, and adds a separately cited Torrance application.

34
00:02:48.517 --> 00:02:50.149
No endorsement is implied.