Logan Together

Logan Together is a not-for-profit organisation that helps service providers, community members, and professionals work together to improve the development of kids in Logan, Queensland.

Lucas and I were contracted to deliver a website that was more organised, easier to manage, and accessible to an audience spanning multiple roles, levels of education, and levels of engagement with the organisation.

UI elements from the new website design

The challenge

Logan, Queensland is a city that is subject to lower child development rates for kids aged 0 - 8. These rates are lower than the Queensland average and lower still than the Australian average.

In a bid to tackle this, dozens and dozens of uncoordinated initiatives have been launched around the city to try and alleviate this, however because there are so many of them, they tend to step on each others' toes and be less effective than they otherwise could be.

Logan Together helps sector workers, funders, and the local community work together to help bring about a more coordinated effort.

While the organisation is known worldwide as an example of this “collective impact” approach, for the average community sector worker or member of the community, Logan Together has had a lot of trouble communicating what it does in a clear, concise way which everyone can understand. Even people who have some involvement in the project don't necessarily know all the ins and outs.

Our role was to identify how their website was contributing to this problem, and rebuild it to:

  • Clearly communicate what Logan Together is and what it does
  • Show the impact the organisation is having
  • Encourage others to get involved

Governance structure

Diagram showing the different groups of people who are involved in Logan Together: community leadership groups, Logan Together leadership table, Government networks (local, state and federal), the action group, partners, the backbone team, the logan friendly childhood board, and the first nations people-led warril yari-go karulbo, which sits in the centre of the diagram.
Logan Together brings together many different groups of people to make sure that projects in Logan co-ordinate effectively.


  • Discovery research
  • Usability testing
  • High fidelity prototype
  • WordPress website


Chris Wood
UX Designer
Lucas Cumsille
Web developer


Karen Murphy
Product Owner (Logan Together)
Matthew Cox
CEO (Logan Together)


4 months, full-time



My research objectives were to:

  • Identify Logan Together’s pain points with the site
  • Discover what the target audiences think of the site
  • Find out which pieces of information the target audiences need to access and where they expect to find them.

Staff interviews

I wanted to find out more about the different roles in the organisation, the backbone team’s day-to-day responsibilities, and how the website affected their work.

I conducted individual and group interviews with 11 of the backbone team members. This gave me insight into each department’s needs and pain points with the website.

“We sell ourselves short because we can't demonstrate what we're doing and people can't find what we're doing."

Customer interviews

The range of people which Logan Together works with was extremely diverse, ranging from interstate investors through to local parents. We decided to focus our research on two groups of people who Logan Together felt could really benefit from the website: community sector workers and members of the local community who were new to or interested in Logan Together.

I spoke with 7 sector workers and community members to find out more about their involvement with Logan Together (if any), what they understood about the organisation so far, and their experience using the website.

"I still don't know who this website’s entirely for."

Content audit and card sorting

The Logan Together website had been built 5 years earlier to mostly acommodate static content. However, over the years, the organisation had outgrown this and was now using it to post information about events, opportunities to get involved, and updates on the movement.

To do this, the team had tacked on pages haphazardly all across the site without any clear structure.

I took the opportunity to create an inventory of every piece of content on the site. I also asked website users to group the different types of content together in a card sorting activity. This helped me understand where users would expect to find different pieces of information and informed the new sitemap.

Google Analytics and PageSpeed

Analysing data on which pages were the most accessed, how users navigated through the site, and the websites which users originated from helped me to understand what users were trying to accomplish.

Lucas also used Google PageSpeed to uncover a number of technical concerns with the website which was making it slow to load.


Usability problems

Participants overwhelmingly mentioned how out of date the information was on the website, with this being mentioned in 10 out of 15 interviews.

Many participants also cited problems trying to find the information they were looking for, either due to:

  • Information being poorly organised (8 out of 15 interviews),
  • Difficulty navigating the website (6 out of 15 interviews), or
  • Information being hard to understand because of the language used (6 out of 15).
Bar chart showing the most commonly cited usability problems. Out-of-date information was mentioned ten times, and information being poorly organised was mentioned eight times.
Usability problems, sorted by the number of interviews where that topic was mentioned. There were 15 interviews in total, 2 of which were group interviews.

Key effects of the site's usability issues

These issues had a number of knock-on effects for the organisation and the users, including:

  • lack of understanding in the local community on what Logan Together do and their value, making it harder for the organistion to have an impact.
  • Community members feeling overwhelmed when they access the site. This was also making people involved in Logan Together feel uncomfortable referring others onto the website for information.
  • Sector workers and volunteers calling up asking for information because they couldn’t find it on the website, taking up the backbone team’s time.
"Do I refer people to it these days? Very rarely, because it's too messy.”
“It was overwhelming to navigate"
Root causes diagram. On the bottom are the following causes: Outdated content, and information being poorly organised. This is causing users to have trouble understanding what Logan Together does, causing members to call Logan Together because they can’t find the information they want,  causing community members to feel overwhelmed, and causing members to feel uncomfortable referring others onto the website.
Root cause diagram, showing the factors which made the website unfit for purpose and the knock-on effects this had.

Causes of these issues with the site

Our staff interviews uncovered several root causes for how the website came to have these problems, which Lucas and I were able to categorise into two themes:

The organisation
  • The task of maintaining the website was under-resourced.
  • There was no clear process for staff to upload content.
The website
  • Staff found it difficult to manage the backend.
  • The backend was not built to accomodate dynamic content.
  • There was no clear strategy for targeting content to specific audiences.

Opportunities for improvement

Content audit
Card sorting

Addressing user needs

I created personas to represent the needs of the different audiences I interviewed. Working with Lucas to reduce my own bias, we analysed the interviews in Dovetail, tagging and grouping key phrases which highlighted:

  • What the participant currently uses the website for
  • What they struggle with
  • What they need from Logan Together.

This allowed me to focus on adding the most value to community members and sector workers in the new designs.

Graphic showing a preview of the personas for community members and sector workers.

Improving the information architecture

I catalogued every piece of content present on the site with a content audit to help me create a new, more coherent information architecture. In addition to duplicated and hard-to-find content, many pages had simply been forgotten about and were several years out of date.

I also asked 6 sector workers and community members to complete a card sorting activity. This gave me insight into how these personas grouped content together in a way that made sense to them.

These two artefacts allowed me to create a new sitemap which:

  • Structured information in a way that’s intuitive for users
  • Priotised content based on Logan Together’s goals
  • Removed duplication of content
Illustration showing stylised blocks of content stacked on top of one another

Improving page structure

Almost all of the content on Logan Together’s website was formatted as a single block of text.

We decided to lay out each page using reusable components to help users scan through a page’s content, with the aim of making it more structured and less overwhelming. We also hoped this would help users find what they were looking for more easily and reduce the effort required in development.

Rebuilding the back end

To make the backend easier to manage, we built it as a series of reusable components to break up the different options available into logical sections.

This made the backend more flexible, as content editors could add, remove, and rearrange blocks within pages to accomodate for the organisation’s changing needs.

To reduce the amount of duplicate content, we took a relational approach to managing the data, ensuring that if a piece of information was shown in multiple places, it came from one single source. This would make the website less prone to becoming out of date because content no longer had to be updated in multiple places.

Lastly, to make the website more accessible for all user groups, Lucas took measures to increase the page load speed on mobile and desktop in the new website build.

A graphic page-builder layout with a tooltip asking the user which staff members they’d like to display on the page.

Testing & prototyping


Iteration 1

The initial prototype

I produced two low-fidlelity prototypes - one for desktop-based sector workers, and one for mobile-based community members - which aimed to:

  • Make the website easier and more intuitive to navigate
  • Use new content to explain more clearly what Logan Together is, its goals, and how it works
  • Provide more information about Logan Together’s projects
  • Show the progress the organisation has made with data
  • Advertise current opportunities for people to get involved with the movement.

I then conducted remote moderated usability testing sessions to measure how effectively it met these goals and to uncover further issues. I tested with 20 participants over 4 iterations.

Our first desktop iteration, ready for usability testing

Testing and iterating copy

Our first round of testing revealed that community members were confused by the indirect language and jargon which Logan Together used in their copy.

I worked with the client to iterate on the key pieces of copy which describe what Logan Together is and the work which they do, testing each iteration until it was more widely understood.

I also produced a copy guide with detailed feedback from testers for Logan Together to use when writing content about their projects, to help them produce copy which was easier to understand for users.

We iterated on key pieces of copy until testers could understand them more clearly
A comparison of copy from the first iteration to the last iteration for the “What is Logan Together” section. The first iteration used very vague language, whereas the last iteration uses more direct language and gives a more detailed description.

Making it easier to contact a member of the backbone team

"I’d go contact? I would look there... I couldn't find them. I'm stuck now."

During testing, sector workers struggled to work out how to contact a specific person on the backbone team. They would often go to the “Contact” page and get stuck.

To alleviate the problem, I added a component on the "Contact" page which linked to the “About > Governance > Backbone team” page containing information on each member of the team.

Added a link to the staff directory on the Contact page
By the final iteration, 5 out of 5 sector workers were able to contact a member of the backbone team
"Oh, staff directory. Yeah. I guess I could click… oh that's cool. And then I can find Karen there. Yeah. That's good."
Diagram showing a button with the text “See the staff directory.” An arrow links this button to a grid showing the different staff members with their name, job title, contact details, and biography.
A link on the “Contact” page takes the sector worker to the staff directory, where they can contact a member of the backbone team directly.
Graphic showing the modal which appears when a user clicks on a partner tile. The modal contains the partner’s logo, a link to the partner’s website, the email address and name of the primary contact, and a description of the work the partner does.
The “Partners” page shows which organisations are involved the movement and how to connect with them.

Helping sector workers connect with each other

During testing, we discovered that sector workers work more effectively when they can connect with others who are working in a similar area to them.

For each organisation on the "Partners" page, we added a bio, contact details, and a link to their website to help sector workers discover and connect with each other.

"Being able to see who's who and have a one-on-one conversation with them is really valuable."
Added a bio and contact details for each partner

Iteration 4

Features of the final prototype


Final prototype

“The pictures are more reflective of the community of Logan. So I'm very happy about that.”
“It's much cleaner, less cluttered than the current one. It seems to be much simpler.”
“It looks very inviting.”
“It's much easier to find pieces of information. They’ve obviously put a lot of work into thinking about how it’s organised”


"I really enjoyed working with Chris. He was knowledgable and made the whole process very easy. His research helped me 'sell in' concepts to my organisation, making the final product exactly right for the audience!"
Karen Murphy
Product Owner (Logan Together)

After presenting the prototype and testing feedback to the stakeholders, they were excited to proceed with the project build.

Lucas developed the website in WordPress and we provided Logan Together with a guide on how to add, remove, and manage content in the backend. We produced video walkthroughs and written steps, and organised all the content in a Notion microsite.

We also helped migrate old content over, and Logan Together is currently content populating the website with information on the projects they are involved in before launching it.

Would you like to work together?