Social network aren’t only Web2.0 start up kind of site and we can use it is many different kind of application for companies : intranet employee social network, customer & supplier network, communities, customer care initiative, knowledge management tools, etc.
In order to deliver this kind of experience, information architects have to develop new skills and techniques. I have worked on five different social networks and I d like to share my experience in developing social web experiences in different context.
Through this presentation, I’m presenting critical elements to take in account during social network conception and answer to different questions : what are the specificities of information structure for social networks? what are the specificities of a social network user interface? what are the specific user behaviours to handle? Through my experience, I have identified some kind of behavioural patterns based on data observation and data mining How can we develop user interface and architecture ensuring network will grow? What is the strategic approach we have to develop during the network lifecycle? How to go further in developing a ubiquitous social network experience taking in account the full web ecosystem and also the offline environment?
This presentation will be explained though very visual elements and I’ll interact with public. I’ll show some deliverable used during those different stages. Last, “Building social web/network experience” doesn’t aim focusing only on social networks. I wish showing to all IA community how important it is to think our conception approach within a broader scope of skills and analysis.
Planning and building user experience requires certainly user centric approach must also use web analytics & business intelligence, marketing and communication skills, persuasive interface technique, entrepreneurship, etc. I really dream of a very very big IA.
by Martin Belam
Ask any average user to perform a task on the Internet, and the chances are that they will start by tapping a couple of words into Google. The search engine giant has become the 'map of the Internet' that everybody seems to use to navigate.
But if 'everything starts with Google', where does that leave site search? This is a particular problem for news providers. Google's universal results already include the latest news, and the Google News product is gaining in popularity - ranked as the fourth most 'trusted' news source in the US, even though it is simply an algorithm.
The challenge, therefore, for news organisations, is to deliver a site search service that offers something more than Google can. They need to offer features that take advantage of a better mapping of their own content, and an understanding of their own audience. And they need to get the results right - every single time.
Looking at a wide range of European broadcasters and newspaper publishers including Kathimerini, ORF, Corriere della Sera, El Pais, The Guardian and the BBC, this presentation shows how news providers are using their site search facilities to differentiate themselves from the ubiquitous Google search box.
The presentation includes insights from real life user-testing sessions within news organisations, and explains how search log and search usage analytics can help a news provider determine the set of search features and UI priorities that they should be delivering to their users.
1. Translate your favourite design solution into a design pattern.
2. Translate your favourite way of working into a process pattern.
3. Combine the two and the result is: Best practices on steroids!
Design patterns are an accepted way to document best practices in a structured format that allows for quick learning, reuse and inspiration for designers of interactive systems. Patterns for typical IA problems such as "breadcrumbs", "advanced search" and "booking process" are well-documented. A designer tasked with designing a system that might contain these elements can browse pattern collections and choose to apply the knowledge documented there.
Process patterns have been applied in the development of object-oriented software for at least 10 years. Scott Ambler describes them as "a collection of general techniques, actions, and/or tasks (activities) for developing object-oriented software" and distinguishes 3 levels of patterns: task, stage and phase. Collectively, process patterns help organizations and teams document knowledge about which part of a process works best in what situation and how to execute the part.
In the past I have proposed to add process attributes to design patterns expanding the focus of patterns to include the context of design. In this presentation, I'd like to expand those ideas and describe what a combined process-and-pattern library could look like. My aim is to encourage attendees to think about combining design patterns with design processes and profit from their synergy, which includes the creation of a common language for clients, designers and developers to talk about design.
26th–27th September 2008