Tec's soup - posts tagged 'Usability'

A New Year’s Compilation Of Usability & Wireframing Poetry

Fri, 11 Mar 2011 12:04:31 GMT

We have moved well into the new year, and this is a great time to briefly pause and look back at the year 2010, which has been a remarkable year in many ways. It’s been exciting, to say the least, with Facebook becoming the most frequented website on the world wide web, Google Android mixing up the mobile market, the number of mobile internet users growing massively, Twitter becoming a viable communication channel for established businesses, and cloud services really starting to take off as companies like Microsoft, IBM, or SAP have followed Amazon into the virtual world.

What role do topics like user interface design or usability play in this setting? Well, with more and more services going “cloud” or mobile, most companies have noticed that traditional interface design concepts need to be reconsidered, not only because navigation patterns differ when you are using software in a web browser or on the small screen of a mobile touch device, but also because the competition is becoming ever more intense online and in the mobile market.

To pay tribute to the rising significance of great user interface design, we have started creating poetry that plays on the variations of UI design topics. Here are a few of the diamonds in this modern category of usability and wireframing poetry. Enjoy!

Ode to the Usability of Interface Designs

Though still unfinished pride of expertness

Thou wireframe of an interface design

A rapid paper prototype used to express

Ideas of layouts and navigation that lurk in the mind

What icons and buttons envelope thy shape

Of links and portals that strive with growth

through the fiber optic cables of an ISP

Streaming gigabytes of info with ease for you and me both

What mad pursuit ever since the struggles of Netscape

When the ripe World Wide Web became destiny

Interfaces designs are sweet, but those uncluttered

Are sweeter: which is a reason why users stay on

When a website is clear it becomes more endear’d

Leading to increased visits and subjective satisfaction

Being used with great ease and not wanting to leave

Accomplishing tasks with minimum error scares

Knowing I can recover if something goes amiss

Though winning near the goal – yet, I do not grieve

For using this graphical user interface design is bliss

With a high level of memorability, this interface design is a breath of fresh air!

Based on “Ode to a Grecian Urn” by John Keats

Ode to a Skinned Interface Design

I went to the link my friend sent me,

And I saw what I never had seen;

An ad banner was built in the midst,

Where I used to click on the screen.

With no choice but to scroll down I did frown,

My friend’s interface design was upside down,

Like a tourist with no clue I looked around lost in town,

‘Cause there were no breadcrumbs to be found.

A millisecond too long I located local navigation,

Thinking ‘they sure could use a wireframe tool for their creations’.

With findability resolved these usability problems would dissolve

And, in tow, his search engine ranking would evolve.

Based on “The Garden of Love” by William Blake

Instant Interface Design Sorrow

My mother groaned, my father wept:

Into their shopping cart unwanted things leapt,

Helpless, overcharged but arrestingly proud,

Feeling like a fiend was hid in ‘the cloud’.

Who to blame when the mouse was in my father’s hands,

Well poor usability & interface design will hurt a brand,

Placing the ‘Cancel’ button a nanometer from ‘Buy’ is not best,

Especially with a return policy worse than the rest.

Based on “Infant Sorrow” by William Blake

The original idea behind these poems was to adapt famous poems and use them to shed light on issues that affect usability, wireframes, wireframing tools and user interface design. If you have some suggestions of poems that you would like for us to interpolate during the coming year, please feel free to leave a comment with your request in it.

Wireframe fidelity – Why does it matter?

Tue, 18 May 2010 18:46:55 GMT

Do you use wireframes in your interface design projects? If so, you may have found yourself debating just how detailed your wireframes should be. In this article I shall explore the concept of wireframe fidelity and how wireframing affects the usability of a user interface in software and/or website design. Deciding which level of fidelity in your wireframes would be most advantageous to you and your project can be pivotal in ensuring success. Experts are still debating the distinctions of wireframe fidelity and whether high or low fidelity is the way to go. In the following paragraphs I will go through the differences in wireframe fidelity and the benefits they carry.

Why use Wireframe Prototypes?

When designing websites or software applications paying attention to a great interface design is key, since the graphical user interface is the part of your software that users see first and use to interact with it. In order to achieve a great interface design, the use of wireframes during the design phase has become a valued method. A wireframe (sometimes referred to as website wireframe, software wireframe or application wireframe) is a visual representation of the projected content and structure of a graphical user interface and is an essential step on the way to a great interface design. It is easily understood by all stakeholders and can serve as communication aid. Much like an architect’s blueprint plans wireframes are an invaluable tool when creating software or websites with a solid foundation. In the same vein, they should be used long before the first bricks (or programming code in this case) are set.

Further Considerations of Using Wireframes.

Wireframes allow a project’s stakeholders to have a vision of what to strive for and are particularly useful in the collaborative process as they ensure that team members can easily understand a software concept and can keep track of a project’s workflow. Popular use cases for wireframes include improving usability through early user tests, involving non-technical key stakeholders early on in the development process, or communicating with developers and designers for planning purposes. The level of detail in a wireframe prototype is referred to as wireframe fidelity and can be in either of two main guises: low fidelity or high fidelity. (Some even distinguish three types, including medium fidelity wireframes.) Knowing which fidelity to employ is of crucial importance as the investment in creating them in terms of time, cost and expertise required varies tremendously.

What are Low Fidelity Wireframes?

Low fidelity wireframes are wireframes that focus on the essentials of a user interface: layout, structure, Information Architecture – and not graphic design! Low fidelity wireframes evolved onto computer screens from rapid paper prototyping wireframes which emerged in the mid 1980s to become a popular Blue Chip company tool by the mid 1990s. Rapid paper prototyping involved the creation of rough sketches (often drawn by hand) of graphical user interfaces as prototypes of software applications to visualize and test usability long before the coding process began.

Example of a low-fidelity wireframe

What is an example of using Low Fidelity Wireframes?

A real life example of successful paper prototyping stems from the mid-90s when e-commerce was beginning to take off and Priceline.com was introducing a service that allowed consumers to submit a bid for a plane ticket along with a credit card. How could they convince users to trust their credit-card details to an as-yet-unknown website? Paper prototyping showed the team that their initial design would have been a failure, allowing them to correct the problems before launching the site. They also discovered that users didn’t need some of the hard-to-implement features they had included. Paper is a readily available resource, but not easy to change or adapt. Hence, nowadays, digital solutions like “digital paper prototyping” with specialized wireframing software are often used in iterative processes as they tend to be more efficient.

What are the benefits of using Low Fidelity Wireframes?

Low fidelity wireframes have many benefits. By eschewing many cosmetic factors they are relatively inexpensive and quick to create or alter. This allows for collaboration as suggestions and refinements can quickly be added to a number of variations very cheaply. Furthermore, low fidelity wireframes are useful in gathering great feedback because their rather rough appearance makes it clear to viewers that they are talking about a draft that is easy to change, rather than an almost finished product, thus inviting honest and unrestrained feedback. In addition, the lower level of detail allows you to focus on fundamental usability issues of your product. When using low fidelity wireframes for usability tests, testers can also give you qualitative feedback that really focuses on usability rather than being distracted by, say, the color of the fonts used. Yet, some critics caution that the level of abstraction may be difficult for inexperienced users. Once usability has been tested and polished, beautiful designs may be added onto a solid foundation that maximizes user experience.

Here you can find an interesting article on sketched wireframes.

What are High Fidelity Wireframes?

High fidelity wireframes (often referred to simply as high-fidelity prototypes) are very close in design to the true representation of the final user interface design. As such, they tend to include slick and polished design features and even go as far as simulating in much detail an application’s workflow or even logic. Despite pixel-perfect good looks a high fidelity wireframe remains but a prototype, however crisp it may look and feel. Due to their high level of detail, high fidelity wireframes tend to be more costly to create and usually take much more time to compose. They may also require more experience, sometimes even technical expertise, and can hinder the feedback process as testers or clients may be distracted by design features rather than focusing on usability. In addition, test users as well as clients may be more hesitant to critique a design done by a professional, which looks like it would require a significant amount of time to change. Fears that such changes may result in higher project costs are not uncommon and may skew feedback, which makes it very important to explain the purpose and method used in creating high fidelity wireframes before soliciting feedback. Advocates of high-fidelity wireframes find that aside from running usability tests, they enable quicker understanding of decision makers.

An examle of a high-fidelity wireframe.

What are the benefits of High Fidelity Wireframes?

On the positive side, high fidelity wireframes share many of the same advantages with low fidelity wireframes in general but have their own benefits in particular. High fidelity wireframes are usually used in addition to low fidelity wireframes, and after the latter have been used to resolve the most impactful and fundamental usability or interface design problems of an application. Being eye-catching and less costly to create than full-fledged applications, high fidelity wireframes can be used to impress clients who have to sign off on a concept quickly. Since they tend to require less programming knowledge than coded prototypes, high fidelity wireframe prototypes can be composed by users with limited programming knowledge. As they are closer in design to the final product, clients can quickly understand the final look and feel of an application without extensive verbal explanations. The high level of detail reduces the amount of abstraction required by non-technical stakeholders, which – depending on personal experience – may be important in some scenarios. In terms of your development team, high fidelity wireframes allow you to collectively bring an interface to life. This helps in keeping a project’s budget manageable which in turn further satisfies clients. Whether or not high fidelity wireframes are necessary or beneficial depends on the particular project at hand and your goal in using them. One should think about the costs and the benefits of creating detailed high fidelity wireframes beforehand. Sometimes, it turns out that it is faster to go from low fidelity wireframes to programmed code directly.

Which type of Wireframe should one use?

As can be seen from the short portrait above, each type of wireframe has its own advantages. It is often not an “either or“ decision which type of wireframe to use. Instead, both types are useful for different purposes and can be used consecutively in a project. It really depends on the goal or use case at hand and the budget of a project. Yet, if you have to choose one type, the low-fidelity wireframe tends to offer a better cost-benefit ratio as it is quick to create and sufficient to resolve the most urgent usability issues in user interface design which may be the most decisive factor affecting the success of your software. Or you could try “real wireframes” – low-fidelity wireframes augmented with some graphic design elements that help a user who is not familiar with the project understand the wireframe more quickly despite its abstractions.

What fidelity do you prefer in your prototypes?

More on when to use low vs. high fidelity:

http://www.uxmatters.com/mt/archives/2007/03/wireframing-with-patterns.php

http://www.boxesandarrows.com/view/what_an_ia_should_know_about_prototypes_for_user_testing

A nice slide show on wireframes:

http://www.slideshare.net/piksels/wireframes-and-interaction-design-documents-presentation

Synchronous, Remote, Real-Time, Internet-based Usability Tests … what for? – Part 2 -

Wed, 03 Feb 2010 13:34:59 GMT

So What About Synchronous Remote Usability Testing?

The previous week, I posted part One of this article.

In order to integrate the user into the design process at the earliest possible date, it is customary to develop a low-fi prototype which will allow initial evaluation of the overall design. We are however faced with a problem if we want to combine the qualitative feedback of synchronous usability testing with the advantages of non-biased remote testing. How can both approaches be combined?

Yet again, technology should hold the answer to this question:

Requirements for Synchronous Usability Testing:

test-user and moderator need to be connected via the Internet
a shared screen needs to be in place for both to view the prototype
a live audio connection should be in place for synchronous communication
the data of the test-session needs to be recorded (audio, video recording of all mouse movements)
recorded data needs to be stored for instant retrieval

Optional requirements which may increase the quality of the session:

information and tasks should be visible to the test-user
moderator’s ability to integrate questionnaires which the user can fill in his own time
the moderator can change parts of the prototype whilst conducting the test
comments and annotations can be included on-the-fly
test-user and moderator can be connected via a live video-feed

Usability Test: Methodologies

The overall test should allow the following methodologies:

Thinking Aloud (test-user must think aloud and express what he thinks or misses in the prototype)
Wizard of Oz Prototyping (the prototype can be changed on-the-fly for instant ratifications)
Team Observation: (the rest of the production team follows the usability test, make notes and come up with alternatives)
Formal and Informal Tests
Click-path Analysis
Use of Questionnaires

Next week, part THREE of this article will follow.

Synchronous, Remote, Real-Time, Internet-based Usability Tests … what for? – Part 1 -

Thu, 21 Jan 2010 08:26:47 GMT

The article will be posted in 3 parts -which should be released a week after another.

Developing a software application is a creative and complex process. It becomes specially challenging when trying to design an interface which suits the end-user. Designers, project managers and programmers all have different views on how to approach their common goal: a successful, stable and user-friendly design.

Now let’s be honest: how many of you have met their targets on time and within budget? How many of you have spent sleepless nights because of unforeseen problems which came up in the very last minute?

I bet there are a few of you and one of them is me!

Most problems come up at a stage where a lot of design and programming work has already been invested. These problems become apparent when the test-users start getting their fingers dirty and as soon as they uncover flaws with your work, a lot of heartache will follow. User-tests are necessary yet are often deployed when it is ‘nearly too late’. Don’t get me wrong, I’m a keen supporter of usability tests but I believe that the traditional ways of running such tests are outdated.

The user should be included in the production process as soon as possible. The sooner this happens, the less time and money you will spend on conducting usability tests since you will be able to spot the flaws at an early stage. Makes sense, right?

So why do we keep insisting on setting up expensive test labs and pay thousands of dollars for expensive equipment and spend time and money in finding the right test-users? I want to present you a different approach to user-testing, a way which may very well change your attitude towards the established forms and also a way which can save you from those troubles mentioned earlier.

In order to gain the feedback you need, it always helps to gather qualitative data of users which can test your product in the right environment. Having housewifes, students or seniors sitting in your office and trying out that new e-commerce website for your client isn’t the way forward, or is it? Well, i think it is defenitely more safe and reliable to let them stay at home and do it from their own desk. Why ruin that new test-rig if you can get your test-users to work remotely?

Remote Usability Testing

Remote Usability Tests are conducted in the natural environment of the user (e.g. at home).

The fact that it is conducted remotely and not in a lab environment has a lot of benefits:

test-user can work in his natural and familiar surrounding
limits biased feedback since user is not ‘under pressure’
saves money for travel & set-up costs
creates sustainable usability testing for a greener world

Synchronous Usability Testing

Synchronous Usability Testing is a well established approach for running qualitative Usability Tests.

As the name suggests, synchronous testing is done on a one-to-one basis and in real time. The test-user will be running tasks set by the moderator which then can be closely monitored and recorded. The moderator’s difficult task is to interpret and evaluate the test-user’s problems with the product. This is not an easy task and it takes a lot of experience and well refined ability to use the feedback in the most effective way possible. This is why synchronous Usability testing is often done with low-fi prototypes – therefore early testing is possible.

The advantages of Synchronous Usability Testing are:

allows moderator to guide the user
produces qualitative feedback
questions can be solved on the spot
UX flaws can be spotted at an early stage

Next week, part TWO of this article will follow.

UXcamp Europe 2010 taking place in Berlin next May

Fri, 15 Jan 2010 08:01:43 GMT

The first UXcamp was a huge success if you read some of the blog articles from last summer (read the review from centigrade or have a look at the German blog feedback). That was encouragement enough to lift the UXcamp to the next level by opening the event to an international audience. This makes it UXcamp Europe 2010.

We still follow the BarCamp principle to bring together the European community for User Experience, Information Architecture, Usability, Interaction Design, Visual Design, and everybody who feels himself dedicated to the user of products and services. In case you fit somehow to that description, please join the UXcamp network and prepare yourself for a trip to Berlin on 29th and 30th of May 2010. The registration for the single days and the UXcamp party is planned to open next month. The concrete date will be published in our network once we decided which day.

Since we want to welcome participants from hopefully every country of Europe, we introduced the concept of Country Ambassadors. If your country is not yet represented by an ambassador, please let us know. The only thing you have to do as an ambassador is to spread the word and connect your local community with our network. We are sure this will be an exciting event to be for everybody!

Usually, a BarCamp is free to the participants to provide everybody with the possibility to join the event and participate by giving a session, discussing with the others, or simply by giving a hand whenever necessary. However, this requires us to cover the expenses with sponsorships. If your company is active in the User Experience field, or if you think your company should get active, please don’t hesitate to get in touch with us. We are thankful for every support we can get!

If you are still in doubt whether you should travel to Germany next May, there is also the International UPA Conference, taking place in Munich from 26.-28. of May, which is right before the UXcamp Europe. Oh, and two weeks before there will be the (German) IAKonferenz in Cologne. And if you’d like to extend your stay in Berlin, right after the UXcamp Europe there will be the Webinale, another gathering for all the Web geeks. So, plenty of events to go to next May.

The Beauty of Web-Based Paper Prototyping -Part 3-

Fri, 08 Jan 2010 08:09:30 GMT

The previous week, part TWO of this post was on the benefits which digital, web-based prototyping will make exportation and presentation easier. This FINAL part will show you how iterations can be made easy and that using digital solutions will in fact help against the fight of global warming.

Quick Iteration:

One of the main benefits of using the digital solution is the possibility to make us of quicker, easier and cost-effective iterations. But this will only happen if the prototype can be adjusted to new requirements in an instant. Digital paper prototypes can be re-used and won’t have to be created all over again once a new iteration starts. You simply have to adjust specific elements once and then apply those changes to the rest of the prototype, that’s it.

Sustainability:

The average usability testing project leaves a footprint of approximately 250 kilograms, or 0.25 a tonne of CO2. That may not seem much but that is close to amount of CO2 emission as a 3 hour flight. Usability testing is universally seen as the best way to improve a system’s ease and satisfaction of use. If one usability test itself emits the equivalent of a 3 hour flight, there clearly are considerable gains to be made! In an ordinary usability test, someone travels from his/her location to a laboratory or office where they interact with a test facilitator. Normally this takes about an hour and the process is repeated with 7 to 10 people.

The carbon emission for a usability testing project is based on an average of 10 participants, with each participant traveling 20 kilometers return to get to the test and spending 1 hour with the test facilitator.
More on: http://www.prnewswire.com

Conclusion:

By making use of the newest technologies it is now possible to make the shift from paper-based prototyping to digital or web-based prototyping. User-centered design, sharing of ideas, iterative work-flow, collection of feedback and collaborative work are all aspects which speak in favor of implementing such process. Developers, designers, clients and test-users alike can benefit from working on digital prototypes which engage them from the very first idea. Unnecessary iterations which often confuse and hinder continuous work-flow can be a thing of the past since everyone will be up-to-date. Test-users can work in their natural surrounding whilst the design team can make changes on-the-fly.

Overall, web-based prototyping can only be beneficial for all parties involved. Also, since using excessive sheets of paper can be a thing of the past, it will be a make our planet a little greener.

The Beauty of Web-Based Paper Prototyping -Part 2-

Mon, 14 Dec 2009 16:27:27 GMT

The previous week, part One of this post was dealing with some of the core ideas of why classic paper prototyping is no longer sufficient. This week, I will talk about why versioning of prototypes and the ability to acces, export and present the results are a necessity.

The Need for Digital Prototyping:

That big round table to which everyone gathers around can never be big enough! The bigger the table becomes, the more sketches and papers are on the whiteboard, the bigger the chance of losing out on some detail. A reasonable alternative would be making use of digital prototyping and to have that table digitized (including the papers, sketches and the words being said). Why keep working with the whiteboard, stacks of paper which have to be carried around the office? Digitizing the work and all what comes with it would make the chaotic meetings a thing of the past. Using a digital solution is a way which allows collaborative work-flow to be fully recorded, ammended, shared and viewed at at given time.

Team Work Challenge:

One of the requirements for successful team work is to administrate various versions of the same prototype. Versioning of prototypes has two meanings within this context:

(1) the different stages in development process which can be accessed at any time
(2) different versions of the same prototype

Once several people work on the same prototype the need for digital versioning quickly becomes apparent. While one is already working on the CSS, the other is still in the process of developing the menu bar; now can you see what may go wrong? Using a tool which gathers all the different process and work-flows of the various co-designers will help to unite the project into one single application and help the collaborative flow. Real-time collaboration will ensure that misunderstandings and miss-communication are reduced to a minimum. A team which works from different locations and on different elements within the same project are in dear need of such a tool!

Presenting the Results:

Once a prototype is finished, the real work starts. The prototype will be used for extensive usability tests, will be used for presentations and is part of the developers specification. All the various players need access to the prototype which again needs to be in various formats. Since it is pivotal to have a prototype ready for presentation, viewing and export, it should be digitized and ready-accessible on the Web. Well, not accessible to all, just to the one’s involved in the process of course!

Usability tests need to be run and an interactive and/or clickable prototype must be easily accessible to the test users. Furthermore, if qualitative feedback is what is needed, a moderator also would need to access the prototype without a problem. In addition, the developers and the rest of the design team must be able to quickly ‘click through’ and be able to make some minor changes if needed. This is why a prototype needs to be open to all the people involved, needs to be updated in real-time and be exportable to any format and at any time!

Part THREE will talk about the benefits of digital iteration cycles and talk about the positive impact digital prototyping can have on our environment. Hope to see you there!

Getting to the customer – why everything you think about User Centred Design is wrong

Fri, 27 Nov 2009 16:34:29 GMT

Great post on UCD and the common belief systems. By Thomas Petersen

“In broad terms, user-centered design (UCD) is a design philosophy and a process in which the needs, wants, and limitations of end users of an interface or document are given extensive attention at each stage of the design process. User-centered design can be characterized as a multi-stage problem solving process that not only requires designers to analyze and foresee how users are likely to use an interface, but also to test the validity of their assumptions with regards to user behaviour in real world tests with actual users. Such testing is necessary as it is often very difficult for the designers of an interface to understand intuitively what a first-time user of their design experiences, and what each user’s learning curve may look like.

The chief difference from other interface design philosophies is that user-centered design tries to optimize the user interface around how people can, want, or need to work, rather than forcing the users to change how they work to accommodate the software developers approach.

So as you can see a typical UCD process to define it in terms of the hammer test, is based on testing the drawing, the cutout and the Styrofoam hammer.

Not the actual hammer.So why is that? How comes something that seems to be an obvious problematic implementation of the goal of UCD, have become the norm?

This way, users have become customers and you can suddenly start to test where it matters with valuable feedback.

This will no doubt mean that many have to re-educate themselves and rethink how they approach design whether it be UX, IA, UI or GUI. It is none the less as stated, necessary to stay relevant for the future. A pivotal part of this will also be to re-educate clients and help them understand that they will need to look at at product design a little different.

Design is a decision, not a democracy. If you are serious about using design strategically then courage is the strategic advantage you should be looking for. And with the ability to quickly change wrong assumptions it’s not really dangerous, just common sense.

Agile User Experience Projects for the small agency

Tue, 24 Nov 2009 09:27:42 GMT

Jakob Nielsen’s article on Agile User Experience Projects suggests that good implementation of usability in agile projects can be vanguarded by:

“Separate design and development, and have the user interface team progress one step ahead of the implementation team. That way, when it comes time to build something, it’s already been designed and tested. (And yes, you can do both in a week or two by using paper prototypes and discount user testing.)”

Out of our own experience, small software and design companies do not have the necessary funds to run a dedicated UX-team and by using the above mentioned approach, good design and usability can be achieved.

The Beauty of Web-Based Paper Prototyping -Part 1-

Mon, 23 Nov 2009 10:52:50 GMT

This article which will deal with the various benefits which digital web-based prototyping can bring to your production cycle. The main idea of this article is to promote the digital implementation from the very start of the production work. Many design agencies still work with pen and paper, a method which has been used for a long time but which in today’s world should be seen a thing from the past. It is time to explore the possibilities which technology can offer us!

The article will be posted in 3 parts -which should be released a week after another. Part ONE will offer a little review on classic prototyping and talk a little about the general structures within the team. The following articles will go more in-depth and talk a little about the ambitions, requirements and solutions for making the product development a little easier and more fun. I hope that you will enjoy this article and hopefully be able to take something useful out of it. Thanks!

Introduction:

User-centered software development is a dynamic and creative process. In the prototyping phase and in the evaluation, one can see it’s benefits and new challenges arise for the production team. The conceivability of the clients must be fully understood, ideas of the heterogeneous design team as well as the gathered feedback of the target audience must be included into the design. A challenging task indeed!

Due to global requirements of today’s digitally connected world, ‘classic paper prototyping‘ often is no longer sufficient. A bunch of draft papers are easily misunderstood, mixed up or lost in the super information highway and the need for an all-encompassing, digital and rapid solution is becoming more of a demand.

Therefore, web-based rapid paper prototyping has been growing into a well known topic for designers, developers and clients. But what is it what makes digital sketching so appealing to the usability community? Are design agencies simply too lazy to do the manual work with pen and paper or do they simply want to be more Eco-friendly and want to stop the deforestation of the amazon by refusing to use paper-based prototypes? This article will touch some of the core points and issues within the field and will list the justifications of this development.

Paper Prototyping:

The easy way to create low-fi prototypes, to gather the design team around the big table or the whiteboard and a chance for everyone to jot down their ideas on the project. This technique supports the main ideas of rapid paper prototyping. Everyone can make changes and also view the changes already made by others. Everyone knows what is going on.

However, there are a few problems with this method. Increasing the complexity of a prototype whilst keeping a full overview on the project as a whole can become a bit of a challenge. Once a change has been made, it it difficult to be undone. Of course you can simply delete or throw away an error prone design but it is not as easy as a simple ‘CTRL+Z’.
To add to this, imagine that the team works from different locations and with different tasks to manage … it can become a mess in no time! Therefore, paper prototyping is no longer sufficient for the demands of the modern design agency.

Prototyping Roles:

The main roles in the prototyping stage are of course the users, the design team, the developers and the client. In order to finish up with a satisfying product, the different needs of those interest groups must be met and considered. Gathering those people around the same table, meeting their requirements, dealing with time pressure, budget limitations and the different locations of the various key players are a tough one to call.

The Design Team:

The design team is a collective of some very smart and able professionals. The interaction designer, visual designer, information architect, human researcher, usability experts and prototype developers are just some of the many roles one can find in a team. In order to express their varied ideas on how the end product should be like, collaborative prototyping is the way to meet this ambition. This method will enable them to discuss and clarify the multitude of requirements.

Next week part TWO of this article will follow. Subjects are the challenges of a team, collaborative working and requirements for digital prototyping.