Tuesday, September 25, 2007

Processes + Patterns (EuroIA 2007 presentation)

Despite having been sick for 20 days, and despite my coughing fits, I managed to deliver a pretty well-received presentation at Euro IA, last week in Barcelona.

Here's the Slideshare-version:

After explaining the concepts of patterns and collections, I spoke about how I thought process patterns and design patterns could be combined and about what the benefits would be to designers and team managers (and of course users and clients) once they were combined.

I ended with a challenge to IAs (and user experience professionals in general) to find new ways to combine process patterns with design patterns. I was lucky to have heard of one such initiative just before the presentation, so I could call them on stage during the Q&A. I hope it inspired the attendees and indeed a couple of people approached me afterwards with suggestions and ideas.

More suggestions, examples, comments, ideas are welcome!


Blogger m said...

i see what u did there :D

12:28 PM, September 25, 2007  
Anonymous Anonymous said...

i saw also your presentation. I think you should defintely try to orientate your theory into an object model system.

Object are you UI Pattern and method could be your methods. Then you have to create a matrice 1 object n methodes or 1 method apply to n objects.

I liked very much your idea to share on this basis some figure, test an results based on different experience. it could be an incredible source of data.

11:18 PM, September 25, 2007  
Anonymous Anonymous said...

Great presentation. Developing repeatable and re-usable templates and processes is a main goal to ultimately reduce work or re-work in the end. Some get it, some do not.

I have been using "light" UML task flows in conjunction with my wireframes or mock-ups for several years now and it works. It works both to convey the design's intention better and give the parties downstream (Development and QA) something more to sink their teeth into.

And to your point, they can be used over and over again. For example, validation points, error handling, deleting, and thier behaviours etc. are all examples of patterns and processes that can continually be re-used, so that they do not have to be re-created for each and every project.

1:59 PM, October 01, 2007  

Post a Comment (moderated)

<< Home