Showing posts with label design. Show all posts
Showing posts with label design. Show all posts

Monday, June 23, 2008

Elements of Taste

I just love compositional guidelines and design principles. It fascinates me to no end that basic design principles such as balance, contrast, repetition, form and the like show up in so many domains of life. Right now I am looking at a book called The Elements of Taste by Gray Kunz and Peter Kaminsky, and they have a great little system for composing flavours and textures to make creative dishes. I won't share any of their recipes here, but I will describe some of their more interesting design ideas.

NARRATIVE: There are narrative arcs in eating experiences. When you take a bite of something, there is an initial flavour/texture - an "introduction" or an "attack" flavour. Flavours then build and change into the middle of the mouthful. They may peak to a climax, or build through the middle to a big finish, or broaden through the middle towards a mellow finish, or whatever. Then there is the finish and the aftertaste.

Finish and aftertaste become the context for the next mouthful of the food, so the time you spend eating one dish will also have a beginning, middle and end. One of my favourite experiences at this level are "slow burn" foods like chili, Indian/African curries or many Korean dishes, which start out with a sharp spicy attack, but then you get used to the spices and things mellow out into the middle, but by the end the burn has built up so much that you are starting to sweat.

The courses of a meal have a narrative structure too, so you can start out with a fresh opening, shift to a savoury slow burn middle, and end with a tangy, floral, sweet dessert, for example. Each act of the meal, beginning, middle and end, can also have a cast of characters - several different flavour/texture/temperature elements that diners will play off against (or with) each other as they eat. Kunz and Kaminsky call this level of food analysis the TASTE LOGIC of a meal.

This idea is too cool!

TASTE PLATFORMS: Kunz and Kaminsky isolate four taste platforms or basic scaffoldings for other elements of the taste experience: GARDEN, MEATY, OCEANIC and STARCHY. These are pretty self-explanatory. One cool thing I inferred from their recipes is that GARDEN palettes allow for a lot of crunch and colour, but also that flavours are often chosen to amplify each other in GARDEN food - e.g. adding both cherry tomatoes and orange bell peppers to a salad to multiply the sweet, tangy and floral notes in the salad. With MEATY platforms, balance is more often sought, bringing salt, tanginess, bulby/allium flavours (onions/garlic/shallots), sweetness, vinted (wine) and funky (age-related - old cheeses, etc) into harmony with each other. There are also two main MEATY notes - the deep flavours of dark meats and the top notes of white meats.

OCEANIC palettes are often already salty, and adding tang and herbaceousness can bring the delicate flavours out more. So like GARDEN, multiplication of flavour is a basic compositional strategy here. STARCHY palettes can be full and nutty, bland and supportive of other flavour elements (providing contrast and balance) or crisp/toasted. Starch and tang really cut each other nicely - witness vinegar on french fries.

So the two levels of TASTE LOGIC and FLAVOUR PLATFORMS set the stage for the drama, the actual actors are the tastes, which Kunz and Kaminsky divide into three categories:

- TASTES THAT PUSH (Salty, picante, sweet)
- TASTES THAT PULL (Tangy, vinted, bulby, spiced aromatic, floral herbal, funky)
- TASTES THAT PUNCTUATE (Bitter)

PUSHING means heightening all the other tastes in a recipe. Salt, spicy heat and sweetness all bring out other flavours. They up the whole flavour profile of the dish. PULLING tastes tend to isolate aspects of the underlying or overall taste of a dish to accentuate it. They make flavours more distinct instead of smoothing them or rounding them out. TANG can heighten and accent the SWEET and FLORAL of fruit, and FUNKY tastes like truffles accentuate the MEATINESS of earthy, savoury dishes.

BITTER has a special role. It slams the brakes on other flavours. Beer is a sugary drink and it would be far too sweet and cloying without the bitterness of hops to slam the brakes on that sweetness. Having cranberry sauce with meat is not the equivalent of having jam on your meat because the bitterness of cranberries slams the brakes on that sweetness and prevents it from overpowering the taste. Salt licorice is incredibly salty, but it is edible because the bitterness of the unsweetened (or is it semi-sweetened) licorice stands guard against all that salt. Conversely, too much bitterness can be countered by salt, sweet, floral or aromatic, etc. Bitterness helps create structure in the food that can hold up to stronger flavourings.

So that's the gist of their system. It is very interesting. The recipes in the book are illuminating as well, although they are a bit fancier than anything I would make myself. I love their design vocabulary, though. It rocks!

Monday, May 26, 2008

Interaction Design

Jennifer Tidwell is the author of the O'Reilly book "Designing Interfaces", and author of a couple of websites: designinginterfaces.com and the older and soon retiring UI Patterns and Techniques site. Reading her stuff is fun because you suddenly get names for all of the user interface elements and experiences you've been having interacting with all of your life (or half of it, for some of us). I just like reading her work and gaining that clarity through labeling my experience. I love what she said (my notes are older, and she may have updated it) about user interfaces for "Navigable Spaces like the web and related technologies. She reckon(s/ed) that Navigable Spaces usually need to supply users with:

- "Map" views of navigable spaces
- Clear Entry Points
- The ability to Go Back One Step
- Some kind of "home" page or base state which allows users to Go Back To A Safe Place
- Some way of recording an Interaction History
- Progress Indicators (e.g. breadcrumbs)
- Bookmarks
- User Annotations
- Pointers that signal the user about what kind of actions they can take (like when an arrow cursor turns into a finger cursor when mouseover on a list)
- Short Descriptions of nodes that save the user from having to take on too much info at once (search engines serve this up for us)
- Disabled Irrelevant Things that can be cleared away if necessary
- Optional Detail on Demand
- Easy icons to aggregate Convenient Environment Actions
- Good Defaults

That's it. I just think it's cool to have names for stuff like that...

Friday, October 27, 2006

Harmonic intervals and emotional characteristics

Okay, I almost gave up on this whole blogging concept, but this is just way too cool! It's a list of different harmonic intervals and the emotional responses we have to them. This is taken from _Exploring Sound Design for Interactive Media_ by Joseph Cancellaro (Thompson 2006). Here it is:

INTERVAL-------- EMOTIONAL QUALITY
Perfect octave----- Completeness, Openness, unity
Major seventh -----Spooky, eerie, off-centre, strange
Minor seventh----- Expectant, suspenseful, full but unbalanced
Major sixth---------Peaceful, balanced
Minor sixth---------A bit sad, soothing
Perfect fifth---------Power, centering, strength, victory
Tritone-------------Horror, terrifying, scary
Perfect fourth-------Ethereal, lightness, transparent, clarity
Major third---------Neutral, hopeful, resolved, nonabrasive
Minor third---------Uplifting, relaxed, positive feelings
Major second-------Unresolved, unsettled, unpredictability
Minor second-------Unclear, tense, anxious, uneasiness
Perfect unison------Peace, strength, calmness, security

There you go! You always knew different intervals had different emotional qualities. It just took someone to actually list them! Thanks Joseph!

Friday, August 25, 2006

Problems upon problems

So I'm designing an online course for some clients of mine, and I have a problem. The course is boring! I am boring myself while writing this course, God only knows how boring the poor students might find it. This won't do. I have to re-think my design plan.

There is a lot of buzz about using narrative principles to structure courses, so I surf around the web and my design library at home. Here is what I figured out.

We very commonly design courses within an overall "problem-solution" pattern. We describe some problem in the world that our students will face, and present the knowledge to be gained by the course as the solution.

I think a simple problem-solution frame is too simplistic to hook and engage the narrative imagination of students (or anyone else for that matter). There is no suspense. The solution is too pat. Too near at hand.

You start to draw on the appeal of narrative by making a very simple shift in your design plan. You heap problems on top of problems at the top-level of the design plan (sub-problems don't count, they have to be top-level).

For example, I was just designing a course for an online MBA program. The topic was organizational lifecycle analysis. My initial problem-solution frame went as follows:

No single management approach is good for all situations. The top management priorities for one firm might be very low on the list for another firm. Furthermore, within any organization, there is a multitude of different units, teams, projects, intiatives and so on, all of which may require different things from managers. The question, "How will you know what to do in each situation?" Organizational lifecycle analysis can help, in these various and sundry ways...


Basic problem-solution, not very dramatic. But wait!

Once you complicate, frustrate, or oppose this solution, making it impossible to attain the result right away, then your course plan starts to exhibit some drama!

...However, just knowing about lifecycle analysis is not enough. There are all kinds of barriers, structural and cultural, that can prevent you from bringing lifecycle problems to the attention of the management team, and further barriers that can prevent you from implementing solutions to lifecycle problems...

Gasp! The goal is in jeopardy! We have entered the drama zone.

For this reason, we will also study tools for overcoming these barriers, to solve lifecycle problems and improve communication on the management team, so that in the future you will be able to anticipate such problems and prepare for them, driving organizational change instead of letting it drive you.

I think that compounding problems on top of problems like this, of holding out a goal but then raising doubts about our ability to reach it, these create more complex problems that are more engaging, more story-like. They are complex enough to hold learner interest. Simple problem-solution design frames, I think, are too simplistic. The sales job they do is too blatant and too on-the-nose. More complex, story-like design frames with some risk and some challenge are much better choices - especially for online education, when the risk of having students drop out is so high.