Let's make a Human Factors Cast GPT

[00:00:00] Nick Roome: And for those of you just joining us Barry has bowed out for this evening.

He was not feeling well. And so we're going to shift gears and do something different. . Maybe I don't have to do this alone. Maybe if I bring in Frank Frank can help me out here.

Live from Orlando. Hello.

[00:00:18] Frank Lacson: Can you hear me? Okay.

[00:00:20] Nick Roome: Can Frank. So this

[00:00:22] Frank Lacson: is

[00:00:22] Nick Roome: actually pretty great. We were talking just a little bit about technology earlier and I'm doing well, Frank.

Thank you for asking. And

I'm thinking that we shift gears a little bit, maybe not do a full show, but I'm wondering, I'm inspired based off this idea from last week's show. There was this LinkedIn post by by Jeremy Van Hill and they had made a human factors, GPT, and they had specifically loaded it up with a GPT or sorry, FDA guidance to do something right at

[00:00:53] Frank Lacson: every

[00:00:54] Nick Roome: response says.

And I'm wondering. What, if we could build one, maybe that's based off of the DOD 1472 guidance.

[00:01:05] Frank Lacson: Oh, neato. Yeah.

[00:01:06] Nick Roome: Load it up there. And perhaps augment it with some other stuff, but I guess for, I was just describing what things would be important to me. If I were to integrate AI into my own personal workflow for the day to day, right?

And I'll ask you too, like when you consult AI, what are you looking for?

[00:01:27] Frank Lacson: Oh, that's a good question. And so I think one of the reasons I was interested about this is other than the stuff that you've talked about, I've never really interacted with AI. This is all fresh to me.

But if I were to do one. I think some kind of assistance or asking about ways to prioritize or sort some of the activities that I'm supposed to do out the rest of life, the non work thing. I think with the work stuff, there's a lot of systems such as JIRA and Kanban and Scrum and other kinds of ways to organize work.

But the challenge is being able to organize. Non work items in a casual manner that doesn't cause stress.

[00:02:14] Nick Roome: So I've opened up a chat GPT and I'm looking at, and for those of you who don't know what a GPT is, it's basically a. Custom like chat bot that you can essentially interact with that is preloaded with information. And how to best describe this? We can create one, right?

Hi, I'll help you build a new GPT. You can say something like make a creative who helps generate visuals for new products, make a software engineer who helps format my code. You can configure it obviously. And and then provide a description and. And provide the instructions, all that stuff. It seems like this create this create section here is more of a chat based approach, which is actually interesting.

So I'm wondering What if we asked it, can you help me create a human factors based GPT that will interact with human factors, user experience, user centered design, customer experience, and human computer interaction professionals? I've just put that in there. It's updating the GPT now. And so this is the first time that we've introduced any information.

So it's looking all right, let's move on to naming it. I want it to be called human factors cast GPT. I'm going to send that in

great. The GPT would be called human factors, cast GPT. Great. It's going to create a profile picture.

Human Factors UX, HCD, CX, and HCI to guide professionals and enthusiasts. Instructions. This GPT will engage professionals and enthusiasts in Human Factors. It, it should provide well researched, thoughtful advice, frameworks, best practices across these fields. It will focus on improving design. User satisfaction and usability while balancing technical feasibility and user needs.

GPT should encourage empathy, iterative design, accessibility, and innovation. Its responses can also offer insights into the latest trends, methodologies, and tools in each domain, suggesting actionable recommendations. The goal is to be an insightful companion for professionals who want to refine their human centered practices and decision making processes.

I think that's pretty good. I think that's pretty good in terms of conversation starters. How can I improve the usability of this design? I think that's okay. Yeah, that's good. What is the best way to incorporate user feedback into design?

I want to change this up a little bit. What's the best way to incorporate user feedback into. My process,

because I think design is one thing but a larger process is another. Can you explain the latest trends in, it's really pulling a lot of the human in

Can we ensure accessibility? How can we ensure? Okay. Yeah, sure. That's fine. Knowledge, upload files. Here we go. Capabilities, web browsing.

Whoa. Dolly image generation. I'm going to turn that off. Maybe not. Let's do code interpreter to data analysis. Let's see here.

All right. So I've uploaded a mil standard

[00:05:15] Frank Lacson: 14,

[00:05:17] Nick Roome: 1472 H.

[00:05:18] Frank Lacson: Oh my God.

[00:05:20] Nick Roome: If you upload files under knowledge, conversations with the GPT may include file contents. So this is all publicly available. I'm not uploading anything that's not I, what are some other good resources for human factors?

Folks, right? There's FDA guidance. Sure. That's there's a bunch that comes down. I'm wondering, I'm like seminal. Human factors

[00:05:40] Frank Lacson: Are you talking about standards or just files? Or

[00:05:43] Nick Roome: standards? Files? Anything like resources. Let's put 'em all in there.

Can you put websites in there? It has web browsing in it. No, it's only files here.

[00:05:54] Frank Lacson: I wonder if it's like a handbook or some, like a publicly available handbook. I'm.

[00:05:59] Nick Roome: Yeah, this could be cool.

[00:06:01] Frank Lacson: Let's see,

[00:06:03] Nick Roome: Steve Merriman. We're gonna

[00:06:06] Frank Lacson: upload, we're gonna upload Steve Merriman.

[00:06:09] Nick Roome: Hi Neil, how you doing? Hi

[00:06:10] Frank Lacson: Neil. Not a bad idea, not a bad idea. Let's

see here. Yeah, we're trying to find some resources to upload to this thing. We uploaded 1472. We're trying to find some resources to upload to

[00:06:24] Nick Roome: Yeah, we got 1472. We're built. So if you're just joining us, welcome. Barry had to call out tonight. He wasn't feeling well. So we got a pitch hitter in here.

Frank is joining us tonight. We're doing something a little bit different. Oh, that's a good one, Neil. And what we're doing is we're building A GPT. I was inspired by somebody's LinkedIn posts that we brought up last week's pre show their GPT was built for hemofactors professionals, but it was uploaded with with FDA guidance, which is fine.

But I think for a lot of us, that might not be enough. And so what I'm trying to do is backload this thing with a few additional resources and make it a little bit broader in scope than just human factors, because you can imagine people have different titles, different roles that they're performing.

And so this is more along the lines of of a broadly accessible UX, human centered design, customer experience GPT to work on these things. And I think let's do ASTM 166. Let's see here. Looking to

[00:07:25] Frank Lacson: see there's a, if there's a,

something on the UX side of the house.

[00:07:30] Nick Roome: Yeah. Yeah. Let's see here. Do I have a copy of this?

[00:07:36] Frank Lacson: Yeah.

[00:07:37] Nick Roome: This is

[00:07:37] Frank Lacson: interesting. Yeah. Nielsen Norman has some UX basics, a study guide, which has a link, a bunch of things, articles and stuff.

[00:07:47] Nick Roome: So this is interesting. Yeah, I think NASA is also another good resource too. I wonder, so I'm going to stick away from

uploading things that you have to pay for. I think the ASTM

F1166 is good. The problem with it is that you have to pay ASTM for a copy. And, not that's a problem necessarily, but the problem for me is uploading that to this GPT to act as a as a foundation for this thing. If I didn't make this publicly available, And this was like, my own personal thing.

I would do that. I'm not saying you can't do that on your own end, but for me to upload that, I think there would probably be some legal challenges. Let me put it that way. So let's look at NASA. What does NASA have in terms of documentation? Wondering if so there's the human factors design standard. Okay. Another mil standard there. Let's pull that one in. MIL standards are great because those are publicly available.

87213A. Department of Defense handbook. What is this one?

Airborne displays. Okay. Yeah, that's good.

Download that one and put that one up there as well.

Download, let's see here. You gonna download for me? Revision B looks like the latest. Alright, we'll configure this one, we'll come back down, we'll upload files. . Alright.

87213.

[00:09:22] Frank Lacson: I'm gonna look up, I've been looking up some. Customer experience and

[00:09:27] Nick Roome: yeah,

[00:09:28] Frank Lacson: new experience.

[00:09:29] Nick Roome: Let's see here. We can we have more,

[00:09:32] Frank Lacson: yeah, we could always add it in.

[00:09:34] Nick Roome: Yeah. We can always add it in. See where

[00:09:38] Frank Lacson: I've got one.

It's called the customer experience playbook.

[00:09:44] Nick Roome: Ooh, interesting.

[00:09:48] Frank Lacson: The Neil has the HFDS.

[00:09:51] Nick Roome: Yeah. Human factors design standard. I'm looking at, so it's hosted on the FAA, which is good. Looking for, I got it directly from the FAA. So this will hopefully be the the latest download complete. Oh, there are a lot

[00:10:07] Frank Lacson: in this space.

Yeah. Neil says If there's a .

[00:10:11] Nick Roome: Oh, yeah. Okay. Hang on, let me Neil, I'm gonna LinkedIn a folder for you,

so we'll focus on these publicly available resources here.

Yeah. Design standard. Great. Okay. We'll do the 2016 version. We'll do the 2016 version. That's better, I think.

[00:10:30] Frank Lacson: Yeah.

[00:10:31] Nick Roome: HFDS. Alright, so there's that. We'll get the design standard in there. If it goes, there it is. NASA HFDS. Okay. And then Frank, you had said something about a handbook or something.

[00:10:49] Frank Lacson: Oh yeah. There was a Customer Experience Playbook.

[00:10:51] Nick Roome: Oh, Customer Experience Playbook, okay.

So I'm actually going to add something in here. The GPT should encourage empathy, iterative design, accessibility. Can also offer insights, methodologies, tools in each domain. Actionable recommendations. The GPT will provide References whenever possible. To ensure the recommendations are trusted by the user. There it is. Okay. Customer customer experience. What was it, Frank? One more time.

[00:11:33] Frank Lacson: Customer experience playbook.

[00:11:35] Nick Roome: Playbook. Let's take a look at

[00:11:38] Frank Lacson: that.

[00:11:39] Nick Roome: GSA. Hey, love that. All right.

I wonder if there's like accessibility standards that we could throw in there

[00:11:49] Frank Lacson: that might be good. .

[00:11:50] Nick Roome: So what we have in there so far is MIL STD 1472H. We have. The military handbook, eight 70 87 21 three B we have the NASA human factors design standards, and we have the customer experience playbook that is available from GSA.

So I'm wondering if there's one thing that I had brought up is accessibility standards.

Yeah, you can imagine that if you had a bunch of these resources, if you had access to a bunch of these resources, you could build your own GPT in a very similar way to what we're doing right now. And use it for your own personal use.

Do not share it educational

[00:12:25] Frank Lacson: purposes

[00:12:26] Nick Roome: only, because then you get into some of those financial advice, not financial advice. Exactly. We are building this for for some of the For educational purposes only. Yes, exactly. We don't want to get in trouble. HFES, HRL, standard human readiness levels. That's right. Yeah. Those are publicly available. So let's see here.

[00:12:47] Frank Lacson: Okay. We're, I think we're one step closer. One step closer. Okay.

This is exciting. So what, how, so once I am excited, I, yeah, you can just ask it all sorts of questions and listen.

[00:13:03] Nick Roome: I'm excited, I can't wait to see what this thing spits out.

, ADA standards?

For accessible design, alright. There's also guidance on top of that, but I'm just gonna upload the baseline here. I think getting the baseline knowledge is good. All right. And of course, there's one more thing that we need to do here that before we really are off to the races. And

that is of course,

changing the GPT logo to one that is a little bit more familiar.

[00:13:35] Frank Lacson: Awesome.

[00:13:37] Nick Roome: Here's a quick, here's a quick checklist of what we've done so far. Context and focus. We set the focus of human factors, cast GPT, find advice in human factors, UX, HTTPS customer experience, HCI, ergonomics, profile picture. We got some prompt starters. We uploaded some files. Hey, look at that. That can be referenced before you launched a few things to consider. Test refinement preview. Hey, what do we want to ask this thing?

[00:13:59] Frank Lacson: What's the ideal viewing distance? For uh, a tablet. Hit

[00:14:09] Nick Roome: for a tablet. All right, here we go. What's the ideal viewing distance for a tablet? Let's see if it can help Frank out here. Searching my knowledge

falls within a range that insert, ensures comfortable readability, reduces eye strain and allows for effective interaction with the device. General guidance for handheld devices suggested that the viewing distance for small displays. Like those on tablets should be between 15 to 30 inches, approximately 38 to 76 centimeters.

This range can vary slightly.

[00:14:42] Frank Lacson: That's pretty neat.

[00:14:43] Nick Roome: Hang on. I'm gonna try, I'm gonna try something. I'm gonna try something. Hang on, Frank. I'm gonna, I'm gonna make you full screen for just a moment, okay? And then we're gonna try something out. It'll be pretty fun here, I think. We're gonna make Frank the big screen Okay, hang on I'm gonna I'm gonna try its visual recognition here.

All right, so I'm gonna say okay. So I've done that. Oh, how far am I away from the thing? Yeah, I'm gonna see if it knows. I'm gonna see if it knows. Alright. So I've taken a screenshot. I'm gonna say, alright. Based on your best estimation.

[00:15:17] Frank Lacson: Oh my god.

[00:15:18] Nick Roome: How far is the viewer in this image away from the tablet they are on, and is it within the suggested range?

Alright, so I've put a screenshot of you, Frank. There's the screenshot. Based on your best estimation, how far is the viewer in this image away from the tablet they are on? And is it within the suggested range?

20 to 25 inches from their face. Whoa! Derived from the size of the head and upper body in relation to the typical field of view seen with front facing tablet cameras, this distance falls within the recommended 15 to 30 inches viewing distance for tablets, which is ideal for comfort and readability.

Thus, distance appears to be within the optimal range for viewing, interacting with a tablet. That's pretty cool. What do we think, chat? Is this good? Is this cool? What? Would y'all use thIs? really, you don't know what you don't know. And what things might I not know to consider for tablet placement?

There's

[00:16:28] Frank Lacson: there's also there's also goodies in the goody box. Oh, there's

[00:16:34] Nick Roome: goodies in the goody box. Oh, there's Hang on, now I have to ask, are these all publicly available, Neil? Or are these things that I'm going to get in trouble if I upload here?

[00:16:42] Frank Lacson: It might be it depends. It

[00:16:45] Nick Roome: does depend, yeah. We

[00:16:46] Frank Lacson: can take one that looks just the MIL STD 3009. We know that one's definitely publicly available. I think you can take the MIL STD and the MIL PRF1. That's a sure thing.

[00:16:59] Nick Roome: All right. What else we got? FAA stuff.

[00:17:03] Frank Lacson: Yeah. The FAA should be definitely

[00:17:07] Nick Roome: technical operation. Yeah. Graphical UI.

[00:17:10] Frank Lacson: Yeah. That's a good one.

[00:17:12] Nick Roome: Yeah.

[00:17:14] Frank Lacson: Yeah. And I think that'll be good. Definitely. Definitely.

Oh, actually, Barry might like this one. There's one from the Ministry of Defense.

[00:17:21] Nick Roome: Oh yeah, let's throw that one in there too.

[00:17:23] Frank Lacson: Get the international

[00:17:24] Nick Roome: perspective.

[00:17:25] Frank Lacson: Death Stand, yeah. Death Stand. There we go.

I think that's, there might be some, but I think the ones that, that just mentioned, those are the sure things.

[00:17:36] Nick Roome: Okay, so let's come back to configure.

[00:17:39] Frank Lacson: Boosted. This is V2. V V beta 0. 2.

[00:17:45] Nick Roome: What did I leave off on? Okay, so we need 3009. We need this one. 301A. We need that one. I wonder what's the limit here?

Like how much can we upload as the base here?

There we go. So you didn't forget

[00:18:06] Frank Lacson: about Barry. I'll make the deal.

[00:18:09] Nick Roome: Yeah. Did I get the def stand? Hold on. I don't know if I got the def stand in there.

[00:18:15] Frank Lacson: Oh, you said the ABC should be good too. A, B, A, B, C, D.

[00:18:21] Nick Roome: Multiple countries. Okay, cool. I'll put that one in there.

[00:18:24] Frank Lacson: Oh, yeah, that might be fun.

[00:18:26] Nick Roome: Something went wrong. Oh, no. It's air saving craft. Hold on. I wonder if we're hitting the upper limit here of the knowledge.

Are

[00:18:35] Frank Lacson: we creating a monster? Sky, it's called Skynet. Skynet.

[00:18:41] Nick Roome: Death stand's in there now. Okay. Okay. Alright. Here we go. A, B, C, D.

Okay. Okay, since you know what I'm going to give, I'm going to give it a little love here and also say the GPT will end every transaction with

[00:19:00] Frank Lacson: But remember,

[00:19:03] Nick Roome: It depends. The other one started with it depends. I'm going to append this one with it depends. All right. Let's see what we got here. All right. Let's ask it another question. Let's do another preview here. Human integration. I'm looking at some of the other ones that you put in there, Neal. That are from like NASA's probably good.

NASA's probably

[00:19:26] Frank Lacson: fine.

[00:19:28] Nick Roome: Download, download.

Yeah, we'll put those ones in there too. Actually. Let me throw those in there before before we get going here.

We got there we go. One

and we got two. Oh it's loving all these files. It's starting to chug a little bit.

There's two. Wow. Look at this baseline of knowledge here of human factors, things.

Look at what we've built. All right. So now there's a ton of resources in here. I'm waiting for this one to upload and then we can try it out with something else. And

I wonder. I, I have an idea. I have an idea.

Hey, look at that. That is pretty cool. I would love to test this out with a real scenario here. So let's look at maybe at fighter pilot fighter jet cockpit.

Okay. And I'm going to I'm going to make this real simple. I don't know what this is. I do not know what this

I got a better one for y'all. Watch this. All right. I'm going to use, I'm going to use the interior of an X wing cockpit. Please hold. I'm gonna throw this in there.

Let me re

Oops. All right. Let's come back to preview. All right. I'm going to be real casual with it. I'm going to be real casual with it this time and just see what it comes back with. Yo, is this good HF?

Yo, is this good HF?

[00:20:59] Frank Lacson: Yo.

[00:21:03] Nick Roome: So what you're looking at in this image is the interior of an X wing cockpit. Cockpit in the image you provided, while visually impressive, may present human factors challenges. Context of use, such as the task complexity, user. Hey, look at this, including MIL STD, NASA, and FAA guidelines. Information overload.

In summary, cockpit may look technologically advanced,

a fast moving boat. Oh, hold on. Human exposure to any risks about human exposure? Oh, it's me. Yeah. Let's here. Let's what's a good boat to use? Let's see. Yeah we'll just do a consumer model here. And we'll ask it, hold on, let's see here.

Let me back out and come back in to clear it out. So that way we get a clean slate here and we'll say all right, there's the boat and say what are some human factors considerations here?

Just keep it very big. I'm not even saying it's a boat. What are some human factors considerations here?

For the speed boat in the image, several human factors considerations are important, ensuring safety comfort operation. Okay. So seating ergonomics and seating visibility line of sight. Control layout environmental exposure, vibration, emotion, safety features, lighting,

but remember it depends. Hey, it's there. Let's see here.

I'm wondering, okay. I want to test its paces. Can we give it some requirements? Design me an interface. To show a dashboard of here's something I'm looking at, like user feedback user feedback metrics,

that's okay to say.

So it's looking through its knowledge. Let's see what it comes back with. Let's see if I'm impressed or not. Snapshot of the most critical feedback. He's ability guy. Okay, great.

Can

[00:22:59] Frank Lacson: there's two pics to,

[00:23:02] Nick Roome: An image for me

could look like, all right, Neil wants me to upload two images. Oh, yeah,

[00:23:09] Frank Lacson: he's got two pictures. Oh, he said the goody basket.

[00:23:14] Nick Roome: Oh, in the goody basket. All right, hold on. Let me go over to the goody basket. Cool.

Net promoter score. Wow. I'm actually impressed that it put NPS in there. I don't know what that says. Something satisfaction. Text is really bad with these things. KPI 6 percent user feedback. Okay. So yeah, this is terrible.

This is bad.

[00:23:36] Frank Lacson: Oh, you're going to, you're going to turn, you're going to upset. I'm sorry. I'm sorry. Hell,

[00:23:43] Nick Roome: The text is bad.

All right. I think actually, hang on.

Okay. Hang on. Neil uploaded two pictures. Let me let me download these pictures and I shall upload them.

And what do you want the prompt to be? Neil, just what is the, what are human what are the, what are some human factors considerations for these things? Did you have a specific question?

[00:24:04] Frank Lacson: Oh, fast moving, but it's a fast moving boat. So I think the same question you had. Looks.

[00:24:10] Nick Roome: Okay. Yeah.

[00:24:13] Frank Lacson: Let's see how it did for, compared to.

[00:24:16] Nick Roome: Let's upload these here. Can I just drop them? Yeah, there we go. Alright. I'll say What human factors are there? Up here.

Okay. Done.

[00:24:32] Frank Lacson: Oh, shock exposure. So you There should be some shock exposure here.

[00:24:40] Nick Roome: High speed tactical boats. Several key aspects come into play. Alright I'll ask, oh, Vibration Exposure.

[00:24:49] Frank Lacson: Oh, there, there's Vibration Exposure.

[00:24:52] Nick Roome: Hey, okay.

[00:24:54] Frank Lacson: Access, Emergency Security Slip.

Only I think.

[00:25:00] Nick Roome: Alright Tell me what I should what to consider. Oops. I'll ask about vibration exposure and see if it comes back with things like shock exposure. I'll keep that separate.

[00:25:14] Frank Lacson: Yes.

[00:25:15] Nick Roome: Critical concern and high speed craft. Okay. Whole body vibration, localized vibration, wave impact, sudden jolts and peaks of vibration. All right. We're getting closer there. Neil says not bad. All right.

[00:25:32] Frank Lacson: Oh, shock mitigating seats.

[00:25:35] Nick Roome: Yeah,

[00:25:35] Frank Lacson: wow, okay. Vertical accelerations, yeah. Vibra Transmission? Yeah, vibration.

[00:25:42] Nick Roome: Frequency range, measurement and standards. I didn't actually upload this. I didn't upload this at all. So It's interesting. No. It's interesting that it pulls that out because it has capability to web crawl. And so it might be leading me off to another thing to say, hey, check out the standard.

[00:26:00] Frank Lacson: Yeah, or something that's referenced in it.

[00:26:03] Nick Roome: Exactly. Peak forces. All right,

dude. Okay. We just asked a simple follow up question about tell me what to consider about vibration exposure. And it pulled out all this stuff. So I think in terms of like our initial goal of setting out to make something that acts as a companion to bounce ideas off of.

From a human factors perspective it works where

[00:26:28] Frank Lacson: to start. It's a place for, it's a, it's a.

[00:26:32] Nick Roome: It's a place for professionals to start is seen as a supporting standard. It's referenced in 1472 for that. Yeah. I, yeah. For those of you following along Neil's mentioning here. ISO 2631 is seen as a supporting standard referenced in 1472.

So we have a bunch of like really cool core seminal human factor stuff in here. And we can add more to this database over time. So now I think what we could do is we could publish this. I could create it and share. I'm wondering if there's anything else that we want to to modify about this, not that we can't do it once, once it's out there, but like what other conversation starters maybe over here, I'll say help me brainstorm

additional conversation. So oops, spelled that wrong. I T. Conversation starters, that might not be, oops,

to some folks some people. Ah, okay. Come on. Come on.

All right.

You want to get, yeah. Okay.

All right. So I think it, let me here.

Okay. We're going to give anyone with the link here. I'm gonna save this for now. Hold on. I'll share the link with y'all in just a minute.

[00:27:51] Frank Lacson: Oh, we got some speaker ideas. Eat. Some what? The boats. It looks like the boats is an interesting follow up topic. Boats.

[00:28:02] Nick Roome: Here. Okay. The GPT is published. I have the link, but before I do that, I might want to see if it can do this thing here. Let me try,

let me try refreshing this really quick. I would like to update that with some additional conversation starters. We'll see if we can get there. But to those of you watching here's the Human Factors cast GPT. I've just posted that in chat, you can get to it here, and in fact, what I will do is that's terrible UI, so let's do a QR code, because I love those.

Let's see here, Human Factor Scan is GPT, how do I add one of these? HFC.

How do I, oh, do I need to do I need to get rid of one of these? I guess I can do this one. Oops. There you go. You can share good human factors news. I got to overwrite this one. I've kept it in there as long as I can. Let's see here. HFC GPT. All right. And there's that. And then, boom. All right. So if you want the Human Factors Cast GPT, you can scan that right there, get to this if that's your preferred method.

I'm going to take away the bottom here, and we are going to get back to it. To I did post that in chat too. So hopefully you can see that. So let's get back to it. I'm going to, I'm going to try my best to get this to where it's going to give us some conversation starters that we may not have thought about.

Can you give me some additional. Conversation starters

that even advanced professionals may not think to ask.

All right. Let's see if it comes back with anything.

Let's see. Let's see what it comes back with. Here's some advanced conversation starters that even experienced professionals in the field of human factors, UXHCI might not think to ask. What are the implications of incorporating biometric data into anthropometric design standards?

All right. Hey, Neal's out there. Usability testing this GPT right now.

[00:30:00] Frank Lacson: Yeah, it's a neat.

[00:30:03] Nick Roome: Let's

[00:30:03] Frank Lacson: see

[00:30:05] Nick Roome: You know what I'm gonna throw you know what I am going to put this one in the conversation starters because I really want There to be like a wide variety of use cases for this and I want to test this as much as we can How can cognitive workload be assessed and balanced in systems that integrate both automated and manual tasks?

Ah, These are cool. Let's see. What strategies exist for designing human machine interfaces that accommodate neurodiverse users? And how can these be standardized across the industries? Wow.

I'm just going to leave it at that. The standardization can, yeah, that's a separate thing, but that's cool. How can cognitive workload be assessed and balanced in systems integrated both. Yeah. Okay. I'm just making sure that there's not like a good into,

yeah. All right. Hey, look at that. We're really cooking now. How can system design be optimized to manage the varying effects of long term environmental stressors?

In what ways can mixed gender accommodation and equipment design be reduced performance gaps? Whoa, this is awesome.

These are some good questions. These are cool.

Okay. Obviously we can add more to it. It's got all these things. Let's see what's under additional settings.

Use conversation in your GPT to improve our models. Fine. Okay.

[00:31:31] Barry Kirby: Ooh.

[00:31:33] Nick Roome: I wonder. What can we do with actions? Let your GPT retrieve information or take actions outside of chat GPT. OpenAI schema. Examples. Weather, JSON, PetStore, BlinkTemplate. Ooh. See now here's where some real power is that is beyond my knowledge.

And if anyone would like to help with that would be cool. Otherwise, I think what we have here is a great first start at this thing. And I'm reading, I'm

reading the private jets.

[00:32:07] Frank Lacson: Yeah. There might be some other responses prompts that some of the user, the community folks out there already started taking a look at it.

[00:32:16] Nick Roome: Yeah. I'm wondering if I can see What people are putting into it. Probably not. There's probably like a bunch of privacy things here.

Let me update this at least with those with those new prompts.

[00:32:28] Frank Lacson: Yeah, I think we could get some community prompts in a future update, get some of the ones from some of those other disciplines.

[00:32:34] Nick Roome: Yeah, absolutely. I think

[00:32:36] Frank Lacson: We got a

[00:32:38] Nick Roome: pretty good coverage from at least the from the the FAA.

Mil standard. What else did we get in there? Hang on, can you Got the boats one, and

[00:32:52] Frank Lacson: vessels.

[00:32:54] Nick Roome: Let me just ask, can you list your knowledge sources?

There you go. Look at that. Here's a list of the documents I currently have access to for providing information.

Oh, hold on. Ooh. Oops, sec. Hang on. Let's see. I'm just checking something. My part, by the way.

Hold on, where are my show notes?

Okay, a few thank yous, really quick, tonight. So first off thank you Barry for being sick so that we could do this exercise, cause that was fun. Thank you Frank for jumping on. Appreciate you pitch hitting. And then thank you, Neil, for being in the chat and helping supply us with some of the foundational documents that we used and sources in this GPT.

And then lastly, I would like to thank the original LinkedIn poster, which again is is I'm pulling it up now. So that way I make sure that they can be referenced. Jeremy who, who created. Did a human factors, GPT, and they used FDA guidance in theirs.

Hey, that's pretty good. All right. All right. We're about a time here. So if there's any last minute contribution, I can't believe we spent two hours on this. This is great. We built this in two hours.

[00:34:05] Frank Lacson: We got a lot of great sources from the community.

Thank you. Thank you, Neil. And yeah, I look forward to seeing some of the updates and community feedback on it. I'm sure we'll this won't be the last time we'll see this one.

[00:34:18] Nick Roome: Yeah, there we go. Hey, I've authored my first GPT in the store. Look at that. You can access it in the store.

Just search for Human Factors Cast GPT. We'll put it on the link to all of our stuff as we put it out there into the world. But once again, you can get to it right here by this link. Test it out. See how you like it. We've uploaded a bunch of source documents to it. And you can see those sources by asking it.

Hey, I hope that this genuinely provides value to somebody somewhere. If you do use this and have feedback or have other sources that are freely available that we can upload as in the backend to help augment this let me know.

[00:34:55] Nick Roome: And if you want any of the behind the scenes stuff, you can watch this full video, but I'm happy to send that stuff your way as well. I'm full on transparency here. So that way you can create your own.

And if you'd like to augment it with your own references, you can do that. So here's fully transparent for you all. And once again, here's the knowledge base that we're working with. And you can ask it for what these things actually are. Everything that we've put into this is freely available on the internet.

We did not pay for anything. to put in. So in terms of like standards, we don't have access to any of that in here. You could nothing stopping you from uploading those standards in your own and say, Hey, given this now, give me some more.

If you do use this, please feel free to give us feedback. This is a free resource to the community. We want this to be Something genuinely that people can use and hopefully it helps them out. I don't know. I think we came up with something pretty cool in two hours.

[00:35:51] Frank Lacson: Yeah. That's a lot of fun.

All right. The use of it, seeing how it goes.

[00:35:58] Nick Roome: We will be off next week for Halloween. I have a little monster to take trick or treating. So we'll be back First week of November but for now, Frank, thank you for being my pitch hitter here.

And I know you're calling in remote doubly appreciate you jumping on and hopefully we can, hopefully this was a fun use of your time in the hotel room.

[00:36:20] Frank Lacson: Yeah, glad it worked out. It's really cool with the technology to be able to contribute to a podcast. Just using a tablet

[00:36:28] Nick Roome: look at that.

All right. Thank you all for all your contributions tonight. And I guess I could plug some things before we go. We, we have our podcast. You can review that anywhere. If you want to support the show, you can let people know word of mouth. You can tell them about the Human Factors cast, GPT, that we created live on stream for you tonight.

If you'd like to, and have the financial means to, we do have a Patreon, so you can support the show right here. It's completely optional, we'll make this free to everybody, but it You want to support us to help us do more fun stuff like this? That's there for you. And then I think we'll wrap it up there.

So thank you, Frank. Thank you, Neil. Thank you, Barry. Thank you, everyone who contributed tonight. Really appreciate your time. And until next time, it depends. It depends. Let's see what it says to It Depends.

Did we break it? You got it right! The phrase It Depends is commonly used in Human Factors UX and design related fields because the best pre yeah. Alright! Thanks everybody! Have a good night! Bye! Bye! Bye everybody! Bye!