User Experience Part One
| Site: | QSC |
| Course: | Q-SYS Level 1 Training |
| Book: | User Experience Part One |
| Printed by: | Guest user |
| Date: | Thursday, 21 November 2024, 3:45 AM |
Description
Video Transcript
0:08
Time for a reality check: It doesn’t matter how well you
0:12
design your Q-SYS audio system if the user can’t figure out how to operate it.
0:16
For most end users, their only interaction with Q-SYS.
0:20
is going to be in the form of the User Control Interface that you design for them.
0:24
Now, whether that’s on a QSC Touchscreen, an iPad or iPhone, or a PC Viewer,
0:31
this UCI is their only access to the audio system.
0:34
As far as they’re concerned, that UCI is Q-SYS.
0:38
If you design a clunky UCI that’s hard to navigate, then they think that Q-SYS sucks.
0:44
And it doesn’t! We here at QSC are relying on your UCIs to represent Q-SYS to the world.
0:51
So whether you like it or not, you have to consider
0:54
the user’s experience when you’re designing their interface.
0:57
In this video series, we’re going to discuss some basic
1:00
design principles that contribute to a positive user experience.
1:04
For some people, this may be second nature.
1:07
For others, you may learn some things you’ve never considered before.
1:11
While we’ll be focusing on building UCIs with the Q-SYS Designer software,
1:15
the design concepts we’ll cover here are universal and you may start to notice
1:20
these principles whenever you interact with a new website, software or app.
1:25
This is a crash course in design philosophy.
1:32
Let’s start big: you don’t have to be an artist to design a good UCI.
1:38
Yes, a skilled graphic designer can add a lot to the visual appearance of a UCI,
1:42
but we’re not trying to turn you into a graphic designer right now.
1:46
This video is about making a comfortable, intuitive, and functional UCI,
1:50
and you don’t need any Photoshop skills for that.
1:53
At the highest level, just keep this one thing in mind: design is intention.
1:59
What does that mean?
2:00
Well, imagine that you’re working on your computer at your desk,
2:04
and you have a coaster for your coffee mug.
2:07
Where does that coaster go?
2:09
If you’re right-handed, you probably instinctively placed it to the right of your keyboard,
2:14
with your intention to make it as easy and natural to use as possible.
2:18
You designed it there, based on where you naturally want it to be.
2:23
You probably didn’t put it inside a drawer, because only an insane person would keep their coffee there.
2:29
Building a UCI is similar; you just probably have to spend a little bit more time
2:33
figuring out exactly where the user instinctively wants to find everything.
2:39
So what’s the first step? Figuring out who that user is!
2:45
Do a little research into who is actually going to be using your UCI.
2:49
Is this a maintenance UCI for the venue’s engineer?
2:52
Is it a public UCI that anyone can interact with?
2:56
The interface you build for something even as simple
2:58
as an Audio Player might be very different depending on who has access to it.
3:03
If you’re able to, it would be worth your time to talk to the actual people involved.
3:08
The more people you talk to, the more you’ll get a good sense of what they need from the UCI.
3:13
You should also consider how many UCIs and Touchscreens are required in the venue.
3:17
If multiple people need to access the same device,
3:20
you have to consider whether you should build a single UCI specific to that device
3:25
that services all their needs,
3:28
or whether it might be better to build separate UCIs that they can log into individually from any device.
3:34
In Q-SYS, you can change a touchscreen’s properties to allow “Dynamic UCI assignment”,
3:40
which allows a user to choose between different UCIs.
3:44
Knowing which method to choose will probably become
3:47
more obvious once you complete the next step of design: Planning!
3:52
You may want to start by drawing a flowchart to guide you through all of the possible functions of the system.
3:59
This is called the taxonomy of the system,
4:02
a chart that will help you to group related concepts together under logical categories.
4:07
Taxonomy is a term you may recognize from taxonomy charts of plants and animals
4:12
that separate them into kingdoms, genuses, phylums,
4:15
all that other stuff from school that you’ve forgotten about.
4:18
Structure out your UCI the same way, before you start building it.
4:23
How many different pages or layers do you need for each task, and what makes sense for your venue?
4:29
Like everything in design, there’s no right answer here.
4:32
Maybe you want a Main Page that lets the user navigate to each of the rooms in the venue,
4:37
and from there you can choose between Audio Control or Lighting Control within that room.
4:41
Or maybe it makes more sense to choose between Audio or Lighting first, and then select a room.
4:47
It will all depend on the different tasks you want to make available,
4:51
and it’s worth the time to organize them in a way that lets the user accomplish each task as easily as possible.
4:58
Within Q-SYS, you can build as many different pages on each UCI as you like.
5:03
And don’t forget that there are a variety of ways you can navigate from page to page.
5:08
Simple UCIs may take advantage of the Page Tabs to select different pages.
5:12
Page tabs can be placed on any edge of your UCI to provide simple menu navigation.
5:19
Or, you could disable these tabs and let the user simply swipe from page to page.
5:25
But more advanced UCIs might have a more complicated menu structure,
5:29
so you probably want to disable the swipe option and instead use the
5:33
Navigation Buttons to direct your user from page to page.
5:38
Navigation buttons can send the user to one particular page,
5:42
which lets you guide their movement more specifically.
5:46
And don’t forget that you can also use Popup buttons to hide away certain controls.
5:50
Just add a popup button from the layout components, and add any number of controls inside its popup window.
5:58
You can resize that window and move it around, and then close it to keep those controls hidden.
6:04
Or – if you’re interested in diving into a little bit of coding – you can
6:08
script different layers to transition on and off-screen as well.
6:12
But whether you’re using pages, popups, or layers, they’re all a part of the taxonomy of your system,
6:19
which is why a flowchart can help you plan out your UCI before you build it.
6:24
A big thing to consider during this planning process involves ... choice.
6:29
What choices do you want to give the user? I mean, choice is a good thing, right?
6:33
Well of course it is … but it can also be a bad thing.
6:36
A design that doesn’t provide enough choices can seem too simplistic or even condescending.
6:42
But too much choice can be a huge problem as well.
6:45
If it takes the user a long time to find the thing they’re looking for,
6:49
or they’re never certain which button to press,
6:52
then the system appears to be too complicated and difficult to work with.
6:56
So, if you feel the need to overcomplicate your UCIs, just blast that idea out of your head right now.
7:10
Providing a user with fewer choices will increase the speed with which they can navigate the system,
7:16
and reduce the number of errors they make along the way.
7:19
Let’s look at the Audio Player again, for instance.
7:21
You may be tempted to drag all these controls onto a UCI so the user can do whatever they like,
7:27
and in some cases that may be fine.
7:30
But if this Audio Player is just playing background music in the Lobby of a hotel for instance,
7:36
does the receptionist really need the ability to fast-forward or rewind the song?
7:41
What about this Auto-Play button?
7:44
This button tells the Audio Player to automatically start whenever the design is pushed to a Q-SYS Core.
7:50
Does the Lobby receptionist know that? No.
7:53
This button will probably just confuse them,
7:56
and you never want the user to be confused when they’re operating your system.
8:00
You want to provide just enough choices so they can accomplish their tasks,
8:04
but not enough choices that they can get themselves into trouble.
8:08
So to recap, research and planning lets you identify the main tasks that your UCI should facilitate,
8:15
and give you a ground plan on how you want to organize the UCI’s page structure.
8:19
Determining which choices your user can make plays a big role in the UCI’s complexity.
8:24
Once you’re comfortable with knowing what you want your UCI to do, then it’s time to start building it.
8:30
In the next video we’ll take a look at common design philosophies to keep
8:34
in mind when you start building the UCI.
Lesson Description
Learn basic design principles to enhance the user experience of Q-SYS.
Tips and Definitions
Coming soon!