Comments (0)

By rphillippi, March 15, 2009 10:30 pm

I went to the SF Redux of Interaction 09 and had a great time not only getting to know some new people but also learning more about Interaction Design. Here’s some quick thoughts and notes of what I saw:

——

Steve Portigal was up first to walk us through his sold out workshop called, “Well, we did all this research … now what?”

My Twitter Feeds on SP:

“Who cares about terminology. Examine, infer and apply to business or design.” I’d say apply to both. Why should they be different.

“Stay out of solution land. Try different methods”

When stuck come up with really bad ideas to encourage creativity.

——-

Second was Kumi Akiyoshi with “Feeling: What Makes an Engaging Product?“.  The slides from the presentation are below:

Third was Ian Swinson with “Postcard Patterns”.

Postcards = simple straight forward messaging

——-

Fourth was Nadya Direkova with “What’s in a game? A look at game design best practices as prime influencers of interaction design.”  The slides from the presentation are below:

Twitter:

Is google a single player or multiplayer game? How many of us get to design apps in 3d?

This is review so far. It’s all about the same from my game design class at Parsons.

Simply controls. Friend invites to play with friends. (AdverGames)

Create a reward in health. Physical Therapy… Doing # of exercises = whatever

——

Kim Goodwin “each one teach one” – people are now saying I experienced good design. This is easier than that.

Twitter:

“Nothing special about the iPhone. Technology is simple. It’s design they are selling. And we’re paying a lot of money for good design.”

“Corporate Americas new found belief in design is fragile.”

A lot of good ideas end up collecting dust. “It’s someone else’s fault. We need to take responsibility.”

Sales people understand progressive commitment. Get people involved in the research and so on to understand reasoning. Pushes commitment.

Even those who are use to rational decisions can be susceptable to emotion. (Ie the Mini Cooper)

Bargaining a normal part of Change Management. “I’ll have the salad with the cake.”

Ixd = generation creation

——

In summary -

Personal gripe: Another thing about less is more on presentation slides… Less information focuses the audience on you and what you are saying. Avoids info overload

At the bar afterwards: “We’re designing behaviour”

Comments (0)

By rphillippi, February 19, 2009 10:27 pm

This is a great article defining IA Principles:

————————–

Information architects still struggle to define the design principles that operate in their environment. Today I would like to give a set of design principles that was developed with an Information Architect a while ago. Design principles are not necessarily right or wrong but should be an accurate reflection of the fundamentals that guide decision making in an enterprise. The following should therefore not be seen as design principles fixed in concrete but rather as examples of business principles. Best practice is to define the design principle in terms of its Benefits and rationale as well as the implication to the enterprise and the counter argument expressing the potential negative impact of the design principle.

Design principle 1: Central management information

Description

All management information and business intelligence will be sourced from a single consolidated source of information

Benefits
• A central source of management information will provide the enterprise with a wide breath of reporting and analysis without being constraint by the organisations functional structuring.
• Users will become used to a single interface to management information allowing managers to become familiar with the infrastructure and extracting maximum benefit from all information available in the organisation.
• The central information will eliminate contradicting information sources and ensure accurate reporting of current affairs and identification of issues and opportunities.
• Increase the flexibility and manageability of providing information rapidly and effectively to support business decisions.
• Use best of breed analytic functionality to support management decision making
• Increased security in managing access to The enterprise’s management information

Implications
• Information must be sourced to the central information infrastructure from all the various operational applications as close to real time as possible
• No additional analytical modules are required for transactional applications.
• The interface to management information and training should be rolled out to all decision makers to effectively access information.

Counter argument
• The central management information might not be adequate in situations where real time analytics of transactional information is needed
• Information in the central information source might not be structured for a specific requirement and the development time might be too long to provide the information in time for a once off request.
• The assumption cannot be made that a single tool will satisfy all the information requirements. The information infrastructure will therefore consist of a variety of integrated tools.

Continue reading “Information Architecture Principles” »

Comments (0)

By rphillippi, August 20, 2008 12:18 pm

Claudia points out the advantages and disadvantages of Flexible Content Models in this presentation.

Comments (0)

By rphillippi, September 6, 2007 3:00 pm

I get that question a lot so in hopes to answer that question the following is taken from O’Reilly Press’s “Information Architecture for the Web, 2nd Edition”:

in·for·ma·tion ar·chi·tec·ture n.

1. The combination of organization, labeling, and navigation schemes within an information system.
2. The structural design of an information space to facilitate task completion and intuitive access to content.
3. The art and science of structuring and classifying web sites and intranets to help people find and manage information.
4. An emerging discipline and community of practice focused on bringing principles of design and architecture to the digital landscape.

—————————- More Definitions ————————————

Information

We use the term information to distinguish information architecture from data and knowledge management. Data is facts and figures. Relational databases are highly structured and produce specific answers to specific questions. Knowledge is the stuff in people’s heads. Knowledge managers develop tools, processes, and incentives to encourage people to share that stuff. Information exists in the messy middle. With information systems, there’s often no single “right” answer to a given question. We’re concerned with information of all shapes and sizes: web sites, documents, software applications, images, and more. We’re also concerned with metadata: terms used to describe and represent content objects such as documents, people, processes, and organizations.

Structuring, Organizing, and Labeling

It’s what information architects do best. Structuring involves determining the appropriate levels of granularity[2] for the information “atoms” in your site, and deciding how to relate them to one another. Organizing involves grouping those components into meaningful and distinctive categories. Labeling means figuring out what to call those categories and the series of navigation links that lead to them.

[2] Granularity refers to the relative size or coarseness of information chunks. Varying levels of granularity might include: journal issue, article, paragraph, sentence.

Finding and Managing

Findability is a critical success factor for overall usability. If users can’t find what they need through some combination of browsing, searching, and asking, then the site fails. But user-centered design isn’t enough. The organizations and people who manage information are important too. An information architecture must balance the needs of users with the goals of the business. Efficient content management and clear policies and procedures are essential.

Art and Science

Disciplines such as usability engineering and ethnography are helping to bring the rigor of the scientific method to the analysis of users’ needs and information seeking behaviors. We’re increasingly able to study patterns of usage and subsequently make improvements to our web sites. But the practice of information architecture will never be reduced to numbers; there’s too much ambiguity and complexity. Information architects must rely on experience, intuition, and creativity. We must be willing to take risks and trust our intuition. This is the “art” of information architecture.

—————————- My Commentary ————————————

In summary, we, Information Architects, are the ones behind the scenes who lay out the content and information to be found in any web site. We are the ones who make it easier for all of you the users to find what you are looking for. Our work is seen in the layout (where the navigation, images, etc, is located on a page) of a web site or system.

What’s interesting about this is that library sciences is coming back in full force because of the amount of information at our fingertips and our need to categorize and organize it all into usable chunks. Librarians were doing this long before there was a web to be concerned about.

Comments (0)

By rphillippi, September 5, 2007 10:40 am

“On the Web, if a site is difficult to use, most people will leave. On an intranet, if employees perform their tasks more slowly due to difficult design, the company bears the cost of the reduced productivity. In fact, I estimate that low intranet usability costs the world economy $100 billion per year in lost employee productivity. This may not be the most important problem facing the planet, but it’s not a trifling issue either.

Usability is an important, though not the only, determinant for the success of a web site or an intranet. Information architecture is an important, though not the only, determinant for the usability of a design. There are other issues, but you ignore information architecture at your peril.

Critics may say that users don’t care about information architecture. They don’t want to learn how a web site is structured; they just want to get in, get their task done, and get out. Users focus on tasks, not on structure. But it’s because users don’t care about the structure of a web site that it is so important to get the information architecture right in the design. If users did bother to study our web sites, they could surely learn how an obscure or illogical structure works and utilize that knowledge to improve their task performance. Humans are flexible creatures and can adapt to hostile environments if they choose to do so.

But since we know that users won’t spend time learning our information architecture, we have to spend resources to design the best information architecture we can. Allow users to focus on their tasks, and let information architects be the ones to spend time worrying about the structure of the web site or intranet. This is a good division of labor, and the pay-off from good information architecture is immense. The more that answers are located in the places you look for them, the easier the design will feel to users, and the more successful the project. There will be more sales (for e-commerce sites), better reputation for good service (for marketing sites), and less loss of productivity (for intranets).

I am a great believer in having professional information architects design the structure of professional information projects such as corporate web sites and intranets. But I also think there will be an increasing role for personal information architecture in the future. It will soon be time to teach a simplified version of the discipline to high school students, and possibly even to bring it into elementary schools as well.

The modern world is one of information overload; we are constantly bombarded by an inflow of messages, and we ought to read much more information than we have time for. Keeping yourself from drowning in this morass of information will require personal information architecture skills for problems like structuring email folders and computer files as well as the ability to manage advanced search features.

In the long run, personal information architecture may turn out to be even more important than corporate information architecture. For now, though, read this second edition of Information Architecture for the World Wide Web and get your web site and intranet in shape to support your customers and employees. Good information architecture makes users less alienated and suppressed by technology. It simultaneously increases human satisfaction and your company’s profits. Very few jobs allow you to do both at the same time, so enjoy.”

Spoken by Jakob Nielsen
Quoted in “Information Architecture for the World Wide Web, 2nd Edition”