What’s wrong with the current design?

The 9 projects all currently have wildly different designs and not in a good way. Notangles and Freerooms look like MUI knockoffs; Chaos and Jobsboard are cool; CSElectives has a stock-image looking illustration on the landing page. It’s just all looking a little messy right now and doesn’t give the impression that all of these amazing projects were built by CSESoc so ultimately, the goal is to change that.

How are we going to achieve this?

• Receive feedback from all the 9 projects about their current website, any existing redesigns, intended future functionality and style guidelines (i.e. colours, fonts).

• Create typography and colour palettes to be used in hi-fidelity wireframes and standardise future designs.

• Create re-usable components and tokens to make the designing process easier and more organised.

• Get feedback from a control group of volunteers as well as the Project teams.

Do we have a timeline for this?

• Yes and no? We are currently already in development for certain projects based on our priorities. We have different timelines for each of them (eg: Term 1 for CSElectives)

Why are we doing this?

With different projects having to work with similar components, it only makes sense to have a standardised component library that they can use. This eliminates the need for duplicate, badly built components that fails to meet modern UX guidelines.

How are we going to achieve this?

• Finalise branding (see the above vision dotpoint for more details).

• Create high fidelity designs of components that everyone (control group of students as well as the ‘client’ we are designing for) is satisfied with.

• Consider how these high fidelity components can be re-used throughout different Projects (create variants etc. as needed).

• Code components up on GitHub and make it available to all projects.

Do we have a timeline for this?

• This part will be worked on continuously throughout the year. Basically, the idea is that once the UI/UX team designs a component, we will then implement it in code.

Why are we doing this?

This is to ensure that an “above satisfactory” user experience is achieved. We are hoping to make the projects more mainstream to not just students in UNSW but also students in other universities as well.

How are we going to achieve this?

• Talk to online/discord bot directors about the control group.

• Ask the control group to navigate through the projects with different goals (the usability of each design can be quantified by counting the number of clicks, timing how long it takes to reach a certain goal).

• Improve as needed, and keep testing.

Do we have a timeline for this?

• Usability must be considered continuously by asking fellow subcommittee members and directors for feedback.

• Testing will be done as soon as a substantial amount of the high fidelity wireframe is completed (i.e. enough for a goal to be created for the control group to complete).

• There will be more formalised testing with more user groups once the entire wireframe has reached its first MVP state.

Why are we doing this?

We would like to ensure that our team members are always comfortable asking questions and learning.

How are we going to achieve this?

• By holding frequent bonding and team events (at least one per every 4-6 weeks).

• By allowing them to have more ownership over projects/designs as they progress.

Do we have a timeline for this?

Will be done gradually throughout the year.