B i r d L i f e
W e b p a g e r e d e s i g n
W h a t t h e y d o
BirdLife Australia is Australia’s largest bird conservation organization. As an independent, not-for-profit organization, the aim is clear : to create a bright future for Australia's birds. Like you, birds are in our nature.
O u r G o a l
To successfully redesign the BirdLife website to enable better user efficiency, usability and accessibility to information using in depth analysis and research and implementing UX/UI methods
T h e P r o c e s s
Research
​
Usability Testing
Infinity Mapping
Synthetization
Prioritization
Storyboarding
SWOT
​
Design & Test
Wireframing
Card Sorting
User Testing
​
Iteration​
​
Mid Fi Prototyping
User Testing
Design Iteration
Style Guide
​
Prototyping
Final Product
Reflection
​
D e f i n i n g t h e P r o b l e m
BirdLife was designed to achieve public access to information regarding the preservation of the Australian bird population and environment and encourage users to donate to the cause. We have observed that the current BirdLife webpage is difficult to navigate which is turning users and potential volunteers/ donors away from the site. How might we improve the BirdLife website so it can entice users (both new and existing) to engage with the website and all of its valuable information and encourage involvement with bird preservation in Australia
P e r s o n a
To begin our research, we created a proto persona in order to gain insight on potential users. The proto persona enabled us to create empathy with users so we could better understand how to design for them throughout this process
U s e r F l o w
To further understand the website, we created a user flow. This informed us how a user would move through the website and the necessary actions required to complete an action, such as donating.
E v a l u a t i o n
We did a heuristic evaluation on the existing BirdLife webpage. Using the 10 general principles for interaction design, we unfortunately found that the current BirdLife website was not adhering to most of these general rules.
C o m p e t i t o r A n a l y s i s
Competitor analysis was up next so we conducted a SWOT analysis. A few key opportunities arose from this that would enable us to showcase how the BirdLife website could not only match but outweigh its current competing websites
U s a b i l i t y T e s t i n g
After our initial research it was time to put the original BirdLife website to the test. We devised a few tasks for user’s to complete so we could see how they were navigating through the current website
U s a b i l i t y R e s u l t s
The results of the usability testing were incredibly informative. After we synthesized the results we had a clear understanding of some of the pain points our users were experiencing. Understanding user behavior allowed us to move forward and define our problem statement
1.
​
Users were struggling to find the information they desired
​
2.
​
Users were intrigued by the “Find a Bird” function but they found it difficult to use
​
3.​
​
Users could easily donate but got annoyed at the amount of information required to make a payment
​
4.
​
The information and flow of the site was cluttered and confusing. Users were often unable to navigate the site
​
S i t e M a p
When we had a look at the original website, there was a lot of cluttered information that users were struggling to process, so we condensed all of the content into four main categories. This would help solve a user insight from the initial usability testing
W i r e f r a m i n g
When we had a look at the original website, there was a lot of cluttered information that users were struggling to process, so we condensed all of the content into four main categories. This would help solve a user insight from the initial usability testing
S t y l e G u i d e
Creating a style guide was the foundation of moving forward into mid/hi fidelity prototyping. We chose a sunset orange to compliment the elegance and simplicity of our font as it is mimics the colour and tone of some Australia native birds
I t e r a t i o n s
Having a border on the event dates hinted that there was an event on. We also gave them the option of viewing the events in a list format
Testing proved that placing one of our most important features in a submenu made it difficult to find, so it became its own header in the menu
Finding there was an overload of information on the website, we sorted group content appropriately
F i n a l P r o d u c t
Through multiple rounds of testing and iteration, we arrived at our final product
