#238: 40 CIOs. 40 Different Missions. How LA County's CIO Holds IT Together
LA County CIO Peter Loo and Info-Tech's Hannes Scheidegger trace a decade-long partnership, from a high-stakes hospital EHR overhaul to a 42-data-center consolidation, revealing what it really takes to turn vendors into true partners in public sector IT.
Joe Toste
Santa Barbara, CA
Player
Show notes
In this episode of the Public Sector Show by TechTables, Joe Toste sits down with Peter Loo, CIO of Los Angeles County, and Hannes Scheidegger, Chief Global Services Officer at Info-Tech, to unpack what it takes to lead IT across one of the largest and most complex county governments in America. They trace the history of their partnership back to the early 2010s when LA County's Department of Health Services undertook a massive EHR replatforming across five hospitals.
Peter and Hannes dig into the human side of large technology transformations: the importance of empowered steering committees, keeping the mission as a North Star, and treating governance as an enabler rather than a set of rigid controls, especially as the county now navigates AI governance. They also discuss the county's data center consolidation journey, going from 42 scattered, risky facilities to a modern, earthquake-resistant Tier 5 data center, and how building a business case around risk and value helped win board support.
The conversation closes with reflections on what separates a true partner from a vendor, including commitment to the cause, patience, honest and candid conversations, and the willingness to be a lightning rod when projects get contentious. Both guests share advice for up-and-coming public sector CIOs on building trust, bridging the gap between executive vision and frontline execution, and always anchoring back to the mission.
Key takeaways
- LA County runs a federated IT model with 40 departments and 40 different CIOs, making alignment and governance especially challenging.
- Successful large-scale implementations, like the DHS EHR rollout across five hospitals, depend more on change management and governance than on technology itself.
- Empowered steering committees that both solve problems and own the outcome are key to building buy-in and sustaining momentum through setbacks.
- AI and large tech governance should be framed as an enabler of responsible use, not just a checklist of controls, to avoid stifling innovation.
- Building a business case with executives means speaking the language of business: value and risk, not just technical details.
- Long-term vendor relationships become true partnerships through commitment to the mission, patience, persistence, and honest, candid conversations.
- Anchoring every project back to its 'why' helps teams navigate challenges and keeps steering committees aligned during difficult implementations.
Highlights
- 0:33 — Peter Loo gives the 30,000-foot overview of LA County's 40 departments and 46 billion dollar budget
- 1:48 — The origin story of the Department of Health Services EHR replatforming across five hospitals
- 8:58 — How a guiding principle pushed decisions down to frontline staff, paralleling today's AI governance challenges
- 16:53 — The data center consolidation story, from 42 closets and racking rooms to a modern Tier 5 facility
- 21:11 — Advice on communicating value and risk to executives in the language of business
- 28:47 — Hannes recalls being asked to help build LA County's new voting system, echoing the DHS partnership
- 33:04 — Closing advice for up-and-coming public sector CIOs on mission, patience, and partnership
00:00:00 Introductions and LA County Overview
00:01:45 Origins of the DHS EHR Project
00:04:38 Building Executive Buy-In and Governance
00:09:37 Guidelines Versus Governance in the AI Era
00:11:47 How InfoTech Partners With 40 CIOs
00:16:53 Consolidating 42 Data Centers Into One
00:21:11 Speaking the Language of Business to Boards
00:26:12 Vendor Versus True Partner
00:28:47 From EHR Project to Voting System Trust
00:33:01 Closing Advice for Public Sector CIOsWEBVTT
00:00:00.160 --> 00:00:04.880
Welcome<00:00:00.320> to<00:00:00.480> the<00:00:00.640> Public<00:00:00.800> Sector<00:00:01.120> Show<00:00:01.360> by<00:00:01.520> TechTable.<00:00:02.159> Super<00:00:02.560> excited<00:00:03.200> to<00:00:03.439> have<00:00:03.600> you<00:00:03.840> both<00:00:04.080> here.
00:00:04.880 --> 00:00:06.960
Peter,<00:00:05.200> for<00:00:05.440> those<00:00:05.520> who<00:00:05.680> don't<00:00:05.839> know<00:00:05.920> you,<00:00:06.080> give<00:00:06.240> us<00:00:06.319> a<00:00:06.480> quick<00:00:06.560> intro.
00:00:06.960 --> 00:00:10.559
Peter<00:00:07.200> Lou,<00:00:07.680> Chief<00:00:07.839> Information<00:00:08.480> Officer<00:00:09.040> of<00:00:09.440> Los<00:00:09.679> Angeles<00:00:10.080> County.
00:00:10.559 --> 00:00:12.719
Fantastic.<00:00:11.200> Hannes,<00:00:11.679> I'm<00:00:11.840> Hannes<00:00:12.160> Shaider.
00:00:12.719 --> 00:00:15.440
I'm<00:00:12.800> the<00:00:12.960> Chief<00:00:13.200> Global<00:00:13.519> Services<00:00:14.000> Officer<00:00:14.400> at<00:00:14.639> InfoTech.
00:00:15.440 --> 00:00:18.080
I<00:00:15.679> joined<00:00:15.920> InfoTech<00:00:16.640> 5<00:00:16.800> and<00:00:16.880> a<00:00:17.039> half<00:00:17.199> years<00:00:17.359> ago.
00:00:18.080 --> 00:00:25.199
Prior<00:00:18.329> to<00:00:18.578> that,<00:00:18.827> I<00:00:19.076> spent<00:00:19.324> 15<00:00:19.573> years<00:00:19.822> as<00:00:20.071> a<00:00:20.320> public<00:00:20.569> sector<00:00:20.818> consultant<00:00:21.067> and<00:00:21.316> did<00:00:21.564> a<00:00:21.813> lot<00:00:22.062> of<00:00:22.311> work<00:00:22.560> with<00:00:22.809> Los<00:00:23.058> Angeles<00:00:23.307> County,<00:00:23.556> which<00:00:23.804> we're<00:00:24.053> going<00:00:24.302> to<00:00:24.551> cover<00:00:24.800> today,
00:00:25.199 --> 00:00:33.040
which<00:00:25.509> is<00:00:25.818> going<00:00:26.128> to<00:00:26.437> be<00:00:26.747> great.<00:00:27.057> So,<00:00:27.366> Peter,<00:00:27.676> for<00:00:27.985> those<00:00:28.295> who<00:00:28.605> don't<00:00:28.914> know,<00:00:29.224> you<00:00:29.534> don't<00:00:29.843> know<00:00:30.153> LA<00:00:30.462> County,<00:00:30.772> first<00:00:31.082> give<00:00:31.391> us<00:00:31.701> the<00:00:32.010> 30,000-foot<00:00:32.320> overview.
00:00:33.040 --> 00:00:42.000
Everybody<00:00:33.440> knows<00:00:33.600> that<00:00:33.840> LA<00:00:34.160> County<00:00:34.320> is<00:00:34.480> big,<00:00:34.880> but<00:00:35.200> what<00:00:35.440> we<00:00:35.600> are,<00:00:36.079> we<00:00:36.320> have,<00:00:36.559> we<00:00:36.800> just<00:00:36.960> adopted<00:00:37.840> a<00:00:38.160> 46<00:00:38.960> billion<00:00:39.680> budget<00:00:40.399> and<00:00:40.719> made<00:00:41.360> 40
00:00:42.000 --> 00:00:46.640
departments<00:00:42.480> now.<00:00:42.719> When<00:00:42.879> I<00:00:43.040> started<00:00:43.280> with<00:00:43.440> the<00:00:43.520> county,<00:00:43.760> there<00:00:44.000> was<00:00:44.079> only<00:00:44.320> a<00:00:44.480> little<00:00:44.559> bit<00:00:44.719> over<00:00:45.200> 33<00:00:46.000> departments.
00:00:46.640 --> 00:00:52.480
So,<00:00:46.969> we're<00:00:47.299> continuing<00:00:47.628> to<00:00:47.957> grow<00:00:48.287> and<00:00:48.616> we<00:00:48.945> are<00:00:49.275> in<00:00:49.604> a<00:00:49.934> federated<00:00:50.263> environment,<00:00:50.592> decentralized<00:00:50.922> at<00:00:51.251> least<00:00:51.580> at<00:00:51.910> this<00:00:52.239> time.
00:00:52.480 --> 00:00:56.559
And<00:00:52.640> so<00:00:52.800> we<00:00:52.960> have<00:00:53.120> 40<00:00:53.520> departments,<00:00:54.000> have<00:00:54.239> 40<00:00:54.640> CIOs<00:00:55.520> that<00:00:55.760> I<00:00:56.000> work<00:00:56.160> with.
00:00:56.559 --> 00:01:01.760
I'm<00:00:56.879> responsible<00:00:57.360> for<00:00:57.600> county<00:00:57.920> direction,<00:00:58.800> strategy<00:00:59.359> and<00:00:59.520> planning<00:00:59.840> and<00:01:00.160> countywide<00:01:00.879> IT.
00:01:01.760 --> 00:01:09.520
There<00:01:01.920> is<00:01:02.160> an<00:01:02.320> Internal<00:01:02.719> Services<00:01:03.120> Department<00:01:03.520> that<00:01:03.760> deals<00:01:04.000> with<00:01:04.239> the<00:01:04.479> operations<00:01:05.040> side<00:01:05.360> that<00:01:05.680> manages<00:01:06.080> about<00:01:06.240> a<00:01:06.479> third<00:01:06.880> of<00:01:07.119> IT<00:01:07.439> and<00:01:07.600> then<00:01:07.760> the<00:01:08.000> rest<00:01:08.159> is<00:01:08.479> out<00:01:09.119> various
00:01:09.520 --> 00:01:11.680
departments.<00:01:10.560> That's<00:01:10.799> fantastic.<00:01:11.280> You're<00:01:11.520> right.
00:01:11.680 --> 00:01:15.520
I<00:01:11.840> think<00:01:12.240> I<00:01:12.400> think<00:01:12.560> LA<00:01:12.960> County<00:01:13.200> is<00:01:13.680> the<00:01:14.159> largest<00:01:14.560> county<00:01:14.960> in<00:01:15.200> America.
00:01:15.520 --> 00:01:17.920
That's<00:01:15.680> the<00:01:15.840> largest<00:01:16.080> county.<00:01:16.880> 40<00:01:17.280> departments.
00:01:17.920 --> 00:01:22.240
40<00:01:18.240> departments.<00:01:18.720> 40<00:01:19.040> departments.<00:01:19.759> 40<00:01:20.159> different<00:01:20.560> CIOs.
00:01:22.240 --> 00:01:25.920
Wow.<00:01:22.640> We're<00:01:22.880> going<00:01:22.960> to<00:01:23.040> unpack<00:01:23.360> that<00:01:23.520> today,<00:01:25.200> which<00:01:25.439> is<00:01:25.520> great.
00:01:25.920 --> 00:01:33.600
We<00:01:26.186> had<00:01:26.451> met<00:01:26.717> before<00:01:26.983> this<00:01:27.249> and<00:01:27.514> one<00:01:27.780> of<00:01:28.046> the<00:01:28.311> stories<00:01:28.577> that<00:01:28.843> I<00:01:29.109> really<00:01:29.374> liked<00:01:29.640> was<00:01:29.906> the<00:01:30.171> history<00:01:30.437> of<00:01:30.703> partnership<00:01:30.969> between<00:01:31.234> the<00:01:31.500> two<00:01:31.766> of<00:01:32.031> you<00:01:32.297> and<00:01:32.563> I<00:01:32.829> thought<00:01:33.094> we<00:01:33.360> could
00:01:33.600 --> 00:01:41.759
start<00:01:34.000> with<00:01:34.640> the<00:01:34.880> Department<00:01:35.200> of<00:01:35.360> Health<00:01:35.600> Services,<00:01:36.560> the<00:01:37.119> you<00:01:37.360> had<00:01:37.520> mentioned<00:01:37.759> the<00:01:38.079> EHR<00:01:38.479> and<00:01:38.720> I<00:01:38.880> thought<00:01:39.119> Peter,<00:01:39.439> you<00:01:39.600> could<00:01:39.840> take<00:01:40.000> us<00:01:40.240> back<00:01:41.040> to<00:01:41.360> was<00:01:41.600> that
00:01:41.759 --> 00:01:45.280
the<00:01:41.920> first<00:01:42.079> engagement<00:01:42.560> that<00:01:42.799> the<00:01:42.960> two<00:01:43.040> of<00:01:43.200> you<00:01:43.439> had<00:01:43.920> or<00:01:44.159> one<00:01:44.320> of<00:01:44.400> the<00:01:44.560> first<00:01:44.720> big<00:01:44.880> ones?
00:01:45.280 --> 00:01:48.079
The<00:01:45.439> first<00:01:45.680> big<00:01:45.840> ones.<00:01:46.320> Yeah.<00:01:46.720> Okay.<00:01:47.040> So,<00:01:47.360> take<00:01:47.520> us<00:01:47.680> back.
00:01:48.079 --> 00:01:51.600
How<00:01:48.240> many<00:01:48.399> years<00:01:48.479> ago<00:01:48.799> was<00:01:48.960> that?<00:01:49.520> Man,<00:01:50.000> I<00:01:50.240> started<00:01:50.479> in<00:01:50.799> 2009.
00:01:51.600 --> 00:01:54.399
I<00:01:51.840> don't<00:01:51.920> know<00:01:52.000> when<00:01:52.159> you<00:01:52.399> joined<00:01:52.720> the<00:01:52.880> county.<00:01:53.520> 2007.
00:01:54.399 --> 00:02:03.280
Okay.<00:01:54.757> Yeah.<00:01:55.116> I<00:01:55.474> rejoined<00:01:55.832> the<00:01:56.191> county<00:01:56.549> in<00:01:56.907> 2007.<00:01:57.265> I<00:01:57.624> think<00:01:57.982> it<00:01:58.340> was<00:01:58.699> around<00:01:59.057> 2010-11<00:01:59.415> time<00:01:59.774> period<00:02:00.132> was<00:02:00.490> when<00:02:00.848> DHS<00:02:01.207> was<00:02:01.565> implementing<00:02:01.923> their<00:02:02.282> their<00:02:02.640> EHR.
00:02:03.280 --> 00:02:06.240
So,<00:02:03.680> let<00:02:03.840> me<00:02:04.000> give<00:02:04.079> you<00:02:04.240> this<00:02:04.560> the<00:02:04.719> kind<00:02:04.880> of<00:02:04.960> a<00:02:05.040> little<00:02:05.119> bit<00:02:05.280> of<00:02:05.439> the<00:02:05.520> background<00:02:05.759> on<00:02:06.000> that.
00:02:06.240 --> 00:02:14.560
So<00:02:06.560> prior<00:02:07.119> to<00:02:07.520> they<00:02:07.759> had<00:02:07.920> a<00:02:08.080> new<00:02:08.160> CIO<00:02:08.640> come<00:02:08.800> in<00:02:09.039> at<00:02:09.200> the<00:02:09.360> Department<00:02:09.599> of<00:02:09.679> Health<00:02:09.920> Services<00:02:10.720> from<00:02:10.959> Florida<00:02:11.360> actually<00:02:11.680> and<00:02:12.000> joined<00:02:12.239> the<00:02:12.480> department<00:02:12.879> and<00:02:13.200> the<00:02:13.440> charge<00:02:13.840> was
00:02:14.560 --> 00:02:22.160
prior<00:02:14.879> to<00:02:15.040> his<00:02:15.280> arrival.<00:02:16.160> We<00:02:16.400> run<00:02:16.800> just<00:02:16.959> to<00:02:17.200> give<00:02:17.280> you<00:02:17.360> a<00:02:17.520> sense<00:02:17.760> the<00:02:17.920> county<00:02:18.239> Department<00:02:18.480> of<00:02:18.640> Health<00:02:18.879> Services<00:02:19.599> runs<00:02:20.000> five<00:02:20.319> hospitals<00:02:21.200> and<00:02:21.360> they<00:02:21.520> see<00:02:21.760> about<00:02:21.920> two<00:02:22.080> and
00:02:22.160 --> 00:02:28.720
a<00:02:22.319> half<00:02:22.480> million<00:02:22.800> clients<00:02:23.280> a<00:02:23.520> year.<00:02:23.920> They<00:02:24.239> also<00:02:24.560> run<00:02:24.879> a<00:02:25.120> long-term<00:02:26.000> rehab<00:02:26.480> center<00:02:27.120> out<00:02:27.760> of<00:02:27.840> Los<00:02:28.000> Amigos.
00:02:28.720 --> 00:02:35.840
And<00:02:28.879> so<00:02:29.360> every<00:02:29.599> one<00:02:29.760> of<00:02:29.920> those<00:02:30.080> five<00:02:30.400> hospitals<00:02:31.040> was<00:02:31.360> running<00:02:31.680> the<00:02:32.000> same<00:02:32.480> product<00:02:32.959> for<00:02:33.360> EHR<00:02:33.920> but<00:02:34.160> implemented<00:02:34.800> five<00:02:35.120> different<00:02:35.360> ways.
00:02:35.840 --> 00:02:43.920
As<00:02:36.080> a<00:02:36.239> department<00:02:36.640> it<00:02:36.879> was<00:02:37.040> very<00:02:37.360> difficult<00:02:37.680> and<00:02:37.920> so<00:02:38.080> when<00:02:38.319> this<00:02:38.480> new<00:02:38.720> CIO<00:02:39.120> came<00:02:39.280> on<00:02:39.440> board<00:02:39.760> there<00:02:39.920> was<00:02:40.000> a<00:02:40.239> need<00:02:40.400> to<00:02:41.040> really<00:02:41.519> replatform<00:02:42.319> the<00:02:42.640> EHR<00:02:43.200> because<00:02:43.440> of<00:02:43.599> all<00:02:43.760> the
00:02:43.920 --> 00:02:50.239
things<00:02:44.080> that<00:02:44.239> was<00:02:44.400> happening<00:02:44.720> with<00:02:44.879> the<00:02:45.120> healthcare<00:02:45.519> industry<00:02:46.239> right<00:02:46.560> with<00:02:46.720> affordable<00:02:47.280> healthcare<00:02:47.680> and<00:02:47.920> everything<00:02:48.160> else<00:02:48.400> there<00:02:48.560> was<00:02:48.640> a<00:02:48.800> big<00:02:48.959> push<00:02:49.440> and<00:02:49.840> need<00:02:50.000> to
00:02:50.239 --> 00:02:58.480
get<00:02:50.603> really<00:02:50.966> ramped<00:02:51.330> up<00:02:51.694> to<00:02:52.057> to<00:02:52.421> support<00:02:52.784> a<00:02:53.148> a<00:02:53.512> systemwide<00:02:53.875> view<00:02:54.239> um<00:02:54.603> of<00:02:54.966> things<00:02:55.330> and<00:02:55.694> they<00:02:56.057> partnered<00:02:56.421> with<00:02:56.784> uh<00:02:57.148> with<00:02:57.512> Hannes's<00:02:57.875> team<00:02:58.239> to
00:02:58.480 --> 00:03:05.360
begin<00:02:58.800> to<00:02:58.959> look<00:02:59.120> at<00:02:59.280> all<00:02:59.360> the<00:02:59.519> from<00:02:59.680> the<00:02:59.840> front<00:03:00.000> end<00:03:00.239> right<00:03:00.400> the<00:03:00.640> solicitation<00:03:01.440> the<00:03:01.680> requirements<00:03:02.239> analysis<00:03:02.959> and<00:03:03.200> putting<00:03:03.440> it<00:03:03.680> out<00:03:03.840> and<00:03:04.080> then<00:03:04.239> the<00:03:04.480> implementation<00:03:05.200> the
00:03:05.360 --> 00:03:14.239
EHR<00:03:05.680> And<00:03:05.840> there<00:03:06.080> was<00:03:06.159> this<00:03:06.480> big<00:03:06.800> need<00:03:07.360> for<00:03:07.680> a<00:03:08.159> industry<00:03:08.640> partner<00:03:09.120> to<00:03:09.360> work<00:03:09.599> with<00:03:09.920> DHS<00:03:10.560> because<00:03:10.800> it's<00:03:11.120> a<00:03:11.360> huge<00:03:11.920> implementation<00:03:12.720> as<00:03:12.879> you<00:03:13.040> can<00:03:13.200> imagine<00:03:13.760> across
00:03:14.239 --> 00:03:16.879
five<00:03:14.560> hospitals<00:03:14.959> and<00:03:15.120> that's<00:03:15.360> where<00:03:15.519> the<00:03:15.680> private<00:03:16.000> shift<00:03:16.239> came.
00:03:16.879 --> 00:03:25.120
So<00:03:17.280> Hannes<00:03:17.760> take<00:03:17.920> take<00:03:18.159> us<00:03:18.319> back<00:03:18.560> there<00:03:19.120> to<00:03:19.519> 2007<00:03:20.159> when<00:03:20.319> I<00:03:20.480> graduated<00:03:20.959> high<00:03:21.120> school<00:03:23.280> uh<00:03:23.840> and<00:03:24.080> didn't<00:03:24.480> know<00:03:24.640> what<00:03:24.879> a
00:03:25.120 --> 00:03:29.920
database<00:03:25.680> or<00:03:26.000> anything<00:03:26.319> was<00:03:26.720> or<00:03:26.959> an<00:03:27.120> EHR<00:03:27.760> any<00:03:28.159> any<00:03:28.319> of<00:03:28.400> that<00:03:28.560> was<00:03:28.800> back<00:03:28.959> in<00:03:29.120> 2007.
00:03:29.920 --> 00:03:32.080
Take<00:03:30.159> us<00:03:30.319> back<00:03:30.480> there<00:03:30.799> like<00:03:31.040> the<00:03:31.280> early<00:03:31.519> stages.
00:03:32.080 --> 00:03:40.400
The<00:03:32.319> very<00:03:32.560> early<00:03:32.879> stages<00:03:33.760> was<00:03:34.480> the<00:03:34.799> desire<00:03:35.200> to<00:03:35.840> make<00:03:36.080> something<00:03:36.400> big<00:03:36.720> happen<00:03:37.040> and<00:03:37.280> to<00:03:37.440> get<00:03:37.519> to<00:03:37.680> an<00:03:37.920> enterprise<00:03:38.319> EHR<00:03:38.879> solution<00:03:39.760> and<00:03:40.080> the
00:03:40.400 --> 00:03:44.879
sentiment<00:03:40.959> that<00:03:41.360> was<00:03:41.519> prevailing<00:03:42.080> was<00:03:42.560> that<00:03:42.959> it<00:03:43.200> had<00:03:43.360> never<00:03:43.519> been<00:03:43.760> done<00:03:43.920> before.
00:03:44.879 --> 00:03:47.599
There<00:03:45.040> was<00:03:45.120> a<00:03:45.280> history<00:03:45.599> of<00:03:45.920> not<00:03:46.159> being<00:03:46.400> successful.
00:03:47.599 --> 00:03:54.159
There<00:03:47.840> was<00:03:48.319> the<00:03:48.799> still<00:03:49.040> the<00:03:49.280> looming<00:03:49.680> shadow<00:03:50.000> of<00:03:50.239> a<00:03:50.400> pretty<00:03:50.720> bad<00:03:51.040> implementation<00:03:51.680> that<00:03:52.000> happened<00:03:52.400> even<00:03:52.720> 10<00:03:52.959> years<00:03:53.280> prior.
00:03:54.159 --> 00:03:58.239
And<00:03:54.319> so<00:03:54.560> there<00:03:54.799> were<00:03:55.040> not<00:03:55.280> many<00:03:55.599> believers<00:03:56.239> in<00:03:56.799> this<00:03:57.040> even<00:03:57.280> being<00:03:57.599> possible.
00:03:58.239 --> 00:04:07.200
And<00:03:58.480> I<00:03:58.720> think<00:03:59.360> what<00:03:59.760> happened<00:04:00.159> is<00:04:00.480> that<00:04:01.200> a<00:04:01.439> a<00:04:01.920> small<00:04:02.319> group<00:04:02.640> of<00:04:03.200> true<00:04:03.519> executive<00:04:04.000> leaders<00:04:04.480> in<00:04:04.720> the<00:04:04.879> county<00:04:05.360> with<00:04:05.599> industry<00:04:06.080> partners<00:04:06.959> said,
00:04:07.200 --> 00:04:15.680
"No,<00:04:07.519> we're<00:04:07.680> going<00:04:07.840> to<00:04:07.920> make<00:04:08.080> this<00:04:08.319> happen."<00:04:08.799> And<00:04:09.040> we<00:04:09.360> got<00:04:09.519> together<00:04:10.239> and<00:04:11.120> committed<00:04:11.599> ourselves<00:04:12.239> to<00:04:12.480> the<00:04:12.720> cause<00:04:13.360> and<00:04:13.760> as<00:04:14.000> a<00:04:14.239> result<00:04:14.720> developed<00:04:15.360> a
00:04:15.680 --> 00:04:20.639
relationship<00:04:16.400> and<00:04:16.639> a<00:04:16.880> governance<00:04:17.280> model<00:04:17.919> that<00:04:18.479> kept<00:04:18.880> the<00:04:19.519> ball<00:04:19.919> moving.
00:04:20.639 --> 00:04:25.040
And<00:04:20.799> whenever<00:04:21.120> we<00:04:21.359> hit<00:04:21.600> the<00:04:21.759> snag,<00:04:22.240> we<00:04:22.479> found<00:04:22.720> a<00:04:22.960> solution<00:04:23.360> so<00:04:23.600> we<00:04:23.840> could<00:04:24.080> continue.
00:04:25.040 --> 00:04:33.680
And<00:04:25.280> that<00:04:25.600> was<00:04:25.840> a<00:04:26.160> mindset<00:04:26.720> that<00:04:26.960> that<00:04:27.280> we<00:04:27.520> put<00:04:27.680> in<00:04:27.840> place<00:04:28.080> very<00:04:28.400> early<00:04:28.720> on<00:04:28.880> at<00:04:29.120> the<00:04:29.360> strategy<00:04:29.759> part<00:04:30.240> and<00:04:30.400> then<00:04:30.639> continued<00:04:31.120> all<00:04:31.360> the<00:04:31.520> way<00:04:31.680> through<00:04:32.080> the<00:04:32.400> implementation
00:04:33.680 --> 00:04:38.320
five<00:04:33.919> or<00:04:34.080> six<00:04:34.320> years<00:04:34.560> later<00:04:34.960> which<00:04:35.280> by<00:04:35.440> the<00:04:35.520> way<00:04:35.919> happened<00:04:36.400> on<00:04:36.720> schedule<00:04:37.120> and<00:04:37.440> within<00:04:37.759> budget.
00:04:38.320 --> 00:04:44.639
So<00:04:38.639> okay<00:04:38.880> so<00:04:39.040> you<00:04:39.199> said<00:04:39.360> a<00:04:39.440> couple<00:04:39.600> things<00:04:39.680> that<00:04:39.919> were<00:04:40.080> really<00:04:40.240> great<00:04:41.199> executive<00:04:42.080> leadership<00:04:42.880> committed<00:04:43.280> to<00:04:43.440> the<00:04:43.600> cause.
00:04:44.639 --> 00:04:51.440
Talk<00:04:44.959> about<00:04:45.279> the<00:04:45.599> lessons<00:04:45.919> of<00:04:46.239> getting<00:04:46.559> buy-in<00:04:46.879> because<00:04:47.199> I<00:04:47.519> think<00:04:47.840> to<00:04:48.160> be<00:04:48.480> really<00:04:48.800> effective<00:04:49.120> in<00:04:49.440> public<00:04:49.760> sector<00:04:50.080> you<00:04:50.400> need<00:04:50.720> buy-in.
00:04:51.440 --> 00:04:56.320
You<00:04:51.680> need<00:04:51.919> leaders<00:04:52.960> who<00:04:53.600> believe<00:04:54.080> you<00:04:54.320> need<00:04:54.479> to<00:04:55.120> you're<00:04:55.360> going<00:04:55.440> to<00:04:55.520> hit<00:04:55.759> snag.
00:04:56.320 --> 00:05:02.000
Talk<00:04:56.479> about<00:04:56.720> how<00:04:57.360> you<00:04:57.919> were<00:04:58.160> able<00:04:58.400> to<00:04:58.960> build<00:04:59.199> those<00:04:59.440> relationships<00:05:00.080> across<00:05:00.800> so<00:05:01.040> many<00:05:01.199> different<00:05:01.440> silos.
00:05:02.000 --> 00:05:06.000
I<00:05:02.160> think<00:05:02.400> what<00:05:02.639> really<00:05:03.040> because<00:05:03.360> it<00:05:03.520> it<00:05:03.759> starts<00:05:03.919> with<00:05:04.000> the<00:05:04.240> governance<00:05:04.639> and<00:05:04.720> that<00:05:04.880> steering<00:05:05.280> committee,<00:05:05.759> right?
00:05:06.000 --> 00:05:13.199
And<00:05:06.240> having<00:05:06.479> the<00:05:06.720> right<00:05:07.199> business<00:05:07.680> leadership<00:05:08.479> in<00:05:08.800> each<00:05:08.960> of<00:05:09.039> the<00:05:09.199> areas<00:05:09.919> of<00:05:10.080> and<00:05:10.320> each<00:05:10.560> of<00:05:10.639> the<00:05:10.800> hospitals<00:05:11.520> being<00:05:11.840> on<00:05:12.080> that<00:05:12.320> group,<00:05:12.720> right?
00:05:13.199 --> 00:05:21.120
So<00:05:13.600> that<00:05:13.840> partnership<00:05:14.320> really<00:05:14.560> worked<00:05:14.800> out<00:05:14.960> because<00:05:15.199> the<00:05:15.440> steering<00:05:15.759> committee<00:05:16.160> recognized<00:05:16.639> the<00:05:16.960> mandate<00:05:17.520> right<00:05:17.840> in<00:05:18.000> the<00:05:18.160> mission<00:05:18.479> to<00:05:18.720> really<00:05:19.039> have<00:05:19.520> this<00:05:19.840> single<00:05:20.639> platform
00:05:21.120 --> 00:05:23.919
that<00:05:21.360> needs<00:05:21.600> to<00:05:21.680> be<00:05:21.840> implemented<00:05:22.400> across<00:05:22.800> these<00:05:23.039> five<00:05:23.360> hospitals.
00:05:23.919 --> 00:05:31.520
That<00:05:24.160> was<00:05:24.240> the<00:05:24.400> vision<00:05:24.639> that<00:05:24.880> really<00:05:25.120> kept<00:05:25.440> that<00:05:25.600> true<00:05:25.759> north<00:05:26.160> if<00:05:26.240> you<00:05:26.400> will<00:05:26.720> right<00:05:26.960> the<00:05:27.120> northstar<00:05:27.840> and<00:05:28.080> so<00:05:28.240> using<00:05:28.560> that<00:05:28.800> as<00:05:28.960> a<00:05:29.199> northstar<00:05:30.000> as<00:05:30.240> Hannes<00:05:30.639> was<00:05:30.880> recounting
00:05:31.520 --> 00:05:37.840
as<00:05:31.680> we<00:05:31.840> went<00:05:32.080> through<00:05:32.320> this<00:05:32.639> project<00:05:32.880> and<00:05:33.039> as<00:05:33.199> we<00:05:33.440> encountered<00:05:33.919> implementation<00:05:34.560> issues<00:05:34.960> and<00:05:35.199> everything<00:05:35.440> else<00:05:35.840> we<00:05:36.080> always<00:05:36.320> focus<00:05:36.639> back<00:05:36.800> on<00:05:37.039> this<00:05:37.199> is<00:05:37.280> the<00:05:37.440> mission<00:05:37.680> it's
00:05:37.840 --> 00:05:44.400
not<00:05:38.000> a<00:05:38.160> question<00:05:38.320> of<00:05:38.560> whether<00:05:38.800> we're<00:05:38.960> going<00:05:39.039> to<00:05:39.120> change<00:05:39.280> the<00:05:39.520> mission<00:05:39.919> but<00:05:40.160> how<00:05:40.320> do<00:05:40.479> we<00:05:40.639> get<00:05:40.800> there<00:05:41.199> right<00:05:41.360> and<00:05:41.600> how<00:05:41.759> do<00:05:41.919> we<00:05:42.080> do<00:05:42.160> that<00:05:42.639> so<00:05:43.120> it<00:05:43.360> was<00:05:43.600> part<00:05:43.840> of<00:05:43.919> the<00:05:44.160> change
00:05:44.400 --> 00:05:51.120
management<00:05:44.800> was<00:05:45.039> that<00:05:45.199> this<00:05:45.440> is<00:05:45.600> going<00:05:45.680> to<00:05:45.840> happen<00:05:46.400> we<00:05:46.560> are<00:05:46.720> going<00:05:46.800> to<00:05:46.960> work<00:05:47.120> with<00:05:47.280> you<00:05:47.600> on<00:05:47.759> the<00:05:48.000> ground<00:05:48.400> on<00:05:48.720> how<00:05:48.960> to<00:05:49.199> ultimately<00:05:49.680> make<00:05:49.840> that<00:05:50.000> happen<00:05:50.240> so<00:05:50.479> it's<00:05:50.639> not<00:05:50.800> a<00:05:50.960> question
00:05:51.120 --> 00:05:56.960
of<00:05:51.360> if<00:05:51.759> right<00:05:51.919> and<00:05:52.080> that<00:05:52.320> was<00:05:52.400> a<00:05:52.560> really<00:05:52.960> important<00:05:53.600> point<00:05:53.919> to<00:05:54.160> make<00:05:54.400> because<00:05:54.800> there<00:05:55.120> was<00:05:55.280> no<00:05:55.840> there<00:05:56.000> was<00:05:56.160> no<00:05:56.320> other<00:05:56.479> option.
00:05:56.960 --> 00:06:04.319
It's<00:05:57.199> a<00:05:57.360> matter<00:05:57.520> of<00:05:57.759> how<00:05:58.000> do<00:05:58.160> we<00:05:58.320> work<00:05:58.560> together<00:05:59.280> and<00:05:59.520> resolve<00:06:00.000> some<00:06:00.240> of<00:06:00.320> these<00:06:00.639> differences<00:06:01.199> between<00:06:01.520> how<00:06:02.000> things<00:06:02.320> are<00:06:02.479> done<00:06:02.639> at<00:06:02.880> the<00:06:03.039> different<00:06:03.360> hospitals<00:06:03.919> and<00:06:04.160> so
00:06:04.319 --> 00:06:10.720
that<00:06:04.479> we<00:06:04.639> can<00:06:04.720> come<00:06:04.880> up<00:06:04.960> with<00:06:05.039> a<00:06:05.199> common<00:06:05.440> set<00:06:05.759> of<00:06:05.919> processes<00:06:06.400> and<00:06:06.639> procedures<00:06:07.360> as<00:06:07.680> a<00:06:08.160> department<00:06:08.960> across<00:06:09.280> these<00:06:09.600> five<00:06:09.759> hospitals<00:06:10.160> to<00:06:10.400> do<00:06:10.560> it.
00:06:10.720 --> 00:06:18.960
So<00:06:10.880> that<00:06:11.039> was<00:06:11.120> a<00:06:11.360> very<00:06:11.600> important<00:06:11.840> part<00:06:12.080> of<00:06:12.400> of<00:06:12.639> how<00:06:13.199> this<00:06:13.520> buy-in<00:06:14.240> needs<00:06:14.560> to<00:06:14.720> happen<00:06:15.120> because<00:06:15.759> the<00:06:16.000> of<00:06:16.160> the<00:06:16.319> direction<00:06:16.720> that<00:06:17.120> it's<00:06:17.360> top<00:06:17.680> down<00:06:18.160> has<00:06:18.319> to<00:06:18.479> happen<00:06:18.800> now
00:06:18.960 --> 00:06:21.600
we're<00:06:19.114> going<00:06:19.269> to<00:06:19.423> try<00:06:19.577> to<00:06:19.731> get<00:06:19.886> a<00:06:20.040> buy-in<00:06:20.194> and<00:06:20.349> how<00:06:20.503> do<00:06:20.657> we<00:06:20.811> make<00:06:20.966> this<00:06:21.120> happen?
00:06:21.600 --> 00:06:24.560
So<00:06:21.840> everything<00:06:22.160> you<00:06:22.400> said<00:06:23.120> there<00:06:23.440> technology<00:06:24.000> matters.
00:06:24.560 --> 00:06:31.199
I<00:06:24.720> always<00:06:25.120> people<00:06:25.440> were<00:06:25.520> like<00:06:25.680> Joe<00:06:25.919> you<00:06:26.080> always<00:06:26.240> say<00:06:26.400> technology<00:06:27.039> the<00:06:27.199> tech<00:06:27.520> the<00:06:27.759> technology<00:06:28.240> matters<00:06:28.639> but<00:06:29.199> there's<00:06:29.440> a<00:06:29.600> lot<00:06:29.680> of<00:06:29.840> well<00:06:30.000> you<00:06:30.080> said<00:06:30.319> change<00:06:30.560> management.
00:06:31.199 --> 00:06:34.400
Yes.<00:06:31.680> Governance.<00:06:32.479> Yes.<00:06:32.800> These<00:06:33.039> are<00:06:33.199> not<00:06:33.360> technology<00:06:33.840> issues.
00:06:34.400 --> 00:06:36.880
Correct.<00:06:34.720> Fundamentally<00:06:35.120> they're<00:06:35.440> human<00:06:35.680> issues.<00:06:36.479> Right.
00:06:36.880 --> 00:06:39.360
And<00:06:37.184> getting<00:06:37.488> the<00:06:37.792> teams<00:06:38.096> to<00:06:38.400> buy-in.
00:06:39.360 --> 00:06:46.800
And<00:06:39.759> I<00:06:40.000> love<00:06:40.160> that<00:06:40.400> you<00:06:40.639> said<00:06:40.800> you<00:06:41.039> keep<00:06:41.120> the<00:06:41.280> mission<00:06:41.520> in<00:06:41.680> front<00:06:41.759> of<00:06:41.919> us<00:06:42.720> and<00:06:43.280> it's<00:06:43.600> not<00:06:43.680> a<00:06:43.919> question<00:06:44.720> of<00:06:44.960> if<00:06:45.600> we're<00:06:45.840> going<00:06:45.919> to<00:06:46.000> get<00:06:46.160> there.
00:06:46.800 --> 00:06:53.919
And<00:06:47.039> it<00:06:47.199> kind<00:06:47.360> of<00:06:47.440> makes<00:06:47.600> me<00:06:47.759> think<00:06:47.840> of<00:06:48.240> back<00:06:48.479> in<00:06:48.560> the<00:06:48.639> day<00:06:48.880> Jeff<00:06:49.120> Bezos<00:06:49.600> when<00:06:49.759> he<00:06:49.919> was<00:06:50.000> running<00:06:50.240> Amazon<00:06:50.720> would<00:06:50.960> have<00:06:51.039> an<00:06:51.280> empty<00:06:51.600> chair<00:06:52.080> kind<00:06:52.240> of<00:06:52.720> to<00:06:53.120> remind<00:06:53.600> everybody
00:06:53.919 --> 00:07:00.319
of<00:06:54.080> the<00:06:54.319> end<00:06:54.639> customer.<00:06:55.280> And<00:06:55.440> I<00:06:55.680> just<00:06:55.840> love<00:06:56.080> that<00:06:56.319> cuz<00:06:56.800> the<00:06:57.039> end<00:06:57.280> customer<00:06:57.840> were<00:06:58.080> serving<00:06:58.960> people<00:06:59.120> who<00:06:59.360> are<00:06:59.440> coming<00:06:59.599> to<00:06:59.759> the<00:06:59.919> hospital.
00:07:00.319 --> 00:07:05.280
My<00:07:00.639> very<00:07:00.880> first<00:07:01.039> professional<00:07:01.599> job<00:07:02.000> was<00:07:02.400> a<00:07:02.639> technical<00:07:03.039> account<00:07:03.360> manager<00:07:04.000> at<00:07:04.319> Yardi<00:07:04.800> Systems.
00:07:05.280 --> 00:07:09.280
And<00:07:05.520> I<00:07:05.680> did<00:07:05.759> not<00:07:05.919> know<00:07:06.160> anything.<00:07:06.800> The<00:07:06.960> first<00:07:07.039> day<00:07:07.199> I<00:07:07.360> walk<00:07:07.520> in,<00:07:07.680> they're<00:07:07.919> talking<00:07:08.000> to<00:07:08.160> me<00:07:08.240> about<00:07:08.639> SQL.
00:07:09.280 --> 00:07:13.840
I<00:07:09.360> don't<00:07:09.440> even<00:07:09.599> know<00:07:09.680> if<00:07:09.840> I<00:07:10.000> could<00:07:10.080> spell<00:07:10.319> it.<00:07:11.120> And<00:07:11.280> they<00:07:11.599> sent<00:07:11.680> me<00:07:11.840> to<00:07:11.919> San<00:07:12.160> Francisco<00:07:12.560> and<00:07:12.800> I<00:07:12.960> did<00:07:13.039> some<00:07:13.199> coding<00:07:13.520> classes.
00:07:13.840 --> 00:07:15.759
And<00:07:14.080> then<00:07:14.240> soon<00:07:14.720> I<00:07:14.880> was<00:07:14.960> like,<00:07:15.039> "What's<00:07:15.360> kind<00:07:15.440> of<00:07:15.520> cool?
00:07:15.759 --> 00:07:18.319
I'm<00:07:15.919> dropping<00:07:16.080> these<00:07:16.240> SQL<00:07:16.560> packages<00:07:16.880> in.<00:07:17.199> I'm<00:07:17.360> updating<00:07:17.919> everything.
00:07:18.319 --> 00:07:23.440
And<00:07:18.479> then<00:07:18.639> the<00:07:18.800> next<00:07:18.960> thing<00:07:19.120> my<00:07:19.280> boss<00:07:19.599> said,<00:07:20.160> he<00:07:20.400> was<00:07:20.479> really<00:07:20.639> great,<00:07:20.960> okay,<00:07:21.120> you're<00:07:21.199> going<00:07:21.280> to<00:07:21.360> go<00:07:21.440> on<00:07:21.599> site<00:07:21.759> and<00:07:21.840> you're<00:07:22.080> actually<00:07:22.240> going<00:07:22.400> to<00:07:22.560> learn<00:07:22.880> that<00:07:23.120> there<00:07:23.280> are
00:07:23.440 --> 00:07:30.880
people<00:07:23.919> behind<00:07:24.479> all<00:07:24.720> of<00:07:24.800> this.<00:07:25.199> And<00:07:25.360> and<00:07:25.840> that<00:07:26.000> was<00:07:26.080> a<00:07:26.319> really<00:07:26.479> fascinating<00:07:26.960> lesson<00:07:27.280> of<00:07:27.680> actually<00:07:27.919> going<00:07:28.080> on<00:07:28.319> site<00:07:28.479> and<00:07:28.639> implementing<00:07:29.039> the<00:07:29.280> software<00:07:29.680> and<00:07:30.000> understanding,
00:07:30.880 --> 00:07:32.960
oh,<00:07:31.599> this<00:07:31.840> is<00:07:31.919> not<00:07:32.080> a<00:07:32.240> software<00:07:32.560> issue.
00:07:32.960 --> 00:07:36.560
Actually,<00:07:33.280> the<00:07:33.520> executive<00:07:34.000> team<00:07:34.160> over<00:07:34.479> here<00:07:34.720> is<00:07:34.960> disconnected<00:07:35.520> from<00:07:35.680> the<00:07:35.840> end<00:07:36.000> users.
00:07:36.560 --> 00:07:41.360
It<00:07:36.720> was<00:07:36.800> a<00:07:37.039> really<00:07:37.199> important<00:07:37.520> lesson<00:07:37.840> I<00:07:38.319> always<00:07:38.639> remembered<00:07:39.360> that<00:07:40.000> I<00:07:40.240> was<00:07:40.400> very<00:07:40.639> curious.
00:07:41.360 --> 00:07:50.000
Takes<00:07:41.680> us<00:07:42.000> to<00:07:42.400> today<00:07:43.120> when<00:07:43.360> you<00:07:43.599> talked<00:07:43.840> about<00:07:44.400> the<00:07:44.639> steering<00:07:45.039> committees<00:07:45.840> here<00:07:46.000> we<00:07:46.160> are<00:07:46.240> in<00:07:46.400> the<00:07:46.560> age<00:07:46.720> of<00:07:46.800> AI<00:07:47.520> right<00:07:48.160> and<00:07:48.479> same<00:07:48.720> thing<00:07:49.199> what<00:07:49.520> lessons
00:07:50.000 --> 00:07:58.800
would<00:07:50.240> you<00:07:50.479> give<00:07:50.880> to<00:07:51.520> other<00:07:51.919> CIOs<00:07:52.479> around<00:07:52.720> the<00:07:52.880> country<00:07:53.280> and<00:07:53.759> making<00:07:54.560> this<00:07:54.879> actually<00:07:55.360> effective<00:07:56.000> I<00:07:56.240> think<00:07:56.319> what<00:07:56.560> also<00:07:57.199> made<00:07:57.440> this<00:07:57.919> effective<00:07:58.400> was
00:07:58.800 --> 00:08:06.800
it<00:07:59.039> was<00:07:59.120> it<00:07:59.360> started<00:07:59.599> with<00:07:59.759> the<00:07:59.919> leadership<00:08:00.560> right<00:08:00.720> the<00:08:01.039> leadership<00:08:01.599> and<00:08:01.840> the<00:08:02.160> technologist<00:08:03.120> were<00:08:03.520> off<00:08:03.759> step<00:08:04.080> techn<00:08:04.479> it<00:08:04.720> wasn't<00:08:04.879> the<00:08:05.120> technologies<00:08:05.759> driving<00:08:06.080> the<00:08:06.319> technology
00:08:06.800 --> 00:08:15.280
and<00:08:07.039> implementation<00:08:07.680> it<00:08:07.919> was<00:08:08.319> this<00:08:08.479> is<00:08:08.560> a<00:08:08.800> business<00:08:09.039> imperative<00:08:09.759> and<00:08:09.919> this<00:08:10.080> is<00:08:10.240> how<00:08:10.560> technology<00:08:10.879> technology<00:08:11.680> is<00:08:12.000> required<00:08:12.400> to<00:08:12.639> enable<00:08:13.039> us<00:08:13.360> to<00:08:13.680> get<00:08:13.840> and<00:08:14.080> meet<00:08:14.319> that<00:08:14.560> imperative.
00:08:15.280 --> 00:08:17.199
Right?<00:08:15.680> So<00:08:15.840> that<00:08:16.080> message<00:08:16.400> was<00:08:16.639> very<00:08:16.879> clear.
00:08:17.199 --> 00:08:22.240
The<00:08:17.360> the<00:08:17.599> other<00:08:17.759> thing<00:08:17.919> I<00:08:18.160> think<00:08:18.240> that<00:08:18.479> was<00:08:18.639> also<00:08:18.879> very<00:08:19.199> important<00:08:19.599> is<00:08:19.840> that<00:08:20.240> the<00:08:20.479> steering<00:08:20.800> committee<00:08:21.120> was<00:08:21.360> empowered.
00:08:22.240 --> 00:08:24.879
Right?<00:08:22.479> So<00:08:22.639> they<00:08:22.879> were<00:08:23.039> just<00:08:23.199> not<00:08:23.280> a<00:08:23.520> steering<00:08:23.840> committee<00:08:24.160> to<00:08:24.319> steer<00:08:24.639> things.
00:08:24.879 --> 00:08:30.240
They<00:08:25.039> were<00:08:25.199> also<00:08:25.440> required<00:08:26.000> and<00:08:26.240> were<00:08:26.479> empowered<00:08:27.199> to<00:08:27.520> facilitate<00:08:28.400> and<00:08:28.720> to<00:08:28.879> drive<00:08:29.199> the<00:08:29.440> implementation.
00:08:30.240 --> 00:08:35.039
Right?<00:08:30.544> And<00:08:30.848> that's<00:08:31.152> part<00:08:31.456> of<00:08:31.760> building<00:08:32.064> out<00:08:32.368> that<00:08:32.672> buy-in<00:08:32.976> and<00:08:33.280> that<00:08:33.584> ownership<00:08:33.888> you're<00:08:34.192> talking<00:08:34.496> about,<00:08:34.800> right?
00:08:35.039 --> 00:08:41.680
Because<00:08:35.200> they're<00:08:35.440> at<00:08:35.599> a<00:08:35.839> table.<00:08:36.479> They're<00:08:36.719> helping<00:08:37.039> solve<00:08:37.279> these<00:08:37.680> differences<00:08:38.159> and<00:08:38.399> issues<00:08:38.959> and<00:08:39.200> now<00:08:39.360> they're<00:08:39.760> also<00:08:40.000> owning<00:08:40.320> it<00:08:40.560> and<00:08:40.800> helping<00:08:41.120> drive<00:08:41.360> that.
00:08:41.680 --> 00:08:47.440
That<00:08:41.839> is<00:08:42.080> so<00:08:42.399> important,<00:08:43.039> right?<00:08:43.440> Many<00:08:43.919> some<00:08:44.080> of<00:08:44.159> the<00:08:44.320> committees<00:08:44.560> I've<00:08:44.880> attended<00:08:45.360> is<00:08:45.519> this<00:08:45.680> committee<00:08:45.920> for<00:08:46.160> committee<00:08:46.480> sake,<00:08:46.880> right?
00:08:47.440 --> 00:08:54.720
But<00:08:47.600> this<00:08:47.760> was<00:08:47.920> really<00:08:48.160> an<00:08:48.480> empowered<00:08:49.040> steering<00:08:49.440> committee<00:08:49.760> with<00:08:50.000> the<00:08:50.160> right<00:08:50.399> leaders<00:08:51.120> that<00:08:51.360> were<00:08:51.680> actually<00:08:52.000> part<00:08:52.240> of<00:08:52.320> the<00:08:52.560> solutioning<00:08:53.279> and<00:08:53.519> then<00:08:53.760> also<00:08:54.080> driving<00:08:54.480> the
00:08:54.720 --> 00:09:03.360
change,<00:08:55.200> right?<00:08:55.519> Not<00:08:55.680> just<00:08:55.920> the<00:08:56.160> technology,<00:08:56.640> the<00:08:56.880> adoption<00:08:57.279> of<00:08:57.440> the<00:08:57.680> technology<00:08:58.560> along<00:08:58.800> with<00:08:59.040> the<00:08:59.279> organizational<00:09:00.080> change<00:09:00.320> that's<00:09:00.640> required<00:09:01.040> for<00:09:01.360> successful<00:09:01.839> implementation.
00:09:03.360 --> 00:09:06.640
He<00:09:03.600> nailed<00:09:03.839> it<00:09:04.000> right<00:09:04.240> there.<00:09:04.480> Sorry.<00:09:06.240> Yeah.
00:09:06.640 --> 00:09:14.800
So<00:09:06.800> we<00:09:07.040> had<00:09:07.120> a<00:09:07.279> guiding<00:09:07.680> principle<00:09:08.480> that<00:09:08.720> we<00:09:08.959> would<00:09:09.120> move<00:09:09.279> the<00:09:09.519> decisions<00:09:10.320> as<00:09:10.640> far<00:09:10.880> down<00:09:11.120> in<00:09:11.360> the<00:09:11.519> organizations<00:09:12.160> as<00:09:12.399> we<00:09:12.640> could<00:09:13.200> so<00:09:13.360> that<00:09:13.680> the<00:09:13.920> decisions<00:09:14.240> would<00:09:14.480> be<00:09:14.560> made
00:09:14.800 --> 00:09:18.080
by<00:09:14.959> the<00:09:15.200> people<00:09:15.360> who<00:09:15.600> actually<00:09:15.920> use<00:09:16.160> the<00:09:16.399> system<00:09:16.640> or<00:09:16.880> provide<00:09:17.120> the<00:09:17.360> patient<00:09:17.680> care.
00:09:18.080 --> 00:09:20.800
And<00:09:18.240> I<00:09:18.399> think<00:09:18.480> to<00:09:18.720> me<00:09:18.880> that's<00:09:19.120> another<00:09:19.440> parallel<00:09:19.920> to<00:09:20.160> AI.
00:09:20.800 --> 00:09:22.880
We<00:09:21.040> can't<00:09:21.440> dictate<00:09:21.920> this<00:09:22.240> topic,<00:09:22.640> right?
00:09:22.880 --> 00:09:30.640
We<00:09:23.040> need<00:09:23.120> to<00:09:23.279> create<00:09:23.519> a<00:09:23.760> structure<00:09:24.080> in<00:09:24.240> a<00:09:24.480> system<00:09:24.800> where<00:09:25.040> the<00:09:25.279> people<00:09:25.440> who<00:09:25.680> actually<00:09:26.000> do<00:09:26.160> the<00:09:26.399> work<00:09:26.640> can<00:09:26.959> figure<00:09:27.200> out<00:09:27.440> how<00:09:27.680> they<00:09:27.920> can<00:09:28.080> best<00:09:28.320> leverage<00:09:29.200> these<00:09:29.519> new<00:09:29.760> technologies.
00:09:30.640 --> 00:09:37.920
And<00:09:30.800> so<00:09:31.040> those<00:09:31.360> are<00:09:31.440> perils.<00:09:31.839> Is<00:09:32.000> the<00:09:32.240> empowerment<00:09:32.959> and<00:09:33.279> then<00:09:33.519> providing<00:09:34.000> the<00:09:34.160> the<00:09:34.320> the<00:09:34.880> guidelines<00:09:35.440> and<00:09:35.680> the<00:09:35.920> direction<00:09:36.320> and<00:09:36.640> make<00:09:36.800> sure<00:09:36.880> it's<00:09:37.200> safe,<00:09:37.600> right?
00:09:37.920 --> 00:09:46.560
So<00:09:38.349> the<00:09:38.779> reason<00:09:39.208> I<00:09:39.638> really<00:09:40.067> like<00:09:40.497> this<00:09:40.926> topic<00:09:41.356> a<00:09:41.785> lot<00:09:42.215> was<00:09:42.644> so<00:09:43.074> when<00:09:43.503> I<00:09:43.933> hear<00:09:44.362> empowerment<00:09:44.792> I<00:09:45.221> think<00:09:45.651> resources<00:09:46.080> like
00:09:46.560 --> 00:09:54.000
I<00:09:46.880> can't<00:09:47.440> assign<00:09:47.760> my<00:09:48.080> wife<00:09:48.240> a<00:09:48.480> task<00:09:48.800> and<00:09:49.040> not<00:09:49.200> give<00:09:49.360> her<00:09:49.600> the<00:09:49.839> appropriate<00:09:50.560> tools,<00:09:51.360> money,<00:09:51.760> whatever<00:09:52.000> it<00:09:52.160> is<00:09:52.240> that<00:09:52.399> she<00:09:52.560> needs<00:09:52.800> to<00:09:52.959> actually<00:09:53.200> do<00:09:53.360> the<00:09:53.519> task.
00:09:54.000 --> 00:10:02.080
But<00:09:54.160> I<00:09:54.320> was<00:09:54.399> thinking<00:09:54.640> in<00:09:54.880> the<00:09:54.959> age<00:09:55.120> of<00:09:55.279> AI<00:09:55.600> and<00:09:55.839> I<00:09:56.000> talked<00:09:56.160> to<00:09:56.240> a<00:09:56.399> lot<00:09:56.480> of<00:09:56.640> CIOs<00:09:57.680> where<00:09:58.240> AI<00:09:58.640> came<00:09:58.880> out<00:09:59.120> first<00:09:59.440> and<00:09:59.600> then<00:09:59.839> there<00:10:00.000> was<00:10:00.080> a<00:10:00.320> rush<00:10:00.560> for<00:10:00.880> what<00:10:01.040> we'll<00:10:01.279> call<00:10:01.600> governance
00:10:02.080 --> 00:10:09.760
one<00:10:02.320> and<00:10:02.560> then<00:10:02.800> behind<00:10:03.040> the<00:10:03.200> scenes<00:10:03.360> I<00:10:03.600> was<00:10:03.680> talking<00:10:03.920> I<00:10:04.160> was<00:10:04.240> like<00:10:04.640> so<00:10:04.800> do<00:10:04.959> you<00:10:05.120> use<00:10:05.360> anything<00:10:07.040> and<00:10:07.200> this<00:10:07.360> is<00:10:07.519> maybe<00:10:07.760> two<00:10:08.000> years<00:10:08.080> ago<00:10:08.320> at<00:10:08.480> this<00:10:08.640> point<00:10:08.959> or<00:10:09.200> 18<00:10:09.519> months
00:10:09.760 --> 00:10:17.279
ago<00:10:10.320> and<00:10:10.640> behind<00:10:10.880> the<00:10:11.040> scenes<00:10:11.279> I<00:10:11.440> was<00:10:11.519> like<00:10:11.760> it<00:10:12.000> almost<00:10:12.160> seems<00:10:12.399> like<00:10:12.480> you<00:10:12.720> need<00:10:12.880> more<00:10:13.279> of<00:10:13.760> guidelines<00:10:14.640> before<00:10:14.959> the<00:10:15.200> rush<00:10:15.440> to<00:10:15.600> governance<00:10:16.079> but<00:10:16.160> I<00:10:16.399> understood<00:10:16.720> the<00:10:16.880> dynamic
00:10:17.279 --> 00:10:23.839
because<00:10:17.519> I<00:10:17.760> said<00:10:18.079> hey<00:10:18.320> your<00:10:18.560> boss<00:10:19.200> they're<00:10:19.519> asking<00:10:19.839> you<00:10:20.079> right<00:10:20.240> now<00:10:20.480> right<00:10:20.640> and<00:10:20.800> they're<00:10:20.959> like<00:10:21.200> yeah<00:10:21.360> the<00:10:21.519> city<00:10:21.760> manager<00:10:22.160> the<00:10:22.320> county<00:10:22.640> CEO<00:10:23.360> Yeah.
00:10:23.839 --> 00:10:30.880
Um<00:10:24.560> so<00:10:25.200> guidelines<00:10:25.680> is<00:10:26.000> important<00:10:26.399> but<00:10:26.640> we<00:10:26.880> are<00:10:27.040> also<00:10:27.360> very<00:10:27.600> careful<00:10:28.079> particularly<00:10:28.399> with<00:10:28.640> large<00:10:28.959> projects<00:10:29.200> and<00:10:29.440> transformative<00:10:30.000> projects<00:10:30.320> and<00:10:30.480> particularly<00:10:30.800> the
00:10:30.880 --> 00:10:39.040
ones<00:10:31.120> that<00:10:31.600> I<00:10:31.760> bring<00:10:31.920> to<00:10:32.079> it<00:10:32.240> is<00:10:32.399> the<00:10:32.720> the<00:10:32.959> principles<00:10:33.760> because<00:10:34.000> once<00:10:34.240> you<00:10:34.399> start<00:10:34.560> getting<00:10:34.800> into<00:10:34.959> guidelines<00:10:36.000> technologies<00:10:36.480> and<00:10:36.640> so<00:10:36.720> forth<00:10:37.360> so<00:10:37.519> prescriptive<00:10:38.800> that
00:10:39.040 --> 00:10:46.959
is<00:10:39.200> this<00:10:39.440> is<00:10:39.600> how<00:10:39.839> it's<00:10:40.160> going<00:10:40.240> to<00:10:40.320> be<00:10:40.399> done<00:10:40.880> it<00:10:41.279> significantly<00:10:42.079> constrains<00:10:42.640> you<00:10:42.959> right<00:10:43.360> so<00:10:43.600> when<00:10:43.839> we<00:10:44.079> establish<00:10:44.720> for<00:10:44.800> example<00:10:45.120> the<00:10:45.360> AI<00:10:45.680> governance<00:10:46.000> in<00:10:46.240> our<00:10:46.399> county<00:10:46.800> we
00:10:46.959 --> 00:10:53.440
worked<00:10:47.200> with<00:10:47.360> the<00:10:47.839> AI<00:10:48.160> collaborative<00:10:48.880> understand<00:10:49.279> what's<00:10:49.519> out<00:10:49.680> there<00:10:49.920> so<00:10:50.079> that<00:10:50.240> we<00:10:50.399> don't<00:10:50.560> have<00:10:50.640> to<00:10:51.120> reinvent<00:10:51.600> the<00:10:51.760> wheel<00:10:52.079> so<00:10:52.160> to<00:10:52.320> speak<00:10:52.560> and<00:10:52.720> collaborate<00:10:53.200> with<00:10:53.360> our
00:10:53.440 --> 00:11:01.680
our<00:10:53.680> partners<00:10:54.000> across<00:10:54.320> the<00:10:54.560> state<00:10:55.120> is<00:10:55.440> that<00:10:55.760> that<00:10:56.079> it<00:10:56.240> was<00:10:56.480> really<00:10:56.720> important<00:10:56.959> that<00:10:57.200> we<00:10:57.440> approach<00:10:57.839> governance<00:10:58.320> as<00:10:58.560> an<00:10:58.800> enabler<00:10:59.279> of<00:10:59.519> the<00:10:59.760> responsible<00:11:00.320> use<00:11:00.560> of<00:11:00.720> AI<00:11:01.440> not
00:11:01.680 --> 00:11:08.800
necessarily<00:11:02.240> the<00:11:02.560> checks<00:11:02.800> and<00:11:03.040> controls<00:11:03.440> you<00:11:03.680> fill<00:11:03.839> out<00:11:04.079> this<00:11:04.320> form<00:11:04.720> and<00:11:04.880> when<00:11:05.040> you<00:11:05.200> go<00:11:05.279> through<00:11:05.519> this<00:11:05.760> process<00:11:06.320> and<00:11:06.480> review<00:11:06.800> cycle<00:11:07.120> and<00:11:07.440> everything<00:11:07.680> else<00:11:07.920> so<00:11:08.320> it<00:11:08.640> needs
00:11:08.800 --> 00:11:15.120
to<00:11:08.880> be<00:11:09.040> viewed<00:11:09.200> when<00:11:09.440> you<00:11:09.519> start<00:11:09.760> establishing<00:11:10.320> governance<00:11:10.800> especially<00:11:11.120> for<00:11:11.279> the<00:11:11.519> county<00:11:11.760> like<00:11:11.920> ours<00:11:12.480> where<00:11:12.720> governance<00:11:13.120> is<00:11:13.279> so<00:11:13.519> important<00:11:13.760> because<00:11:14.000> it's<00:11:14.240> so<00:11:14.399> federated
00:11:15.120 --> 00:11:22.160
we<00:11:15.360> have<00:11:15.519> to<00:11:15.680> really<00:11:16.000> understand<00:11:16.320> that<00:11:16.560> it<00:11:16.720> has<00:11:16.800> to<00:11:16.959> be<00:11:17.040> done<00:11:17.200> in<00:11:17.440> the<00:11:17.600> context<00:11:17.839> of<00:11:18.079> how<00:11:18.240> do<00:11:18.320> we<00:11:18.480> enable<00:11:18.800> the<00:11:19.040> responsible<00:11:19.600> use<00:11:19.839> of<00:11:20.000> technology<00:11:20.800> and<00:11:21.040> AI<00:11:21.440> and<00:11:21.680> protect<00:11:21.920> our
00:11:22.160 --> 00:11:30.000
assets<00:11:22.720> and<00:11:22.880> still<00:11:23.200> be<00:11:23.360> able<00:11:23.519> to<00:11:23.760> deliver<00:11:24.320> the<00:11:24.560> kind<00:11:24.720> of<00:11:24.880> value<00:11:25.200> we<00:11:25.440> need<00:11:25.519> to<00:11:26.079> on<00:11:26.240> that<00:11:26.480> AI<00:11:26.800> and<00:11:26.959> technology<00:11:27.519> to<00:11:28.079> deliver<00:11:28.399> for<00:11:28.640> our<00:11:28.800> departments<00:11:29.200> and<00:11:29.519> the<00:11:29.600> missions.
00:11:30.000 --> 00:11:32.240
<00:11:30.160> Yeah,<00:11:30.320> I<00:11:30.399> love<00:11:30.560> that<00:11:30.640> you<00:11:30.959> mentioned<00:11:31.360> Gov<00:11:31.760> AI.
00:11:32.240 --> 00:11:34.880
Shout<00:11:32.399> out<00:11:32.560> to<00:11:32.640> Khaled<00:11:33.040> Talk.<00:11:33.519> Been<00:11:33.600> on<00:11:33.760> the<00:11:33.839> podcast<00:11:34.160> several<00:11:34.480> times.
00:11:34.880 --> 00:11:37.120
Randomly<00:11:35.440> went<00:11:35.600> to<00:11:35.760> a<00:11:35.920> Dodger<00:11:36.240> game<00:11:36.399> with<00:11:36.560> him<00:11:36.800> too.
00:11:37.120 --> 00:11:39.600
<00:11:37.307> But<00:11:37.493> yeah,<00:11:37.680> I<00:11:37.867> think<00:11:38.053> Gov<00:11:38.240> AI<00:11:38.427> a<00:11:38.613> great<00:11:38.800> example.
00:11:39.600 --> 00:11:42.240
I<00:11:39.760> think<00:11:40.160> not<00:11:40.320> so<00:11:40.480> much<00:11:40.640> now,<00:11:40.800> but<00:11:40.959> early<00:11:41.120> on<00:11:41.360> was<00:11:41.440> like,<00:11:41.600> hey,<00:11:41.760> where<00:11:41.839> do<00:11:42.000> I<00:11:42.079> start?
00:11:42.240 --> 00:11:45.760
And<00:11:42.320> I'm<00:11:42.480> like,<00:11:42.640> you<00:11:42.800> should<00:11:42.880> just<00:11:42.959> go<00:11:43.040> to<00:11:43.120> Gov<00:11:43.360> AI.<00:11:43.680> There's<00:11:43.839> templates,<00:11:44.320> resources,<00:11:44.880> other<00:11:45.120> things<00:11:45.200> like<00:11:45.360> that.
00:11:45.760 --> 00:11:47.920
Hannes,<00:11:46.320> I<00:11:46.480> did<00:11:46.720> want<00:11:46.880> to<00:11:47.120> jump<00:11:47.519> to<00:11:47.760> you.
00:11:47.920 --> 00:11:56.160
Could<00:11:48.240> you<00:11:48.320> talk<00:11:48.480> a<00:11:48.640> little<00:11:48.800> bit<00:11:48.959> about<00:11:49.519> how<00:11:50.320> Info-Tech<00:11:51.760> partners<00:11:52.079> 40<00:11:52.720> departments<00:11:53.040> 40<00:11:53.360> different<00:11:54.160> CIOs<00:11:54.399> you<00:11:54.640> also<00:11:54.800> have<00:11:54.959> to<00:11:55.040> get<00:11:55.279> buy-in<00:11:55.600> right<00:11:56.000> you
00:11:56.160 --> 00:12:04.959
talk<00:11:56.320> about<00:11:56.480> how<00:11:56.640> Info-Tech<00:11:57.600> helps<00:11:58.399> folks<00:11:58.800> get<00:11:58.959> the<00:11:59.200> buy-in<00:11:59.360> to<00:11:59.760> really<00:12:00.480> make<00:12:00.800> impact<00:12:00.959> <00:12:01.680> so<00:12:02.240> first<00:12:02.480> and<00:12:02.640> foremost<00:12:03.279> we<00:12:03.839> want<00:12:04.079> to<00:12:04.560> provide
00:12:04.959 --> 00:12:14.399
value<00:12:05.360> to<00:12:05.839> our<00:12:06.079> members<00:12:06.480> and<00:12:06.720> clients<00:12:07.200> and<00:12:07.440> we<00:12:07.600> do<00:12:07.760> that<00:12:08.079> by<00:12:08.959> providing<00:12:09.839> knowledge<00:12:10.480> templates<00:12:11.040> and<00:12:11.360> approaches<00:12:12.079> that<00:12:12.399> are<00:12:12.880> immediately<00:12:13.519> implementable
00:12:14.399 --> 00:12:22.880
and<00:12:14.639> so<00:12:15.279> when<00:12:15.519> we<00:12:15.760> work<00:12:15.920> with<00:12:16.160> members<00:12:17.120> we<00:12:17.839> obviously<00:12:18.320> understand<00:12:19.120> the<00:12:19.200> the<00:12:19.440> need<00:12:19.600> or<00:12:19.839> the<00:12:20.160> problem<00:12:20.560> and<00:12:20.800> then<00:12:21.040> we<00:12:21.519> help<00:12:21.839> solution<00:12:22.320> and<00:12:22.639> we're
00:12:22.880 --> 00:12:25.519
there<00:12:23.360> during<00:12:23.760> the<00:12:23.920> implementation<00:12:24.560> of<00:12:24.800> the<00:12:24.959> solution.
00:12:25.519 --> 00:12:28.639
But<00:12:25.760> I<00:12:26.000> was<00:12:26.160> going<00:12:26.240> to<00:12:26.320> add<00:12:26.560> to<00:12:26.720> that<00:12:26.959> was<00:12:27.200> that's<00:12:27.519> really<00:12:27.839> important,<00:12:28.320> right?
00:12:28.639 --> 00:12:37.279
Because<00:12:29.279> where<00:12:29.760> we<00:12:30.000> see<00:12:30.480> particularly<00:12:30.959> partners<00:12:31.440> like<00:12:31.839> like<00:12:32.079> Info-Tech<00:12:32.800> that<00:12:32.959> are<00:12:33.200> helpful<00:12:33.440> for<00:12:33.600> the<00:12:33.839> county<00:12:34.079> is<00:12:34.240> that<00:12:34.399> there<00:12:34.639> are<00:12:34.800> gaps<00:12:35.519> within<00:12:35.920> our<00:12:36.240> resources<00:12:36.959> that
00:12:37.279 --> 00:12:40.959
are<00:12:37.519> required<00:12:37.920> and<00:12:38.160> knowledge<00:12:38.720> that<00:12:39.040> are<00:12:39.200> required<00:12:39.600> to<00:12:39.839> deliver<00:12:40.160> some<00:12:40.320> of<00:12:40.480> this<00:12:40.639> stuff.
00:12:40.959 --> 00:12:50.000
Less<00:12:41.279> so<00:12:41.440> the<00:12:41.600> subject<00:12:41.920> matter<00:12:42.320> expertise<00:12:42.880> because<00:12:43.200> we<00:12:43.360> have<00:12:43.519> the<00:12:43.760> subject<00:12:44.079> matter<00:12:44.399> experts<00:12:44.959> but<00:12:45.200> the<00:12:45.440> programmatic<00:12:46.160> side<00:12:46.480> of<00:12:46.880> implementing<00:12:47.680> large<00:12:48.240> complex<00:12:49.360> systems,
00:12:50.000 --> 00:12:52.160
right?<00:12:50.480> How<00:12:50.639> do<00:12:50.720> we<00:12:50.880> do<00:12:51.200> the<00:12:51.360> change<00:12:51.600> management?
00:12:52.160 --> 00:13:00.160
How<00:12:52.320> do<00:12:52.399> we<00:12:52.560> do<00:12:52.639> that?<00:12:52.880> What<00:12:53.040> does<00:12:53.200> that<00:12:53.360> look<00:12:53.600> like?<00:12:53.920> Those<00:12:54.399> actionable<00:12:54.959> templates<00:12:55.680> and<00:12:56.079> best<00:12:56.399> practices<00:12:57.279> are<00:12:57.519> really<00:12:57.839> important<00:12:58.240> to<00:12:58.480> help<00:12:58.720> inform<00:12:59.200> us<00:12:59.360> on<00:12:59.600> how<00:12:59.760> we<00:13:00.000> can
00:13:00.160 --> 00:13:02.000
leverage<00:13:00.480> that<00:13:00.720> because<00:13:00.959> this<00:13:01.200> is<00:13:01.279> new<00:13:01.519> to<00:13:01.680> us.
00:13:02.000 --> 00:13:06.240
We've<00:13:02.320> never<00:13:02.560> done<00:13:03.120> and<00:13:03.360> replace<00:13:03.920> five<00:13:04.320> hospital<00:13:04.880> systems<00:13:05.279> at<00:13:05.440> the<00:13:05.600> same<00:13:05.839> time.
00:13:06.240 --> 00:13:12.639
For<00:13:06.320> example,<00:13:06.880> right?<00:13:07.279> How<00:13:07.440> do<00:13:07.519> we<00:13:07.760> go<00:13:07.839> about<00:13:08.160> doing<00:13:08.320> that<00:13:08.560> and<00:13:08.800> what<00:13:08.959> are<00:13:09.120> the<00:13:09.279> best<00:13:09.519> practices<00:13:09.920> that<00:13:10.160> we<00:13:10.320> could<00:13:10.480> infuse<00:13:10.880> into<00:13:11.120> the<00:13:11.279> project<00:13:11.519> to<00:13:11.760> help<00:13:11.839> us<00:13:12.079> get<00:13:12.240> there,
00:13:12.639 --> 00:13:16.480
right?<00:13:12.959> And<00:13:13.120> that's<00:13:13.360> where<00:13:13.519> the<00:13:13.680> partnership<00:13:14.079> and<00:13:14.320> the<00:13:14.480> expertise<00:13:14.959> comes<00:13:15.200> in<00:13:15.440> to<00:13:15.600> help.
00:13:16.480 --> 00:13:20.720
<00:13:16.676> So<00:13:16.872> when<00:13:17.068> you<00:13:17.264> sign<00:13:17.460> up<00:13:17.656> for<00:13:17.852> Info-Tech,<00:13:18.048> they<00:13:18.244> don't<00:13:18.440> just<00:13:18.635> give<00:13:18.831> you<00:13:19.027> a<00:13:19.223> bunch<00:13:19.419> of<00:13:19.615> playbooks<00:13:19.811> and<00:13:20.007> then<00:13:20.203> leave<00:13:20.399> you.
00:13:20.720 --> 00:13:24.320
No,<00:13:20.959> we<00:13:21.200> do<00:13:21.360> these<00:13:21.680> things<00:13:22.000> with<00:13:22.320> you<00:13:22.639> and<00:13:22.880> not<00:13:23.120> to<00:13:23.440> you,<00:13:24.000> right?
00:13:24.320 --> 00:13:29.600
And<00:13:24.480> we<00:13:24.639> do<00:13:24.720> it<00:13:24.880> in<00:13:25.040> a<00:13:25.200> way<00:13:25.360> that<00:13:25.600> the<00:13:25.920> knowledge<00:13:26.160> and<00:13:26.480> the<00:13:26.639> expertise<00:13:27.600> stays<00:13:28.079> and<00:13:28.399> sticks<00:13:28.639> with<00:13:28.880> you,<00:13:29.279> right?
00:13:29.600 --> 00:13:33.600
Because<00:13:29.760> we<00:13:30.000> want<00:13:30.079> to<00:13:30.560> systematically<00:13:31.360> improve<00:13:31.839> your<00:13:32.160> IT<00:13:32.560> organization.
00:13:33.600 --> 00:13:41.839
And<00:13:34.000> we<00:13:34.320> want<00:13:34.480> to<00:13:34.639> make<00:13:34.800> sure<00:13:34.959> that<00:13:35.200> if<00:13:35.360> you<00:13:35.519> pick<00:13:36.160> one<00:13:36.480> of<00:13:36.560> the<00:13:36.800> 50<00:13:37.120> processes<00:13:37.680> and<00:13:37.920> you<00:13:38.079> implement<00:13:38.560> the<00:13:38.959> Info-Tech<00:13:39.600> playbook<00:13:40.000> that<00:13:40.240> you<00:13:40.480> end<00:13:40.720> up<00:13:40.800> at<00:13:41.040> a<00:13:41.200> higher<00:13:41.440> level<00:13:41.680> in
00:13:41.839 --> 00:13:47.440
maturity,<00:13:42.800> function<00:13:43.200> more<00:13:43.440> efficiently<00:13:43.920> and<00:13:44.240> go<00:13:44.399> to<00:13:44.560> the<00:13:44.720> next<00:13:44.959> process<00:13:45.279> that<00:13:45.519> you<00:13:45.680> need<00:13:45.839> to<00:13:46.000> make<00:13:46.160> that<00:13:46.399> same<00:13:46.639> step<00:13:46.880> up.
00:13:47.440 --> 00:13:56.000
That's<00:13:47.811> our<00:13:48.182> philosophy.<00:13:48.553> <00:13:48.924> That's<00:13:49.295> great.<00:13:49.665> So<00:13:50.036> Hannes,<00:13:50.407> you<00:13:50.778> have<00:13:51.149> the<00:13:51.520> added<00:13:51.891> advantage<00:13:52.262> of<00:13:52.633> working<00:13:53.004> with<00:13:53.375> a<00:13:53.745> lot<00:13:54.116> of<00:13:54.487> different<00:13:54.858> customers<00:13:55.229> all<00:13:55.600> around
00:13:56.000 --> 00:14:00.480
I<00:13:56.160> was<00:13:56.320> going<00:13:56.399> to<00:13:56.480> say<00:13:56.560> the<00:13:56.800> US,<00:13:57.040> but<00:13:57.199> at<00:13:57.360> this<00:13:57.440> point<00:13:57.600> you<00:13:57.760> I<00:13:57.839> think<00:13:57.920> you<00:13:58.079> were<00:13:58.160> just<00:13:58.240> in<00:13:58.399> Sydney,<00:13:58.639> so<00:13:58.880> maybe<00:13:59.040> the<00:13:59.199> world,<00:13:59.680> the<00:13:59.839> globe.
00:14:00.480 --> 00:14:08.800
With<00:14:01.120> kind<00:14:01.279> of<00:14:01.360> that<00:14:01.760> lens,<00:14:02.639> what<00:14:02.880> have<00:14:03.120> you<00:14:03.360> seen<00:14:03.920> from<00:14:04.959> Peter<00:14:05.360> Lou's<00:14:05.760> team<00:14:06.160> and<00:14:06.480> LA<00:14:06.880> County<00:14:07.279> that<00:14:07.440> are<00:14:07.600> some<00:14:07.760> best<00:14:08.000> practices<00:14:08.480> that
00:14:08.800 --> 00:14:14.320
other<00:14:09.120> CIOs<00:14:09.760> and<00:14:09.920> other<00:14:10.240> counties<00:14:10.639> and<00:14:10.880> local<00:14:11.199> governments,<00:14:11.600> even<00:14:11.839> state<00:14:12.079> agencies<00:14:13.040> can<00:14:13.279> take<00:14:13.519> back?
00:14:14.320 --> 00:14:20.800
<00:14:14.700> So<00:14:15.080> I<00:14:15.460> think<00:14:15.840> two<00:14:16.220> aspects.<00:14:16.600> One<00:14:16.980> is<00:14:17.360> at<00:14:17.739> the<00:14:18.119> kind<00:14:18.499> of<00:14:18.879> guidelines<00:14:19.259> and<00:14:19.639> policy<00:14:20.019> side,<00:14:20.399> right?
00:14:20.800 --> 00:14:29.600
Where<00:14:21.199> it<00:14:21.440> is<00:14:21.600> your<00:14:21.839> role<00:14:22.160> to<00:14:22.399> establish<00:14:22.959> policies<00:14:23.839> that<00:14:24.240> are<00:14:24.480> then<00:14:25.040> followed<00:14:25.519> by<00:14:25.760> all<00:14:25.920> the<00:14:26.079> 40<00:14:26.480> departments<00:14:26.800> so<00:14:27.040> that<00:14:27.199> over<00:14:27.440> time<00:14:27.680> you<00:14:28.000> kind<00:14:28.160> of<00:14:28.320> converge<00:14:28.959> on
00:14:29.600 --> 00:14:32.800
similar<00:14:30.000> technologies<00:14:30.639> or<00:14:30.880> similar<00:14:31.279> ways<00:14:31.600> to<00:14:31.760> apply<00:14:32.160> technology.
00:14:32.800 --> 00:14:41.040
So<00:14:32.959> I<00:14:33.199> think<00:14:33.279> that's<00:14:33.600> one<00:14:34.480> area<00:14:34.880> where<00:14:35.199> there's<00:14:35.440> a<00:14:35.680> constant<00:14:36.399> struggle<00:14:37.199> because<00:14:37.600> the<00:14:37.920> more<00:14:38.079> federated<00:14:38.560> you<00:14:38.800> are<00:14:39.040> the<00:14:39.199> more<00:14:39.279> there's<00:14:39.519> a<00:14:39.680> tendency<00:14:40.079> to<00:14:40.399> diverge<00:14:40.880> and
00:14:41.040 --> 00:14:49.920
not<00:14:41.279> converge.<00:14:41.920> I<00:14:42.240> think<00:14:42.560> the<00:14:43.120> the<00:14:43.760> second<00:14:44.160> part<00:14:44.560> is<00:14:44.959> to<00:14:46.000> really<00:14:46.639> bring<00:14:47.279> people<00:14:47.680> together<00:14:48.639> on<00:14:48.880> a<00:14:49.120> common
00:14:49.920 --> 00:14:52.320
approach,<00:14:50.639> solution,<00:14:51.519> whatnot,<00:14:52.079> right?
00:14:52.320 --> 00:15:00.000
And<00:14:52.560> one<00:14:52.800> example<00:14:53.120> that<00:14:53.360> comes<00:14:53.600> to<00:14:53.760> mind<00:14:53.920> is<00:14:54.160> the<00:14:54.320> data<00:14:54.639> center<00:14:54.959> consolidation<00:14:55.760> here<00:14:56.000> at<00:14:56.160> the<00:14:56.399> county,<00:14:57.120> which<00:14:57.360> was<00:14:57.760> it<00:14:58.000> was<00:14:58.079> a<00:14:58.240> bit<00:14:58.320> of<00:14:58.399> an<00:14:58.560> uphill<00:14:58.959> battle,<00:14:59.519> right?
00:15:00.000 --> 00:15:08.639
uh<00:15:00.160> initially<00:15:00.800> but<00:15:01.040> it<00:15:01.279> was<00:15:01.360> a<00:15:01.519> mandate<00:15:02.000> by<00:15:02.240> the<00:15:02.399> board<00:15:02.560> of<00:15:02.720> supervisors<00:15:03.920> and<00:15:04.560> it<00:15:04.880> was<00:15:05.199> your<00:15:05.600> office<00:15:06.000> who<00:15:06.959> implemented<00:15:07.440> that<00:15:07.680> mandate<00:15:08.240> again
00:15:08.639 --> 00:15:16.000
with<00:15:09.440> facilitation<00:15:10.240> and<00:15:10.480> partnership<00:15:11.279> and<00:15:11.839> and<00:15:12.399> managing<00:15:12.880> some<00:15:13.440> very<00:15:13.839> divergent<00:15:14.480> viewpoints<00:15:14.959> at<00:15:15.199> times.
00:15:16.000 --> 00:15:20.639
<00:15:16.364> Okay.<00:15:16.727> So<00:15:17.091> let's<00:15:17.455> take<00:15:17.818> the<00:15:18.182> data<00:15:18.545> center<00:15:18.909> consolidation<00:15:19.273> as<00:15:19.636> an<00:15:20.000> example.
00:15:20.639 --> 00:15:28.480
<00:15:20.970> Yeah,<00:15:21.301> <00:15:21.632> that's<00:15:21.963> a<00:15:22.294> pretty<00:15:22.625> common<00:15:22.956> one.<00:15:23.287> You<00:15:23.618> probably<00:15:23.949> have<00:15:24.280> a<00:15:24.610> wide<00:15:24.941> spectrum<00:15:25.272> of<00:15:25.603> of<00:15:25.934> leaders<00:15:26.265> who<00:15:26.596> are<00:15:26.927> involved<00:15:27.258> in<00:15:27.589> the<00:15:27.920> decision-making.
00:15:28.480 --> 00:15:33.279
There<00:15:28.720> are<00:15:28.880> other<00:15:29.040> leaders<00:15:29.440> across<00:15:29.760> the<00:15:30.000> US<00:15:30.160> who<00:15:30.480> will<00:15:30.800> probably<00:15:31.040> still<00:15:31.279> go<00:15:31.360> through<00:15:31.519> a<00:15:31.680> data<00:15:32.000> center<00:15:32.320> consolidation.
00:15:33.279 --> 00:15:39.199
Yeah.<00:15:33.600> Hannes,<00:15:34.079> when<00:15:34.320> folks<00:15:34.560> come<00:15:34.880> when<00:15:35.040> CIOs<00:15:35.600> come<00:15:35.680> to<00:15:35.839> Info-Tech<00:15:36.639> and<00:15:36.959> hey,<00:15:37.199> we've<00:15:37.440> got<00:15:37.519> this<00:15:37.760> complex<00:15:38.240> problem.
00:15:39.199 --> 00:15:41.760
We<00:15:39.360> want<00:15:39.440> to<00:15:39.600> consolidate<00:15:40.160> this<00:15:40.560> data<00:15:40.800> center<00:15:41.040> example.
00:15:41.760 --> 00:15:45.360
What<00:15:42.000> does<00:15:42.079> that<00:15:42.240> look<00:15:42.399> like?<00:15:42.880> How<00:15:43.040> do<00:15:43.199> you<00:15:43.760> kick<00:15:44.079> off<00:15:44.240> that<00:15:44.480> engagement?
00:15:45.360 --> 00:15:49.680
Give<00:15:45.519> us<00:15:45.680> a<00:15:45.760> little<00:15:45.839> more.<00:15:46.079> You<00:15:46.240> said<00:15:46.560> needs<00:15:47.279> looking<00:15:47.440> at<00:15:47.600> the<00:15:47.839> problem,<00:15:48.160> your<00:15:48.480> solutioning.
00:15:49.680 --> 00:15:51.920
go<00:15:50.399> a<00:15:50.720> step<00:15:51.040> deeper<00:15:51.360> for<00:15:51.600> us.
00:15:51.920 --> 00:16:00.240
We<00:15:52.160> can<00:15:52.240> do<00:15:52.399> this<00:15:52.560> at<00:15:52.720> different<00:15:53.120> levels.<00:15:53.600> We<00:15:53.839> can<00:15:54.079> look<00:15:54.240> at<00:15:54.480> the<00:15:54.720> problem<00:15:55.279> and<00:15:55.519> then<00:15:55.759> go<00:15:56.000> find<00:15:56.320> what<00:15:56.560> we<00:15:56.800> call<00:15:56.880> a<00:15:57.120> blueprint<00:15:57.839> and<00:15:58.160> say<00:15:58.480> a<00:15:58.720> how-to<00:15:59.199> guide<00:15:59.440> to<00:15:59.680> do<00:15:59.839> it.
00:16:00.240 --> 00:16:02.240
And<00:16:00.399> you<00:16:00.560> can<00:16:00.720> take<00:16:00.880> that<00:16:01.040> and<00:16:01.279> say,<00:16:01.360> "Good,<00:16:01.759> I'm<00:16:02.000> good.
00:16:02.240 --> 00:16:10.320
I'll<00:16:02.480> go<00:16:02.720> do<00:16:02.880> it<00:16:02.959> on<00:16:03.120> my<00:16:03.279> own."<00:16:03.680> You<00:16:03.920> can<00:16:04.079> then<00:16:04.320> do<00:16:04.560> that<00:16:04.959> as<00:16:05.120> a<00:16:05.360> guided<00:16:05.680> implementation<00:16:06.399> where<00:16:06.639> you<00:16:06.800> have<00:16:07.040> analyst<00:16:07.519> calls<00:16:07.839> along<00:16:08.160> the<00:16:08.320> way<00:16:08.560> and<00:16:08.880> this<00:16:09.360> these<00:16:09.600> are<00:16:09.759> checkpoints
00:16:10.320 --> 00:16:12.959
where<00:16:10.480> you<00:16:10.639> have<00:16:10.720> a<00:16:10.880> partner<00:16:11.120> who<00:16:11.440> makes<00:16:11.600> sure<00:16:11.759> you're<00:16:12.079> doing<00:16:12.160> it<00:16:12.399> right.
00:16:12.959 --> 00:16:16.240
You<00:16:13.120> can<00:16:13.279> then<00:16:13.759> do<00:16:13.920> it<00:16:14.160> as<00:16:14.320> part<00:16:14.480> of<00:16:14.639> as<00:16:14.880> a<00:16:15.040> workshop,<00:16:15.920> right?
00:16:16.240 --> 00:16:24.959
where<00:16:16.480> we<00:16:16.880> come<00:16:17.360> to<00:16:17.680> you,<00:16:18.160> we<00:16:18.480> work<00:16:18.720> together<00:16:19.440> over<00:16:19.920> a<00:16:20.240> period<00:16:20.480> of<00:16:20.720> time<00:16:21.360> and<00:16:21.600> we<00:16:22.000> drive<00:16:22.240> to<00:16:22.399> a<00:16:22.639> solution<00:16:22.959> that<00:16:23.199> could<00:16:23.360> be<00:16:23.440> for<00:16:23.680> a<00:16:23.839> data<00:16:24.079> center<00:16:24.399> strategy
00:16:24.959 --> 00:16:33.279
or<00:16:25.279> for<00:16:25.519> requirements<00:16:26.160> gathering<00:16:26.639> or<00:16:27.120> a<00:16:27.519> small<00:16:27.920> discrete<00:16:28.480> piece<00:16:28.880> of<00:16:29.040> one<00:16:29.279> of<00:16:29.360> those<00:16:29.519> bigger<00:16:29.920> journeys<00:16:30.800> or<00:16:31.120> you<00:16:31.440> can<00:16:31.600> you<00:16:31.920> can<00:16:32.079> do<00:16:32.240> consulting<00:16:32.880> where<00:16:33.120> we're
00:16:33.279 --> 00:16:41.759
there<00:16:33.440> with<00:16:33.680> you<00:16:33.839> through<00:16:34.079> the<00:16:34.320> entire<00:16:34.720> process.<00:16:35.199> So<00:16:35.680> our<00:16:36.000> approach<00:16:36.320> is<00:16:36.639> very<00:16:36.959> flexible<00:16:37.680> but<00:16:37.920> it<00:16:38.160> is<00:16:38.320> very<00:16:38.639> consistent<00:16:39.440> in<00:16:40.320> how<00:16:40.639> we<00:16:41.279> what
00:16:41.759 --> 00:16:46.160
playbook<00:16:42.240> we<00:16:42.560> follow<00:16:43.120> and<00:16:43.360> how<00:16:43.519> we<00:16:43.759> implement<00:16:44.079> it<00:16:44.240> and<00:16:44.399> it's<00:16:44.639> always<00:16:44.959> outcome<00:16:45.360> focused.
00:16:46.160 --> 00:16:49.600
<00:16:46.436> We're<00:16:46.713> not<00:16:46.989> just<00:16:47.265> there<00:16:47.541> to<00:16:47.818> spend<00:16:48.094> time<00:16:48.370> and<00:16:48.646> figure<00:16:48.923> things<00:16:49.199> out.
00:16:49.600 --> 00:16:53.600
We<00:16:49.788> have<00:16:49.976> a<00:16:50.164> plan<00:16:50.352> when<00:16:50.540> we<00:16:50.728> show<00:16:50.916> up.<00:16:51.104> <00:16:51.292> We<00:16:51.480> got<00:16:51.668> add<00:16:51.856> a<00:16:52.044> little<00:16:52.232> bit<00:16:52.420> of<00:16:52.608> a<00:16:52.796> customer's<00:16:52.984> perspective<00:16:53.172> to<00:16:53.360> that.
00:16:53.600 --> 00:16:57.199
<00:16:53.884> We<00:16:54.167> chose<00:16:54.451> the<00:16:54.735> consulting<00:16:55.018> approach<00:16:55.302> just<00:16:55.585> because<00:16:55.869> of<00:16:56.153> this<00:16:56.436> particular<00:16:56.720> topic.
00:16:57.199 --> 00:17:01.600
Right.<00:16:57.680> We<00:16:57.920> needed<00:16:58.160> a<00:16:58.399> consultant<00:16:58.800> a<00:16:59.040> partner<00:16:59.519> to<00:16:59.759> help<00:16:59.920> us<00:17:00.160> build<00:17:00.720> the<00:17:00.959> why.
00:17:01.600 --> 00:17:05.439
Why<00:17:01.839> are<00:17:02.000> we<00:17:02.160> consolidating<00:17:03.040> 42?<00:17:03.839> We<00:17:04.079> have<00:17:04.240> 42<00:17:04.640> data<00:17:04.880> centers.
00:17:05.439 --> 00:17:08.079
Many<00:17:05.679> of<00:17:05.760> them<00:17:06.000> were<00:17:06.160> closets<00:17:06.559> and<00:17:06.799> racking<00:17:07.199> rooms<00:17:07.520> and<00:17:07.679> offices.
00:17:08.079 --> 00:17:11.360
They<00:17:08.240> were<00:17:08.400> not<00:17:08.559> really<00:17:08.959> data<00:17:09.199> centers,<00:17:09.520> but<00:17:09.679> they<00:17:09.839> were<00:17:09.919> used<00:17:10.079> as<00:17:10.319> data<00:17:10.480> centers,<00:17:10.880> right?
00:17:11.360 --> 00:17:13.280
So<00:17:11.600> what<00:17:11.760> is<00:17:11.919> the<00:17:12.079> why<00:17:12.319> why<00:17:12.559> are<00:17:12.720> we<00:17:12.880> doing<00:17:13.039> this?
00:17:13.280 --> 00:17:19.679
We<00:17:13.520> were<00:17:13.600> at<00:17:13.760> the<00:17:13.919> point<00:17:14.079> the<00:17:14.240> county<00:17:14.480> was<00:17:14.559> at<00:17:14.720> a<00:17:14.880> critical<00:17:15.199> point<00:17:15.439> where<00:17:15.600> we<00:17:15.760> had<00:17:15.919> to<00:17:16.000> decide<00:17:16.240> whether<00:17:16.559> we<00:17:16.720> build<00:17:16.880> our<00:17:17.039> data<00:17:17.360> center<00:17:17.839> which<00:17:18.240> require<00:17:18.640> we<00:17:18.799> have<00:17:18.959> the<00:17:19.120> space.
00:17:19.679 --> 00:17:26.720
We<00:17:19.839> would<00:17:20.000> have<00:17:20.160> to<00:17:20.319> have<00:17:20.799> substantial<00:17:21.280> capital<00:17:21.679> investment<00:17:22.079> to<00:17:22.319> do<00:17:22.400> that<00:17:22.880> or<00:17:23.120> at<00:17:23.280> that<00:17:23.520> time<00:17:23.839> maybe<00:17:24.079> we<00:17:24.240> need<00:17:24.400> to<00:17:24.559> look<00:17:24.640> at<00:17:24.799> alternative<00:17:25.360> ways<00:17:25.600> on<00:17:25.839> how<00:17:26.079> we<00:17:26.240> can<00:17:26.400> provide
00:17:26.720 --> 00:17:30.640
data<00:17:26.959> center<00:17:27.280> services<00:17:27.760> in<00:17:28.000> a<00:17:28.160> much<00:17:28.400> more<00:17:28.559> managed<00:17:28.960> way<00:17:29.360> and<00:17:29.600> a<00:17:29.760> lower<00:17:30.080> cost<00:17:30.320> way.
00:17:30.640 --> 00:17:35.679
So<00:17:30.799> we<00:17:31.039> build<00:17:31.200> that<00:17:31.440> business<00:17:31.679> case<00:17:31.919> and<00:17:32.080> it<00:17:32.320> became<00:17:32.559> very<00:17:32.880> apparent<00:17:33.200> to<00:17:33.440> us<00:17:33.679> is<00:17:34.080> we<00:17:34.240> build<00:17:34.400> it<00:17:34.640> around<00:17:35.120> risk.
00:17:35.679 --> 00:17:37.919
What<00:17:35.919> would<00:17:36.080> happen<00:17:36.320> if<00:17:36.559> we<00:17:36.720> don't<00:17:36.880> do<00:17:37.039> this<00:17:37.600> right?
00:17:37.919 --> 00:17:41.280
We<00:17:38.160> did<00:17:38.320> an<00:17:38.960> inventory<00:17:39.919> with<00:17:40.240> Info-Tech<00:17:40.880> helper.
00:17:41.280 --> 00:17:44.480
We<00:17:41.440> went<00:17:41.600> out<00:17:41.840> and<00:17:42.000> we<00:17:42.240> did<00:17:42.480> this<00:17:42.880> survey<00:17:43.200> of<00:17:43.360> all<00:17:43.520> the<00:17:43.679> 42<00:17:44.160> days.
00:17:44.480 --> 00:17:51.760
We<00:17:44.640> went<00:17:44.799> took<00:17:45.039> pictures<00:17:45.520> with<00:17:45.679> the<00:17:45.919> conditions<00:17:46.240> of<00:17:46.559> some<00:17:46.640> of<00:17:46.799> these<00:17:46.960> data<00:17:47.120> centers<00:17:47.520> and<00:17:47.760> when<00:17:47.919> we<00:17:48.080> sat<00:17:48.320> down<00:17:48.720> with<00:17:49.039> our<00:17:49.520> board<00:17:49.919> members<00:17:50.400> to<00:17:50.720> explain<00:17:51.039> why<00:17:51.280> we<00:17:51.520> needed
00:17:51.760 --> 00:17:56.000
to<00:17:51.840> do<00:17:51.919> this.<00:17:52.160> We<00:17:52.240> had<00:17:52.320> a<00:17:52.480> good<00:17:52.720> board<00:17:53.039> sponsor<00:17:53.760> and<00:17:53.919> said<00:17:54.240> here's<00:17:54.480> the<00:17:54.720> risk<00:17:54.960> if<00:17:55.200> we<00:17:55.360> don't<00:17:55.520> do<00:17:55.679> this.
00:17:56.000 --> 00:18:03.919
when<00:17:56.240> they<00:17:56.400> start<00:17:56.720> seeing<00:17:56.960> the<00:17:57.280> conditions<00:17:58.000> of<00:17:58.240> some<00:17:58.400> of<00:17:58.559> our<00:17:58.720> data<00:17:59.039> centers<00:17:59.440> and<00:17:59.760> why<00:18:00.000> and<00:18:00.240> what<00:18:00.480> and<00:18:00.720> whatn<00:18:00.880> not<00:18:01.120> it<00:18:01.280> became<00:18:01.600> a<00:18:01.760> now<00:18:02.000> that<00:18:02.160> imperative<00:18:02.880> right<00:18:03.280> and<00:18:03.520> so
00:18:03.919 --> 00:18:12.240
it<00:18:04.160> was<00:18:04.240> a<00:18:04.400> risk<00:18:04.799> mandated<00:18:05.520> imperative<00:18:06.000> for<00:18:06.240> us<00:18:06.400> to<00:18:06.559> deal<00:18:07.120> took<00:18:07.280> us<00:18:07.440> close<00:18:07.679> to<00:18:07.840> about<00:18:08.400> four<00:18:08.720> years<00:18:09.200> but<00:18:09.440> now<00:18:09.600> we<00:18:09.840> are<00:18:10.080> we<00:18:10.320> don't<00:18:10.480> have<00:18:10.640> those<00:18:10.880> 42<00:18:11.280> data<00:18:11.600> centers<00:18:12.000> running
00:18:12.240 --> 00:18:20.640
in<00:18:12.480> closets<00:18:13.039> and<00:18:13.440> in<00:18:13.840> office<00:18:14.160> spaces<00:18:14.640> anymore<00:18:15.039> and<00:18:15.280> now<00:18:15.440> we<00:18:15.600> have<00:18:15.760> whole<00:18:16.000> T5<00:18:16.720> data<00:18:17.120> center<00:18:17.679> that<00:18:17.919> is<00:18:18.320> earthquake<00:18:19.679> earthquake<00:18:20.240> proof
00:18:20.640 --> 00:18:26.720
and<00:18:20.799> now<00:18:20.960> we're<00:18:21.280> much<00:18:21.440> more<00:18:21.600> resilient<00:18:22.000> than<00:18:22.240> we<00:18:22.320> were<00:18:22.480> ever<00:18:22.640> with<00:18:22.880> and<00:18:23.039> the<00:18:23.200> risks<00:18:23.600> have<00:18:23.840> dramatically<00:18:24.880> been<00:18:25.120> reduced<00:18:25.679> So<00:18:25.919> you<00:18:26.080> said<00:18:26.320> pictures.
00:18:26.720 --> 00:18:31.039
Did<00:18:26.920> you<00:18:27.120> show<00:18:27.320> you<00:18:27.520> did<00:18:27.720> you<00:18:27.920> show<00:18:28.120> up<00:18:28.320> with<00:18:28.520> a<00:18:28.720> stack<00:18:28.920> of<00:18:29.120> photos<00:18:29.320> to<00:18:29.520> sell<00:18:29.720> the<00:18:29.920> business<00:18:30.120> game<00:18:30.320> <00:18:30.520> with<00:18:30.720> slides?
00:18:31.039 --> 00:18:34.559
There<00:18:31.200> were<00:18:31.280> data<00:18:31.679> slides<00:18:32.480> windows,<00:18:33.120> refrigerators<00:18:33.919> in<00:18:34.080> there.
00:18:34.559 --> 00:18:36.880
Yeah.<00:18:34.839> <00:18:35.119> Under<00:18:35.400> desks.<00:18:35.680> Yes.<00:18:35.960> <00:18:36.240> Yeah.
00:18:36.880 --> 00:18:40.320
<00:18:37.142> Yeah.<00:18:37.404> I<00:18:37.665> love<00:18:37.927> that.<00:18:38.189> <00:18:38.451> So<00:18:38.713> again,<00:18:38.975> think<00:18:39.236> about<00:18:39.498> the<00:18:39.760> question.
00:18:40.320 --> 00:18:42.640
You've<00:18:40.559> got<00:18:40.720> this<00:18:40.960> business<00:18:41.200> case<00:18:41.440> you<00:18:41.679> want<00:18:41.760> to<00:18:41.919> make.
00:18:42.640 --> 00:18:49.280
<00:18:43.015> Again,<00:18:43.390> not<00:18:43.765> a<00:18:44.140> technology<00:18:44.515> thing,<00:18:44.890> but<00:18:45.265> what<00:18:45.640> advice<00:18:46.015> would<00:18:46.390> you<00:18:46.765> give<00:18:47.140> on<00:18:47.515> either<00:18:47.890> presenting,<00:18:48.265> positioning,<00:18:48.640> structuring?
00:18:49.280 --> 00:18:53.760
Like<00:18:49.506> how<00:18:49.732> should<00:18:49.958> CIOs,<00:18:50.184> if<00:18:50.409> they<00:18:50.635> want<00:18:50.861> to<00:18:51.087> go,<00:18:51.313> you<00:18:51.539> said<00:18:51.765> you<00:18:51.991> had<00:18:52.216> a<00:18:52.442> sponsor,<00:18:52.668> which<00:18:52.894> is<00:18:53.120> great.
00:18:53.760 --> 00:18:56.080
probably<00:18:54.080> the<00:18:54.240> sponsor<00:18:54.640> probably<00:18:54.880> didn't<00:18:55.039> happen<00:18:55.280> overnight,<00:18:55.840> right?
00:18:56.080 --> 00:19:03.760
There<00:18:56.240> had<00:18:56.320> to<00:18:56.400> be<00:18:56.559> a<00:18:56.720> relationship<00:18:57.120> there.<00:18:58.000> Talk<00:18:58.160> about<00:18:58.320> how<00:18:58.480> you<00:18:58.640> can<00:18:58.799> build<00:18:58.960> those<00:18:59.200> relationships<00:19:00.240> with<00:19:00.480> the<00:19:00.720> sponsors<00:19:01.120> that<00:19:01.280> you<00:19:01.520> need<00:19:02.400> so<00:19:02.640> that<00:19:02.880> folks<00:19:03.120> just<00:19:03.360> understand,
00:19:03.760 --> 00:19:12.480
hey,<00:19:04.198> this<00:19:04.636> isn't<00:19:05.074> just<00:19:05.512> this<00:19:05.949> kind<00:19:06.387> of<00:19:06.825> vague<00:19:07.263> risk,<00:19:07.701> <00:19:08.139> but<00:19:08.577> so<00:19:09.015> that<00:19:09.453> folks<00:19:09.891> can<00:19:10.328> really<00:19:10.766> understand<00:19:11.204> that<00:19:11.642> the<00:19:12.080> almost
00:19:12.480 --> 00:19:14.960
the<00:19:12.960> like<00:19:13.520> what's<00:19:13.760> the<00:19:13.919> right<00:19:14.080> word<00:19:14.240> for<00:19:14.480> this?
00:19:14.960 --> 00:19:22.480
It<00:19:15.120> would<00:19:15.280> almost<00:19:15.600> be<00:19:16.320> like<00:19:16.559> when<00:19:16.799> you<00:19:16.960> communicate<00:19:17.520> to<00:19:17.760> the<00:19:17.919> technical<00:19:18.320> team,<00:19:19.120> there's<00:19:19.440> certain<00:19:19.760> language<00:19:20.240> there<00:19:20.480> that<00:19:20.799> they<00:19:20.960> would<00:19:21.120> understand,<00:19:21.600> but<00:19:21.919> oftentimes
00:19:22.480 --> 00:19:29.440
it<00:19:22.720> gets<00:19:22.880> lost<00:19:23.039> in<00:19:23.280> translation.<00:19:23.760> When<00:19:23.919> you<00:19:24.000> have<00:19:24.080> to<00:19:24.240> communicate<00:19:24.480> to<00:19:24.640> the<00:19:24.799> executive<00:19:25.200> team,<00:19:25.840> what<00:19:26.080> advice<00:19:26.400> would<00:19:26.640> you<00:19:26.799> give<00:19:27.600> communicating<00:19:28.160> to<00:19:28.320> the<00:19:28.480> executive<00:19:28.880> team?
00:19:29.440 --> 00:19:36.160
<00:19:29.693> For<00:19:29.946> the<00:19:30.198> executive<00:19:30.451> team<00:19:30.704> is<00:19:30.957> the<00:19:31.210> language<00:19:31.462> of<00:19:31.715> business<00:19:31.968> and<00:19:32.221> when<00:19:32.474> you<00:19:32.726> talk<00:19:32.979> to<00:19:33.232> executives,<00:19:33.485> they<00:19:33.738> care<00:19:33.990> about<00:19:34.243> value<00:19:34.496> and<00:19:34.749> what<00:19:35.002> does<00:19:35.254> that<00:19:35.507> value<00:19:35.760> translate
00:19:36.160 --> 00:19:38.240
to<00:19:36.400> the<00:19:36.640> different<00:19:36.880> things<00:19:37.039> that<00:19:37.200> are<00:19:37.360> important<00:19:37.679> to<00:19:37.840> them.
00:19:38.240 --> 00:19:42.400
What<00:19:38.400> the<00:19:38.559> board<00:19:38.720> of<00:19:38.960> supervisors<00:19:39.520> and<00:19:39.679> accounting<00:19:40.000> is<00:19:40.240> our<00:19:40.559> services<00:19:40.880> to<00:19:41.120> our<00:19:41.280> constituents,<00:19:42.160> right?
00:19:42.400 --> 00:19:46.160
How<00:19:42.640> do<00:19:42.799> we<00:19:42.960> provide<00:19:43.760> better<00:19:44.160> value<00:19:44.799> to<00:19:45.039> the<00:19:45.280> services<00:19:45.600> that<00:19:45.760> we<00:19:45.919> need?
00:19:46.160 --> 00:19:52.960
And<00:19:46.320> many<00:19:46.559> times<00:19:46.799> often<00:19:47.200> times<00:19:47.520> also<00:19:48.160> many<00:19:48.400> of<00:19:48.559> the<00:19:48.720> recipients<00:19:49.120> of<00:19:49.280> our<00:19:49.440> services<00:19:49.840> are<00:19:50.000> safety<00:19:50.400> net<00:19:50.640> services<00:19:51.039> where<00:19:51.280> they<00:19:51.440> don't<00:19:51.600> have<00:19:51.760> any<00:19:52.240> other<00:19:52.320> other<00:19:52.559> place<00:19:52.720> to
00:19:52.960 --> 00:20:01.280
go.<00:19:53.360> So<00:19:53.840> how<00:19:54.080> do<00:19:54.240> we<00:19:54.400> get<00:19:54.720> proper<00:19:55.120> accessibility<00:19:55.919> to<00:19:56.240> these<00:19:56.480> services<00:19:57.039> and<00:19:57.280> so<00:19:57.440> forth<00:19:57.919> reaching<00:19:58.320> digital<00:19:58.799> device<00:19:59.200> and<00:19:59.440> gaps<00:20:00.080> reaching<00:20:00.480> out<00:20:00.640> and<00:20:00.880> be<00:20:01.039> able
00:20:01.280 --> 00:20:09.120
to<00:20:01.600> enable<00:20:02.240> the<00:20:02.559> people<00:20:02.880> the<00:20:03.039> frontline<00:20:03.440> workers<00:20:03.760> that<00:20:04.080> work<00:20:04.240> with<00:20:04.559> these<00:20:04.880> folks<00:20:05.360> the<00:20:05.760> information<00:20:06.160> and<00:20:06.400> the<00:20:06.640> systems<00:20:06.880> and<00:20:07.039> the<00:20:07.200> technology<00:20:07.520> they<00:20:07.760> need<00:20:07.919> to<00:20:08.080> do<00:20:08.320> to<00:20:08.720> better
00:20:09.120 --> 00:20:11.280
deliver<00:20:09.520> those<00:20:09.760> services.<00:20:10.240> That's<00:20:10.480> one<00:20:10.720> area<00:20:11.120> right?
00:20:11.280 --> 00:20:14.480
That's<00:20:11.520> what<00:20:11.679> value<00:20:12.000> means<00:20:12.320> to<00:20:12.480> us<00:20:12.880> in<00:20:13.120> public<00:20:13.440> sector<00:20:13.679> and<00:20:13.919> the<00:20:14.080> county.
00:20:14.480 --> 00:20:17.200
The<00:20:14.720> other<00:20:14.880> one<00:20:14.960> that<00:20:15.200> they're<00:20:15.440> also<00:20:15.679> very<00:20:15.919> mindful<00:20:16.240> of<00:20:16.480> is<00:20:16.720> risk.
00:20:17.200 --> 00:20:25.120
You<00:20:17.360> balance<00:20:17.760> value<00:20:18.080> with<00:20:18.320> risk.<00:20:18.640> If<00:20:18.799> there<00:20:18.960> are<00:20:19.120> things<00:20:19.360> that<00:20:19.679> are<00:20:19.840> at<00:20:20.080> risk<00:20:20.559> for<00:20:20.720> the<00:20:20.880> county<00:20:21.280> that<00:20:21.360> that<00:20:21.679> jeopardizes<00:20:22.400> the<00:20:22.640> way<00:20:23.360> we<00:20:23.600> deliver<00:20:24.000> our<00:20:24.240> services<00:20:24.720> and<00:20:24.960> so
00:20:25.120 --> 00:20:29.200
forth<00:20:25.520> and<00:20:25.679> so<00:20:25.840> forth,<00:20:26.160> how<00:20:26.320> do<00:20:26.400> we<00:20:26.720> mitigate<00:20:27.200> those<00:20:27.440> risks<00:20:27.840> and<00:20:28.080> how<00:20:28.240> do<00:20:28.320> we<00:20:28.480> address<00:20:28.720> those<00:20:28.960> risks?
00:20:29.200 --> 00:20:36.400
So,<00:20:29.360> if<00:20:29.520> you<00:20:29.600> talk<00:20:29.760> to<00:20:29.919> it<00:20:30.080> in<00:20:30.240> those<00:20:30.480> terms,<00:20:31.039> those<00:20:31.360> business<00:20:31.760> terms,<00:20:32.320> I<00:20:32.480> think<00:20:32.559> it<00:20:32.799> resonates<00:20:33.280> that<00:20:33.440> and<00:20:33.600> that's<00:20:33.760> how<00:20:33.919> you<00:20:34.080> build<00:20:34.320> that<00:20:34.640> sponsorship<00:20:35.200> and<00:20:35.440> the<00:20:35.600> relationship.
00:20:36.400 --> 00:20:42.720
The<00:20:36.640> other<00:20:36.799> thing<00:20:36.880> that<00:20:37.120> we<00:20:37.280> also<00:20:37.760> do<00:20:38.000> quite<00:20:38.240> a<00:20:38.400> bit<00:20:38.559> of<00:20:38.880> is<00:20:39.520> listening<00:20:40.000> to<00:20:40.240> them<00:20:40.400> and<00:20:40.720> seeing<00:20:41.039> understanding<00:20:41.520> what<00:20:41.760> their<00:20:42.000> priorities<00:20:42.480> are.
00:20:42.720 --> 00:20:44.640
We<00:20:42.880> have<00:20:43.039> five<00:20:43.280> board<00:20:43.600> members,<00:20:44.240> right?
00:20:44.640 --> 00:20:47.120
And<00:20:44.880> each<00:20:45.039> one<00:20:45.200> of<00:20:45.360> them<00:20:45.600> have<00:20:45.760> their<00:20:46.000> own<00:20:46.159> set<00:20:46.320> of<00:20:46.559> priorities.
00:20:47.120 --> 00:20:51.360
Some<00:20:47.280> of<00:20:47.440> them<00:20:47.600> are<00:20:47.760> the<00:20:47.919> same<00:20:48.080> and<00:20:48.320> some<00:20:48.480> of<00:20:48.559> them<00:20:48.720> are<00:20:48.880> a<00:20:48.960> little<00:20:49.039> bit<00:20:49.200> different<00:20:49.440> based<00:20:49.679> on<00:20:49.840> the<00:20:50.000> communities<00:20:50.400> they<00:20:50.720> represent.
00:20:51.360 --> 00:20:55.200
Listening<00:20:51.679> to<00:20:51.840> them<00:20:52.080> and<00:20:52.320> understanding<00:20:52.960> what<00:20:53.280> those<00:20:53.840> pain<00:20:54.159> points<00:20:54.559> are.
00:20:55.200 --> 00:20:57.679
What<00:20:55.440> are<00:20:55.600> the<00:20:55.840> things<00:20:56.000> that<00:20:56.240> are<00:20:56.400> most<00:20:56.640> important<00:20:56.960> for<00:20:57.200> them?
00:20:57.679 --> 00:21:04.880
And<00:20:57.840> then<00:20:58.080> making<00:20:58.400> sure<00:20:58.640> that<00:20:58.880> when<00:20:59.039> we<00:20:59.280> bring<00:20:59.600> forth<00:21:00.000> and<00:21:00.320> develop<00:21:00.720> initiatives<00:21:01.679> is<00:21:01.919> that<00:21:02.159> it<00:21:02.400> that's<00:21:02.720> the<00:21:02.960> why<00:21:03.760> why<00:21:04.000> we're<00:21:04.320> doing<00:21:04.480> this.
00:21:04.880 --> 00:21:09.039
And<00:21:05.039> in<00:21:05.360> connecting<00:21:05.679> those<00:21:06.000> those<00:21:06.240> are<00:21:06.400> very<00:21:06.640> important<00:21:07.039> things<00:21:07.440> that<00:21:07.679> we<00:21:07.840> do<00:21:08.000> out<00:21:08.159> of<00:21:08.320> our<00:21:08.480> office.
00:21:09.039 --> 00:21:11.840
<00:21:09.257> I<00:21:09.476> love<00:21:09.694> that.<00:21:09.912> So<00:21:10.130> I<00:21:10.349> heard<00:21:10.567> talk<00:21:10.785> the<00:21:11.003> language<00:21:11.222> of<00:21:11.440> business.
00:21:11.840 --> 00:21:15.039
Yeah.<00:21:12.116> <00:21:12.391> Just<00:21:12.667> in<00:21:12.942> addition<00:21:13.218> in<00:21:13.493> the<00:21:13.769> use<00:21:14.044> of<00:21:14.320> partnerships.
00:21:15.039 --> 00:21:23.760
I<00:21:15.200> think<00:21:15.679> you<00:21:16.400> and<00:21:16.720> your<00:21:16.960> predecessor<00:21:17.520> you've<00:21:17.840> been<00:21:18.000> very<00:21:18.799> mindful<00:21:19.200> and<00:21:19.520> savvy<00:21:20.000> in<00:21:20.400> using<00:21:20.960> partners<00:21:21.760> for<00:21:22.080> certain<00:21:22.400> pieces<00:21:22.720> of<00:21:22.880> the<00:21:23.120> message
00:21:23.760 --> 00:21:31.600
to<00:21:24.000> support<00:21:24.320> it<00:21:24.559> with<00:21:25.120> we<00:21:25.360> had<00:21:25.520> somebody<00:21:25.679> on<00:21:25.840> the<00:21:26.000> team<00:21:26.240> who<00:21:26.400> did<00:21:26.480> a<00:21:26.640> cons<00:21:27.039> data<00:21:27.280> center<00:21:27.520> consolidation<00:21:28.159> in<00:21:28.400> the<00:21:28.480> line<00:21:28.960> or<00:21:29.360> you<00:21:29.600> put<00:21:29.840> the<00:21:30.240> consultant<00:21:30.720> in<00:21:30.880> the<00:21:31.039> front<00:21:31.280> seat
00:21:31.600 --> 00:21:38.880
when<00:21:32.080> otherwise<00:21:32.480> it's<00:21:32.720> just<00:21:32.880> getting<00:21:33.120> political<00:21:33.600> for<00:21:33.840> the<00:21:34.000> political<00:21:34.880> reason<00:21:35.360> right<00:21:35.679> so<00:21:35.919> I<00:21:36.080> think<00:21:36.240> the<00:21:36.559> good<00:21:36.720> use<00:21:36.960> of<00:21:37.200> partnerships<00:21:37.760> where<00:21:38.000> we're<00:21:38.159> all<00:21:38.320> aligned<00:21:38.720> on
00:21:38.880 --> 00:21:47.360
where<00:21:39.185> we<00:21:39.490> want<00:21:39.796> to<00:21:40.101> go<00:21:40.406> but<00:21:40.711> sometimes<00:21:41.016> you<00:21:41.321> have<00:21:41.627> to<00:21:41.932> have<00:21:42.237> somebody<00:21:42.542> else<00:21:42.847> say<00:21:43.153> it<00:21:43.458> because<00:21:43.763> it<00:21:44.068> just<00:21:44.373> comes<00:21:44.679> across<00:21:44.984> differently<00:21:45.289> <00:21:45.594> and<00:21:45.899> I<00:21:46.204> think<00:21:46.510> you<00:21:46.815> you've<00:21:47.120> used
00:21:47.360 --> 00:21:49.440
that<00:21:47.611> really<00:21:47.863> well<00:21:48.114> over<00:21:48.366> the<00:21:48.617> years.<00:21:48.869> <00:21:49.120> Yeah.
00:21:49.440 --> 00:21:56.000
<00:21:49.768> The<00:21:50.097> talk<00:21:50.425> in<00:21:50.753> business<00:21:51.082> terms.<00:21:51.410> I<00:21:51.739> love<00:21:52.067> what<00:21:52.395> you<00:21:52.724> added<00:21:53.052> about<00:21:53.380> how<00:21:53.709> you<00:21:54.037> communicate<00:21:54.366> the<00:21:54.694> value<00:21:55.022> of<00:21:55.351> the<00:21:55.679> county.
00:21:56.000 --> 00:22:00.159
I<00:21:56.159> think<00:21:56.240> sometimes<00:21:56.559> that<00:21:56.799> actually<00:21:56.960> gets<00:21:57.280> missed.<00:21:57.600> What<00:21:57.760> does<00:21:57.840> the<00:21:58.000> val<00:21:58.240> what<00:21:58.320> does<00:21:58.400> the<00:21:58.559> value<00:21:58.720> actually<00:21:58.960> mean<00:21:59.120> to<00:21:59.280> you<00:21:59.360> in<00:21:59.600> the<00:21:59.679> county?
00:22:00.159 --> 00:22:03.760
I<00:22:00.320> love<00:22:00.559> the<00:22:00.799> value<00:22:01.039> and<00:22:01.280> risk<00:22:01.679> balance<00:22:02.400> is<00:22:03.120> really<00:22:03.440> good.
00:22:03.760 --> 00:22:08.000
And<00:22:03.919> then<00:22:04.480> the<00:22:04.880> ability<00:22:05.360> to<00:22:06.400> you<00:22:06.640> mentioned<00:22:06.799> the<00:22:07.039> five<00:22:07.280> board<00:22:07.520> members.
00:22:08.000 --> 00:22:13.520
So<00:22:08.253> I<00:22:08.505> think<00:22:08.758> understanding<00:22:09.010> the<00:22:09.263> board<00:22:09.515> members<00:22:09.768> even<00:22:10.021> in<00:22:10.273> Santa<00:22:10.526> Barbara<00:22:10.778> County<00:22:11.031> there<00:22:11.284> we<00:22:11.536> have<00:22:11.789> a<00:22:12.041> local<00:22:12.294> it's<00:22:12.546> called<00:22:12.799> Noozhawk.
00:22:13.520 --> 00:22:20.320
I'm<00:22:13.840> usually<00:22:14.159> most<00:22:14.400> curious<00:22:14.720> around<00:22:15.120> it's<00:22:15.360> hey<00:22:15.520> we're<00:22:15.600> going<00:22:15.679> to<00:22:15.840> pass<00:22:16.000> this<00:22:16.240> budget<00:22:16.559> and<00:22:16.720> then<00:22:16.880> you<00:22:17.039> get<00:22:17.200> to<00:22:17.360> hear<00:22:17.760> the<00:22:18.000> folks<00:22:18.320> talk<00:22:18.559> about<00:22:19.120> and<00:22:19.360> then<00:22:19.600> which<00:22:19.840> departments
00:22:20.320 --> 00:22:22.960
are<00:22:20.667> like<00:22:21.013> bullish<00:22:21.360> on<00:22:21.707> AI.<00:22:22.053> <00:22:22.400> Yeah.
00:22:22.960 --> 00:22:30.080
<00:22:23.186> Yeah.<00:22:23.411> <00:22:23.637> And<00:22:23.863> so<00:22:24.089> you<00:22:24.314> can<00:22:24.540> kind<00:22:24.766> of<00:22:24.991> hear<00:22:25.217> okay<00:22:25.443> this<00:22:25.669> is<00:22:25.894> what<00:22:26.120> they<00:22:26.346> care<00:22:26.571> about<00:22:26.797> that<00:22:27.023> makes<00:22:27.249> sense<00:22:27.474> and<00:22:27.700> so<00:22:27.926> you<00:22:28.151> get<00:22:28.377> the<00:22:28.603> different<00:22:28.829> priorities<00:22:29.054> some<00:22:29.280> overlap
00:22:30.080 --> 00:22:34.240
some<00:22:30.464> don't<00:22:30.848> but<00:22:31.232> you<00:22:31.616> also<00:22:32.000> talk<00:22:32.383> about<00:22:32.767> the<00:22:33.151> consultant<00:22:33.535> coming<00:22:33.919> in.
00:22:34.240 --> 00:22:38.000
Have<00:22:34.480> you<00:22:34.640> ever<00:22:34.880> been<00:22:35.039> in<00:22:35.200> that<00:22:35.360> position<00:22:36.000> where<00:22:36.400> you<00:22:36.640> were<00:22:36.799> in<00:22:36.960> the<00:22:37.039> front<00:22:37.280> seat?
00:22:38.000 --> 00:22:40.880
<00:22:38.800> Yes.<00:22:39.600> <00:22:40.400> Yeah.
00:22:40.880 --> 00:22:44.080
Tell<00:22:41.039> us<00:22:41.120> more.<00:22:41.280> We<00:22:41.440> had<00:22:41.600> one<00:22:41.760> in<00:22:41.919> the<00:22:42.080> data<00:22:42.320> consolidation<00:22:43.440> process.
00:22:44.080 --> 00:22:52.080
There<00:22:44.240> was<00:22:44.320> a<00:22:44.480> lot<00:22:44.559> of<00:22:44.640> contention<00:22:45.200> around<00:22:45.600> just<00:22:45.919> certain<00:22:46.240> elements<00:22:46.559> of<00:22:46.799> control<00:22:47.280> in<00:22:47.600> the<00:22:47.919> governance<00:22:48.400> process<00:22:49.200> and<00:22:49.520> we<00:22:49.679> had<00:22:49.919> one<00:22:50.159> meeting<00:22:50.640> where<00:22:50.960> I<00:22:51.280> think<00:22:51.520> the<00:22:51.760> vast
00:22:52.080 --> 00:23:01.440
majority<00:22:52.480> of<00:22:52.640> the<00:22:52.799> county<00:22:53.200> CIOs<00:22:53.679> were<00:22:53.840> all<00:22:54.000> in<00:22:54.159> one<00:22:54.400> room<00:22:54.960> and<00:22:55.360> we<00:22:55.679> had<00:22:55.919> thought<00:22:56.240> that<00:22:56.480> we<00:22:56.640> had<00:22:56.880> agreed<00:22:57.280> on<00:22:57.919> the<00:22:58.240> final<00:22:58.960> roles<00:22:59.280> and<00:22:59.440> responsibilities<00:23:00.799> and
00:23:01.440 --> 00:23:09.840
turned<00:23:01.679> out<00:23:01.840> in<00:23:02.000> the<00:23:02.159> meeting<00:23:02.480> that<00:23:02.720> was<00:23:02.799> not<00:23:02.960> the<00:23:03.120> case<00:23:03.760> and<00:23:04.159> it<00:23:04.480> was<00:23:04.799> one<00:23:05.039> of<00:23:05.120> the<00:23:05.280> more<00:23:05.440> pretentious<00:23:06.000> meetings<00:23:06.400> of<00:23:06.640> my<00:23:06.880> career<00:23:07.520> and<00:23:07.840> I<00:23:08.000> was<00:23:08.159> front<00:23:08.400> and<00:23:08.640> center<00:23:09.200> just
00:23:09.840 --> 00:23:14.000
taking<00:23:10.080> the<00:23:10.320> shots<00:23:11.200> watching<00:23:11.679> the<00:23:12.000> fireworks<00:23:12.559> but<00:23:12.720> we<00:23:12.960> worked<00:23:13.120> through<00:23:13.360> it.<00:23:13.679> Right.
00:23:14.000 --> 00:23:21.360
It<00:23:14.159> was<00:23:14.320> important<00:23:14.640> and<00:23:14.799> I<00:23:14.960> think<00:23:15.039> it<00:23:15.200> would<00:23:15.360> have<00:23:15.440> been<00:23:16.080> it<00:23:16.320> would<00:23:16.480> it<00:23:16.799> could<00:23:17.039> have<00:23:17.200> had<00:23:17.360> a<00:23:17.600> different<00:23:18.000> outcome<00:23:18.480> or<00:23:18.720> a<00:23:18.880> longer<00:23:19.280> story<00:23:19.520> to<00:23:19.840> it<00:23:20.080> had<00:23:20.320> this<00:23:20.480> been<00:23:20.799> the<00:23:20.960> county
00:23:21.360 --> 00:23:23.520
CIO<00:23:21.919> kind<00:23:22.080> of<00:23:22.159> as<00:23:22.400> a<00:23:22.559> party<00:23:22.799> in<00:23:23.039> there.
00:23:23.520 --> 00:23:27.280
I<00:23:23.760> was<00:23:23.919> not<00:23:24.240> partial<00:23:24.640> to<00:23:24.880> anything.<00:23:25.440> I<00:23:25.600> was<00:23:25.760> just<00:23:26.000> there<00:23:26.240> to<00:23:26.400> do<00:23:26.559> the<00:23:26.720> right<00:23:26.880> thing.
00:23:27.280 --> 00:23:32.559
<00:23:27.524> Yeah.<00:23:27.768> <00:23:28.012> And<00:23:28.257> so<00:23:28.501> that's<00:23:28.745> that<00:23:28.989> happens<00:23:29.233> and<00:23:29.477> that's<00:23:29.722> why<00:23:29.966> you<00:23:30.210> sometimes<00:23:30.454> need<00:23:30.698> a<00:23:30.942> third<00:23:31.187> party<00:23:31.431> in<00:23:31.675> the<00:23:31.919> mix.
00:23:32.559 --> 00:23:41.200
<00:23:32.864> Specifically<00:23:33.168> when<00:23:33.473> you<00:23:33.778> move<00:23:34.082> from<00:23:34.387> 42<00:23:34.692> data<00:23:34.996> centers<00:23:35.301> to<00:23:35.606> to<00:23:35.910> a<00:23:36.215> consolidated<00:23:36.519> set<00:23:36.824> of<00:23:37.129> data<00:23:37.433> centers,<00:23:37.738> you<00:23:38.043> really<00:23:38.347> a<00:23:38.652> lot<00:23:38.957> of<00:23:39.261> it<00:23:39.566> is<00:23:39.871> about<00:23:40.175> perceived<00:23:40.480> control.
00:23:41.200 --> 00:23:47.280
And<00:23:41.360> so<00:23:41.520> a<00:23:41.760> lot<00:23:41.840> of<00:23:41.919> the<00:23:42.159> discussions<00:23:42.559> that<00:23:42.799> we<00:23:42.960> had<00:23:43.360> to<00:23:43.600> work<00:23:43.840> through<00:23:44.000> those<00:23:44.240> issues<00:23:44.559> was<00:23:44.799> like<00:23:45.120> what<00:23:45.440> parts<00:23:45.760> do<00:23:45.919> you<00:23:46.000> really<00:23:46.240> want<00:23:46.480> to<00:23:46.720> control?
00:23:47.280 --> 00:23:54.240
Do<00:23:47.440> you<00:23:47.600> want<00:23:47.760> to<00:23:47.919> control<00:23:48.159> the<00:23:48.480> utility<00:23:48.960> or<00:23:49.200> do<00:23:49.360> you<00:23:49.520> want<00:23:49.600> to<00:23:49.760> control<00:23:50.080> where<00:23:50.240> it<00:23:50.480> makes<00:23:50.640> sense<00:23:50.880> and<00:23:51.120> where<00:23:51.280> it<00:23:51.440> matters<00:23:52.000> at<00:23:52.240> the<00:23:52.480> application<00:23:53.039> level<00:23:53.360> and<00:23:53.600> at<00:23:53.760> the<00:23:53.919> data
00:23:54.240 --> 00:23:57.200
level?<00:23:54.720> And<00:23:54.960> yes<00:23:55.200> and<00:23:55.360> the<00:23:55.520> answer<00:23:55.760> was<00:23:56.080> yeah<00:23:56.320> generally<00:23:56.640> that's<00:23:56.880> true.
00:23:57.200 --> 00:24:01.200
Then<00:23:57.600> let's<00:23:57.840> take<00:23:58.080> out<00:23:58.240> all<00:23:58.400> the<00:23:58.640> other<00:23:58.880> stuff<00:23:59.440> off<00:23:59.600> your<00:23:59.760> plate<00:24:00.000> so<00:24:00.159> that<00:24:00.240> you<00:24:00.400> don't<00:24:00.480> have<00:24:00.640> to<00:24:00.720> worry<00:24:00.880> about<00:24:00.960> it.
00:24:01.200 --> 00:24:08.080
So<00:24:01.280> they<00:24:01.520> can<00:24:01.679> do<00:24:01.760> more<00:24:02.000> of<00:24:02.159> that.<00:24:02.559> But<00:24:02.880> what<00:24:03.120> are<00:24:03.280> the<00:24:03.360> things<00:24:03.600> now<00:24:03.919> to<00:24:04.080> challenge<00:24:04.400> our<00:24:04.799> internal<00:24:05.280> services<00:24:05.760> department<00:24:06.320> was<00:24:06.799> what<00:24:06.960> are<00:24:07.120> the<00:24:07.280> things<00:24:07.440> that<00:24:07.760> needs<00:24:08.000> to
00:24:08.080 --> 00:24:15.440
be<00:24:08.159> there<00:24:08.480> and<00:24:08.559> the<00:24:08.799> transparency<00:24:09.520> and<00:24:09.760> the<00:24:09.919> cost<00:24:10.480> transparency<00:24:11.039> and<00:24:11.200> everything<00:24:11.520> about<00:24:11.760> that<00:24:12.320> that<00:24:12.559> you<00:24:12.799> would<00:24:13.120> require<00:24:13.520> to<00:24:13.760> provide<00:24:14.320> to<00:24:14.559> the<00:24:14.799> departments<00:24:15.120> that<00:24:15.360> are
00:24:15.440 --> 00:24:17.919
going<00:24:15.520> to<00:24:15.679> be<00:24:15.760> consuming<00:24:16.240> this<00:24:16.559> utility<00:24:17.039> the<00:24:17.279> services.
00:24:17.919 --> 00:24:21.279
So<00:24:18.061> a<00:24:18.203> lot<00:24:18.344> of<00:24:18.486> these<00:24:18.628> consulting<00:24:18.770> work<00:24:18.912> that<00:24:19.054> we<00:24:19.195> do<00:24:19.337> and<00:24:19.479> a<00:24:19.621> lot<00:24:19.763> of<00:24:19.904> the<00:24:20.046> work<00:24:20.188> that<00:24:20.330> we<00:24:20.472> do<00:24:20.614> out<00:24:20.755> of<00:24:20.897> the<00:24:21.039> office.
00:24:21.279 --> 00:24:28.559
So<00:24:21.360> the<00:24:21.520> CIO<00:24:21.919> is<00:24:22.080> kind<00:24:22.240> of<00:24:22.320> like<00:24:22.640> bridging<00:24:23.120> those<00:24:23.440> conversations<00:24:24.320> right<00:24:24.480> and<00:24:24.720> facilitating<00:24:25.440> it<00:24:25.600> so<00:24:25.760> that<00:24:25.919> we<00:24:26.080> can<00:24:26.320> begin<00:24:26.559> to<00:24:26.799> then<00:24:27.120> say<00:24:27.600> this<00:24:27.840> is<00:24:27.919> how<00:24:28.080> we<00:24:28.240> would<00:24:28.480> want
00:24:28.559 --> 00:24:30.799
to<00:24:28.720> do<00:24:28.799> it<00:24:28.960> and<00:24:29.200> this<00:24:29.279> is<00:24:29.440> how<00:24:29.600> we're<00:24:29.760> going<00:24:29.840> to<00:24:29.919> proceed<00:24:30.240> forward.
00:24:30.799 --> 00:24:34.080
So,<00:24:31.039> I<00:24:31.200> like<00:24:31.360> what<00:24:31.520> you<00:24:31.679> last<00:24:31.919> said<00:24:32.080> about<00:24:32.320> bridging<00:24:32.720> the<00:24:32.960> conversations.
00:24:34.080 --> 00:24:40.400
I<00:24:34.320> think<00:24:34.400> that's<00:24:34.799> really<00:24:35.120> great.<00:24:35.360> It's<00:24:35.600> one<00:24:35.760> of<00:24:35.919> those<00:24:36.080> phrases<00:24:37.039> that<00:24:38.080> sounds<00:24:39.039> really<00:24:39.440> easy<00:24:39.679> to<00:24:39.840> do.
00:24:40.400 --> 00:24:46.240
Leadership<00:24:40.880> is<00:24:41.120> very<00:24:41.440> hard.<00:24:42.080> Communication<00:24:42.720> is<00:24:43.279> very<00:24:43.600> hard<00:24:44.080> with<00:24:44.320> lots<00:24:44.640> of<00:24:44.799> different<00:24:44.960> organizations<00:24:45.760> folks.
00:24:46.240 --> 00:24:50.159
Craig<00:24:46.559> Groeschel,<00:24:47.039> he<00:24:47.200> say<00:24:47.279> this<00:24:47.440> a<00:24:47.520> lot,<00:24:47.679> but<00:24:47.840> he'll<00:24:48.000> say<00:24:48.159> when<00:24:48.320> the<00:24:48.400> leader<00:24:48.640> gets<00:24:48.799> better,<00:24:49.120> everyone<00:24:49.440> gets<00:24:49.679> better.
00:24:50.159 --> 00:24:56.000
And<00:24:50.400> I<00:24:50.559> think<00:24:51.120> so<00:24:51.440> much<00:24:51.919> of<00:24:52.720> really<00:24:53.120> everything<00:24:53.520> rests<00:24:53.840> and<00:24:54.000> falls<00:24:54.320> on<00:24:54.640> the<00:24:54.960> leadership.
00:24:56.000 --> 00:24:58.400
And<00:24:56.320> so,<00:24:56.480> I<00:24:56.640> love<00:24:56.799> the<00:24:56.960> bridging<00:24:57.360> the<00:24:57.600> conversations.
00:24:58.400 --> 00:25:04.159
That's<00:24:58.618> another<00:24:58.835> really<00:24:59.053> great<00:24:59.270> phrase.<00:24:59.488> I'm<00:24:59.706> going<00:24:59.923> to<00:25:00.141> go<00:25:00.358> steal<00:25:00.576> that<00:25:00.794> and<00:25:01.011> actually<00:25:01.229> say<00:25:01.446> borrow<00:25:01.664> it<00:25:01.882> and<00:25:02.099> give<00:25:02.317> that<00:25:02.534> over<00:25:02.752> to<00:25:02.970> some<00:25:03.187> CIOs<00:25:03.405> that<00:25:03.622> I<00:25:03.840> know.
00:25:04.159 --> 00:25:12.080
But<00:25:04.240> I<00:25:04.400> did<00:25:04.559> want<00:25:04.640> to<00:25:04.799> transition.<00:25:05.279> I<00:25:05.360> I<00:25:05.760> love<00:25:05.919> the<00:25:06.240> partnership,<00:25:06.799> this<00:25:07.120> long-term<00:25:08.400> partnership<00:25:08.960> between<00:25:09.440> that<00:25:09.679> you<00:25:09.919> have<00:25:10.080> with<00:25:10.320> Hanis,<00:25:10.960> with<00:25:11.120> InfoTech.
00:25:12.080 --> 00:25:20.720
I<00:25:12.400> think<00:25:12.799> one<00:25:13.120> of<00:25:13.200> the<00:25:13.440> benefits<00:25:14.080> of<00:25:14.480> long-term<00:25:15.120> partnerships<00:25:15.600> that<00:25:15.840> often<00:25:16.159> doesn't<00:25:16.400> get<00:25:16.559> talked<00:25:16.880> about<00:25:17.039> a<00:25:17.200> lot<00:25:17.679> is<00:25:17.919> the<00:25:18.240> compounding<00:25:18.960> effect<00:25:19.279> of<00:25:19.520> trust<00:25:20.320> and
00:25:20.720 --> 00:25:24.240
you<00:25:21.039> your<00:25:21.360> ability<00:25:21.600> to<00:25:21.840> move<00:25:22.080> faster<00:25:22.480> because<00:25:22.799> you<00:25:23.039> have<00:25:23.120> that<00:25:23.440> trust.
00:25:24.240 --> 00:25:29.039
And<00:25:24.960> I<00:25:25.120> recently<00:25:25.440> recorded<00:25:25.679> an<00:25:25.840> interview<00:25:26.080> with<00:25:26.320> Tim<00:25:26.559> Blosser,<00:25:27.039> the<00:25:27.279> state<00:25:27.520> CIO<00:25:27.840> of<00:25:28.000> Nevada.
00:25:29.039 --> 00:25:34.320
He<00:25:29.279> was<00:25:29.440> recounting<00:25:29.919> last<00:25:30.240> year<00:25:30.880> about<00:25:31.279> the<00:25:31.840> largest<00:25:32.159> ransomware<00:25:32.720> attack<00:25:33.039> in<00:25:33.279> state<00:25:33.520> history.
00:25:34.320 --> 00:25:43.440
I<00:25:34.559> actually<00:25:34.720> recorded<00:25:35.120> an<00:25:35.440> episode<00:25:36.159> the<00:25:36.559> day<00:25:36.799> before<00:25:37.200> that<00:25:37.600> happened<00:25:38.159> with<00:25:38.480> Tim<00:25:38.960> and<00:25:39.200> Alan<00:25:39.520> Fuller<00:25:39.840> at<00:25:40.000> the<00:25:40.159> state<00:25:40.240> of<00:25:40.400> Utah<00:25:40.960> and<00:25:41.120> and<00:25:41.520> Bill<00:25:41.840> at<00:25:42.000> the<00:25:42.080> state<00:25:42.240> of<00:25:42.400> Washington.
00:25:43.440 --> 00:25:49.200
<00:25:43.716> And<00:25:43.992> so<00:25:44.268> the<00:25:44.544> four<00:25:44.820> of<00:25:45.096> us,<00:25:45.372> we<00:25:45.648> have<00:25:45.924> this<00:25:46.200> conversation,<00:25:46.476> this<00:25:46.752> podcast,<00:25:47.028> and<00:25:47.304> the<00:25:47.580> next<00:25:47.856> day<00:25:48.132> I<00:25:48.408> get<00:25:48.684> an<00:25:48.960> email.
00:25:49.200 --> 00:25:52.480
They're<00:25:49.360> like,<00:25:49.440> "Do<00:25:49.760> not<00:25:49.919> release<00:25:50.159> this<00:25:50.400> episode<00:25:50.720> yet."
00:25:52.480 --> 00:25:56.400
<00:25:52.832> It's<00:25:53.184> just<00:25:53.536> all<00:25:53.888> caps,<00:25:54.240> red,<00:25:54.592> emergency<00:25:54.944> emoji,<00:25:55.296> the<00:25:55.648> whole<00:25:56.000> thing.
00:25:56.400 --> 00:26:04.080
Yeah.<00:25:56.720> So<00:25:56.960> then<00:25:57.120> eventually<00:25:57.440> I<00:25:57.600> released<00:25:57.840> the<00:25:58.080> episode<00:25:58.480> and<00:25:58.720> so<00:25:59.279> following<00:25:59.600> that<00:25:59.919> almost<00:26:00.159> a<00:26:00.320> year<00:26:00.480> later<00:26:00.880> we<00:26:01.039> have<00:26:01.200> Tim<00:26:01.520> back<00:26:01.679> on<00:26:01.840> the<00:26:02.000> show<00:26:02.480> and<00:26:02.799> with<00:26:03.120> Mark<00:26:03.360> Hellsbush
00:26:04.080 --> 00:26:12.559
from<00:26:04.458> InfoTech<00:26:04.836> recounting<00:26:05.215> how<00:26:05.593> InfoTech<00:26:05.971> really<00:26:06.349> showed<00:26:06.727> up<00:26:07.105> not<00:26:07.484> just<00:26:07.862> as<00:26:08.240> a<00:26:08.618> vendor<00:26:08.996> but<00:26:09.375> as<00:26:09.753> a<00:26:10.131> partner<00:26:10.509> <00:26:10.887> and<00:26:11.265> we<00:26:11.644> actually<00:26:12.022> recounted<00:26:12.400> some
00:26:12.559 --> 00:26:20.880
of<00:26:12.720> those<00:26:13.279> really<00:26:13.600> intense<00:26:14.000> moments<00:26:14.400> and<00:26:14.960> I'd<00:26:15.279> love<00:26:15.440> to<00:26:15.600> hear<00:26:16.320> uh<00:26:16.480> I'd<00:26:16.720> love<00:26:16.799> to<00:26:16.960> hear<00:26:17.039> from<00:26:17.279> you<00:26:17.520> first<00:26:17.919> on<00:26:18.320> I<00:26:18.559> think<00:26:19.200> generally<00:26:20.240> what<00:26:20.480> you<00:26:20.720> look
00:26:20.880 --> 00:26:23.440
for<00:26:21.120> and<00:26:21.279> the<00:26:21.440> difference<00:26:21.600> between<00:26:21.919> a<00:26:22.159> vendor<00:26:22.480> and<00:26:22.720> a<00:26:22.880> partner.
00:26:23.440 --> 00:26:26.400
Certainly<00:26:23.840> a<00:26:24.000> more<00:26:24.159> obvious<00:26:24.480> things<00:26:24.720> is<00:26:24.960> a<00:26:25.120> partner<00:26:25.440> is<00:26:25.600> long-term,<00:26:26.159> right?
00:26:26.400 --> 00:26:35.120
And<00:26:26.559> that<00:26:26.720> long-term<00:26:27.200> is<00:26:27.360> not<00:26:27.520> just<00:26:27.760> because<00:26:28.080> of<00:26:28.320> just<00:26:28.799> the<00:26:29.120> time<00:26:29.279> that<00:26:29.520> you<00:26:29.679> guys<00:26:29.919> work<00:26:30.159> together,<00:26:30.559> but<00:26:31.039> that<00:26:31.279> that<00:26:31.360> that<00:26:32.080> duration<00:26:32.720> also<00:26:33.440> allows<00:26:34.240> the<00:26:34.640> partner
00:26:35.120 --> 00:26:42.559
to<00:26:35.360> really<00:26:35.600> understand<00:26:36.559> the<00:26:36.799> county<00:26:37.200> and<00:26:37.360> our<00:26:37.600> pain<00:26:37.840> points<00:26:38.240> and<00:26:38.480> our<00:26:38.720> challenges<00:26:39.360> and<00:26:39.679> the<00:26:39.919> things<00:26:40.320> and<00:26:40.559> more<00:26:40.720> importantly<00:26:41.120> our<00:26:41.440> strategies<00:26:41.919> and<00:26:42.080> what<00:26:42.240> we're<00:26:42.400> trying
00:26:42.559 --> 00:26:48.880
to<00:26:42.720> accomplish.<00:26:43.360> That<00:26:43.600> partnership<00:26:44.240> and<00:26:44.400> that<00:26:44.640> trust<00:26:45.039> is<00:26:45.360> really<00:26:45.679> important<00:26:46.000> because<00:26:46.240> of<00:26:46.480> that<00:26:46.640> longevity<00:26:47.120> of<00:26:47.279> of<00:26:47.600> that<00:26:47.840> relationship.
00:26:48.880 --> 00:26:50.799
new<00:26:49.200> partners<00:26:49.760> that<00:26:50.080> come<00:26:50.320> on<00:26:50.559> board.
00:26:50.799 --> 00:26:57.919
We<00:26:51.039> have<00:26:51.440> new<00:26:51.679> vendors<00:26:52.000> and<00:26:52.159> new<00:26:52.400> partners<00:26:52.640> that<00:26:52.799> that<00:26:53.200> we<00:26:53.360> begin<00:26:53.600> to<00:26:53.760> build<00:26:53.919> those<00:26:54.159> partnerships<00:26:54.640> is<00:26:54.880> one<00:26:55.200> coming<00:26:55.440> into<00:26:55.679> the<00:26:55.919> door<00:26:56.400> demonstrating<00:26:56.960> that<00:26:57.200> you're<00:26:57.440> not
00:26:57.919 --> 00:27:05.520
selling<00:26:58.159> a<00:26:58.480> product<00:26:58.720> or<00:26:59.039> service,<00:26:59.679> but<00:26:59.919> more<00:27:00.320> here's<00:27:00.640> how<00:27:00.880> we're<00:27:01.039> going<00:27:01.120> to<00:27:01.279> work<00:27:01.440> with<00:27:01.679> you<00:27:02.000> to<00:27:02.320> help<00:27:02.559> address<00:27:03.279> this<00:27:03.600> particular<00:27:04.000> initiative<00:27:04.480> and<00:27:04.720> execute<00:27:05.120> on<00:27:05.279> some
00:27:05.520 --> 00:27:09.919
of<00:27:05.600> these<00:27:05.760> things.<00:27:06.159> Partnerships<00:27:06.720> happens<00:27:07.039> in<00:27:07.360> different<00:27:07.760> levels<00:27:08.320> and<00:27:08.480> different<00:27:08.720> levels<00:27:09.039> of<00:27:09.279> engagement.
00:27:09.919 --> 00:27:18.240
And<00:27:10.198> so<00:27:10.476> you<00:27:10.755> have<00:27:11.034> to<00:27:11.312> almost<00:27:11.591> kind<00:27:11.870> of<00:27:12.148> be<00:27:12.427> sustained<00:27:12.706> and<00:27:12.984> then<00:27:13.263> if<00:27:13.542> you're<00:27:13.820> new<00:27:14.099> to<00:27:14.377> be<00:27:14.656> able<00:27:14.935> to<00:27:15.213> really<00:27:15.492> come<00:27:15.771> in<00:27:16.049> with<00:27:16.328> a<00:27:16.607> understanding<00:27:16.885> of<00:27:17.164> where<00:27:17.443> we<00:27:17.721> are<00:27:18.000> and
00:27:18.240 --> 00:27:25.840
what<00:27:18.480> we<00:27:18.640> are<00:27:18.799> challenged<00:27:19.039> with<00:27:19.279> and<00:27:19.440> what<00:27:19.600> we're<00:27:19.760> trying<00:27:19.840> to<00:27:20.000> accomplish<00:27:20.640> and<00:27:20.880> then<00:27:21.120> truly<00:27:21.440> partner<00:27:21.679> with<00:27:21.840> us<00:27:22.080> because<00:27:22.320> no<00:27:22.640> project<00:27:23.279> will<00:27:23.520> go<00:27:24.320> as<00:27:24.559> planned<00:27:24.960> right<00:27:25.200> adjustments
00:27:25.840 --> 00:27:27.840
need<00:27:26.080> to<00:27:26.240> be<00:27:26.320> made<00:27:26.799> things<00:27:27.039> have<00:27:27.200> to<00:27:27.279> be<00:27:27.520> done.
00:27:27.840 --> 00:27:34.159
We<00:27:28.080> try<00:27:28.320> to<00:27:28.720> county<00:27:29.440> and<00:27:29.600> public<00:27:29.840> sector<00:27:30.480> we<00:27:30.640> have<00:27:30.720> a<00:27:30.880> statement<00:27:31.200> of<00:27:31.440> work<00:27:31.760> deliverables<00:27:32.720> and<00:27:32.960> task<00:27:33.360> and<00:27:33.600> so<00:27:33.760> forth.
00:27:34.159 --> 00:27:41.520
When<00:27:34.240> we<00:27:34.400> get<00:27:34.480> into<00:27:34.720> a<00:27:34.880> plan,<00:27:35.200> reality<00:27:35.600> hits.<00:27:36.080> Things<00:27:36.400> need<00:27:36.559> to<00:27:36.720> be<00:27:36.880> adjusted,<00:27:37.440> plans<00:27:37.840> need<00:27:38.000> to<00:27:38.159> be<00:27:38.240> adjusted,<00:27:38.799> deliverables<00:27:39.440> need<00:27:39.679> to<00:27:39.760> be<00:27:39.919> reconfigured<00:27:40.640> and<00:27:40.880> so<00:27:41.039> forth.
00:27:41.520 --> 00:27:49.279
So<00:27:41.760> that<00:27:42.000> partnership<00:27:42.480> is<00:27:42.960> how<00:27:43.200> many<00:27:43.360> change<00:27:43.600> orders<00:27:43.919> do<00:27:44.080> you<00:27:44.240> put<00:27:44.320> into<00:27:44.640> us<00:27:44.799> and<00:27:45.120> how<00:27:45.360> do<00:27:45.440> we<00:27:45.679> work<00:27:45.840> with<00:27:46.080> you<00:27:46.240> to<00:27:46.559> accommodate<00:27:47.440> some<00:27:47.679> of<00:27:47.840> these<00:27:48.159> adjustments<00:27:48.720> that<00:27:49.039> we
00:27:49.279 --> 00:27:56.880
know<00:27:49.600> are<00:27:49.919> inherent<00:27:50.400> in<00:27:50.720> any<00:27:50.960> large<00:27:51.279> complex<00:27:51.840> projects<00:27:52.400> without<00:27:52.799> having<00:27:52.960> to<00:27:53.120> say<00:27:53.360> oh<00:27:53.520> there's<00:27:53.760> change<00:27:53.919> order<00:27:54.320> number<00:27:54.559> 26<00:27:55.120> and<00:27:55.360> this<00:27:55.600> is<00:27:55.679> what<00:27:55.840> it<00:27:56.000> means<00:27:56.159> and<00:27:56.399> this.
00:27:56.880 --> 00:27:59.600
So<00:27:57.120> what<00:27:57.200> does<00:27:57.360> that<00:27:57.520> partnership<00:27:58.000> look<00:27:58.159> like<00:27:58.320> and<00:27:58.559> how<00:27:58.640> do<00:27:58.799> you<00:27:58.880> execute<00:27:59.279> it?
00:27:59.600 --> 00:28:04.320
That's<00:27:59.840> what<00:28:00.000> build<00:28:00.320> trust,<00:28:00.880> right?<00:28:01.200> And<00:28:01.440> that's<00:28:01.679> built<00:28:01.919> that's<00:28:02.080> what<00:28:02.320> builds<00:28:02.640> commitment<00:28:03.039> and<00:28:03.200> truly<00:28:03.600> partnership.
00:28:04.320 --> 00:28:07.200
<00:28:04.465> Oh,<00:28:04.611> there<00:28:04.756> was<00:28:04.901> so<00:28:05.047> many<00:28:05.192> good<00:28:05.338> things<00:28:05.483> you<00:28:05.628> said<00:28:05.774> right<00:28:05.919> there.
00:28:07.200 --> 00:28:12.880
<00:28:07.436> I<00:28:07.672> think<00:28:07.908> you<00:28:08.145> nailed<00:28:08.381> it.<00:28:08.617> First,<00:28:08.853> you<00:28:09.089> don't<00:28:09.325> start<00:28:09.561> where<00:28:09.798> you<00:28:10.034> are<00:28:10.270> when<00:28:10.506> you've<00:28:10.742> had<00:28:10.978> that<00:28:11.214> time<00:28:11.451> to<00:28:11.687> build<00:28:11.923> that<00:28:12.159> relationship.
00:28:12.880 --> 00:28:15.600
So,<00:28:13.120> you<00:28:13.360> got<00:28:13.520> to<00:28:13.679> start<00:28:14.000> different<00:28:14.320> though.<00:28:14.480> You<00:28:14.640> said<00:28:14.799> different<00:28:15.039> levels,<00:28:15.440> right?
00:28:15.600 --> 00:28:19.520
I<00:28:15.760> love<00:28:15.919> that.<00:28:16.480> So,<00:28:16.960> you<00:28:17.200> start<00:28:17.520> I<00:28:17.679> think<00:28:17.919> how<00:28:18.080> do<00:28:18.159> you<00:28:18.320> build<00:28:18.559> that<00:28:18.799> trust?
00:28:19.520 --> 00:28:22.480
You<00:28:19.760> show<00:28:20.000> up,<00:28:20.559> you<00:28:20.799> listen.<00:28:21.840> Exactly.
00:28:22.480 --> 00:28:30.960
challenges,<00:28:23.279> pain<00:28:23.600> points,<00:28:24.480> and<00:28:24.640> then<00:28:24.960> over<00:28:25.279> time<00:28:26.000> when,<00:28:26.799> like<00:28:26.960> you<00:28:27.120> said,<00:28:27.360> no<00:28:27.520> project<00:28:27.919> ever<00:28:28.159> goes<00:28:28.720> according<00:28:29.120> to<00:28:29.679> it's<00:28:30.000> just<00:28:30.159> kind<00:28:30.240> of<00:28:30.320> fantasy<00:28:30.799> land
00:28:30.960 --> 00:28:38.240
to<00:28:31.120> think<00:28:31.440> everything<00:28:31.760> just<00:28:31.919> goes<00:28:32.159> perfectly,<00:28:33.120> but<00:28:33.360> you're<00:28:33.600> showing<00:28:33.840> up,<00:28:34.080> you're<00:28:34.320> probably<00:28:34.559> having<00:28:34.720> a<00:28:34.960> good<00:28:35.120> attitude,<00:28:36.159> you're<00:28:36.399> probably<00:28:36.640> willing<00:28:36.880> to<00:28:37.039> do<00:28:37.360> inconvenient,
00:28:38.240 --> 00:28:42.960
you're<00:28:38.480> probably<00:28:38.640> willing<00:28:38.880> to<00:28:39.039> take<00:28:39.200> calls<00:28:39.440> at<00:28:39.600> inconvenient<00:28:40.240> hours,<00:28:40.960> all<00:28:41.039> the<00:28:41.279> kind<00:28:41.360> of<00:28:41.440> things<00:28:41.600> that<00:28:41.919> build<00:28:42.320> trust.
00:28:42.960 --> 00:28:47.760
So,<00:28:43.200> Bahanas,<00:28:43.679> I'd<00:28:43.840> love<00:28:43.919> to<00:28:44.080> hear<00:28:44.399> from<00:28:44.720> you<00:28:45.360> as<00:28:45.600> you<00:28:45.840> started<00:28:46.080> to<00:28:46.399> make<00:28:47.200> that<00:28:47.440> jump.
00:28:47.760 --> 00:28:55.279
Was<00:28:48.000> there<00:28:48.159> a<00:28:48.320> specific<00:28:48.880> project<00:28:49.279> where<00:28:49.520> you<00:28:49.679> were<00:28:49.840> like,<00:28:50.080> "Hey,<00:28:50.480> now<00:28:50.720> I<00:28:50.960> feel<00:28:51.120> like<00:28:51.600> we're<00:28:51.919> really<00:28:52.240> having<00:28:52.559> that<00:28:52.960> really<00:28:53.520> strong<00:28:54.159> partnership."
00:28:55.279 --> 00:29:03.679
<00:28:55.602> Yes.<00:28:55.925> One<00:28:56.249> specific<00:28:56.572> moment<00:28:56.895> comes<00:28:57.218> to<00:28:57.542> mind<00:28:57.865> when<00:28:58.188> I<00:28:58.511> was<00:28:58.835> asked<00:28:59.158> to<00:28:59.481> meet<00:28:59.804> with<00:29:00.128> with<00:29:00.451> the<00:29:00.774> CIOs<00:29:01.097> Rich<00:29:01.421> Sanchez<00:29:01.744> then<00:29:02.067> at<00:29:02.390> the<00:29:02.714> time<00:29:03.037> and<00:29:03.360> Dean
00:29:03.679 --> 00:29:12.159
Logan<00:29:04.064> the<00:29:04.449> head<00:29:04.833> of<00:29:05.218> the<00:29:05.603> department<00:29:05.988> of<00:29:06.373> a<00:29:06.757> registrar-recorder<00:29:07.142> and<00:29:07.527> county<00:29:07.912> clerk<00:29:08.297> and<00:29:08.682> they<00:29:09.066> said<00:29:09.451> we<00:29:09.836> want<00:29:10.221> to<00:29:10.606> build<00:29:10.990> a<00:29:11.375> new<00:29:11.760> voting
00:29:12.159 --> 00:29:16.399
system.<00:29:12.388> <00:29:12.616> Y<00:29:12.845> <00:29:13.074> and<00:29:13.302> we<00:29:13.531> need<00:29:13.760> you<00:29:13.988> to<00:29:14.217> do<00:29:14.445> what<00:29:14.674> you<00:29:14.903> did<00:29:15.131> for<00:29:15.360> DHS.
00:29:16.399 --> 00:29:24.640
That<00:29:16.719> was<00:29:17.039> the<00:29:17.359> extent<00:29:17.679> of<00:29:17.999> initial<00:29:18.319> ask<00:29:18.639> <00:29:18.959> and<00:29:19.279> to<00:29:19.599> me<00:29:19.919> that<00:29:20.239> is<00:29:20.559> that<00:29:20.879> is<00:29:21.199> that<00:29:21.519> expression<00:29:21.839> of<00:29:22.159> we<00:29:22.479> want<00:29:22.799> to<00:29:23.119> do<00:29:23.439> something<00:29:23.759> impossible<00:29:24.079> that's<00:29:24.399> never
00:29:24.640 --> 00:29:33.760
been<00:29:24.799> done<00:29:25.039> before<00:29:25.840> and<00:29:26.080> we<00:29:26.320> are<00:29:26.480> asking<00:29:26.799> you<00:29:27.279> to<00:29:28.000> be<00:29:28.159> the<00:29:28.399> partner<00:29:28.799> through<00:29:29.039> this<00:29:29.520> and<00:29:29.760> I<00:29:29.919> think<00:29:30.080> what<00:29:30.320> it<00:29:30.559> shows<00:29:30.960> is<00:29:31.840> there's<00:29:32.080> a<00:29:32.240> professional<00:29:32.799> respect
00:29:33.760 --> 00:29:42.159
which<00:29:34.000> I<00:29:34.159> think<00:29:34.320> would<00:29:34.480> add<00:29:34.720> to<00:29:34.880> your<00:29:35.120> list<00:29:35.760> there<00:29:36.080> is<00:29:36.559> a<00:29:36.880> belief<00:29:37.440> that<00:29:37.840> we<00:29:38.000> have<00:29:38.080> a<00:29:38.240> partner<00:29:38.559> who<00:29:38.720> will<00:29:38.880> commit<00:29:39.120> to<00:29:39.279> the<00:29:39.520> cause<00:29:40.159> and<00:29:40.480> kind<00:29:40.640> of<00:29:40.720> stick<00:29:40.960> it<00:29:41.120> out<00:29:41.360> with<00:29:41.520> you
00:29:42.159 --> 00:29:46.080
and<00:29:42.399> then<00:29:42.559> I<00:29:42.799> think<00:29:42.880> there's<00:29:43.200> also<00:29:43.520> then<00:29:43.760> there's<00:29:44.000> the<00:29:44.159> element<00:29:44.480> of<00:29:44.720> being<00:29:45.039> honest<00:29:45.600> Right?
00:29:46.080 --> 00:29:49.760
We<00:29:46.640> I've<00:29:47.200> walked<00:29:47.760> away<00:29:48.320> from<00:29:48.880> projects,<00:29:49.440> right?
00:29:49.760 --> 00:29:54.960
When<00:29:50.000> you<00:29:50.320> think<00:29:50.559> you<00:29:50.799> cannot<00:29:51.279> do<00:29:51.440> it<00:29:51.679> or<00:29:52.320> the<00:29:52.559> time<00:29:52.799> has<00:29:53.039> come<00:29:53.279> where<00:29:53.520> you<00:29:53.679> no<00:29:53.919> longer<00:29:54.159> add<00:29:54.480> value.
00:29:54.960 --> 00:29:57.760
I<00:29:55.200> think<00:29:55.360> that<00:29:56.000> all<00:29:56.480> goes<00:29:56.799> into<00:29:57.120> that.
00:29:57.760 --> 00:29:59.760
<00:29:58.096> That<00:29:58.432> is<00:29:58.768> really<00:29:59.104> important,<00:29:59.440> right?
00:29:59.760 --> 00:30:01.919
Because<00:29:59.919> it<00:30:00.159> helps<00:30:00.399> build<00:30:00.799> credibility,<00:30:01.600> right?
00:30:01.919 --> 00:30:08.159
Commitment<00:30:02.320> to<00:30:02.480> the<00:30:02.720> cause<00:30:03.200> and<00:30:03.440> know<00:30:03.679> when<00:30:04.399> the<00:30:04.559> value<00:30:04.960> is<00:30:05.120> not<00:30:05.279> there<00:30:05.520> and<00:30:05.840> to<00:30:06.000> have<00:30:06.159> those<00:30:06.320> honest<00:30:06.720> conversations<00:30:07.200> with<00:30:07.440> their<00:30:07.600> clients.
00:30:08.159 --> 00:30:10.000
You<00:30:08.328> know<00:30:08.497> what?<00:30:08.666> I<00:30:08.835> know<00:30:09.003> you're<00:30:09.172> trying<00:30:09.341> to<00:30:09.510> do<00:30:09.679> this.
00:30:10.000 --> 00:30:13.760
I<00:30:10.320> understand<00:30:10.720> I'm<00:30:10.960> committed<00:30:11.200> to<00:30:11.360> your<00:30:11.520> mission,<00:30:11.840> but<00:30:12.159> maybe<00:30:12.399> we<00:30:12.559> need<00:30:12.640> to<00:30:12.799> do<00:30:12.880> a<00:30:13.039> reset,<00:30:13.520> right?
00:30:13.760 --> 00:30:18.080
and<00:30:14.000> be<00:30:14.159> able<00:30:14.320> to<00:30:14.480> have<00:30:14.640> those<00:30:14.960> frank<00:30:15.520> candid<00:30:16.000> conversations<00:30:16.640> and<00:30:16.960> know<00:30:17.200> when<00:30:17.440> to<00:30:17.600> do<00:30:17.679> that.
00:30:18.080 --> 00:30:23.679
The<00:30:18.240> other<00:30:18.399> thing<00:30:18.559> that<00:30:18.799> hers<00:30:19.200> didn't<00:30:19.360> mention<00:30:19.600> and<00:30:19.760> he's<00:30:20.000> done<00:30:20.080> this<00:30:20.320> multiple<00:30:20.720> times<00:30:20.880> in<00:30:21.120> our<00:30:21.360> partnership<00:30:21.679> with<00:30:21.840> a<00:30:22.080> different<00:30:22.480> project<00:30:22.720> that<00:30:22.880> we<00:30:23.039> worked<00:30:23.279> on.
00:30:23.679 --> 00:30:29.520
If<00:30:23.840> he<00:30:24.000> would<00:30:24.080> be<00:30:24.240> sitting<00:30:24.480> next<00:30:24.640> to<00:30:24.799> me<00:30:24.960> like<00:30:25.200> this<00:30:25.600> in<00:30:25.840> front<00:30:26.000> of<00:30:26.080> the<00:30:26.240> folks<00:30:26.559> that<00:30:26.799> would<00:30:26.880> be<00:30:27.039> the<00:30:27.200> issues<00:30:27.840> and<00:30:28.080> work<00:30:28.240> with<00:30:28.480> us,<00:30:28.960> right?
00:30:29.520 --> 00:30:35.840
Be<00:30:29.679> the<00:30:29.840> lightning<00:30:30.159> rod<00:30:30.480> for<00:30:30.720> a<00:30:30.880> lot<00:30:31.120> of<00:30:31.279> the<00:30:31.440> concerns<00:30:31.919> and<00:30:32.159> the<00:30:32.320> feedback<00:30:32.720> and<00:30:33.200> and<00:30:33.440> so<00:30:33.600> forth<00:30:33.840> and<00:30:34.000> how<00:30:34.159> do<00:30:34.320> we<00:30:34.480> work<00:30:34.640> together,<00:30:35.279> right?
00:30:35.840 --> 00:30:41.840
Meet<00:30:36.080> with<00:30:36.240> the<00:30:36.399> messaging<00:30:36.799> and<00:30:37.120> then<00:30:37.279> and<00:30:37.520> then<00:30:37.600> the<00:30:37.760> collaboration<00:30:38.559> to<00:30:38.799> work<00:30:39.120> right<00:30:39.360> in<00:30:39.600> the<00:30:39.760> trenches<00:30:40.399> to<00:30:40.720> execute<00:30:41.039> these<00:30:41.360> projects.
00:30:41.840 --> 00:30:43.840
That's<00:30:42.080> what<00:30:42.240> commitment<00:30:42.799> means,<00:30:43.360> right?
00:30:43.840 --> 00:30:49.200
And<00:30:43.919> it<00:30:44.000> has<00:30:44.159> it<00:30:44.399> ups<00:30:44.559> and<00:30:44.720> downs.<00:30:44.960> Sometimes<00:30:45.360> you<00:30:45.520> take<00:30:45.679> more<00:30:45.840> heat<00:30:46.240> than<00:30:46.480> you<00:30:46.640> need<00:30:46.799> to,<00:30:46.960> but<00:30:47.120> you<00:30:47.279> just<00:30:47.440> sit<00:30:47.600> there<00:30:47.679> and<00:30:47.840> just<00:30:48.000> work<00:30:48.240> through<00:30:48.399> it,<00:30:48.720> right?
00:30:49.200 --> 00:30:51.679
And<00:30:49.440> that's<00:30:49.679> what<00:30:50.000> builds<00:30:50.240> that<00:30:50.399> trust<00:30:50.720> and<00:30:50.880> that<00:30:51.039> relationship.
00:30:51.679 --> 00:31:00.080
<00:30:51.989> I<00:30:52.300> love<00:30:52.610> the<00:30:52.921> frank<00:30:53.231> and<00:30:53.542> and<00:30:53.852> I'm<00:30:54.163> laughing<00:30:54.473> because<00:30:54.783> Dominic<00:30:55.094> D'Ullo,<00:30:55.404> he's<00:30:55.715> been<00:30:56.025> on<00:30:56.336> the<00:30:56.646> podcast<00:30:56.956> before<00:30:57.267> in<00:30:57.577> Broward<00:30:57.888> County<00:30:58.198> and<00:30:58.509> he's<00:30:58.819> an<00:30:59.130> avid<00:30:59.440> listener.
00:31:00.080 --> 00:31:06.240
He<00:31:00.399> messages<00:31:01.039> me<00:31:01.200> and<00:31:01.520> goes,<00:31:01.840> "Do<00:31:02.080> you<00:31:02.240> know<00:31:02.320> how<00:31:02.480> many<00:31:02.720> times<00:31:03.039> you<00:31:03.279> say<00:31:03.679> love<00:31:03.919> it<00:31:04.080> on<00:31:04.320> a<00:31:04.480> podcast?"
00:31:06.240 --> 00:31:08.720
Every<00:31:06.480> time<00:31:06.640> I<00:31:06.799> say<00:31:06.880> it<00:31:07.120> now,<00:31:07.279> I<00:31:07.520> just<00:31:07.679> can't<00:31:07.840> stop<00:31:08.080> thinking<00:31:08.320> about<00:31:08.480> it.
00:31:08.720 --> 00:31:11.919
Cracks<00:31:09.039> me<00:31:09.120> up.<00:31:09.279> I'm<00:31:09.360> like,<00:31:09.520> you<00:31:09.679> listen<00:31:09.840> to<00:31:09.919> this<00:31:10.080> podcast<00:31:10.399> too<00:31:10.640> much.
00:31:11.919 --> 00:31:20.240
But<00:31:12.159> the<00:31:12.480> frank<00:31:12.880> candid<00:31:13.360> candid<00:31:14.159> conversations<00:31:15.200> I<00:31:15.440> think<00:31:15.600> that's<00:31:15.919> where<00:31:16.320> you<00:31:16.559> really<00:31:16.960> build<00:31:17.760> where<00:31:18.080> you<00:31:18.240> build<00:31:18.399> in<00:31:18.640> that<00:31:18.799> trust<00:31:18.960> that<00:31:19.200> you're<00:31:19.360> willing<00:31:19.600> to<00:31:19.760> have<00:31:20.000> those
00:31:20.240 --> 00:31:28.240
hard<00:31:20.559> doesn't<00:31:20.960> happen<00:31:21.200> at<00:31:21.440> first<00:31:21.840> but<00:31:22.320> whether<00:31:22.559> it's<00:31:22.799> in<00:31:22.960> marriage<00:31:23.360> or<00:31:23.679> in<00:31:23.919> business<00:31:24.640> being<00:31:24.880> able<00:31:25.120> to<00:31:25.440> have<00:31:25.600> those<00:31:25.919> honest<00:31:26.320> conversations<00:31:27.120> is<00:31:27.440> when<00:31:27.679> things<00:31:28.000> actually
00:31:28.240 --> 00:31:36.399
get<00:31:28.559> stronger.<00:31:29.039> I<00:31:29.279> coach<00:31:29.520> high<00:31:29.679> school<00:31:29.919> basketball<00:31:31.039> every<00:31:31.360> year<00:31:31.679> on<00:31:31.840> the<00:31:32.000> JV<00:31:32.480> team<00:31:32.880> you<00:31:33.200> get<00:31:33.760> the<00:31:34.000> best<00:31:34.240> freshman<00:31:34.640> go<00:31:34.720> up<00:31:34.880> to<00:31:35.039> JV<00:31:35.840> and<00:31:36.000> then<00:31:36.240> every
00:31:36.399 --> 00:31:38.960
year<00:31:36.659> you<00:31:36.919> lose<00:31:37.179> most<00:31:37.440> of<00:31:37.700> your<00:31:37.960> team<00:31:38.220> to<00:31:38.480> varsity.
00:31:38.960 --> 00:31:46.240
So,<00:31:39.200> it's<00:31:39.440> constantly<00:31:39.840> getting<00:31:40.080> reloaded.<00:31:40.880> And<00:31:41.039> what's<00:31:41.360> interesting<00:31:41.600> is<00:31:42.320> at<00:31:42.480> the<00:31:42.640> beginning<00:31:42.880> of<00:31:42.960> the<00:31:43.200> season<00:31:43.919> with<00:31:44.080> the<00:31:44.320> new<00:31:44.480> players,<00:31:45.120> there<00:31:45.279> isn't<00:31:45.519> that<00:31:45.760> trust.
00:31:46.240 --> 00:31:48.640
There<00:31:46.399> isn't<00:31:46.640> that<00:31:46.799> buy<00:31:46.960> in.<00:31:47.360> And<00:31:47.519> then<00:31:47.600> I<00:31:47.840> started<00:31:48.000> noticing<00:31:48.320> something.
00:31:48.640 --> 00:31:51.039
We<00:31:48.799> would<00:31:48.880> go<00:31:48.960> on<00:31:49.120> with<00:31:49.279> the<00:31:49.440> van<00:31:49.679> rides.<00:31:50.000> We'd<00:31:50.240> go<00:31:50.320> to<00:31:50.480> away<00:31:50.720> games.
00:31:51.039 --> 00:31:55.519
And<00:31:51.200> then<00:31:51.440> soon<00:31:52.080> we<00:31:52.240> stop<00:31:52.399> at<00:31:52.559> Chick-fil-A<00:31:53.039> or<00:31:53.200> the<00:31:53.279> kids<00:31:53.519> love<00:31:53.760> Canes<00:31:54.240> and<00:31:54.559> you'd<00:31:54.880> stop.
00:31:55.519 --> 00:31:59.679
And<00:31:55.760> suddenly<00:31:56.480> you<00:31:56.720> could<00:31:56.880> see<00:31:57.039> the<00:31:57.360> team<00:31:57.600> coming<00:31:57.840> together<00:31:58.159> and<00:31:58.320> I<00:31:58.480> was<00:31:58.559> like,<00:31:58.640> "Oh,<00:31:58.960> interesting.
00:31:59.679 --> 00:32:02.480
We<00:31:59.840> run<00:32:00.000> the<00:32:00.159> same<00:32:00.320> place,<00:32:00.880> but<00:32:01.200> now<00:32:01.600> there's<00:32:02.000> buy-in.
00:32:02.480 --> 00:32:05.440
Now<00:32:02.720> there's<00:32:02.960> trust.<00:32:03.600> The<00:32:03.840> turnovers<00:32:04.480> go<00:32:04.640> down.
00:32:05.440 --> 00:32:13.760
There's<00:32:05.840> less<00:32:06.159> miscommunication.<00:32:07.760> you<00:32:08.000> can<00:32:08.080> start<00:32:08.240> to<00:32:08.399> have<00:32:08.559> those<00:32:08.880> conversations<00:32:09.600> and<00:32:09.919> even<00:32:10.240> start<00:32:10.480> to<00:32:10.720> push,<00:32:11.279> hey,<00:32:11.919> I<00:32:12.159> noticed<00:32:12.640> that<00:32:13.440> here's
00:32:13.760 --> 00:32:20.559
where<00:32:14.000> you<00:32:14.159> are<00:32:14.320> right<00:32:14.559> now,<00:32:14.799> but<00:32:15.360> here's<00:32:15.679> where<00:32:15.760> I<00:32:16.000> actually<00:32:16.159> think<00:32:16.320> you<00:32:16.559> could<00:32:16.799> be<00:32:17.039> in<00:32:17.279> the<00:32:17.440> future,<00:32:18.159> which<00:32:18.320> I<00:32:18.480> think<00:32:18.559> is<00:32:18.720> an<00:32:18.880> important<00:32:19.120> part<00:32:19.279> of<00:32:19.440> leadership,<00:32:20.240> but
00:32:20.559 --> 00:32:25.919
in<00:32:20.720> being<00:32:20.960> able<00:32:21.120> to<00:32:21.279> have<00:32:21.440> those<00:32:21.679> honest<00:32:22.080> conversations<00:32:22.720> and<00:32:22.960> I<00:32:23.120> know<00:32:23.200> it<00:32:23.360> can<00:32:23.519> be<00:32:23.600> uncomfortable<00:32:24.240> cuz<00:32:24.399> there<00:32:24.640> are<00:32:24.799> different<00:32:25.039> personalities.
00:32:25.919 --> 00:32:30.480
My<00:32:26.159> wife,<00:32:26.480> she<00:32:26.640> would<00:32:26.799> probably<00:32:26.960> run<00:32:27.120> away<00:32:27.360> and<00:32:27.440> like,<00:32:27.600> hey,<00:32:27.760> we<00:32:27.919> should<00:32:28.000> have<00:32:28.159> a<00:32:28.480> Jamie<00:32:29.519> and<00:32:29.679> she's<00:32:30.000> gone.
00:32:30.480 --> 00:32:36.480
And<00:32:30.720> so<00:32:31.200> I'm<00:32:31.600> very<00:32:31.919> different.<00:32:32.399> If<00:32:32.559> like<00:32:32.799> Hanis<00:32:33.279> wants<00:32:33.440> to<00:32:33.519> get<00:32:33.679> hyped<00:32:34.000> up<00:32:34.159> on<00:32:34.399> me,<00:32:34.640> for<00:32:34.720> example,<00:32:35.200> I<00:32:35.360> would<00:32:35.519> probably<00:32:35.679> get<00:32:35.840> hyped<00:32:36.080> up,<00:32:36.320> too.
00:32:36.480 --> 00:32:40.000
Like<00:32:36.640> in<00:32:36.799> a<00:32:36.880> good<00:32:37.039> way,<00:32:37.279> just<00:32:37.440> 'cause<00:32:37.840> I'm<00:32:38.399> into<00:32:38.720> sports<00:32:39.039> and<00:32:39.200> all<00:32:39.279> that<00:32:39.440> kind<00:32:39.600> of<00:32:39.679> stuff.
00:32:40.000 --> 00:32:46.640
But<00:32:40.399> and<00:32:40.640> everyone's<00:32:40.960> a<00:32:41.039> little<00:32:41.120> bit<00:32:41.200> different.<00:32:41.440> But<00:32:41.600> I<00:32:41.760> love<00:32:41.840> the<00:32:42.320> regardless<00:32:42.720> of<00:32:43.039> how<00:32:43.279> you<00:32:43.519> communicate,<00:32:44.559> at<00:32:44.799> some<00:32:44.960> point<00:32:45.360> there'll<00:32:45.600> need<00:32:45.679> to<00:32:45.840> be<00:32:45.919> a<00:32:46.080> conversation
00:32:46.640 --> 00:32:49.039
that<00:32:46.880> needs<00:32:47.039> to<00:32:47.200> be<00:32:47.279> honest.<00:32:47.840> Hey,<00:32:48.080> here's<00:32:48.240> where<00:32:48.399> we're<00:32:48.559> at.
00:32:49.039 --> 00:32:52.320
Here<00:32:49.279> are<00:32:49.360> the<00:32:49.519> blockers.<00:32:50.480> This<00:32:50.640> is<00:32:50.720> a<00:32:50.960> red<00:32:51.200> flag.
00:32:52.320 --> 00:32:55.039
How<00:32:52.480> can<00:32:52.720> we<00:32:53.200> like<00:32:53.440> just<00:32:53.600> what<00:32:53.760> does<00:32:53.840> it<00:32:54.000> take<00:32:54.159> to<00:32:54.320> move<00:32:54.480> past?
00:32:55.039 --> 00:32:57.840
Yeah.<00:32:55.360> I<00:32:55.519> just<00:32:55.679> love<00:32:55.840> the<00:32:56.080> language.<00:32:56.720> Love<00:32:56.880> the<00:32:57.039> language<00:32:57.360> there.
00:32:57.840 --> 00:33:01.519
So,<00:32:58.000> as<00:32:58.240> we<00:32:58.399> start<00:32:58.559> to<00:32:59.200> turn<00:32:59.440> the<00:32:59.679> corner<00:32:59.840> on<00:33:00.080> the<00:33:00.240> podcast,<00:33:00.720> we<00:33:00.880> wrap<00:33:01.120> this<00:33:01.279> up.
00:33:01.519 --> 00:33:04.240
I'd<00:33:01.679> love<00:33:01.840> to<00:33:02.000> hear<00:33:02.080> from<00:33:02.240> you,<00:33:02.880> Peter,<00:33:03.200> and<00:33:03.440> then<00:33:03.600> Hanis.
00:33:04.240 --> 00:33:12.159
What's<00:33:04.640> one<00:33:05.440> piece<00:33:05.840> of<00:33:06.080> advice<00:33:06.480> that<00:33:06.799> you<00:33:06.960> would<00:33:07.120> leave<00:33:07.279> the<00:33:07.519> audience<00:33:07.840> with<00:33:08.159> of<00:33:08.640> I<00:33:08.880> really<00:33:09.120> want<00:33:09.279> this<00:33:09.519> partnership<00:33:10.000> but<00:33:10.240> it<00:33:10.399> takes<00:33:10.559> a<00:33:10.720> while<00:33:10.960> to<00:33:11.120> get<00:33:11.360> to.
00:33:12.159 --> 00:33:14.399
Where<00:33:12.399> should<00:33:12.559> I<00:33:12.799> start?<00:33:13.200> What<00:33:13.360> should<00:33:13.519> I<00:33:13.679> look<00:33:13.840> for?
00:33:14.399 --> 00:33:18.880
Maybe<00:33:14.662> there<00:33:14.925> are<00:33:15.188> younger<00:33:15.451> there<00:33:15.714> are<00:33:15.977> a<00:33:16.240> lot<00:33:16.502> of<00:33:16.765> up-and-coming<00:33:17.028> new<00:33:17.291> CIOs<00:33:17.554> in<00:33:17.817> public<00:33:18.080> sector.
00:33:18.880 --> 00:33:24.080
What<00:33:19.039> piece<00:33:19.200> of<00:33:19.360> advice<00:33:19.519> would<00:33:19.679> you<00:33:19.760> give<00:33:19.919> to<00:33:20.000> them?<00:33:20.320> Building<00:33:20.640> partnerships<00:33:21.120> and<00:33:21.360> being<00:33:21.760> an<00:33:22.080> effective<00:33:22.559> CIO<00:33:22.960> in<00:33:23.200> public<00:33:23.440> sector.
00:33:24.080 --> 00:33:28.559
Care<00:33:24.399> for<00:33:24.720> the<00:33:24.880> county's<00:33:25.279> mission.<00:33:25.760> Care<00:33:26.000> for<00:33:26.320> the<00:33:26.559> public<00:33:26.880> sector<00:33:27.440> mission<00:33:27.679> that<00:33:27.919> you're<00:33:28.159> in.
00:33:28.559 --> 00:33:32.320
Right.<00:33:28.880> I'm<00:33:29.200> doing<00:33:29.440> public<00:33:29.679> sector.<00:33:30.000> Been<00:33:30.159> doing<00:33:30.320> it<00:33:30.480> for<00:33:30.559> over<00:33:30.880> 30<00:33:31.120> years<00:33:31.360> because<00:33:31.519> I<00:33:31.840> love<00:33:32.000> it.
00:33:32.320 --> 00:33:37.360
Right.<00:33:32.720> You<00:33:33.039> can<00:33:33.200> see<00:33:33.360> the<00:33:33.679> impact<00:33:34.320> that<00:33:34.640> you<00:33:34.799> make<00:33:35.039> even<00:33:35.279> though<00:33:35.440> we're<00:33:35.679> working<00:33:35.840> on<00:33:36.000> IT<00:33:36.399> and<00:33:36.640> technology.
00:33:37.360 --> 00:33:45.279
You<00:33:37.519> can<00:33:37.679> see<00:33:37.840> the<00:33:38.080> impact<00:33:38.880> you<00:33:39.120> make<00:33:39.440> directly<00:33:40.080> in<00:33:40.320> the<00:33:40.559> services<00:33:40.960> that<00:33:41.120> are<00:33:41.360> being<00:33:41.519> enabled<00:33:41.919> by<00:33:42.080> what<00:33:42.320> you're<00:33:42.559> that's<00:33:42.799> what<00:33:43.039> excites<00:33:43.360> me<00:33:43.760> that<00:33:44.000> what's<00:33:44.320> keeps<00:33:44.559> me<00:33:44.799> going.
00:33:45.279 --> 00:33:53.679
The<00:33:45.440> other<00:33:45.679> thing<00:33:45.919> in<00:33:46.159> public<00:33:46.480> sector<00:33:46.880> especially<00:33:47.440> what<00:33:47.760> also<00:33:48.080> gives<00:33:48.320> me<00:33:48.640> excited<00:33:49.279> is<00:33:49.600> that<00:33:49.840> often<00:33:50.159> times<00:33:50.480> there<00:33:50.720> is<00:33:50.880> this<00:33:51.200> gap<00:33:51.760> between<00:33:52.159> what<00:33:52.640> the<00:33:52.880> leaders<00:33:53.440> wants
00:33:53.679 --> 00:33:57.919
to<00:33:53.919> accomplish<00:33:54.640> and<00:33:54.880> the<00:33:55.120> people<00:33:55.440> that<00:33:55.760> needs<00:33:56.000> to<00:33:56.240> be<00:33:56.399> part<00:33:56.799> and<00:33:57.120> understand<00:33:57.600> that.
00:33:57.919 --> 00:34:04.080
That's<00:33:58.159> why<00:33:58.320> in<00:33:58.559> our<00:33:58.799> projects<00:33:59.360> and<00:33:59.919> major<00:34:00.159> initiatives<00:34:00.720> let's<00:34:00.960> make<00:34:01.120> sure<00:34:01.200> we<00:34:01.440> understand<00:34:02.000> why<00:34:02.320> we<00:34:02.559> are<00:34:02.720> doing<00:34:03.039> this<00:34:03.600> right.
00:34:04.080 --> 00:34:11.359
So<00:34:04.240> because<00:34:04.559> as<00:34:04.799> we<00:34:05.039> go<00:34:05.200> through<00:34:05.440> challenges<00:34:06.000> as<00:34:06.240> challenges<00:34:06.640> will<00:34:06.880> always<00:34:07.120> come<00:34:07.360> up<00:34:07.760> in<00:34:08.000> large<00:34:08.240> initiatives<00:34:08.800> in<00:34:08.960> strate<00:34:09.359> implementing<00:34:10.000> strategies<00:34:10.720> we<00:34:10.960> can<00:34:11.040> always
00:34:11.359 --> 00:34:19.280
go<00:34:11.520> back<00:34:12.000> remember<00:34:12.320> why<00:34:12.639> we're<00:34:12.879> doing<00:34:13.040> this<00:34:13.359> and<00:34:13.599> how<00:34:13.839> do<00:34:14.000> we<00:34:14.159> then<00:34:14.480> get<00:34:14.639> there<00:34:15.119> and<00:34:15.359> so<00:34:15.520> forth<00:34:15.839> and<00:34:16.079> so<00:34:16.399> that<00:34:16.720> helps<00:34:16.960> us<00:34:17.200> anchor<00:34:17.599> it<00:34:17.839> and<00:34:18.079> being<00:34:18.240> able<00:34:18.480> to<00:34:18.720> bridge<00:34:19.040> that
00:34:19.280 --> 00:34:26.720
gap<00:34:19.520> between<00:34:20.079> the<00:34:20.320> executive<00:34:20.879> vision<00:34:21.520> and<00:34:21.760> be<00:34:21.919> able<00:34:22.079> to<00:34:22.320> translate<00:34:22.800> that<00:34:23.040> in<00:34:23.200> terms<00:34:23.359> of<00:34:23.520> here<00:34:23.760> are<00:34:23.839> the<00:34:24.079> things<00:34:24.480> that<00:34:24.720> could<00:34:24.960> enable<00:34:25.359> us<00:34:25.599> achieving<00:34:26.000> that<00:34:26.240> vision.
00:34:26.720 --> 00:34:33.599
That's<00:34:27.040> what's<00:34:27.520> that<00:34:27.760> was<00:34:28.000> really<00:34:28.320> important<00:34:28.560> and<00:34:28.800> that's<00:34:28.960> what<00:34:29.119> I<00:34:29.280> think<00:34:29.359> a<00:34:29.520> role<00:34:29.760> of<00:34:30.000> of<00:34:30.079> a<00:34:30.320> CIO<00:34:31.040> is<00:34:31.280> very<00:34:31.520> important<00:34:31.760> to<00:34:31.919> be<00:34:32.079> that<00:34:32.399> love<00:34:32.560> that<00:34:32.720> you<00:34:32.879> ever<00:34:33.040> read<00:34:33.440> start
00:34:33.599 --> 00:34:40.480
with<00:34:33.760> why<00:34:34.000> by<00:34:34.240> Simon<00:34:34.560> Sinek.<00:34:35.040> Yeah,<00:34:35.359> probably<00:34:36.960> one<00:34:37.200> of<00:34:37.359> those<00:34:38.000> very<00:34:39.119> easy<00:34:39.520> phrases,<00:34:40.240> right?
00:34:40.480 --> 00:34:48.079
But<00:34:40.639> what<00:34:40.879> I<00:34:40.960> love<00:34:41.119> is<00:34:41.359> when<00:34:41.520> you<00:34:41.679> start<00:34:41.919> getting<00:34:42.159> into<00:34:43.200> or<00:34:43.440> projects<00:34:43.919> start<00:34:44.159> to<00:34:44.320> become<00:34:44.639> tough,<00:34:45.119> things<00:34:45.359> start<00:34:45.599> happening,<00:34:46.480> going<00:34:46.720> back<00:34:46.879> up<00:34:47.040> to<00:34:47.200> that<00:34:47.359> why<00:34:47.679> level.
00:34:48.079 --> 00:34:50.159
Yeah.<00:34:48.560> So<00:34:48.800> crucial.<00:34:49.679> So<00:34:49.919> crucial.
00:34:50.159 --> 00:34:55.760
I<00:34:50.320> love<00:34:50.480> that.<00:34:50.960> I<00:34:51.119> said<00:34:51.200> it<00:34:51.359> again.<00:34:52.000> Really<00:34:52.240> cool<00:34:52.399> is<00:34:52.560> when<00:34:52.720> you<00:34:52.879> start<00:34:53.040> seeing<00:34:53.599> steering<00:34:53.919> committee<00:34:54.159> members<00:34:54.560> saying<00:34:54.720> the<00:34:54.879> same<00:34:55.040> thing,<00:34:55.280> right?
00:34:55.760 --> 00:35:01.920
remember<00:34:56.159> why<00:34:56.399> we're<00:34:56.560> doing<00:34:56.720> this<00:34:57.119> right<00:34:57.359> and<00:34:57.520> let's<00:34:57.760> focus<00:34:58.000> on<00:34:58.160> unless<00:34:58.640> figuring<00:34:58.880> out<00:34:59.040> how<00:34:59.200> to<00:34:59.280> get<00:34:59.440> there<00:34:59.680> right<00:35:00.079> then<00:35:00.320> you<00:35:00.480> know<00:35:00.640> it's<00:35:00.880> starting<00:35:01.119> to<00:35:01.200> kind<00:35:01.359> of<00:35:01.440> propagate
00:35:01.920 --> 00:35:08.240
so<00:35:02.160> it's<00:35:02.400> really<00:35:02.640> important<00:35:02.880> for<00:35:03.040> us<00:35:03.200> to<00:35:03.359> anchor<00:35:03.760> that<00:35:04.000> mission<00:35:04.480> fantastic<00:35:05.040> Hanis<00:35:05.520> three<00:35:05.839> things<00:35:06.000> I<00:35:06.320> would<00:35:06.480> point<00:35:06.720> out<00:35:06.960> so<00:35:07.119> the<00:35:07.359> first<00:35:07.440> one<00:35:07.599> you<00:35:07.760> mentioned<00:35:08.000> it's
00:35:08.240 --> 00:35:16.560
commitment<00:35:08.640> to<00:35:08.800> the<00:35:08.960> cause<00:35:09.599> you<00:35:09.839> can't<00:35:10.000> have<00:35:10.079> a<00:35:10.240> partnership<00:35:10.800> if<00:35:11.119> not<00:35:11.280> both<00:35:11.599> partners<00:35:11.920> are<00:35:12.160> committed<00:35:12.480> to<00:35:12.800> the<00:35:13.040> greater<00:35:13.359> good<00:35:13.680> the<00:35:13.760> why<00:35:14.320> the<00:35:14.560> second<00:35:14.800> one<00:35:15.200> is<00:35:16.079> as<00:35:16.320> a
00:35:16.560 --> 00:35:24.800
partner<00:35:17.119> in<00:35:17.760> public<00:35:18.160> with<00:35:18.560> public<00:35:18.880> sector<00:35:19.359> organizations<00:35:20.000> you<00:35:20.160> have<00:35:20.240> to<00:35:20.400> be<00:35:20.560> patient<00:35:20.880> and<00:35:21.200> persistent<00:35:22.079> it<00:35:22.320> takes<00:35:22.640> time<00:35:23.119> right<00:35:23.359> and<00:35:23.599> there's<00:35:23.839> often<00:35:24.560> things
00:35:24.800 --> 00:35:32.160
that<00:35:25.119> happen<00:35:25.440> that<00:35:25.760> you<00:35:26.240> wonder<00:35:26.640> why<00:35:26.880> and<00:35:27.119> you<00:35:27.280> have<00:35:27.359> to<00:35:27.599> understand<00:35:28.000> and<00:35:28.240> there's<00:35:28.480> usually<00:35:28.720> a<00:35:28.960> reason<00:35:29.200> or<00:35:29.440> a<00:35:29.680> process<00:35:30.000> or<00:35:30.320> something<00:35:30.720> and<00:35:30.960> the<00:35:31.119> third<00:35:31.359> point<00:35:31.680> I<00:35:32.000> think
00:35:32.160 --> 00:35:40.480
is<00:35:32.560> the<00:35:33.440> make<00:35:33.680> sure<00:35:33.920> that<00:35:34.640> we<00:35:35.040> work<00:35:35.359> together<00:35:35.760> as<00:35:36.000> a<00:35:36.240> we<00:35:36.720> we<00:35:37.280> have<00:35:37.359> a<00:35:37.520> contractual<00:35:38.079> relationships<00:35:38.800> right<00:35:39.040> and<00:35:39.280> that<00:35:39.599> alone<00:35:40.000> is<00:35:40.160> sometimes
00:35:40.480 --> 00:35:49.040
not<00:35:40.720> easy<00:35:40.960> to<00:35:41.200> actually<00:35:41.520> get<00:35:41.760> to<00:35:42.320> but<00:35:42.640> if<00:35:42.880> we<00:35:43.119> go<00:35:43.280> through<00:35:43.839> then<00:35:44.240> the<00:35:44.480> engagement<00:35:45.040> as<00:35:45.280> an<00:35:45.520> us<00:35:45.839> versus<00:35:46.240> them<00:35:46.960> it's<00:35:47.200> usually<00:35:47.520> not<00:35:47.760> a<00:35:47.920> good<00:35:48.079> ending<00:35:48.400> so<00:35:48.880> it
00:35:49.040 --> 00:35:54.880
is<00:35:49.200> what<00:35:49.280> it<00:35:49.440> is<00:35:49.520> what<00:35:49.760> we've<00:35:50.000> contracted<00:35:50.400> for<00:35:50.640> but<00:35:50.800> now<00:35:50.880> we<00:35:51.040> have<00:35:51.119> to<00:35:51.200> do<00:35:51.359> the<00:35:51.520> project<00:35:51.760> and<00:35:52.000> we're<00:35:52.240> committed<00:35:52.560> to<00:35:52.720> do<00:35:52.880> that<00:35:53.040> together<00:35:53.599> and<00:35:53.760> I<00:35:54.000> think<00:35:54.079> that's<00:35:54.320> what<00:35:54.640> that
00:35:54.880 --> 00:35:57.760
allows<00:35:55.200> us<00:35:55.359> to<00:35:56.160> offer<00:35:56.560> all<00:35:56.720> these<00:35:56.960> other<00:35:57.119> things<00:35:57.359> to<00:35:57.520> happen.
00:35:57.760 --> 00:36:03.599
And<00:35:57.920> that's<00:35:58.160> how<00:35:58.240> you<00:35:58.400> build<00:35:58.640> the<00:35:58.880> partnership<00:35:59.440> and<00:35:59.520> you<00:35:59.680> start<00:35:59.839> to<00:36:00.079> navigate<00:36:00.560> challenges<00:36:01.040> together<00:36:01.839> because<00:36:02.079> you're<00:36:02.320> committed<00:36:02.640> to<00:36:02.800> the<00:36:03.040> cause.
00:36:03.599 --> 00:36:08.240
You<00:36:03.920> have<00:36:04.160> the<00:36:04.400> right<00:36:04.640> patience<00:36:05.040> and<00:36:05.280> understanding<00:36:05.760> for<00:36:06.000> the<00:36:06.160> process<00:36:06.800> and<00:36:06.960> you<00:36:07.280> really<00:36:07.440> do<00:36:07.599> it<00:36:07.839> together.
00:36:08.240 --> 00:36:11.920
I<00:36:08.400> love<00:36:08.560> that.<00:36:08.800> With<00:36:08.960> that,<00:36:09.200> thank<00:36:09.359> you<00:36:09.440> for<00:36:09.599> coming<00:36:09.760> on<00:36:10.000> the<00:36:10.240> public<00:36:10.560> sector<00:36:10.880> show<00:36:11.040> by<00:36:11.200> Tech<00:36:11.440> Tables.
00:36:11.920 --> 00:36:15.359
Thank<00:36:12.079> you<00:36:12.240> for<00:36:12.400> having<00:36:12.560> me.<00:36:12.720> Thank<00:36:12.880> you.<00:36:13.200> Thank<00:36:13.359> you.
Chapters
No chapters for this episode.
Transcript
No transcript for this episode.
No matching lines.
Hosts & Guests
Hannes Scheidegger
Chief Global Services Officer | Helping Leaders Drive Measurable Business Value from IT
View profile