Good content is essential to good user experiences, and to making good information architecture work. I'll highlight two ways to include content quality in the scope of UX: involving content owners in a Delphi-like review of website (or intranet) structure; and delivering practical writing specifications to help subject-matter experts produce useful content - even if they're not natural communicators.

"101 Things I Learned in Architecture School" by Matthew Frederick delivers practical, experience-based advice to architects. Where's our equivalent? Where is "101 I learned in Interaction Design School"? Well, let's get started. You nominate a number from 1 to 101. I translate that architecture principle into an interaction design principle. If I can't, then you get a go.

Early project information and documentation e.g. scope, project objectives, business requirements often take an organisational or technical perspective in describing the future system. A UX strategy on the other hand takes as its start point the perspective of those who will use the system. We define the development of a UX strategy then, as the process through which project information is critically translated and interpreted into a description of the future system from the perspective of the user experience. Our process starts by taking existing project information including user research and translating it into relevant user stories.

We've all heard it. Customer experience should consistently engage a customer across all touch points. This utopian vision speaks to our souls and warms our empathetic hearts it can also fry the mind. This talk will highlight the challenges of creating an integrated customer experience, then share practical models and techniques that help break it down to size–interaction by interaction.

One of Atlassian's core problems is the difficulty of sharing and manipulating content in one application from within another. The Design Engineer assigned to the project of resolving this problem, Lachlan Hardy, will lead you through the design choices and implementation decisions that produced the new open dashboard which allows simple powerful content sharing from external sources on the web as well as our own products.

In this talk, writer and researcher Alex Wright will take us on a guided tour of the many ways people have collected and shared information over the years: from the earliest folk taxonomies to the origins of writing, books, libraries and early hypertext systems that in some ways surpassed the present-day Web.

We (Design Researchers at the People and Systems Lab, QUT) do a lot of work with video, collected in our usability lab and in the field, but we rarely show that video to other people. We've found that by turning video into visualisations it's easier to compare different videos.

Playing games is more fun than work, right? So if we can combine games and work, work will be fun. Design games can help you learn about your users, or help a design team generate better solutions.

Let's talk about examples of really bad UI/UX design collated from around the web/mobile/software/etc. Everyone can email me their favourite bad examples in the lead up to the conference and I'll collate and host.

Why are some robots perceived as being cute while others are just plain freaky? This is a (mostly) irreverent exploration of recent robots and an introduction to the uncanny valley hypothesis.