September 26

Start of class, each group should have:

(to present to professors – see: Team meeting schedule):

• A team of three members. (For now, defer who will do: B/SD/ I…but think about it).
• An agreed upon shared entity (be it an institution; a business; an organization; or event/program, initiative / campaign, etc.)
• A shared thematic idea of what each group will build as a team of designers (more on this below)

First stab at a mission statement

• A mission statement is more about the present, and the purpose of actions. It should cover for whom, what you’re doing, and how generally you’ll accomplish it. Possibly a single sentence, and no more than three (try to be concise, but more to be said than with vision).

First stab at a vision statement

• A vision statement defines (envisions) an optimal state that would be the result of your work. Typically, these are far in the future, but how far forward you’re looking is simply contingent upon your project. Probably one sentence, compact, inspiring.

Diagram study of your institution; business; organization; or event/program

• 22 x 34 (landscape orientation) – for posting in the class.
• Hand-drawn (informal, or with stickies), scan for presentation.
• title of entity, type of entity, plus list of team members up top
• define core parts, organizational activity areas, etc.
• annotate potential stakeholders, users, audiences, impacted parties, etc.
• finally, anticipate needs and matching design touch points in the areas of Branding, Interaction Design and Service Design (annotation > list)

………………………………………………………

In-class work…

Convene in teams and continue to develop your ideas. Look ahead to next Tuesdays (10/01) presentation for outstanding elements. You might begin with the case study. Or you might attempt to get more specific with possible touchpoints. Etc.

Working toward’s 10/01 (in-class, 9/26)

Co-write with your group, in-class, a creative/systems brief that accounts for the following:

YOUR ENTITY PROPER … (what is your entity? what does it do? what service does it provide? etc.)

• off your “diagram-like” (or analogous) study, describe core parts, organizational activity areas, etc. of your system.

WHAT TYPE OF BEHAVIORS ARE FOUND/SUPPORTED BY YOUR SYSTEM (motivations, needs, social conventions, etc.)

• remember all the UX behaviors + our provocation presentations …

WHAT KIND OF PEOPLE ARE FOUND/SUPPORTED BY YOUR SYSTEM … (who is who in the system? doing what? etc.)

• take into account stakeholders, users, service providers, parties, etc.; if/when in doubt, follow the breakdown below:
• stakeholders: constituents, citizens, affiliated groups, etc.
• users: participants, audiences, impacted third parties
• service providers: agents, staff, drivers, front- and back-of-the-house, etc.

Note: Ultimately, your umbrella creative/systems brief will describe all of the above and provide us with a general sense of where you are heading when it comes to a design system. Furthermore, this umbrella description will begin to provide you with insights as to where you might find touchpoints that will need your attention and design.