DDQ TUE 2023-02-21
18. Ideation¶
18.1. Agenda¶
Released |
Category |
Assignment |
Day |
Date |
|---|---|---|---|---|
2023-01-10 |
Term Project |
FRI |
2023-01-20 |
|
2023-01-19 |
Paper Pres. |
THU |
2023-01-26 |
|
2023-01-19 |
Term Project |
Milestone 1: Problem Proposal (Part 1) |
FRI |
2023-01-27 |
2023-01-19 |
Paper Pres. |
THU |
2023-02-09 |
|
2023-01-19 |
Term Project |
Milestone 1: Problem Proposal (Part 2) |
FRI |
2023-02-10 |
2023-02-07 |
Exams |
FRI |
2023-02-10 |
|
2023-02-07 |
Exams |
TUE |
2023-02-14 |
|
2023-02-16 |
Term Project |
FRI |
2023-03-17 |
|
2023-03-20 |
Term Project |
FRI |
2023-04-14 |
|
2023-03-28 |
Exams |
FRI |
2023-04-21 |
|
2023-03-28 |
Exams |
THU |
2023-04-27 |
|
2023-03-28 |
Term Project |
TUE |
2023-05-09 |
General Announcements
Important: Figma Education Accounts
See Piazza @60 to setup a Figma Education account if you have not done so already.
Activity
18.2. Activity¶
18.2.1. Introduction¶
In human-centered design approaches, the design process is iterative:
Fig. 18.1 The Iterative Cycle of Human-Centered Design [TB:1].¶
- ideation¶
- idea generation¶
In most human-centered design approaches, including design thinking, ideation (or idea generation) is a brainstorming component of the preliminary design phase that is focused on generating potential solutions [TB:1]. Ideation is often semi-structured, team-based, and subject to the following rules [02:21:1]:
Generate numerous ideas – as many as you can.
Be creative without regard to constraints.
Question everything, especially the status quo.
Empathize with users [02:21:2].
Ideation can focus on a single requirement, multiple requirements, or even general problems.
Important
In Milestone 3 of the term project, you will be asked to “include something in your deliverables to illustrate that you did generate numerous ideas” for each relevant user story. We suggest that you model each of these off today’s activity.
- status quo¶
The existing state of affairs, especially regarding social or political issues. In design, this includes common, existing design solutions that address your requirement or a similar requirement.
- stupid question¶
A questions that asks about things so fundamental that everyone assumes the answer is obvious [TB:1].
I am particularly fond of stupid questions. […] [W]hen the question is taken is seriously, it often turns out to be profound: the obvious often is not obvious at all. What we assume to be obvious is simply the way things have always been done, but now that it is questioned, we don’t actually know the reasons.
—Don Norman, The Design of Everyday Things [TB:1]
18.3. Breakout Groups¶
Randomize! Groups of 4 Preferred.
Please randomize! Also, four students per group is preferred for this activity.
18.3.1. Part 1¶
Quickly introduce yourselves to each other, if you don’t already know each other.
Pick a group representative. This person will be responsible for posting your breakout group’s response on Piazza before breakout group work ends for this activity.
When instructed, click here to access a Figma FigJam for this part of the activity.
As a group, pick an app or system with a computer-related graphical interface.
Come up with an interesting, non-trivial user experience requirement involving the app or system that you picked, then note down that requirement on your group’s first sticky note using a user story.
Non-Trivial?
Avoid requirements related to login, logout, etc.
Reframe: On your group’s second sticky note, reframe your requirement as a “how might we” statement.
Template: User Story \(\to\) How Might We
As a
type of user, I wantsome goalso thatsome reason.How might we, as
type of users, accomplishsome goalso thatsome reason.Ideate: Based on your “how might we
...” statement, generate numerous ideas for how you might.... No need to discuss; just generate ideas.Good Faith Effort
Remember to consider the rules included in our working definition for ideation (presented earlier). If you are not willing to follow those rules in good faith, then you are welcome to leave and not receive credit for this activity.
A copy of the Figma FigJam file that resulted from this activity will be embedded below.
18.3.2. Part 2¶
Help your group representative respond to the following in a followup discussion to Piazza @64.
List the names of your breakout group members.
App: What app did your group pick?
User Story: What is your user experience requirement?
How Might We?: What is your “How might we?” statement?
Status Quo: What is the status quo? If possible, provide one or more screenshots or images that illustrate the status quo.
Worst Idea:
What do you think is your group’s worst idea and why?
How does your worst idea compare to the status quo?
Best Idea:
What do you think is your group’s best idea and why?
How does your best idea compare to the status quo?
As a group, discuss and comment on the work presented in other followup discussions until the breakout rooms end.
18.4. After Class¶
Before the next class period, individually comment on another group’s post by replying to their followup discussion in Piazza @64.
Continue reading the Design module.
Here is a list of current assignments:
Released
Category
Assignment
Day
Date
2023-01-10
Term Project
FRI
2023-01-20
2023-01-19
Paper Pres.
THU
2023-01-26
2023-01-19
Term Project
Milestone 1: Problem Proposal (Part 1)
FRI
2023-01-27
2023-01-19
Paper Pres.
THU
2023-02-09
2023-01-19
Term Project
Milestone 1: Problem Proposal (Part 2)
FRI
2023-02-10
2023-02-07
Exams
FRI
2023-02-10
2023-02-07
Exams
TUE
2023-02-14
2023-02-16
Term Project
FRI
2023-03-17
2023-03-20
Term Project
FRI
2023-04-14
2023-03-28
Exams
FRI
2023-04-21
2023-03-28
Exams
THU
2023-04-27
2023-03-28
Term Project
TUE
2023-05-09
Additional References
- 02:21:1
Elizabeth Gerber. Using Improvisation to Enhance the Effectiveness of Brainstorming, pages 97–104. Association for Computing Machinery, New York, NY, USA, 2009. doi:10.1145/1518701.1518718.
- 02:21:2
Froukje Sleeswijk Visser and Merlijn Kouprie. Stimulating Empathy in Ideation Workshops. In Proceedings of the Tenth Anniversary Conference on Participatory Design 2008, PDC '08, 174–177. USA, 2008. Indiana University. doi:10.5555/1795234.1795265.
Comments
Please keep the comments polite and constructive. In addition to whatever else you want to write, please comment on one aspect of a group’s post that you like and one aspect that you think needs improvement (e.g., you find that something is unclear or you don’t understand a justification). As always, be sure to provide a brief justification for each.