WEBVTT 00:08.640 --> 00:11.820 I'm being inundated with questions so 00:11.820 --> 00:15.720 I'll ask one of myself or I asked one 00:15.720 --> 00:18.220 of Mr McNeese . How about that ? Will 00:18.220 --> 00:22.120 that work ? Sure sir . Okay so when 00:22.130 --> 00:25.510 so when the C . G . Says transformation 00:25.510 --> 00:28.860 what does that mean to you ? That's 00:28.860 --> 00:32.530 that is a really good question because 00:32.540 --> 00:34.707 transformation means so many things to 00:34.707 --> 00:37.260 different people . But you have 00:37.270 --> 00:40.630 transition when you change from once 00:40.640 --> 00:42.680 one station to another and you know 00:42.680 --> 00:45.570 where you're going transformation is 00:45.570 --> 00:48.840 more like an open ended journey . You 00:48.840 --> 00:50.840 know that you're going to cross the 00:50.840 --> 00:52.951 ocean but you're not sure what you're 00:52.951 --> 00:55.118 going to get when you get there or how 00:55.118 --> 00:57.229 you're going to be able to adapt when 00:57.229 --> 00:59.340 you get there . Uh So you got an idea 00:59.340 --> 01:01.340 of what you're trying to get to but 01:01.340 --> 01:03.507 you're not sure what you're gonna look 01:03.507 --> 01:05.673 like when you're there but we'll we'll 01:05.673 --> 01:08.700 all be there together . Yeah so that's 01:08.700 --> 01:11.880 kind of then back to me and so so let 01:11.880 --> 01:15.000 me let me kind of I'll tag along after 01:15.010 --> 01:18.820 after that . No . So when 01:18.820 --> 01:20.931 you're , you know , I didn't . One of 01:20.931 --> 01:22.931 the , one of the interesting things 01:22.931 --> 01:26.310 about this job for me is 01:26.320 --> 01:28.950 is describing 01:29.940 --> 01:33.610 a future state that's always 01:33.610 --> 01:36.210 difficult for leaders . But I think 01:36.290 --> 01:39.120 especially if you're , if you're in an 01:39.120 --> 01:42.370 organization that provides a different 01:42.380 --> 01:44.680 set of services than what you're used 01:44.690 --> 01:46.912 to being around . I mean , so I grew up 01:46.912 --> 01:49.470 in the civil affairs community , so I 01:49.470 --> 01:51.750 kind of knew how to describe a future , 01:51.760 --> 01:55.760 a future state for civil affairs , but 01:55.760 --> 01:58.560 a readiness division delivers a certain 01:59.240 --> 02:02.820 set of services to our partners . And , 02:02.830 --> 02:05.370 and so it's a little bit difficult to 02:05.370 --> 02:09.160 describe it . But as I talked to 02:09.540 --> 02:11.710 to Colonel Lewis and Colonel cheater 02:11.710 --> 02:14.810 this morning , I'm starting to get my 02:14.810 --> 02:18.350 feet under me to describe what what the 02:18.350 --> 02:22.200 future looks like and and how 02:22.210 --> 02:25.040 we can transform into delivering 02:25.040 --> 02:28.190 services either better or 02:28.190 --> 02:31.560 faster or more comprehensive . 02:32.140 --> 02:35.300 And so I'll give you kind of one one 02:35.300 --> 02:39.200 example of the , so you've 02:39.210 --> 02:43.060 got a facility out in the Denver area , 02:43.740 --> 02:46.170 the Fitz Simmons facility . And it's 02:46.170 --> 02:48.450 been under , I've had units in that 02:48.460 --> 02:50.720 facility as long as I've been at your 02:50.720 --> 02:54.640 officer oh and one recurring 02:54.640 --> 02:58.100 theme that's that's always brought to 02:58.110 --> 03:00.277 people's attention about that facility 03:00.277 --> 03:03.860 is the gate is everyone 03:04.540 --> 03:07.660 identifies that the gate not working 03:08.140 --> 03:11.350 well or all the time as an issue . 03:12.220 --> 03:15.580 And that that one singular gait creates 03:17.140 --> 03:20.930 physical security issues . So the 03:20.930 --> 03:24.730 real response to that , what's 03:24.730 --> 03:28.410 going on there , it really isn't just 03:28.420 --> 03:32.050 a D . P . D . A . D . P . W . Problem . 03:33.040 --> 03:36.680 There's also aspects of that that are G . 03:36.680 --> 03:40.310 34 which which looks at the 03:40.320 --> 03:43.690 physical security of our facilities . 03:44.340 --> 03:47.560 Some of it's even the G four 03:48.840 --> 03:52.730 that looks at how much stuff is stored 03:52.740 --> 03:56.590 in the facility . And so to actually 03:56.590 --> 04:00.390 improve uh the facility 04:00.390 --> 04:03.950 for our partner or our partners that 04:03.950 --> 04:06.330 are there and actually improve their 04:06.330 --> 04:09.610 readiness requires a little bit more of 04:09.610 --> 04:12.640 a comprehensive response . And so if 04:12.640 --> 04:15.860 you if you participate in the 04:15.870 --> 04:18.740 commander's update brief , the one that 04:18.740 --> 04:22.450 we had in in 04:22.790 --> 04:25.950 May , the last one we had was in May 04:26.510 --> 04:28.510 and we ended up having a discussion 04:28.510 --> 04:31.640 about , well how does a physical 04:31.640 --> 04:35.340 security deficiency get in the 04:35.350 --> 04:37.890 facility itself ? How does that , how 04:37.890 --> 04:40.057 does that get brought to the attention 04:40.540 --> 04:44.310 DPW And I think we identified 04:44.320 --> 04:47.550 kind of a gap that is pretty easily 04:47.550 --> 04:51.180 fixed right now . It's just you just 04:51.180 --> 04:53.236 have to walk over and make sure that 04:53.236 --> 04:57.150 DPW knows that hey the CSS ticket 04:57.150 --> 04:59.990 that's gonna come in related to the 05:00.000 --> 05:03.660 Fitzsimmons facility is 05:04.340 --> 05:07.010 actually one that's a priority because 05:07.010 --> 05:09.160 it was identified as a physical 05:09.160 --> 05:13.120 security deficiency . Yeah , I 05:13.120 --> 05:15.410 think the other thing that then flows 05:15.410 --> 05:17.360 out of that is is the things that 05:17.370 --> 05:21.050 cannot be addressed are are 05:21.050 --> 05:24.770 then able to be articulated better is 05:24.770 --> 05:26.881 things that the commander may need to 05:26.881 --> 05:30.600 get involved in . And so , you know , 05:30.610 --> 05:34.560 to me , transformation sometimes isn't 05:35.240 --> 05:38.490 about a new thing or 05:38.500 --> 05:42.020 even a new , even necessarily a new 05:42.020 --> 05:44.560 process , it's about ways for us to 05:44.560 --> 05:47.630 communicate better about an issue . And 05:47.630 --> 05:49.463 how do we respond to it ? And we 05:49.463 --> 05:52.170 respond to it comprehensively ? Or do 05:52.170 --> 05:55.090 we just respond to it as one individual 05:55.090 --> 05:59.060 section at a time responding to it ? 05:59.940 --> 06:01.940 I think a critical piece of that is 06:01.940 --> 06:04.860 always letting our customer . No , 06:05.440 --> 06:08.650 that there is that there is indeed 06:09.240 --> 06:12.160 an issue . I want to check here real 06:12.160 --> 06:14.800 quick . There may be a question and 06:14.800 --> 06:16.960 chan okay , so 06:18.340 --> 06:21.460 this one is from 06:22.240 --> 06:25.440 uh robert thomas sir . We are eager 06:25.450 --> 06:29.390 uh to see who will be wear so we can 06:29.390 --> 06:32.230 make plans . I suspect that quite a few 06:32.230 --> 06:34.286 green suitors that have been working 06:34.286 --> 06:36.760 out of Fort McCoy , we'll be working at 06:36.760 --> 06:39.350 Fort Snelling at some point soon . It 06:39.350 --> 06:41.840 also makes sense that we that we keep 06:41.840 --> 06:44.310 some people at Fort McCoy to work side 06:44.310 --> 06:45.870 by side with their civilian 06:45.870 --> 06:48.200 counterparts would be helpful to know 06:48.200 --> 06:50.500 when that decision will be made . You 06:50.500 --> 06:52.810 have any estimate as to when you will 06:52.810 --> 06:56.640 make that decision ? Well sort of as I 06:56.640 --> 06:59.610 laid out , I really have made the 06:59.610 --> 07:01.620 decision that we're gonna be split 07:01.620 --> 07:03.453 stationed and I think what we're 07:03.453 --> 07:06.250 waiting for right now is feedback from 07:06.250 --> 07:09.230 the staff on some of the each is that 07:09.240 --> 07:13.130 you describe , you know , I'm not I'm 07:13.130 --> 07:16.850 certainly not looking , I'm not 07:16.850 --> 07:18.860 looking to oh 07:20.140 --> 07:23.010 make a decision that somebody comes 07:23.010 --> 07:25.860 back around , you know , a year from 07:25.860 --> 07:28.560 now or two years from now and second 07:28.560 --> 07:31.730 guesses , what I'm interested in is 07:31.730 --> 07:34.570 making decisions that make sense for 07:34.570 --> 07:37.950 the command . Now , some of that is 07:37.950 --> 07:41.840 found in the in the manning document 07:41.850 --> 07:44.160 for the command . You know , there's a 07:44.740 --> 07:47.720 there's a stationing action that was 07:47.720 --> 07:51.680 proved . Oh and went into I 07:51.680 --> 07:53.830 guess the media went into effect back 07:53.830 --> 07:56.060 in october , that sort of says where 07:56.060 --> 07:58.227 people are supposed to be . There have 07:58.227 --> 08:00.338 been some of those positions that had 08:00.338 --> 08:03.120 been moved over to McCoy . Uh we we 08:03.120 --> 08:06.400 frankly we can't we can't piece an A G 08:06.400 --> 08:09.140 R for example , we can't pcs them the 08:09.140 --> 08:12.650 second time . Oh , just from 08:12.650 --> 08:15.600 McCoy back over to schmeling . So some 08:15.600 --> 08:18.470 of the changes that fall into that 08:18.480 --> 08:21.190 category will occur , you know , when 08:21.190 --> 08:23.830 someone's backfield comes in . Probably 08:23.830 --> 08:26.250 the best example of that that I know 08:26.260 --> 08:29.770 right off the top of my head is the 08:29.770 --> 08:33.530 SGS position . So so the position 08:33.530 --> 08:35.900 actually on the Teda is supposed to be 08:35.910 --> 08:39.790 at fortunately . But 08:39.790 --> 08:43.260 it was moved over to Fort 08:43.260 --> 08:45.482 McCoy because that's where the previous 08:45.482 --> 08:47.560 commander thought that that position 08:48.040 --> 08:51.950 could best be utilized . And in my case 08:52.150 --> 08:55.860 and in my case I kind of might going in 08:56.240 --> 08:59.550 assumption is that people belong where 08:59.550 --> 09:03.250 the army thinks they thinks they should 09:03.260 --> 09:05.400 be , which is identified in Teda 09:05.410 --> 09:08.200 documents . And certainly in my case , 09:09.050 --> 09:11.420 I really do think that the SGS needs to 09:11.430 --> 09:15.000 be nearest the commander to help 09:15.010 --> 09:18.530 organize the correspondence 09:18.540 --> 09:21.320 coming in and out with the commander . 09:21.320 --> 09:23.900 And certainly helped me to be able to 09:23.910 --> 09:27.740 talk , you know , to talk to the 09:27.740 --> 09:30.550 SGS without having to pick up the phone 09:31.100 --> 09:32.933 and wonder if Colonel Venable is 09:32.933 --> 09:35.156 rolling his eyes at anything I might be 09:35.156 --> 09:38.260 saying . I know he wouldn't do that . 09:38.270 --> 09:40.980 But he could be when you can't actually 09:40.980 --> 09:43.540 see somebody . So we're gonna work 09:43.540 --> 09:45.651 through it in a logical fashion . And 09:45.651 --> 09:48.460 we will if I I mean I would I would say 09:48.460 --> 09:50.920 the specifics on that . I'm kind of 09:50.920 --> 09:54.460 looking at Kelly next 30 days , easily 09:54.460 --> 09:56.571 within the next 30 days . Okay easily 09:56.571 --> 10:00.250 within the next 30 days . Ah Okay . 10:00.740 --> 10:04.110 No . Do I have another , another 10:04.110 --> 10:05.388 question from anyone ? 10:08.440 --> 10:10.640 Let's see . Maybe I have a follow up . 10:10.650 --> 10:14.570 No up I have a 10:14.570 --> 10:18.390 hand raised so let's 10:18.390 --> 10:22.360 see uh long name and I 10:22.360 --> 10:23.750 don't have my glasses on 10:26.440 --> 10:30.310 fine like hey dominick , sorry I 10:30.310 --> 10:32.810 got my glasses on now so I can I can 10:32.810 --> 10:34.260 see you . So go ahead 10:37.340 --> 10:38.650 my wife . Okay . 10:42.340 --> 10:45.940 Sure . Yeah . 10:46.540 --> 10:49.720 Yeah . Mhm . Readiness . Peace 10:50.240 --> 10:52.500 building . A sense of community harvey 10:52.500 --> 10:56.250 reserves kind of a standard within 10:56.250 --> 11:00.170 geographic nature of deserves just 11:00.180 --> 11:03.440 curious your thoughts on moving forward 11:03.440 --> 11:06.820 how ways to kind of bring army reserve 11:06.820 --> 11:09.180 together as a community to get through 11:09.180 --> 11:11.347 the time since the saddle size soldier 11:11.347 --> 11:15.120 family ready ? Yeah . So , so here I'll 11:15.120 --> 11:17.287 just give you , I mean , I'll give you 11:17.287 --> 11:19.453 some , I'll give you some thoughts and 11:19.453 --> 11:21.398 some of this will no doubt be uh , 11:24.240 --> 11:26.351 some of this will be kind of big hand 11:26.351 --> 11:30.340 wave stuff . I realized . I , I think 11:30.350 --> 11:32.980 one of the things we kind of , we kind 11:32.980 --> 11:35.160 of suffer from with a lot of our 11:35.170 --> 11:38.450 programs in the army reserve is we've 11:38.460 --> 11:40.570 been doing , we've been doing them a 11:40.570 --> 11:44.410 certain way for a long time and in some 11:44.410 --> 11:46.470 cases we have to do them that way 11:46.480 --> 11:49.060 because that's what maybe even the 11:49.060 --> 11:51.050 statute says or certainly the 11:51.050 --> 11:54.740 regulation says . I 11:54.750 --> 11:58.550 think one of the advantages of 11:58.560 --> 12:01.340 this kind of innovation process that 12:01.350 --> 12:03.550 I'm trying to introduce the command to 12:04.140 --> 12:08.130 is this idea of try something 12:08.130 --> 12:10.170 small , something that's minimally 12:10.170 --> 12:13.750 viable and then give some feedback 12:14.240 --> 12:17.560 from those that it's supposed to impact . 12:18.240 --> 12:20.510 And so I think from the family , from 12:20.510 --> 12:24.150 the family readiness a standpoint 12:25.040 --> 12:27.410 or from the soldier family readiness 12:27.410 --> 12:30.300 standpoint . As you know , you got a 12:30.310 --> 12:33.810 couple of constituencies that 12:33.820 --> 12:36.980 you're trying to impact soldiers and 12:36.980 --> 12:39.450 their and their families and in some 12:39.450 --> 12:43.350 cases extended families . Uh , so 12:43.360 --> 12:46.080 in my mind , those are , so there are 12:46.090 --> 12:49.570 customers or our partners in this 12:49.570 --> 12:52.590 process and therefore there might be 12:52.590 --> 12:56.150 things that we need to know from them 12:56.540 --> 13:00.460 and then try try out , try out for them . 13:01.140 --> 13:03.307 Yeah , I ain't one of the things we've 13:03.307 --> 13:06.260 learned in the army reserve is , well , 13:06.940 --> 13:09.570 you know , the double eagle app , I'll 13:09.570 --> 13:11.590 refer to it as the long suffering 13:11.600 --> 13:15.090 double eagle app . It is a great 13:15.090 --> 13:17.610 idea . I think if it , I think if it 13:17.610 --> 13:20.040 had , you know , kind of one 13:20.050 --> 13:23.590 overarching failing it was that it was 13:23.590 --> 13:27.490 rolled out and you weren't able to 13:27.490 --> 13:30.350 provide some of that kind of user 13:30.350 --> 13:34.350 feedback on what would make it , what 13:34.350 --> 13:37.740 would make it more functional . And so 13:37.740 --> 13:40.030 when I kind of think about when I think 13:40.030 --> 13:42.190 about soldier and family readiness , 13:42.940 --> 13:45.400 you know , part of it is is we went 13:45.410 --> 13:48.990 from , we went from an environment 13:49.000 --> 13:52.260 where we were deploying a lot as an 13:52.260 --> 13:56.190 Army reserve . Yeah . You 13:56.190 --> 14:00.050 know , six years ago , uh now 14:00.800 --> 14:03.160 the environment has changed quite a bit . 14:03.740 --> 14:06.880 And so now we're deploying much , much 14:06.880 --> 14:10.230 less for nine month 14:10.240 --> 14:13.960 deployments and we're doing , you know , 14:14.540 --> 14:18.360 exercise support That may last 30 days . 14:18.740 --> 14:22.510 Uh We we we have we've 14:22.510 --> 14:25.560 had Covid which initially presented 14:25.560 --> 14:27.600 some challenges to families that we 14:27.600 --> 14:31.560 hadn't we hadn't faced before . And 14:32.040 --> 14:35.580 you know , so I think it's this idea of 14:35.590 --> 14:38.970 how do we look for ways to meet the 14:38.970 --> 14:42.360 needs of those we serve . 14:43.240 --> 14:46.060 You know , it's and it is geographic 14:46.440 --> 14:48.700 and so there's , I mean , I think 14:48.700 --> 14:51.740 there's always been this issue of unit 14:51.750 --> 14:55.590 cohesion . Unit cohesion is always 14:55.590 --> 14:57.646 meant a lot to the army , but you're 14:57.646 --> 15:00.250 really having to kind of aggregate that 15:00.250 --> 15:02.600 cohesion at a much higher level . And I 15:02.600 --> 15:04.711 think that impacts how do people want 15:04.711 --> 15:08.580 to be involved ? So I've I've responded 15:08.590 --> 15:12.060 long winded lee with no real answers 15:12.060 --> 15:14.060 other than I think what I would say 15:14.060 --> 15:16.690 kind of you and your team is look for 15:16.690 --> 15:18.580 those ways . They really get some 15:18.580 --> 15:22.250 customer customer feedback from people 15:22.940 --> 15:26.930 that might tell us something that's a 15:26.930 --> 15:29.152 little bit different . And so I'll give 15:29.152 --> 15:30.986 you a couple of examples . We've 15:30.986 --> 15:33.097 already had some customer feedback on 15:33.097 --> 15:35.263 some things that I've said in the chat 15:35.263 --> 15:38.830 box . So one is after my response about 15:38.830 --> 15:42.800 Fort Snelling ah receiving logistical 15:42.800 --> 15:44.967 support while working at Fort Snelling 15:44.970 --> 15:48.940 has has us at a disadvantage . Can we 15:48.940 --> 15:50.884 have the U . I . C . S . From Fort 15:50.884 --> 15:53.051 Snelling updated so that the dough dax 15:53.051 --> 15:55.620 and point to Fort Snelling . I'm 15:55.620 --> 15:58.290 looking at Mr Desert who's in the room 15:58.290 --> 16:00.457 here with us and he's shaking his head 16:00.457 --> 16:02.679 because that's been a frustrating point 16:02.679 --> 16:04.980 to him as well . And so that's 16:05.290 --> 16:07.840 something that you know that we can 16:07.840 --> 16:11.300 work through because now we understand 16:11.310 --> 16:13.680 now we're committing to a direction and 16:13.680 --> 16:15.847 it's something we know we need to work 16:15.847 --> 16:19.390 through a different comment . Double 16:19.390 --> 16:21.880 Eagle app is not user friendly or 16:21.880 --> 16:25.120 millennial user friendly . That is the 16:25.120 --> 16:28.170 majority of the military age group . I 16:28.170 --> 16:30.003 think that's you know , hey that 16:30.003 --> 16:32.170 comments right right on the mark . And 16:32.170 --> 16:35.250 it gets into this idea really . You got 16:35.250 --> 16:38.730 to get feedback from people before you 16:38.730 --> 16:42.540 commit , you know , literally 16:42.540 --> 16:45.020 hundreds of thousands of dollars 16:46.140 --> 16:49.910 to something . I think it's this idea 16:49.910 --> 16:52.680 of trying , trying small things , 16:52.680 --> 16:55.190 getting some feedback and if , and if 16:55.190 --> 16:57.810 it's , you know , if it's what people 16:57.810 --> 17:00.570 are wanting , uh , then 17:01.040 --> 17:04.270 moving to something 17:04.640 --> 17:07.550 that's a little bit , give them another 17:07.550 --> 17:09.810 feature or another couple of features 17:09.810 --> 17:13.630 and keep getting their feedback . I 17:13.640 --> 17:17.320 mentor startups . Uh , in 17:17.330 --> 17:21.290 texas tech university . And that's the 17:21.290 --> 17:23.890 process of startup . Goes , goes with 17:23.900 --> 17:27.760 it has an idea . It tries to get some 17:27.770 --> 17:30.170 feedback initially when it's just an 17:30.170 --> 17:34.150 idea . Would this help you let me know 17:34.150 --> 17:37.990 how , how you feel about it ? Those 17:38.020 --> 17:40.760 kind of customer interviews really have 17:40.760 --> 17:43.100 to occur in person . You know , you 17:43.100 --> 17:46.500 can't . Surveymonkey is 17:46.500 --> 17:50.280 good for certain things , but 17:50.280 --> 17:52.336 it's things like this where you have 17:52.336 --> 17:54.670 ideas , you have to find a way to talk 17:55.280 --> 17:57.310 to those that would actually be the 17:57.310 --> 17:59.800 customers of it . I realize that's not 17:59.800 --> 18:02.060 easy when it comes to in the family 18:02.070 --> 18:04.292 world to find people that will actually 18:04.292 --> 18:06.880 talk to you and and in reality find 18:06.880 --> 18:08.769 people that will talk to you that 18:08.769 --> 18:10.960 haven't been talking to you . I think 18:10.960 --> 18:14.410 that's always important . So do we have 18:14.410 --> 18:16.970 a I got more double down on the double 18:16.980 --> 18:19.330 Eagle app is not user friendly for the 18:19.330 --> 18:22.020 civilian workforce . I would agree with 18:22.020 --> 18:24.560 that . I agree with that wholeheartedly .