Design Development Reviews

Sometime it’s not clear

It’s not always clear what to expect when building software especially when you’re reliant on user stories that don’t describe the full story.

But then again, sometimes user stories can’t be clear without some visual concepts what the users needs.

From experience with visual concepts, many users thought this was it, concrete.

Maybe that’s because it’s down to how polished a design concept is.

Depending what you’re target audience is, it should be very basic to explain itself to the user what each element of a concept does.

Factor in the user’s knowledge of what they may currently know to build the amount of detail needed in the design concept.

We all have to remember that visuals are just concepts, therefore there may be some changes in the pipeline that weren’t considered back then and that they may need looking into present.

Trying a different approach without the visuals is another challenge.

So when you’re building from scratch it only makes sense somewhere along the line where smaller components fit together but still don’t describe what they do.

Adding titles, labels, icons makes sense.

Then you start to see a pattern of inconsistency delivered in Agile methodology, that’s where you’re suppose to constantly deliver.

Sometime it’s better to extend and add a sprint to rectify these issues before it gets complicated to work with.

Yes it adds some time to productivity, but would you rather have this or the latter?


Testing procedures for the web

What is Usability Testing?
Usability testing is commonly used to test something new, a product or service, and measure the reactions of audiences to it. Feedback is then used to improve it with the owner, inventor or developer. The same process occurs again until the owner is happy with it.

One may think this process could become repetitive, but fear not! Only test the most important issues that occur the most and are generally higher priority.

What is Accessibility Testing?
This is concerned more with people with disabilities. How would one interact with something if they were blind, deaf or unable to physically touch and move something? These are the major concerns to address and solve. This is similar to usability testing.

Do not mistake Focus Groups as Accessibility & Usability Testing!
Focus groups are groups of people (roughly 5 to 8) working together as a team about ideas and design to gather all thoughts into different concepts.

Usability testing is a one person process guessing which item to test and how to use it.

In contrast, accessibility testing is focused towards disabled people, inventing alternative methods when using products or services.

But focus groups have advantages, they can determine what the audience wants and needs and also test the idea behind the site, making sure it makes sense and it appeals to them.

The disadvantages are that it is difficult to acknowledge whether the product or service works and if improvements can be made.

Focus groups are better done in the research task and during the idea generation and development process for fine-tuning, but don’t mistake them for usability testing. They cannot tell whether people can use the product or service.

So when should test take place?
It’s common sense to continue testing throughout the whole process. When researching, there’s a test to compare existing products or services in competition. After idea generation, ideas can be compared and combined into one final idea. Various problems may occur which can be corrected.

Who should do the testing?
By now, one will know how many tests are to be done, but the first test should be done with a small group of all ages and genders who know about a product or service. After this anybody will be able to participate, thus saving time. Any business or company should do as many tests as possible for accuracy.

Testing in a professional environment.
In a professional environment, 2 labs should be hired with a very large mirrored wall in-between them. The owners, inventors or developers watch from one lab to the other and observe the person and the prototype tested.

Simple testing without using professionals.
Use one room with at least 2 cameras to record the person and product being tested, which will be used later with the owners, inventors or developers.

The problem with simple testing is the professional environment can be costly to businesses. Compared to simple testing, it’s far cheaper and flexible for businesses and the people involved.