Re: [IxDA Discuss] Most usable doesn't always mean best solution
Todd wrote: On Mar 3, 2008, at 5:26 PM, Elizabeth Buie wrote: No, the automatic would come out as the most learnable Well, this is one very key factor in determining usability. Yes, of course. But it does not constitute usability by its own self; there are other factors. Remember that usability does not exist in a vacuum; it depends on who is using the product and in what context. I worked for a couple of years on an air traffic control system, and most learnable in that context would definitely NOT have been most usable because it would have slowed them down in operation and could have made the skies much less safe. Elizabeth Welcome to the Interaction Design Association (IxDA)! To post to this list ... [EMAIL PROTECTED] Unsubscribe http://www.ixda.org/unsubscribe List Guidelines http://www.ixda.org/guidelines List Help .. http://www.ixda.org/help
Re: [IxDA Discuss] IxDA Announces New Board of Directors for 2008-2009
Just a little follow-up. Having had a response from the IAI it seems their mentoring process *is* robust and intact ... it seems it might be my email service that isn't/wasn't. Happy to clarify on their behalf. John. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Posted from the new ixda.org http://www.ixda.org/discuss?post=26528 Welcome to the Interaction Design Association (IxDA)! To post to this list ... [EMAIL PROTECTED] Unsubscribe http://www.ixda.org/unsubscribe List Guidelines http://www.ixda.org/guidelines List Help .. http://www.ixda.org/help
Re: [IxDA Discuss] Most usable doesn't always mean best solution
Brandon Ward writes: I think everyone could agree that automatic is technically 'easier', Depends on by whom. It really *isn't* easier for me. Sorry if this isn't very coherent - but I think my point is in there somewhere. I'm not so sure. I drive a stick, never owned an automatic. I use a Mac, never owned a Windows machine. Go figure. :-) Elizabeth -- or maybe I'm just weird Welcome to the Interaction Design Association (IxDA)! To post to this list ... [EMAIL PROTECTED] Unsubscribe http://www.ixda.org/unsubscribe List Guidelines http://www.ixda.org/guidelines List Help .. http://www.ixda.org/help
Re: [IxDA Discuss] Most usable doesn't always mean best solution
On Mar 4, 2008, at 9:30 AM, Elizabeth Buie wrote: Yes, of course. But it does not constitute usability by its own self; there are other factors. That's my point. Many of the usability professionals I run into don't see usability as multi-factor. Unfortunately, many of them equate usability to efficiency and intuition, which are only a small, albeit significant, part of the pie. While intuition and efficiency are important parts, we can't forget about learnability, satisfaction, and the ability to inevitably complete a task/goal. Cheers! Todd Zaki Warfel President, Design Researcher Messagefirst | Designing Information. Beautifully. -- Contact Info Voice: (215) 825-7423 Email: [EMAIL PROTECTED] AIM:[EMAIL PROTECTED] Blog: http://toddwarfel.com -- In theory, theory and practice are the same. In practice, they are not. Welcome to the Interaction Design Association (IxDA)! To post to this list ... [EMAIL PROTECTED] Unsubscribe http://www.ixda.org/unsubscribe List Guidelines http://www.ixda.org/guidelines List Help .. http://www.ixda.org/help
Re: [IxDA Discuss] Most usable doesn't always mean best solution
On Mar 4, 2008, at 9:48 AM, Elizabeth Buie wrote: I don't know how they can miss it, given how ISO 9241 defines usability. Elizabeth, there are a lot of people out in the field, especially marketing agencies, performing usability studies who haven't got a clue that there's an ISO 9241 standard for it. You might be surprised by this, but it's true. But wait a minute. In your first post on the subject, you said that the product was less usable but yielded *greater* satisfaction, so I pointed out that your comment ignored the satisfaction component of usability. Now you're telling *me* that satisfaction is a component of usability? What is wrong with this picture? I include satisfaction in my definition of usability, but as I said before, many HCI purists, especially in academia don't see it that way. You might not see that in your work, but that might be due to the industry you're focused in. Likewise, since I'm not involved in government work, where we're not obligated to be bound by ISO standards, I see it pretty often. Cheers! Todd Zaki Warfel President, Design Researcher Messagefirst | Designing Information. Beautifully. -- Contact Info Voice: (215) 825-7423 Email: [EMAIL PROTECTED] AIM:[EMAIL PROTECTED] Blog: http://toddwarfel.com -- In theory, theory and practice are the same. In practice, they are not. Welcome to the Interaction Design Association (IxDA)! To post to this list ... [EMAIL PROTECTED] Unsubscribe http://www.ixda.org/unsubscribe List Guidelines http://www.ixda.org/guidelines List Help .. http://www.ixda.org/help
Re: [IxDA Discuss] Most usable doesn't always mean best solution
Elizabeth, there are a lot of people out in the field, especially marketing agencies, performing usability studies who haven't got a clue that there's an ISO 9241 standard for it. You might be surprised by this, but it's true. .. To the point: In the dusty institutions where usability standards gather to party with each other, ISO 9241 is a bit of a celebrity. It is widely cited by people who would be hard pushed to name any other standard, and* **parts of it are virtually enshrined in law in some European countries. *But as is the fate of many celebrities , *all most usability professionals know about the standard is its name*. - http://www.userfocus.co.uk/articles/ISO9241.html Welcome to the Interaction Design Association (IxDA)! To post to this list ... [EMAIL PROTECTED] Unsubscribe http://www.ixda.org/unsubscribe List Guidelines http://www.ixda.org/guidelines List Help .. http://www.ixda.org/help
Re: [IxDA Discuss] Most usable doesn't always mean best solution
Todd writes: Elizabeth, there are a lot of people out in the field, especially marketing agencies, Well, there you have it. They're marketing folks. IMNERHO they aren't usability professionals; they're just calling themselves that. I include satisfaction in my definition of usability, Then would you mind explaining what you had in mind when you said that a design was less usable but more satisfying? Help me out here. You might not see that in your work, but that might be due to the industry you're focused in. I have clients in the government, nonprofit, and commercial sectors. Which industry did you have in mind? :-) Likewise, since I'm not involved in government work, where we're not obligated to be bound by ISO standards, I see it pretty often. I am not talking about being bound by ISO standards. I am talking about knowing the definition of usability, which happens to be best captured in ISO 9241/11. This definition comes up rather frequently among people who actually *are* usability professionals. Elizabeth Welcome to the Interaction Design Association (IxDA)! To post to this list ... [EMAIL PROTECTED] Unsubscribe http://www.ixda.org/unsubscribe List Guidelines http://www.ixda.org/guidelines List Help .. http://www.ixda.org/help
[IxDA Discuss] IxDA London meet-up, more meetings - and money!
Hi all, Last night was a very interesting meeting! It was fantastic to meet such a wide variety of people and work - education, entertainment, consultancy, information, engineering (that's me and my boats!) - and I'm really looking forward to the forum that will be opened inside the group. As for decisions about future groups: We have some sponsorship! My company has kindly agreed to pay for food / drink for meetings - I need to sort out the details a bit more, but you should all be regularly getting a good feed, at the very least. IxDA London will be meeting on the first Monday and third Thursday of each month (with the exception of the first meeting - which will be on the 27th of March). The first one or two meetings will be mixers - a relax after work, chatting getting to know each other, our work and what our challenges are, etc. It will also be a chance to get to know a bit more about what everyone is after and what people would enjoy from the group. We also spoke about notification of IxD related events such as this evening's 'This happened...'. Everyone is going to take responsibility for tagging these events with 'ixdalondon' on sites such as upcoming.org. I'm going to organise a venue for the next meeting and will keep everyone in the loop. All the best! Alex. Welcome to the Interaction Design Association (IxDA)! To post to this list ... [EMAIL PROTECTED] Unsubscribe http://www.ixda.org/unsubscribe List Guidelines http://www.ixda.org/guidelines List Help .. http://www.ixda.org/help
Re: [IxDA Discuss] Most usable doesn't always mean best solution
On Mar 4, 2008, at 10:59 AM, Elizabeth Buie wrote: Well, there you have it. They're marketing folks. IMNERHO they aren't usability professionals; they're just calling themselves that. They call themselves that and they are doing usability research. Companies are hiring them. I've seen the tapes. I've read the reports. Whether we like it or not, and personally I don't really like it, the reality is that these people are doing usability work and it's rather common. Then would you mind explaining what you had in mind when you said that a design was less usable but more satisfying? Help me out here. Can't. Satisfaction is included in my definition of usability. But as I've said before, not everyone shares my definition of usability (remember those marketing agencies doing usability work?). I have clients in the government, nonprofit, and commercial sectors. Which industry did you have in mind? :-) Based on your site, it looks like your focus is on government and non- profit. While we've done work for both, that's not our focus—we focus more on commercial businesses. However, whenever we deal with government/non-profit, we do have different standards we have to abide by. For example, right now, we're doing work for a very large bank. Actually, the company was acquired last year by a large bank. So, small startup that's now part of one of the world's largest banks. Last year, they weren't bound by 508 compliance and a few other standards that this bank is. Now they are. So, now part of our work is upgrading their systems for them. And btw, it wasn't that they didn't care before, they weren't aware and didn't have the budget for this type of work before. Now they are aware and required so they have to create a budget for it. I am not talking about being bound by ISO standards. I am talking about knowing the definition of usability, which happens to be best captured in ISO 9241/11. This definition comes up rather frequently among people who actually *are* usability professionals. Last year at UPA, I taught an entire day long tutorial on creating data-driven design research persons. Part of that was how to use them in the usability process. During our discussion of usability, not one single person in the room of 50+ ever once referenced the ISO 9241 definition of usability. Now, while this isn't conclusive, I'd think that a crowd at UPA is a pretty good representation of usability professionals. Additionally, I've spoken at a number of UPA groups and have not once heard any reference to ISO 9241. I'm aware there's a standard, but I'll bet you that most people I encounter in the field aren't as well versed on it as you are and couldn't give me the ISO definition. I'm not claiming that my experience is the entire total truth, clearly it's not. But clearly, there's an entire universe out there doing usability work who are totally and completely unaware of the ISO standard definition. Cheers! Todd Zaki Warfel President, Design Researcher Messagefirst | Designing Information. Beautifully. -- Contact Info Voice: (215) 825-7423 Email: [EMAIL PROTECTED] AIM:[EMAIL PROTECTED] Blog: http://toddwarfel.com -- In theory, theory and practice are the same. In practice, they are not. Welcome to the Interaction Design Association (IxDA)! To post to this list ... [EMAIL PROTECTED] Unsubscribe http://www.ixda.org/unsubscribe List Guidelines http://www.ixda.org/guidelines List Help .. http://www.ixda.org/help
[IxDA Discuss] Usability is more than...
In the past few months I've heard rumblings on the list that usability is about more than evaluation (first from Jared and more recently from Elizabeth). I'm not a card-carrying member of UPA, but this is interesting to me and I'd like to learn more about the point of view. I was taught that Design represents the intersection of three attributes: - the useful - the usable - the desirable My entire context for usability has been as an evaluation tool to identify design elements that are initially confusing or that involve a high error rate for some ergonomic reason. In that context, short term learnability almost always trumps everything else. That can be frustrating. I've viewed it as a failing of usability testing; something that seems to be baked in. Now it appears that's not the case. In a recent thread, Elizabeth mentioned satisfaction and effectiveness as components of usability. That seems to frame usability as an analog for design itself. I'm all for disciplinary scope creep, but I want to make sure I understand the position correctly. Without starting a holy war, I'd be interested in opposing perspectives on what constitutes usability. // jeff Welcome to the Interaction Design Association (IxDA)! To post to this list ... [EMAIL PROTECTED] Unsubscribe http://www.ixda.org/unsubscribe List Guidelines http://www.ixda.org/guidelines List Help .. http://www.ixda.org/help
[IxDA Discuss] Job, Interface Designer/Graphic Designer, Pennington, NJ, Recruiter, Full Time Direct Hire
Seeking an innovative graphic designer with strong layout, typography and brand identity skills. Responsibilities include designing interfaces for transactional web pages, data intensive applications and other financial products and services. Candidates must have experience in designing web applications, ecommerce or transactional sites a plus. An on line portfolio of samples must be presented for review. If interested, please share resume and samples in URL or PDF format. Dana M. Christ Merrill Lynch, Corporate Recruiting Email: [EMAIL PROTECTED] mailto:[EMAIL PROTECTED] Phone: 609-274-1122 This message w/attachments (message) may be privileged, confidential or proprietary, and if you are not an intended recipient, please notify the sender, do not use or share it and delete it. Unless specifically indicated, this message is not an offer to sell or a solicitation of any investment products or other financial product or service, an official confirmation of any transaction, or an official statement of Merrill Lynch. Subject to applicable law, Merrill Lynch may monitor, review and retain e-communications (EC) traveling through its networks/systems. The laws of the country of each sender/recipient may impact the handling of EC, and EC may be archived, supervised and produced in countries other than the country in which you are located. This message cannot be guaranteed to be secure or error-free. This message is subject to terms available at the following link: http://www.ml.com/e-communications_terms/. By messaging with Merrill Lynch you consent to the foregoing. Welcome to the Interaction Design Association (IxDA)! To post to this list ... [EMAIL PROTECTED] Unsubscribe http://www.ixda.org/unsubscribe List Guidelines http://www.ixda.org/guidelines List Help .. http://www.ixda.org/help
Re: [IxDA Discuss] Most usable doesn't always mean best solution
I'm a bit confused. You reference the fact that the form takes more time and effort as meaning it's unusable.Efficiency (which is what I assume you are referring to) doesn't just mean faster, it means less wasted time. If the goal if the form was to be more secure and adding more questions accomplished that goal, how is that wasted time to look through more questions? Particularly when the user satisfaction was high. I don't know, but I would guess based on your results from testing that this form is indeed usable. As for the automatic/manual argument, both pass usablility depending on your users goals. It's not a one size fits all solution. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Posted from the new ixda.org http://www.ixda.org/discuss?post=26755 Welcome to the Interaction Design Association (IxDA)! To post to this list ... [EMAIL PROTECTED] Unsubscribe http://www.ixda.org/unsubscribe List Guidelines http://www.ixda.org/guidelines List Help .. http://www.ixda.org/help
Re: [IxDA Discuss] Usability is more than...
On Mar 4, 2008, at 12:01 PM, Jeff Howard wrote: My entire context for usability has been as an evaluation tool to identify design elements that are initially confusing or that involve a high error rate for some ergonomic reason. [...] That seems to frame usability as an analog for design itself[...] Without starting a holy war, I'd be interested in opposing perspectives on what constitutes usability. Jeff, great question. My first response to you would be how did you arrive at your view/perspective on usability? And no, it's not a trick question or trap. According to the ISO, usability is defined as effectiveness, efficiency and satisfaction with which a specified set of users can achieve a specified set of tasks in a particular environment. While I would personally say that it's really goals rather than tasks, I'm not going to get into a semantic debate here on this one. It's close enough to get the point across. While you're correct for the most part about it being an evaluation tool/method, in it's most rigid sense, at my company we couple usability/research with design. I cannot speak for other firms, but that's the way we operate—one informs the other and hold a symbiotic relationship to each other. As for what usability measures/evaluates, well, in my opinion effectiveness, efficiency, and satisfaction consist of: Error frequency, prevention, and recovery—how often are errors made and how well does the system support error prevention (first) and error recovery (second). Efficiency and productivity—how does the system support or hinder the person from doing their job or accomplishing their goal/activity? Learnability—is it immediately intuitive? If not, then how quickly can someone learn to use the system and maintain that knowledge? Satisfaction—to what degree do they like/hate using the system? I'd be interested to hear what others have to say as well. Cheers! Todd Zaki Warfel President, Design Researcher Messagefirst | Designing Information. Beautifully. -- Contact Info Voice: (215) 825-7423 Email: [EMAIL PROTECTED] AIM:[EMAIL PROTECTED] Blog: http://toddwarfel.com -- In theory, theory and practice are the same. In practice, they are not. Welcome to the Interaction Design Association (IxDA)! To post to this list ... [EMAIL PROTECTED] Unsubscribe http://www.ixda.org/unsubscribe List Guidelines http://www.ixda.org/guidelines List Help .. http://www.ixda.org/help
[IxDA Discuss] Upcoming Event: Gel Conference, NYC, April 24-25
Hello, On behalf of Mark Hurst Phil Terry and the folks at Creative Good, I'd like to announce an upcoming event, the 2008 Gel Conference. I attended this conference last year and was significantly influenced by the speakers and concepts to which I was introduced (such as bit literacy, which taught me to how empty out my email InBox at the end of every day and has since made a big difference in the way I work). The Gel conference is a two-day event in New York every April. The name Gel is short for Good Experience Live, and it explores good experience not just in the online world but in *all* areas - art, business, technology, creativity, and so on. Gel 2008 is next month - on Thursday-Friday, April 24-25 - see info here: http://gelconference.com/c/gel08.php Past Gel speakers include radio host Ira Glass, artists Christo Jeanne-Claude, Bob Mankoff (New Yorker cartoon editor), and many others - you can see video clips here: http://gelconference.com/videos.php On the first day, Thursday, attendees have direct experiences all across New York City; on Friday, speakers present in the theater for 20 minutes each - this way Gel can fit about 15 speakers into the day. Gel is a very diverse, multidisciplinary event, both in the speakers and the attendees. See the range of attendees at last year's conference: http://gelconference.com/07/attendees.php By attending an event that mostly features people *outside* our discipline, we have a better chance of learning patterns and examples that we can apply *within* our discipline, in new ways. Sign up soon, since there aren't many tickets left: http://gelconference.com/c/gel08.php Regards, Gloria Welcome to the Interaction Design Association (IxDA)! To post to this list ... [EMAIL PROTECTED] Unsubscribe http://www.ixda.org/unsubscribe List Guidelines http://www.ixda.org/guidelines List Help .. http://www.ixda.org/help
Re: [IxDA Discuss] IxDA London meet-up, more meetings - and money!
Thanks for all your work Alex - It was great to meet everyone last night - looking forward to further meetings. Joe -- http://formd.net Welcome to the Interaction Design Association (IxDA)! To post to this list ... [EMAIL PROTECTED] Unsubscribe http://www.ixda.org/unsubscribe List Guidelines http://www.ixda.org/guidelines List Help .. http://www.ixda.org/help
[IxDA Discuss] Designing an Analytics UI
I'm about to start designing the UX and UI for the analytics portion of an RIA. (Flex) Anybody have any links/books they'd like to share discussing the display of data, interactivity, preferred visualizations etc.? Thanks, B Welcome to the Interaction Design Association (IxDA)! To post to this list ... [EMAIL PROTECTED] Unsubscribe http://www.ixda.org/unsubscribe List Guidelines http://www.ixda.org/guidelines List Help .. http://www.ixda.org/help
Re: [IxDA Discuss] Usability is more than...
I agree with Todd's criteria for evaluating usability. We have the same criteria plus we branch out learnability into memorability. In other words, can someone come into an application, start using it, walk away for a week or two and then come back in and interact without having to relearn everything. We recently built a CMS for internal sites and have been conducting training. Users come back a week or two later with similar questions from before. In that case, I think we need to work on memorability and need to adjust a few things. I'll also cast my vote, two if I could, that satisfaction plays a critical role in usability. I've observed many sessions where users aren't thrilled with certain aspects and become reluctant to use it. Jason . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Posted from the new ixda.org http://www.ixda.org/discuss?post=26788 Welcome to the Interaction Design Association (IxDA)! To post to this list ... [EMAIL PROTECTED] Unsubscribe http://www.ixda.org/unsubscribe List Guidelines http://www.ixda.org/guidelines List Help .. http://www.ixda.org/help
Re: [IxDA Discuss] Usability is more than...
Here is how I think of it, Jeff. Usability is a dimension of design. I like the construct of useful, usable and desirable which you can think of as three dimensions that a good design requires. Each of these dimensions has associated with it various tool and techniques. Usability testing is a technique that can be used to assess (some aspects of) usability. Other techniques like persona development also contribute to usability. For me, this makes it all pretty simple. A good design must be usable. But usability is not the only characteristic of a good design. Charlie Welcome to the Interaction Design Association (IxDA)! To post to this list ... [EMAIL PROTECTED] Unsubscribe http://www.ixda.org/unsubscribe List Guidelines http://www.ixda.org/guidelines List Help .. http://www.ixda.org/help
Re: [IxDA Discuss] Usability is more than...
Todd wrote: My first response to you would be how did you arrive at your view/perspective on usability? My initial exposure to usability was self-taught through Nielsen's Designing Web Usability and Krug's Don't Make Me Think. At Carnegie Mellon's School of Design, they break design research into three fluid phases: exploratory, generative and evaluative, with the last focused on usability testing. None of the phases exist in a bubble and they all feed back into the design process. For me, usability mostly involves guerilla cubicle testing, though I've done a few more formal studies; one for a mobile wayfinding system and one for a consumer electronics project. Both involved people with no prior exposure to the design, so learnability was key to both. Both also stretched over the course of a week with rapid design iteration between subjects. In all cases that I'm familiar with, usability testing bears more resemblance to a cross-sectional study than a longitudinal study. // jeff . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Posted from the new ixda.org http://www.ixda.org/discuss?post=26788 Welcome to the Interaction Design Association (IxDA)! To post to this list ... [EMAIL PROTECTED] Unsubscribe http://www.ixda.org/unsubscribe List Guidelines http://www.ixda.org/guidelines List Help .. http://www.ixda.org/help
Re: [IxDA Discuss] Usability is more than...
For those who include satisfaction under usability, is there anything you include beyond usability in determining whether a design is good or is usability a synonym for good design? I'll also cast my vote, two if I could, that satisfaction plays a critical role in usability. I've observed many sessions where users aren't thrilled with certain aspects and become reluctant to use it. Welcome to the Interaction Design Association (IxDA)! To post to this list ... [EMAIL PROTECTED] Unsubscribe http://www.ixda.org/unsubscribe List Guidelines http://www.ixda.org/guidelines List Help .. http://www.ixda.org/help
Re: [IxDA Discuss] Designing an Analytics UI
Tufte's books and particularly Stephen Few's books for dashboard design are very good. - Russ blog: http://www.dexodesign.com/ http://www.dexodesign.com/about.html On Tue, Mar 4, 2008 at 12:27 PM, Brandon E.B. Ward [EMAIL PROTECTED] wrote: I'm about to start designing the UX and UI for the analytics portion of an RIA. (Flex) Anybody have any links/books they'd like to share discussing the display of data, interactivity, preferred visualizations etc.? Thanks, B Welcome to the Interaction Design Association (IxDA)! To post to this list ... [EMAIL PROTECTED] Unsubscribe http://www.ixda.org/unsubscribe List Guidelines http://www.ixda.org/guidelines List Help .. http://www.ixda.org/help -- Russell Wilson Vice President of Product Design, NetQoS Blog: http://www.dexodesign.com Welcome to the Interaction Design Association (IxDA)! To post to this list ... [EMAIL PROTECTED] Unsubscribe http://www.ixda.org/unsubscribe List Guidelines http://www.ixda.org/guidelines List Help .. http://www.ixda.org/help
[IxDA Discuss] Design Deliverables and Developers
One of the things I am interested as a designer is how we can work better with developers. If you are lucky enough to work as part of an in-house team you probably (hopefully) have a stronger relationship with developers than those of use who only come in as consultants. Often as a consultant, the only contact we have with the development team might be through the project manager or technical lead. So we must rely on our design documents to deliver our message. Although we would all like our deliverables to be developer-friendly, they don't always turn out that way. Many of the guidelines I've read for creating client deliverables focus on impressing the client and not necessarily getting work done. Sure, they also try to present the information in a way that readers can understand them, but project managers are a much different audience than developers who are actually doing the work. Does anyone know of studies or other research that explicitly looks at how developers are using design deliverables in practice? Particularly integrating things such as wireframes in to functional specifications. Or even if developers get the wireframes and mockups we give them. I've found that developers prefer annotated slides or a big numbered list of issues to having to read anything big, but those types of things don't look as nice as a fully written final report for the project manager. Thoughts? ~ Celeste -- Celeste 'seele' Paul www.obso1337.org Welcome to the Interaction Design Association (IxDA)! To post to this list ... [EMAIL PROTECTED] Unsubscribe http://www.ixda.org/unsubscribe List Guidelines http://www.ixda.org/guidelines List Help .. http://www.ixda.org/help
Re: [IxDA Discuss] Design Deliverables and Developers
Though I do not have any research to backup your question, I do have a lot of experience with handing off my designs/code to developers. Rule #1: Be as specific as possible! :) Our team typically goes through many iterations of design with the business clients and project manager before handing anything to developers. With this audience, we are presenting glossy mockups of the application along with any necessary large-print diagrams. We are doing everything possible to sell the design to the clients. At the point of handing off to developers, we repackage the designs into something more relevent to the developers. We call this converted document a User Interface Specification Document. This document has a screenshot of the mockup with numbers next to all of the screen components (fields, labels, images, widgets, etc). Later in the document we list the numbers along with all the necessary data that a developer cares about: field length, validation, onblur, onfocus, onload, size, height, width, etc... In this way, we hand off a high-fidelity mockup with a detailed document explaining how everything works on the screen. Does that help? Rob On Tue, 4 Mar 2008 15:15:33 -0500, Celeste 'seele' Paul [EMAIL PROTECTED] wrote: Does anyone know of studies or other research that explicitly looks at how developers are using design deliverables in practice? Particularly integrating things such as wireframes in to functional specifications. Or even if developers get the wireframes and mockups we give them. I've found that developers prefer annotated slides or a big numbered list of issues to having to read anything big, but those types of things don't look as nice as a fully written final report for the project manager. Thoughts? ~ Celeste Welcome to the Interaction Design Association (IxDA)! To post to this list ... [EMAIL PROTECTED] Unsubscribe http://www.ixda.org/unsubscribe List Guidelines http://www.ixda.org/guidelines List Help .. http://www.ixda.org/help
[IxDA Discuss] Email Registration
Hi list, When designing sites, I often come up against the question of what required fields to include for an Email Registration form. By Email Registration I mean registering for updates/promotions from the site. I have always felt that less fields is a better approach (ie. just email address if possible), but sometimes various stakeholders want to capture other data like name and location so it can be used for other marketing efforts. Any thoughts/research on this? Like are people people deterred when they see too many fields? Thanks, Jason Welcome to the Interaction Design Association (IxDA)! To post to this list ... [EMAIL PROTECTED] Unsubscribe http://www.ixda.org/unsubscribe List Guidelines http://www.ixda.org/guidelines List Help .. http://www.ixda.org/help
Re: [IxDA Discuss] Design Deliverables and Developers
I view design deliverables in the same way as I view whatever it is that I'm designing: I'm building something for *someone*, so in order to get it right, I must consult with them and understand their needs. It's more important to me that I deliver something that conveys functionality and behavior effectively without creating too much noise, i.e., usable documentation. In my most recent project, I communicated with the developer as I worked on the documentation, providing him with samples of different options (in the context of the project) so he could choose which type of documentation best suited him. Additionally, I'd recommend encouraging communication during the development process when possible as things invariably arise that weren't covered in the documentation. Does anyone know of studies or other research that explicitly looks at how developers are using design deliverables in practice? Particularly integrating things such as wireframes in to functional specifications. Or even if developers get the wireframes and mockups we give them. I've found that developers prefer annotated slides or a big numbered list of issues to having to read anything big, but those types of things don't look as nice as a fully written final report for the project manager. Welcome to the Interaction Design Association (IxDA)! To post to this list ... [EMAIL PROTECTED] Unsubscribe http://www.ixda.org/unsubscribe List Guidelines http://www.ixda.org/guidelines List Help .. http://www.ixda.org/help
Re: [IxDA Discuss] Design Deliverables and Developers
This is something I deal with nearly every day - especially as we have 2 week dev cycles between product releases. Everyone who has replied to the thread already has provided sage advice. Let's put it this way... most developers never get more than a few bullet points for specs or as inputs while many others still work in environments of oral history where deliverables are verbally explained but never written! So, when a developer gets design docs and/or functional specs - even imperfect ones, they are often happy. The more you involve them in the process and the better you are in communicating with developers as part of your deliverables, the smoother the experience will be but to actually have something written that illustrates what the desired output should be and explains what happens if 'user X clicks on a button' and man, you'll be ahead of the game. On 3/4/08, Celeste 'seele' Paul [EMAIL PROTECTED] wrote: One of the things I am interested as a designer is how we can work better with developers. If you are lucky enough to work as part of an in-house team you probably (hopefully) have a stronger relationship with developers than those of use who only come in as consultants. Often as a consultant, the only contact we have with the development team might be through the project manager or technical lead. So we must rely on our design documents to deliver our message. Although we would all like our deliverables to be developer-friendly, they don't always turn out that way. Many of the guidelines I've read for creating client deliverables focus on impressing the client and not necessarily getting work done. Sure, they also try to present the information in a way that readers can understand them, but project managers are a much different audience than developers who are actually doing the work. Does anyone know of studies or other research that explicitly looks at how developers are using design deliverables in practice? Particularly integrating things such as wireframes in to functional specifications. Or even if developers get the wireframes and mockups we give them. I've found that developers prefer annotated slides or a big numbered list of issues to having to read anything big, but those types of things don't look as nice as a fully written final report for the project manager. Thoughts? ~ Celeste -- Celeste 'seele' Paul www.obso1337.org Welcome to the Interaction Design Association (IxDA)! To post to this list ... [EMAIL PROTECTED] Unsubscribe http://www.ixda.org/unsubscribe List Guidelines http://www.ixda.org/guidelines List Help .. http://www.ixda.org/help -- -- www.flyingyogi.com -- Welcome to the Interaction Design Association (IxDA)! To post to this list ... [EMAIL PROTECTED] Unsubscribe http://www.ixda.org/unsubscribe List Guidelines http://www.ixda.org/guidelines List Help .. http://www.ixda.org/help
Re: [IxDA Discuss] Email Registration
Jason, It depends on the offer. If what you're offering is compelling enough, people will fill out more fields. If you're asking for personal information that doesn't seem (from the customer's POV) to be relevant, you've either got to do a good job explaining how collecting this data benefits THEM, or the offer has to be so worthwhile, it overcomes their resistance. On Mar 4, 2008, at 3:46 PM, Jason Wei Lee wrote: Hi list, When designing sites, I often come up against the question of what required fields to include for an Email Registration form. By Email Registration I mean registering for updates/promotions from the site. I have always felt that less fields is a better approach (ie. just email address if possible), but sometimes various stakeholders want to capture other data like name and location so it can be used for other marketing efforts. Any thoughts/research on this? Like are people people deterred when they see too many fields? -- Kim + + + + + + + + + + + + + + + + + + Kim Bieler Graphic Design www.kbgd.com + + + + + + + + + + + + + + + + + + Welcome to the Interaction Design Association (IxDA)! To post to this list ... [EMAIL PROTECTED] Unsubscribe http://www.ixda.org/unsubscribe List Guidelines http://www.ixda.org/guidelines List Help .. http://www.ixda.org/help
Re: [IxDA Discuss] Design Deliverables and Developers
On Tuesday 04 March 2008 15:24:03 Rob Nero wrote: In this way, we hand off a high-fidelity mockup with a detailed document explaining how everything works on the screen. Do you create a separate client deliverable or give the same thing to you project contact (or are you part of an integrated or in-house team so plop factor doesn't matter as much). On Tuesday 04 March 2008 15:46:14 Jason Zietz wrote: In my most recent project, I communicated with the developer as I worked on the documentation, providing him with samples of different options (in the context of the project) so he could choose which type of documentation best suited him. Additionally, I'd recommend encouraging communication during the development process when possible as things invariably arise that weren't covered in the documentation. I always prefer to work closely with developers, but that doesn't always happen. That is why I am so interested (and concerned) about deliverables. A wireframe can be both a helpful and dangerous tool, depending on how much you read (or don't read) in to it. Also, developers are used to different kinds of documentation, so a written point-by-point specification might resonate with them more than a picture. Who knows? (That is why I am asking these questions). On Tuesday 04 March 2008 16:02:55 Ari Feldman wrote: most developers never get more than a few bullet points for specs or as inputs while many others still work in environments of oral history where deliverables are verbally explained but never written! So, when a developer gets design docs and/or functional specs - even imperfect ones, they are often happy. I totally agree unless they are handed an 80 page report of 6 months of research. And a cup of coffee. And some aspirin. There are lots of things that should happen in a project -- clear product goals and documentation, communicating with developers, writing perfect reports, lots of extras to tape on the wall -- but they don't always happen. Maybe it is just the capacity I work in (aka miracle worker) that nothing goes as planned. I usually get called in to the middle of a project which is in serious trouble and get caught between backfilling necessary user research and fixing it now. It is really about making the best of what you got and hoping your message gets across. And being thankful the client is thinking about these things at all. Is there a SIG for Guerrilla Design? -- Celeste 'seele' Paul www.obso1337.org Welcome to the Interaction Design Association (IxDA)! To post to this list ... [EMAIL PROTECTED] Unsubscribe http://www.ixda.org/unsubscribe List Guidelines http://www.ixda.org/guidelines List Help .. http://www.ixda.org/help
[IxDA Discuss] web-Second Life registration process
I'm working on a project for a client that has a presence in Second Life, but wants their customers to register through their own site first. This is partly so they can customize the user's SL experience, and partly because some of the target audiences may not be familiar with SL. Putting aside the rather large question of whether SL is in fact the appropriate platform for what they're trying to accomplish (which has been raised repeatedly), I'm wondering if anyone can share examples of similar web/SL hybrid experiences. The one I have found thus far that mirrors the approach my client wishes to take is the CSI:NY Virtual Experience: http://alpha.cbs.com/primetime/csi_ny/second_life/ http://csi-ny.reg.electricsheepcompany.com/join-secondlife/csi-ny/avatar The CSI web site has a registration wizard that allows you select a custom avatar, name, etc. Then, when you download and run the SL app, it drops you into a special CSI:NY orientation island that explains the rules of the CSI game. Is anyone aware of any similar registration processes - where the registration takes place partly or entirely outside of SL? Thanks, Patrick Welcome to the Interaction Design Association (IxDA)! To post to this list ... [EMAIL PROTECTED] Unsubscribe http://www.ixda.org/unsubscribe List Guidelines http://www.ixda.org/guidelines List Help .. http://www.ixda.org/help
Re: [IxDA Discuss] Design Deliverables and Developers
We have moved away from comprehensive PRD, DRD and TRD's. They are slow, painful. They also tend to reduce dialog. As a designer, I really like the interaction and realtime dialog with the dev group. They are included up front so that the communication during the dev cycle is pretty open. This helps to make the dev review a little less harsh. As for docs, we deliver mocks - typically as pdf with layered annotation. Often times we script the interactions with flash or html, but that is fairly rare. We also have a wiki for nearly every project and nearly daily team updates. Mark On Tue, Mar 4, 2008 at 3:15 PM, Celeste 'seele' Paul [EMAIL PROTECTED] wrote: One of the things I am interested as a designer is how we can work better with developers. If you are lucky enough to work as part of an in-house team you probably (hopefully) have a stronger relationship with developers than those of use who only come in as consultants. Often as a consultant, the only contact we have with the development team might be through the project manager or technical lead. So we must rely on our design documents to deliver our message. Although we would all like our deliverables to be developer-friendly, they don't always turn out that way. Many of the guidelines I've read for creating client deliverables focus on impressing the client and not necessarily getting work done. Sure, they also try to present the information in a way that readers can understand them, but project managers are a much different audience than developers who are actually doing the work. Does anyone know of studies or other research that explicitly looks at how developers are using design deliverables in practice? Particularly integrating things such as wireframes in to functional specifications. Or even if developers get the wireframes and mockups we give them. I've found that developers prefer annotated slides or a big numbered list of issues to having to read anything big, but those types of things don't look as nice as a fully written final report for the project manager. Thoughts? ~ Celeste -- Celeste 'seele' Paul www.obso1337.org Welcome to the Interaction Design Association (IxDA)! To post to this list ... [EMAIL PROTECTED] Unsubscribe http://www.ixda.org/unsubscribe List Guidelines http://www.ixda.org/guidelines List Help .. http://www.ixda.org/help Welcome to the Interaction Design Association (IxDA)! To post to this list ... [EMAIL PROTECTED] Unsubscribe http://www.ixda.org/unsubscribe List Guidelines http://www.ixda.org/guidelines List Help .. http://www.ixda.org/help
[IxDA Discuss] JOB - User Interface Architect ~ San Francisco area ~ Cisco Systems ~ Full Time
COMPANY NAME: Ironport division of Cisco LOCATION: San Bruno, CA (just south of San Francisco) JOB TITLE: User Interface Architect DURATION: Full Time Employment CONTACT: dalloyd at cisco.com JOB DESCRIPTION: IronPort, acquired by Cisco in April 2007, is a proven leader of anti-spam, anti-virus and anti-spyware appliances for organizations ranging from small businesses to the Global 2000. The IronPort User Interface Development team is looking for a leader to develop and architect the next generation of its Email and Web Security Appliance GUIs. Responsibilities: The UI Development team is looking for a candidate with strong technical leadership skills, enthusiasm for new technology, leadership in building scalable, efficient and flexible UI platforms. This individual will collaborate with product management and engineering architects to help identify and prioritize product requirements; work closely with design consultants to design new features and improve existing functionality and behavioral paradigms; and organize, participate in, and ensure the success of the ongoing development activities for the products' CLI and web based GUIs. Key responsibilities include: Define UI architecture and roadmap Manage UI coding standards and guidelines Strategic planning of UI platform development Task level planning and management of project deliverables Ownership of the quality of all code written by UI developers Required Experience and Skills: Demonstrated success in the development and deployment of enterprise application GUI. 10-15 years of industry experience with 8-10 years programming experience preferably in one or more of these scripting languages: Python, PHP, Perl, ASP.NET, Ruby, etc. Practical experience with XHTML, CSS2, and JavaScript. Strong attention to detail and exceptional organization, logic, and analytic skills Communicate effectively throughout all phases of the life cycle with product management, software development, technical documentation and QA Demonstrated ability to ask appropriate questions, communicate effectively and persuasively convey design solutions to a broad range of stakeholders including product managers, engineers, interaction designers, and customers Desired Experience and Skills: Experience developing thin-client, browser-based, commercial appliance, server application administration, or consumer-oriented user interfaces. Experience developing commercial or corporate intranet applications is also a plus. An understanding of Internet and email standards, UNIX system administration, enterprise networking topologies and security is highly desirable. Experience with open source mail, spam detection programs, caching web proxies, anti-spyware, anti-virus and integration of database technology to customer systems a definite plus. Experience collaborating with remote development teams is a plus Welcome to the Interaction Design Association (IxDA)! To post to this list ... [EMAIL PROTECTED] Unsubscribe http://www.ixda.org/unsubscribe List Guidelines http://www.ixda.org/guidelines List Help .. http://www.ixda.org/help
Re: [IxDA Discuss] Design Deliverables and Developers
I am apart of an integrated in-house team. Everyone involved with a given project is employed by the same company. So that does give me an advantage that I can easily go over to any developer's cube and chat with him/her about my design or what they need. We will create separate deliverables depending on the recipient. The business clients and project manager will receive just the screen designs and high-level diagrams of flow and interaction. The developers would receive the ultra-detailed spec documents of each screen in the application. We typically create a separate spec doc for each screen in a web app. Like you say… things usually never go as planned. Even though I can create the frontend html code and hand that off with a full spec doc for each screen… the final app typically does not look exactly how I had envisioned it. Things get lost in translation. :) On Tue, 4 Mar 2008 16:23:56 -0500, Celeste 'seele' Paul [EMAIL PROTECTED] wrote: On Tuesday 04 March 2008 15:24:03 Rob Nero wrote: In this way, we hand off a high-fidelity mockup with a detailed document explaining how everything works on the screen. Do you create a separate client deliverable or give the same thing to you project contact (or are you part of an integrated or in-house team so plop factor doesn't matter as much). Welcome to the Interaction Design Association (IxDA)! To post to this list ... [EMAIL PROTECTED] Unsubscribe http://www.ixda.org/unsubscribe List Guidelines http://www.ixda.org/guidelines List Help .. http://www.ixda.org/help
[IxDA Discuss] Call for participation: Study #07-12643 Persona Usage Evaluation in Design Field
Dear Sir/Madam: This is Yen-ning Chang, second year master student in School of Informatics, Indiana University, Bloomington. I am doing a research about the usage of persona in design field. Your participation in this study will help me understand how professionals use persona in practice, also your values and ideas about that. This study is a brief online survey which aims to know your experience and reflection of using or not-using persona. It is completely anonymous and will take about 15 minutes of your time. Your opinions will provide valuable input to my research. If you wish to participate in this study, please visit the survey page by clicking on the link below, where you will find a study information sheet: http://www.surveymonkey.com/s.aspx?sm=2W0kbn4HUFcTFBEavPKjuQ%3d%3d Thanks very much for your time. Wish you have a wonderful day, Best, Yen-ning Chang Human-Computer Interaction Design School of Informatics Indiana University, Bloomington PS: Please feel free to forward this invitation to any other list or person who may be interested in the experiment. Thank you. Welcome to the Interaction Design Association (IxDA)! To post to this list ... [EMAIL PROTECTED] Unsubscribe http://www.ixda.org/unsubscribe List Guidelines http://www.ixda.org/guidelines List Help .. http://www.ixda.org/help
Re: [IxDA Discuss] Design Deliverables and Developers
From: Celeste 'seele' Paul [EMAIL PROTECTED] Does anyone know of studies or other research that explicitly looks at how developers are using design deliverables in practice? Particularly integrating things such as wireframes in to functional specifications. Or even if developers get the wireframes and mockups we give them. I've found that developers prefer annotated slides or a big numbered list of issues to having to read anything big, but those types of things don't look as nice as a fully written final report for the project manager. Some opinions/questions: 1. Why only have one deliverable? If you're convinced developers want something diferent from what the client liason wants, design your deliverables that way. Have a section in your spec marked For developers or create two seperate documents for the two different purposes. 2. By far the most common thing I've seen developers do with design documents, if anything at all, is hold up screenshots in the printed doc next to the screen and work to make 'em match. In fact I've had many programmers tell me they skip through the spec, and mostly focus on the screens. Like Rob suggests, make sure any screenshots you have are labeled with font names, Hex codes for colors, font sizes, pixel widths, etc. to make it as easy as possible to get those details right. The easier you make those precise details to understand, the higher the odds the developer will actually do them. 2+. Do an informal usability study on your deliverables - Seriously, have you ever watched someone actually use what you make? Or gotten feedback from them on how it could have been more useful? Or gone back later to see how much of what was in your deliverable actually made it into the final release? If you treat your delvierables like a user experience, you can apply tons of basic UX techniques to your specs, prototypes, wireframes, reports, etc. 3. Ask, early, to have at least one meeting with an actual developer, even if it's with the project liason from your client also there. That will give you a chance to ask the developer directly how they like to work, what they're most concerned about and what the best way is to help them with your talents. Even a 5 minute meeting will make it more comfortable to follow up later and ask questions. Design documents are worthless without a relationship behind them - there are always assumptions and interpretations and without a relationship there is no effective way to resolve them. Initiate contact, ask for feedback, and follow up later to ask if there are questions or problems. 4. Every consultancy and client are different - so if you're not sure how the stuff you make is being used on any project, go find out. It's entirely reasonable for you to ask your clients about this, since the more you know about how your stuff is used (even if it's being mostly ignored) the higher the odds you'll make something more useful next time. -Scott Scott Berkun www.scottberkun.com Welcome to the Interaction Design Association (IxDA)! To post to this list ... [EMAIL PROTECTED] Unsubscribe http://www.ixda.org/unsubscribe List Guidelines http://www.ixda.org/guidelines List Help .. http://www.ixda.org/help
Re: [IxDA Discuss] Design Deliverables and Developers
On Tuesday 04 March 2008 17:11:23 Scott Berkun wrote: 1. Why only have one deliverable? If you're convinced developers want something diferent from what the client liason wants, design your deliverables that way. Have a section in your spec marked For developers or create two seperate documents for the two different purposes. Personally I create two deliverables, the big fat report for project manager to put on his shelf and then something more useful for developers to refer to that corresponds with the report and is easier to flip through and print. Basically I asked these questions because I was curious to see how other people are handling this problem. 2+. Do an informal usability study on your deliverables - Seriously, have you ever watched someone actually use what you make? Or gotten feedback from them on how it could have been more useful? Or gone back later to see how much of what was in your deliverable actually made it into the final release? If you treat your delvierables like a user experience, you can apply tons of basic UX techniques to your specs, prototypes, wireframes, reports, etc. ^ This is something I'm planning on doing. I brought up this discussion to fill in anything I might not have thought of. -- Celeste 'seele' Paul www.obso1337.org Welcome to the Interaction Design Association (IxDA)! To post to this list ... [EMAIL PROTECTED] Unsubscribe http://www.ixda.org/unsubscribe List Guidelines http://www.ixda.org/guidelines List Help .. http://www.ixda.org/help
Re: [IxDA Discuss] Design Deliverables and Developers
Also, I highly, highly recommend Dan Brown's book Designing Documentation. Pretty much covers most deliverables for a project. That said, I always try to do some interviews with developers to find out what speaks to them. joe . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Posted from the new ixda.org http://www.ixda.org/discuss?post=26800 Welcome to the Interaction Design Association (IxDA)! To post to this list ... [EMAIL PROTECTED] Unsubscribe http://www.ixda.org/unsubscribe List Guidelines http://www.ixda.org/guidelines List Help .. http://www.ixda.org/help
Re: [IxDA Discuss] Usability is more than...
Charles B. Kreitzberg wrote: Here is how I think of it, Jeff. Usability is a dimension of design. I like the construct of useful, usable and desirable which you can think of as three dimensions that a good design requires. Very well put -- and with apedigree going back to Vitrivius' desired qualities in a building: Firmness, Commodity, and Delight - Jim Welcome to the Interaction Design Association (IxDA)! To post to this list ... [EMAIL PROTECTED] Unsubscribe http://www.ixda.org/unsubscribe List Guidelines http://www.ixda.org/guidelines List Help .. http://www.ixda.org/help
Re: [IxDA Discuss] Design Deliverables and Developers
Hi Celeste, I work with an in-house dev team and find they are truly grateful when I document a handful of details in addition to the general broad brush-strokes of wireframes, layouts, etc: - Error and status messages, especially when a consistent word order format is used. - Dimensions of images and graphical assets. - State charts of complex controls (you click this here and that lights up there, except when this other deelie is held down). What these have in common is they're all head-scratchers that take the poor developer out of flow and make them puzzle over what really ought to happen in a situation. They have to stop being a developer and start being a designer. I know (from trying to switch back the other way sometimes) that this is a difficult leap to make quickly. Some simple web forms get total documentation of a quickie Visio wireframe drawing and a page of accompanying text and that's it, everybody's happy, but more complex rich client components may end up with many pages of detailed docs plus some sort of prototype to play with. Oh one other thing I've noticed is that product managers and marketing folks love to extract high-level feature lists from development requirements docs and use them for their own nefarious purposes. So I've been putting this information in tables lately in an intro section to make it easier for them. Michael Micheletti Welcome to the Interaction Design Association (IxDA)! To post to this list ... [EMAIL PROTECTED] Unsubscribe http://www.ixda.org/unsubscribe List Guidelines http://www.ixda.org/guidelines List Help .. http://www.ixda.org/help
Re: [IxDA Discuss] web-Second Life registration process
A few more uses of Second Life's custom registration portal API: http://secondlife.reuters.com/stories/2007/05/04/new-orientation-islands-take-off/ http://www.timewarner.com/corp/newsroom/pr/0,20812,1675445,00.html http://freshtakes.typepad.com/sl_communicators/2007/06/slbc_meeting_tr.html http://blogs.electricsheepcompany.com/cory/?p=30 http://virtualworlds.nmc.org/wp-content/uploads/2008/01/press-release-nmc-virtual-worlds-2008-plans.pdf More information about the API is at http://wiki.secondlife.com/wiki/RegAPI . Looks like they're limiting new signups, but I have no idea how strictly. My company does Second Life work, so I might get to find out sometime soon Jennifer Berk Amplify Public Affairs On Tue, Mar 4, 2008 at 4:30 PM, Patrick Grizzard [EMAIL PROTECTED] wrote: I'm working on a project for a client that has a presence in Second Life, but wants their customers to register through their own site first. This is partly so they can customize the user's SL experience, and partly because some of the target audiences may not be familiar with SL. Putting aside the rather large question of whether SL is in fact the appropriate platform for what they're trying to accomplish (which has been raised repeatedly), I'm wondering if anyone can share examples of similar web/SL hybrid experiences. The one I have found thus far that mirrors the approach my client wishes to take is the CSI:NY Virtual Experience: http://alpha.cbs.com/primetime/csi_ny/second_life/ http://csi-ny.reg.electricsheepcompany.com/join-secondlife/csi-ny/avatar The CSI web site has a registration wizard that allows you select a custom avatar, name, etc. Then, when you download and run the SL app, it drops you into a special CSI:NY orientation island that explains the rules of the CSI game. Is anyone aware of any similar registration processes - where the registration takes place partly or entirely outside of SL? Thanks, Patrick Welcome to the Interaction Design Association (IxDA)! To post to this list ... [EMAIL PROTECTED] Unsubscribe http://www.ixda.org/unsubscribe List Guidelines http://www.ixda.org/guidelines List Help .. http://www.ixda.org/help Welcome to the Interaction Design Association (IxDA)! To post to this list ... [EMAIL PROTECTED] Unsubscribe http://www.ixda.org/unsubscribe List Guidelines http://www.ixda.org/guidelines List Help .. http://www.ixda.org/help
