WEBVTT

00:00.440 --> 00:02.662
So ladies , thanks for joining us today

00:02.662 --> 00:04.884
on leadership blog , which is a podcast

00:04.884 --> 00:07.107
for the Air Force Life Cycle Management

00:07.107 --> 00:06.980
Center community on topics of interest

00:06.990 --> 00:08.934
and the topic of interest today is

00:08.934 --> 00:10.990
learning about gear fit , uh an app

00:11.000 --> 00:13.580
that that helps us get the right

00:13.590 --> 00:15.610
fitting or the right fit for our

00:15.610 --> 00:18.020
equipment , I think it's how it is , so

00:18.030 --> 00:20.197
what we're going to learn about that ,

00:20.197 --> 00:22.308
so um taylor , if you could introduce

00:22.308 --> 00:24.308
yourself to the audience and give a

00:24.308 --> 00:26.474
little bit of your career background ,

00:26.474 --> 00:28.530
well thanks for having us today , we

00:28.530 --> 00:30.752
really appreciate it . Um So my name is

00:30.752 --> 00:32.808
Taylor Harrison and I am the program

00:32.808 --> 00:35.030
manager for gear fit . I currently work

00:35.030 --> 00:37.086
in human systems division within the

00:37.086 --> 00:39.740
Combat Ready Airmen branch . Um prior

00:39.740 --> 00:42.900
to that I worked in MQ nine and I also

00:42.900 --> 00:46.290
did um six years of active duty working

00:46.290 --> 00:48.480
within the acquisition community . So

00:48.480 --> 00:50.536
I've been at this for a little bit ,

00:50.536 --> 00:52.480
but I've been here in Combat Ready

00:52.480 --> 00:54.702
Airmen for almost two years now . Um So

00:54.940 --> 00:58.530
just had a lot of different abilities

00:58.530 --> 01:02.470
to get to really impact our

01:02.480 --> 01:04.560
airmen and not so much just like

01:05.040 --> 01:07.910
platforms , but we're , this this

01:07.910 --> 01:09.799
particular program has been super

01:09.799 --> 01:12.640
amazing because we're getting feedback

01:12.640 --> 01:14.862
from our airmen and from the end user ,

01:14.862 --> 01:16.862
so we're not just delivering them ,

01:16.862 --> 01:18.918
hoping that we've hit the mark , but

01:18.918 --> 01:20.862
they are in the process of it . So

01:20.862 --> 01:23.140
that's been a really great opportunity .

01:23.140 --> 01:25.251
So overall uh help us understand what

01:25.251 --> 01:27.362
is combat Ready airmen , what is that

01:27.362 --> 01:30.030
program . Great question . Um So Combat

01:30.030 --> 01:32.380
Ready Airman is a new program office

01:32.380 --> 01:34.630
that's standing up and it is serving

01:34.630 --> 01:38.580
the 91% of all A . F . S . Es um that

01:38.580 --> 01:42.380
are not aircrew or um Special Ops .

01:42.390 --> 01:45.230
So those have specific program offices

01:45.230 --> 01:47.452
that deal with all their needs , but we

01:47.452 --> 01:50.490
focus solely on like maintenance ,

01:50.500 --> 01:53.760
security forces , medics , anybody that

01:54.140 --> 01:56.780
isn't Aircrew or Special Ops . And so

01:56.790 --> 02:00.210
um right now there is no program office

02:00.210 --> 02:02.488
that's really standardizing everything .

02:02.488 --> 02:04.543
So everything is at the unit level ,

02:04.543 --> 02:07.370
the commanders find the needs for them

02:07.370 --> 02:10.490
and we don't have consistency across

02:10.490 --> 02:12.950
the Air Force which can cause gaps in

02:13.540 --> 02:17.340
um training . So if you're at home and

02:17.340 --> 02:20.760
your one unit uses you know product A

02:21.140 --> 02:23.362
and you're used to that , but maybe you

02:23.362 --> 02:25.720
pcs and you go to unit B well now they

02:25.720 --> 02:27.942
don't use that . So now you get a whole

02:27.942 --> 02:30.053
new thing and you're trying to figure

02:30.053 --> 02:32.164
it out . But it's the same , you know

02:32.164 --> 02:34.276
the same purpose , right ? And you're

02:34.276 --> 02:36.276
talking gear , gear and equipment ,

02:36.276 --> 02:38.331
right , yep . It could be , yep . So

02:38.331 --> 02:41.930
like body armor or um maybe handcuffs

02:41.930 --> 02:45.880
even um overalls , anything that

02:45.890 --> 02:49.090
is specific to their fc . So we are

02:49.090 --> 02:51.257
trying to just make sure that they are

02:51.257 --> 02:53.423
all standardized and maybe that's just

02:53.423 --> 02:55.550
us providing a list that says hey if

02:55.550 --> 02:57.606
you're looking for body armor , your

02:57.606 --> 03:00.090
authorized these three vests , you can

03:00.090 --> 03:02.257
pick within it , but all the Air force

03:02.257 --> 03:04.257
has access to it . So if you deploy

03:04.257 --> 03:06.368
your trained up on it , you know what

03:06.368 --> 03:08.479
your buddy is wearing , You can , you

03:08.479 --> 03:10.479
know , get it off if they're really

03:10.479 --> 03:12.701
injured and they need a quick exit . Um

03:12.701 --> 03:14.812
and it just helps make sure we're all

03:14.812 --> 03:17.034
safe across the air force and we're all

03:17.034 --> 03:19.500
standardized . And so now gear fit is a

03:19.510 --> 03:21.720
part of that or supports that combat

03:21.720 --> 03:24.350
ready airmen and help us understand how

03:25.040 --> 03:26.830
So ? Well , that's kind of an

03:26.830 --> 03:28.997
interesting question because so within

03:28.997 --> 03:31.163
combat Ready Airmen , we have a female

03:31.163 --> 03:34.070
fit mint initiative . Um and so I'm the

03:34.070 --> 03:36.540
female Fitbit lead as well . And the

03:36.540 --> 03:38.820
intent of that is to ensure that all

03:38.820 --> 03:41.070
current and future human system

03:41.070 --> 03:43.870
division requirements have a female fit

03:43.870 --> 03:46.660
mint focus . So it doesn't mean that

03:46.670 --> 03:48.990
each requirement is specific for

03:48.990 --> 03:50.823
females . It means that it's all

03:50.823 --> 03:52.970
encompassing . So maybe if we're

03:52.970 --> 03:55.600
looking at , let's say for our aircrew

03:55.600 --> 03:58.840
side masks , oxygen masks , did we

03:58.840 --> 04:00.896
include the anthropocene metric data

04:01.440 --> 04:03.960
that allows for their size , face to be

04:04.340 --> 04:06.396
involved ? When we wrote the PPS and

04:06.396 --> 04:09.280
PSAs for that mass . If not , that's

04:09.280 --> 04:11.558
where we kind of come in and say , hey ,

04:11.558 --> 04:13.980
we think we need to tweak those PSAs to

04:13.980 --> 04:17.730
be a little bit broader . Um So where

04:17.730 --> 04:20.850
gear fit comes into this is in 2019 ,

04:20.850 --> 04:23.540
there was an app works challenge and

04:23.600 --> 04:25.656
they had a workshop and this was for

04:25.656 --> 04:29.220
aircrew or or a female airmen and

04:29.380 --> 04:33.270
they had a lot of concerns

04:33.270 --> 04:36.750
and kind of voiced some of the

04:37.240 --> 04:40.330
gaps that they had for their air air

04:40.490 --> 04:44.110
air crew equipment . And so when

04:45.140 --> 04:47.362
leaving that , we were like , how do we

04:47.362 --> 04:50.700
capture all of these gaps because the

04:50.700 --> 04:52.890
requirements are getting to us , but

04:52.890 --> 04:55.320
we're not being intentional to make

04:55.320 --> 04:57.431
sure that they are encompassing these

04:57.431 --> 04:59.570
ladies . And so that's where the gear

04:59.570 --> 05:02.620
fit came in was , how do those users

05:02.630 --> 05:05.620
provide that feedback back to the , to

05:05.620 --> 05:09.260
the spo so that we can help get

05:09.270 --> 05:11.048
get like right to it when those

05:11.048 --> 05:13.270
requirements come in , because we don't

05:13.270 --> 05:15.437
control the requirements , right ? And

05:15.437 --> 05:17.492
the acquisition community , we don't

05:17.492 --> 05:19.714
build the requirements , We fill them ,

05:19.714 --> 05:21.900
right . And so , um , when we're

05:21.900 --> 05:24.122
getting those requirements were working

05:24.122 --> 05:25.733
with those magic ums and the

05:25.733 --> 05:27.956
requirements owners to make sure like ,

05:27.956 --> 05:30.178
hey , we've gotten a lot of concerns or

05:30.178 --> 05:32.400
questions or feedback about this , Like

05:32.400 --> 05:34.400
have we thought of this ? And we're

05:34.400 --> 05:36.567
working with those communities to make

05:36.567 --> 05:38.511
sure the requirement is really all

05:38.511 --> 05:40.567
encompassing . And so that's kind of

05:40.567 --> 05:42.567
where gear fit came about . But now

05:42.567 --> 05:45.010
gear fit is not just for females , this

05:45.010 --> 05:48.470
is open to all aircrew . And so we are

05:48.470 --> 05:51.070
really trying to figure out where those

05:51.070 --> 05:53.440
gaps are and it's a non attribution

05:53.460 --> 05:56.390
environment . So we're hoping that hey ,

05:56.390 --> 05:59.330
as this feedback comes in , these air

05:59.330 --> 06:01.690
crew are going to see long term the

06:01.690 --> 06:04.410
impacts of having that communication

06:04.410 --> 06:07.610
with us . Yeah . And so that led to

06:07.610 --> 06:10.060
kind of our partnership ultimately with

06:11.090 --> 06:14.700
with uh , with , I'm sorry , I forgot

06:14.700 --> 06:16.930
the name of the company skylight

06:16.940 --> 06:18.996
skylight . Okay . So that led to our

06:18.996 --> 06:21.051
collaboration with skylight . And so

06:21.051 --> 06:23.273
let's go ahead and meet you . Nicole if

06:23.273 --> 06:25.107
you could introduce yourself and

06:25.107 --> 06:27.384
explain a little bit about what you do .

06:27.740 --> 06:29.740
Sure . Hello . I'm Nicole . I'm the

06:29.740 --> 06:31.960
product manager for the gear fit

06:32.340 --> 06:36.020
products . So I work with some skylight

06:36.120 --> 06:38.670
teammates , developers , designers ,

06:38.670 --> 06:41.840
researchers in addition to some Air

06:41.840 --> 06:43.896
Force developers as well through the

06:43.896 --> 06:46.230
best been software factory . And we are

06:46.230 --> 06:48.620
working on building out the gear fit

06:48.620 --> 06:51.460
website and experience . So we

06:51.470 --> 06:55.170
are continuously releasing new

06:55.170 --> 06:57.281
features and iterating on feedback we

06:57.281 --> 07:00.460
hear to get closer to optimizing the

07:00.460 --> 07:02.571
goals that taylor was talking about .

07:02.940 --> 07:05.051
Okay . And and how long have you been

07:05.051 --> 07:07.570
with with the company ? Um , I've been

07:07.570 --> 07:09.890
with for over a year now . Okay .

07:09.900 --> 07:12.233
Alright . And and Sarah , how about you ?

07:14.040 --> 07:16.300
Yeah , so I'm Sarah and I worked with ,

07:16.310 --> 07:18.421
I'm a product designer for gear fit .

07:18.421 --> 07:20.477
So I work with the other designer on

07:20.477 --> 07:23.220
our team , Taylor um , and we are sort

07:23.220 --> 07:27.050
of the voice for the user . So we work

07:27.050 --> 07:29.800
and do research understanding who's

07:29.800 --> 07:31.967
using gear fit , get a better sense of

07:31.967 --> 07:34.133
what they want and what they need . So

07:34.133 --> 07:35.800
that we're always creating an

07:35.800 --> 07:37.967
application . Sorry , the website that

07:37.967 --> 07:40.830
um works really well and accommodates

07:40.830 --> 07:43.590
for all their needs . Um , and that's

07:43.590 --> 07:45.590
sort of where we play into building

07:45.590 --> 07:48.520
gear fit as a website . Okay . And are

07:48.520 --> 07:51.240
both you guys , are you coders or your

07:51.240 --> 07:54.160
software designers or ? No , your

07:54.160 --> 07:56.438
project . You're like product managers .

07:56.740 --> 07:59.000
No . So yeah , I can explain a little

07:59.010 --> 08:01.190
post nickel and I don't have technical

08:01.190 --> 08:05.020
roles . So um our work

08:05.030 --> 08:07.280
goes more on the product end of our day

08:07.280 --> 08:09.447
to day has nothing to do with actually

08:09.447 --> 08:11.750
coding the app . But we help make the

08:11.750 --> 08:15.100
product decisions that will inform um

08:15.110 --> 08:17.360
what the developers end up actually

08:17.370 --> 08:20.140
making happen and come into reality

08:20.140 --> 08:22.370
into the into the website . Okay .

08:22.380 --> 08:25.720
Alright , cool . Um so taylor they

08:25.720 --> 08:27.720
mentioned best men . So let's let's

08:27.720 --> 08:29.720
talk about the relationship between

08:29.720 --> 08:31.770
human systems are with your comment

08:31.770 --> 08:34.690
already Airman program and with best

08:36.040 --> 08:39.640
Sure . Um so this is um a really

08:39.640 --> 08:43.480
unique um opportunity for me to come

08:43.480 --> 08:46.510
into because um so obviously for human

08:46.510 --> 08:50.430
Systems were more familiar

08:50.430 --> 08:53.080
and apt to get a requirement that's

08:53.080 --> 08:56.820
more of a tangible material solution

08:56.880 --> 08:59.140
and go and procure it and then deliver

08:59.140 --> 09:01.280
it to the user . But that's not what

09:01.280 --> 09:03.220
gear fit is gear fit like they

09:03.220 --> 09:07.060
mentioned is a software product and

09:07.060 --> 09:08.838
it's constantly evolving . It's

09:08.838 --> 09:11.480
constantly changing . And so that's not

09:11.490 --> 09:14.260
that's not our forte but we're really

09:14.260 --> 09:16.260
lucky because we have the best been

09:16.260 --> 09:19.660
team and that is what they do and so we

09:19.660 --> 09:23.430
work with them and they're contracting

09:23.430 --> 09:26.100
officers and their F . F . M . Team and

09:26.100 --> 09:29.680
their programmatic team all oversee the

09:29.680 --> 09:33.560
actual contract with Skylight . But

09:33.560 --> 09:36.280
human systems is the one that is

09:36.290 --> 09:38.690
funding it and we're the ones that are

09:38.690 --> 09:41.830
kind of not the requirements owner per

09:41.830 --> 09:43.886
se , but we're the ones that kind of

09:44.440 --> 09:46.970
tell them hey we need this and where

09:46.970 --> 09:49.560
the not the user because we also have a

09:49.560 --> 09:52.600
user but we're kind of this , I guess

09:52.600 --> 09:54.822
the brainchild really , that's where it

09:54.822 --> 09:56.822
came from us . So we work with them

09:56.822 --> 09:59.960
because each of us have this level of

09:59.960 --> 10:03.660
expertise and with , we play with the

10:03.660 --> 10:05.882
other ones , you know , expert level on

10:05.882 --> 10:08.200
it . And it works for some , for some

10:08.200 --> 10:11.820
reason we just have them on our team to

10:12.540 --> 10:14.960
to really execute with skylight .

10:16.040 --> 10:19.320
So so gear fit , it's a website .

10:19.330 --> 10:21.890
That's correct . Okay , so ultimately

10:21.900 --> 10:24.122
it's a , it's like a database . Is that

10:24.122 --> 10:26.178
is that the idea is that we're gonna

10:26.178 --> 10:28.122
collect a lot of data on different

10:28.540 --> 10:31.980
sizes and and fits and and things like

10:31.980 --> 10:34.210
that so that we can better design

10:34.210 --> 10:37.090
products or or or what , what are we

10:37.090 --> 10:39.880
trying to capture ? That's a good

10:39.880 --> 10:43.360
question . So each of the users comes

10:43.370 --> 10:47.030
into the website when they want and

10:47.030 --> 10:49.480
they are submitting like reports

10:49.480 --> 10:52.430
basically . Um and so we will have

10:52.440 --> 10:54.662
different categories and maybe it'll be

10:54.662 --> 10:57.180
like , oh this is under helmet . And so

10:57.180 --> 10:59.470
the the user might have had a flight

10:59.470 --> 11:01.526
that day and had an issue with their

11:01.526 --> 11:03.637
helmet and they're like I really want

11:03.637 --> 11:06.060
the program office to know about this .

11:06.440 --> 11:09.400
And so they will go in and they will

11:09.410 --> 11:13.380
submit a ticket under helmet and

11:13.380 --> 11:15.658
that will come to human systems office ,

11:16.140 --> 11:18.710
um , and we will look at it and maybe

11:18.710 --> 11:21.960
it's um , us finding out that their

11:21.960 --> 11:24.050
helmet digs into their shoulders or

11:24.050 --> 11:26.680
it's too heavy on their neck or they ,

11:26.690 --> 11:28.860
when they landed something jostled and

11:28.860 --> 11:30.804
it felt wrong . Some of this stuff

11:31.440 --> 11:33.720
maybe goes to their eighth shop and

11:33.720 --> 11:35.942
they can get it fixed . Maybe this is a

11:35.942 --> 11:37.776
recurring issue and they're just

11:37.776 --> 11:39.942
letting us know like , hey , I've been

11:39.942 --> 11:42.109
flying for six years and this has been

11:42.109 --> 11:44.220
an issue at every base and it doesn't

11:44.220 --> 11:46.498
matter what it does . I just have this ,

11:46.498 --> 11:48.831
this major issue with my helmet . Right ?

11:48.831 --> 11:50.831
And so we're not so much collecting

11:50.831 --> 11:52.942
sizes as we're collecting feedback on

11:52.942 --> 11:54.942
how the equipment is functioning in

11:54.942 --> 11:57.053
their day to day operation . Um , and

11:57.053 --> 12:00.200
our hope is is that when we get

12:00.370 --> 12:02.592
different bases , different match comes

12:02.592 --> 12:05.090
different platforms , um , all

12:05.100 --> 12:07.310
submitting different feedback that

12:07.310 --> 12:09.660
we're able to find those big gaps in

12:09.660 --> 12:11.493
the requirements and tweak those

12:11.493 --> 12:13.716
requirements so that we can go and fill

12:13.716 --> 12:15.604
those needs . Yeah . And that's ,

12:15.604 --> 12:17.716
that's long been a problem with a lot

12:17.716 --> 12:19.827
of our acquisition programs where the

12:19.827 --> 12:22.750
end user has the actual use of the , of

12:22.750 --> 12:25.430
the product and , but there's no link

12:25.440 --> 12:27.440
back to the program office . So the

12:27.440 --> 12:29.551
program office never knows whether it

12:29.551 --> 12:31.662
works or whether it meets their needs

12:31.662 --> 12:33.884
or not or or what kind of modifications

12:33.884 --> 12:35.884
they can feel to make it work , you

12:35.884 --> 12:38.051
know ? And so this is just a means for

12:38.051 --> 12:40.329
them to be able to do that , yep . And ,

12:40.329 --> 12:42.496
and we're not saying in the app like ,

12:42.496 --> 12:42.240
oh , yep , your , you know , your

12:42.240 --> 12:44.407
solution will be delivered next week .

12:44.440 --> 12:47.110
However , we are building that

12:47.110 --> 12:49.054
relationship with the magic um and

12:49.054 --> 12:51.790
that's really where this is a huge um a

12:51.790 --> 12:54.060
huge gain for the Air Force is because

12:54.740 --> 12:56.830
we are standing gear fit up . But

12:56.830 --> 12:58.886
simultaneously we are building these

12:58.886 --> 13:00.997
relationships with the requirements ,

13:00.997 --> 13:03.190
owners with the match comms with the

13:03.190 --> 13:05.500
commanders so that they see the value

13:05.500 --> 13:08.080
that they want their users to go in and

13:08.080 --> 13:11.560
put in their reports and it's not too ,

13:12.440 --> 13:14.273
we're not trying to recreate the

13:14.273 --> 13:17.080
process , we're trying to augment the

13:17.080 --> 13:20.310
pre existing processes and procedures

13:20.310 --> 13:22.254
that we have set up within the Air

13:22.254 --> 13:24.477
Force to just make sure that every time

13:24.477 --> 13:26.699
we are fulfilling a requirement is that

13:26.699 --> 13:30.290
we've got the Airmen's true feedback

13:30.300 --> 13:32.467
and they're buying that we're going to

13:32.467 --> 13:34.633
get after the right thing . Yeah , and

13:34.633 --> 13:36.800
you know , that's , that's important .

13:36.800 --> 13:39.022
A lot of times when you get a product ,

13:39.022 --> 13:41.078
you want to be able to tell somebody

13:41.078 --> 13:40.230
about it , you want to know that you've

13:40.230 --> 13:43.750
been hurt . Right ? So , absolutely .

13:45.440 --> 13:48.240
So right now , if you are interested in

13:48.240 --> 13:50.790
going to the website , it's a CAC

13:50.790 --> 13:53.250
enabled website , aircrew are able to

13:53.260 --> 13:55.710
go in select as taylor was describing

13:55.710 --> 13:57.800
any gear issues , you have describe

13:57.800 --> 13:59.967
what's going on , have a little bit of

13:59.967 --> 14:02.022
contact details , we do also have an

14:02.022 --> 14:04.078
anonymous capability if you prefer .

14:04.078 --> 14:07.250
And it does go in into a database

14:07.640 --> 14:11.500
and on and the folks in the human

14:11.500 --> 14:13.556
systems division , the gear smes are

14:13.556 --> 14:17.130
able to manage the responses and uh

14:17.140 --> 14:19.196
we're able to just keep that data in

14:19.196 --> 14:21.140
one spot . One of the things we're

14:21.140 --> 14:23.290
focusing on for the next couple of

14:23.300 --> 14:25.189
months is really building out our

14:25.440 --> 14:27.551
trends and analytics capabilities and

14:27.551 --> 14:29.440
learning more about what would be

14:29.440 --> 14:32.430
valuable to capture their uh in more

14:32.430 --> 14:35.190
depth but right now that you could call

14:35.190 --> 14:37.134
them tickets that come through and

14:37.134 --> 14:39.190
they're just all collected collected

14:39.190 --> 14:41.310
there . Okay . And do you guys get

14:41.310 --> 14:43.280
feedback from the users as well as

14:43.280 --> 14:45.336
first like they're the experience of

14:45.336 --> 14:48.220
them , you know to facilitate , make it

14:48.220 --> 14:49.831
easier for them to input the

14:49.831 --> 14:51.942
information into the website and that

14:51.942 --> 14:54.460
kind of thing . Yeah , for sure .

14:54.840 --> 14:57.440
That's exactly what Sarah is working on

14:57.440 --> 14:59.662
as a designer . I'll let her talk a bit

14:59.662 --> 15:02.310
more about that process . Okay . Yeah .

15:02.320 --> 15:04.920
So part of this sort of design process

15:04.930 --> 15:08.880
that um we have on the year 15 is we

15:08.880 --> 15:10.991
have really regular interactions with

15:10.991 --> 15:12.991
the people using the app . So other

15:12.991 --> 15:15.047
that the aircrew that are submitting

15:15.047 --> 15:17.670
but then also on the end of our um

15:17.680 --> 15:19.847
requirements managers which are people

15:19.847 --> 15:22.990
on the HST side um and also at the

15:22.990 --> 15:25.101
magical level that are actually going

15:25.101 --> 15:27.268
in and responding to the feedback . We

15:27.268 --> 15:29.434
have regular interactions and sessions

15:29.434 --> 15:31.323
with them where we can hear their

15:31.323 --> 15:33.212
feedback about how the website is

15:33.212 --> 15:35.434
working for them understand where their

15:35.434 --> 15:35.030
pain points are and that's what helps

15:35.030 --> 15:37.840
us to prioritize which features and

15:37.840 --> 15:40.007
which new capabilities to add into the

15:40.007 --> 15:43.230
app so that our website so that um we

15:43.230 --> 15:45.500
are able to actually have an enjoyable

15:45.500 --> 15:48.810
experience for our users . Which is

15:48.810 --> 15:51.950
what makes your fit a more modern

15:51.950 --> 15:53.672
website because we're not just

15:53.672 --> 15:56.210
producing it all in one go , you're

15:56.210 --> 15:58.154
constantly improving , improving ,

15:58.154 --> 16:00.043
improving and hopefully making it

16:00.043 --> 16:02.266
enjoyable for our people that are using

16:02.266 --> 16:04.377
it . Yeah I mean if you don't make it

16:04.377 --> 16:06.099
painless for people to put the

16:06.099 --> 16:08.154
information in then they're just not

16:08.154 --> 16:07.660
gonna bother doing it , you know ,

16:07.670 --> 16:11.090
ultimately . So uh so that's that's

16:11.090 --> 16:14.600
really great . Um So taylor let's uh if

16:14.600 --> 16:18.150
people hear this episode um and they

16:18.150 --> 16:20.390
want to be involved or they want to

16:20.400 --> 16:22.622
check it out what's what's the best way

16:22.622 --> 16:24.844
for them to to reach out to your office

16:24.844 --> 16:27.460
or or to contact you .

16:28.640 --> 16:31.540
So um I am on the Global so they can

16:31.540 --> 16:34.080
always look at Taylor Harrison . Um and

16:34.080 --> 16:36.860
I'm in W . N . U . But um if they want

16:36.860 --> 16:39.970
to check out gear fit um we are on the

16:39.970 --> 16:41.970
Air Force portal so they can always

16:41.970 --> 16:44.192
search gear fit on the Air Force portal

16:44.192 --> 16:46.414
and actually go check out the website .

16:46.414 --> 16:48.414
Um that's the quickest way to check

16:48.414 --> 16:50.637
that out and then once they're on there

16:50.637 --> 16:52.748
there is an email address um to email

16:52.748 --> 16:55.300
the gear fit team and so they can

16:55.300 --> 16:57.467
always email that the gear fit team as

16:57.467 --> 17:00.870
well to just get more information or um

17:00.870 --> 17:03.660
reach out to us with specific questions .

17:04.240 --> 17:06.760
Okay , so that pretty much brings us to

17:06.760 --> 17:08.920
the end of our time , but before we

17:08.920 --> 17:10.920
close , I just want to see is there

17:10.920 --> 17:13.087
anything that I forgot to ask you guys

17:13.087 --> 17:12.830
about or anything that you would like

17:12.830 --> 17:15.350
to add or reiterate ? Well , we

17:15.350 --> 17:17.520
appreciate this . Um , we definitely

17:17.520 --> 17:19.687
want to make it a success . So getting

17:19.687 --> 17:21.798
the name out there and letting people

17:21.798 --> 17:23.964
know that it's , there is a big deal ,

17:23.964 --> 17:26.187
so we appreciate it and um , Nicole and

17:26.187 --> 17:28.242
sarah , thank you for joining . Um I

17:28.242 --> 17:30.464
definitely appreciate the support and I

17:30.464 --> 17:32.940
think it um having you guys on , I

17:32.940 --> 17:35.273
think really highlights kind of this um ,

17:35.273 --> 17:38.740
blended approach that gear fit has ,

17:38.740 --> 17:41.010
which is one of the unique things about

17:41.010 --> 17:43.810
it . So appreciate that . All right ,

17:43.810 --> 17:46.190
well , hey , I appreciate the fact that ,

17:46.200 --> 17:48.320
that you guys are working so hard to

17:48.330 --> 17:51.920
deliver gear that airmen can use and

17:51.930 --> 17:54.041
and meets their needs actually in the

17:54.041 --> 17:56.208
field . So I think that I think it's a

17:56.208 --> 17:58.374
long time coming and it's great to see

17:58.374 --> 18:00.880
people really dedicated to that task .

18:00.890 --> 18:03.057
So thanks for joining us on leadership

18:03.057 --> 18:05.001
log today , appreciate your time .

18:05.001 --> 18:05.960
Thank you , appreciate it