Welcome to TiddlyWiki created by Jeremy Ruston, Copyright © 2007 UnaMesa Association
Between delivering on funded projects and fighting fires, it’s quite difficult to leave time for any forward-looking, strategic efforts. Yet for many UX groups, this is where we could add the most value—demonstrating ways in which things could be significantly better. And as a leader in a large company, I had to be able to defend how every bit of our time—no matter how large or small— fits into the overall strategic direction. This is especially the case where resources are tight and you have to make tradeoff and priority decisions that don’t sit well with some.
I developed the ‘blueprint’ model to help facilitate these discussions, discern the important from the urgent, and communicate these real priorities in a way that makes sense to executive management.
A tiered-look at how much fidelity IAs can convey concepts to clients and visual designers. From a bulleted list of components to pixel-perfect wireframes, the level of granularity presented greatly dictates what the final visual product looks like. There is a middle ground between lo-fi and hi-fi conceptualization allowing a client to understand what a proposed experience will entail and provide enough freedom for visual design to take the initial conceptual work to the next step.
By presenting too much visual information to a designer, they (and at times, the client) become wed to the annotated experience shown to them. This experience is regurgitated as the final product with a technicolor glow. On the other hand, if you give a visual designer (and the client) too little information, you may end up with an unusable experience lacking any sense of congruity.
With technology changing at a meteoric pace, the concept of ‘The Fold’ on a web site has quickly become a moving target. What once was good for CRT monitors no longer applies to laptops and widescreen LCD displays. Not to mention the fact that recent studies show that site visitors are most certainly not adverse to scrolling.
The fold line is better represented today by a belt. A band of no-man’s land that can help identify the best placement for banner ads and may help quell those stakeholders vying for prime homepage real estate as the fold is no longer an exact science.
http://www.iasummit.org/proceedings/2008/reducing_global_attitudes_into
For the last year I have been working on a global redesign for a blue chip oil company. One of our key objectives in this project has been to attend to the fractured brand personality. A symptom of a large number of country websites performing as single entities each with a unique taxonomy and brand personality. The client requested a fixed online configuration that could be rolled out to 84 countries to be populated with local content. Our local website had to deliver a consistent brand experience across business units and geographies. Local websites had to mirror the global content structure and look and feel to create a single more powerful brand personality
After many months of concepting and requirements gathering we had the bones of a website we felt happy to proceed with. Deciding to roll out a single online “packaged solution” to 84 different countries was not going to be acceptable without solid evidence that our single solution was robust enough to satisfy an enormous and diverse global audience. We had to be certain that our proposed solution was not purely Euro centric, and so I embarked on a month long multi national user testing tour.
I met with 35 representative users in 7 countries on 4 continents and sat them before the same prototype. What I found was that some assumed problem areas were not at all the obstacles I imagined they would be. And some seemingly unimportant cultural differences in the way people interacted with the prototype would have wide reaching effects on our content structure and user interface. Users in China, for example, had to be incentivized to use the website.
Many of these subtle differences might seem to be obvious but the impact they had on our content structure and Interface design was far reaching. This case study will outline some of the observations I made about the way people view and navigate a website based on where they live and how those observations began to reshape the way we composed our local online strategy.
http://www.iasummit.org/proceedings/2008/a_management_fable_the_little
UX management often feels like a mystic art. It can entail moving people and processes within an organization without the enchantment of an official mandate. In fact, UX managers usually need to work their magic from inside other managers’ kingdoms. Business owners control a project’s strategic development; engineers own construction; and Marketing teams frequently manage implementation.
This presentation will deconstruct an illustrated fable about an intrepid little creature who introduces user goals to a development process that would have otherwise been dominated by royal business owners and technological black magic. The deconstruction will surface issues around user types, user-based requirements gathering, scope creep and implementation anxiety.
The presentation will provide current and potential supervisors with specific tactics for successfully managing UX resources within an organization and provide the forum for seasoned veterans to talk about their own exploits rescuing user experiences from the clutches of evil forces.
Aaron Martlage is the managing designer of Electronic Ink’s Design team. The team is responsible for creating user interface concepts for web and desktop applications including information architecture, wireframes, aesthetics and icons. The team also designs portals and dashboards for client intranets and extranets.
Aaron’s recent successes at Electronic Ink include the design of information architecture for a hospital information system, the design of a dashboard and framework for a major software vendor, the rearchitecture of multiple Content Management Systems, and the design of information architecture as well as aesthetic direction for a data playback system comprised of audio, video, radar and network data.
Prior to Electronic Ink, Aaron led teams of designers and human factors specialists for Siemens Corporate Research designing enterprise product user interfaces for the NYCT Subway PA/CIS System, Building Management Systems, and Medical Imaging Software Frameworks in the US, Germany and Hungary. He has coordinated user experience testing in Belgium, the Netherlands, Germany, and the US. He also designed solutions at Siemens Medical Solutions for their next generation hospital information system focusing on Cardiology, Radiology, and the product Portal and Workflow.
Aaron is a Certified Scrum Master bringing agile project management techniques to design to help lead the front in iterative design of user experience. He has several patents pending. Aaron is a graduate of Boston University where he majored in Advertising.
Aaron Rosenberg is the business manager of ~ScanPath Labs at Kent State University. He is also a graduate student in the IAKM Program at Kent State.
The following plugins are used in this ~TiddlyWiki:
*AutoRefreshPlugin - refreshes the custom schedule
*DisplayOpenTiddlersPlugin - used to show the list of currently open tiddlers as links at the top of the page
*ForEachTiddlerPlugin - used to generate the custom schedule
*HideWhenPlugin - used to toggle the star image when marking favorites
*InsertStar - used to insert star graphic, based on [[InsertSmiley|http://www.personal.psu.edu/staff/a/c/ach12/tiddlywiki/extensions.htm#%5B%5BInsertSmiley%20(TW%202.0%20compatible)%5D%5D]]
*IntelliTaggerPlugin - used to edit tags more easily
*TagglyTagCloud - used for the obligatory tag cloud
*TiddlerDisplayTopPlugin - used to open tiddlers always at the top
*ToggleTag2 - used to toggle the favorite tags
The original starting point for this ~TiddlyWiki came from [[TinyTiddly|http://tinytiddly.tiddlywiki.org/]] since I wanted to keep the file size down.
I obtained the original layout from the [[Monkeymind Theme|http://tiddlythemes.com/#Monkymind]], but then I hacked it up.
I'm not exactly sure how much time I've logged on this in the last couple of days, but I'd estimate about 16 hours or so...
This poster is a visual depiction of the Activity Centered Design of ~First-Wave Millennials. Activity Centered Design differs from User Centered Design in that the focus shifts from the user to what the user is actually doing. It is always important to analyze audience needs, but many designers focus too much on user needs and less on the context of user activity. Activity Centered Design gives users only the tools that they need and that they will use.
The poster is based on research conducted on ~First-Wave Millennials or those people who came of age at the beginning of the 21st century. This is the next and maybe greatest generation to have come into existence. The visualizations on this poster were created with the help of IBM’s Many Eyes, http://services.alphaworks.ibm.com/manyeyes/home
Alex Kirtland is a user experience design and usability professional who works with his clients to help them evaluate, envision and develop their web sites and applications. He has over 11 years experience designing usable interfaces for a variety of clients in a variety of industries, including Morgan Stanley, ~InTrade, Peak6, Western Union, CIGNA, Philip Morris USA, Rodale, Avaya, Kodak, XM Satellite Radio, ~Moto-Research, and Ford Motor Company.
Alla Zollers is a ~PhD student in Information Studies at UCLA. Her research interests include social tagging, social network sites, and human-computer interaction.
There is no widely accepted means of evaluating category systems for information search and browsing. The key to evaluation is provision of specific feedback. This presentation outlines an evaluation scheme and an evaluation method that combine the best features of intrinsic and extrinsic, automatic and empirical evaluations. The scheme delineates features broadly classified under comprehensiveness, coherence, and correctness. The study method given requires minimal resources and effort, is easily done remotely, and is easily modified. The method evaluates the category system through an interactive survey distributed among subject domain experts. Inferences are then drawn about the method of generating the system. This study technique is but one possible application of the scheme. The overall approach finds the over- and under-sensitivities of the method of generating the system. A case study has demonstrated the usefulness of the method, and inter-rater reliability in the data suggests that the evaluation scheme is meaningful.
In this poster, we will present findings based on eyetracking users as they accomplish a search task using Google. The basic questions we ask is: Where do users look on a Google results page?
In our analysis, we partitioned the Google results page into three distinct Areas of Interest (AOI). ~AOIs for the Google search page include: top sponsored link, right sponsored link and organic links. The total gaze time per person for each AOI was gathered.
Our findings suggest that people have a tendency to look mainly at the organic search listings. We found that the average subject spent 70% of the gaze time on organic searching, 15% on the right column sponsored links and 15% on the top sponsored link.
Further analysis shows that this trend (70%-15%-15%) is not a group effect but rather remains remarkably consistent across each subject.
Anders Ramsay has over ten years experience designing large-scale web sites working with clients including AOL, CBS, CNN, Deutsche Bank, Fidelity, FOX News, JP Morgan Chase, and Viacom. A Senior Interaction Designer at Funny Garbage, a design agency in New York City, Anders is also highly active in the New York City User Experience community, organizing events and conferences, including the monthly NYC Information Architecture Meetup, the "New Challenges in Information Architecture" IA retreat, and a recent ~BarCamp 'unconference' held at the Microsoft offices in New York City.
Anders is also a contributor to the Boxes & Arrows online magazine and blogs about all things UX at andersramsay.com
Andrew Crow is a senior experience designer, trainer, and speaker at Adaptive Path. He has a passion for developing innovative design solutions for customers' needs.
Continually obsessed with the latest technologies in the mobile and gaming space, Andrew advises on the design of mobile applications, social networking, and collaboration software. He is an advocate of ubiquitous computing, and approaches projects with a desire to ensure that the experience of the device fits into the overall product strategy.
Andrew is a member of AIGA, IxDA and IAI.
Andrew Hinton has designed digital experiences since 1990. Now a Lead Information Architect at Vanguard, he previously worked as a consultant for clients including American Express, Wachovia and ~Kimberly-Clark. Andrew is a co-founder of the Information Architecture Institute and keeps a home on the web at inkblurt.com
Anindita Paul is a doctoral student of Information Science and a senior coordinator at the Information Experience Laboratory at University of Missouri. Her research interest involves examining the various tools and methods to understand the information behavior of users.
Anne is the User Experience Manager at Channel 4 New Media in the UK. She has worked as an Information Architect for over 7 years and has a broad range of experience across many different clients and platforms. In her previous role at ~LBi Anne was responsible for setting up the company’s first graduate recruitment and training programme for Experience Architects. She is currently responsible for setting up and managing the User Experience discipline within New Media at Channel 4 Television.
Tony Turko is currently pursuing a Master’s degree in IA/Usability in the IAKM program at Kent State University while working in the program’s usability lab, Scanpath. He has a Bachelor’s of Science Journalism degree from Ohio University with a specialization in Visual Communication.
Are Halland is a senior Information Architect with ~NetLife Research in Oslo, Norway. Over the last 11 years he has designed search and navigation interfaces and consulted to a number of high profiled clients. Are is a local ambassador for ~UXnet in Norway.
Dr. Hasegawa is the President and Information Architect of Concent, Inc., an independent design agency in Japan. He received Ph.D. in cognitive science from the University of Tokyo and M.Sc. in Elementary Particle Physics from Tohoku University.
He started as an IA in 2000, and founded Concent, Inc. in 2002.
He is a founder of Information Architecture Association Japan(iaaj.org), member of IA Institute and councilor of Japan Human Centered Design Organization.
http://www.iasummit.org/proceedings/2008/audiences_artifacts
As designers, why don’t we concentrate more on designing our documentation? Too often artifacts of our design process are initiated haphazardly, difficult to maintain, unusable by recipients, and organically grown into something we never anticipated. Are our artifacts optimally user-centered? Not as much as they could be.
We’ll explore both the artifacts we produce and the audiences we produce them for, and by mapping those artifacts to audiences, we’ll reveal what works... and what doesn’t. The discussion will focus on the phases through which a deliverable evolves - the deliverable’s life cycle - and we’ll discuss why that life cycle is problematic. We’ll then shift into specific ideas about what we can do to fix it such as deliverable recipes, page patterns, and even modular deliverables tailored to specific audiences.
With an interesting blend of helpful software tips and real-world examples, this talk aims to provoke you to be more prepared, predictable, collaborative, focused, investigative, and focused with your design communications.
As a Senior Information Architect with Comcast Interactive Media, Austin Govella works towards creating better products, better teams, and better experiences.
/***
|''Name:''|AutoRefreshPlugin|
|''Version:''|1.0.1 (2007-01-20)|
|''Type:''|plugin|
|''Source:''|http://tiddlywiki.abego-software.de/#AutoRefreshPlugin|
|''Author:''|Udo Borkowski (ub [at] abego-software [dot] de)|
|''Documentation:''|[[AutoRefreshPlugin Documentation|http://tiddlywiki.abego-software.de/#%5B%5BAutoRefreshPlugin%20Documentation%5D%5D]]|
|''Licence:''|[[BSD open source license (abego Software)|http://www.abego-software.de/legal/apl-v10.html]]|
|''~CoreVersion:''|2.1.3|
|''Browser:''|Firefox 1.5.0.9 or better; Internet Explorer 6.0|
A tiddler containing the {{{<<autoRefresh...>>}}} macro is automatically refreshed (re-painted) whenever a tiddler changes.
!Syntax
{{{
<<autoRefresh [observeTiddler: tiddler ...]>>
}}}
|{{{observeTiddler}}}|(optional) when specified the refresh will only happen when one of the tiddlers specified is changed.|
!Source Code
***/
//{{{
if (!window.abego) window.abego = {};
// autoRefresh Macro =============================================================
//
(function() {
var REFRESHER_NAME = "abego_onEveryChange";
var tiddlersToRefresh = {}; // A set holding the names of tiddlers to be refreshed
var onEveryChangeRefresher = function(e,changeList) {
var tiddlerElem = story.findContainingTiddler(e);
if (!tiddlerElem) return false;
var title = tiddlerElem.getAttribute("tiddler");
if (!title) return false;
// if "observeTiddler" are specified we only refresh if one of the given
// tiddlers has changed.
var observedTiddlers = e.getAttribute("observedTiddlers");
if (observedTiddlers) {
var a = observedTiddlers.readBracketedList();
if (!changeList || !a.containsAny(changeList))
return;
}
// Refresh the tiddler asynchronously.
// This way we can avoid repeated refreshes (e.g. when a tiddler is renamed)
tiddlersToRefresh[title] = true;
setTimeout(function() {
// Refresh all tiddlers in tiddlersToRefresh
for(var title in tiddlersToRefresh)
story.refreshTiddler(title,null,true);
// We have refreshed all pending tiddlers. Clear the set.
tiddlersToRefresh = {};
}, 0);
return true;
}
config.refreshers[REFRESHER_NAME] = onEveryChangeRefresher;
config.macros.autoRefresh = {};
config.macros.autoRefresh.handler = function(place,macroName,params,wikifier,paramString,tiddler) {
params = paramString.parseParams("observeTiddler",null,true,false,true); // allowEval, cascadeDefaults, names allowed
var e = createTiddlyElement(place,"span");
e.setAttribute("refresh",REFRESHER_NAME);
var observedTiddlers = params[0]["observeTiddler"];
if (observedTiddlers && observedTiddlers.length) {
var s = "[["+observedTiddlers.join("]] [[")+"]]";
e.setAttribute("observedTiddlers",s);
}
};
})();
//}}}
http://www.iasummit.org/proceedings/2008/becoming_an_iaux_coach_proving
Information Architects often feel that their practice needs to go further, in order to deliver greater value and impact. However, we are stumped and frustrated when we see that things are slow to change or do not change at all -- within our organizations or that of our clients’. We are surprised when asked to cost-justify our approach, with business partners whom we have worked with for many years. We feel discouraged when colleagues with high business fluency fail as change agents within their organizations.
To address this need, we will explore coaching as a mindset and practice, drawing from the field of professional coaching. This session will help the advanced IA/UX professional to think like a coach, be a coach, and to select IA/UX tools to use as a coach. I will talk about the personal characteristics of the UX Champion that the Coach will need to look for. We will also explore the right time and place to introduce this practice.
To illustrate the idea of blending coaching with IA, I have developed a model that combines the five levels of UX Coaching with Jesse James Garrett’s Elements of User Experience. I will also talk about the heart of coaching and some of the softer skills required for this approach. Lastly, I will present a short case study.
http://www.iasummit.org/proceedings/2008/blind_ambition_how_the_accessi
How accessible is a sighted person’s experience of using a web site? Would you rather design user experiences than pages and sitemaps? You’ll have a better grasp of user experience when you can translate it into something even a blind person would recognize.
We’ll begin by discussing cases where web sites focused on user experience may be more useful to the public than sites serving as information indices. We’ll examine why visual-tactile experience should sometimes be unpredictable. We’ll then pause to consider what sensory experience has to do with site structure, the traditional concern of IA.
We’ll then discuss shortcomings of traditional notions of accessibility, the user experience of controlling screen reader software and listening to automated speech, and potential rewards of providing more disability-friendly alternatives. We’ll consider currently available alternative technologies and look at controversies surrounding what constitutes an equivalent sensory experience in different sensory modalities. The debate will be illustrated with examples drawn from the audio description of video programs.
Finally, we’ll consider the challenge of designing auditory equivalents for unpredictable experience-oriented web sites. Whether determining what’s clickable or what a button means, gleaning site structure or identifying navigation options, we’ll devise auditory equivalents for interactive eye-hand behavior and concomitant inferencing likely to elicit the same emotional response to the site’s message as that which sighted users experience.
Brandon Schauer is an experience design director for Adaptive Path, where he guides the practice of design strategy. Brandon teaches and practices design as a means to create value for both people and business. He applies his mixed-up designer/MBA brain to create valued new experiences for clients like Flickr and Ameriprise Financial. Brandon’s the co-author of Adaptive Path’s book, Subject To Change, and he has a love of Excel that is unnatural for a designer.
Brian currently works at The Washington Post as an interaction designer. He has worked with numerous government agencies, non-profit organizations, and private companies. He holds a Master of Arts in Professional Communication from Clemson University and a Bachelor of Arts in English from Virginia Tech.
[img[http://students.washington.edu/adcockm/IASummit/Hyatt_2.png]]
<<tagging>>
Bryce Glass is a Senior Interaction Designer at Yahoo! He works on Community Platforms and is professionally interested in: social media and user participation in online communities; models for representing user reputation; and concept modeling as part of the product development process.
Bryce has an MS in Information Design & Technology from Georgia Tech and has worked as an in-house UI designer at Netscape, America Online, Sun Microsystems and Yahoo!
He telecommutes from his home in Columbus, Ohio where he and his wife are embracing the challenges of being new parents. Bryce keeps a blog at soldierant.net
http://www.iasummit.org/proceedings/2008/building_customer_trust_throug
Hotwire is routinely faced with a unique user experience challenge: the business model requires that customers compromise some upfront knowledge of the product in exchange for significantly lower prices. Considering the “buyer beware” attitude that a typical consumer brings to a site, how is it possible to gain user trust even when some upfront information is compromised?
Inspired by “The Paradox of Choice,” we addressed the issue of user distrust with a new approach during the recent redesign of the Air Search path: we mimicked an interaction with a travel agent. A travel agent would never offer an overwhelming number of options, so, unlike many travel sites, we extended this model by exploring interruptions and information restriction -- creating an unconventional approach for providing flight search results to the user.
Regardless of industry, users spend an increasing amount of time searching an overwhelming number of options to find the best product. In this session, we will discuss how to successfully guide your users through these large amounts of data. The following will be addressed: our issues of trust, information guiding the Hotwire approach, Hotwire’s flight search redesign strategy and solution, the outcome with regards to user feedback, conversion improvement and changes in trust, and tips for how to apply this model to your site.
Using Dan Brown's book "Communicating Design" as reference, I will show some of the real-world design deliverables coming out of a website project in 2006/2007 for a Top 5 Dutch bank. A combined team of SNS Bank and Info.nl employees went through the scoping, analysis, concept design, prototyping, detailed design, evaluation, and implementation phases. The team did not set out to follow Dan's book (some deliverables were created before the book was published) but in hindsight produced all of its main deliverables.
I have selected the most interesting deliverables for inclusion on the poster (but will bring copies of others) and will highlight how these deliverables relate to each other in this project, how they were presented to the client and used by the design team. The poster will show that real world design can sometimes really be done by the book.
http://www.iasummit.org/proceedings/2008/checking_the_feel_of_your_ui_w
What is your site’s “feel?” Is it smooth and consistent, or jagged and unpredictable? Do links always navigate, or do they sometimes pop up overlays, change state, or pull down a menu? How many ways can users make an exclusive choice or disclose hidden content? The modern Web supports a dizzying variety of possibilities, but that doesn’t mean you should offer all of them.
In this presentation we’ll show how to evaluate the consistency of your site’s “feel.” Using a recent audit of the interaction design of a major Web site as an example—an audit of the site’s “feel”—we’ll discuss how to collect and catalog the variety of interactions users encounter. The methodology includes taking inventory of visual cue meanings/behaviors, task flows, and data representations. These findings are used to evaluate the “feel” of portions of the user experience, pointing up jagged discontinuities and unpredictable behaviors as well as smooth transitions and consistent affordances, paths and representations.
This audit can determine if a site’s interactions are consistent, and if the site’s “feel” aligns with organizational values. We’ll round up our case study’s key findings, and discuss future extensions of the audit, including development of design patterns and values, and objective and subjective metrics for measuring the “feel” of a user experience.
Chris Chandler has been advocating on behalf of the true "silent majority" (i.e., people who use software) since 1994, when he realized no one else on his team would do so. Chris is currently Director of Creative Services for Walt Disney Parks and Resorts Online, an internal agency where all projects must be useful, usable AND magical. While at WDPRO Chris has led projects to redesign the online booking process for Disneyland.com and Disneyworld.com, as well as the creation of several new websites such as Hongkongdisneyland.com. He has taught a hands-on class in Information Architecture with Lynn Boyden in the UCLA Department of Information Studies.
Prior to becomming a cast member at Disney, Chris worked as an Information Architect, Information Designer, Project Manager and Site Developer for several Los Angeles firms such as Genex, ~NextLeft, Escott Associates and Kore Digital. Chris has worked with national consumer product brands such as ~HealthyChoice.com, ~MightyDog.com, financial services portals such as Citibank's Bizzed.com as well as numerous other clients in the entertainment and online services industries. Chris is a graduate of the University of California, Los Angeles, holding a BA in Anthropology and an MA in Urban Planning.
Chris Conley is a founding partner of Gravity Tank and is a professor of design at the Institute of Design (ID) in Chicago. He has over fifteen years of experience teaching design and helping some of the world's most influential companies change the way they define and develop new offerings. Core to that change is a multidisciplinary and collaborative approach that makes extensive use of prototyping. At the Institute of Design, he educates a new kind of design professional - one that can work throughout the modern organization leading initiatives aimed at innovation and delivering results to the bottom line. At Gravity Tank, Chris has helped companies like Office Max, Unilever, Goodyear, and Samsung work differently to define and launch successful new products and services. Recently he became the first design advisor to the CEO of Samsung Telecommunications on how to broaden the impact of design expertise throughout their organization.
Chris holds a Master of Science of Design from ID and a mechanical engineering degree from the Illinois Institute of Technology. Chris is a regular contributor to design conferences and competitions worldwide and was the 2006 Chair of the IDEA ~BusinessWeek Awards. He lives in Chicago with his wife Cira, who is a partner in Gravity Tank, and two children who only work there on a part time basis.
Christian Crumlish has been designing and writing about shared information spaces since 1994. He is the curator of the Yahoo! pattern library and is director of technology for the Information Architecture Institute. He studied philosophy at Princeton and painting at the San Francisco School of Art He is the author of, most recently, The Power of Many: How the Living Web is Transforming Politics, Business, and Everday Life (Wiley, 2004), and he is working a book about online presence and identity, tentatively titled Presence of Mind. He lives in Oakland, California, with his wife, Briggs, and his cat, Fraidy.
Christina Wodtke is founder and publisher of Boxes and Arrows. A relentless instigator, she also cofounded Cucina Media, the creator of the software Boxes and Arrows runs on. Previously, she cofounded MIG, a management consulting firm, cofounded the Information Architecture Institute; authored the bestselling book Information Architecture: Blueprints for the Web; and has spoken on the topic of the human experience in information spaces at conferences worldwide.
Christopher ~McConnell is a doctoral student in ~Radio-TV-Film at the University of Texas at Austin and production manager at educational media firm, Ignite Learning. His research interests lie at the intersection of computers and culture, and how smart design can improve users’ experiences on- and off-line.
Claude’s work on message effects of sound patterns includes songwriting, a presentation on vocal characteristics of villainous cartoon characters at Pixar Animation Studios, and publications on vocal characteristics of trustworthy American male heroes and convincing voiceover appeals.
As a ~UserWorks usability specialist, Claude has evaluated ecommerce sites and social marketing campaigns. Voice interface projects include web portal to phone conversion, comparison of voice and text messaging, and testing of audio equivalents of print publications.
http://www.iasummit.org/proceedings/2008/closing_plenary_linkosophy
At times, especially in comparison to the industrial and academic disciplines of previous generations, the User Experience family of practices can feel terribly disorganized: so little clarity on roles and responsibilities, so much dithering over semantics and orthodoxy. And in the midst of all this, IA has struggled to explain itself as a practice and a domain of expertise.
But guess what? It turns out all of this is perfectly natural.
To explain why, we'll use IA as an example to learn about how communities of practice work and why they come to be. Then we'll dig deeper into describing the "domain" of Information Architecture, and explore the exciting implications for the future of this practice and its role within the bigger picture of User Experience Design.
http://www.iasummit.org/proceedings/2008/code_blue_how_service_design_c
Historically, technology design challenges have been centralized around the two-dimensional presentation of information and tasks. But a new discipline has emerged: Service Design, or the creation of a complete experience that satisfies the user at every touch-point throughout the service cycle. The rise of this new discipline presents complex problems that user experience practitioners must solve by appropriately leveraging products, people and technology.
~UXs on the leading edge of Service Design are using ethnographic research, data visualization and information architecture to help resolve service issues in the most critical of environments – hospitals.
In hospitals, new patient services are helping to improve the quality of care. The creation of Rapid Response Teams, an elite nursing-led intensive care unit, has helped avoid possible ‘code blue’ situations by searching for early warning signs of patient decline. These new services combine patients, nurses, physicians, technology, and physical space to create a unique experience design challenge.
In this presentation, we will explore techniques for leveraging the varied skill sets of those in the UX design field to provide service design in a complex environment. Experts must balance the social dynamics between different personas; capture and sift vast amounts of data in attempt to distill pertinent information; and visualize their findings with precision to ensure that the experience is improved.
Attendees will walk away with valuable specifics on how to conduct a service design project in any environment – from inception to implementation – utilizing the collaborative skills of researchers, information architects and UX practitioners.
In this presentation, we will:
* Define Service Design as an emerging practice
* Explore the ~IAs role in multi-disciplinary service design teams
* Examine a hospital case study to understand the interrelation of the web, information systems, and physical space
* Provide practical take-aways for experience designers
Background: #fff
Foreground: #000
PrimaryPale: #e990bc
PrimaryLight: #d4508a
PrimaryMid: #9b0046
PrimaryDark: #69002f
SecondaryPale: #dcf4b6
SecondaryLight: #b7cc8e
SecondaryMid: #98b55b
SecondaryDark: #5c7133
TertiaryPale: #eee
TertiaryLight: #ccc
TertiaryMid: #999
TertiaryDark: #666
Error: #f88
Concept models are simple diagrams that pack a lot of punch. Information architects have adopted this technique as a means for:
* understanding the information space in which they're working
* illustrating structures that might serve as the foundation for a web site
Founded on the simple premise that any domain can be represented as nouns connected by verbs, concept models are easy to understand. What may be more difficult is creating them, and then using them in the design process. Information architects may not be aware of how to apply these models effectively as a design technique.
This poster will provide examples of concept models and describe:
* Purpose, elements, and format: What concept models do and what they look like.
* Benefits and advantages: How concept models compare to other techniques.
* Creation: Simple steps and tips for creating concept models.
* Use: Tips and techniques for employing concept models in the design process.
http://www.iasummit.org/proceedings/2008/content_page_design_best_pract
In today’s social, distributed, search-driven Web, customers are finding their way to Web content through an increasing number of distinct experiences. Yet when people arrive at most Web pages, the experience they get isn’t optimised for this context. Instead, the vast majority of content pages online remain more concerned with their own context than the context of their users: where did a user arrive from and where are they likely to go next? These pages remain designed as if they were primarily accessed from a Web site’s home page or a carefully thought-out selection from the site’s information architecture.
To address these issues and more, this talk outlines a set of best practices for Web content page design that focuses on appropriate presentations of content, context, and calls to action. Specifically: how can content be optimised to meet user expectations as they arrive from a diverse number of access points; what is the minimum amount of context required to frame content appropriately; how can the most relevant calls to action be presented to maximize user engagement? Applying these considerations enables information architects to deliver content experiences that take full advantage of emerging opportunities online and the existing assets within their Web sites.
http://www.iasummit.org/proceedings/2008/core_and_paths_putting_a_creat
The Core and Paths framework provides a simple, yet effective approach that enhances findability, simplicity and persuasion for websites and applications.
By starting the design process with the findable object itself (the core), and then designing inward and outward paths to and from the core, a number of benefits can be reaped.
This presentation will briefly recap the framework (which was introduced at last years ~IAsummit in Las Vegas) then look at how the approach has been applied to a number of real world projects.
The various uses and benefits includes using the framework as:
* a powerful thought-tool to rethink IA, navigation and findability in new and creative ways
* a fun and inspiring way to kick-off design and redesign projects
* a design and prioritization tool inspired by and building on 37signals Epicenter design
* a client communication tool to fight frontpage focus and other classic project problems
* a metrics vizualisation tool to identify and communicate key metrics and ~KPIs
Cases will include sonyericsson.com and more.
Target audience
The presentation will be suitable for any information architect looking for new approaches to the evolving problems of designing application-like sites and the difficulties of conceiving, documenting and measuring them.
http://www.iasummit.org/proceedings/2008/creating_career_paths_for_ux_p
What makes a Senior IA? Is going down the management path the only way to get ahead? Do you need a team of generalists or specialists? How do you know when to promote someone? Are you hiring the person or the job description? These are questions all managers face, but some answers are better than others.
Defining career paths within a UX group is an easy thing to do, yet many managers never get around to doing it. This session presents a framework around which you can clearly define roles, set goals, and provide clear opportunities for career advancement for your team.
I’ve found that using this career pathing framework has increased job satisfaction for my direct reports, created a way to facilitate conversations about career advancement and performance, improved our recruiting process and helped me to be a better manager.
This session will cover:
* Defining structure: exploring agency vs. in-house group models
* Defining parallel tracks: people management vs. technical leadership paths
* Creating job descriptions, titles, job families and salary grades
* Recruiting and selecting great team members – the difference between job descriptions and job ads, using career pathing as a recruiting tool
* Using career pathing documents: creating development plans, setting goals, and using them to deal with difficult conversations about performance, expectations and compensation.
/***
|''Name:''|CryptoFunctionsPlugin|
|''Description:''|Support for cryptographic functions|
***/
//{{{
if(!version.extensions.CryptoFunctionsPlugin) {
version.extensions.CryptoFunctionsPlugin = {installed:true};
//--
//-- Crypto functions and associated conversion routines
//--
// Crypto "namespace"
function Crypto() {}
// Convert a string to an array of big-endian 32-bit words
Crypto.strToBe32s = function(str)
{
var be = Array();
var len = Math.floor(str.length/4);
var i, j;
for(i=0, j=0; i<len; i++, j+=4) {
be[i] = ((str.charCodeAt(j)&0xff) << 24)|((str.charCodeAt(j+1)&0xff) << 16)|((str.charCodeAt(j+2)&0xff) << 8)|(str.charCodeAt(j+3)&0xff);
}
while (j<str.length) {
be[j>>2] |= (str.charCodeAt(j)&0xff)<<(24-(j*8)%32);
j++;
}
return be;
};
// Convert an array of big-endian 32-bit words to a string
Crypto.be32sToStr = function(be)
{
var str = "";
for(var i=0;i<be.length*32;i+=8)
str += String.fromCharCode((be[i>>5]>>>(24-i%32)) & 0xff);
return str;
};
// Convert an array of big-endian 32-bit words to a hex string
Crypto.be32sToHex = function(be)
{
var hex = "0123456789ABCDEF";
var str = "";
for(var i=0;i<be.length*4;i++)
str += hex.charAt((be[i>>2]>>((3-i%4)*8+4))&0xF) + hex.charAt((be[i>>2]>>((3-i%4)*8))&0xF);
return str;
};
// Return, in hex, the SHA-1 hash of a string
Crypto.hexSha1Str = function(str)
{
return Crypto.be32sToHex(Crypto.sha1Str(str));
};
// Return the SHA-1 hash of a string
Crypto.sha1Str = function(str)
{
return Crypto.sha1(Crypto.strToBe32s(str),str.length);
};
// Calculate the SHA-1 hash of an array of blen bytes of big-endian 32-bit words
Crypto.sha1 = function(x,blen)
{
// Add 32-bit integers, wrapping at 32 bits
add32 = function(a,b)
{
var lsw = (a&0xFFFF)+(b&0xFFFF);
var msw = (a>>16)+(b>>16)+(lsw>>16);
return (msw<<16)|(lsw&0xFFFF);
};
// Add five 32-bit integers, wrapping at 32 bits
add32x5 = function(a,b,c,d,e)
{
var lsw = (a&0xFFFF)+(b&0xFFFF)+(c&0xFFFF)+(d&0xFFFF)+(e&0xFFFF);
var msw = (a>>16)+(b>>16)+(c>>16)+(d>>16)+(e>>16)+(lsw>>16);
return (msw<<16)|(lsw&0xFFFF);
};
// Bitwise rotate left a 32-bit integer by 1 bit
rol32 = function(n)
{
return (n>>>31)|(n<<1);
};
var len = blen*8;
// Append padding so length in bits is 448 mod 512
x[len>>5] |= 0x80 << (24-len%32);
// Append length
x[((len+64>>9)<<4)+15] = len;
var w = Array(80);
var k1 = 0x5A827999;
var k2 = 0x6ED9EBA1;
var k3 = 0x8F1BBCDC;
var k4 = 0xCA62C1D6;
var h0 = 0x67452301;
var h1 = 0xEFCDAB89;
var h2 = 0x98BADCFE;
var h3 = 0x10325476;
var h4 = 0xC3D2E1F0;
for(var i=0;i<x.length;i+=16) {
var j,t;
var a = h0;
var b = h1;
var c = h2;
var d = h3;
var e = h4;
for(j = 0;j<16;j++) {
w[j] = x[i+j];
t = add32x5(e,(a>>>27)|(a<<5),d^(b&(c^d)),w[j],k1);
e=d; d=c; c=(b>>>2)|(b<<30); b=a; a = t;
}
for(j=16;j<20;j++) {
w[j] = rol32(w[j-3]^w[j-8]^w[j-14]^w[j-16]);
t = add32x5(e,(a>>>27)|(a<<5),d^(b&(c^d)),w[j],k1);
e=d; d=c; c=(b>>>2)|(b<<30); b=a; a = t;
}
for(j=20;j<40;j++) {
w[j] = rol32(w[j-3]^w[j-8]^w[j-14]^w[j-16]);
t = add32x5(e,(a>>>27)|(a<<5),b^c^d,w[j],k2);
e=d; d=c; c=(b>>>2)|(b<<30); b=a; a = t;
}
for(j=40;j<60;j++) {
w[j] = rol32(w[j-3]^w[j-8]^w[j-14]^w[j-16]);
t = add32x5(e,(a>>>27)|(a<<5),(b&c)|(d&(b|c)),w[j],k3);
e=d; d=c; c=(b>>>2)|(b<<30); b=a; a = t;
}
for(j=60;j<80;j++) {
w[j] = rol32(w[j-3]^w[j-8]^w[j-14]^w[j-16]);
t = add32x5(e,(a>>>27)|(a<<5),b^c^d,w[j],k4);
e=d; d=c; c=(b>>>2)|(b<<30); b=a; a = t;
}
h0 = add32(h0,a);
h1 = add32(h1,b);
h2 = add32(h2,c);
h3 = add32(h3,d);
h4 = add32(h4,e);
}
return Array(h0,h1,h2,h3,h4);
};
}
//}}}
Dan Brown co-founded ~EightShapes, LLC, a user experience consulting firm based in Washington, DC. He wrote Communicating Design (New Riders 2007), a book dedicated to creating design documentation. His current clients include Comcast, Hanley Wood, Marriott, and National Geographic.
Dan Willis has been launching robust Web sites for more than a decade. Currently a consultant for Sapient, Willis was washingtonpost.com’s first User Experience Director and had the same title at PBS.org. He has designed and coded major Web sites, run usability testing, and managed designers, information architecture and Web analytics. He is the creator of UX Crank (www.uxcrank.com), a highly opinionated resource for UX professionals. He has also presented at previous IA Summits.
http://www.iasummit.org/proceedings/2008/data_driven_design_research_pe
Whether you call them personas, characters, or actors, creating an accurate representative profile of your customers is one of the most useful tools in our user experience war chest. Personas are one of the most common buzz words in our industry, and yet the formula for crafting them seems to be locked away in some safe alongside the recipe for ~Coca-Cola. Well, that’s about to change. During this presentation we'll focus on methods for collecting and using data to create personas. And more importantly, I'll share some new visualization techniques we've been using that have made our personas even more effective and valuable to the design process.
Additionally, we'll address how and when to actually use personas once you’ve created them, ways to keep them alive throughout the design and development process (as well as after launch), and ways to measure the effectiveness on the product once it has launched.
Dave is a User Experience Lead at GSI interactive, a division of GSI Commerce, a turnkey e-commerce provider located in King of Prussia, PA. He is a strategy lead for user experience guiding user research, usability testing, and taxonomy. Dave's work is informed by masters degrees in information systems (Drexel University) and social science (University of Illinois).
Dave lives in Philadelphia with his husband, Gordon, and their three children: Netflix, ~TiVo, and Ketel One.
David Karemaker has been working as an interaction designer, project manager and information architect since 1998. He currently works at User Intelligence, a user experience design and evaluation collective based in Amsterdam. David holds a BA and MSC in Information Science from the University of Amsterdam (2006) and a BA in Video Design from the Royal Academy of Art in The Hague (1997). Current research interests: Action Research methodologies, Personality, Quantitative validation of personas.
David B. Robins is an Assistant Professor in the Interdisciplinary Program in Information Architecture and Knowledge Management at Kent State University. He is conducting research on aesthetics and credibility in websites.
[[iA SUMMIT 2008 TiddlyWiki]]
Recent analysis and discussions with a range of clients has led me to begin creating a new aspect of these documentation systems: page patterns. Through analysis of 100s of sample deliverables, I’ve realized two things: (1) there’s no one-size-fits-all page from which you start to document every design, and (2) there is a clear set of prioritized patterns to those pages that emerge.
What is a page pattern? It’s a framework of textual and object-based structures that - when applied - enable the designer to easily place artwork (e.g., wireframes) and annotate (e.g., content specs). With such starting points predefined, one can create consistent, effective documentation far more quickly.
This poster will define the term “page pattern”, place it in context of broader systematic approaches for creating documentation, and display the 50+ page patterns already available in a easily browsed gallery format.
The workshop will be presented by Dennis Schleicher, Director of Usability & Senior Information Architect at e.magination. Dennis has taught classes and workshops to over 1600 participants over the last 18 years teaching many similar concepts. He has organized and conducted slams for non-profit clients, for-profit clients, for fun, and for internal corporate development. He worked in marketing on the JWT Ford account, CTC in the education and collaboration arena, and Argus Associates. www.dennisschleicher.com
/***
|''Name:''|DeprecatedFunctionsPlugin|
|''Description:''|Support for deprecated functions removed from core|
***/
//{{{
if(!version.extensions.DeprecatedFunctionsPlugin) {
version.extensions.DeprecatedFunctionsPlugin = {installed:true};
//--
//-- Deprecated code
//--
// @Deprecated: Use createElementAndWikify and this.termRegExp instead
config.formatterHelpers.charFormatHelper = function(w)
{
w.subWikify(createTiddlyElement(w.output,this.element),this.terminator);
};
// @Deprecated: Use enclosedTextHelper and this.lookaheadRegExp instead
config.formatterHelpers.monospacedByLineHelper = function(w)
{
var lookaheadRegExp = new RegExp(this.lookahead,"mg");
lookaheadRegExp.lastIndex = w.matchStart;
var lookaheadMatch = lookaheadRegExp.exec(w.source);
if(lookaheadMatch && lookaheadMatch.index == w.matchStart) {
var text = lookaheadMatch[1];
if(config.browser.isIE)
text = text.replace(/\n/g,"\r");
createTiddlyElement(w.output,"pre",null,null,text);
w.nextMatch = lookaheadRegExp.lastIndex;
}
};
// @Deprecated: Use <br> or <br /> instead of <<br>>
config.macros.br = {};
config.macros.br.handler = function(place)
{
createTiddlyElement(place,"br");
};
// Find an entry in an array. Returns the array index or null
// @Deprecated: Use indexOf instead
Array.prototype.find = function(item)
{
var i = this.indexOf(item);
return i == -1 ? null : i;
};
// Load a tiddler from an HTML DIV. The caller should make sure to later call Tiddler.changed()
// @Deprecated: Use store.getLoader().internalizeTiddler instead
Tiddler.prototype.loadFromDiv = function(divRef,title)
{
return store.getLoader().internalizeTiddler(store,this,title,divRef);
};
// Format the text for storage in an HTML DIV
// @Deprecated Use store.getSaver().externalizeTiddler instead.
Tiddler.prototype.saveToDiv = function()
{
return store.getSaver().externalizeTiddler(store,this);
};
// @Deprecated: Use store.allTiddlersAsHtml() instead
function allTiddlersAsHtml()
{
return store.allTiddlersAsHtml();
}
// @Deprecated: Use refreshPageTemplate instead
function applyPageTemplate(title)
{
refreshPageTemplate(title);
}
// @Deprecated: Use story.displayTiddlers instead
function displayTiddlers(srcElement,titles,template,unused1,unused2,animate,unused3)
{
story.displayTiddlers(srcElement,titles,template,animate);
}
// @Deprecated: Use story.displayTiddler instead
function displayTiddler(srcElement,title,template,unused1,unused2,animate,unused3)
{
story.displayTiddler(srcElement,title,template,animate);
}
// @Deprecated: Use functions on right hand side directly instead
var createTiddlerPopup = Popup.create;
var scrollToTiddlerPopup = Popup.show;
var hideTiddlerPopup = Popup.remove;
// @Deprecated: Use right hand side directly instead
var regexpBackSlashEn = new RegExp("\\\\n","mg");
var regexpBackSlash = new RegExp("\\\\","mg");
var regexpBackSlashEss = new RegExp("\\\\s","mg");
var regexpNewLine = new RegExp("\n","mg");
var regexpCarriageReturn = new RegExp("\r","mg");
}
//}}}
http://www.iasummit.org/proceedings/2008/antisocial_networks_beyond_amb
This presentation considers the role of traditional social networks and the role of ~IAs in addressing the challenges that arise when designing and using online social networks.
The presentation discusses philosophical approaches to sharing the self, how this relates to offline social networks and human interactions in different contexts, and provides guidance on how online social networking tools can be designed to support these relationships.
It also covers ethical issues, including privacy, and how these can conflict with business needs. A range of examples illustrate the impact of these drivers and how design decisions can lead to the creation of anti-social networks.
Finally, it considers the design role which ~IAs play, and how recognising the impact of business needs, philosophy and ethics can help deliver better social networks. It also considers how the IA community generally could influence and improve social network design.
The presentation is aimed at ~IAs who are designing, building or using social networks, who also recognise that their design choices, philosophy and ethical background have a fundamental impact on user experience.
Participants will learn about different approaches to social network design, and how online social networks relate to traditional ways of viewing human interactions. They will also gain some practical advice on the different issues which should be considered when designing and using social networks.
http://www.iasummit.org/proceedings/2008/designing_with_patterns_in_the
Can you streamline web design and development with design patterns? Really? How?
Do patterns help or hinder agile user-centered design?
Do design patterns stifle innovation?
We’ll share what we’ve learned about bootstrapping pattern libraries from scratch and how to “extract” patterns from existing products.
We’ll share stories (er, I mean real-world case studies) to illustrate ways pattern libraries can both aid and stifle innovation, how they help solve real-world web design problems, and how they support rapid production of common IA deliverables.
We’ll bask in the glow of the “magic triangle” of patterns + code modules + wireframe templates that enable rapid prototyping and agile development, and then cower in the miserly shadow of the “iron triangle” of fast, cheap, or good.
How to structure and maintain a pattern library? Check. We’ve got you covered. How do you trick… er… get people to adopt patterns and help improve them? What tools help you do this? Are wikis the answer? How far can you get with an open-source CMS, a boatload of other people’s mistakes, spit, baling wire, and wing and a prayer?
To find out, come to Austin and Christian’s presentation where we’ll share what we’ve learned, what works, and what we will never ever do again at Comcast and Yahoo!
http://www.iasummit.org/proceedings/2008/designing_your_reputation_syst
Leaderboards, Levels, Points, "Top 10 Reviewer", Elite Status, Gold Member, Badges and Trophies—the options for representing a person's reputation within a community are almost as varied as the reasons you might want to do so.
Reputation can incent users to higher-and-higher levels of contribution, motivate them to stick around longer and form a deeper relationship with your product, but tread lightly: research and common usage have shown that specific reputation patterns lend themselves to some fairly specific contexts and—when used inappropriately—can harm your community dynamic. Ugly side-effects like increased competitiveness, lowered quality of contributions and petty squabbles may result. This talk presents 15 questions to take into account when designing your reputation system, including:
* What type of community spirit are you trying to promote?
* How exclusive should earned reputations be in your community?
* How transparent should you be with the inner workings of the system?
* Should reputations decay from non-use?
* Are there cultural aspects that you should consider?
* And more…
Finally, specific patterns are recommended to achieve specific goals. Each pattern has been tested by Yahoo! and all patterns are discussed within a framework of actual user acceptance: either in a live product environment or responses from comparative lab studies.
Key objectives of the poster:
* Discuss how cognitive load relates to information architecture.
* Describe the effects of cognitive overload on user comprehension and performance.
* Understand how to measure cognitive load during a usability test by imposing a secondary load via tapping.
Observations of usability tests often reveal the participants dropping tasks, failing to follow through with actions, disregarding information, or not seeing information. All of these problems are symptoms of cognitive overload. If the information architect can identify the problematical areas, they can be fixed early in the design stage. Cognitive load refers to the total amount of mental activity that a person has to maintain in memory at any one time. Once the resources are exhausted, the user suffers from cognitive overload which increases errors and lowers comprehension and performance. Identifying these places within a design should improve the overall usability.
Dick Horst is an experimental psychologist and user experience specialist with over 30 years’ experience in applied behavioral research, systems development, and usability engineering. He is the founder and President of ~UserWorks, Inc., a usability engineering consulting firm in the Washington, DC area. Dick has conducted or overseen over a hundred usability testing projects for organizations in government, the private sector, non-profits, and academia. Over the last five years, a number of these studies have involved remote testing methods. Dick has a Ph.D. in experimental psychology from ~Carnegie-Mellon University and is a board certified professional ergonomist.
/***
|Name|DisplayOpenTiddlersPlugin|
|Location|http://www.orst.edu/~woodswa/tiddlywikiplugs.html|
|Version|1.0|
|Author|Walt Woods|
|Requirements||
!Description
Displays similar to the popular BreadCrumbsPlugin by AlanHecht, this plugin instead keeps a list of currently open tiddlers.
!History
08-06-2007: Initial version.
!Code
***/
//{{{
version.extensions.DisplayOpenTiddlers = {major: 1, minor: 0, revision: 0};
function addOpenTiddlerLine(title, element)
{
if (title != openTiddlerClosing)
{
if (tiddlerLine != "")
tiddlerLine += " | ";
tiddlerLine += "[[" + title + "]]";
}
}
function refreshOpenTiddlersList()
{
if (!document.getElementById("openTiddlers")) {
var ta = document.createElement("div");
ta.id = "openTiddlers";
ta.style.visibility= "hidden";
var targetArea = document.getElementById("tiddlerDisplay")||document.getElementById("storyDisplay");
targetArea.parentNode.insertBefore(ta,targetArea);
}
var tiddlers = document.getElementById("openTiddlers");
tiddlers.style.visibility = "visible";
removeChildren(tiddlers);
tiddlerLine = "";
story.forEachTiddler(addOpenTiddlerLine);
wikify(tiddlerLine,tiddlers)
}
Story.prototype.displayTiddlerDisplayOpenTiddlers = Story.prototype.displayTiddler;
Story.prototype.displayTiddler = function(srcElement,title,template,animate,slowly)
{
this.displayTiddlerDisplayOpenTiddlers(srcElement,title,template,animate,slowly);
openTiddlerClosing = "";
refreshOpenTiddlersList();
}
Story.prototype.closeTiddlerDisplayOpenTiddlers = Story.prototype.closeTiddler;
Story.prototype.closeTiddler = function(title,animate,unused)
{
this.closeTiddlerDisplayOpenTiddlers(title,animate,unused);
openTiddlerClosing = title;
refreshOpenTiddlersList();
}
//}}}
http://www.iasummit.org/proceedings/2008/do_real_people_really_use_tag
Much has been said about how the Web 2.0 era has fundamentally altered the way consumers interact online. But to what degree is today’s digital consumer really changing her online behavior? Are the hallmarks of Web 2.0 site design (tag clouds, wikis, social media, etc.) on the way to becoming mainstream hits or just techno-hype? And what are the implications for us, as experience designers, as we strive to create more useful and usable digital products?
These are some of the fundamental questions our design research team set out to answer when we surveyed 475 U.S. consumers about their digital behavior in 2007. In our study we found that today's mainstream consumers are enthusiastically adopting some Web 2.0 behaviors: they are increasingly personalizing their digital experiences with simple tools; snacking on highly specialized content through blogs and interactive video; and using search engines for almost every conceivable task. On the flip side, a surprising number of today's consumers are skipping some of the most innovative and buzz-worthy totems of Web 2.0.
"Do People Really Use Tag Clouds" will help experience designers navigate this evolving Web 2.0 landscape with quantitative data, explore trends shaping the industry and pinpoint concepts for further exploration in the months ahead.
Where information architecture makes the inherent structures of information salient, content strategy serves to highlight the actual information. As such, the line between these two disciplines is blurry at best. ~IAs and content strategists now struggle with a tough question: where does your work end and mine begin? These issues are exemplified in the difficulties surrounding documentation. Web teams often struggle with the separation of content and design, and find it difficult to accommodate the editorial process in design artifacts, and vice versa.
This poster will unpack this problem, presenting a framework that might help design teams talk about the issues and brainstorm solutions. The framework shows how content impacts other areas of the design process and how those relationships lead to different ways of thinking about content. This framework will then be extended to documentation to show how it predicts problems in the current suite of user experience deliverables, and how those problems might be addressed.
Dorelle Rabinowitz leads a user experience design team at Google, creating standards, patterns & resources. Previously, she managed a UX team at Yahoo!, was an experience lead at SBI.Razorfish and produced Oxygen.com’s "Our Stories" site. She is on the advisory board of the IAI, and is a former editor of Boxes and Arrows. A graduate of NYU's Interactive Telecommunications Program, Dorelle also holds a BFA in graphic design from the Rhode Island School of Design.
Dustin Chambers is a user experience designer at ~UserWorks Inc. His responsibilities include user research, user-centered design and information architecture. He has conducted both remote and in-person usability testing studies for a variety of government and private sector clients. Dustin’s background is in human factors, psychology and graphic design. He has a Masters degree in human factors and ergonomics from Loughborough University in the U.K. A special area of interest is user-centered design in the developing world.
http://www.iasummit.org/proceedings/2008/eservice_what_we_can_learn_fro
As ~IAs, we often preach the value of our work by citing the self-service opportunities we can create. Yet how many of us have actually examined the foundations of customer service? And can we still learn from the service gurus of the 80s?
Having helped develop several service-training programs -- and indirectly turned two mediocre carriers into “Airlines of the Year” -- I think customer service might just be the UX motherlode.
The concept of “customer service” has been kicking around for over a century. More recently, we’ve seen it morph into “Customer Relationship Management.” Basically, we’re talking about the design and execution of a system of activities -- people, processes, and technology -- that ultimately build brand, revenues, and customer satisfaction. These services include:
* Help me services (Scotty, beam me up)
* Fix it services (My doggone printer just ate my homework)
* Value-added services (Here’s milk to go with your cookies)
Some are online, some are offline; often they are converged systems that address both areas. In this presentation, I will review the basics of customer service and show:
* Why 90% customer satisfaction isn’t nearly good enough.
* Why most service metrics don’t address the real customer pain points
* Why service redundancy is usually way better than corporate synergy
* Why sometimes we shouldn’t listen to our customers
* How we, as ~IAs can start to create robust service experiences that build real trust and increase conversion rates.
For decades, service gurus such as Ron Zemke, John Tschohl, Karl Albrecht, and Ray Considine, have been helping businesses understand the dynamics of customer service. Some of them finally woke up to the opportunities of the Internet around 2001 -- but their messages were buried in the rubble of the dot-bomb.
I know where to dig.
http://www.iasummit.org/proceedings/2008/effective_ia_for_enterprise_po
Portal design efforts often quickly come to a point where their initial information architecture is unable to effectively accommodate change and growth in types of users, content, or functionality, thereby lowering the quality of the overall user experience. This case study style presentation will demonstrate how a framework of standardized information architecture building blocks solved these recurring problems of growth and change for a series of business intelligence and enterprise application portals.
In a narrative and visual review of the evolution of a suite of enterprise portals constructed for a major global corporation, participants will see how the building blocks provided a consistent and stable framework for the design, expansion, and eventual integration of the user experiences of nearly a dozen distinct portal design efforts.
After introducing the building blocks framework, the presentation will follow successive waves of change in the audiences, structures, and contents of the portals, highlighting the benefits of a framework based design: repeatable mental models and navigation flows, reuse of design and development work, reduced costs and timelines, incorporation of social media capabilities into existing architectures, and a shared reference point for the user experience, technical, and business perspectives.
Allowing time for time for questions and discussion, the presentation will share recommendations on planning portal design efforts, and best practices.
For intermediate and advanced level practitioners.
http://www.iasummit.org/proceedings/2008/embodying_ia_incorporating_lib
This case study describes one IA’s volunteer efforts to revitalize a small public library’s website and bring a user-centered focus to its building renovation efforts. Through blueprints, photos and architectural renderings, the presentation details how the IA worked with a local architect, building consultant, and a group of graduate students in information architecture to help the library’s administrators conceptualize new ways to integrate virtual and physical aspects of the library experience and to take the first steps toward embracing “Library 2.0,” a new service model that enables patrons to provide direct and continuous feedback on library programs and services.
Unlike other, well-documented projects involving experience integration efforts—such as the MAYA Design Group’s work on the Carnegie Library of Pittsburgh and Seattle Public Library’s large-scale efforts—this project was handicapped by all of the challenges facing small public libraries today, including drastic under-funding, minimal I.T. resources, and a general lack of awareness of information architecture and its value in developing websites and wayfinding systems. Despite its public library focus this presentation should be of interest to ~IAs of any persuasion for its demonstration of how information architecture and UCD principles can be used to address seemingly intractable service delivery problems, even in the face of severe budgetary and technological constraints.
As a former director at the Danish Royal Theatre in Copenhagen, Eric Reiss knows something about presentation. As a former copywriter at a leading European ad agency, he understands persuasion. Because he is willing to make a fool of himself, the IA Slam features good laughs and an entertaining business case. Having helped create the programs that led to two consecutive “Airline of the Year” awards, he is passionate about customer service.
Eric is author of Practical Information Architecture and Web Dogma ‘06, President of the Information Architecture Institute, Associate Professor of Usability and Design at the Instituto de Empresa Business School in Madrid, and Chair of the ~EuroIA Summit. His partners at ~FatDUX in Copenhagen, have managed to contain many of his eccentricities, including the wearing of Hawaiian shirts and tailored business suits simultaneously.
http://www.iasummit.org/proceedings/2008/exploratory_search_and_folkson
Exploratory search is triggered by the complexity of real world: we lack the knowledge or contextual awareness to formulate queries or navigate complex information spaces, the search task requires exploration, or system indexing of information is insufficient. The integration of searching and browsing is believed a necessity in this process. Today’s exploratory search systems employ different information organization schemes to facilitate searching and browsing, which are hierarchical classes, faceted categories, and clusters. In social tagging systems, where information seeking is exploratory in nature, we see a fourth one - folksonomy that aggregates user-generated tags assigning to resources also provided by them. In this paper, we study the four structures comparatively and create a grid summarizing their pros and cons in supporting exploratory search. Incompactness of folksonomy, usually considered as a defect, however enables more exploration possibilities - being aware, monitoring, searching and browsing around the three basic elements of tagging systems, which is shaped into our exploration framework for social environments.
http://www.iasummit.org/proceedings/2008/extending_the_gaming_experienc
The video game industry produces an enormous volume of highly innovative user interface experiences, but this rich source of creative thinking is largely unseen by communities dedicated to conventional software or Web design. As gaming becomes a ubiquitous activity among a vast worldwide customer base, its direction and conventions will become not merely relevant to HCI design, but indeed impossible to ignore. The vast market penetration of gaming systems also offers a large-scale laboratory for researching new directions in interactivity.
This presentation will explain the gaming experience and discuss its significance to the design of conventional user interfaces. It will further:
* Provide an overview of game-based interaction spaces, and the shared characteristics of all games. The presentation will posit applications to non-gaming UI’s, and review real world examples of gaming resolutions to interface problems.
* Discuss emerging interface standards in gaming, with an eye toward crafting analogous experiences in dissimilar applications.
* Review collaborative and competitive gaming interfaces used for synchronous play.
* Survey innovations in nonstandard video game user inputs, and speculate about possible applications to conventional software interfaces.
This presentation will be of greatest interest to user interface designers who have the opportunity to rethink broad paradigms for interactivity in software or Web development, or for those who are interested in integrating gamelike components into a UI.
The poster shows a timeline for a 10-week facilitated workgroup that explored user needs and tasks and architected the content foundation for the FAA Employee Web site. During the 10-week journey, participants followed a research-based process to gather information about Employee Web users. Stakeholders and participants asked:
* How can we learn about what people want to do with the Employee Web?
* How can we develop a structure that better reflects user needs?
* How can we apply research and testing in developing a content-rich foundation?
The poster shows the process participants followed as they moved through a user-focused Framework (following the mnemonic GECKO -- gathering, evaluating, chunking, knowing (testing and articulating) and optimizing.
Be first in line and grab some take-aways you can share with bosses and colleagues.
[img[http://students.washington.edu/adcockm/IASummit/Hyatt_1.png]]
<<tagging>>
[img[http://students.washington.edu/adcockm/IASummit/Hyatt_4.png]]
<<tagging>>
/***
|''Name:''|ForEachTiddlerPlugin|
|''Version:''|1.0.8 (2007-04-12)|
|''Source:''|http://tiddlywiki.abego-software.de/#ForEachTiddlerPlugin|
|''Author:''|UdoBorkowski (ub [at] abego-software [dot] de)|
|''Licence:''|[[BSD open source license (abego Software)|http://www.abego-software.de/legal/apl-v10.html]]|
|''Copyright:''|© 2005-2007 [[abego Software|http://www.abego-software.de]]|
|''TiddlyWiki:''|1.2.38+, 2.0|
|''Browser:''|Firefox 1.0.4+; Firefox 1.5; InternetExplorer 6.0|
!Description
Create customizable lists, tables etc. for your selections of tiddlers. Specify the tiddlers to include and their order through a powerful language.
''Syntax:''
|>|{{{<<}}}''forEachTiddler'' [''in'' //tiddlyWikiPath//] [''where'' //whereCondition//] [''sortBy'' //sortExpression// [''ascending'' //or// ''descending'']] [''script'' //scriptText//] [//action// [//actionParameters//]]{{{>>}}}|
|//tiddlyWikiPath//|The filepath to the TiddlyWiki the macro should work on. When missing the current TiddlyWiki is used.|
|//whereCondition//|(quoted) JavaScript boolean expression. May refer to the build-in variables {{{tiddler}}} and {{{context}}}.|
|//sortExpression//|(quoted) JavaScript expression returning "comparable" objects (using '{{{<}}}','{{{>}}}','{{{==}}}'. May refer to the build-in variables {{{tiddler}}} and {{{context}}}.|
|//scriptText//|(quoted) JavaScript text. Typically defines JavaScript functions that are called by the various JavaScript expressions (whereClause, sortClause, action arguments,...)|
|//action//|The action that should be performed on every selected tiddler, in the given order. By default the actions [[addToList|AddToListAction]] and [[write|WriteAction]] are supported. When no action is specified [[addToList|AddToListAction]] is used.|
|//actionParameters//|(action specific) parameters the action may refer while processing the tiddlers (see action descriptions for details). <<tiddler [[JavaScript in actionParameters]]>>|
|>|~~Syntax formatting: Keywords in ''bold'', optional parts in [...]. 'or' means that exactly one of the two alternatives must exist.~~|
See details see [[ForEachTiddlerMacro]] and [[ForEachTiddlerExamples]].
!Revision history
* v1.0.8 (2007-04-12)
** Adapted to latest TiddlyWiki 2.2 Beta importTiddlyWiki API (introduced with changeset 2004). TiddlyWiki 2.2 Beta builds prior to changeset 2004 are no longer supported (but TiddlyWiki 2.1 and earlier, of cause)
* v1.0.7 (2007-03-28)
** Also support "pre" formatted TiddlyWikis (introduced with TW 2.2) (when using "in" clause to work on external tiddlers)
* v1.0.6 (2006-09-16)
** Context provides "viewerTiddler", i.e. the tiddler used to view the macro. Most times this is equal to the "inTiddler", but when using the "tiddler" macro both may be different.
** Support "begin", "end" and "none" expressions in "write" action
* v1.0.5 (2006-02-05)
** Pass tiddler containing the macro with wikify, context object also holds reference to tiddler containing the macro ("inTiddler"). Thanks to SimonBaird.
** Support Firefox 1.5.0.1
** Internal
*** Make "JSLint" conform
*** "Only install once"
* v1.0.4 (2006-01-06)
** Support TiddlyWiki 2.0
* v1.0.3 (2005-12-22)
** Features:
*** Write output to a file supports multi-byte environments (Thanks to Bram Chen)
*** Provide API to access the forEachTiddler functionality directly through JavaScript (see getTiddlers and performMacro)
** Enhancements:
*** Improved error messages on InternetExplorer.
* v1.0.2 (2005-12-10)
** Features:
*** context object also holds reference to store (TiddlyWiki)
** Fixed Bugs:
*** ForEachTiddler 1.0.1 has broken support on win32 Opera 8.51 (Thanks to BrunoSabin for reporting)
* v1.0.1 (2005-12-08)
** Features:
*** Access tiddlers stored in separated TiddlyWikis through the "in" option. I.e. you are no longer limited to only work on the "current TiddlyWiki".
*** Write output to an external file using the "toFile" option of the "write" action. With this option you may write your customized tiddler exports.
*** Use the "script" section to define "helper" JavaScript functions etc. to be used in the various JavaScript expressions (whereClause, sortClause, action arguments,...).
*** Access and store context information for the current forEachTiddler invocation (through the build-in "context" object) .
*** Improved script evaluation (for where/sort clause and write scripts).
* v1.0.0 (2005-11-20)
** initial version
!Code
***/
//{{{
//============================================================================
//============================================================================
// ForEachTiddlerPlugin
//============================================================================
//============================================================================
// Only install once
if (!version.extensions.ForEachTiddlerPlugin) {
if (!window.abego) window.abego = {};
version.extensions.ForEachTiddlerPlugin = {
major: 1, minor: 0, revision: 8,
date: new Date(2007,3,12),
source: "http://tiddlywiki.abego-software.de/#ForEachTiddlerPlugin",
licence: "[[BSD open source license (abego Software)|http://www.abego-software.de/legal/apl-v10.html]]",
copyright: "Copyright (c) abego Software GmbH, 2005-2007 (www.abego-software.de)"
};
// For backward compatibility with TW 1.2.x
//
if (!TiddlyWiki.prototype.forEachTiddler) {
TiddlyWiki.prototype.forEachTiddler = function(callback) {
for(var t in this.tiddlers) {
callback.call(this,t,this.tiddlers[t]);
}
};
}
//============================================================================
// forEachTiddler Macro
//============================================================================
version.extensions.forEachTiddler = {
major: 1, minor: 0, revision: 8, date: new Date(2007,3,12), provider: "http://tiddlywiki.abego-software.de"};
// ---------------------------------------------------------------------------
// Configurations and constants
// ---------------------------------------------------------------------------
config.macros.forEachTiddler = {
// Standard Properties
label: "forEachTiddler",
prompt: "Perform actions on a (sorted) selection of tiddlers",
// actions
actions: {
addToList: {},
write: {}
}
};
// ---------------------------------------------------------------------------
// The forEachTiddler Macro Handler
// ---------------------------------------------------------------------------
config.macros.forEachTiddler.getContainingTiddler = function(e) {
while(e && !hasClass(e,"tiddler"))
e = e.parentNode;
var title = e ? e.getAttribute("tiddler") : null;
return title ? store.getTiddler(title) : null;
};
config.macros.forEachTiddler.handler = function(place,macroName,params,wikifier,paramString,tiddler) {
// config.macros.forEachTiddler.traceMacroCall(place,macroName,params,wikifier,paramString,tiddler);
if (!tiddler) tiddler = config.macros.forEachTiddler.getContainingTiddler(place);
// --- Parsing ------------------------------------------
var i = 0; // index running over the params
// Parse the "in" clause
var tiddlyWikiPath = undefined;
if ((i < params.length) && params[i] == "in") {
i++;
if (i >= params.length) {
this.handleError(place, "TiddlyWiki path expected behind 'in'.");
return;
}
tiddlyWikiPath = this.paramEncode((i < params.length) ? params[i] : "");
i++;
}
// Parse the where clause
var whereClause ="true";
if ((i < params.length) && params[i] == "where") {
i++;
whereClause = this.paramEncode((i < params.length) ? params[i] : "");
i++;
}
// Parse the sort stuff
var sortClause = null;
var sortAscending = true;
if ((i < params.length) && params[i] == "sortBy") {
i++;
if (i >= params.length) {
this.handleError(place, "sortClause missing behind 'sortBy'.");
return;
}
sortClause = this.paramEncode(params[i]);
i++;
if ((i < params.length) && (params[i] == "ascending" || params[i] == "descending")) {
sortAscending = params[i] == "ascending";
i++;
}
}
// Parse the script
var scriptText = null;
if ((i < params.length) && params[i] == "script") {
i++;
scriptText = this.paramEncode((i < params.length) ? params[i] : "");
i++;
}
// Parse the action.
// When we are already at the end use the default action
var actionName = "addToList";
if (i < params.length) {
if (!config.macros.forEachTiddler.actions[params[i]]) {
this.handleError(place, "Unknown action '"+params[i]+"'.");
return;
} else {
actionName = params[i];
i++;
}
}
// Get the action parameter
// (the parsing is done inside the individual action implementation.)
var actionParameter = params.slice(i);
// --- Processing ------------------------------------------
try {
this.performMacro({
place: place,
inTiddler: tiddler,
whereClause: whereClause,
sortClause: sortClause,
sortAscending: sortAscending,
actionName: actionName,
actionParameter: actionParameter,
scriptText: scriptText,
tiddlyWikiPath: tiddlyWikiPath});
} catch (e) {
this.handleError(place, e);
}
};
// Returns an object with properties "tiddlers" and "context".
// tiddlers holds the (sorted) tiddlers selected by the parameter,
// context the context of the execution of the macro.
//
// The action is not yet performed.
//
// @parameter see performMacro
//
config.macros.forEachTiddler.getTiddlersAndContext = function(parameter) {
var context = config.macros.forEachTiddler.createContext(parameter.place, parameter.whereClause, parameter.sortClause, parameter.sortAscending, parameter.actionName, parameter.actionParameter, parameter.scriptText, parameter.tiddlyWikiPath, parameter.inTiddler);
var tiddlyWiki = parameter.tiddlyWikiPath ? this.loadTiddlyWiki(parameter.tiddlyWikiPath) : store;
context["tiddlyWiki"] = tiddlyWiki;
// Get the tiddlers, as defined by the whereClause
var tiddlers = this.findTiddlers(parameter.whereClause, context, tiddlyWiki);
context["tiddlers"] = tiddlers;
// Sort the tiddlers, when sorting is required.
if (parameter.sortClause) {
this.sortTiddlers(tiddlers, parameter.sortClause, parameter.sortAscending, context);
}
return {tiddlers: tiddlers, context: context};
};
// Returns the (sorted) tiddlers selected by the parameter.
//
// The action is not yet performed.
//
// @parameter see performMacro
//
config.macros.forEachTiddler.getTiddlers = function(parameter) {
return this.getTiddlersAndContext(parameter).tiddlers;
};
// Performs the macros with the given parameter.
//
// @param parameter holds the parameter of the macro as separate properties.
// The following properties are supported:
//
// place
// whereClause
// sortClause
// sortAscending
// actionName
// actionParameter
// scriptText
// tiddlyWikiPath
//
// All properties are optional.
// For most actions the place property must be defined.
//
config.macros.forEachTiddler.performMacro = function(parameter) {
var tiddlersAndContext = this.getTiddlersAndContext(parameter);
// Perform the action
var actionName = parameter.actionName ? parameter.actionName : "addToList";
var action = config.macros.forEachTiddler.actions[actionName];
if (!action) {
this.handleError(parameter.place, "Unknown action '"+actionName+"'.");
return;
}
var actionHandler = action.handler;
actionHandler(parameter.place, tiddlersAndContext.tiddlers, parameter.actionParameter, tiddlersAndContext.context);
};
// ---------------------------------------------------------------------------
// The actions
// ---------------------------------------------------------------------------
// Internal.
//
// --- The addToList Action -----------------------------------------------
//
config.macros.forEachTiddler.actions.addToList.handler = function(place, tiddlers, parameter, context) {
// Parse the parameter
var p = 0;
// Check for extra parameters
if (parameter.length > p) {
config.macros.forEachTiddler.createExtraParameterErrorElement(place, "addToList", parameter, p);
return;
}
// Perform the action.
var list = document.createElement("ul");
place.appendChild(list);
for (var i = 0; i < tiddlers.length; i++) {
var tiddler = tiddlers[i];
var listItem = document.createElement("li");
list.appendChild(listItem);
createTiddlyLink(listItem, tiddler.title, true);
}
};
abego.parseNamedParameter = function(name, parameter, i) {
var beginExpression = null;
if ((i < parameter.length) && parameter[i] == name) {
i++;
if (i >= parameter.length) {
throw "Missing text behind '%0'".format([name]);
}
return config.macros.forEachTiddler.paramEncode(parameter[i]);
}
return null;
}
// Internal.
//
// --- The write Action ---------------------------------------------------
//
config.macros.forEachTiddler.actions.write.handler = function(place, tiddlers, parameter, context) {
// Parse the parameter
var p = 0;
if (p >= parameter.length) {
this.handleError(place, "Missing expression behind 'write'.");
return;
}
var textExpression = config.macros.forEachTiddler.paramEncode(parameter[p]);
p++;
// Parse the "begin" option
var beginExpression = abego.parseNamedParameter("begin", parameter, p);
if (beginExpression !== null)
p += 2;
var endExpression = abego.parseNamedParameter("end", parameter, p);
if (endExpression !== null)
p += 2;
var noneExpression = abego.parseNamedParameter("none", parameter, p);
if (noneExpression !== null)
p += 2;
// Parse the "toFile" option
var filename = null;
var lineSeparator = undefined;
if ((p < parameter.length) && parameter[p] == "toFile") {
p++;
if (p >= parameter.length) {
this.handleError(place, "Filename expected behind 'toFile' of 'write' action.");
return;
}
filename = config.macros.forEachTiddler.getLocalPath(config.macros.forEachTiddler.paramEncode(parameter[p]));
p++;
if ((p < parameter.length) && parameter[p] == "withLineSeparator") {
p++;
if (p >= parameter.length) {
this.handleError(place, "Line separator text expected behind 'withLineSeparator' of 'write' action.");
return;
}
lineSeparator = config.macros.forEachTiddler.paramEncode(parameter[p]);
p++;
}
}
// Check for extra parameters
if (parameter.length > p) {
config.macros.forEachTiddler.createExtraParameterErrorElement(place, "write", parameter, p);
return;
}
// Perform the action.
var func = config.macros.forEachTiddler.getEvalTiddlerFunction(textExpression, context);
var count = tiddlers.length;
var text = "";
if (count > 0 && beginExpression)
text += config.macros.forEachTiddler.getEvalTiddlerFunction(beginExpression, context)(undefined, context, count, undefined);
for (var i = 0; i < count; i++) {
var tiddler = tiddlers[i];
text += func(tiddler, context, count, i);
}
if (count > 0 && endExpression)
text += config.macros.forEachTiddler.getEvalTiddlerFunction(endExpression, context)(undefined, context, count, undefined);
if (count == 0 && noneExpression)
text += config.macros.forEachTiddler.getEvalTiddlerFunction(noneExpression, context)(undefined, context, count, undefined);
if (filename) {
if (lineSeparator !== undefined) {
lineSeparator = lineSeparator.replace(/\\n/mg, "\n").replace(/\\r/mg, "\r");
text = text.replace(/\n/mg,lineSeparator);
}
saveFile(filename, convertUnicodeToUTF8(text));
} else {
var wrapper = createTiddlyElement(place, "span");
wikify(text, wrapper, null/* highlightRegExp */, context.inTiddler);
}
};
// ---------------------------------------------------------------------------
// Helpers
// ---------------------------------------------------------------------------
// Internal.
//
config.macros.forEachTiddler.createContext = function(placeParam, whereClauseParam, sortClauseParam, sortAscendingParam, actionNameParam, actionParameterParam, scriptText, tiddlyWikiPathParam, inTiddlerParam) {
return {
place : placeParam,
whereClause : whereClauseParam,
sortClause : sortClauseParam,
sortAscending : sortAscendingParam,
script : scriptText,
actionName : actionNameParam,
actionParameter : actionParameterParam,
tiddlyWikiPath : tiddlyWikiPathParam,
inTiddler : inTiddlerParam, // the tiddler containing the <<forEachTiddler ...>> macro call.
viewerTiddler : config.macros.forEachTiddler.getContainingTiddler(placeParam) // the tiddler showing the forEachTiddler result
};
};
// Internal.
//
// Returns a TiddlyWiki with the tiddlers loaded from the TiddlyWiki of
// the given path.
//
config.macros.forEachTiddler.loadTiddlyWiki = function(path, idPrefix) {
if (!idPrefix) {
idPrefix = "store";
}
var lenPrefix = idPrefix.length;
// Read the content of the given file
var content = loadFile(this.getLocalPath(path));
if(content === null) {
throw "TiddlyWiki '"+path+"' not found.";
}
var tiddlyWiki = new TiddlyWiki();
// Starting with TW 2.2 there is a helper function to import the tiddlers
if (tiddlyWiki.importTiddlyWiki) {
if (!tiddlyWiki.importTiddlyWiki(content))
throw "File '"+path+"' is not a TiddlyWiki.";
tiddlyWiki.dirty = false;
return tiddlyWiki;
}
// The legacy code, for TW < 2.2
// Locate the storeArea div's
var posOpeningDiv = content.indexOf(startSaveArea);
var posClosingDiv = content.lastIndexOf(endSaveArea);
if((posOpeningDiv == -1) || (posClosingDiv == -1)) {
throw "File '"+path+"' is not a TiddlyWiki.";
}
var storageText = content.substr(posOpeningDiv + startSaveArea.length, posClosingDiv);
// Create a "div" element that contains the storage text
var myStorageDiv = document.createElement("div");
myStorageDiv.innerHTML = storageText;
myStorageDiv.normalize();
// Create all tiddlers in a new TiddlyWiki
// (following code is modified copy of TiddlyWiki.prototype.loadFromDiv)
var store = myStorageDiv.childNodes;
for(var t = 0; t < store.length; t++) {
var e = store[t];
var title = null;
if(e.getAttribute)
title = e.getAttribute("tiddler");
if(!title && e.id && e.id.substr(0,lenPrefix) == idPrefix)
title = e.id.substr(lenPrefix);
if(title && title !== "") {
var tiddler = tiddlyWiki.createTiddler(title);
tiddler.loadFromDiv(e,title);
}
}
tiddlyWiki.dirty = false;
return tiddlyWiki;
};
// Internal.
//
// Returns a function that has a function body returning the given javaScriptExpression.
// The function has the parameters:
//
// (tiddler, context, count, index)
//
config.macros.forEachTiddler.getEvalTiddlerFunction = function (javaScriptExpression, context) {
var script = context["script"];
var functionText = "var theFunction = function(tiddler, context, count, index) { return "+javaScriptExpression+"}";
var fullText = (script ? script+";" : "")+functionText+";theFunction;";
return eval(fullText);
};
// Internal.
//
config.macros.forEachTiddler.findTiddlers = function(whereClause, context, tiddlyWiki) {
var result = [];
var func = config.macros.forEachTiddler.getEvalTiddlerFunction(whereClause, context);
tiddlyWiki.forEachTiddler(function(title,tiddler) {
if (func(tiddler, context, undefined, undefined)) {
result.push(tiddler);
}
});
return result;
};
// Internal.
//
config.macros.forEachTiddler.createExtraParameterErrorElement = function(place, actionName, parameter, firstUnusedIndex) {
var message = "Extra parameter behind '"+actionName+"':";
for (var i = firstUnusedIndex; i < parameter.length; i++) {
message += " "+parameter[i];
}
this.handleError(place, message);
};
// Internal.
//
config.macros.forEachTiddler.sortAscending = function(tiddlerA, tiddlerB) {
var result =
(tiddlerA.forEachTiddlerSortValue == tiddlerB.forEachTiddlerSortValue)
? 0
: (tiddlerA.forEachTiddlerSortValue < tiddlerB.forEachTiddlerSortValue)
? -1
: +1;
return result;
};
// Internal.
//
config.macros.forEachTiddler.sortDescending = function(tiddlerA, tiddlerB) {
var result =
(tiddlerA.forEachTiddlerSortValue == tiddlerB.forEachTiddlerSortValue)
? 0
: (tiddlerA.forEachTiddlerSortValue < tiddlerB.forEachTiddlerSortValue)
? +1
: -1;
return result;
};
// Internal.
//
config.macros.forEachTiddler.sortTiddlers = function(tiddlers, sortClause, ascending, context) {
// To avoid evaluating the sortClause whenever two items are compared
// we pre-calculate the sortValue for every item in the array and store it in a
// temporary property ("forEachTiddlerSortValue") of the tiddlers.
var func = config.macros.forEachTiddler.getEvalTiddlerFunction(sortClause, context);
var count = tiddlers.length;
var i;
for (i = 0; i < count; i++) {
var tiddler = tiddlers[i];
tiddler.forEachTiddlerSortValue = func(tiddler,context, undefined, undefined);
}
// Do the sorting
tiddlers.sort(ascending ? this.sortAscending : this.sortDescending);
// Delete the temporary property that holds the sortValue.
for (i = 0; i < tiddlers.length; i++) {
delete tiddlers[i].forEachTiddlerSortValue;
}
};
// Internal.
//
config.macros.forEachTiddler.trace = function(message) {
displayMessage(message);
};
// Internal.
//
config.macros.forEachTiddler.traceMacroCall = function(place,macroName,params) {
var message ="<<"+macroName;
for (var i = 0; i < params.length; i++) {
message += " "+params[i];
}
message += ">>";
displayMessage(message);
};
// Internal.
//
// Creates an element that holds an error message
//
config.macros.forEachTiddler.createErrorElement = function(place, exception) {
var message = (exception.description) ? exception.description : exception.toString();
return createTiddlyElement(place,"span",null,"forEachTiddlerError","<<forEachTiddler ...>>: "+message);
};
// Internal.
//
// @param place [may be null]
//
config.macros.forEachTiddler.handleError = function(place, exception) {
if (place) {
this.createErrorElement(place, exception);
} else {
throw exception;
}
};
// Internal.
//
// Encodes the given string.
//
// Replaces
// "$))" to ">>"
// "$)" to ">"
//
config.macros.forEachTiddler.paramEncode = function(s) {
var reGTGT = new RegExp("\\$\\)\\)","mg");
var reGT = new RegExp("\\$\\)","mg");
return s.replace(reGTGT, ">>").replace(reGT, ">");
};
// Internal.
//
// Returns the given original path (that is a file path, starting with "file:")
// as a path to a local file, in the systems native file format.
//
// Location information in the originalPath (i.e. the "#" and stuff following)
// is stripped.
//
config.macros.forEachTiddler.getLocalPath = function(originalPath) {
// Remove any location part of the URL
var hashPos = originalPath.indexOf("#");
if(hashPos != -1)
originalPath = originalPath.substr(0,hashPos);
// Convert to a native file format assuming
// "file:///x:/path/path/path..." - pc local file --> "x:\path\path\path..."
// "file://///server/share/path/path/path..." - FireFox pc network file --> "\\server\share\path\path\path..."
// "file:///path/path/path..." - mac/unix local file --> "/path/path/path..."
// "file://server/share/path/path/path..." - pc network file --> "\\server\share\path\path\path..."
var localPath;
if(originalPath.charAt(9) == ":") // pc local file
localPath = unescape(originalPath.substr(8)).replace(new RegExp("/","g"),"\\");
else if(originalPath.indexOf("file://///") === 0) // FireFox pc network file
localPath = "\\\\" + unescape(originalPath.substr(10)).replace(new RegExp("/","g"),"\\");
else if(originalPath.indexOf("file:///") === 0) // mac/unix local file
localPath = unescape(originalPath.substr(7));
else if(originalPath.indexOf("file:/") === 0) // mac/unix local file
localPath = unescape(originalPath.substr(5));
else // pc network file
localPath = "\\\\" + unescape(originalPath.substr(7)).replace(new RegExp("/","g"),"\\");
return localPath;
};
// ---------------------------------------------------------------------------
// Stylesheet Extensions (may be overridden by local StyleSheet)
// ---------------------------------------------------------------------------
//
setStylesheet(
".forEachTiddlerError{color: #ffffff;background-color: #880000;}",
"forEachTiddler");
//============================================================================
// End of forEachTiddler Macro
//============================================================================
//============================================================================
// String.startsWith Function
//============================================================================
//
// Returns true if the string starts with the given prefix, false otherwise.
//
version.extensions["String.startsWith"] = {major: 1, minor: 0, revision: 0, date: new Date(2005,11,20), provider: "http://tiddlywiki.abego-software.de"};
//
String.prototype.startsWith = function(prefix) {
var n = prefix.length;
return (this.length >= n) && (this.slice(0, n) == prefix);
};
//============================================================================
// String.endsWith Function
//============================================================================
//
// Returns true if the string ends with the given suffix, false otherwise.
//
version.extensions["String.endsWith"] = {major: 1, minor: 0, revision: 0, date: new Date(2005,11,20), provider: "http://tiddlywiki.abego-software.de"};
//
String.prototype.endsWith = function(suffix) {
var n = suffix.length;
return (this.length >= n) && (this.right(n) == suffix);
};
//============================================================================
// String.contains Function
//============================================================================
//
// Returns true when the string contains the given substring, false otherwise.
//
version.extensions["String.contains"] = {major: 1, minor: 0, revision: 0, date: new Date(2005,11,20), provider: "http://tiddlywiki.abego-software.de"};
//
String.prototype.contains = function(substring) {
return this.indexOf(substring) >= 0;
};
//============================================================================
// Array.indexOf Function
//============================================================================
//
// Returns the index of the first occurance of the given item in the array or
// -1 when no such item exists.
//
// @param item [may be null]
//
version.extensions["Array.indexOf"] = {major: 1, minor: 0, revision: 0, date: new Date(2005,11,20), provider: "http://tiddlywiki.abego-software.de"};
//
Array.prototype.indexOf = function(item) {
for (var i = 0; i < this.length; i++) {
if (this[i] == item) {
return i;
}
}
return -1;
};
//============================================================================
// Array.contains Function
//============================================================================
//
// Returns true when the array contains the given item, otherwise false.
//
// @param item [may be null]
//
version.extensions["Array.contains"] = {major: 1, minor: 0, revision: 0, date: new Date(2005,11,20), provider: "http://tiddlywiki.abego-software.de"};
//
Array.prototype.contains = function(item) {
return (this.indexOf(item) >= 0);
};
//============================================================================
// Array.containsAny Function
//============================================================================
//
// Returns true when the array contains at least one of the elements
// of the item. Otherwise (or when items contains no elements) false is returned.
//
version.extensions["Array.containsAny"] = {major: 1, minor: 0, revision: 0, date: new Date(2005,11,20), provider: "http://tiddlywiki.abego-software.de"};
//
Array.prototype.containsAny = function(items) {
for(var i = 0; i < items.length; i++) {
if (this.contains(items[i])) {
return true;
}
}
return false;
};
//============================================================================
// Array.containsAll Function
//============================================================================
//
// Returns true when the array contains all the items, otherwise false.
//
// When items is null false is returned (even if the array contains a null).
//
// @param items [may be null]
//
version.extensions["Array.containsAll"] = {major: 1, minor: 0, revision: 0, date: new Date(2005,11,20), provider: "http://tiddlywiki.abego-software.de"};
//
Array.prototype.containsAll = function(items) {
for(var i = 0; i < items.length; i++) {
if (!this.contains(items[i])) {
return false;
}
}
return true;
};
} // of "install only once"
// Used Globals (for JSLint) ==============
// ... DOM
/*global document */
// ... TiddlyWiki Core
/*global convertUnicodeToUTF8, createTiddlyElement, createTiddlyLink,
displayMessage, endSaveArea, hasClass, loadFile, saveFile,
startSaveArea, store, wikify */
//}}}
/***
!Licence and Copyright
Copyright (c) abego Software ~GmbH, 2005 ([[www.abego-software.de|http://www.abego-software.de]])
Redistribution and use in source and binary forms, with or without modification,
are permitted provided that the following conditions are met:
Redistributions of source code must retain the above copyright notice, this
list of conditions and the following disclaimer.
Redistributions in binary form must reproduce the above copyright notice, this
list of conditions and the following disclaimer in the documentation and/or other
materials provided with the distribution.
Neither the name of abego Software nor the names of its contributors may be
used to endorse or promote products derived from this software without specific
prior written permission.
THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS" AND ANY
EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES
OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT
SHALL THE COPYRIGHT OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT,
INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED
TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR
BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN
CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN
ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH
DAMAGE.
***/
| | ![[Flagler / Monroe]] | ![[Brickell]] | ![[Tuttle]] | ![[Flex: Orchid C/D]] |
| [[8:00 - 8:30AM|08:00 - 8:30AM]] |>|>|>| Registration |
| [[8:30 - 5:30PM|08:30 - 5:30PM]] |>|>|>| ~Pre-Conference Workshops |
| [[6:30 - 8:30PM]] |>|>|>| Welcome Reception |
Garrick Schmitt is Vice President of User Experience at Avenue A | Razorfish. Over the past eight years, he has helped clients and industry leaders envision and deliver breakthrough customer experiences across multiple platforms. He also leads an in-house innovation team that is focused on next-generation consumer applications and technologies; and writes and edits Avenue A | Razorfish's Digital Design Blog at www.digitaldesignblog.com
Gene Smith is an information architect and social media aficionado. He’s the author of Tagging: ~People-Powered Metadata for the Social Web (2008, New Riders), which covers the design and development of tagging systems. At nForm User Experience he advises a variety of clients on their IA, design and social media strategies.
http://www.iasummit.org/proceedings/2008/good_news_on_your_cell_phone_o
Newspapers still struggle with the transition from paper to WEB. They face an even harder challenge (because of ) the extended use of WAP for reading news on cell phones. How can complex and rich content be adapted to a media with such specific constraints and without diminishing the user experience? We will demonstrate Best Practise WAP design through an evaluation of the five largest newspapers in Norway.
We will demonstrate how the differences in the European, American and Asian markets affect the services themselves.
What you will learn:
* The challenges involved when transferring content from one media to another
* Mobile interface design: How to create good user experiences in different media
* The diverse user behaviour of celluar phones in Europe, the United States and Asia
Greg Nudelman is a Senior User Experience Engineer at eBay. Greg holds MS CIS and has been researching, designing and developing software since 1997.
Hallie Wilfert works as an Information Architect at SRA International, a technology and strategic consulting firm in Arlington, VA. Previously, Hallie worked as the Director of New Media at the Institute of Medicine. Hallie received her B.A. in American Studies, studying at University of California, Berkeley and University of Maryland, College Park. She likes data and likes to use data to make web sites easier to use. Hallie presented at the 2007 IA Summit on “My Grandmother the Information Architect.”
Henning Fischer is a design strategist for Adaptive Path. His principal focus is on design research and strategy development. He holds a Master of Design from the Institute of Design at Illinois Institute of Technology. Henning's portfolio of skills include digital product strategy development, business concept illustration, and user-centered research and analysis techniques. Past clients include Ameriprise, Eli Lilly, Guggenheim Museum, Hallmark, Hunter Douglas, Japan Society, ~LeapFrog, Magellan, Novartis, Trek Bicycle Corporation, uGenie, Vanguard Financial. He speaks German fluently and is diligently working on his Mandarin to impress his in-laws.
/***
|Name:|HideWhenPlugin|
|Description:|Allows conditional inclusion/exclusion in templates|
|Version:|3.1 ($Rev: 3919 $)|
|Date:|$Date: 2008-03-13 02:03:12 +1000 (Thu, 13 Mar 2008) $|
|Source:|http://mptw.tiddlyspot.com/#HideWhenPlugin|
|Author:|Simon Baird <simon.baird@gmail.com>|
|License:|http://mptw.tiddlyspot.com/#TheBSDLicense|
For use in ViewTemplate and EditTemplate. Example usage:
{{{<div macro="showWhenTagged Task">[[TaskToolbar]]</div>}}}
{{{<div macro="showWhen tiddler.modifier == 'BartSimpson'"><img src="bart.gif"/></div>}}}
***/
//{{{
window.hideWhenLastTest = false;
window.removeElementWhen = function(test,place) {
window.hideWhenLastTest = test;
if (test) {
removeChildren(place);
place.parentNode.removeChild(place);
}
};
merge(config.macros,{
hideWhen: { handler: function(place,macroName,params,wikifier,paramString,tiddler) {
removeElementWhen( eval(paramString), place);
}},
showWhen: { handler: function(place,macroName,params,wikifier,paramString,tiddler) {
removeElementWhen( !eval(paramString), place);
}},
hideWhenTagged: { handler: function (place,macroName,params,wikifier,paramString,tiddler) {
removeElementWhen( tiddler.tags.containsAll(params), place);
}},
showWhenTagged: { handler: function (place,macroName,params,wikifier,paramString,tiddler) {
removeElementWhen( !tiddler.tags.containsAll(params), place);
}},
hideWhenTaggedAny: { handler: function (place,macroName,params,wikifier,paramString,tiddler) {
removeElementWhen( tiddler.tags.containsAny(params), place);
}},
showWhenTaggedAny: { handler: function (place,macroName,params,wikifier,paramString,tiddler) {
removeElementWhen( !tiddler.tags.containsAny(params), place);
}},
hideWhenTaggedAll: { handler: function (place,macroName,params,wikifier,paramString,tiddler) {
removeElementWhen( tiddler.tags.containsAll(params), place);
}},
showWhenTaggedAll: { handler: function (place,macroName,params,wikifier,paramString,tiddler) {
removeElementWhen( !tiddler.tags.containsAll(params), place);
}},
hideWhenExists: { handler: function(place,macroName,params,wikifier,paramString,tiddler) {
removeElementWhen( store.tiddlerExists(params[0]) || store.isShadowTiddler(params[0]), place);
}},
showWhenExists: { handler: function(place,macroName,params,wikifier,paramString,tiddler) {
removeElementWhen( !(store.tiddlerExists(params[0]) || store.isShadowTiddler(params[0])), place);
}},
hideWhenTitleIs: { handler: function(place,macroName,params,wikifier,paramString,tiddler) {
removeElementWhen( tiddler.title == params[0], place);
}},
showWhenTitleIs: { handler: function(place,macroName,params,wikifier,paramString,tiddler) {
removeElementWhen( tiddler.title != params[0], place);
}},
'else': { handler: function(place,macroName,params,wikifier,paramString,tiddler) {
removeElementWhen( !window.hideWhenLastTest, place);
}}
});
//}}}
http://www.iasummit.org/proceedings/2008/hotel_yeoville
Ethnographic research methods and an empathetic approach to users can form the basis for information architecture solutions that attempt to directly address and improve the lives of people in developing countries.
Yeoville is a neglected suburb in Johannesburg. Over 65% of its inhabitants are foreign African nationals. It is a space of dislocation, insecurity, uncertainty, transience, neglect, crime, contest, exploitation and the transgression of boundaries. It is also one of two Internet Café hubs in the city.
This project uses a community based website as the default home page in Internet cafés. By working with Internet cafés and survival strategies already present and employed by people in these communities we are exploring how information environments and tools can improve lives.
The project aims to investigate, record and make visible the experience of the people who are living there, and to consider the implication of these reflections for the decisions of policymakers, city planners and designers.
We will share insight into the community, our ethnographic research methods, the findings, the intervention and UX strategy, the information architecture solution and the impact that the solution is making.
Audience
Information architects (all levels), user experience designers, researchers and those with an interest in the digital divide topic and design for developing contexts.
http://www.iasummit.org/proceedings/2008/how_to_be_a_user_experience_te
Team structures have naturally creative properties. There's an exchange and evolution of ideas that happens when you have many people thinking about a problem. Solo ~IAs and interaction designers must produce creative solutions without the support of a team, and it can make their work challenging. Furthermore, the fledgling commitment to user experience in many organizations can make UX professionals feel that they need to focus on defending their work, rather than scrutinizing it to see if superior ideas for user experience emerge.
Still, it's possible for solo practitioners to achieve the creative results that teams do by adopting the methods of larger user experience groups. Here, Leah will share a number of design techniques that Adaptive Path uses, and show how they can be adapted for use in a solo practice.
In this session, you'll learn specific techniques that you can use to generate and refine design ideas. You'll see how these activities can help you speak with greater authority about the tradeoffs in various design directions. Attendees will learn flexible, simple activities that can be used quickly, wherever they're needed. Most require little more than pen and paper.
This session is recommended for all solo practitioners, as well as anyone who regularly works on projects as the only user experience professional.
http://www.iasummit.org/proceedings/2008/how_to_set_up_and_run_particip
This workshop will provide user experience professionals with practical guidance on how to successfully set up and run participatory design sessions, analyze data and present results effectively to project stake-holders. Lab set-up with a range of budgets, appropriate methodologies like PICTIVE, group and individual design sessions will be discussed. After attending the course, attendees should be able to:
#. Set up and run a successful participatory design session.
#. Determine the right methods and tools to fit specific projects.
#. Analyze and interpret participatory design session data.
#. Create an effective presentation and deliver clear recommendations to project stakeholders.
#. Understand how participatory design can fit into your company’s user-centered research and design strategy.
http://www.iasummit.org/proceedings/2008/ia_slam_2008_the_workshop_with
In this session, we're not looking for a definition of what we do, or arcane methodologies, or gilt-edged case studies: we're looking for results, and we promise a clear-cut winner. Good design demands cross-disciplinary collaboration to reconcile the particular with the grand in a politicized world. This session brings the rhetorical spices of ethos and pathos to locus, coupled to a deadline from hell, to challenge ideas of practice and teamwork and to seek a roadmap to re-engineer the project delivery process. We emphasize creation, integration, presentation, and results. Not your garden-variety lecture and ~PowerPoint presentation; this is hands-on interactive adventure that is fun and educational.
During the session, participants are divided into groups. The groups are presented with a project, provided with client-side deliverables, and allowed to interview the client team. Groups create and present a solution within a deliberately stressful timeframe. The session concludes with presentations from the groups to the assembly. Presentations will be evaluated on technical and artistic criteria. Bonus points will be awarded for creative headgear. Judging criteria are loosely based on the 2002 International Skating Union publication "Judging Olympic Figure Skating". The medal in Information Architecture will be awarded at the following day’s luncheon.
http://www.iasummit.org/proceedings/2008/ia_for_tiny_stuff_exploring_de
Much of the challenge of information architecture since the inception of the web has revolved around making coherent and useful web 'sites' and web 'pages'. However, it is becoming just as common to see information presented in small discrete chunks known as 'widgets'.
The explosion of social networking sites has created a demand for widgets to add to profiles. Whether it is the last track you played, predictions for your star-sign, or the scores of the team you support, there seems to be a widget for everything. Meanwhile, Google and Yahoo! both have cross-platform desktop-based widget formats, and the growing market-share of Vista is exposing an increasing number of business users to the potential of Vista Gadgets. The rise of widgets poses new IA challenges. How can a client's requirements be crammed into such a tiny space? How do you attract and retain audience attention without cluttering the user's desktop or Facebook profile?
This talk examines what makes a successful widget from an information delivery point of view. It also looks at how information professionals can help develop more 'playful' ways of representing and structuring the information presented. These examples will illustrate how to develop a more engaging user experience, one that stands out from the all-too-common formula of 'information feed + logo + home link = marketing widget'.
http://www.iasummit.org/proceedings/2008/ias_language_and_lego_an_intro
Typically, the approach taken by ~IAs to understand and categorise content is through conduct content audits and content analysis – a process that would be a lot simpler if content was created like building a Lego™ model – in a structured, logical and consistent way.
Unfortunately, English is messy, with exceptions to rules, different styles of writing, and a multitude of different ways to write about exactly the same thing. This apparent lack of structure means that analysis is always hard, very time consuming, and made all the more difficult if you lack subject-area expertise.
This presentation will introduce Semantic Analysis – a way in which content can be analysed and classified through its linguistic basis, rather than through its overt meaning. It will achieve this by using Lego as a metaphor for language and demonstrating that by examining the building blocks of language a deeper understanding of content can be gained.
A case study involving the analysis of medical restrictions text will be used to demonstrate the effectiveness of this approach, and how it informed the creation of a tool that would help codify the content, make it machine readable for repurposing, and introduce a higher level of standardisation.
The presentation will also highlight the potential of this approach in other areas, including search engine optimisation and content/language translation.
The tragic events of 9/11, Hurricane Katrina, and Virginia Tech have forced professionals at the federal, state and local levels to examine the way information resources are organized and then distributed to the public. While FEMA is currently working on ways to develop and implement a plan for an integrated national Emergency Alerting System (EAS), there has been a lack of coordination between state and local government resources. The coordination and cooperation of government policy and technical resources is crucial in achieving the goal of effective emergency message dissemination. Stakeholders involved can benefit from understanding the information architecture of a new proposed EAS. The current work focuses on the information architecture of both policy and technical resources. This poster presents a visual model representing the importance of resource coordination in order to achieve the goal of effective emergency message dissemination.
http://www.iasummit.org/proceedings/2008/information_horizons_proposing
Having a difficult time translating users’ need into the website architecture? Are you looking for ways to counter the influences of the lab environment or the issues with wording in surveys? Do you want to go a step further than surveys, interviews and focus groups? Here is another tool that can counter issues with user's feedback and attempts to provide highly contextual feedback from the user's perspective.
We propose the application of Sonnenwald's 'Information Horizons' (IH) framework that helps to get the user's feedback through a graphical representation of the user's behavior that involves the information sources they access, the tools they use to access that information and a verbal feedback of the user as a discussion of their behavior. The framework allows an open-ended unstructured protocol for the user to provide rich feedback in the relevant context through a free flow of information right from their past experience and usual information habits.
We will report the use of the IH framework for assessing a website architecture based on Morville and Rosenfeld’s components of website architecture - organization, labeling, navigation and searching information.
Ingrid Tofte is a senior Interaction Designer with Logica´s UX unit in Oslo, Norway. Apart from freezing a lot, Ingrid has spent the last 12 years of her life designing interactive solutions for some of Norway´s most renowned brands.
// //''Description:'' Inserts a small star graphic at the location of the macro and does not require any external graphics. The method used should work on most current browser platforms.
// //Examples: <<star>>
// //''Code section:''
version.extensions.star = {major: 0, minor: 1, revision: 1, date: new Date("Mar 13, 2008")};
config.macros.star = {}
config.macros.star.handler = function(place,macroName,params)
{
var palette = ["transparent","#cbb339","#e0bf39","#dec344","#edca3f","#e7d24a","#f3d645","#dfca5d","#f7d854","#fbe262","#d6c677","#e4d27f","#e0d494","#f9e78e","#d2cead","#e7d6a5","#e9dbb2","#ded6ce","#e7e1d3","#efe7c6","#efe7ce","#efe7d6","#f1efde","#f7efe7","#f7f7e7","#fffff7"];
var data = params;
var imageMap = null;
if(!data[0])
imageMap = "aaaaaaaraaaaaaaaaaaaaaqxaaaaaaaaaaaaxltaaaaaaaaaaaamilaaaaaaaaaaaahihaaaaaarttstpiieptsttrxkfnnjjigjnnfkxaxmdfiiiiifdmxaaaapddefecdpaaaaaaamecbfemaaaaaaaalebbcelaaaaaaavfcbkbcfvaaaaaaqcbtathcqaaaaaakksaaaxkkaaaaaaoaaaaaaaoaaa";
else
createTiddlyElement(place,"span",null,"errorNoSuchMacro","unknown star");
if(imageMap)
{
var box = createTiddlyElement(place,"span",null,"star",String.fromCharCode(160));
box.style.position = "relative";
box.style.width = "15px";
box.style.height = "15px";
box.style.marginLeft = "1px";
box.style.marginRight = "1px";
box.style.paddingRight = "12px";
box.style.verticalAlign = "top";
//now divide into 15x15 grid and create each pixel
// rows
for(r=0; r<15; r++)
{
// columns
for(c=0; c<15; c++)
{
var pixelcolor = palette[imageMap.charCodeAt((r*15)+c)-97];
if (pixelcolor != "transparent")
{
//create each pixel with the correct background
var pix = document.createElement("img");
pix.className = "starPixel";
pix.style.position = "absolute";
pix.border = 0;
pix.style.top = r + "px";
pix.style.left = c + "px";
pix.style.width = "1px";
pix.style.height = "1px";
pix.style.backgroundColor = pixelcolor;
pix.src = "data:image/gif,GIF89a%01%00%01%00%91%FF%00%FF%FF%FF%00%00%00%C0%C0%C0%00%00%00!%F9%04%01%00%00%02%00%2C%00%00%00%00%01%00%01%00%40%02%02T%01%00%3B";
box.appendChild(pix);
}
}
}
}
}
http://www.iasummit.org/proceedings/2008/inspiration_from_the_edge_new
Want a fresh perspective on UI design? Look around. Not at other web sites or desktop applications but at other interactive media. Tivo, the iPhone, the Wii software interface, the ‘Sugar’ OS for the XO Laptop… there’s a world of new UI inspiration that is already being proven out in other devices— yet much of what we see in application design is more of the same. Tabbed menus. Drop downs. Form fields. Sure, patterns and conventions are important. But is ‘familiar’ always better? What might be more natural? While years of usability studies assert that consistent UI elements are a critical requirement, we also know that people quickly adapt to new patterns of use, new game interfaces, and new hardware-specific interactions.
To increase our field of vision, we’ll take a macro view of interface design, focusing on alternative ~UIs— and emphasizing patterns that can be leveraged in a business context. What might World of Warcraft tell us about improving our business intelligence tool? How might Club Penguin, a virtual destination for young children, influence the information architecture of our new CRM tool? How might designing for the iPhone affect our desktop UI designs? These are the types of questions we’ll explore, along with how skills in abstraction and synthesis can open our eyes to see new opportunities all around us.
http://www.iasummit.org/proceedings/2008/integrating_web_analytics_into
Web statistics data provides quantitative information about what people do on a web site—24 hours a day, 7 days a week—but many organizations have still not instituted a process for analyzing this data. A web analytics program is essential to a strong user centered design practice, as analytics can inform and direct more qualitative user research methods and can provide quick feedback on site changes.
Following up on the 2007 IA Summit presentations on analytics, I will use real world examples of how I implemented analytics for our clients. I will provide attendees with an overview of how to get the most from the data they capture and how to use web analytics as a first step to improving a site’s user experience.
My presentation should be useful for anyone who doesn’t already use web analytics regularly. It will address:
* how to analyze statistics quickly and easily;
* what to look for in an analytics report and what to ignore;
* how to deal with not using cookies due to privacy concerns;
* how to present the data in a way that is understandable; and
* how to set the stage for additional, more qualitative, research.
/***
|''Name:''|IntelliTaggerPlugin|
|''Version:''|1.0.2 (2007-07-25)|
|''Type:''|plugin|
|''Source:''|http://tiddlywiki.abego-software.de/#IntelliTaggerPlugin|
|''Author:''|Udo Borkowski (ub [at] abego-software [dot] de)|
|''Documentation:''|[[IntelliTaggerPlugin Documentation]]|
|''~SourceCode:''|[[IntelliTaggerPlugin SourceCode]]|
|''Licence:''|[[BSD open source license (abego Software)]]|
|''~CoreVersion:''|2.0.8|
|''Browser:''|Firefox 1.5.0.2 or better|
***/
/***
!Version History
* 1.0.2 (2007-07-25):
** Feature: "Return" key may be used to accept first tag suggestion (beside "Alt-1")
** Bugfix: Keyboard shortcuts (Alt+3 etc.) shifted
* 1.0.1 (2007-05-18): Improvement: Speedup when using TiddlyWikis with many tags
* 1.0.0 (2006-04-26): Initial release
***/
// /%
if(!version.extensions.IntelliTaggerPlugin){if(!window.abego){window.abego={};}if(!abego.internal){abego.internal={};}abego.alertAndThrow=function(s){alert(s);throw s;};if(version.major<2){abego.alertAndThrow("Use TiddlyWiki 2.0.8 or better to run the IntelliTagger Plugin.");}version.extensions.IntelliTaggerPlugin={major:1,minor:0,revision:2,date:new Date(2007,6,25),type:"plugin",source:"http://tiddlywiki.abego-software.de/#IntelliTaggerPlugin",documentation:"[[IntelliTaggerPlugin Documentation]]",sourcecode:"[[IntelliTaggerPlugin SourceCode]]",author:"Udo Borkowski (ub [at] abego-software [dot] de)",licence:"[[BSD open source license (abego Software)]]",tiddlywiki:"Version 2.0.8 or better",browser:"Firefox 1.5.0.2 or better"};abego.createEllipsis=function(_2){var e=createTiddlyElement(_2,"span");e.innerHTML="…";};abego.isPopupOpen=function(_4){return _4&&_4.parentNode==document.body;};abego.openAsPopup=function(_5){if(_5.parentNode!=document.body){document.body.appendChild(_5);}};abego.closePopup=function(_6){if(abego.isPopupOpen(_6)){document.body.removeChild(_6);}};abego.getWindowRect=function(){return {left:findScrollX(),top:findScrollY(),height:findWindowHeight(),width:findWindowWidth()};};abego.moveElement=function(_7,_8,_9){_7.style.left=_8+"px";_7.style.top=_9+"px";};abego.centerOnWindow=function(_a){if(_a.style.position!="absolute"){throw "abego.centerOnWindow: element must have absolute position";}var _b=abego.getWindowRect();abego.moveElement(_a,_b.left+(_b.width-_a.offsetWidth)/2,_b.top+(_b.height-_a.offsetHeight)/2);};abego.isDescendantOrSelf=function(_c,e){while(e){if(_c==e){return true;}e=e.parentNode;}return false;};abego.toSet=function(_e){var _f={};for(var i=0;i<_e.length;i++){_f[_e[i]]=true;}return _f;};abego.filterStrings=function(_11,_12,_13){var _14=[];for(var i=0;i<_11.length&&(_13===undefined||_14.length<_13);i++){var s=_11[i];if(s.match(_12)){_14.push(s);}}return _14;};abego.arraysAreEqual=function(a,b){if(!a){return !b;}if(!b){return false;}var n=a.length;if(n!=b.length){return false;}for(var i=0;i<n;i++){if(a[i]!=b[i]){return false;}}return true;};abego.moveBelowAndClip=function(_1b,_1c){if(!_1c){return;}var _1d=findPosX(_1c);var _1e=findPosY(_1c);var _1f=_1c.offsetHeight;var _20=_1d;var _21=_1e+_1f;var _22=findWindowWidth();if(_22<_1b.offsetWidth){_1b.style.width=(_22-100)+"px";}var _23=_1b.offsetWidth;if(_20+_23>_22){_20=_22-_23-30;}if(_20<0){_20=0;}_1b.style.left=_20+"px";_1b.style.top=_21+"px";_1b.style.display="block";};abego.compareStrings=function(a,b){return (a==b)?0:(a<b)?-1:1;};abego.sortIgnoreCase=function(arr){var _27=[];var n=arr.length;for(var i=0;i<n;i++){var s=arr[i];_27.push([s.toString().toLowerCase(),s]);}_27.sort(function(a,b){return (a[0]==b[0])?0:(a[0]<b[0])?-1:1;});for(i=0;i<n;i++){arr[i]=_27[i][1];}};abego.getTiddlerField=function(_2d,_2e,_2f){var _30=document.getElementById(_2d.idPrefix+_2e);var e=null;if(_30!=null){var _32=_30.getElementsByTagName("*");for(var t=0;t<_32.length;t++){var c=_32[t];if(c.tagName.toLowerCase()=="input"||c.tagName.toLowerCase()=="textarea"){if(!e){e=c;}if(c.getAttribute("edit")==_2f){e=c;}}}}return e;};abego.setRange=function(_35,_36,end){if(_35.setSelectionRange){_35.setSelectionRange(_36,end);var max=0+_35.scrollHeight;var len=_35.textLength;var top=max*_36/len,bot=max*end/len;_35.scrollTop=Math.min(top,(bot+top-_35.clientHeight)/2);}else{if(_35.createTextRange!=undefined){var _3b=_35.createTextRange();_3b.collapse();_3b.moveEnd("character",end);_3b.moveStart("character",_36);_3b.select();}else{_35.select();}}};abego.internal.TagManager=function(){var _3c=null;var _3d=function(){if(_3c){return;}_3c={};store.forEachTiddler(function(_3e,_3f){for(var i=0;i<_3f.tags.length;i++){var tag=_3f.tags[i];var _42=_3c[tag];if(!_42){_42=_3c[tag]={count:0,tiddlers:{}};}_42.tiddlers[_3f.title]=true;_42.count+=1;}});};var _43=TiddlyWiki.prototype.saveTiddler;TiddlyWiki.prototype.saveTiddler=function(_44,_45,_46,_47,_48,_49){var _4a=this.fetchTiddler(_44);var _4b=_4a?_4a.tags:[];var _4c=(typeof _49=="string")?_49.readBracketedList():_49;_43.apply(this,arguments);if(!abego.arraysAreEqual(_4b,_4c)){abego.internal.getTagManager().reset();}};var _4d=TiddlyWiki.prototype.removeTiddler;TiddlyWiki.prototype.removeTiddler=function(_4e){var _4f=this.fetchTiddler(_4e);var _50=_4f&&_4f.tags.length>0;_4d.apply(this,arguments);if(_50){abego.internal.getTagManager().reset();}};this.reset=function(){_3c=null;};this.getTiddlersWithTag=function(tag){_3d();var _52=_3c[tag];return _52?_52.tiddlers:null;};this.getAllTags=function(_53){_3d();var _54=[];for(var i in _3c){_54.push(i);}for(i=0;_53&&i<_53.length;i++){_54.pushUnique(_53[i],true);}abego.sortIgnoreCase(_54);return _54;};this.getTagInfos=function(){_3d();var _56=[];for(var _57 in _3c){_56.push([_57,_3c[_57]]);}return _56;};var _58=function(a,b){var a1=a[1];var b1=b[1];var d=b[1].count-a[1].count;return d!=0?d:abego.compareStrings(a[0].toLowerCase(),b[0].toLowerCase());};this.getSortedTagInfos=function(){_3d();var _5e=this.getTagInfos();_5e.sort(_58);return _5e;};this.getPartnerRankedTags=function(_5f){var _60={};for(var i=0;i<_5f.length;i++){var _62=this.getTiddlersWithTag(_5f[i]);for(var _63 in _62){var _64=store.getTiddler(_63);if(!(_64 instanceof Tiddler)){continue;}for(var j=0;j<_64.tags.length;j++){var tag=_64.tags[j];var c=_60[tag];_60[tag]=c?c+1:1;}}}var _68=abego.toSet(_5f);var _69=[];for(var n in _60){if(!_68[n]){_69.push(n);}}_69.sort(function(a,b){var d=_60[b]-_60[a];return d!=0?d:abego.compareStrings(a.toLowerCase(),b.toLowerCase());});return _69;};};abego.internal.getTagManager=function(){if(!abego.internal.gTagManager){abego.internal.gTagManager=new abego.internal.TagManager();}return abego.internal.gTagManager;};(function(){var _6e=2;var _6f=1;var _70=30;var _71;var _72;var _73;var _74;var _75;var _76;if(!abego.IntelliTagger){abego.IntelliTagger={};}var _77=function(){return _72;};var _78=function(tag){return _75[tag];};var _7a=function(s){var i=s.lastIndexOf(" ");return (i>=0)?s.substr(0,i):"";};var _7d=function(_7e){var s=_7e.value;var len=s.length;return (len>0&&s[len-1]!=" ");};var _81=function(_82){var s=_82.value;var len=s.length;if(len>0&&s[len-1]!=" "){_82.value+=" ";}};var _85=function(tag,_87,_88){if(_7d(_87)){_87.value=_7a(_87.value);}story.setTiddlerTag(_88.title,tag,0);_81(_87);abego.IntelliTagger.assistTagging(_87,_88);};var _89=function(n){if(_76&&_76.length>n){return _76[n];}return (_74&&_74.length>n)?_74[n]:null;};var _8b=function(n,_8d,_8e){var _8f=_89(n);if(_8f){_85(_8f,_8d,_8e);}};var _90=function(_91){var pos=_91.value.lastIndexOf(" ");var _93=(pos>=0)?_91.value.substr(++pos,_91.value.length):_91.value;return new RegExp(_93.escapeRegExp(),"i");};var _94=function(_95,_96){var _97=0;for(var i=0;i<_95.length;i++){if(_96[_95[i]]){_97++;}}return _97;};var _99=function(_9a,_9b,_9c){var _9d=1;var c=_9a[_9b];for(var i=_9b+1;i<_9a.length;i++){if(_9a[i][1].count==c){if(_9a[i][0].match(_9c)){_9d++;}}else{break;}}return _9d;};var _a0=function(_a1,_a2){var _a3=abego.internal.getTagManager().getSortedTagInfos();var _a4=[];var _a5=0;for(var i=0;i<_a3.length;i++){var c=_a3[i][1].count;if(c!=_a5){if(_a2&&(_a4.length+_99(_a3,i,_a1)>_a2)){break;}_a5=c;}if(c==1){break;}var s=_a3[i][0];if(s.match(_a1)){_a4.push(s);}}return _a4;};var _a9=function(_aa,_ab){return abego.filterStrings(abego.internal.getTagManager().getAllTags(_ab),_aa);};var _ac=function(){if(!_71){return;}var _ad=store.getTiddlerText("IntelliTaggerMainTemplate");if(!_ad){_ad="<b>Tiddler IntelliTaggerMainTemplate not found</b>";}_71.innerHTML=_ad;applyHtmlMacros(_71,null);refreshElements(_71,null);};var _ae=function(e){if(!e){var e=window.event;}var tag=this.getAttribute("tag");if(_73){_73.call(this,tag,e);}return false;};var _b2=function(_b3){createTiddlyElement(_b3,"span",null,"tagSeparator"," | ");};var _b4=function(_b5,_b6,_b7,_b8,_b9){if(!_b6){return;}var _ba=_b8?abego.toSet(_b8):{};var n=_b6.length;var c=0;for(var i=0;i<n;i++){var tag=_b6[i];if(_ba[tag]){continue;}if(c>0){_b2(_b5);}if(_b9&&c>=_b9){abego.createEllipsis(_b5);break;}c++;var _bf="";var _c0=_b5;if(_b7<10){_c0=createTiddlyElement(_b5,"span",null,"numberedSuggestion");_b7++;var key=_b7<10?""+(_b7):"0";createTiddlyElement(_c0,"span",null,"suggestionNumber",key+") ");var _c2=_b7==1?"Return or ":"";_bf=" (Shortcut: %1Alt-%0)".format([key,_c2]);}var _c3=config.views.wikified.tag.tooltip.format([tag]);var _c4=(_78(tag)?"Remove tag '%0'%1":"Add tag '%0'%1").format([tag,_bf]);var _c5="%0; Shift-Click: %1".format([_c4,_c3]);var btn=createTiddlyButton(_c0,tag,_c5,_ae,_78(tag)?"currentTag":null);btn.setAttribute("tag",tag);}};var _c7=function(){if(_71){window.scrollTo(0,ensureVisible(_71));}if(_77()){window.scrollTo(0,ensureVisible(_77()));}};var _c8=function(e){if(!e){var e=window.event;}if(!_71){return;}var _cb=resolveTarget(e);if(_cb==_77()){return;}if(abego.isDescendantOrSelf(_71,_cb)){return;}abego.IntelliTagger.close();};addEvent(document,"click",_c8);var _cc=Story.prototype.gatherSaveFields;Story.prototype.gatherSaveFields=function(e,_ce){_cc.apply(this,arguments);var _cf=_ce.tags;if(_cf){_ce.tags=_cf.trim();}};var _d0=function(_d1){story.focusTiddler(_d1,"tags");var _d2=abego.getTiddlerField(story,_d1,"tags");if(_d2){var len=_d2.value.length;abego.setRange(_d2,len,len);window.scrollTo(0,ensureVisible(_d2));}};var _d4=config.macros.edit.handler;config.macros.edit.handler=function(_d5,_d6,_d7,_d8,_d9,_da){_d4.apply(this,arguments);var _db=_d7[0];if((_da instanceof Tiddler)&&_db=="tags"){var _dc=_d5.lastChild;_dc.onfocus=function(e){abego.IntelliTagger.assistTagging(_dc,_da);setTimeout(function(){_d0(_da.title);},100);};_dc.onkeyup=function(e){if(!e){var e=window.event;}if(e.altKey&&!e.ctrlKey&&!e.metaKey&&(e.keyCode>=48&&e.keyCode<=57)){_8b(e.keyCode==48?9:e.keyCode-49,_dc,_da);}else{if(e.ctrlKey&&e.keyCode==32){_8b(0,_dc,_da);}}if(!e.ctrlKey&&(e.keyCode==13||e.keyCode==10)){_8b(0,_dc,_da);}setTimeout(function(){abego.IntelliTagger.assistTagging(_dc,_da);},100);return false;};_81(_dc);}};var _e0=function(e){if(!e){var e=window.event;}var _e3=resolveTarget(e);var _e4=_e3.getAttribute("tiddler");if(_e4){story.displayTiddler(_e3,_e4,"IntelliTaggerEditTagsTemplate",false);_d0(_e4);}return false;};var _e5=config.macros.tags.handler;config.macros.tags.handler=function(_e6,_e7,_e8,_e9,_ea,_eb){_e5.apply(this,arguments);abego.IntelliTagger.createEditTagsButton(_eb,createTiddlyElement(_e6.lastChild,"li"));};var _ec=function(){if(_71&&_72&&!abego.isDescendantOrSelf(document,_72)){abego.IntelliTagger.close();}};setInterval(_ec,100);abego.IntelliTagger.displayTagSuggestions=function(_ed,_ee,_ef,_f0,_f1){_74=_ed;_75=abego.toSet(_ee);_76=_ef;_72=_f0;_73=_f1;if(!_71){_71=createTiddlyElement(document.body,"div",null,"intelliTaggerSuggestions");_71.style.position="absolute";}_ac();abego.openAsPopup(_71);if(_77()){var w=_77().offsetWidth;if(_71.offsetWidth<w){_71.style.width=(w-2*(_6e+_6f))+"px";}abego.moveBelowAndClip(_71,_77());}else{abego.centerOnWindow(_71);}_c7();};abego.IntelliTagger.assistTagging=function(_f3,_f4){var _f5=_90(_f3);var s=_f3.value;if(_7d(_f3)){s=_7a(s);}var _f7=s.readBracketedList();var _f8=_f7.length>0?abego.filterStrings(abego.internal.getTagManager().getPartnerRankedTags(_f7),_f5,_70):_a0(_f5,_70);abego.IntelliTagger.displayTagSuggestions(_a9(_f5,_f7),_f7,_f8,_f3,function(tag,e){if(e.shiftKey){onClickTag.call(this,e);}else{_85(tag,_f3,_f4);}});};abego.IntelliTagger.close=function(){abego.closePopup(_71);_71=null;return false;};abego.IntelliTagger.createEditTagsButton=function(_fb,_fc,_fd,_fe,_ff,id,_101){if(!_fd){_fd="[edit]";}if(!_fe){_fe="Edit the tags";}if(!_ff){_ff="editTags";}var _102=createTiddlyButton(_fc,_fd,_fe,_e0,_ff,id,_101);_102.setAttribute("tiddler",(_fb instanceof Tiddler)?_fb.title:String(_fb));return _102;};abego.IntelliTagger.getSuggestionTagsMaxCount=function(){return 100;};config.macros.intelliTagger={label:"intelliTagger",handler:function(_103,_104,_105,_106,_107,_108){var _109=_107.parseParams("list",null,true);var _10a=_109[0]["action"];for(var i=0;_10a&&i<_10a.length;i++){var _10c=_10a[i];var _10d=config.macros.intelliTagger.subhandlers[_10c];if(!_10d){abego.alertAndThrow("Unsupported action '%0'".format([_10c]));}_10d(_103,_104,_105,_106,_107,_108);}},subhandlers:{showTags:function(_10e,_10f,_110,_111,_112,_113){_b4(_10e,_74,_76?_76.length:0,_76,abego.IntelliTagger.getSuggestionTagsMaxCount());},showFavorites:function(_114,_115,_116,_117,_118,_119){_b4(_114,_76,0);},closeButton:function(_11a,_11b,_11c,_11d,_11e,_11f){var _120=createTiddlyButton(_11a,"close","Close the suggestions",abego.IntelliTagger.close);},version:function(_121){var t="IntelliTagger %0.%1.%2".format([version.extensions.IntelliTaggerPlugin.major,version.extensions.IntelliTaggerPlugin.minor,version.extensions.IntelliTaggerPlugin.revision]);var e=createTiddlyElement(_121,"a");e.setAttribute("href","http://tiddlywiki.abego-software.de/#IntelliTaggerPlugin");e.innerHTML="<font color=\"black\" face=\"Arial, Helvetica, sans-serif\">"+t+"<font>";},copyright:function(_124){var e=createTiddlyElement(_124,"a");e.setAttribute("href","http://tiddlywiki.abego-software.de");e.innerHTML="<font color=\"black\" face=\"Arial, Helvetica, sans-serif\">© 2006-2007 <b><font color=\"red\">abego</font></b> Software<font>";}}};})();config.shadowTiddlers["IntelliTaggerStyleSheet"]="/***\n"+"!~IntelliTagger Stylesheet\n"+"***/\n"+"/*{{{*/\n"+".intelliTaggerSuggestions {\n"+"\tposition: absolute;\n"+"\twidth: 600px;\n"+"\n"+"\tpadding: 2px;\n"+"\tlist-style: none;\n"+"\tmargin: 0;\n"+"\n"+"\tbackground: #eeeeee;\n"+"\tborder: 1px solid DarkGray;\n"+"}\n"+"\n"+".intelliTaggerSuggestions .currentTag {\n"+"\tfont-weight: bold;\n"+"}\n"+"\n"+".intelliTaggerSuggestions .suggestionNumber {\n"+"\tcolor: #808080;\n"+"}\n"+"\n"+".intelliTaggerSuggestions .numberedSuggestion{\n"+"\twhite-space: nowrap;\n"+"}\n"+"\n"+".intelliTaggerSuggestions .intelliTaggerFooter {\n"+"\tmargin-top: 4px;\n"+"\tborder-top-width: thin;\n"+"\tborder-top-style: solid;\n"+"\tborder-top-color: #999999;\n"+"}\n"+".intelliTaggerSuggestions .favorites {\n"+"\tborder-bottom-width: thin;\n"+"\tborder-bottom-style: solid;\n"+"\tborder-bottom-color: #999999;\n"+"\tpadding-bottom: 2px;\n"+"}\n"+"\n"+".intelliTaggerSuggestions .normalTags {\n"+"\tpadding-top: 2px;\n"+"}\n"+"\n"+".intelliTaggerSuggestions .intelliTaggerFooter .button {\n"+"\tfont-size: 10px;\n"+"\n"+"\tpadding-left: 0.3em;\n"+"\tpadding-right: 0.3em;\n"+"}\n"+"\n"+"/*}}}*/\n";config.shadowTiddlers["IntelliTaggerMainTemplate"]="<!--\n"+"{{{\n"+"-->\n"+"<div class=\"favorites\" macro=\"intelliTagger action: showFavorites\"></div>\n"+"<div class=\"normalTags\" macro=\"intelliTagger action: showTags\"></div>\n"+"<!-- The Footer (with the Navigation) ============================================ -->\n"+"<table class=\"intelliTaggerFooter\" border=\"0\" width=\"100%\" cellspacing=\"0\" cellpadding=\"0\"><tbody>\n"+" <tr>\n"+"\t<td align=\"left\">\n"+"\t\t<span macro=\"intelliTagger action: closeButton\"></span>\n"+"\t</td>\n"+"\t<td align=\"right\">\n"+"\t\t<span macro=\"intelliTagger action: version\"></span>, <span macro=\"intelliTagger action: copyright \"></span>\n"+"\t</td>\n"+" </tr>\n"+"</tbody></table>\n"+"<!--\n"+"}}}\n"+"-->\n";config.shadowTiddlers["IntelliTaggerEditTagsTemplate"]="<!--\n"+"{{{\n"+"-->\n"+"<div class='toolbar' macro='toolbar +saveTiddler -cancelTiddler'></div>\n"+"<div class='title' macro='view title'></div>\n"+"<div class='tagged' macro='tags'></div>\n"+"<div class='viewer' macro='view text wikified'></div>\n"+"<div class='toolbar' macro='toolbar +saveTiddler -cancelTiddler'></div>\n"+"<div class='editor' macro='edit tags'></div><div class='editorFooter'><span macro='message views.editor.tagPrompt'></span><span macro='tagChooser'></span></div>\n"+"<!--\n"+"}}}\n"+"-->\n";config.shadowTiddlers["BSD open source license (abego Software)"]="See [[Licence|http://tiddlywiki.abego-software.de/#%5B%5BBSD%20open%20source%20license%5D%5D]].";config.shadowTiddlers["IntelliTaggerPlugin Documentation"]="[[Documentation on abego Software website|http://tiddlywiki.abego-software.de/doc/IntelliTagger.pdf]].";config.shadowTiddlers["IntelliTaggerPlugin SourceCode"]="[[Plugin source code on abego Software website|http://tiddlywiki.abego-software.de/archive/IntelliTaggerPlugin/Plugin-IntelliTagger-src.1.0.2.js]]\n";(function(){var _126=restart;restart=function(){setStylesheet(store.getTiddlerText("IntelliTaggerStyleSheet"),"IntelliTaggerStyleSheet");_126.apply(this,arguments);};})();}
// %/
Jackson Fox leads a double life, working as a UX Designer for Lulu.com in Raleigh, NC by day, and pursuing his ~PhD in Information Science at UNC Chapel Hill by night.
Jacob Alonzo is anticipating receiving his master’s degree in Information Architecture, from Kent State University’s IAKM program May of 2008. Jacob is currently a graduate assistant with Kent State’s ~ScanPath Usability Lab. Jacob hold’s a BA in American Studies from Rutgers, the State University of New Jersey.
Jacob is hoping to be employed, after graduation, as an Information Architect or Usability Experience Designer. So if you have an opportunity, then I am your man!
James Robertson heads Step Two Designs, a vendor-neutral consultancy based in Sydney, Australia. James became known as the ‘intranet guy’ at the IA Summit in Vancouver, and is a globally-recognised expert on intranet strategy, content management and enterprise IA.
James has keynoted or presented conferences and workshops throughout Australia, as well as in New Zealand, Singapore, Malaysia, Brunei, Denmark, the Netherlands, Canada, the UK and the US.
Janna Korzenko is a doctoral student in Public Policy, and Program Coordinator for IAKM.
A software developer and programmer, Jared founded User Interface Engineering in 1988. He has more than 15 years of experience conducting usability evaluations on a variety of products, and is an expert in low-fidelity prototyping techniques.
Jared is on the faculty of the Tufts University Gordon Institute and teaches seminars on product usability. He is a member of SIGCHI, the Usability Professionals Association, the Association for Computing Machinery, and the IEEE. Jared is a recognized authority on user interface design and human factors in computing. He is a regular tutorial speaker at the annual CHI conference and Society for Technical Communications conferences around the country.
Jason Hobbs lives in Johannesburg and runs jh-01, a user experience design company. The company divides its time between arts and culture, non-profit and commercial projects. He has been researching Internet Cafés and their role in people’s lives in developing contexts for the past three years.
Jason advises to the board of the IA Institute, is a local ambassador for ~UXnet and runs the SA UX Forum.
Jason Holmes is an Assistant Professor in SLIS at Kent State University. His research interests include website usability testing.
Jed is an interaction designer and entrepreneur. He bridges the gap between design and programming through a deep respect and talent for both. Using tools like Adobe Flash, he creates rapid prototypes and functional applications that combine data sources with interactive interfaces. Most recently he worked on the Bose Media System, which debuted in the Ferrari 612 Scaglietti. Jed holds a Master's degree from the Institute of Design, where he now serves as adjunct faculty member.
Jess has been working in design and user experience since 1997. He specializes in helping clients work with multiple stakeholders to bridge competing viewpoints, align project vision, and create a clear understanding of the problems at hand. His value-centered approach grounds strategy at the intersection of business goals and customer needs – the sweet spot that produces sustainable value and real innovation.
Jess regularly writes and speaks at conferences about user experience, design thinking, and innovation. His work with the design and user experience community is focused on helping practitioners increase their influence in the organizations they work with.
Joe Lamantia is a veteran consultant, architect, and thought leader in the international user experience community. An author and frequent speaker on design, information architecture, business, and enterprise technology, Joe is also the creator of the leading freely available tool for card sort analysis.
Joe is currently based in New York, working as a user experience and strategy consultant for the enterprise architecture group of a global IT firm. He blogs regularly at www.joelamantia.com
Joe has more than 17 years of experience in user experience-related fields. He has concentrated on crafting excellent user experiences, using information architecture, interaction design, writing, and user research. At Keane, Joe acts as an advocate for user experience consulting: Information architecture, user research, interaction design, and usability evaluation along with visual design and Web design. He leads a team of information architects, visual designers, and interactive developers, mentoring them in competency skills along with general business consulting practices. In addiion, he evangelizes best practices in UX among both internal and external clients. Previously he held UX-oriented positions in Hamburg, Germany; Richmond, VA; Chicago, IL; and Durham, NC. He's also been a soldier, a cook, a radio DJ, a road manager, a teacher, and a reporter once upon a time.
John has worked in information architecture for 9 years, designing interfaces for websites, desktop applications, and web-based video games. He currently serves as the lead user behavior specialist in his role as a senior IA with Vanguard.
Before entering the professional world, John earned a BA and an MA in communications. His graduate degree was paid in part through a fellowship coaching speech & debate, so he'll welcome contrary arguments from anyone attending his presentation.
John’s professional loves include search engines and quantitative log file analysis, but his heart belongs to his wife Amanda. He lives in the Philadelphia suburbs and blogs at worldwideintertubes.com.
Jørgen Dalen works for the Norwegian company, Halogen, as an Information Architect. He specializes in the optimization of user experience in digital media. Dalen is a Product Designer and holds an MA in psychology.
Josh Damon Williams is a user experience designer at Hot Studio, Inc., where he has worked on a diverse range of projects with clients such as eBay and Architecture for Humanity.
Karen Loasby is the Information Architecture Team Leader at the BBC in London. She has been at the BBC for six years and previously worked for the Guardian newspaper. In her role at the BBC she has championed entry-level roles, set up a work experience scheme, and managed 16 junior ~IAs. Ex-juniors now form the majority of the BBC IA team.
Karl Johan Saeth is a senior Information Architect with Logica´s UX unit in Oslo, Norway. Even though he loves fishing Karl Johan has spent most of the last 12 years developing IA and interactive concepts.
Keith ~DuFresne is the Art Director at ~EightShapes, LLC, a user experience consulting firm based in Washington, DC. Keith has been designing online experiences since 1996 and is interested in interaction design and the emotional connection customers establish with brands.
Prior to ~EightShapes, Keith led the visual design efforts for Sprint Nextel and Revolution Health. He has also helped Via Spiga, Timberland, Cole Haan, Dick's Sporting Goods, and Liz Claiborne translate their retail stores into compelling online destinations.
http://www.iasummit.org/proceedings/2008/keynote_journey_to_the_center
User-centered design was born in the 1980s, amidst a world filled with frustration with blinking VCR clocks and computer command lines. Up until this time, developers focused on making the devices work, giving little heed to how they'd be used. Terms like "user friendly" and "easy to use," buzzwords for the UCD movement, soon became as common as "new and improved" on laundry soap.
Fast forward 25 years and it now seems the foundations of user- centered design are now disintegrating. Notable community members are suggesting UCD practice is burdensome and returns little value. There's a growing sentiment that spending limited resources on user research takes away from essential design activities. Previously fundamental techniques, such as usability testing and persona development, are now regularly under attack. And let's not forget that today's shining stars, such as Google, Facebook, Twitter, and the iPod, came to their success without UCD practices.
Is it time for user-centered design to evolve into something else? Or is there something else happening in our world of experience design that makes UCD obsolete? Should something else occupy the center of design?
These are just the questions that this year's keynote presenter, Jared Spool, likes to answer. Especially after a few drinks. And while a Saturday morning keynote may seem early for the kind of heavy drinking these particular questions demand, Jared will have just arrived from Italy, a nation with a long tradition of philosophical intoxication. This will set the perfect stage for an entertaining and insightful presentation to open our conference.
We guarantee a journey that shouldn't be missed.
Kristen Johansen has been a user experience and design practitioner for over ten years, holding positions as a user experience designer, usability specialist, and UX manager. She is currently the Senior Manager of User Experience at Citrix Online, and currently leads the user experience team responsible for the award-winning ~GoToMyPC, ~GoToAssist and ~GoToMeeting products. Previously, Kristen was the Manager of Interaction Design & Usability at Move, Inc., where she built a UX team from scratch.
Kyungsun Park is a doctoral student majoring in Educational Technology, Department of Education, Seoul National University, Seoul, Korea. Her current research is about e-learning usability.
Larry Hannigan is a User Experience Research Usability Lab Manager at eBay. Larry is responsible for coordinating user research lab studies, recruiting and video capture.
Leah Buley is an experience designer at Adaptive Path. She enjoys making products that are useful, intuitive, and delightful -- and has a related interest in the tools and methodologies that make that possible. She has worked with organizations in a variety of industries, including financial, legal, telecom, social networking, and non-profit. Before Adaptive Path, Leah was a user interface designer for Barclays Global Investors, where she was a proud user experience team of one.
Lee Iverson is an assistant professor in the department of Electrical and Computer Engineering at the University of British Columbia. His main areas of research cover socio-technical systems, privacy and social information management, digital libraries and museums.
/***
|''Name:''|LegacyStrikeThroughPlugin|
|''Description:''|Support for legacy (pre 2.1) strike through formatting|
|''Version:''|1.0.2|
|''Date:''|Jul 21, 2006|
|''Source:''|http://www.tiddlywiki.com/#LegacyStrikeThroughPlugin|
|''Author:''|MartinBudden (mjbudden (at) gmail (dot) com)|
|''License:''|[[BSD open source license]]|
|''CoreVersion:''|2.1.0|
***/
//{{{
// Ensure that the LegacyStrikeThrough Plugin is only installed once.
if(!version.extensions.LegacyStrikeThroughPlugin) {
version.extensions.LegacyStrikeThroughPlugin = {installed:true};
config.formatters.push(
{
name: "legacyStrikeByChar",
match: "==",
termRegExp: /(==)/mg,
element: "strike",
handler: config.formatterHelpers.createElementAndWikify
});
} //# end of "install only once"
//}}}
Lucas Pettinati is a Senior Interaction Designer at Yahoo! and leads design efforts for the Yahoo! User Interface Library. Since joining Yahoo! in 2004 he has designed several YUI widgets, was responsible for Yahoo's all new user registration process and the redesigned Yahoo! Personals site. Before learning to yodel, Lucas designed products for American Express, Sabre Holdings, and BMC Software. He holds a BA in Architecture from the University of California at Berkeley and sits on the industry advisory board for the Georgia Institute of Technology’s HCI Master’s program.
Luke Wroblewski is an internationally recognized Web thought leader who has designed or contributed to software used every day by more than 750 million people. He is currently Senior Principal of Product Ideation & Design at Yahoo! Inc. and Founder of ~LukeW Interface Designs, a product strategy and design consultancy.
Luke also publishes "Functioning Form," a leading online publication for interaction designers. He has authored two books on Web interface design principles “Web Form Design Best Practices” and "~Site-Seeing: A Visual Approach to Web Usability". Luke is consistently a top-rated speaker at various conferences and companies around the world.
Lynn Boyden trained as a librarian but has not worked in a library since she was seventeen. She teaches information architecture in the UCLA library school, and has practiced for agencies, institutions, and corporations. She is published widely, most recently on the subject of information architecture as a career choice. She is an OG Instigator for the IA slam, and has presented a slam at the IA Summit each year since 2004. She is a loving mother to Trixie and Mojo and lives with them, five fish, and her adored husband in Los Angeles.
[[Thursday]]
[[Friday]]
[[Saturday]]
[[Sunday]]
[[Monday]]
[[My Schedule]]
http://www.iasummit.org/proceedings/2008/making_the_leap_from_practitio
Are you yearning to make the leap from Practitioner to Manger but aren’t quite sure how to achieve that promotion? Have you recently started a management position where you’re suddenly faced with personnel challenges you never thought would be part of your job? As a seasoned manager with a decade of experience managing teams as both an “innie” in large companies and an “outie” as a consultant, I will offer techniques for moving into management and maturing as a manager that I’ve honed in the trenches.
This talk will cover which skills (both expected and unexpected) will be most valuable, gory details about the mistakes I’ve made and how to avoid them (names will be changed to protect the innocent), and suggestions for keeping your sanity as you leave behind the comfortable identity of practitioner and forge a new identity as a manager of user experience professionals.
Margaret Hanley is the Head of Consultancy at Web Technology Group in the UK. She has worked as a User Experience lead and manager over the last eight years in companies ranging from Yellow Pages in Australia and Argus Associates in the US; to Information Architecture Team Leader and Executive Producer at the BBC in the UK and Head of User Experience of DNA, a division of Avenue A| Razorfish. Throughout her time as a manager she has managed teams as large as 50 and as small as three. Her credo is to learn from as many situations as possible especially from your mistakes.
Martin Belam is an independent internet consultant and author, with 8 years experience working with global brands including Sony, Vodafone and the BBC. Martin specialised in search analytics at the BBC, and has since worked in areas such as online news, personalised email broadcast solutions, and the user experience definition for online and mobile retail. Originally from London in the UK, he is now based on the Greek island of Crete. Martin blogs at http://www.currybet.net
Maryam Najafian Razavi is a Ph.D. Candidate in the Department of Electrical and Computer Engineering at the University of British Columbia. Her current research focus is creating usable privacy management support for sharing personal information in a social context.
Matthew Fetchko is currently Vice President of Interactive Marketing for the Retail Division of ~AllianceBernstein, an asset management firm. His team is responsible for the international and domestic retail Web properties and online applications. Looking back, he has worked with a number of interesting and crazy clients, covering areas from financial services to online communities. Matthew earned his undergraduate degree in visual communications from the George Washington University and a MPS in interactive telecommunications from New York University. He currently lives in New York City.
Matthew Hodgson is a senior consultant with SMS Management & Technology in Canberra, Australia, and is their Regional-lead for Web and Information Management. Matthew has over 10 years experience in e-business, information architecture, information and knowledge management, and has recently added social-computing strategy to his portfolio. This expertise is underpinned by a comprehensive applied-knowledge of web and information standards, degrees in organisational psychology and knowledge management, and a passion for technology and social change.
As Director of Insight and Planning with Critical Mass in Toronto, Canada, Matthew leads a team of information architects, design researchers, web analytics specialists and experience planners who collectively mold business strategy and design thinking into all types of interactive experiences.
Matthew has a Masters degree in Information Architecture and when he's not trying to reframe information architects as strategy wonks, he moonlights as a course director at York University in Toronto.
Matthew is a member of the Information Architecture Institute and co-founder of the infamous UX Irregulars, a Toronto area user experience group.
There is no widely accepted means of evaluating category systems for information search and browsing. The key to evaluation is provision of specific feedback. This presentation outlines an evaluation scheme and an evaluation method that combine the best features of intrinsic and extrinsic, automatic and empirical evaluations. The scheme delineates features broadly classified under comprehensiveness, coherence, and correctness. The study method given requires minimal resources and effort, is easily done remotely, and is easily modified. The method evaluates the category system through an interactive survey distributed among subject domain experts. Inferences are then drawn about the method of generating the system. This study technique is but one possible application of the scheme. The overall approach finds the over- and under-sensitivities of the method of generating the system. A case study has demonstrated the usefulness of the method, and inter-rater reliability in the data suggests that the evaluation scheme is meaningful.
Melissa currently manages the user experience discipline for Hotwire, an Expedia-owned discount travel website. With 10 years of industry experience, Melissa has led information architecture, interaction design and product strategy efforts to deliver successful user experiences that drive business results.
Her most recent clients include: Royal Caribbean, American Legacy Foundation (Truth), Children’s Hospital Boston, Fidelity Investments, Timberland, Lycos, and SAP, among others.
Melissa studied Human Computer Interaction and Psychology at Stanford University.
Michael J. Albers is an Associate Fellow in STC. He currently is an associate professor at East Carolina University, in the professional writing program. He previously taught at the University of Memphis. In 1999, he completed his ~PhD in technical communication and rhetoric from Texas Tech University. His research interests include designing documentation focused on answering real-world questions and online presentation of complex information.
Michael Magoolaghan is an Information Architect with the Vanguard Group. Before coming to Vanguard Michael served as the Business Information & Innovation Architect for the Board of Pensions of the Presbyterian Church in Philadelphia, where he co-designed the company’s intranet site and managed its digital library and search engines. Michael presented “A ‘Spirit of Simplicity’: What Information Architects Can Learn from the Arts & Crafts Movement” at the 2003 IA Summit.
Michael Morgan has worked in the industry since May 2000 and manages a User Experience Research group for eBay that focuses on Search and eBay Motors.
Michelle Watson is a Lead Information Architect at Digitas based in the UK. She has worked as an Information Architect in London over the last 6 years. At Wheel she specialised in e-commerce and online retail, working for clients ranging from Marks and Spencer to H Samuel and Laura Ashley. At Victoria Real she was able to look at usability beyond web build and was able to apply her analytical skills to a number of other digital mediums such as mobile pilots, online games and video streaming. At DNA Michelle became a team leader and became increasingly more involved in the technical side of information architecture. At Digitas Michelle has spent the last year flexing all of her IA muscles as she works on the substantial global redesign of a blue chip company.
Miles Rochford is a Design Specialist at Nokia Design, based in London, England.
He has been an information architect and user experience specialist for more than six years, working on a range of projects for government, non-profit, corporate and startup clients based in the United States, Europe and Australia.
He has experience in a range of different areas, including interaction design, spatial data, health informatics, social networking, media sharing, mobile devices, and service delivery.
| | ![[Flagler / Monroe]] | ![[Brickell]] | ![[Tuttle]] | ![[Flex: Orchid C/D]] |
| [[8:30 - 9:15AM|08:30 - 9:15AM]] | [[Why Markets Love the Internet (Or, The 1 Hour MBA for User Experience Designers and Other Layabouts)]] | [[Storytelling - a compelling design tool]] | [[Embodying IA: Incorporating library 2.0 and experience integration concepts in a small public library renovation]] | [[Repeat: Search Patterns]] |
| [[9:15 - 9:30AM|09:15 - 9:30AM]] |>|>|>| Break |
| [[9:30 - 10:15AM|09:30 - 10:15AM]] | [[Designing for the social: Avoiding anti-social networks]] | [[Putting multiple user centered design techniques in combination to create one global information system]] | [[Audiences & artifacts]] | [[How to set up and run participatory design sessions, analyze data and present results effectively]] |
| [[10:15 - 10:45AM]] |>|>| Morning tea |~|
| [[10:45 - 11:30AM]] | [[Becoming an IA/UX coach: Proving success one champion at a time]] | [[Data driven design research personas]] | [[Good news on your cell phone: Optimizing the user experience]] |~|
| [[11:30 - 11:45AM]] |>|>|>| Break |
| [[11:45 - 12:30PM]] | [[Designing with patterns in the real world: Lessons from Yahoo! And Comcast]] | [[IA for tiny stuff: Exploring widgets and gadgets]] | [[Information horizons: Proposing an alternate approach to assessing website architecture]] | |
| [[12:30 - 2:00PM]] |>|>|>| Lunch |
| [[2:00 - 2:45PM]] | [[What are your users REALLY thinking? An objective way to uncover the subjective]] | [[Re-experiencing information: Dealing with user-submitted data]] | [[Checking the feel of your UI with an interaction audit]] | |
| [[2:45 - 3:00PM]] |>|>|>| Break |
| [[3:00 - 4:00PM]] |>|>|>| [[Closing Plenary: Linkosophy]] |
| [[4:00 - 4:45PM]] |>|>|>| 5-minute madness (open mic) |
| [[4:45 - 4:45PM]] |>|>|>| Conference close |
!Saturday
<<forEachTiddler
where
'tiddler.tags.contains("session") && tiddler.tags.contains("favorite") && tiddler.tags.contains("Saturday")'
sortBy
'getType(tiddler, "time", false)+"###"+tiddler.title'
script
'function getType(tiddler, tagtype, linkify)
{
var result = "";
var tiddlertags = tiddler.tags;
if (!tiddlertags) return "";
tiddlertags.sort();
for (var i = 0; i < tiddlertags.length;i++)
{
var tags = store.getValue(store.getTiddler(tiddlertags[i]),"tags");
if (!tags) tags="";
var list=tags.split(" ");
if (list.length > 0)
{
for (l=0;l<=list.length-1;l++)
{
if (list[l] == tagtype)
{
if (linkify)
{
result = result + "\n*[[" + tiddlertags[i] + "]]";
}
else
{
result = result + " " + tiddlertags[i];
}
}
}
}
}
return result;
}
function getGroupTitle(tiddler, context)
{
if (context.lastGroup == getType(tiddler, "time", false))
{
context.lastGroup = getType(tiddler, "time", false);
return "@@color:red;"+(context.lastGroup?context.lastGroup:"no tags")+"@@ in "+getType(tiddler, "location", false)+"\n";
}
else
{
context.lastGroup = getType(tiddler, "time", false);
return ""+(context.lastGroup?context.lastGroup:"no tags")+" in "+getType(tiddler, "location", false)+"\n";
}
} '
write
'"!!"+getGroupTitle(tiddler, context)+" [[" + tiddler.title+"]]" + getType(tiddler, "speaker", true) + "\n"'
>>
!Sunday
<<forEachTiddler
where
'tiddler.tags.contains("session") && tiddler.tags.contains("favorite") && tiddler.tags.contains("Sunday")'
sortBy
'getType(tiddler, "time", false)+"###"+tiddler.title'
script
'function getType(tiddler, tagtype, linkify)
{
var result = "";
var tiddlertags = tiddler.tags;
if (!tiddlertags) return "";
tiddlertags.sort();
for (var i = 0; i < tiddlertags.length;i++)
{
var tags = store.getValue(store.getTiddler(tiddlertags[i]),"tags");
if (!tags) tags="";
var list=tags.split(" ");
if (list.length > 0)
{
for (l=0;l<=list.length-1;l++)
{
if (list[l] == tagtype)
{
if (linkify)
{
result = result + "\n*[[" + tiddlertags[i] + "]]";
}
else
{
result = result + " " + tiddlertags[i];
}
}
}
}
}
return result;
}
function getGroupTitle(tiddler, context)
{
if (context.lastGroup == getType(tiddler, "time", false))
{
context.lastGroup = getType(tiddler, "time", false);
return "@@color:red;"+(context.lastGroup?context.lastGroup:"no tags")+"@@ in "+getType(tiddler, "location", false)+"\n";
}
else
{
context.lastGroup = getType(tiddler, "time", false);
return ""+(context.lastGroup?context.lastGroup:"no tags")+" in "+getType(tiddler, "location", false)+"\n";
}
} '
write
'"!!"+getGroupTitle(tiddler, context)+" [[" + tiddler.title+"]]" + getType(tiddler, "speaker", true) + "\n"'
>>
!Monday
<<forEachTiddler
where
'tiddler.tags.contains("session") && tiddler.tags.contains("favorite") && tiddler.tags.contains("Monday")'
sortBy
'getType(tiddler, "time", false)+"###"+tiddler.title'
script
'function getType(tiddler, tagtype, linkify)
{
var result = "";
var tiddlertags = tiddler.tags;
if (!tiddlertags) return "";
tiddlertags.sort();
for (var i = 0; i < tiddlertags.length;i++)
{
var tags = store.getValue(store.getTiddler(tiddlertags[i]),"tags");
if (!tags) tags="";
var list=tags.split(" ");
if (list.length > 0)
{
for (l=0;l<=list.length-1;l++)
{
if (list[l] == tagtype)
{
if (linkify)
{
result = result + "\n*[[" + tiddlertags[i] + "]]";
}
else
{
result = result + " " + tiddlertags[i];
}
}
}
}
}
return result;
}
function getGroupTitle(tiddler, context)
{
if (context.lastGroup == getType(tiddler, "time", false))
{
context.lastGroup = getType(tiddler, "time", false);
return "@@color:red;"+(context.lastGroup?context.lastGroup:"no tags")+"@@ in "+getType(tiddler, "location", false)+"\n";
}
else
{
context.lastGroup = getType(tiddler, "time", false);
return ""+(context.lastGroup?context.lastGroup:"no tags")+" in "+getType(tiddler, "location", false)+"\n";
}
} '
write
'"!!"+getGroupTitle(tiddler, context)+" [[" + tiddler.title+"]]" + getType(tiddler, "speaker", true) + "\n"'
>>
<<autoRefresh>>
Nathan Curtis is a founder and principal at ~EightShapes, LLC, a UX consulting firm based in Washington, DC. His interests include information architecture, interaction design, and documentation systems for design and deliverables. He has recently created systems and conducted workshops for clients including Comcast, Sun, Discovery, Sprint, Cisco, and Marriott. Nathan also enjoys discovering the potential of many IA software, including Visio, ~InDesign and Illustrator and blogs on design and documentation at www.nathancurtis.com.
Olly Wright is Experience Architecture Director at Media Catalyst Amsterdam, where he is responsible for a wide range of web and mobile projects, including sonyericsson.com. Previously he obtained a degree in philosophy in London, where he was told that Darwin has nothing to do with ethics. He disagrees. He blogs at ollywright.org
These InterfaceOptions for customising TiddlyWiki are saved in your browser
Your username for signing your edits. Write it as a WikiWord (eg JoeBloggs)
<<option txtUserName>>
<<option chkSaveBackups>> SaveBackups
<<option chkAutoSave>> AutoSave
<<option chkRegExpSearch>> RegExpSearch
<<option chkCaseSensitiveSearch>> CaseSensitiveSearch
<<option chkAnimate>> EnableAnimations
----
Also see AdvancedOptions
<!--- More ideas shamesslessly begged, borrowed or stolen from..... Simon Baird, Clint Checketts and Christine Hodges :)) --->
<!--{{{-->
<div class='header' macro="gradient vert [[ColorPalette::PrimaryLight]] [[ColorPalette::PrimaryPale]]">
<div id='topMenu'>
<span refresh='content' tiddler='SiteTitle'></span>
<span refresh='content' tiddler='MainMenu'></span></div>
</div>
</div>
<div id='sidebar'>
<div id='sidebarOptions' refresh='content' tiddler='SideBarOptions'></div>
<!--
<div id='sidebarTabs' refresh='content' force='true' tiddler='SideBarTabs'></div>
-->
</div>
<div id='displayArea'>
<div id='messageArea'></div>
<div id='tiddlerDisplay'></div>
</div>
<!--}}}-->
http://www.iasummit.org/proceedings/2008/developing_junior_programmes_i
In this strong market for web professionals, many UX managers have come to the realisation that finding suitable outside practitioners for every role is hard to do. They seek other ways to develop talent in their groups. In this panel, we will talk about developing programmes for entry-level positions in an organisation.
Each person in the panel will bring a different aspect to the panel
* Anne Stevens from Channel 4 will introduce the concept of junior programmes, discussing how to set up junior recruitment and training programmes
* Karen Loasby from BBC will discuss junior programme at the BBC and their effectiveness as a way of developing a practice within the organisation
* Mags Hanley from the Web Technology Group will discuss starting a traineeship at a London agency for a Consultancy team and how it has helped the organisation codify the practice
* Henning Fischer from Adaptive Path will talk from his experience as an Intern and now the co-ordinator of the Adaptive Path programme, in particular making an internship better for the new members of staff and how this has changed the Adaptive Path course
http://www.iasummit.org/proceedings/2008/practical_prototyping_panel
Prototypes are a great way to involve customers early in the design and development process. With the decreasing barrier to entry and an increasing availability of tools today, like Flash, Fireworks, iRise, Expression, and an endless supply of JS/AJAX libraries prototyping should be in every interaction designers’ toolbox. So, why isn’t prototyping as common place in software development as it is in industrial design and architecture? The failure to include prototyping is rarely due to lack of skills with the tools, but instead naiveté about the kinds of prototypes to make and how to use them productively with colleagues and users.
This panel brings together a seasoned group of practitioners to discuss various methods for prototyping with a focus on why we don't prototype in software as much as we should and why we should be doing it more. We'll also discuss what's available today that makes it more accessible and easier today than it was a few years ago (e.g. JS/AJAX libraries, tools like Expression, Flash, Fireworks, iRise) and how to make better decisions about picking the right kind of prototype for the job.
Who Should Attend
Information architects of all levels will benefit from this panel discussion, especially those who are currently dealing with, or planning to deal with Rich Internet Applications or ~DHTMLheavy applications of any kind.
What You Will Learn
When you leave this session, you’ll be equipped with a broader understanding of some of the more commonly used toolkits, reasons why you should be prototyping, how to prototype better, and a greater understanding of some of the pitfalls of prototyping.
http://www.iasummit.org/proceedings/2008/presence_identity_and_attentio
With the explosion of tools such as Twitter, the concept of online “presence” has suddenly become much more visible. The design of social experiences needs a model of identity and attention, including presence as a central factor.
This panel will examine presence by looking at the evolving interaction and architectural design elements involved in social design. We'll explore useful examples of existing social tools and look at which of them attend to the concerns of presence well, and why.
In addition, we will touch on more general questions of social design: How do we promote desired behaviors? How does a social tool strike a balance between control and openness, simplicity and richness? When are familiar conventions useful, and when are they not enough? We will invite audience participation as we puzzle through these challenging new issues as a community.
Core ~IA-related issues:
* Structure of social sites
* Tagging and folksonomies
* Data models for people and their relationships
* Navigation in a community site
http://www.iasummit.org/proceedings/2008/peer_coaching_support_for_ux_m
Over the last year, I have taught UX Management course to 50 UX Managers and have found that during those times the course is less important than the contacts and conversations they had during and after the tutorial.
As part of the IAI, we have been offering a free service of online peer mentoring, but it has fallen flat for two reasons – firstly the times are not always suitable for everyone and secondly there needs to be a great degree of trust amongst the participants. The most successful listen and learn sessions were when I coached people that I knew closely – the degree of trust was very strong and we were able to find solutions for their problems.
I would therefore like to propose a two-hour peer coaching working session where I could demonstrate the coaching method with a group of managers. They would then organise themselves into small groups (about 4 or 5) and take the rest of the session to start coaching each other. Ideally once the working session was finished the groups would continue the conversations online or in person once a month.
There is increasing awareness of the changing role of ~IAs with tools and methodologies developing that provide for agile development and co-creation. To structure the debate and clarify the different roles IAs find themselves in or create for themselves, a set of personas of Information Architects is presented. The segmentation and creation of these personas are based on different data sources: personal experiences, interviews, discussions on IA blogs & mailing lists, theoretical papers on organizational culture and different systems development paradigms and a survey sent out among IAs. The results are different persona descriptions and some tips for practitioners that recognize they operate in a specific role. The tips are practical advice on how to counteract possible drawbacks of the specific role. Bundles of small cards will be available with the set of personas and tips.
Using Dan Brown's book "Communicating Design" as reference, I will show some of the real-world design deliverables coming out of a website project in 2006/2007 for a Top 5 Dutch bank. A combined team of SNS Bank and Info.nl employees went through the scoping, analysis, concept design, prototyping, detailed design, evaluation, and implementation phases. The team did not set out to follow Dan's book (some deliverables were created before the book was published) but in hindsight produced all of its main deliverables.
I have selected the most interesting deliverables for inclusion on the poster (but will bring copies of others) and will highlight how these deliverables relate to each other in this project, how they were presented to the client and used by the design team. The poster will show that real world design can sometimes really be done by the book.
Peter Morville is widely known as a founding father of information architecture. He co-authored the best-selling “polar bear book” and has consulted with such organizations as AT&T, Harvard, IBM, Microsoft, the National Cancer Institute, and Yahoo!. Peter is president of Semantic Studios, author of Ambient Findability, and a founder and past president of the Information Architecture Institute. He has served as a faculty member at the University of Michigan, and his work has been featured in many publications and programs including Business Week, The Economist, Fortune, MSNBC, NPR, The Wall Street Journal, and The Washington Post. He blogs at findability.org.
Peter Stahl is Lead User Experience Designer at eBay, where he focuses on design patterns, interaction design, and holistic site experience. Earlier employers include Business Signatures, AOL, Netscape, and ~PlaceWare.
http://www.iasummit.org/proceedings/2008/placemaking_and_information_ar
Placemaking is the process of creating squares, plazas, parks, streets, and waterfronts that will attract people because they are pleasurable or interesting. This past year I took an intensive workshop in how to do placemaking, how to study how people experience public spaces, and specifically how to improve a market for making it attractive to people so that they will enter the area, spend time there, enjoy themselves, and spend money. The methods and tools of placemaking are very powerful ways to explore the dimensions of information that users experience while doing things in public spaces.
First, we will explore how we as ~IAs can learn from placemaking in the physical world and apply these techniques and lessons toward building better virtual environments and collaboration spaces that are more pleasurable and interesting. Second, we will investigate markets and public places around the use of mobile technologies and how they add another layer of communication and sense-making on top of physical public places.
I hope that with a better understanding of the context of public places we as ~IAs can build better information media and mobile applications for use in those public places.
| !Poster Title | !Presenter(s) |
| [["How Hi is too Hi-Fi?"]] | [[Keith DuFresne]] |
| [[Activity centered design considerations for first wave millennials]] | [[Jacob Alonzo]] |
| [[An Evaluation Scheme for Hierarchical Information Browsing Structures]] | [[Megan Richardson]] |
| [[Analyzing the architecture of Google through eyetracking: discovering where users look on a Google results page?]] | [[Jason Holmes]] |
|~| [[David Robins]] |
|~| [[Aaron Rosenberg]] |
| [[By the book - Peter (and Dan Brown's) perfect case study]] | [[Peter Boersma]] |
| [[Concept Models: Techniques for Next Generation Information Architecture]] | [[Dan Brown]] |
| [[Deliverable Page Patterns]] | [[Nathan Curtis]] |
| [[Detecting Cognitive Overload Points to Improve Information Architecture Designs]] | [[Michael Albers]] |
| [[Documenting Content: Balancing Content and Design in IA Documentation]] | [[Dan Brown]] |
| [[FAA Employee Web – A Story about Crafting a Usable Government Resource]] | [[Thom Haller]] |
| [[Information architecture and the dissemination of emergency information: Visualizing the integration of policy and technology]] | [[Anthony Turko]] |
| [[Personas of the information architect]] | [[David Karemaker]] |
| [[Production process modeling in mediawiki]] | [[Christopher McConnell]] |
| [[Putting Your Design in the Crosshair: Turning to Visual Grammar to Evaluate Your Web Designs]] | [[Brian Verhoeven]] |
| [[Site-it: IA Prototyping toolkit]] | [[Atsushi Hasegawa]] |
| [[Tagging people for relationship management]] | [[Maryam Najafian Razavi]] |
|~| [[Lee Iverson]] |
| [[Tagging: Motivations, behavior, and implications]] | [[Vanesa Mirzaee]] |
|~| [[Lee Iverson]] |
| [[The UX Funnel - Modelling and Remotely Testing the User Experience]] | [[Reinoud Bosman]] |
| [[Visualizing tag aging and decay]] | [[Alla Zollers]], [[Jackson Fox]] |
| [["A Blueprint for Managing A Strategic UX Design Group"]] | [[Stephen Anderson]] |
| [["Unfold Your Sites"]] | [[Keith DuFresne]] |
Wikis have gained attention and adoption as knowledge management tools. In most cases, the software is used for informal knowledge-sharing, but wikis can also be used to formalize workflows, to ensure that the appropriate stakeholders see the appropriate information during a production process.
This poster will discuss how Information Architecture principles such as controlled vocabularies and labeling were used to transform a ~MediaWiki installation into the primary production-tracking tool at an educational media firm. Although the software lacks formal business-process-modeling tools, it is now in use to track the status of over 600 animated and video pieces through a twenty-seven-step media production process. Although ~MediaWiki was hardly designed as a tool for modeling production processes , application of Information Architecture principles to its features has made it an invaluable tool for internal employees and external contractors.
As information architects we are always looking for ways to improve the user experience. We rely on many tools and processes, including user research and patterns, to design information environments that support the users and activities. Even with these existing tools and processes, one of the greatest challenges to any design process is assessing the subconscious consumption of information. We often rely on expensive user testing sessions and/or eyetracking experiments in an attempt to uncover this subconscious process. However, visual grammar provides a simple tool that may be used to help us evaluate how our designs facilitate subconscious information processing. My poster will provide Kress and Van Leeuwen's "dimensions of visual space" crosshair and explain how to use it to reliably predict the subconscious processing of any visual composition in Western culture including websites.
http://www.iasummit.org/proceedings/2008/putting_multiple_user_centered
This paper talks about the challenge of presenting and getting user feedback on large amounts of disparate information to create an intranet based one-stop-shop to get help for Intel employees worldwide. A combination of three usability techniques including card sorting, focus groups, and wireframe design activities, were conducted to allow users to experience and manipulate the information based on their expectation. The combination of studies is an easy, effective, and practical way to create a user centered design that can be applied to any new or existing product where global user input is required on the interface design, information process flow, and desired user interaction.
http://www.iasummit.org/proceedings/2008/reexperiencing_information_dea
The wide-spread adoption of web-based services has helped people organize information, connect with loved ones, and share data through an electronic medium. This convenience, however, has spawned a massive proliferation of single-purpose user profiles, closed data repositories, and endless login credentials. Not surprisingly, people are quickly becoming less tolerant of experiences that require large quantities of personal information upfront.Deciding what information to ask a customer when creating an account is a literal balance between user needs and business needs. Users want to protect their privacy and provide as little information as possible. The business, on the other hand, wants to learn who their customer is, and ask as many revealing questions as possible.
In this session, I will draw from my experience in redesigning the Yahoo! registration and account recovery systems. I will also show examples from other web sites, and suggest techniques to apply toward common IA and Interaction Design challenges faced in designing membership frameworks.
This session will discuss the following topics:
* Making registration painless for your customers
* Encouraging accurate and truthful data entry
* Maintaining account information up-to-date
* Keeping the bad guys out but allowing for password recovery
Reinoud Bosman is an information architect working in interactive environments for 8 years. Currently he’s working at Media Catalyst Amsterdam for clients like Sony Ericsson, Sony, Variety and Philips.
Before joining Media Catalyst Reinoud worked at ~EzGov, a leading provider of e-government applications. Projects he worked on included the Self Assessment online tax return and Corporation Tax Online for the UK HM Revenue and Customs.
Reinoud holds a ~MSc in Biology from the Free University Amsterdam and researched the communication of science on the web at the Free University Berlin. He has lived and worked in Sydney and Tokyo.
http://www.iasummit.org/proceedings/2008/content_page_design_best_pract
In today’s social, distributed, search-driven Web, customers are finding their way to Web content through an increasing number of distinct experiences. Yet when people arrive at most Web pages, the experience they get isn’t optimised for this context. Instead, the vast majority of content pages online remain more concerned with their own context than the context of their users: where did a user arrive from and where are they likely to go next? These pages remain designed as if they were primarily accessed from a Web site’s home page or a carefully thought-out selection from the site’s information architecture.
To address these issues and more, this talk outlines a set of best practices for Web content page design that focuses on appropriate presentations of content, context, and calls to action. Specifically: how can content be optimised to meet user expectations as they arrive from a diverse number of access points; what is the minimum amount of context required to frame content appropriately; how can the most relevant calls to action be presented to maximize user engagement? Applying these considerations enables information architects to deliver content experiences that take full advantage of emerging opportunities online and the existing assets within their Web sites.
http://www.iasummit.org/proceedings/2008/search_patterns
Search is among our most important and complex challenges. As the choice of first resort for many users and tasks, search is a defining element of the user experience. And, as a unique amalgam of content, metadata, technology and design, the search results interface demands intense cross-disciplinary collaboration. In this fast-paced session, we’ll describe a pattern language for search that explains user psychology and information seeking behavior, highlights emerging technologies and interaction models, illustrates repeatable solutions to common problems, and positions us all to design better search interfaces and applications.
Topics
* A flexible model for describing search patterns that embraces multiple contexts including enterprise, e-commerce, web, desktop, and mobile applications.
* An overview of classic and cutting-edge research focused on user psychology, behavior, and experience with respect to search, navigation, retrieval, findability, and keeping found things found.
* Designing next-generation search interfaces and applications that combine best practices in tagging and taxonomies with search analytics, guided navigation, thesauri, clustering algorithms, linguistic toolsets, and rich result interfaces.
* Evaluating the multi-channel challenges and real-world opportunities for search and discovery presented by the emerging Internet of objects.
Audiences
This session is intended for information architects, interaction designers, software developers, user experience managers, entrepreneurs, and anyone else (experts and beginners alike) with an interest in the design of search interfaces and applications.
Samantha Bailey is a highly skilled leader with over ten years of management experience in a variety of user-centered design environments. She is currently consulting and teaching as an adjunct professor at Kent State University in the Information Architecture & Knowledge Management program. Previously she was the Director of Usability at Thomson West for the westlaw.com interface and Information Architecture VP for Wachovia.com. Prior to joining Wachovia, Samantha was Vice President of Operations at Argus Associates, a pioneering information architecture firm. Her clients included AT&T, Procter & Gamble, Vanguard and the Weather Channel. She holds a master’s degree in library science from the University of Michigan.
Sanda Erdelez conducts research, teaching and consulting in information user behavior and usability evaluation. She is an associate professor and director of the Information Experience Laboratory at University of Missouri.
| | ![[Flagler / Monroe]] | ![[Brickell]] | ![[Tuttle]] | ![[Flex: Orchid C/D]] |
| [[8:00 - 8:30AM|08:00 - 8:30AM]] |>|>|>| Registration |
| [[8:30 - 10:00AM|08:30 - 10:00AM]] |>|>|>| [[Keynote: Journey to the Center of Design]] |
| [[10:00 - 10:30AM]] |>|>|>| Morning tea |
| [[10:30 - 11:15AM]] | [[Integrating web analytics into information architecture and user-centered design]] | [[IAs, language and lego - an introduction to semantic analysis]] | [[Tagging: Five emerging trends]] | [[Exploratory search and folksonomy: Exploration paths in social tagging systems]] |
| [[11:15 - 11:30AM]] |>|>|>| Break |
| [[11:30 - 12:15PM]] | [[Web use recorders: The future of web analytics?]] | [[Core and paths: Putting a creative findability framework to use]] | [[Do real people really use tag clouds?: Research to help distinguish between web 2.0's hits and hype]] | |
| [[12:15 - 1:45PM]] |>|>|>| Lunch |
| [[1:45 - 2:30PM]] | [[Designing your reputation system in 15 easy steps]] | [[Effective IA for enterprise portals: The building blocks design framework]] | [[A management fable: The little UX that went a long way]] | |
| [[2:30 - 2:45PM]] |>|>|>| Break |
| [[4:00 - 4:45PM]] | [[IA Slam 2008: The workshop with a winner]] | [[Content page design best practices]] | [[How to be a user experience team of one]] | [[Peer coaching - support for UX managers]] |
| [[3:30 - 4:00PM]] |~|>| Afternoon tea |~|
| [[4:00 - 4:45PM]] |~| [[The business of experience: The experience impact framework]] | [[Blind ambition: How the accessibility movement overlooks sensory experience]] |~|
| [[4:45 - 5:00PM]] |~|>|>| Break |
| [[5:00 - 5:45PM]] |~| [[Inspiration from the edge: New patterns for interface design]] | [[The long wow]] | |
| [[5:45 - 7:45PM]] |>|>|>| [[Posters & reception]] |
http://www.iasummit.org/proceedings/2008/search_patterns
Search is among our most important and complex challenges. As the choice of first resort for many users and tasks, search is a defining element of the user experience. And, as a unique amalgam of content, metadata, technology and design, the search results interface demands intense cross-disciplinary collaboration. In this fast-paced session, we’ll describe a pattern language for search that explains user psychology and information seeking behavior, highlights emerging technologies and interaction models, illustrates repeatable solutions to common problems, and positions us all to design better search interfaces and applications.
Topics
* A flexible model for describing search patterns that embraces multiple contexts including enterprise, e-commerce, web, desktop, and mobile applications.
* An overview of classic and cutting-edge research focused on user psychology, behavior, and experience with respect to search, navigation, retrieval, findability, and keeping found things found.
* Designing next-generation search interfaces and applications that combine best practices in tagging and taxonomies with search analytics, guided navigation, thesauri, clustering algorithms, linguistic toolsets, and rich result interfaces.
* Evaluating the multi-channel challenges and real-world opportunities for search and discovery presented by the emerging Internet of objects.
Audiences
This session is intended for information architects, interaction designers, software developers, user experience managers, entrepreneurs, and anyone else (experts and beginners alike) with an interest in the design of search interfaces and applications.
Shibani Kapoor is a Human Factors Engineer at Intel Corporation in the Information Technology department. She partners with cross-functional teams across Intel and uses various data gathering methods to evaluate and improve the user experience of business processes and software applications used by internal Intel employees as well as Intel’s customers and suppliers. She also develops user interface specifications, user and context assessments, scenarios, business flow diagrams, and prototypes. She prioritizes and tracks usability issues throughout the planning, design, development, and deployment phases of the project lifecycle. She provides strategic direction, consultation, advocacy, and education on effective user-centered design methods and usability issues across the organization.
She is interested in understanding the usability variances in different cultures and designing evaluation methodologies that take them into account.
Shibani has a Bachelors degree in ~Math-Computer Science with a minor in Cognitive Science from the University of California, San Diego. She completed her M.S. in Information specializing in ~Human-Computer Interaction from the University of Michigan, Ann Arbor.
<<search>><<closeAll>><<permaview>><<newTiddler>><<saveChanges>><<slider chkSliderOptionsPanel OptionsPanel 'options >' 'Change TiddlyWiki advanced options'>><<slider 1 SideBarTabs "tabs > ">>
Site-it is a simple, powerful and cheap prototyping tool for site structure and user experience flow.
This tool is a set of stickies printed abstract appearance of web pages. It contains 7 types of templates that express most of web pages. ~IAs can use it for brainstorming and discussion with clients. By using this tool, you can focus on IA discussion and cultivate understandings of user experience in the sites with team members and clients.
On the presentation, we demonstrate the tool and explain the design retionale hehind the tool.
April 10-14 in Miami, Florida
[[iA SUMMIT 2008|iA SUMMIT 2008 TiddlyWiki]]
/***
|''Name:''|SparklinePlugin|
|''Description:''|Sparklines macro|
***/
//{{{
if(!version.extensions.SparklinePlugin) {
version.extensions.SparklinePlugin = {installed:true};
//--
//-- Sparklines
//--
config.macros.sparkline = {};
config.macros.sparkline.handler = function(place,macroName,params)
{
var data = [];
var min = 0;
var max = 0;
var v;
for(var t=0; t<params.length; t++) {
v = parseInt(params[t]);
if(v < min)
min = v;
if(v > max)
max = v;
data.push(v);
}
if(data.length < 1)
return;
var box = createTiddlyElement(place,"span",null,"sparkline",String.fromCharCode(160));
box.title = data.join(",");
var w = box.offsetWidth;
var h = box.offsetHeight;
box.style.paddingRight = (data.length * 2 - w) + "px";
box.style.position = "relative";
for(var d=0; d<data.length; d++) {
var tick = document.createElement("img");
tick.border = 0;
tick.className = "sparktick";
tick.style.position = "absolute";
tick.src = "data:image/gif,GIF89a%01%00%01%00%91%FF%00%FF%FF%FF%00%00%00%C0%C0%C0%00%00%00!%F9%04%01%00%00%02%00%2C%00%00%00%00%01%00%01%00%40%02%02T%01%00%3B";
tick.style.left = d*2 + "px";
tick.style.width = "2px";
v = Math.floor(((data[d] - min)/(max-min)) * h);
tick.style.top = (h-v) + "px";
tick.style.height = v + "px";
box.appendChild(tick);
}
};
}
//}}}
A consultant, entrepreneur, and speaker, Stephen is passionate about elegant design and the technological innovations that make desirable experiences possible. He is currently the VP of Design at Viewzi, where he hopes to change how people view search results.
Prior to Viewzi, Stephen grew and led the user experience teams at both Sabre Travel Network and Bright Corner, a creative and technology services company he co-founded in 2001.
Stephen can be found online at poetpainter.com.
http://www.iasummit.org/proceedings/2008/storytelling_a_compelling_desi
Everyone agrees that stories are powerful and add impact - your audience remembers stories and passes them on. How you tell your story makes a big difference too, and the more personal and poignant - the more the audience can identify, making the message more effective. Storytelling is a powerful way to bring a concept to life, and I recommend we do it more often as a design tool.
Many of you are already using storytelling techniques -- through personas and scenarios. But there are other phases of the design process where storytelling can augment methods. During user research sharing stories connect us with our subjects. Storytelling helps teams collaborate. When we articulate concepts we can establish credibility by telling a story. It’s especially compelling as an adjunct to diagrams and numbers -- a good story can facilitate buy-in and approval of solutions. From problem definition to research, team building to communication, stories are a winning tool to gain consensus, improve collaborative relationships and create user experiences that resonate.
This presentation will demonstrate how to combine storytelling techniques with the user-centered methodologies we are already practicing. Building on work by Tom Erickson, Dana Atchley and others, we'll listen to stories, practice telling our own, and learn when, where, why and how to add storytelling to our toolkit.
<!--- The default TW colours with modified layout. Ideas shamesslessly taken from (and suggested by) Simon Baird, Clint Checketts and Christine Hodges --->
/*{{{*/
.headerForeground { display: none;}
#sidebar {width: 170px; }
#sidebarTabs .tabContents {width: 158px; }
#displayArea {background: [[ColorPalette::Background]];margin: 1em 15.7em 0em 1em;}
#topMenu { background: transparent; padding: 6px;margin-left: -5px; border-bottom: solid 3px [[ColorPalette::SecondaryMid]];}
#topMenu .button, #topMenu .tiddlyLink, tiddlyLinkExisting, #topMenu .externalLink
{
color: [[ColorPalette::PrimaryDark]];
text-align: center;
font-weight: bold;
font-size: 1.1em;
text-decoration: none;
letter-spacing: 1.5px;
background: transparent;
border-right: solid 1px [[ColorPalette::Background]];
padding: 5px 15px 8px 15px;
}
#topMenu a:hover {
color: [[ColorPalette::Background]];
background: [[ColorPalette::SecondaryLight]];
}
#topMenu br {display: none; padding-right: 1em;}
#topMenu span .tiddlyLinkNonExisting {font-style:normal;}
/*}}}*/
/*{{{*/
body {background:[[ColorPalette::Background]]; color:[[ColorPalette::Foreground]];}
a {color:[[ColorPalette::PrimaryMid]];}
a:hover {background-color:[[ColorPalette::PrimaryMid]]; color:[[ColorPalette::Background]];}
a img {border:0;}
h1,h2,h3,h4,h5,h6 {color:[[ColorPalette::SecondaryDark]]; background:transparent;}
h1 {border-bottom:2px solid [[ColorPalette::TertiaryLight]];}
h2,h3 {border-bottom:1px solid [[ColorPalette::TertiaryLight]];}
.button {color:[[ColorPalette::PrimaryDark]]; border:1px solid [[ColorPalette::Background]];}
.button:hover {color:[[ColorPalette::PrimaryDark]]; background:[[ColorPalette::SecondaryLight]]; border-color:[[ColorPalette::SecondaryMid]];}
.button:active {color:[[ColorPalette::Background]]; background:[[ColorPalette::SecondaryMid]]; border:1px solid [[ColorPalette::SecondaryDark]];}
.header {background:[[ColorPalette::PrimaryMid]];}
.headerShadow {color:[[ColorPalette::Foreground]];}
.headerShadow a {font-weight:normal; color:[[ColorPalette::Foreground]];}
.headerForeground {color:[[ColorPalette::Background]];}
.headerForeground a {font-weight:normal; color:[[ColorPalette::PrimaryPale]];}
.tabSelected{color:[[ColorPalette::PrimaryDark]];
background:[[ColorPalette::TertiaryPale]];
border-left:1px solid [[ColorPalette::TertiaryLight]];
border-top:1px solid [[ColorPalette::TertiaryLight]];
border-right:1px solid [[ColorPalette::TertiaryLight]];
}
.tabUnselected {color:[[ColorPalette::Background]]; background:[[ColorPalette::TertiaryMid]];}
.tabContents {color:[[ColorPalette::PrimaryDark]]; background:[[ColorPalette::TertiaryPale]]; border:1px solid [[ColorPalette::TertiaryLight]];}
.tabContents .button {border:0;}
#sidebar {}
#sidebarOptions input {border:1px solid [[ColorPalette::PrimaryMid]];}
#sidebarOptions .sliderPanel {background:[[ColorPalette::PrimaryPale]];}
#sidebarOptions .sliderPanel a {border:none;color:[[ColorPalette::PrimaryMid]];}
#sidebarOptions .sliderPanel a:hover {color:[[ColorPalette::Background]]; background:[[ColorPalette::PrimaryMid]];}
#sidebarOptions .sliderPanel a:active {color:[[ColorPalette::PrimaryMid]]; background:[[ColorPalette::Background]];}
.wizard {background:[[ColorPalette::PrimaryPale]]; border:1px solid [[ColorPalette::PrimaryMid]];}
.wizard h1 {color:[[ColorPalette::PrimaryDark]]; border:none;}
.wizard h2 {color:[[ColorPalette::Foreground]]; border:none;}
.wizardStep {background:[[ColorPalette::Background]]; color:[[ColorPalette::Foreground]];
border:1px solid [[ColorPalette::PrimaryMid]];}
.wizardStep.wizardStepDone {background:[[ColorPalette::TertiaryLight]];}
.wizardFooter {background:[[ColorPalette::PrimaryPale]];}
.wizardFooter .status {background:[[ColorPalette::PrimaryDark]]; color:[[ColorPalette::Background]];}
.wizard .button {color:[[ColorPalette::Foreground]]; background:[[ColorPalette::SecondaryLight]]; border: 1px solid;
border-color:[[ColorPalette::SecondaryPale]] [[ColorPalette::SecondaryDark]] [[ColorPalette::SecondaryDark]] [[ColorPalette::SecondaryPale]];}
.wizard .button:hover {color:[[ColorPalette::Foreground]]; background:[[ColorPalette::Background]];}
.wizard .button:active {color:[[ColorPalette::Background]]; background:[[ColorPalette::Foreground]]; border: 1px solid;
border-color:[[ColorPalette::PrimaryDark]] [[ColorPalette::PrimaryPale]] [[ColorPalette::PrimaryPale]] [[ColorPalette::PrimaryDark]];}
#messageArea {border:1px solid [[ColorPalette::SecondaryMid]]; background:[[ColorPalette::SecondaryLight]]; color:[[ColorPalette::Foreground]];}
#messageArea .button {color:[[ColorPalette::PrimaryMid]]; background:[[ColorPalette::SecondaryPale]]; border:none;}
.popupTiddler {background:[[ColorPalette::TertiaryPale]]; border:2px solid [[ColorPalette::TertiaryMid]];}
.popup {background:[[ColorPalette::TertiaryPale]]; color:[[ColorPalette::TertiaryDark]]; border-left:1px solid [[ColorPalette::TertiaryMid]]; border-top:1px solid [[ColorPalette::TertiaryMid]]; border-right:2px solid [[ColorPalette::TertiaryDark]]; border-bottom:2px solid [[ColorPalette::TertiaryDark]];}
.popup hr {color:[[ColorPalette::PrimaryDark]]; background:[[ColorPalette::PrimaryDark]]; border-bottom:1px;}
.popup li.disabled {color:[[ColorPalette::TertiaryMid]];}
.popup li a, .popup li a:visited {color:[[ColorPalette::Foreground]]; border: none;}
.popup li a:hover {background:[[ColorPalette::SecondaryLight]]; color:[[ColorPalette::Foreground]]; border: none;}
.popup li a:active {background:[[ColorPalette::SecondaryPale]]; color:[[ColorPalette::Foreground]]; border: none;}
.popupHighlight {background:[[ColorPalette::Background]]; color:[[ColorPalette::Foreground]];}
.listBreak div {border-bottom:1px solid [[ColorPalette::TertiaryDark]];}
.tiddler .defaultCommand {font-weight:bold;}
.shadow .title {color:[[ColorPalette::TertiaryDark]];}
.title {color:[[ColorPalette::SecondaryDark]];}
.subtitle {color:[[ColorPalette::TertiaryDark]];}
.toolbar {color:[[ColorPalette::PrimaryMid]];}
.toolbar a {color:[[ColorPalette::TertiaryLight]];}
.selected .toolbar a {color:[[ColorPalette::TertiaryMid]];}
.selected .toolbar a:hover {color:[[ColorPalette::Foreground]];}
.tagging, .tagged {border:1px solid [[ColorPalette::TertiaryPale]]; background-color:[[ColorPalette::TertiaryPale]];}
.selected .tagging, .selected .tagged {background-color:[[ColorPalette::TertiaryLight]]; border:1px solid [[ColorPalette::TertiaryMid]];}
.tagging .listTitle, .tagged .listTitle {color:[[ColorPalette::PrimaryDark]];}
.tagging .button, .tagged .button {border:none;}
.toggle .button {border:1;}
.toggle .button {color:[[ColorPalette::PrimaryDark]]; background:[[ColorPalette::SecondaryLight]]; border:1px solid [[ColorPalette::SecondaryMid]];}
.toggle .button:hover {color:[[ColorPalette::PrimaryDark]]; background:[[ColorPalette::SecondaryLight]]; border-color:[[ColorPalette::SecondaryMid]];}
.toggle .button:active {color:[[ColorPalette::Background]]; background:[[ColorPalette::SecondaryMid]]; border:1px solid [[ColorPalette::SecondaryDark]];}
.footer {color:[[ColorPalette::TertiaryLight]];}
.selected .footer {color:[[ColorPalette::TertiaryMid]];}
.sparkline {background:[[ColorPalette::PrimaryPale]]; border:0;}
.sparktick {background:[[ColorPalette::PrimaryDark]];}
.error, .errorButton {color:[[ColorPalette::Foreground]]; background:[[ColorPalette::Error]];}
.warning {color:[[ColorPalette::Foreground]]; background:[[ColorPalette::SecondaryPale]];}
.lowlight {background:[[ColorPalette::TertiaryLight]];}
.zoomer {background:none; color:[[ColorPalette::TertiaryMid]]; border:3px solid [[ColorPalette::TertiaryMid]];}
.imageLink, #displayArea .imageLink {background:transparent;}
.annotation {background:[[ColorPalette::SecondaryLight]]; color:[[ColorPalette::Foreground]]; border:2px solid [[ColorPalette::SecondaryMid]];}
.viewer .listTitle {list-style-type:none; margin-left:-2em;}
.viewer .button {border:1px solid [[ColorPalette::SecondaryMid]];}
.viewer blockquote {border-left:3px solid [[ColorPalette::TertiaryDark]];}
.viewer table, table.twtable {border:2px solid [[ColorPalette::TertiaryDark]];}
.viewer th, .viewer thead td, .twtable th, .twtable thead td {background:[[ColorPalette::SecondaryMid]]; border:1px solid [[ColorPalette::TertiaryDark]]; color:[[ColorPalette::Background]];}
.viewer td, .viewer tr, .twtable td, .twtable tr {border:1px solid [[ColorPalette::TertiaryDark]];}
.viewer pre {border:1px solid [[ColorPalette::SecondaryLight]]; background:[[ColorPalette::SecondaryPale]];}
.viewer code {color:[[ColorPalette::SecondaryDark]];}
.viewer hr {border:0; border-top:dashed 1px [[ColorPalette::TertiaryDark]]; color:[[ColorPalette::TertiaryDark]];}
.highlight, .marked {background:[[ColorPalette::SecondaryLight]];}
.editor input {border:1px solid [[ColorPalette::PrimaryMid]];}
.editor textarea {border:1px solid [[ColorPalette::PrimaryMid]]; width:100%;}
.editorFooter {color:[[ColorPalette::TertiaryMid]];}
#backstageArea {background:[[ColorPalette::Foreground]]; color:[[ColorPalette::TertiaryMid]];}
#backstageArea a {background:[[ColorPalette::Foreground]]; color:[[ColorPalette::Background]]; border:none;}
#backstageArea a:hover {background:[[ColorPalette::SecondaryLight]]; color:[[ColorPalette::Foreground]]; }
#backstageArea a.backstageSelTab {background:[[ColorPalette::Background]]; color:[[ColorPalette::Foreground]];}
#backstageButton a {background:none; color:[[ColorPalette::Background]]; border:none;}
#backstageButton a:hover {background:[[ColorPalette::Foreground]]; color:[[ColorPalette::Background]]; border:none;}
#backstagePanel {background:[[ColorPalette::Background]]; border-color: [[ColorPalette::Background]] [[ColorPalette::TertiaryDark]] [[ColorPalette::TertiaryDark]] [[ColorPalette::TertiaryDark]];}
.backstagePanelFooter .button {border:none; color:[[ColorPalette::Background]];}
.backstagePanelFooter .button:hover {color:[[ColorPalette::Foreground]];}
#backstageCloak {background:[[ColorPalette::Foreground]]; opacity:0.6; filter:'alpha(opacity:60)';}
/*}}}*/
/*{{{*/
* html .tiddler {height:1%;}
body {font-size:.75em; font-family:arial,helvetica; margin:0; padding:0;}
h1,h2,h3,h4,h5,h6 {font-weight:bold; text-decoration:none;}
h1,h2,h3 {padding-bottom:1px; margin-top:1.2em;margin-bottom:0.3em;}
h4,h5,h6 {margin-top:1em;}
h1 {font-size:1.35em;}
h2 {font-size:1.25em;}
h3 {font-size:1.1em;}
h4 {font-size:1em;}
h5 {font-size:.9em;}
hr {height:1px;}
a {text-decoration:none;}
dt {font-weight:bold;}
ol {list-style-type:decimal;}
ol ol {list-style-type:lower-alpha;}
ol ol ol {list-style-type:lower-roman;}
ol ol ol ol {list-style-type:decimal;}
ol ol ol ol ol {list-style-type:lower-alpha;}
ol ol ol ol ol ol {list-style-type:lower-roman;}
ol ol ol ol ol ol ol {list-style-type:decimal;}
.txtOptionInput {width:11em;}
#contentWrapper .chkOptionInput {border:0;}
.externalLink {text-decoration:underline;}
.indent {margin-left:3em;}
.outdent {margin-left:3em; text-indent:-3em;}
code.escaped {white-space:nowrap;}
.tiddlyLinkExisting {font-weight:bold;}
.tiddlyLinkNonExisting {font-style:italic;}
/* the 'a' is required for IE, otherwise it renders the whole tiddler in bold */
a.tiddlyLinkNonExisting.shadow {font-weight:bold;}
#mainMenu .tiddlyLinkExisting,
#mainMenu .tiddlyLinkNonExisting,
#sidebarTabs .tiddlyLinkNonExisting {font-weight:normal; font-style:normal;}
#sidebarTabs .tiddlyLinkExisting {font-weight:bold; font-style:normal;}
.header {position:relative;}
.header a:hover {background:transparent;}
.headerShadow {position:relative; padding:4.5em 0em 1em 1em; left:-1px; top:-1px;}
.headerForeground {position:absolute; padding:4.5em 0em 1em 1em; left:0px; top:0px;}
.siteTitle {font-size:3em;}
.siteSubtitle {font-size:1.2em;}
#mainMenu {position:absolute; left:0; width:10em; text-align:right; line-height:1.6em; padding:1.5em 0.5em 0.5em 0.5em; font-size:1.1em;}
#sidebar {position:absolute; right:3px; width:16em; font-size:.9em;}
#sidebarOptions {padding-top:0.3em;}
#sidebarOptions a {margin:0em 0.2em; padding:0.2em 0.3em; display:block;}
#sidebarOptions input {margin:0.4em 0.5em;}
#sidebarOptions .sliderPanel {margin-left:1em; padding:0.5em; font-size:.85em;}
#sidebarOptions .sliderPanel a {font-weight:bold; display:inline; padding:0;}
#sidebarOptions .sliderPanel input {margin:0 0 .3em 0;}
#sidebarTabs .tabContents {width:15em; overflow:hidden;}
.wizard {padding:0.1em 1em 0em 2em;}
.wizard h1 {font-size:2em; font-weight:bold; background:none; padding:0em 0em 0em 0em; margin:0.4em 0em 0.2em 0em;}
.wizard h2 {font-size:1.2em; font-weight:bold; background:none; padding:0em 0em 0em 0em; margin:0.4em 0em 0.2em 0em;}
.wizardStep {padding:1em 1em 1em 1em;}
.wizard .button {margin:0.5em 0em 0em 0em; font-size:1.2em;}
.wizardFooter {padding:0.8em 0.4em 0.8em 0em;}
.wizardFooter .status {padding:0em 0.4em 0em 0.4em; margin-left:1em;}
.wizard .button {padding:0.1em 0.2em 0.1em 0.2em;}
#messageArea {position:fixed; top:2em; right:0em; margin:0.5em; padding:0.5em; z-index:2000; _position:absolute;}
.messageToolbar {display:block; text-align:right; padding:0.2em 0.2em 0.2em 0.2em;}
#messageArea a {text-decoration:underline;}
.tiddlerPopupButton {padding:0.2em 0.2em 0.2em 0.2em;}
.popupTiddler {position: absolute; z-index:300; padding:1em 1em 1em 1em; margin:0;}
.popup {position:absolute; z-index:300; font-size:.9em; padding:0; list-style:none; margin:0;}
.popup .popupMessage {padding:0.4em;}
.popup hr {display:block; height:1px; width:auto; padding:0; margin:0.2em 0em;}
.popup li.disabled {padding:0.4em;}
.popup li a {display:block; padding:0.4em; font-weight:normal; cursor:pointer;}
.listBreak {font-size:1px; line-height:1px;}
.listBreak div {margin:2px 0;}
.tabset {padding:1em 0em 0em 0.5em;}
.tab {margin:0em 0em 0em 0.25em; padding:2px;}
.tabContents {padding:0.5em;}
.tabContents ul, .tabContents ol {margin:0; padding:0;}
.txtMainTab .tabContents li {list-style:none;}
.tabContents li.listLink { margin-left:.75em;}
#contentWrapper {display:block;}
#splashScreen {display:none;}
#displayArea {margin:1em 17em 0em 14em;}
.toolbar {text-align:right; font-size:.9em;}
.tiddler {padding:1em 1em 0em 1em;}
.missing .viewer,.missing .title {font-style:italic;}
.title {font-size:1.6em; font-weight:bold;}
.titlemarker {float:left;}
.missing .subtitle {display:none;}
.subtitle {font-size:1.1em;}
.tiddler .button {padding:0.2em 0.4em;}
.tagging {margin:0.5em 0.5em 0.5em 0; float:left; display:none;}
.isTag .tagging {display:block;}
.tagged {margin:0.5em; float:right;}
.tagging, .tagged {font-size:0.9em; padding:0.25em;}
.tagging ul, .tagged ul {list-style:none; margin:0.25em; padding:0;}
.tagClear {clear:both;}
.footer {font-size:.9em;}
.footer li {display:inline;}
.annotation {padding:0.5em; margin:0.5em;}
* html .viewer pre {width:99%; padding:0 0 1em 0;}
.viewer {line-height:1.4em; padding-top:0.5em;}
.viewer .button {margin:0em 0.25em; padding:0em 0.25em;}
.viewer blockquote {line-height:1.5em; padding-left:0.8em;margin-left:2.5em;}
.viewer ul, .viewer ol {margin-left:0.5em; padding-left:1.5em;}
.viewer table, table.twtable {border-collapse:collapse; margin:0.8em 1.0em;}
.viewer th, .viewer td, .viewer tr,.viewer caption,.twtable th, .twtable td, .twtable tr,.twtable caption {padding:3px;}
table.listView {font-size:0.85em; margin:0.8em 1.0em;}
table.listView th, table.listView td, table.listView tr {padding:0px 3px 0px 3px;}
.viewer pre {padding:0.5em; margin-left:0.5em; font-size:1.2em; line-height:1.4em; overflow:auto;}
.viewer code {font-size:1.2em; line-height:1.4em;}
.editor {font-size:1.1em;}
.editor input, .editor textarea {display:block; width:100%; font:inherit;}
.editorFooter {padding:0.25em 0em; font-size:.9em;}
.editorFooter .button {padding-top:0px; padding-bottom:0px;}
.fieldsetFix {border:0; padding:0; margin:1px 0px 1px 0px;}
.sparkline {line-height:1em;}
.sparktick {outline:0;}
.zoomer {font-size:1.1em; position:absolute; overflow:hidden;}
.zoomer div {padding:1em;}
* html #backstage {width:99%;}
* html #backstageArea {width:99%;}
#backstageArea {display:none; position:relative; overflow: hidden; z-index:150; padding:0.3em 0.5em 0.3em 0.5em;}
#backstageToolbar {position:relative;}
#backstageArea a {font-weight:bold; margin-left:0.5em; padding:0.3em 0.5em 0.3em 0.5em;}
#backstageButton {display:none; position:absolute; z-index:175; top:0em; right:0em;}
#backstageButton a {padding:0.1em 0.4em 0.1em 0.4em; margin:0.1em 0.1em 0.1em 0.1em;}
#backstage {position:relative; width:100%; z-index:50;}
#backstagePanel {display:none; z-index:100; position:absolute; margin:0em 3em 0em 3em; padding:1em 1em 1em 1em;}
.backstagePanelFooter {padding-top:0.2em; float:right;}
.backstagePanelFooter a {padding:0.2em 0.4em 0.2em 0.4em;}
#backstageCloak {display:none; z-index:20; position:absolute; width:100%; height:100px;}
.whenBackstage {display:none;}
.backstageVisible .whenBackstage {display:block;}
/*}}}*/
/*{{{*/
@media print {
#mainMenu, #sidebar, #messageArea, #breadCrumbs, #openTiddlers, #topMenu, #hoverMenu,
#backstage, #backstageButton, .tagged,
#backstageArea, .toolbar, .siteSubtitle, .siteTitle, .header, .subtitle
{display: none ! important;}
#displayArea {margin: 1em 1em 0em 1em;}
/* Fixes a feature in Firefox 1.5.0.2 where print preview displays the
noscript content */
noscript {display:none;}
}
/*}}}*/
| | ![[Flagler / Monroe]] | ![[Brickell]] | ![[Tuttle]] | ![[Flex: Orchid C/D]] |
| [[9:00 - 9:45AM|09:00 - 9:45AM]] | [[Extending the gaming experience to conventional UI’s]] | [[Taxonomy is user experience]] | [[Placemaking and information architecture]] | |
| [[9:45 - 10:15AM|09:45 - 10:15AM]] |>|>|>| Morning tea |
| [[10:15 - 11:00AM]] | [[Testing for advertising effectiveness]] | [[Building trust through restricted information: A case study of the Hotwire.com air redesign]] | [[Hotel Yeoville]] | [[Repeat: Content page design best practices]] |
| [[11:00 - 11:15AM]] |>|>|>| Break |
| [[11:15 - 12:00PM]] | [[The information architect and the fighter pilot]] | [[Search Patterns]] | [[UX in the Wind: Finding Experience on a Motorcycle]] | |
| [[12:00 - 1:30PM]] |>|>|>| Lunch |
| [[1:30 - 3:00PM]] | [[Panel: Presence, identity, and attention in social web architecture]] | [[Panel: Practical prototyping]] | [[Panel: Developing junior programmes in UX teams]] | |
| [[3:00 - 3:30PM]] |>|>|>| Afternoon tea |
| [[3:30 - 4:15PM]] | [[What do innovative intranets look like?]] | [[Code blue: How service design can revolutionize patient care in hospitals]] | [[Making the leap from practitioner to manager: Confidence building strategies and common pitfalls]] | [[Creating career paths for UX professionals]] |
| [[4:15 - 4:30PM]] |>|>| Break |~|
| [[4:30 - 5:15PM]] | [[The impact of social ethics on IA and interactive design - experiences from the Norwegian woods]] | [[E-service: What we can learn from the customer-service gurus]] | [[Web site maturity cycles]] |~|
<<tagglyTagCloud excludeSearch excludeLists systemConfig>>
Access control in social software is often defined in terms of 'networks of friends' relationships, in which all `friends' are created equal and are often required to be reciprocal. We argue that the potential audience for various kinds of personal artifacts in social software must be defined in a user’s own terms, based on a variety of kinds of relationships, some of which are one-sided.
We propose tagging people as a lightweight mechanism for managing relationships in social software. By tagging people in their social network, users can define egocentric groups of friends or collaborators, to which they can grant or deny access to various pieces of information in their personal space. Each new tag applied to a person has a distinctly specifiable visibility, and people tagged with the same key word form a relationship group that can be used as an access control option for each piece of information.
http://www.iasummit.org/proceedings/2008/tagging_five_emerging_trends
Tagging has been the subject of much discussion over the last several years, including many IA Summit presentations. But recent trends show that tagging is evolving quickly, and that today's conventional wisdom might not be accurate for long.
This session will explore five counterintuitive tagging trends that provide a glimpse into the next generation of user-generated classification.
The five trends are:
* The market wants structure. The next wave of tagging systems impose more structure and accept less ambiguity in tags.
* A pace for all layers. Pace layering suggests that tags are a fast-moving form of metadata, while facets and taxonomies are more stable, slower layers. But recent research and practice suggest that tagging patterns are often quite stable, and that tagging systems can operate across multiple pace layers.
* Automanual folksonomies. While most folksonomies are generated by analyzing statistical patterns in tags, new approaches mix manual and automatic approaches to yield better results.
* Communities matter. Some people have suggested that tagging works best when it's done for personal reasons. But it appears that the community around a tagging system is a major contributor to its health and success. Active communities like the one at ~LibraryThing can help create robust and useful tag sets.
* User-generated innovation. Where tags are implemented alongside data feeds a remarkable pattern of user-generated innovation occurs. Tags and feeds create a simple read-write system for any web application, allowing users to freely hack new features and extend the application. While this isn't news exactly, the consistency of this pattern across significantly different tagging systems suggests that it's important.
The session will consist of real-world examples, sprinkled with academic theory, used in the book "Tagging".
This poster describes an ongoing investigation aimed at understanding users’ motivations and behaviour when utilizing social tagging models to manage (acquire, organize, maintain, and retrieve) their personal and social information space. We employed both quantitative measures and qualitative research methodologies to analyze data gathered from users’ interaction with a social tagging application (http://www.opntag.net) using surveys, one-to-one interviews, and system automated data interaction logs. Qualitative research methodologies are used to do an in depth study of the participants’ behaviour as they use this social tagging application to discover structures, circumstances, and dependencies. Quantitative measures are utilized to develop statistical accounts of application usage by the participants.
/***
''Plugin:'' TagglyTag Cloud Macro
''Author:'' Clint Checketts
''Source URL:''
//Note the macro name was changed to stop it from clashing with the original TagCloud plugin//
!Usage
<<tagglyTagCloud excludeSearch excludeLists>>
!Code
***/
//{{{
version.extensions.tagglyTagCloud = {major: 1, minor: 0 , revision: 0, date: new Date(2006,2,4)};
//Created by Clint Checketts, contributions by Jonny Leroy and Eric Shulman
config.macros.tagglyTagCloud = {
noTags: "No tag cloud created because there are no tags.",
tooltip: "%1 tiddlers tagged with '%0'"
};
config.macros.tagglyTagCloud .handler = function(place,macroName,params) {
var tagCloudWrapper = createTiddlyElement(place,"div",null,"tagCloud",null);
var tags = store.getTags();
for (var t=0; t<tags.length; t++) {
for (var p=0;p<params.length; p++) if (tags[t][0] == params[p]) tags[t][0] = "";
}
if(tags.length == 0)
createTiddlyElement(tagCloudWrapper,"span",null,null,this.noTags);
//Findout the maximum number of tags
var mostTags = 0;
for (var t=0; t<tags.length; t++) if (tags[t][0].length > 0){
if (tags[t][1] > mostTags) mostTags = tags[t][1];
}
//divide the mostTags into 4 segments for the 4 different tagCloud sizes
var tagSegment = mostTags / 4;
for (var t=0; t<tags.length; t++) if (tags[t][0].length > 0){
var tagCloudElement = createTiddlyElement(tagCloudWrapper,"span",null,null,null);
tagCloudWrapper.appendChild(document.createTextNode(" "));
var theTag = createTiddlyLink(tagCloudElement,tags[t][0],true);
theTag.className += " tagCloudtag tagCloud" + (Math.round(tags[t][1]/tagSegment)+1);
// theTag.setAttribute("tag",tags[t][0]);
}
};
setStylesheet(".tagCloud span{height: 2.5em;margin: 3px;}.tagCloud1{font-size: 1.3em; color:#dcf4b6;}.tagCloud2{font-size: 1.6em; color:#b7cc8e;}.tagCloud3{font-size: 1.9em; color:#98b55b;}.tagCloud4{font-size: 2.2em; color:#5c7133;}.tagCloud5{font-size: 2.5em;font-weight: bold; color:#5c7133;}","tagCloudsStyles");
//}}}
http://www.iasummit.org/proceedings/2008/taxonomy_and_user_experience
In the past couple of years, much attention has been paid to user-organized, user-generated content. There has even been a certain amount of talk about the end of taxonomies. But in spite of the rise of tagging and wikis, taxonomy has not decreased in importance. Indeed, it appears that taxonomies are becoming more important to the work we do as metadata and ontologies extend their reach further into the user experience.
This presentation has three goals:
* to demonstrate the virtues of thinking of taxonomy in terms of the user experience and not simply as data or classification
* to introduce ways of talking about taxonomy that clearly communicate its value to the business and help promote taxonomy as a practice
* to illustrate how to craft a user-centric taxonomy by examining several e-commerce redesign case studies
Attendees will also be presented with both a conceptual framework and examples for understanding taxonomy as user experience that can be leveraged when discussing taxonomy with the business to create buy-in.
The overall presentation will be kept to 30 minutes to allow open discussion about the challenges and successes audience members have experienced during their own taxonomy projects.
The presentation is best suited for beginner and intermediate practitioners; however, all IA practitioners will benefit from discussion on selling taxonomy.
http://www.iasummit.org/proceedings/2008/testing_for_advertising_effect
Many times we do user testing to ensure that a site we have designed meets the needs of the users to find information or interact with an application- we want it to be usable and useful. The advertising placed on the site is an afterthought and usually placed in the design as unobtrusively as possible.
What if the role of user research was to identify how far the organisation could go when it came to placing advertising on the site? If the goal of the user research was to ensure that it did not negatively impact the users or reduce the brand values of the site? How does that affect the way user research is performed and the recommendations made back to the client?
Taking lessons learnt from working with government organisations in the UK, I will discuss how advertising user testing differs from normal user testing; from how to meet the testing goals to the choice of advertising models and the way we develop scripts. I will also discuss how the reactions of the users in the testing (focusing on the advertising and the brand) can be generalised and applied to web sites considering applying advertising.
When successfully (re-)designing a website the design-team’s objective should be to aim for a close match between how people work and how they use the internet. Continuously asking yourselves ‘what do people want’? If you aren’t able to answer this question for a piece of functionality that’s being designed it shouldn’t make it in.
To find these answers, this poster shows a number of techniques to involve as many people as possible and walks through the steps to perform in order to achieve this involvement. Starting off with asking people questions in surveys on what’s important to them and what they prefer and analyzing these results in prioritized user scenarios. And once there is something to show: collect feedback by making use of early prototypes, whether in person or via test sites that are connected to analysis software.
The UX Funnel condenses this process into 8 discrete steps which are easily applicable to any UCD project and gives short practical explanations on how to implement them.
http://www.iasummit.org/proceedings/2008/the_business_of_experience_the
Increasing our influence in the organizations we work with is a challenge we all face. That influence comes when we find the right opportunities and actions for our own situations. Threading the maze of business can be daunting – but we don’t need an MBA to be an agent of change.
The experience impact framework offers a simple tool that helps ~IAs understand the kinds of impact user experience practice can have on business.
The experience impact framework shows the intersections between business and user experience practice, and highlights areas where ~IAs and others can build on their current work to extend their influence. By diagnosing the situation, recognizing the underlying patterns, and integrating more influential activities into their practice, ~IAs will improve their position and contributions to their clients and organizations.
The experience impact framework includes three dimensions:
* The elements of business
* The fundamentals of user experience practice
* The kinds of impact we can have
These components and the resulting framework will be explained through concepts and case studies.
To conclude the session, the presenter will then call on the audience to discuss one or more of their own situations using the framework, illustrating its use as a pragmatic diagnostic tool that can suggest real opportunities and activities.
http://www.iasummit.org/proceedings/2008/the_impact_of_social_ethics_on
This presentation discusses ethics in IA from a practical point of view. Through different case studies we illustrate the impact of social ethics on IA and interactive design, and sum up our experiences on dealing with ethics in real projects.
~E-Commerce for the Norwegian Alcohol Retail Monopoly
In this project we had to interpret the Norwegian alcohol legislation (which is very restrictive) as well as Norwegian ethics of drinking. The solution is balancing the tightrope between legislation, social ethics and technical and conceptual possibilities.
E-commerce with Products Targeted Towards Children
In this project we have interpreted the Norwegian ethic codes regarding marketing towards children. Marketing towards children is prohibited in some marketing channels, but there are no specific regulations within interactive media.
Solution for Buying ~CO2 Quotas from The Norwegian Pollution Control Authority
In this project we have considered the social ethics of environmental issues and of buying and selling ~CO2-quotas on the Internet.
In our opinion these cases show that interactive design in one way or another always is based on interpretation of ethical rules, expressed or latent. IA and design is bound by cultural imperatives, and this is a fact we cannot ignore.
The presentation should be useful for ~IAs and designers working with real life solutions.
http://www.iasummit.org/proceedings/2008/the_information_architect_and
A fighter pilot and military strategist, the late John Boyd is considered by some to be the most important strategic thinker since Sun Tzu. His influence has been felt in the military community as well as the business world, with an increasing number of successful business leaders claiming his influence in their approaches to strategic thinking.
With much of his thinking based on the notion of conflict, Boyd’s ideas seem to be contrary to the way in which information architects engage in the design of experiences. This couldn’t be further from the truth; Boyd’s thinking can teach us a great deal about how to understand, interpret and design for human decision-making. In particular, his ideas on trust, communication and group interaction are extremely relevant to the contemporary information architect.
While Boyd’s ideas will have multiple applications for information architects, one of the most intriguing areas of interest is the design of social networks and emergent software. A common theme in Boyd’s work is the design of behavior for group situations and his ideas have considerable value in the context of informing strategy and design for technology-mediated social environments.
This presentation is targeted at all levels of practitioners, but will be of most interest to intermediate and advanced information architects who are looking to bring deeper perspectives to their design practices
http://www.iasummit.org/proceedings/2008/the_long_wow
Customer loyalty — the idea that a customer will return to you repeatedly — is a hot topic these days. It’s been in the spotlight ever since business author Frederick Riechfield introduced the "Net Promoter Score," a simple calculation used to measure the loyalty of your customers.
Although it’s become easier to measure customer loyalty, it's just not that simple to create it. Rewards cards, frequent-whatever-programs, and other artificial attempts at customer loyalty just get in the way. Instead, engaging customers in more meaningful relationships over time is what builds true loyalty. And that is where well-planned, notably great experiences can play a big role in business.
This presentation lays out an experience-centric approach to fostering and creating loyalty by systematically impressing your customers again and again. The Long Wow challenges creators of customer experiences to plan across channels, time, and disciplines to identify a progression of seduceable moments.
Together, we'll take a fun look at long wow experiences from inside and outside of the field of Information Architecture, extracting from these examples what is "wow" and how it can be planned for and sustained.
For practitioners and mangers asked to deliver competitive customer experiences, this presentation will supply a framework for tackling customer loyalty challenges with user experience solutions.
Thom Haller, teacher, speaker, writer, and user advocate—teaches principles of performance-based information architecture and usability. Since 1998, Thom has taught classes on architecting usable Web/Intranet sites. As a teacher, Thom enables students to structure information so people can find it, use it, and appreciate the experience. A noted speaker and facilitator, Thom is funny, passionate, and inclusive. He creates change in organizations, infusing his optimism and showing how we can make the complex clear.
| | ![[Flagler / Monroe]] | ![[Brickell]] | ![[Tuttle]] | ![[Flex: Orchid C/D]] |
| [[8:00 - 8:30AM|08:00 - 8:30AM]] |>|>|>| Registration |
| [[8:30 - 5:30PM|08:30 - 5:30PM]] |>|>|>| ~Pre-Conference Workshops |
/***
|Name|TiddlerDisplayTopPlugin|
|Location|http://www.orst.edu/~woodswa/tiddlywikiplugs.html|
|Version|1.0|
|Author:|Walt Woods|
|Requirements:|Should NOT be used in tandem with SinglePageModePlugin.|
!Description
Keeps the tiddlers display looking fresh by opening new tiddlers at the top of the page. This keeps toolbars and menus accessible at all times, while allowing for multiple tiddlers to be open.
!History
08-06-2007: Initial version.
!Code
***/
//{{{
version.extensions.TiddlerDisplayTopPlugin = {major: 1, minor: 0, revision: 0};
Story.prototype.displayTiddlerTiddlerDisplayTop = Story.prototype.displayTiddler;
Story.prototype.displayTiddler = function(srcElement,title,template,animate,slowly)
{
if (story.hasChanges(title))
{
this.displayTiddlerTiddlerDisplayTop(srcElement,title,template,animate,slowly);
}
else
{
story.closeTiddler(title);
this.displayTiddlerTiddlerDisplayTop(null,title,template,animate,slowly)
var tiddlerElem = document.getElementById(this.idPrefix + title);
if (animate)
anim.startAnimating(new Zoomer(title,srcElement,tiddlerElem),new Scroller("top"));
}
}
//}}}
Tingting Jiang is a third-year Ph.D. student at the School of Information Sciences, University of Pittsburgh. She began to study information architecture as an undergraduate student and continued to pursue her academic interests during her master’s degree which resulted in a thesis entitled Evaluating the Information Architecture of University Websites. Her current professional experience includes working as a public reference service assistant for the University of Pittsburgh Library System where her responsibilities are offering direction in online search and digital library use, among others. These combine with her doctoral research that focuses on exploratory search and information architecture. She has a teaching background with experience in the graduate-level course Information Architecture, taught by Dr. Sherry Koshman, her dissertation advisor.
Todd Zaki Warfel is President and founder of Messagefirst, a Philadelphia-based design research consulting firm, where he blends research and design to evolve products in innovate and beautiful ways. Todd is a dynamic speaker and storyteller by nature. He’s rarely short on details. He is an active member in a number of industry communities and organizations, including the Information Architecture Institute, ~IxDA, and UPA.
Todd’s clients have included Albertsons, AT&T Wireless, Bankrate, Bank of America, ~CitiGroup, Comcast, Cornell University, ~IntraLinks, Hartford, Motorla, Palm, Sallie Mae, and SBC. Todd currently lives in Philadelphia, blogs at toddwarfel.com, and is currently working on a book on prototyping with Rosenfeld Media "A Practitioner's Guide to Prototyping" available in 2008.
/***
An under construction replacement for toggleTag
<<tTag mode:text text:D tag:Done>>
<<tTag mode:text text:N tag:Next>>
***/
//{{{
merge(config.macros,{
tTag: {
createIfRequired: true,
shortLabel: "[[%0]]",
longLabel: "[[%0]] [[%1]]",
handler: function(place,macroName,params,wikifier,paramString,tiddler) {
var parsedParams = paramString.parseParams("tags",null,true);
if (!tiddler)
tiddler = store.getTiddler(getParam(parsedParams,"title"));
var tag = getParam(parsedParams,"tag","checked");
var title = getParam(parsedParams,"title",tiddler.title);
var refreshAll = getParam(parsedParams,"refreshAll",false);
var defaultLabel = (title == tiddler.title ? this.shortLabel : this.longLabel);
var label = getParam(parsedParams,"label",defaultLabel);
var theTiddler = title == tiddler.title ? tiddler : store.getTiddler(title);
var mode = getParam(parsedParams,"mode","checkbox");
var theClass = getParam(parsedParams,"class",tag+"Button");
var currentValue = theTiddler &&
(macroName == "tTag" ? theTiddler.isTagged(tag) : store.getValue(theTiddler,tag)=="true");
if (mode == "checkbox") {
// create the checkbox
var cb = createTiddlyCheckbox(place, label.format([tag,title]), currentValue, function(e) {
if (!store.tiddlerExists(title)) {
if (config.macros.tTag.createIfRequired) {
var content = store.getTiddlerText(title); // just in case it's a shadow
store.saveTiddler(title,title,content?content:"",config.options.txtUserName,new Date(),null);
}
else
return false;
}
//store.suspendNotifications();
if (macroName == "tTag")
store.setTiddlerTag(title,this.checked,tag);
else // it must be tField
store.setValue(title,tag,this.checked?"true":null);
if (refreshAll) {
story.forEachTiddler(function(title,element) {
if (element.getAttribute("dirty") != "true")
story.refreshTiddler(title,false,true);
});
}
//store.resumeNotifications();
return true;
});
}
else if (mode == "text") {
var text = getParam(parsedParams,"text","X");
var cl = createTiddlyButton(place, text, text, function(e) {
if(!e) var e = window.event;
if (!store.tiddlerExists(title)) {
if (config.macros.tTag.createIfRequired) {
var content = store.getTiddlerText(title); // just in case it's a shadow
store.saveTiddler(title,title,content?content:"",config.options.txtUserName,new Date(),null);
}
else
return false;
}
//store.suspendNotifications();
var currentState = this.getAttribute("state")=="true";
var newState = !currentState;
store.setTiddlerTag(title,newState,tag);
if (macroName == "tTag")
store.setTiddlerTag(title,newState,tag);
else // it must be tField
store.setValue(title,tag,newState?"true":null);
// this is terrible please refactor
if (currentState) {
cl.setAttribute("state","false");
removeClass(cl,"on");
addClass(cl,"off");
}
else {
cl.setAttribute("state","true");
removeClass(cl,"off");
addClass(cl,"on");
}
//refreshDisplay();
if (refreshAll) {
story.forEachTiddler(function(title,element) {
if (element.getAttribute("dirty") != "true")
story.refreshTiddler(title,false,true);
});
}
//store.resumeNotifications();
e.cancelBubble = true;
if(e.stopPropagation) e.stopPropagation();
return false;
});
addClass(cl,theClass.replace(/ /g,''));
if (currentValue) {
cl.setAttribute("state","true");
removeClass(cl,"off");
addClass(cl,"on");
}
else {
cl.setAttribute("state","false");
removeClass(cl,"on");
addClass(cl,"off");
}
}
else if (mode == "popup") {
var cl = createTiddlyButton(place, "zzz", text, function(e) {
// props to Saq
if(!e) var e = window.event;
var popup = Popup.create(this);
createTiddlyButton(createTiddlyElement(popup,"li"),"foo","bar",function(e) {
// under contruction
alert(this.getAttribute("tag"));
});
Popup.show(popup,false);
e.cancelBubble = true;
if(e.stopPropagation) e.stopPropagation();
return false ;
});
}
}
}
});
config.macros.tField = config.macros.tTag;
setStylesheet(["",
".button.off {border-style:none;background:#fff;color:#ccc;}",
".button.on {border-style:none;background:#ddd;color:#000;}",
// TODO move this css elsewhere
"#realmSelector .button.off {margin:0 0.5em;padding:0 1em;border:2px solid #aaa;background:#eee;color:#333;}", // actually reversed, ie off is "on"
"#realmSelector .button.on {margin:0 0.5em;padding:0 1em;border:2px solid #999;background:#999;color:#ccc;}", // actually reversed, ie off is "on"
""].join("\n"),"tTag");
//}}}
Tone Terum works for the Norwegian company, Halogen, as an Information Architect. She specializes in the optimization of user experience in digital media. Terum is one of three authors who published the very first WAP guidelines (2000) and holds an MA in psychology.
[img[http://students.washington.edu/adcockm/IASummit/Hyatt_3.png]]
<<tagging>>
Other interactions deliver experiences, not just Web- or computer-based ones. In my recent life, I've been able to combine passions for both user experience consulting and thought with a love for motorcycling. In addition, when I ride my bike, I'm often struck at how much sheer experience is part of the activity.
In this presentation, I'll take a quick look at the motorcycling experience from my perspective. I'll then talk about controls and the differences between conventions versus some unconventional design choices -- and what implications they have on the experience itself. I'll use my knowledge of and experience with recent Moto Guzzis for examples.
Finally, I'll draw some contrasts between business dashboards that use automotive metaphors and the motorcycle experience of using dashboards and controls.
This presentation should resonate with participants of all levels who are interested in experience away from the computer.
[img[http://students.washington.edu/adcockm/IASummit/Hyatt.png]]
<<tagging>>
!!Creating My Schedule
#''Browse through the content and decide which sessions you are interested in...''
##The links to each day's schedule at the top of the page are a good place to start.
##You could also search for specific concepts and keywords using the search box.
#''When you find an interesting session, click the Toggle favorite button...''
##It's located right above the tags assigned to the item, on the right of the content area.
##If you have marked an item as a favorite, a [[star]] <<star>> will appear before the title.
#''//Save changes!!! ^^0^^//''
#''Click the [[My Schedule]] link at the top of the page, and you'll see your custom schedule!''
##Notice that //matching// time slot conflicts^^1^^ are shown in red. You shouldn't be in two places at once, silly!
!!Using Tags to Navigate
*''Each item^^2^^ in view may have tags associated with it.''
**You may have noticed them in the gray boxes on the right.
**Click them!
*''Tags let you pivot between related information items, but you probably knew that already!''
**For instance, each session is tagged with speaker(s), a time slot, room, and day.
**Click on the speaker name tag attached to a session and you can quickly jump to other talks or posters they are doing.
**You can always get back to where you came from by jumping around with tags.
**Stalk your favorite IA peeps! See what else is going on in the same room! Remind yourself of the days of the week!
!!Finding Aids and Navigation
*''All the items you currently have open will be displayed at the top of the page.''
**Click on one of these links to bring the item to the top of the page, for easy sorting and access.
**When you close an item, it will disappear from the top. //Oh no!// But don't worry, you'll be able to find it again...
*''Have you noticed the search box? Isn't it inviting?''
**It searches all^^3^^ the content in the ~TiddlyWiki.
**Just start typing and the search will be performed in realtime.
**For instance, type in ''metadata'' and you'll find a speaker guy and some sessions. //Easy, huh?//
*''You probably want a tag cloud, don't you?''
**Well, ok. Since you asked nicely... Here is your [[Tag Cloud|TagCloud]].
*''The main links in the header will always be around to help you if you get lost, so never fear!''
!!Additional Controls
*''Each //tiddler// item has some links at the top.''
**You can probably figure out most of them so I won't go into details here...
*''There are a few control links under the search box too.''
**Again, you should be able to figure them out!
!!Feeling Clever?
*''Create a new tiddler using the link^^4^^ under the search box.''
**Don't worry, unless you messed around with the ''options'', a backup will be saved every time you ''save changes''.
*''You can find other ways to dig in and get into trouble under the //tabs// area on the right.''
*''The //backstage// area, accessible from the link at the top right will let you do all sorts of exciting and dangerous things!''
*''You should really look around on the web for more information about ~TiddlyWikis before you start breaking things. Just [[Google|http://www.google.com/search?q=tiddlywiki]] it. There is lots if information out there!''
^^0. If you access this file on a webserver, you won't be able to save your changes. See note 4.^^
^^1. Sadly, conflicts resulting from overlapping times that do not share identical timeslots are not shown. But you're smart so you can figure it out!^^
^^2. Each item is actually called a //tiddler// in the world of ~TiddlyWiki. Silly isn't it?^^
^^3. Ok, you got me. I lied. It doesn't search everything. It's not going to search in the custom code I wrote, or the plugins I imported, or CSS styles, etc. But you don't want to look for that anyway //do you??//^^
^^4. If you save this file on a website, the edit features will be disabled. This ~TiddlyWiki is meant to be edited and used locally, but if you just want to view your content, you can put it up on the web somewhere.^^
Vanesa Mirzaee is a Ph.D. Candidate in the Department of Electrical and Computer Engineering at the University of British Columbia. Her research interests include semantic web and ontologies, personal information management, personal and social tagging.
Vera Rhoads has been working on optimizing web solutions for large-scale Fortune 500 companies and non-profits (Fannie Mae, AARP, IMF) for 15 years.
Vera’s specialties include web strategy and operations, next-generation web site evolution, usability, branding, multi-lingual globalization, web content management and search implementations. She is PMP certified and works on enhancing process methodologies into the web development lifecycle.
Vera is an also adjunct faculty member at the Graduate School of the University of Maryland.
<!--{{{-->
<div class='toolbar' macro='toolbar closeTiddler closeOthers +editTiddler > fields syncing permalink references jump'></div>
<div class='titlemarker' macro="showWhenTagged favorite"><div class='titlemarker' macro="star"></div> </div><div class='title' macro='view title'></div>
<div class='subtitle'></div>
<div class='tagged' macro='tags'><div macro="showWhenTagged session"><div class='toggle' macro="tTag mode:text text:'Toggle favorite' tag:favorite"></div><hr/></div></div>
<div class='viewer' macro='view text wikified'></div>
<div class='tagClear'></div>
<!--}}}-->
Tag clouds are visualization tools utilized in social tagging systems to help users retrieve tagged resources as well as recognize relationships among tags. Currently tag clouds use varying font sizes to visually differentiate between frequency of tag use, with the most frequent tag being displayed in a large font. Although tag clouds are extremely useful, they do not adequately address problems related to tag aging. The flexibility of tagging systems allows users to rapidly adopt new terms and engage in extremely dynamic tagging practices, yet tag clouds are not able to represent agile shifts in tagging patterns. This poster will first present an overview of the problems related to tag aging such as semantic drift, changes in tagging patterns, and linguistic shifts, as well as present alternative tag cloud visualizations that specifically incorporate concepts of tag aging and decay.
http://www.iasummit.org/proceedings/2008/web_site_maturity_cycles
How does your web site stack against the best of breed and your competition? How can you convince upper management of that? A proper maturity rating could be the answer. If you build a hugely successful web site could you keep repeating your success?
The Web Site Maturity Model presents a comprehensive evaluation framework using a repeatable model for measuring the quality of a web site through a hierarchical, evolutionary model with distinctly defined stages of the web site existence. Traditionally, a maturity model is a method for judging the maturity of the processes of any organization and for identifying the key practices required to increase the maturity of such processes. Extending upon well known models such CMM the Web Site Maturity model applies directly to the web.
The model was developed based on extensive practical experience and academic research. The methodology for applying the model, a step-by-step roadmap and toolkit for the Web Site Maturity Model will be discussed as well.
During this presentation you will learn how to benchmark your web site against the model and how to derive direct business value from it.
While a maturity model presentation can be a rather dry affair, the practical advice and the shared experience from the trenches of each level bring out the specifics of the model vividly to life.
http://www.iasummit.org/proceedings/2008/web_use_recorders_the_future_o
This presentation will examine web use recorders, a new technology for unobtrusively monitoring web usage that has the potential for dramatically improving web analytics. Web use recorders characterize the actions of web users on a particular site in fine-grained detail, not just page visits and time spent on a given page, but where clicks occurred, scrolling, and cursor hovering without clicking. The recording is server-side, automated, and transparent to the user. To date, the commercial products based on this capability offer the ability to “playback” individual web browsing sessions, provide rudimentary compilations of summary metrics, and display “heatmap” visualizations of the density of clicks and hovers.
Our presentation will explore the potential for this capability to provide a new generation of web analytic tools for providing insights into naturalistic user behaviors and design quality. We will show examples of the data provided by web use recorders, contrast them with conventional web analytic tools, speculate about their potential for providing insights regarding user experiences and usability, and suggest the kinds of research that are needed to fully realize this potential. We will review some of the research that has already been reported using web recorder technology and show examples from our own initial attempts to explore the utility of this capability.
http://www.iasummit.org/proceedings/2008/what_are_your_users_really_thi
Information architects need to quickly characterize audiences. Through Howard Gardner’s theory of multiple intelligences, we can better understand the way different people experience information. Because people are intelligent in a number of ways (e.g. “word smart,” “music smart,” or “picture smart”), they exhibit different behaviors when interacting with information.
This session will demonstrate how Q Methodology can be used to identify the extent to which multiple intelligences exist in an audience. Using that characterization, we can then have solid data on which to build personas, services, or content. The power of Q Methodology lies in the fact that users are forced to make subtle distinctions among the range of the concourse, thus revealing latent subjective judgments.
Prior to the presentation, we will conduct a Q sort on volunteers attending the conference using stimuli that will reveal tendency toward particular intelligences. The results of the Q sort will be presented. The discussion will include how the results could be applied to the development of personas. In addition, we will explain how Q Methodology captures subjectivity, the steps involved in the process, and how the analysis is performed.
http://www.iasummit.org/proceedings/2008/what_do_innovative_intranets_l
Intranets are almost always hidden from view. While good work is being done on these sites, there is little opportunity for new approaches to be shared. With web 2.0 driving innovation on the web, there is increasing pressure to answer the question: what do innovative intranets look like?
In late 2007 the winners of the inaugural Intranet Innovation Awards were announced. With submissions from across the globe, the winning entries represented the US, UK, Italy, Denmark, Switzerland, Australia and New Zealand.
The goal of the awards was to uncover innovative approaches to the design and delivery of intranets. Uniquely, the awards focused on individual improvements, not intranets as a whole. The field of information architecture has become increasingly engaged with intranets, and their ability to deliver clear business benefits. Beyond ‘best practice’ usability principles, there is much yet to explore about intranets.
This talk provides insights into the winning entries, and provides ‘lessons learnt’ for organisations looking to drive innovation via their intranet.
http://www.iasummit.org/proceedings/2008/why_markets_love_the_internet
Since virtually anything can be purchased or traded for on the internet, it’s worth reviewing some basic economic concepts about markets, and how companies try to position themselves within the marketplace online. We’ll talk about concepts such as information costs, experience goods, lock-in, switching costs, signaling, perfect markets, liquidity, and others, and discuss how they influence user experience design. Knowing a bit about economics not only makes you sound smarter (we hope), but can help you bring increased value to any project.
Yvonne has been a UX consultant for 10 years. Some of the User Experience Champions that Yvonne has raised come from the Fortune 500 clients and government agencies that she has worked with. Before that, Yvonne was a human factors researcher at Defence Research and Development Canada, where she specialized in human performance within extreme environments. Yvonne earned her undergraduate degree at the University of Toronto, and her Masters in Ergonomics from University College London.
!!Welcome!
The [[Information Architecture Summit|http://www.iasummit.org/2008/]] takes place from ''Thursday, April 10th to Monday April 14th'' in Miami, Florida at the [[Hyatt Regency|http://miamiregency.hyatt.com/hyatt/hotels/index.jsp]].
[[Adriana Machado|http://iasummit08.crowdvine.com/profiles/11694]] was kind enough to provide this great [[map of the conference|http://maps.google.com/maps/ms?hl=en&gl=us&ptab=2&ie=UTF8&oe=UTF8&msa=0&msid=116492361552105426707.000447e29c04ff8b250dc&ll=25.775933,-80.188265&spn=0.041892,0.068836&z=14]] and surrounding area, showing alternative hotels, restaurants, and other points of interest.
This [[TiddlyWiki|http://www.tiddlywiki.com/]] was designed to help you easily review the [[sessions|session]] available and create your own [[custom schedule|My Schedule]]!
!!!!Download it here: http://students.washington.edu/adcockm/IASummit/IASummit2008.html //(Right click, save, you know the drill...)//
!!Features
Complete information^^1^^ about the conference is provided:
*[[schedule|schedule]],
*[[sessions|session]],
*[[speakers|speaker]],
*[[posters|poster]],
*[[poster presenters|poster presenter]], and
*[[locations|location]]. (Maps for each location will be displayed if you are online.)
The links at the top of the page provide ''schedule grids'' for each of the conference days. The ''tags'' for each item will provide direct links to similarly tagged items. The ''search box'' on the right will search the entire text content of the ~TiddlyWiki. Since this is a ''single HTML file'', it is very ''portable'' and can be carried on a flash drive. It should be compatible with any modern browser including ''~FireFox'', ''IE'', ''Safari'', and ''Opera''. The //clever user// may ''customize'' things, ''track interesting sessions'', make notes by ''editing'', and more...
You can find additional help and ideas here: [[Usage Examples]]
!!About the Designer
[[Michael Adcock|mailto:adcockm@u.washington.edu]] is a MLIS student at the University of Washington [[Information School|http://www.ischool.washington.edu/]], and expects to graduate in the summer. He still doesn't have a proper website, but will soon. In the mean time, you might want to check out the [[TiddlyThesaurus|http://students.washington.edu/adcockm/amateurastronomythesaurus/]] he created for a course project. Or perhaps you'll take a look at a site he created for the [[iEdge conference|http://students.washington.edu/adcockm/iEdge/iEdge.html]] (which is surprisingly similar to this one -- coincidence?) He has been fond of ~TiddlyWiki for a while now, and created this iA SUMMIT tool in his spare time so he'd have an easy way to manage his conference experience. He makes no claims on the content, as it was lifted from the official [[iA SUMMIT site|http://www.iasummit.org/2008/]]. (Please don't sue me!)
!!Acknowledgements
I made use of a few [[plugins|Acknowledgements]] when designing this site.
Also, I'd like to thank [[Eric Reiss|http://iasummit08.crowdvine.com/profiles/13405]] and [[FatDUX|http://www.fatdux.com]] for offering scholarships this year! It is very appreciated!!!
In addition to [[myself|http://iasummit08.crowdvine.com/profiles/11156]], I'd like to congratulate:
*[[Marie Joyce|http://iasummit08.crowdvine.com/profiles/13583]] (Kent State University)
*[[Tommy Keswick|http://iasummit08.crowdvine.com/profiles/14140]] (UCLA)
*[[Adriana Machado|http://iasummit08.crowdvine.com/profiles/11694]] (University of Baltimore)
*[[Tanya Rabourn|http://iasummit08.crowdvine.com/profiles/13089]] (University of Texas)
*James "JP" Sweeney (University of Michigan)
^^1. This ~TiddlyWiki does NOT contain detailed information about the ~Pre-Conference Workshops. As a poor student, I am not planning to go to any of them!^^
[img[http://students.washington.edu/adcockm/IASummit/Hyatt.png]]
<<tagging>>
[[Thursday 10th April|Thursday]]
8:00 am – 8:30 am Registration
8:30 am – 5:30 pm ~Pre-Conference Workshops
[[Friday 11th April|Friday]]
8:00 am – 8:30 am Registration
8:30 am – 5:30 pm ~Pre-Conference Workshops
6:30 pm – 8:30 pm Welcome Reception
[[Saturday 12th April|Saturday]]
8:00 am – 8:30 am Registration
8:30 am – 5:45 pm Conference
6:00 pm – 8:00 pm Reception & Posters
[[Sunday 13th April|Sunday]]
9:00 am – 5:15 pm Conference
[[Monday 14th April|Monday]]
8:30 am – 4:45 pm Conference
See if you can figure out how the star image (<<star>>) is stored!
Hints:
*It's //NOT// linked to an external image.
*It's //not// stored as a local image file.