Posts tagged “process”
More of 100 doodles in 100 days
Since the beginning of the year, I’ve been working on 100 doodles in 100 days. Here are the 60s.
An update on 100 doodles in 100 days
Since the beginning of the year, I’ve been working on 100 doodles in 100 days. I’ll probably wait for the project to complete before I reflect in more detail but I thought for the last half I’d do a few posts to share the output. Here are the 50s.
Dollars to Donuts: Behind The Music
My new Dollars to Donuts podcast features a nifty bit of intro and outro music. In the podcast you just hear snippets of the song, written expressly for the podcast by my brother-in-law, Bruce Todd. I’ve long been an admirer of Bruce’s songwriting and playing and overall musical thang, and it was an absolute thrill to have him create a piece of music for me.
Now you can hear the whole piece!
Since we’re all about digging into creative processes, here’s Bruce’s explanation of how he developed this music.
This song came to light through questions and (heaven forbid) assumptions about what Steve was looking for or better yet – listening for. Based on some email conversations and musical examples, I had a rough idea that the music had to be relatively fast-paced, rocking and attention=grabbing. Since Steve had some alternatives there was no pressure for me to actually produce anything and this allowed me to experiment and take a few small sound risks. Most of this recording was completed through digital amplification or direct line inputs which allowed me to work quietly and at my leisure (everything except vocals). Often when recording instruments with microphones you need a quiet peaceful environment which I don’t always have access to in my (non-soundproofed) home studio.
I began by finding a drum track: a simple upbeat 4/4 rock drum track which I had used on a previous recording (having exported the tracks from a master file and imported to my Tascam DP 32 Portastudio). Then the fun began. Knowing that the end result would be used as a short clip, I laid down about 2 minutes of drums and then pulled out my Fender Telecaster and began to experiment with a riff. This came pretty quickly as it is quite a simple progression in the key of F-sharp. Next, I plugged in my Vox DA5 (5-watt digital amplifier) and located an overdrive sound I liked and added a small amount of delay. I recorded two tracks with the same guitar sound and panned the tracks left and right, which results in creating a thicker overall sound by doubling the part. After the rhythm guitar tracks were completed I worked on the bass part. I ran the bass also through the little digital Vox and added compression which brought out a punchy bass track (this is a discovery I have been using on my other recordings ever since). Once drums, guitar and bass were complete I left the recording for a few days so I could revisit the idea when I was ready.
Coming back, I wasn’t too sure I liked what I had. If this was a more serious venture I would have probably scrapped the idea. Given that I wasn’t overly convinced that the song idea had much merit I thought I would have my young daughters (Talia 8, Arianna, 4) join me and be exposed to the recording process. Regardless of what the end result was I was sure Uncle Steve would get a kick out of his nieces being involved. Talia has a small electronic keyboard which I plugged into the Portastudio, and I gave her some headphones and had her play along with the guitar, bass and drums. Her first track was a keeper as she found a funny sound and played a part that complimented the space that the guitar riff left. Then Arianna played a part with a toy instrument of hers (in the end this track did not make it on the recording). The girls also helped me do a little vocal improvisation which also didn’t make the master mix but helped me get to the next part of the recording.
Several days again went by until I felt ready to listen to the song and see what was there and what else I could add. I went back to my guitar and found another overdrive tone which I overlaid with the auto-wah pedal sound setting on the Vox DA5. This was a lucky choice as I think it is what gets the attention of the listener at the beginning of the song. The track is pretty much one big lead guitar riff which from time to time stops and echoes the rhythm guitar tracks. This was a fun part for me as was the final vocal tracks. For the vocal tracks I ran a Shure 57 through the Vox DA 5 flanger setting with a lot of flange and overdrive and experimented by saying “Talk it Out” and by making other weird sounds. I mixed the song and sent it digitally via email to Steve – and to my surprise received a very nice response.
And that is how Dollars to Donuts found its music.
Interviewing the Interviewer – Steve Portigal talks with Maish Nichani
UX Booth has published a two-part conversation I had with Maish Nichani of Pebble Road.
In Part 1, Maish interviews me (excerpt below). We explore a few aspects of the research process, including how a project plan is negotiated.
MN: What is an appropriate response to give clients who insist on specifying aspects of your research methodology?
SP: Whenever a client approaches me and has already specified the approach we should take with their study, that’s usually time for a conversation. Sometimes teams create a research plan as a stake in the ground when what they actually want is feedback and a recommended approach. Sometimes, though, their plan is a good one, and we might just suggest one or two changes to see if they are amenable. I can’t count the number of times I’ve received a detailed request, exclaimed “what?!” and then had a really excellent conversation to better understand the reasons behind it. Obviously, no one should take a project where they don’t believe the method is going to produce results. An examination of a prescribed approach is one of the first tests of (the potential for) good collaboration.
In Part 2, I interview Maish (excerpt below). We talk about how to improve the organizational learning user research.
SP: If you could wave a magic wand and create any kind of tool or artifact to support the research process, what would it be?
MN: Research is really all about creating new knowledge and the more people who have access to that knowledge, the better. Currently, our research findings and insights are all locked up in (what Karen McGrane calls) “blobs.” We need it, instead, to be “chunked” (as Sara Wachter-Boettcher says) so that it can travel more freely and be mixed and mashed up to create, again, new knowledge. I don’t know of any existing project or initiative but I was thinking about using a schema (like what is already available on schema.org) for research findings. That way anyone writing up research findings could use the same markup and then search engines and specialist apps could read and move those findings more efficiently.
Our latest article: Elevator Pitch
Our latest interactions column (written by Steve Portigal and Julie Norvaisas) Elevator Pitch has just been published.
It seems only yesterday that the VCR and its flashing 12:00 was the go-to whipping boy for the interaction field. “Gosh almighty,” the lament would rise. “What does it say about us if we can’t even make a usable digital clock, one that won’t blinkingly admonish us for our failures?” Note to younger readers: The VCR, now obsolete, was an entertainment device that “streamed” video information directly from physical media, not unlike its successor, the nearly obsolete DVD player. We’re stoked to propose an alternative that isn’t likely to be obsolete for a while: the elevator.
Get the PDF here.
Previous articles also available:
- Persona Non Grata
- Everybody’s Talkin’ At Me
- The Journey Is The Reward
- Hold Your Horses
- Living In The Overlap
- Some Different Approaches to Making Stuff
- Poets, Priests, and Politicians
- Interacting with Advertising
- Ships in the Night (Part I): Design Without Research?
- Ships in the Night (Part II): Research Without Design?
- We Are Living in a Sci-Fi World
- On Authenticity
- The Hard Work Lies Ahead (If You Want It)
- What to Expect When You’re Not Expecting It
- Kilroy Was Here
- Never Eat Anything Raw
- Content, the Once and Future King
ChittahChattah Quickies
- [from steve_portigal] Delta-Northwest Merger’s Long and Complex Path [NYTimes.com] – [While there's humor at the banality of decisions, the successfully merged experience worships the God who lives in the details.] Airlines have specific working rules, flying procedures, maintenance schedules and computer programs. And all have their own cultures…Pilots at Delta used to ring the cabin bell four times as they began their final approach, while those at Northwest rang it twice. The food catering operations of both airlines had 8,000 pages of one-line codes describing everything from soda orders to the price of strawberries. Each airline had different codes and paid different prices. Delta used to cut its limes in 10 slices while Northwest cut them 16 ways. The lime debate was even mentioned at a meeting attended by the chief executive, who was told it saved Northwest about $500,000 a year. In the end, Delta stuck with its 10 slices. But the airline also realized that it had been loading more limes on its flights than it needed. So it is now carrying fewer limes.
ChittahChattah Quickies
- [from steve_portigal] Hong Kong’s Couples Invited to Wed at McDonald’s [NYTimes.com] – [We did visit a McDonald's in Hong Kong the other week but we didn't see anything like this!] McWedding starts at $1,280, which includes food and drinks for 50 people. The package includes a budget version of the usual trappings: a “cake” made of stacked apple pies, gifts for the guests and invitation cards, each with a wedding photo of the couple. (Hong Kong wedding photos are taken in advance, with the couple in rented finery.) McDonald’s employees dressed in black suits mimic the actions of hostesses at upscale hotels. They greet guests at the entrance, usher them to the signature book and deliver food, even if it is just a Big Mac and fries. McWeddings were devised in line with local customs, particularly Chinese numerology beliefs that determine the best dates for weddings or other important events. The engaged couple was given a photo frame shaped like Ronald McDonald, marked with the “limited edition number” 138, an auspicious figure.
- [from steve_portigal] Stalking insights with Steve Portigal [Foolproof] – [Lovely concise report from our UX Hong Kong workshop. Thanks, Tom!] Even a novice UX researcher knows the dangers of moving too swiftly to draw conclusions from fieldwork. It’s important to maintain a state of openness and observation. Leaping to solutions and recommendations can bias your view. This could cause you to miss something really revealing or valuable simply because it doesn’t fit with the way your view is developing. It shouldn’t be true, but in fact the older and more experienced you get the more danger there is that you’ll fall into this trap. Firstly you’re instinctively calling on experiences and patterns in user behaviour that you may have seen before. Secondly, the more senior you are, the more impact your (wrong-headed) views may have on the situation. The antidote? Spend some time with Steve.
Because you *want* the words to rhyme
Eminem, interviewed recently in Rolling Stone magazine, reveals just a bit of his creative process, linked to a childhood impulse. While his “compulsion” isn’t one we all share, it evokes other behaviors from that time in our lives. Nice that Marshall has managed to use his to inform, if not define, his art.
How do you go about putting together a verse?
Even as a kid, I always wanted the most words to rhyme. Say I saw a word like “transcendalistic tendencies.” I would write it out on a piece of paper – trans-cend-a-list-tic ten-den-cies – and underneath, I’d line up a word with each syllable: and bend all mystic sentence trees. Even if it didn’t make sense, that’s the kind of drill I would do to practice. To this day, I still want as many words as possible in a sentence to rhyme.
Also important is the idea of a simple activity that will help you develop your creative muscles, an idea I explored in Skill Building for Design Innovators
I also enjoyed this insight about Eminem’s approach because it reminded me of some fun fieldwork a few years ago, where we met a young rapper who demonstrated his process for us, flowing from using looped music to freestyle against, a workbook where he’d write up a ton of lines, picking and choosing based on what worked when rapped aloud.
Sometimes I’ll write a song in just one sit down and it’s perfect, I don’t even touch it. For me, like I’ll feel good about it. Sometimes it’s just crap, and that’s fine, because I feel like you get out the crap and then you can pull the little gems out of it. Or even if it’s just one paragraph of a song I wrote, I’ll take that and piece it into other songs. In this case, I would sit down and open a file and then I’d just listen through it, see if there’s anything worth keeping.
His process (which developed into some exciting design implications for our client’s products) became a bit of a meme around the office, eventually becoming iconified thusly:
See thoughts on creativity, previously from Jack White and Will.i.am.
Ups and downs
After writing recently about managing the adoption of a new type of elevator UI, I found a particularly bad implementation of the norm at my hotel in Austin last weekend.
Unusually, there are two elevators on either side of two rooms.
Beside each elevator is this cautionary/alarmist admonishment:
“This button” refers to “these buttons – those ones down there” despite the horizontal arrow. But we can probably figure that out. The reason for this sign – an obvious afterthought is that there’s no place where you can stand and easily see both elevators at once. You must approach one elevator to press the button, and if you stand there and wait, you are likely to miss the arrival of the elevator if it doesn’t come to that door. There is a standard solution: a light near each elevator door that lights up just before the elevator arrives and the door opens. But (other than in the hotel lobby) they’ve neglected that and instead the hotel guest must be “alert” when doing a basic task like trying to get down for breakfast.
This is a well-known and long-solved situation; why the builders would choose to put the elevators around two rooms and then create such a poor experience would be interesting to explore. What were the design and other decision processes that led to this sub-optimal solution?