01:25	Okay. Um welcome to our second meeting. This is the functional design meeting. And I hope you all had a good individual working time. Okay, let's get started. Okay, here's the agenda for the meeting. After the opening um I am going to
01:43	fulfil the role of secretary, take the meeting minutes. And we're gonna have three presentations, one from each of you. Then we're gonna discuss some new project requirements. Um gonna come to a decision on the functions of the remote control. And then we're gonna close up the meeting. And we're gonna do this all in about forty minutes. @
02:02	Okay. First I want to discuss the goals of this meeting. First we need to determine the user requirements and the question that we can ask ourselves is what needs and desires are to be fulfilled by this remote control. And then we're going to determine the technical functions, what is the effect of the apparatus, what actually is it supposed to do, what do people pick up the remote and use it for.
02:31	And then lastly we're going to determine its working design, how exactly will it perform its functions, that's the whole technical side of -
02:42	'Kay I'll just give you a minute, 'cause it looks like you're making some notes.
02:49	#
02:49	'Kay.
02:52	Oh, well let's go ahead and, @ back, previous. So what I wanna do right now is hear from all three of you, on your research that you just did. Who would like to start us off?
02:52	# $
02:55	#
03:10	'Kay.
03:10	I don't mind going first.
03:11	Okay. Um do you have a PowerPoint or no?
03:14	Yeah, it's in the - should be in the m- Project.
03:16	Okay.
03:16	Do you want us to do our PowerPoints now or -
03:18	You know you could you could do it yourself actually.
03:21	Oh.
03:21	Did you send it?
03:23	Save it in the project documents. Okay.
03:23	Put it in Project Documents, yeah.
03:31	Mm-mm-mm*.
03:36	This one? Okay.
03:38	Sure. $
03:42	Yeah.
03:44	Okay. Great.
03:44	Okay.
03:48	Um well, the function # of a remote control, as what uh we've been informed, is basically to send messages to the television set, for example, switch it on, switch it off, go to this channel, go to channel nine, turn the volume up, etcetera.
04:09	Um some of the considerations is just um for example the what it needs to include it's the numbers, you know, zero to nine, so you can move to a channel, the power button on slash off,
04:23	the channel going up and down,
04:26	volume going up and down, and then mute,
04:30	a mute function. And then functions for V_H_S_, D_V_D_, for example, play, rewind, fast-forward, stop, pause, enter. And enter would be for like, you know, the menus. % And then other menus for D_V_ as well as T_V_, whether that means like um we can go and decide the brightness of the screen, things like that, all the more complicated functions of menus.
04:53	@
04:54	And we can decide if that's what we want, @, um if we want to include that on the remote, if that's something that would stay on the T_V_ itself, for example.
04:57	Okay.
05:02	Okay.
05:03	These are two examples. Um and you can see on the left, it's got a lot more buttons, and I don't know if you can read it, but it says, step, go to, freeze, um slow, repeat, program, mute, and so those are some of the buttons and so it gives you an idea of s- one example. And then on the right, it's a lot more simpler, it's got volume, it's got the play the like circle set, which is play, rewind, but it's also what is - fast-forward is also like next on a menu. So you have functions that are d- uh duplicating.
05:06	%
05:39	Right.
05:39	And you have a mute button and then the numbers and the eject, and the power button. So that gives you two different kinds, a more complex and more simple version.
05:47	Okay.
05:48	Ready.
05:49	And then lastly, it's just the questions that we want to consider like what functions do we want it to include, and how simple, complex it should be? And what functions it needs to complete. Uh, what are needed to complete insulation process, 'cause, you know, that's something that also has to be considered and it's gonna be hopefully a one-time thing, when you set it up it should be set to go, but we have to include the functions that can allow it to set up i- in the first place.
06:18	@
06:18	So that's it.
06:20	Alright. Very good presentation. Thank you. You speak with such authority on the matter. $ Okay. Who would like to um follow that one up?
06:26	Mm. Left.
06:32	Now, that we've discussed - Okay. Do you want me to run it or you wanna - Okay.
06:32	I can go.
06:35	Yeah, you should run it.
06:38	[do d- do sounds imitating whistling]
06:40	Functional requirements. 'Kay.
06:41	# Mm yes.
06:50	Alright. Now we have Courtney with the functional requirements.
06:53	Yes, okay so we tested a hundred subjects in our lab, and we just we watched them and we also made them fill out a questionnaire, and we found that the $ users are not typically happy with current remote controls. Seventy five percent think they're ugly. Eighty percent want - they've - are willing to spend more, which is good news for us um if we make it look fancier, and basically w- we just need something that really I mean there's some other points up there, but they - it needs to be snazzy* and it - but yet simple. So that's really what we need to do. And we need we need it to be simple, yet it needs to be high-tech looking. So -
07:29	@ Wait.
07:37	And that meaning what?
07:38	Like -
07:40	They like I guess use the buttons a lot. Yeah.
07:43	Okay.
07:45	I don't know. It's from my uh research.
07:45	@
07:48	Right.
07:49	Okay, what do you m- Oh, I'm sorry. What do you mean by um the current remote controls do not match well with the operating behaviour of the user, like they have to press the buttons.
07:49	My team wasn't very clear. $ That's okay.
07:50	Only use ten percent of the buttons.
07:58	I I think it's like the engineering versus user, whereas like the engineering she showed that the engineering ones are more complex and users don't really need all of the buttons that are contained on there, because they only use ten percent of the buttons really.
08:00	Okay.
08:05	Oh, right.
08:09	The buttons.
08:11	Okay.
08:11	#
08:13	Yeah. Okay.
08:14	We only use ten per cent of our brains. $
08:16	$ %
08:17	Good point. It's a necessary evil.
08:18	It works. $ Ready for the next slide?
08:20	# yeah.
08:21	Mm-hmm. # And so people say that they typically lose it, as you yourself know, because you probably lose your remote control all the time, much like any small appliance like a cellphone, and they - we need something simple, because most people, well thirty four percent say that it's just too much time to learn how to use a new one, and we don't want to go - we don't want to vary too far from the normal standard remote, but I mean they do need to be able to identify it, and R_S_I_, I'm not very sure what that is.
08:30	Hmm.
08:31	Lost.
08:46	S-
08:53	It's okay. It's very important. $
08:54	Yes, it is important for the remote control world.
08:56	Wait, is that like your -
08:57	$
08:59	Sh-
08:59	ergonomics like your hand movements or something?
09:02	Could be, yeah.
09:02	Uh possibly.
09:04	Do we really need t- to provide more information on what R_S_I_ is?
09:07	Like - $
09:08	Uh yeah, that's what my web site said, I
09:08	Oh.
09:11	Channel, volume, power.
09:11	don't know.
09:11	I think that's a pretty good guess though.
09:13	Yeah, I would assume so. I think we're supposed to know it as remote control experts. $ But also s- so the channel, the volume and the power buttons are the most important on our company website you can find like the specific statistics concerning to how much each button is used, but those are the definitely the top ones.
09:13	%
09:15	It's like if you're holding it -
09:18	Yeah. It's okay. $
09:34	Okay. Next slide?
09:36	Yes.
09:37	And so personally I think that we need a modern eye-catching design, but it it really needs to be simple. So saying from y- your slide, your presentation, the engineering versus the user-specified remotes, I think that we should go with something that's more user-friendly. Where the engineering ones, the boxes, tend to make it look more complicated than it really is. Um the functionality of the product really needs to be considered as to like what type of buttons do we really need on it.
09:53	User-friendly.
10:08	And it needs to be open to a wide range of consumers, so even though we need a small number of buttons, we also need to take in - like are most people going to be using it for a D_V_D_ player, a TiVo, what what exactly are we using it for, as well as the age range. So we need a hip, but not a corny marketing scheme for promoting our product. And also we found - our team found that speech recognition is - it's like an up-and-coming thing they really - consumers are really interested in it, and since our findings found that people are willing to pay more money for a remote for it to be more high-class we could consider it.
10:31	@
10:48	And so just to - just to clarify by speech recognition you mean they would say, channel five, and the thing would go to channel five?
10:54	I guess so, yeah.
10:55	%
10:56	Okay.
10:57	@ to just say, where are you, and thing beeps, you know. $
11:00	$ Oh, that'd be lovely.
11:00	Yeah, I guess we can interpret it like, we can just try out different types of speech recognition within our remote programme.
11:04	Yeah.
11:06	# Didn't they - um didn't our rival companies manufacture a remote that you would press the button on the T_V_ and it would - the remote would beep so if you have lost it -
11:15	It's kinda like what the remote phone used to do.
11:17	Mm. Oh, yeah, that's true. We could definitely include that if we wanted to.
11:18	You know like go to the base. Yeah.
11:22	If it's within our price. Okay. Are we ready for our last presentation, Amber?
11:28	Yeah, I'm just trying to move it.
11:29	Okay.
11:38	'Kay. I think it should be there, working design.
11:40	Working design.
11:42	There we go.
11:42	%
11:44	'Kay.
11:45	'Kay. Uh I didn't get a chance to complete this one, 'cause some of the tools that I was given were frustrating. Uh okay, so method method of our design, I think I just start listing th- some of the things that we actually need to put into this. We need a power source, we're gonna need a smart chip if we're gonna make it multi-functional. Um extra functions will probably need an additional chip. Either that or the smart chip will have to be extremely smart.
11:48	Oh my bad.
11:53	#
11:53	Oh that's fine.
11:54	Help me.
12:18	$
12:19	What exactly is a smart chip?
12:21	Usually a smart chip is just a chip that's been programmed and designed so that it can complete a fair range of functions.
12:29	Well, how much extra would the additional chip be? Is that gonna push us over our production costs?
12:34	I wouldn't think so, 'cause we could probably get it from like, in bulk, from a a newer company. And they tend to sell their chips pretty cheap.
12:41	Mm-hmm.
12:43	Okay.
12:45	Ready?
12:45	Um yep, nothing here.
12:48	$
12:48	That's okay.
12:50	Um power source, I figured, batteries, 'cause they're easily available. Typically a remote has either two double A_s or four triple A_s, sometimes three. Uh it really kinda depends on the size of the actual remote itself. Um a large on-off button, # demographically we're moving towards an older generation of people, so a large on-off button would probably be good. Selection button for various entertainment devices, so you want something that will permit you to select the D_V_D_ player or the T_V_ or the stereo system.
13:01	@
13:13	$
13:15	@
13:16	Hmm.
13:27	Um smart chip that perverts - uh that permits, sorry, universal application again,
13:35	something that'll allow us to skip over between devices, and that's kinda it. Uh this is my fifty second design.
13:39	@
13:46	$
13:47	Power source over here. We're gonna have a switch obviously between the power source and the rest of it, and you're gonna need the switch. Um extra bulb could just be for flashiness, um subcomponent which would be like a way of diverting the power to different parts of the the device. Um the chip and of course the infra-red bulb, so it can communicate with the various devices that it needs to talk to.
14:15	So what exactly we are looking at, is this like the front of the remote?
14:18	This is just like a rough schematic. So this is the internal workings.
14:20	So this would be the front? So the red would be the front of the remote though, right? Okay.
14:22	Oh okay.
14:24	Yeah.
14:25	Yeah, that's gonna be what's communicating with the T_V_, but the other bulb, I think, is good to just to indicate, I'm doing something, it's sort of like a reassurance.
14:32	The l- # the light up kind of - Yeah.
14:32	Like that we know the battery's working.
14:33	Yeah, so you don't have to stare at that infra-red, 'cause you know when the battery starts dying in your remote currently, you have to actually stare at that bulb and go, okay, when I push this button, is it working? We can skip that whole thing. Yep.
14:41	Hmm.
14:43	Okay.
14:43	It'd probably* be lighting up the key too, right?
14:46	Yeah.
14:46	Yeah.
14:46	'Kay.
14:47	So you can put it in the dark. $
14:48	The buttons.
14:50	Yeah, and that's good. We should make it glow in the dark. $
14:51	Okay.
14:52	Yeah, definitely. 'Kay nex- R- Ready?
14:55	Yeah, that's it.
14:56	'Kay, any p- 'Kay?
14:56	#
14:57	Mm 'kay.
14:59	Anything you wanna add for personal preferences though, you f- you said already that we needed a large on-off button, you think. Anything else?
15:04	I think that that's a good idea, because you know that's one of the most important buttons.
15:08	Just -
15:09	Okay.
15:10	Well, should it be larger buttons in general, you know like uh the examples that I had, they were swi- quite small. So should we try and go for something that has l- larger buttons?
15:19	I think we should. Like I think that would be in a as in - like in - for the design, sorry, um. I think we should definitely go with buttons that don't look like a normal remote, 'cause most remotes have small square buttons, I think we should do something like maybe bigger and round like bubbles.
15:29	Mm.
15:31	Ovals.
15:32	Yeah, yeah.
15:33	Okay. Okay, let's talk about all of our -
15:38	We'll come to decision later about all the components that we need to include, let's um wrap up this one, and # I'm gonna go back to my PowerPoint, 'cause we need to discuss the new project requirements which you might've already seen flashed up on the screen a bit earlier. $ Wait*, come back.
15:57	Alright. Sorry, let's go through this. Alright. Here we go. New product requirements. First it's only going to be a T_V_ remote. We're trying not to over-complicate things. So no D_V_D_, no TiVo, no stereo. It's not gonna be multi-functional.
16:11	# Okay.
16:16	@
16:17	Hey. And we th- need to promote our company more, so we need to somehow include our colour and our company slogan on the remote.
16:27	We're trying to get our name out there in the world. Okay. And you know what teletext is?
16:31	@
16:35	Yeah.
16:36	@ in States we don't have it, but um it's like they just have this channel where just has news and weather, kind of sports, it's very um bland looking, it's just text on the screen, not even - Yeah, just black with just text.
16:37	I know.
16:37	What is it?
16:39	%
16:47	Yeah, it's like black, black and white kind of -
16:50	Like running along the bottom?
16:51	Yeah.
16:52	You can also get the kind of the T_V_ guide so -
16:52	It'll give you the sports.
16:55	Wait, is it like the Weather Channel where it's got like the ticker running on the bottom or something?
16:58	Kind of.
16:58	Except the entire screen.
17:00	It's the entire screen is just running information at random. Seemingly.
17:00	Yeah it's the whole screen.
17:04	You can pick sports, you can pick the news, you- entertainment, you know it's like -
17:04	So anyway -
17:08	So it's like a separate channel from like what you're watching?
17:08	Right. Right. But it's becoming out-dated now, because of the Internet. Nobody needs to go to the teletext channel to check the news, # and we have twenty four hour news channels now too, so - Those are our new product requirements. Alright. Mm-hmm.
17:10	Yeah.
17:21	Okay. So, do we have to include the company colour within that?
17:21	Okay.
17:25	Yes. It's part of the logo.
17:30	Okay.
17:31	Company colour being yellow. $
17:33	What we're going to do right now is come to some decisions, definitive that we can all agree on, about um the target group and the functions and just definite things that we need to do and then we'll close up the meeting. So. Alright.
17:53	@ Whatever.
17:57	Okay.
18:04	So our target group is - You mentioned um older people? Would it just be universal for everyone, you think? Because I think even if something has large buttons, as long as they are not childishly large, like even technically -
18:10	Mm-hmm.
18:17	It's gonna make it nicer.
18:19	Yeah.
18:22	non-technically challenged people are gonna use it. I mean they want something user-friendly, so -
18:26	Mm well, even if we kept the regular standard size of remote, if we reduced the buttons down to the ones that people are saying that they use the most often and a couple extra, 'cause they're saying they only use ten per cent of them, then we should be able to accommodate fairly decent sized buttons.
18:36	Yeah.
18:38	Yeah.
18:43	Okay, so we want um for our target group would we say, I mean, young and old, all age ranges, all um, not kids obviously, right?
18:54	Or kids?
18:54	No, kids need to know how to use a remote, I would think. They gotta change between Disney Channel, Cartoon Network.
18:57	Most of them will intuitively pick it up though.
18:58	@
19:01	Okay, so we're going to go anywhere from kids to adult in the age range - Um what about
19:03	Yeah, I think we need it all.
19:11	technic- technical um specifications, like how how technically literate are these people who are going to be using our remote?
19:19	@
19:19	Um I would say we should say dumber than the average person.
19:23	Okay.
19:23	We should go for the lowest denominator.
19:25	Yeah.
19:25	Right, okay.
19:27	High school educated.
19:27	So so they need no technical experience to operate -
19:30	@ how 'bout little to no, because there is no way that you are gonna be able to make it no.
19:49	Okay. And we also need to determine the specific functions of this, just to get it all out on paper. So we said it needs to send messages to the T_V_, needs to change the channel, turn on and off, just basic simple stuff like this. So if you have something just say it and we'll add it to my meeting minutes.
20:13	Well it's channel, on-off button, volume, mute.
20:15	Mm-hmm, volume.
20:17	And channel. Yeah. Those are the most important ones.
20:20	Right. And we wanna keep um - I'll make a note here that we wanna keep the number of buttons down. Correct, because people only use ten percent. 'Kay.
20:27	Yeah.
20:33	Hey, what else?
20:33	Um.
20:42	Um.
20:44	#
20:44	Do we want this thing to be able to be found easily?
20:49	I think so. What do you -
20:52	Sure, yeah.
20:53	@
20:54	A finding kind of device or - Yeah, ho- homing device. $
20:54	And
20:55	I need - we we need a like homing device.
20:56	like if this is gonna get lost underneath the coach, how are we going to accommodate the quick ability to find it?
20:57	Oh right yeah okay.
21:01	Mm 'kay.
21:02	Tracking.
21:06	Okay.
21:06	Because people really are looking for a remote that's more high-tech.
21:12	What if we gave it a charger? And on the charger, just like a phone, like you get a portable phone and it's got a charger, and if you d- leave your phone somewhere, you push the button to find it, and it finds th- the phone beeps for you.
21:12	Right.
21:18	But you got a base.
21:23	Do you think people'll really go for that though?
21:26	Because -
21:26	It's useful for the remote phone.
21:29	Hmm. Would that add to our costs at all, I wonder?
21:30	Yeah.
21:33	I would think so, because you'd have to develop a base.
21:35	Right.
21:35	Well, if you have the base, you could start putting in a charger and then you have a different kind of battery.
21:40	Yeah.
21:42	Hmm.
21:43	Rechargeable batteries are cheaper usually.
21:46	Yeah.
21:47	Okay. I I think we can make a decision about that later. Uh we'll still put that as a point that we need to discuss. So that would include battery source -
21:57	Power source rather. Is it going to have a charger, or is it going to be run strictly off batteries? And we also need to deal with the issue you mentioned of speech recognition, if we want that.
22:09	Right.
22:11	Do w-
22:11	Well, then we could - If we have the speech recognition then we can start aiming at a like another kind of more handicapped disabled uh demo- demographic.
22:19	Mm.
22:21	Well, th- there's the people who desire speech recognition, there's the different demog- demographics have different desires, I don't know if you guys ge-
22:30	You could um - we could hook it up. Oh.
22:32	It wouldn't copy onto the the thing 'cause it's black, but all the different age groups have different desires for speech recognition. So # basically older people don't really care.
22:45	It's really the people twenty five to thirty five. I feel those are the people that really watch a lot of T_V_ though. They're the ones that get addicted to soap operas and
22:45	@
22:50	Mm-hmm.
22:53	$
22:54	just sitcoms and stuff.
22:55	Well -
22:55	And if and if we introduced it when they're this age, they're going to probably always buy a remote that has -
22:59	Right.
23:00	Well, then then do you put the voice recognition - do you put the r- like receiver on the actual television, in the base, or in the actual remote, 'cause then you've already got remote* in your hand, why you just gonna speak to the remote, whereas if you just speak in general and you don't have to have the remote in your hand and like talk at it.
23:01	So -
23:11	Right.
23:17	Yeah. @ and the speech recognition could be part of the lost and found device, too. If we said, find remote, locate remote, or something.
23:23	Right.
23:26	A certain phrase
23:28	then it could beep. I dunno. Just throwing it out there.
23:32	Yeah.
23:37	Well - $
23:38	$
23:42	Still @ fifteen minutes.
23:48	Um.
23:48	Okay, anything else we wanna discuss?
23:50	Well, do we wanna include the numbers like zero through nine? Can we conceive of leaving them out?
23:58	Um.
23:59	Wait, on the remote itself?
24:00	Yeah, like you have one, two, three, four, five, six, seven, eight, nine, zero.
24:00	@
24:03	How how, yeah, how would you leave those out?
24:03	Well, we definitely need those.
24:05	Yeah.
24:06	Well, I don't know, I mean, if you can @ like well - I don't know, if there's just a way of leaving them out?
24:09	Unless you could say the channel.
24:11	I think people would find that too foreign.
24:13	Yeah. You definitely need -
24:14	Yeah, that's true. And also remember that in this day in age we need, you know, like a hundred button, too. I used to have a remote that did not even go up past like fifty. $ So I couldn't - whenever I got cable, I had to get a new T_V_.
24:29	It's when we get satellite.
24:31	Mm. @ get your own remote, or digital cable. 'Kay. Um.
24:34	Yeah.
24:40	I guess, we're gonna discuss the project financing later, making sure that we can fit all of the stuff that we want to on our budget. Um.
24:53	Yeah, 'cause I don't have any material pricing information available to me at the moment, so -
24:57	'Kay. And don't forget we need to include the colour
25:02	of our company and the logo.
25:04	Wait.
25:04	The colour being yellow?
25:06	I'm guessing. And the R_R_.
25:08	And how do we -
25:08	I feel like a ye- I feel like a yellow one would be too garish.
25:09	R_ the double R_.
25:11	We could just have the logo in yellow, or maybe a yellow light for the keys.
25:12	Can't make it entirely -
25:14	Or is the l-
25:15	Or put like stripes, oh yeah, yellow lights.
25:18	Yeah, # yellow could be and it could - doesn't have to be huge.
25:22	Yeah.
25:22	Well if you have like a # - Hang on. If you have this sort of strip kind of down at the bottom @ the base of it, just like yellow with the R_R_.
25:32	Right.
25:37	So we've simplified, we don't need all those um play, fast-forward, rewind,
25:41	Right, yeah.
25:42	Yeah.
25:42	or no menu buttons. So we've pretty much pared it down to on-off, volume, mute, channel up and down, um the numbers -
25:54	Yeah. $
25:56	$
25:56	Yeah.
26:02	# Um can we go back to - I'm gonna look really quickly back at those
26:07	Two examples. Yeah.
26:07	examples and see if there is anything. Which one is yours, technical functions or functional requirement? Okay.
26:11	Oh, it's a - Yeah.
26:14	Yeah, audi- audio settings and screen settings, we need those like audio settings mono, stereo, pitch, screen settings like brightness, colour, or do we just want that accessed* accessed from the television itself?
26:24	The T_V_. I think that that's fine just for the T_V_. I mean how often does the average user need to do that kind of stuff?
26:31	Well, the other option is sort of like down at the bottom, like farther away, you just have this sort of box inset where it's like the buttons that you don't use as much, but occasionally you will use.
26:41	Hmm.
26:43	Yeah, 'cause we need to - we definitely need to have buttons for like sub-titles and things like that. It's 'cause the foreign film market is expanding and stuff, and like on television like I know f- k- living in Los Angeles it's tons of Spanish network television if it has English sub-titles it's definitely helpful.
26:43	and so it's like -
27:00	Couldn't we do that all through one button, something, a menu button, that pops up with a menu on the T_V_ that says, you know, audio, video, whatever, language, you know?
27:03	I don't - well, I don't know.
27:10	Right.
27:10	So we need up, down, and side-to-side buttons.
27:13	Well, that could be - No you could just double up with like the channel or the volume buttons.
27:13	For the menus.
27:17	Mm-hmm.
27:18	That's true.
27:19	Yeah, okay.
27:19	Channel is just up and down.
27:21	Okay, yeah.
27:22	And then add a -
27:24	Something that looks mayb- you know.
27:25	Such as, yeah, the one the one over there on the left the engineering centred one.
27:29	Y- right, right right right. That one?
27:30	Yeah.
27:31	So we just have it like - add a menu button then for the various things needed, including v- voice recognition if we have any like settings for voice recognition now
27:36	Right. In the middle perhaps.
27:43	included in the menu.
27:44	Yep.
27:47	Ooh, I just got an idea for a design.
27:49	@ good.
28:02	Anybody have anything else they'd like to bring up in this meeting?
28:05	I had something, but I forgot.
28:07	$ Okay. @ get out of here. Let's go back to the meeting closure then and see what we need to do next. Mm.
28:24	Alright. After this meeting we're gonna be sent a questionnaire and summary again which we need to reply to that e-mail. And then we're gonna have lunch break. And after lunch thirty minutes of individual work time. Um I'm gonna put the minutes - I put the minutes for the first meeting already in the project documents folder, if you'd like to review them. And I'm gonna type up the minutes for this one as well. Um here's what we're each going to do. The I_D_ is going to work on the components concept, um U_I_D_ the user interface concept, and you're going to do some trend watching.
28:58	'Kay. Specific instructions will be sent to you by your personal coach. And if anybody has anything they would like to add? No? Okay, well, this meeting is officially over.
29:11	Thank you all.

---