Tag: Article

When You’re Holding A Hammer Everything Seems Like A Nail

This post is inspired by a conversation with one of the winners of the UXBite competition, Tomek. We were talking about various wireframing tools and one of the things Tomek said caught my attention: I was trying to work with ***, but I felt like they gave me a hammer and now I’m obliged to only see nails around me. That made me thinking.

We are being limited by the names we give to specific objects and tools. We are being limited by our habits. We are being limited by habits of other people. And we are being limited by our own usual ways of using certain tools.

For example: what you can do with a hammer? First thing that comes to mind: hit the nails with it of course! What a stupid question?! But as you keep thinking you can find different ways of using a hammer. You can hit nails with it but you can take them out of wooden boards as well. Or you can kill someone with this tool. Everything depends on current needs.

I know that you may be thinking  prototyping / wireframing tool  is only for wireframing or prototyping. Period. Today I want to show you a little alternative way of using JustProto. How? See below.

Product Retrospect.

Product Retrospect is a simple yet effective way of summary after the project’s closed. You gather the whole team and discuss every pro and con that’s project related. You don’t point fingers saying “You screwed this up by not talking to me earlier” but say “This was badly executed due to lack of communication”. Sometimes when your team is spread all over the world it’s extremely difficult to do this kind of project retrospective – time difference and gathering everyone on the same page is hard. JustProto’s collaborative features come in handy in this time of need:

  • Multiple Collaborators,
  • Real-Time Collaboration,
  • Chat,
  • Project Preview with just One Link,
  • Live Preview.

How it works?

Each JustProto account have an Administrator/Owner, who can grant access to others – The Collaborators. Each Collaborator gets his unique login and password to login to the project at a certain time. Using nothing else but computer with Internet access everyone edit the same project at the same time and everyone see all changes in the real time (that’s the Real-Time Collaboration).Kinda like on Google Docs while editing the same spreadsheet or word document.

Each person choses note, tag or pin color they like and that’s that – by editing its text Collaborators – The Team add their point of view on a closed project. What is important – everyone can talk on a project Chat. Smart history will save all the conversations. This way everyone’s up to date even if the Internet connection dies: Chat history and current version of the retrospective is saved and always available online.

Any person who is not on the project team but gets the Preview Link will see the retrospective project. Let’s say your boss is not one of your project team but you’d like him to know the results of the retrospective – send him a Preview Link and that’s that!

What’s even more fun and handy and cool – if a person who get the Preview Link will open it while you and your team edit the notes, they will see everything in the real time too thanks to Realtime Preview! How the project retrospective can all look like? See here.

This example shows that you don’t ALWAYS need to stick to the tool’s purpose. Don’t be limited, try thinking of other ways you can use the tools you like : ) What it also shows is the fact that wireframing tool can be helpful not only while design happen – it can also become pretty useful after the project is done. Remember that the tool is just a hammer. You don’t need to see nails everywhere.

Case Study – Real Story, Real Users, Real Help!

Today We’d Like To Brag A Little (Humbly, Of Course) About One Of UXPin’s Great Users. We’ll Be Introducing You To SocialPaths And Their Real-Life UXPin Adventure With Interactive Wireframes!

“We are no longer able to work without UXPin…”

SocialPaths (a.k.a. The Great User)
SocialPaths is a social media agency that, in their own Creative Director Piotr Zaniewicz’s words – mainly takes care of supporting all kinds of social media marketing activities. Their house speciality is engaging social media games connected to different kinds of loyalty programs that make good use of social media’s viral nature. Among many cool projects, the team at SocialPaths have created contest apps for the Facebook page of one of the biggest trance music festivals in Europe as well as a very popular app called The Great Advice of Mieciu The Eternal Student. While their apps are mainly created for Facebook, they also build interactive tabs for websites and contests.

KISS (a.k.a. The Biggest Work-Related Headache ; )
Working with clients isn’t always a bed of roses, the SocialPaths crew can vouch for that. Putting up with those occasional clients who always know best is one of the most annoying little problems SocialPaths encounters. Of course, clients have every right to have their vision of their product realized, BUT painting that vision in the form of a working app is sooooo complex and difficult that it’s not the piece of cake that clients think it is upfront. Our main problem that we face on an everyday basis is meeting client’s high expectations and stick to the golden KISS (Keep It Simple, Stupid) rule at the same time. Sometimes it is a struggle to convince client not to interfere where we know better – says Piotr Zaniewicz, Creative Director of SocialPaths.

UXPin (a.k.a. The Solution)
After a major brainstorming session, the SocialPaths team came to a conclusion about creating wireframes and interactive prototypes that could solve this problem, so they decided to try out some of the prototyping and wireframing apps out there. One of their friends sent them an interactive prototype made with UXPin and that gave them their first glimpse of our little baby.

Piotr, Creative Director of SocialPaths talks about what they were looking for exactly – We were in great need of tool that lets you create really advanced prototypes step by step so that our team would instantly know what parameters to consider while building (i.e. size, style, layout etc.) and that lets you create prototypes that REALLY visualize all the looks and features to the client.

It’s not easy to find a tool that does both, of course, but the final thing that made UXPin their weapon of choice was its ability to do everything online, so that there is no problem with keeping the project up to date; The newest version is always available to every member of the team at any given time. Another big plus was that UXPin’s really easy to implement – there’s no bigger pain than when the learning curve steals time instead of saving it: We were afraid of the implementation of new tool, but UXPin is so easy to use that after just a little while a fully functioning prototype went to the Graphic Designer – says Piotr.

The Conclusion (a.k.a. How UXPin Helped SocialPaths)
In our team, UXPin is used mainly by Project Managers and Designers who collect feedback and make on-the-spot changes to the projects according to our client’s wishes. In the first phase of the project creation, UXPin is the link between clients and our team. After three months of using UXPin we can honestly say it really does make our job easier! Thanks to making fully interactive, clickable prototypes, we avoid misunderstandings and unnecessary changes after the implementation. Our clients and us both save a lot of time. -Piotr Zaniewicz, SocialPaths

SocialPaths case is a great example of how wireframing saves time, money and refines communication. So why haven’t YOU used interactive wireframes to help YOUR business?

Create an account today and see firsthand how UXPin helps your!

Four Ways Of Making Your Wireframing Job Easier!

Is it even possible? Well… YES! We did a lot of listening and thinking lately and now we can proudly present four new features that will make your job easier and faster! So, let’s cut the chit-chat.

Feature One – Context-Sensitive Menu and the Properties Tab

After years of using non-web-based prototyping tools such as Axure, I am accustomed to right-clicking on elements and this is one area that unfortunately the limitations of the medium created some difficulty – right clicks within Chrome, for example, result in the Chrome popup window rather than any context-sensitive menus for JustProto itself.  It wouldn’t be fair to criticism JustProto for this, however, as it’s a limitation that applies to all web-applications but I felt that because the interface is just so, well, slick, I kept forgetting that it was a web-app at all. – John Clark wrote reviewing JustProto.We took his words very seriously and decided to make a change. After all, people are creatures of habit ;) That is why, from now on, right clicking on the workbench or elements will show a brand new context-sensitive menu!

Also, when you click on any of the elements, the properties tab on the right will show up automatically. Small but significant improvement – saves two clicks before changing the element’s properties. :)

Feature Two – Grouping

You build this amazing wireframe, there’s a gallery there with 10 pictures. After you set it up, when everything’s ready, you need to resize the images to fit 4 new ones. And now what? Resize of all elements is long and can set you back. Resize one and then delete the rest and copy/paste? I don’t think so! From now on, the problem is gone. Grouping option just arrived to the scene! :) Select elements you need, group them and then resize and move everything the way you need it and how you like it. You can find the Group/Ungroup Options in the new Context-Sensitive Menu.

Feature Three – Fade To Gray

If you want to keep focused on the functionalities of the project and not on its outlook this is The Feature for you! It sometimes happens with the clients – showing them the wireframe is one endless series of questions like: “Why this button is light orange, it should be big and screaming red, and this blue line should be two pixels to the left…” And all the UX stuff is non-existing. Crashing into User Experience Iceberg happens a lot – see presentation by Trevor Van Gorp. Fade To Gray lets you… well… fade to gray everything that takes the attention away from UX and interactions of the wireframe.

Feature Four – Border Radius and Shadow

We added two new properties to the properties tab – Border Radius and Shadow. From now on, if you need shadow and rounded edges in your wireframe’s elements – no problem! Just select the element, set up shadow and border radius you want and need ET VOILA!

Also, a little tip: thanks to border radius you can now add a new shape to the wireframe – circle. Just play with the properties :)

We hope new features will help you make your work even easier and faster than before :) To try out new the new stuff login to your account or create new one.

How customer feedback helps us improve JustProto

Another e-mail from one of the users about JustProto features:
One quick question when we share a preview link with the client can I hide the left pane which shows the pages other than minimizing it.

Thanks, Rakesh

Well, a week ago we didn’t have that option.  Sharing a prototype preview link generated by our wire framing tool gave only the option to show your project with a sitemap and that sometimes could lead to tons of questions like: WHAT IS THIS PAGE I DIDNT ASK FOR THIS I AM NOT PAYING FOR THIS!!!! ;)

Now the problem is gone – you can share your wireframe link with or without the sitemap!

We love to help you make your wireframing experience better and better all the time. If any of you guys have another great idea on how to improve JustProto for you just drop us a line here!

Thank you Rakesh for the suggestion!


Check the new feature at work!

Building strategy while designing

IDEO is one of the largest and most important American design and consulting companies. Starting from the industrial design and interaction design (one of the founders was Bill Modgidge) IDEO has extended its consulting services and fell under strategic competence of consulting companies like McKinsey.

What differs IDEO from the others is approach based on using the same tools while designing products, such as user’s observation,analysis of use context, prototyping and iterative process for developing business strategy and marketing.
How design thinking can help building strategy?

Typical tools for strategists such as Excel spreadsheets and PowerPoint slides don’t favor creativity and good communication (as we know, PowerPoint is an evil ;) – seriously, it was responsible for the disaster of the space shuttle Columbia and its use has been banned by NASA.) You can’t properly rethink the whole project if it’s vision is contained in short passwords. PowerPoint slides are boring, and words can be understood differently. Strategy formulated and presented in this way, is trapped in ambiguous abstractions, difficult to clarify and evaluate.

According to IDEO, preparing strategic prototypes is much better solution. Prototype is not the right project, but it is only the presentation of vision engaging emotions and imagination (built to think). The human mind needs to confront some real object or a story to develop an idea and assess its strengths and weaknesses. Prototype can be a mockup of the product, it also can be a comic strip or film, which shows the use of the service in narrative form. An example of such prototype is concept presentation of future web browser Aurora, prepared by Adaptive Path, another company which integrates designing with strategic consulting.

In his article “Strategy by Design” the head of IDEO, Tim Brow, outlines the elements of creating a strategy. At the beginning: hit the Streets. This process of creating a strategy needs to be “human-centered”. To gather interesting insights it’s important to spend some time with consumers, watching their behaviors, personally test the products and services, get know the „user-experience” on which we can often build the whole strategy.

The next step is prototyping:

Design thinking is by nature a process of prototyping. When you are on a promising idea, build it. The prototype is usually a drawing, model, or a video describing the product, system or service. We build these models very fast, they are strict and not very elegant, but they work. The aim is not to create approximations of the finished product, or process, the aim is to gather feedback that will help us resolve the problem. In a sense, we build to think.

When you start rapidly prototype, you begin to build a strategy. Doing this at very beginning of the cycle of innovation, allows you to release the most precious things in your organization: human intuition. When you sit down with team of experienced employees and show them prototypes of products and services that you want to implement within two years, you will learn whether they have an intuitive feeling that you are going in the right direction. It is enlightening trial-and-error method: Observe the world, pattern recognition and behavior, generate ideas, collect feedback, repeat the process and improve project until you are going to be ready to put product on the market.

Prototype tells the story. Prototyping is simultaneously an evaluation process – it generates feedback, which allows you to put the amendments on the fly – and is the process of telling stories. This is the way of visual presentation and experiencing every strategy. – Tim Brown, CEO of IDEO.

JustProto would like to send special thanks to Maciej Lipiec, who gave authorization for publishing this article. You can find original version of this post written by Maciej on his User Experience Blog – http://uxdesign.pl/

Let’s communicate Part 2

Yes, we can finally sit and start the conversation with our client.

Of course conversation doesn’t only mean speaking, it’s both – effective listening and smart presenting our thoughts. How to do it as much clear as it possible?

During conversation remember to:

Demonstrate the initiative

As a for example; Project manager, should show initiative. Do not only listen to what the client has to say about his problems, just try to put yourself in his situation, and propose your own, unique solutions and improvements.

If you suggest him a better solution than client’s one, there is a big chance that you gain a lifelong customer.

Use appropriate language

Use language that the customer can understand. Too many account managers uses technical knowledge terms, which customers do not understand. The famous ancient philosopher Aristotle advised: “Think like a wise man, but speak as a simple man.”

Take a break

From time to time, take a break. In this way, you give the client a chance to remember all informations you mentioned about. Also repeat what client just said, to make sure that you just caught the sense of his speech. It is not always necessary to repeat exactly the same words, same thing can be said in different words. In the meantime, it is good to summarize the most important information, so as to give the customer a chance to get a better view of the situation.

Differences between genders

How women conducts conversations, how men solves problems? Below, some practical comparison which can be usefull while business dialogues.

Women are more interested in the social environment, whereas men focus on their task. This leads to the fact that the conversation of men is more about facts, numbers, when women concentrates on whole conversation atmosphere.

How to refer this knowledge to communication with clients?
When a woman starts an appointment, probably her every choice will be dependent on atmosphere of whole meeting.

Of course, they will want to know a few facts, but they won’t focus on that as man. He will want to know everything about a subject, not paying much attention to the way we will present it.

Therefore, women are more able to forgive us some substantial mistakes, but will require the goodwill and friendly conversation.

Also, ways of solving problems are different. Women like to see the problem from many different points of view. That’s why they want to know opinion of the others about the subject. In company decisions are made together, during brainstorm sessions.

Men depend on their own opinion about the subject. They have specific approach to the issue and want to hold on into it. That’s way, looking for different opinion is not necessary for them. Thus they do not feel need of making analysis of the situation, because opinion of the others have little chance to change anything.

It doesn’t mean that, men-client is not interested in establishing nice atmosphere around or don’t want to know the opinion of the others , and similarly – women-client won’t be interested in any details or can’t take any decision by her own. It’s good to take those differences between genders under consideration and adapt style of conversation to each person.

In third, last part, you will find a few words about non-verbal communication.

Everything is designed

Recently, after Tall Ship Races and famous Heineken Open’er Festival, Gdynia opened city for second edition of Gdynia DesignDays.

The idea of this event was to integrate artists from countries over Baltic Sea, and give them opportunity to present their art-work on exhibitions or sell them in specially arranged containers. You could see there strange and beautiful projects, modern, known and unknown products and innovative items or furniture.

Beside exhibitions, many open conferences and workshops took place. One of them was lecture about open – plan offices issue, given by Małgorzata Grzyb, well-experienced designer and manager at Martel’s planning office. Quick lecture turned into heated dispute where debaters accused open – plan offices to be unsuccessful relict. Małgorzata emphasized their importance in improving the efficiency of every office worker.

What’s all about?

“(…)Open plan is the generic term used in architectural and interior design for any floor plan which makes use of large, open spaces and minimizes the use of small, enclosed rooms such as private offices in which there are no defined property boundaries such as hedges, fences or walls.” (Wikipedia)

Open spaces have a twisted reputation

“Open – plan office is violating human psyche, which effects with serious health problems” – say Australian researchers.

“(…)In 90 per cent of the research, the outcome of working in an open-plan office was seen as negative, with open – plan offices causing high levels of stress, conflict, high blood pressure, and a high staff turnover. The high level of noise causes employees to lose concentration, leading to low productivity” – says researcher Dr Vinesh Oommen from the Queensland University of Technology’s Institute of Health and Biomedical Innovation.

Another problem of open spaces is their lack of privacy. Everyone can see what we are doing on the computer at the moment, hear our private phone conversations – this leads workers to depression and insecurity. According to evolution, every human has right to have his own territory – even at work. Employees also fear that their labor and effort, put in work, won’t be noticeable by employer.

From physical side, “working in an open-plan office could contribute to higher blood pressure”, Dr Oommen said, and an increased risk of illnesses as bugs such as the influenza virus were more swiftly passed around.

Any positives?

Open space gives a perfect opportunity to improve communication and information flow, so solving various problems and issues can be faster and more efficient. What’s more, workers form higher level can easily share experience with those who are lower in career hierarchy.

Open – plan offices are conductive for cementing interpersonal relationships or creating own identity above the others (as a leader, coordinator etc.) Individual work is now in background, open space put teamwork on the top. It’s also a good training in working and behaving in large group. Psychology thesis says (mere exposition effect), that the more often we tend to see particular people, the more we like them. Open spaces favors building positive bonds? Yes, but only when one has an opportunity to choose between contacting or avoiding it.

On the another hand, for employer open – plan offices mean lower cost of arranging working place and much more control under employees and their work.

How to arrange working space for web developers?

Agile Development philosophy promotes dividing room into two quarters – one for those who want to work individualy – providing them an ability for privacy – and the other – for those who are working in groups.

Agile also suggests that working in pairs is a perfect working condition for web developers. Employees may initially criticize moving to open – plan office, but after few months they will appreciate benefits of working together.

Teasley Stephanie made a research about putting web developers together (in the experiment researchers use term “radical collocation” ). Teasley proved that this procedure has a good influence on employees efficiency.

“(…) Our study of six teams that experienced radical collocation showed that in this setting they produced remarkable productivity improvements. Although the teammates were not looking forward to working in close quarters, over time they realized the benefits of having people at hand, both for coordination, problem solving and learning.“(Rapid Software Development Through Team Collocation, Teasley S., Covi L., Krishnan M.S.,Olson J.)

Looking for compromise

Forcing people to work in a team or open – plan office is not good idea, it may result with escaping team or quitting job in general. It’s good to discuss possible removal to open – plan office with every team member. During the discussion we should take into consideration every opinion, fear of our employees and point costs / gainings of such move.

Are open – plan offices better than private, little territories? This is a question which every employer should take under individual consideration. What about working in such open – plan office ? :)

Bibliography:

Let's talk about prototyping

Let’s talk about prototyping

While working as a programmer many times I had to guess what client thinks about. Unfortunately, the specification does not reflect the reality of how the functions should work. This causes lots of problems. First of all, it triggers multiple adjustments, as the customer’s vision is completely different from the vision of the developer.

Fortunately there is a way to improve creating applications and avoid unnecessary (and sometimes time-consuming) amendments. This method is called prototyping.

Prototypes enable showing a vision of how various features and the whole application will look like. They allow the client to set everything as he wants it in the initial phase, and facilitate the subsequent stages of the creation of the site.

I had the opportunity to create a service using the guidelines provided in the prototype. I must admit that supplied the prototype has proved extremely useful and significantly accelerated creation of applications for a simple reason – no unnecessary questions were asked as well as multiple amendments were avoided.

As prototypes are so useful what are the ways of their creation? There are several methods, each radically different from another. Each has some advantages and disadvantages, will take a look at them.

PowerPoint – the use of presentation.

It was one of methods used at our company.

The service sketch is created in an application for creating presentations. It’s strange, but effective. It turns out that a lot of people use this prototyping method.

You can guess the process of creating a prototype in such application looks like. Despite its apparent simplicity and ease of use this method has a significant disadvantage – every time you need to send the resulting file to the client so that they can watch it. Moreover if the prototype needs amendments you must repeat the entire cycle.

Sheet of paper – the traditional way.

IMHO the most funny way to do it. The entire prototype is sketched on a sheet(s) of paper. Do I need to explain how this method seems to be ridiculous for several reasons? The smallest error in the prototype requires recreating it anew. On top of that, sending such a model to a client is quite problem.

Surprisingly Corel used to create paper prototypes, which later were used to test usability. On YouTube you can find a video presenting such a test. I believe that after watching this film there’s no need to mention the deficiencies of such method.

JustProto.com – a new approach to prototyping!

I am proud to introduce on my blog the product in creation of which I had the opportunity to participate. I am talking about justproto.com – tool for online prototyping.

What are the main advantages of our solution? First of all: simplicity. Everything we do is simple because we do not want our users to spend hours learning our tool. Everything has to be intuitive no time lost on getting to know the new environment.

What’s more? Prototypes developed in JustProto are interactive. This means that you can create prototype with dynamic links between the pages.

The online prototype it is available from everywhere, without installing any additional applications.

One of the most important advantages is the creating of a online HTML prototype preview. You simply give your client the link and he will be able to keep track of changes made in the prototype just with refreshing the screen.

If you are interested in prototypes try JustProto now!

Wireframes and Prototypes – 6 common mistakes

It’s hard to imagine the work of information architect without use of wireframes and prototypes. Thanks to them we can see the final product before the graphic and web designers even start working.

Terms website wireframes and prototypes, are often used interchangeably, so you might ask there any differences between them?
Wireframes (and their more advanced form called mockups)are simply drawings of the interface and functionalities. Prototypes are interactive wireframes allowing to test user interaction and usually click through the website.

Hi-fi and lo-fi

Wireframes are traditionally divided into 2 groups, according to their detail level and fine-tuning.
On the “lo-fi” wireframes only basic and interaction compulsory elements are presented. Such project is examined from global perspective and focus is on crucial factors.
The more simplified the model is, the more imagination we use to describe it and it is best suited for preliminary stage of design. such a wireframe can be drawn using pen and paper and that’s how it’s usually done.
The “hi-fi” wireframes look a lot like final product, and are used more common in final phase of design. Here focus is on details of all used elements, rather than general representation. The most mature wireframe is a graphic design that should be created basing on previous wireframes (at least theoretically). Such wireframes can no longer be prepared manually, a software is required.
When do we consider model a “hi-fi? There’s no strict separation. Often, however, following situation may occur: we show the wireframe printout to an Director, President or other important person.
They will usually tell “Oh yes, very cool, fresh, I see progress, good job!” Then usually comes the sentence, which for the first time beats us off the track: “so where can I see this website on the Internet?”
If someone confuses prototype with real website, that is to say that the model is sufficiently “hi-fi.”

What are the common mistakes in the use of mock-ups?

1. Starting from drawing wireframes. This happens notoriously. I arrive at the client to discuss my idea for website mock-up (that I will design) and what do I see? A Beautifully drawn wireframe, or even worse – complete graphic design. You get a graphic designer and tell him: design a new page for us, because the old one is outdated and we need some refreshing. The designer does his job. In such case it is difficult to tell the client that first we should have started working on design. To Identify what’s wrong with present state of web service, how people use it, describe a vision for change, establish short and long term goals, prepare some scenarios, and only then draw it.
Drawing as such is not a bad way to brainstorm what we want to have on the new site. But it must be clear – it is not yet a mockup, it’s just a preliminary sketch.

2. “Joyfull drawing” neglecting the assumptions. When we start drawing, we suddenly bear down fantasy and forget about what we previously assumed. Than sometimes we forget about that couple different functions that should be implemented and … there’s no place for them anymore.
Quite an effective way to stick to the correct path is to make preliminary sketches, mock-ups for each user (role), that we previously designed. Separate role wireframe for main role and separate for each side role. In such case we draw for single user only, if that user does not use specific function it is not represented on the wireframe. This process is time consuming obviously, but it should be implemented for the major part of the product, e.g. for the home page.

3. Focusing on design. This is why it is important to know when we use the “lo-fi “and “hi-fi ” approach.If we start the design with selecting font size, color and background, then it’s to late to talk about the site layout or navigation scheme. Elements which are not in the wireframe are not discussed, so every time we feel like “beautifying” something, it is worth considering whether we want to discuss such details at this stage of design.

4. Using the advanced tools. Is this a mistake? Yes, if we create a “lo-fi” model, tools with multiple drawing and formatting functions (e.g. Photoshop, Corel) can only harm the project. The very characteristics of such a tool makes prototype look much better than we need at this particular stage.

5. Assuming that a good model is an almost finished product. Recently on Axure forum (a popular prototyping tool) I saw a delightful thread by someone who has created a prototype of an intranet for a company, and likes it so much that… it could stay like this. Creating a prototype and final product are two separate processes and cannot be combined without harm to the product.
Only exception I can imagine – we create a prototype in WYSIWYG tool for creating web pages or software – and in such case each prototype leads us closer to the final product. But the use of such tools within larger projects is limited, web sites consisting of only the interface, without the application backend are very rare.

6. Neglecting customers education. Customers should always know what is the purpose of prototypes, which are shown to them.
Cooperation with graphic designers, taught many decision-makers that what they see is “almost” the final product, therefore it contains more or less what the final product will have. What the client sees, and what’s in and not in it – are the basis, that somehow have to be communicated, before the first showing of any design (…).

This post was created by Robert Drózd. Here’s the original post, you can also visit Robert’s blog at www.webaudit.pl/blog/ (in Polish).
This article is available on Creative Commons 2.5 BY-NC-ND license: http://creativecommons.org/licenses/by-nc-nd/2.5/.