Artwork for podcast The Pair Program
Driving Government Modernization: Tales from GovTech Innovators | The Pair Program Ep. 41
Episode 412nd April 2024 • The Pair Program • hatch I.T.
00:00:00 01:01:47

Share Episode

Shownotes

Driving Government Modernization: Tales from GovTech Innovators | The Pair Program Ep. 41

In this episode, join our hosts as they engage in a thought-provoking conversation with Rob Murtha, the visionary CEO and Founder of Adjective, and Ken Kato, Vice President of DevSecOps & AI at Omni Federal.

Together, they explore the intricate landscape of tech innovation across diverse government domains, sharing insights on how engineering and product experts are crafting tailored solutions to address the unique needs of government agencies. From discussing the imperatives of GovTech modernization to revealing the transformative work they're currently undertaking, our guests offer invaluable perspectives on identifying governmental challenges and building effective solutions.Don't miss out on this enlightening discussion with two leading voices shaping the future of GovTech!

About Rob Murtha:

Rob's the CEO and Founder of Adjective, a Human Factors Design Company. Rob founded Adjective because he was passionate about building the bridge between deep automation, human productivity, and system instrumentation. Rob takes a systematic approach to learn about systems, craft processes that accommodate evolving industries, to move quickly and constantly create as much value for those systems as possible.

About Ken Kato:

Ken has led a journey that’s anything but typical. The start-up scene in Boston, then a bit of good weirdness at MIT Lincoln Labs and Mitre, found himself in meetings for ‘AOC Pathfinder’ that became what we know better today as Kessel Run, joined a White House Presidential Innovation Fellowship where he regularly tells people that friends don’t let friends accidentally start a new DevOps program in the government.

Sign-Up for the Weekly hatchpad Newsletter: https://www.myhatchpad.com/newsletter/

Transcripts

Tim Winkler:

Welcome to The Pair Program from hatchpad, the podcast that gives you

2

:

a front row seat to candid conversations

with tech leaders from the startup world.

3

:

I'm your host, Tim Winkler,

the creator of hatchpad.

4

:

And I'm your other host, Mike Gruen.

5

:

Join us each episode as we bring

together two guests to dissect topics

6

:

at the intersection of technology,

startups, and career growth.

7

:

Welcome back.

8

:

Another episode of The Pair Program.

9

:

Uh, Tim Winkler here, Mike Gruen, uh, my,

uh, co host Mike, what's going on, man?

10

:

I feel like we haven't, uh, seen

each other since the holidays.

11

:

Yeah, it's going all right.

12

:

Mike Gruen: Things, you know, uh, the

weather in DC is always fun, up and down,

13

:

cold, snow, rain, whatever, it's all good.

14

:

What about you?

15

:

How you doing?

16

:

Tim Winkler: Good, good, good

weather, uh, pitch there.

17

:

So let's talk about the weather.

18

:

I'm good, man.

19

:

Um, I was actually listening to

a podcast this morning and it was

20

:

talking about how Chipotle is kind

of scaling up staff right now.

21

:

Uh, did you know that

there's a burrito season?

22

:

I did not.

23

:

Yeah.

24

:

Burrito season is March to

May, so Chipotle is gearing up.

25

:

I'm pretty pumped.

26

:

Is there like a, uh, a go to, go

to burrito that you, uh, you roll

27

:

Mike Gruen: with?

28

:

So I'm a big fan of California tortilla,

which is like a local DC, um, chain.

29

:

Um, I've been going there since

the, like the, one of the first

30

:

franchises in Bethesda and I

know the owners and, um, yeah.

31

:

But is it that white

32

:

Tim Winkler: case?

33

:

So they have that white case.

34

:

So that's, is there some,

who's known for that good case?

35

:

So I think it's, uh, well, maybe it's

36

:

Mike Gruen: not, I mean, I like

their, theirs, but in Avon, um, I

37

:

don't know, but they make some really

good, like interesting, uh, burritos,

38

:

like they mix it up a little bit.

39

:

So I just like to.

40

:

I like to do like Korean barbecue

burrito or something a little

41

:

different or the, the shrimp one,

like not a traditional French toast

42

:

Rob Murtha: burrito.

43

:

Mike Gruen: Yeah.

44

:

I mean, back in the day they had

a tie, they had a tie burrito.

45

:

That was amazing.

46

:

I love it.

47

:

That's sick.

48

:

That's awesome.

49

:

It was

50

:

Tim Winkler: great.

51

:

Yep.

52

:

Breakfast burritos too are killer.

53

:

Had one as well.

54

:

They're a little young

on potatoes in there.

55

:

Yep.

56

:

Rob Murtha: So hungry.

57

:

Tim Winkler: We checked

weather, we checked burritos.

58

:

Let's move on.

59

:

Um, all right.

60

:

I'm, uh, I'm pumped to

tackle, uh, today's topic.

61

:

So if, if you've been a listener of the

pod, you know, that we've been releasing

62

:

a number of these episodes that are

centered around tech modernization

63

:

across different areas of the government.

64

:

So some of those past ones

have been like how to innovate

65

:

and agencies like defense or.

66

:

Go to market strategies for like dual

use tech startups trying to break their

67

:

products in the government markets.

68

:

Um, today we're going to dive a

little bit deeper into, you know,

69

:

how engineering and product folks are

actually like implementing solutions

70

:

for federal government customers.

71

:

Um, so we've got a couple of tech

leaders with us, uh, both have been very

72

:

involved in, in digital transformation

and in the public sector for.

73

:

A number of years, Rob, uh, Murtha,

uh, CEO and founder of adjective.

74

:

Rob brings a lot of experience to

the table within, um, areas of big

75

:

data analytics, product design, user

centered, uh, design UX research, uh,

76

:

private sector and government, uh,

portfolios he's, he's worked with.

77

:

So, um, uh, appreciate Rob being with us.

78

:

And also Rob served as a.

79

:

Uh, a senior analyst for the

army for, for a number of years.

80

:

Uh, and then we've got Ken Cato.

81

:

Uh, Kim is the vice president of

DevSecOps and AI at Omni Federal.

82

:

Uh, Ken served as an entrepreneur

in residence at the White House

83

:

Presidential Innovation Fellowship.

84

:

Uh, already said it, DevSecOps is,

is a big part of his, uh, focus.

85

:

Uh, does a lot of work delivering agile

development and solutions to, um, the

86

:

Navy and various other federal agencies.

87

:

Guys.

88

:

Thanks for joining us on the pod.

89

:

Thanks

90

:

Rob Murtha: for having us.

91

:

Yeah.

92

:

Tim Winkler: Good stuff.

93

:

All right.

94

:

Now, before we jump in, we always

kick things off with a fun segment

95

:

called pair me up, Mike, you usually

tee it up, go ahead and kick us off.

96

:

What do you got?

97

:

All right.

98

:

I'm pretty pleased with this one.

99

:

Mike Gruen: Uh, teenagers and Febreze.

100

:

If you have some teenage boys, you

have some stuff to look forward to.

101

:

So that's, uh, that, that was my pairing.

102

:

The last, uh, A couple of weeks,

that's been a, been trying to

103

:

track down some things and Febreze

has definitely come in handy.

104

:

Track down the scent, like

track down what's going on.

105

:

Yeah, a little bit of like,

what, why, what, what is this?

106

:

How old are your boys?

107

:

Uh, one's 17, one's 14.

108

:

Is sports, are they in, uh, I

think one plays baseball, right?

109

:

Yeah, yeah.

110

:

One plays baseball.

111

:

Yep.

112

:

Um, it's entirely just,

uh, he, uh, second base.

113

:

Oh, right.

114

:

He likes third base.

115

:

But, uh, we moved up to the big field

and, uh, as an eighth grader going from

116

:

third to first, that's a big throw.

117

:

So, um, , it's, you know, the

pro, we're on the professional

118

:

size team, so, uh, field rather.

119

:

So, uh, it's a's a, he's

moved over to second base.

120

:

That's a

121

:

Tim Winkler: teenage boys and Febreze.

122

:

You just bring these kids down with.

123

:

Yeah, exactly.

124

:

Freeze when they when

they walk in the door.

125

:

Now, mostly just a bedroom.

126

:

The hamper, especially the hamper.

127

:

It's all that good stuff.

128

:

All right.

129

:

I dig it.

130

:

I can I can see it.

131

:

I can relate to that.

132

:

I'll keep it.

133

:

Mike Gruen: That's for

134

:

Tim Winkler: you.

135

:

I'll keep the kid train.

136

:

I'll keep the kid train going.

137

:

I'm going to go with toddlers and forts.

138

:

Um, so like everybody has, you know,

those, those childhood memories of

139

:

building forts with like, um, you

know, blankets and pillows, but we

140

:

got this gift from my mother in law.

141

:

It's called a nugget couch and this thing

is, Oh dude, they're, they're so cool.

142

:

There's like, they've got an entire like

Instagram, like followers that just like

143

:

put out these crazy ideas of like, Hey,

this is what I did with my nugget couch.

144

:

Rob Murtha: And they vote

on the colors and stuff.

145

:

I mean, it's like the colors

146

:

Tim Winkler: for folks that don't know.

147

:

It's like, um, so it's,

it's, it's a couch.

148

:

It's made out of like four or

five, like big foam pieces.

149

:

And it's pretty sturdy.

150

:

Um, and you can just kind of put

these pieces in different areas

151

:

throughout, you know, throughout

the space that you've got it in.

152

:

So we, we put it in the basement and

we've got it, uh, connected to like

153

:

different pieces of our furniture that

we build, like these little tunnels that

154

:

lead to like a small little ball pit.

155

:

So it's just been a blast, um, for my

daughter and she's just, you know, getting

156

:

into that phase where I think she, she

doesn't quite understand what it is and

157

:

she'll appreciate it here in a year or so,

but I personally am having a lot of fun.

158

:

I think it's, it's a way for adults to

kind of get back into that childhood

159

:

phase of like Fort sort of the shit.

160

:

Yeah.

161

:

So, um, anyways, Yeah,

it's the truth, man.

162

:

It really gets your mind working.

163

:

Like what else can I do

with this thing here?

164

:

You know?

165

:

So anyways, I'm going to go

with the toddlers and forts

166

:

and, uh, and that's it for me.

167

:

Let's, let's kick it over to, uh, to

our guests, Ken, but a quick intro

168

:

and, uh, and, and your pairing.

169

:

Ken Kato: So the pairing I was thinking

about is Massachusetts and Dunkin Donuts.

170

:

So it's my wife.

171

:

So ordering Dunks in the

DMV area of Maryland, D.

172

:

C., Virginia is painful because

I actually had to say things out

173

:

loud, like the full name of things.

174

:

In New England, I just say, large regular.

175

:

That's it.

176

:

Tim Winkler: That's hilarious.

177

:

That's great.

178

:

That's great.

179

:

Yeah.

180

:

I, uh, I'm a fan of Duncan too.

181

:

I think they're facing a little

bit of a lawsuit right now.

182

:

Aren't they?

183

:

Somebody's like trying to come at

them for someone's trying to come at

184

:

them, uh, for, uh, they're using the

American disabilities act saying that

185

:

they were charged a surcharge for oat

milk, um, where, you know, they're

186

:

lactose intolerant and they shouldn't

have to, to pay that service fee.

187

:

It's like, anyways, I, I think,

uh, Duncan's probably just.

188

:

I'm going to poo poo that, just be

like, whatever here, take, take, take

189

:

some money they're doing just fine.

190

:

Pun intended on the

lactose intolerance and the

191

:

Mike Gruen: poo poo.

192

:

Yeah, poo poo, poo

193

:

Ken Kato: poo.

194

:

Mike Gruen: I'm lactose

intolerant, I can make that joke.

195

:

Ken Kato: The biggest dunk related

pun is their catch line, right?

196

:

America runs on dunks, or

dunking, and the basement of the

197

:

Pentagon, there's Dunkin Donuts.

198

:

And that's, that line is

always like murderously long.

199

:

I'm like, oh, America does

literally run on dunks, awesome.

200

:

Tim Winkler: That is so funny.

201

:

Yeah.

202

:

Uh, Rob, how about yourself, man?

203

:

Quick intro and, uh, your pairing.

204

:

Rob Murtha: Yeah.

205

:

Quick pairing.

206

:

Um, I guess similar to Mike,

like my, uh, so like, I guess

207

:

teenage kids and, and, and dances.

208

:

So I got two girls, 12 year old, uh,

12 years old and eight years old.

209

:

Um, the 12 year old is going to

like a Valentine's day dance.

210

:

And it's just like, you know,

I want to be a chaperone.

211

:

I want to, I want to be

like, what's going on.

212

:

It's like a couple of towns away.

213

:

It's just so hilarious.

214

:

So, I mean, we're, we're in

the Valentine's day season, so.

215

:

You know, funny, funny little, uh,

parenting wrinkle there, but I guess, you

216

:

know, we gotta, we gotta get used to it.

217

:

Um, and then quick intro.

218

:

Yeah.

219

:

You, I mean, you covered

my overview pretty well.

220

:

Uh, can it just for, for, you

know, Ken and I know each other

221

:

just from the Kessa run era.

222

:

And Ken's been an awesome

mentor of mine for years.

223

:

I mean, I've always hit him up with

any types of, you know, product

224

:

challenges I've come across,

you know, Um, entrepreneurial

225

:

challenges, technology challenges.

226

:

It's just been really fun.

227

:

Life challenges.

228

:

We both like, you know, know each

other's families really well.

229

:

So it's been fun just to like, you know,

self reflect and zoom out and have someone

230

:

you could rely on like that with Ken.

231

:

So it's, it's great to be

on this podcast with him.

232

:

Um, quick background for me.

233

:

You mentioned it kind of had a, had a

weird pathway, grew up in the Hamptons,

234

:

which was hilarious, went to art school,

um, graduated during the recession

235

:

in Florida, and I was like, uh, WTF.

236

:

Um, I ended up joining the military.

237

:

Nobody served in my family, uh, met

like a hilarious recruiter out at a bar.

238

:

And he was like, Oh, do you want to

be Jason Moore and go the Intel route?

239

:

Um, no, I ended up doing Intel

and definitely wasn't that like,

240

:

other than that, I didn't know

anything about the military.

241

:

I thought it was like Forrest Gump.

242

:

I thought like, you know, someone yelled

at me if I didn't clean my rifle, right.

243

:

Um, so ended up, uh, had, I had

like a really awesome experience.

244

:

I actually wrote like a little

blog on my, on my website.

245

:

A website, uh, talking about like

how we kind of started to introduce

246

:

customer experience elements to

operational stuff, not just like the

247

:

tech scene, but like how, how you can

wrap that around anything, not just,

248

:

you know, innovation, modernization.

249

:

Um, and that's kind of what we did.

250

:

Like we kind of, uh, productized,

uh, like our, our Intel

251

:

capabilities, which is really cool.

252

:

Um, just as like a team, we thought about

it from like a go to market strategy.

253

:

And we just had fun.

254

:

And so like, you know, right, right

after I got done with training, ended

255

:

up deploying Afghanistan and, and

had like a wild experience there, um,

256

:

came back and did some stuff stateside

and then ended up deploying again.

257

:

And it was like a completely

different setting.

258

:

So it was like another, another crazy fun

experience with like different variables.

259

:

Um, from there I became like an

IC, a trade craft instructor, um,

260

:

and, and curriculum developer.

261

:

Um, and that's kind of how I got

exposed to product design and fell

262

:

in love with like, uh, human factors

and, you know, really just building

263

:

experiences for people, um, that

align with either doctrine or tech

264

:

or whatever you're trying to kind

of associate those experiences with.

265

:

Um, and then from there I went to

the FBI and I was a product designer.

266

:

Um, built some really sick products there.

267

:

We can go into that later.

268

:

I'm sure we will.

269

:

When we get into the DevOps stuff

and then, uh, yeah, ended up at

270

:

KR, met Ken, met a bunch of really

cool people, had a blast there.

271

:

Um, and from there I just kind of, yeah,

like you mentioned, bouncing around the

272

:

ecosystem, doing startup stuff, doing

defense stuff, um, super opinionated about

273

:

a lot of things, just having that kind

of like multidimensional background where

274

:

it's been like, you know, operational,

um, you know, Product related stuff, you

275

:

know, product team stuff where I'm like

tactically in the trenches, just trying to

276

:

build things that solve people's problems.

277

:

So I'm just super grateful to have like

stumble into this like kind of community.

278

:

Awesome.

279

:

Tim Winkler: Yeah.

280

:

It's a tight knit community.

281

:

It's so tight knit that we've definitely

had like two or three other folks from

282

:

Kessel Run on the, on our podcast.

283

:

It's like a seven degrees of separation.

284

:

Like, uh, it's, it's wild.

285

:

Um, but I think what's It relevant, right?

286

:

And the reason like we like bringing

those folks in is because Kessel Run

287

:

was a big catalyst for, you know,

like how modernization can get, you

288

:

know, implemented and how there's this

need to fast forward things, right?

289

:

Like, can't, can't just be this slow

as molasses kind of transformation.

290

:

I know that that is a, a very

symbolic thing of trying to

291

:

do business in the government.

292

:

Right.

293

:

But, um, I think, you know, the

reality is that we're in a, We're

294

:

in an interesting time right now.

295

:

And, and we see it, you know, at hatch

anyways, because we, we've, we've done

296

:

a lot of stuff in GovTech back in the

day, and then we switched to commercial

297

:

product, and now we are getting back into

a lot more of this, you know, defense

298

:

tech, dual use tech, there's, there's

certainly a major shift in the technology

299

:

landscape, right, in, in government

towards modernization right now.

300

:

Um, but the reality is.

301

:

You know, there's still a cultural

and a procedural thing, a way of

302

:

doing things in the government.

303

:

Uh, you know, flexibility isn't really a,

a word that you hear thrown around a lot.

304

:

Um, but there is a way to

do it and it is being done.

305

:

And, and, you know, our goal with, with

this episode and with some of the other

306

:

episodes that we've been building here

is, is to build awareness for folks that

307

:

want to be a part of that, or Are building

something that, you know, can, can

308

:

help in one way, shape or fashion here.

309

:

And so, uh, super grateful to

have both of you guys on here.

310

:

What I like too, about the backgrounds

here, we, we hand selected is,

311

:

um, you know, can kind of have

a little bit more of a, like on

312

:

the engineering side of things.

313

:

more on that product

and design side as well.

314

:

So, you know, when our listeners,

our audience is usually a pretty

315

:

wide spectrum of folks from

product design, data engineering.

316

:

So we're hoping that we can hit on a few

of these different levels on, on how it's

317

:

done and, and some, some actual examples.

318

:

Uh, before we jump in, maybe it's helpful

just to hear just quick, uh, snippets of

319

:

like a bird's eye view of the type of work

that each of your all's firms are doing.

320

:

Uh, Ken, let's start with you, maybe at

a high level, just some of the work that

321

:

OmniFederal is delivering and the kind

of customers that you're supporting.

322

:

Ken Kato: Sure.

323

:

So today we focused largely

on defense and intel agencies.

324

:

So only about, you know, cut their

teeth in this world with NGA.

325

:

And since then it's gone pretty wide.

326

:

We have a lot of relationship with the

Air Force primarily, between platform

327

:

one, customer one, stuff like that.

328

:

Uh, my personal focus is on AI and

AI product development these days.

329

:

So I just had an idea recently

to, uh, build a small form

330

:

factor version of Code Llama.

331

:

So Code Llama, for those who may not

know, is a fine tuned version of Llama

332

:

for the purpose of code generation.

333

:

And why would I want to build

this when I can get to the cloud?

334

:

Well, that's why.

335

:

Right, the, there is no authority

to operate on AI instantiations

336

:

today, especially open source ones,

but if I build a physical computer

337

:

and drop it in someone's office,

AOs, authorizing officials, know how

338

:

to say yes or no to those things.

339

:

So my motivation there is to spend a

ludicrous amount of money for an H100 GPU

340

:

card, drop it into a box and literally,

you know, travel with a dog and pony show.

341

:

Here's my code.

342

:

Let me hook up to your BS code.

343

:

That's kind of stuff that I've

been working on these days.

344

:

Tim Winkler: Cool.

345

:

Yeah.

346

:

And we'll dissect some of that

as well as like how it's done

347

:

and the process to implement.

348

:

But, uh, Rob, how about yourself?

349

:

A little bit more on the adjective and

the type of work you all are doing.

350

:

Yeah.

351

:

Rob Murtha: Yeah, totally.

352

:

No, that's, that's awesome, Ken.

353

:

I love your approach to it.

354

:

So he's like lean and

practical, which is so exciting.

355

:

I love like your description there.

356

:

So adjective I just

launched about a year back.

357

:

It was like really, um, it was

actually a hilarious way that

358

:

I, uh, I launched my company.

359

:

It was pretty organic.

360

:

Ken was there for like when I initially

kicked it off, but I ended up just

361

:

getting a bunch of like demand and deal

flow, um, commercially and my, uh, my

362

:

mentor and, and, and, and, you know,

boss at the time, uh, Wes over at Clarity

363

:

and other, you know, services company.

364

:

It was like, dude, just jump for it.

365

:

Like being, you know, you, you've

always had like entrepreneurship

366

:

in your blood, very supportive.

367

:

A lot of people around me were like,

Hey, just, you know, give it a shot.

368

:

You know, cause there's been, there's

been situations in the past where

369

:

I've launched startups here and

there that are absolutely hilarious

370

:

and good segues at some point, um,

from from a podcast perspective and

371

:

you know, they, they either weren't

successful or I didn't put enough into

372

:

them or whatever it was this time.

373

:

It was like, I just had a lot of demand.

374

:

So I was like, you know what,

I'm going to give it a shot.

375

:

Don't really have a model to focus on

other than like Rob as a service or, you

376

:

know, startup athlete as a service, but

like my crazy box of, uh, um, and I ended

377

:

up just like straight up like building

the ship as I sailed it a little bit.

378

:

Um, and it was kind of cool.

379

:

I mean, you know, since we started, you

know, we've, we've kind of, uh, went, uh,

380

:

you know, a bunch of different directions.

381

:

And I think like the company's strategy,

um, you know, is, is kind of wrapped

382

:

with, with my vision of what product

design could become for, you know, the,

383

:

the, the, the whole market and what

it could evolve to with the advent of

384

:

generative AI and stuff, and also what

product design can realistically become

385

:

for the DOD and the public sector.

386

:

Um, I think like, you know, it's,

it's really hard to just lift and

387

:

shift perspectives and models and,

you know, you, you don't really,

388

:

you have to start somewhere.

389

:

Right.

390

:

So I'd say the first, you know, three

to five years of, of defense and

391

:

public sector innovation, we just

kind of had to lift and shift what

392

:

was successful in the private sector.

393

:

And we recruited a bunch of people

that had those perspectives.

394

:

Um, and then as you start to iterate,

as you, you know, start to try to

395

:

stitch those things into different

agencies, some of them work better

396

:

with those agencies than others, right?

397

:

You see a lot of, you see civic

tech just like blazing fast.

398

:

You see a lot of these different

organizations just adopting things very

399

:

easily because the way that they're set

up, the paradigm of those organizations

400

:

naturally align with, you know, Kind

of the private sector and some essence

401

:

of a market that, you know, they're

supporting public sector people.

402

:

They have huge hundred thousand user

accounts that are like putting in

403

:

simulating pressure on the features

and, and, and highlighting the

404

:

value of like UX work and stuff

versus defense, which is like.

405

:

a little more industrial, a

little more kind of small market

406

:

segments and, and nuance to how

you, how you go to market, right?

407

:

It's like a little more

challenging and different.

408

:

Um, so it's cool to see all of

those practices evolve and that's

409

:

kind of what I'm focusing on it.

410

:

Um, at adjective, I'm trying to figure

out ways to, you know, commercialize

411

:

product design, commercialize UX

methodologies, commercialize behavioral

412

:

psychology, and make it like super town.

413

:

tangible data driven results

oriented where people want

414

:

to sink their teeth into it.

415

:

And it's not like this, Oh, like make

sure we're satisfying section 508 or,

416

:

you know, some other kind of box check.

417

:

It needs to become this like

really rich thing that's tied

418

:

to success and risk reduction.

419

:

Tim Winkler: It's really fascinating, man.

420

:

I, I, um, I want to talk, maybe just

kind of like point this back to, uh, an

421

:

overarching point that I was reading a

blog that you had written, uh, it was,

422

:

or a social post that you had written.

423

:

It was about value creation, uh, and,

and the, the importance of producing

424

:

value for, for government customers.

425

:

You know, when you're walking

through like an engagement with,

426

:

with a customer, like, how are you.

427

:

You know, how do you get to the point of

like where you're, you're defining what

428

:

value means and like measuring this in

the context of like a digital solution?

429

:

Because I think that's like an area that,

you know, when you talk about end users

430

:

and the government or a specific agency.

431

:

Um, really like, uh, outlining the

specifics of the value that they'll

432

:

see, like, what does that mean to you?

433

:

Like how, you know, when, in that

post, like what, what, what were you

434

:

kind of like trying to allude to?

435

:

Rob Murtha: So something like I've

been really driving towards and

436

:

Ken, Ken will appreciate this.

437

:

And we, we talk about

this frequently together.

438

:

It's like, you know, what's the

equivalent of a marketplace in the DOD?

439

:

Like everyone has a customer,

regardless of whether you're like an

440

:

operational person, whether you're

like an, you know, HR practitioner, a

441

:

quartermaster, logistician, logistician,

You know, everyone has a market.

442

:

Everyone has a customer.

443

:

And like the faster that the DoD, the

faster that these agencies can like

444

:

adopt that mindset, the more kind of

value value focused people will be when

445

:

it comes to any kind of allocation of

capacity, any allocation of resources.

446

:

So what I'm, uh, to answer your question,

I, I think it's really tricky, right?

447

:

Every engagement's a little

different and, you know, you have to.

448

:

immediately start learning is as

soon as you get an opportunity to

449

:

work with one of these customers.

450

:

And I've had a number of engagements this

year, specifically public sector related,

451

:

and some of them are ongoing where, you

know, it's not a one size fits all, right?

452

:

You have to, I always say like model

your market, like understand, you

453

:

know, the elements of your market.

454

:

That, um, you know, introduce,

uh, incentives to the

455

:

people that depend on it.

456

:

And also, like, how, how can you

hold your practitioners and your

457

:

resource allocation accountable?

458

:

So those are two things

I'm very passionate about.

459

:

That's always been tough to measure and

implement in, in, in the government.

460

:

It's just challenging.

461

:

Like, how do you, How do you measure, you

know, how do you manage incentives, right?

462

:

When you have like very fixed policy

that you have to abide by with like

463

:

personnel and GS rates and like

people's ranks and promotion schedules.

464

:

It's all very like tied to policy.

465

:

That's beyond anyone's control.

466

:

There's like hacks that you can like

implement, but, um, Really, it's just

467

:

like, I don't know, I, the way I'd

respond to that is like, it's really

468

:

tied to the specific engagement.

469

:

One example, I'll give

you a great example.

470

:

So I'm working with a customer now and

you know, at the surface level, you see

471

:

everybody asking for the same stuff.

472

:

It's like, I want to be

a DevSecOps organization.

473

:

I want to be a software factory.

474

:

I want to be, you know, like all of

these like kind of big labels that

475

:

are like, you know, there's a ton

of nuance that exists below them.

476

:

Um, and you get in there and you

realize like just having experience in.

477

:

A private industry and then, and,

and be like at a software factory.

478

:

It's like, well, really you're

kind of more of like a skunk

479

:

works, like proof of concept shop.

480

:

Like you don't have the foundation to

do day two ops and, you know, manage

481

:

tier one, tier two, tier three help desk

and solve people's problems when bugs

482

:

surface and like things break and you

have to get stuff back online and whatnot.

483

:

And so like you start interacting

with the customers and you

484

:

know, the first step is like.

485

:

You know, getting them to culture, you

know, culturally getting them to trust

486

:

you and just like listening to them and

not like making them feel uncomfortable.

487

:

Like everyone, everyone has

a really strong opinion.

488

:

Um, and everyone has a perspective

and great experience to learn from.

489

:

Right.

490

:

I think that's something all like

digital transformation, people or

491

:

people supporting modernization

can really continue to kind

492

:

of gut check yourself with.

493

:

That's.

494

:

I got checked myself all the time.

495

:

It's like, you know, did what I, you

know, the way that I've framed advice or

496

:

recommendation or the way I'm like pairing

with this person, is it condescending?

497

:

You know, is it, you know,

how, how am I like seeing them?

498

:

How am I, how am I incorporating their

perspectives, even if they don't have

499

:

like some private industry exposure

or something, because everyone has

500

:

something really useful to contribute.

501

:

And, you know, a lot of the people

you work with are freaking brilliant.

502

:

They've been in these

program office for 20 years.

503

:

They've, done things with like legacy

VX rails that like nobody could imagine

504

:

where they stitch these things together

and deploy like, you know, Tanzu, um,

505

:

instantiations and they're like, you

know, to these like, you know, on prem,

506

:

you know, on prem hardware stacks.

507

:

And it's just, they, they've cobbled

together some really crazy stuff.

508

:

Like, I mean, ton of talent,

uh, talent all over the place.

509

:

Um, and it's kind of like, you know,

be self aware, you know, you know,

510

:

observe the situation, um, yeah.

511

:

And just always, always, always try

to like, I don't know, add, add data

512

:

and fidelity to the way that you

understand what it's going to take

513

:

to get them from moving to a place

of like arbitrary activities to

514

:

we're producing value for something.

515

:

And if there was some form of currency

in this environment, that like user

516

:

group or that customer, whatever,

however you classify it would be

517

:

willing to pay for the activities

that that program office is doing.

518

:

Tim Winkler: Yeah, that's,

that's well said, man.

519

:

And it is interesting because you're

dealing with a group of folks that, you

520

:

know, these end users, um, oftentimes

you said been, been there for 20 plus

521

:

years, you know, that's, that's, there's

value in being able to tap into that

522

:

and just be like, Hey, like, let's,

let's really understand like how things

523

:

have progressed over this timeline.

524

:

Um, we're oftentimes maybe you don't

get that of it, you don't have that,

525

:

uh, that advantage because somebody

has been there just for a few years

526

:

in that role or what have you.

527

:

Um, so it is unique, I think.

528

:

And when you're thinking, talking

about like the government as,

529

:

as that agency being the end

530

:

Mike Gruen: customer.

531

:

I think it's exciting that like that shift

in mindset, like when I worked with the

532

:

government in a number of places, there

was this like sort of captive audience.

533

:

Mindset of like, yeah, it

doesn't have to look good.

534

:

Like whatever, they'll deal with it.

535

:

Like it's like, it's sort of that like

mindset of like, yeah, they'll figure it

536

:

out there, whatever, like they just didn't

really want to put that much effort into

537

:

finding that value for who was essentially

their customer, but their customer had

538

:

no choice but to use them in some cases.

539

:

So there was sort of a, not much incentive

for them to really go after that.

540

:

So I think it's cool to, to sort of

really stress on how important it is

541

:

to think about your, who's using your

product and how to get them to value.

542

:

Rob Murtha: Mike, I totally want

to throw something out there.

543

:

You just reminded me of

something outrageous and fun.

544

:

And Ken's going to love this.

545

:

I'm going to pass it right over

to him, but Ken, you know what?

546

:

This reminds me of good old faths

that we never like really rolled out

547

:

that we still like, yeah, so one of

the things it's so funny, cause to

548

:

go back to your question, how do you

define success for these organizations?

549

:

I think it's more tactical.

550

:

It's all like kind of really understanding

their user groups, their customers,

551

:

kind of what their charter is, what

are they supposed to be delivering?

552

:

If there's like an operational community

at the other end, if they're kind of I

553

:

think one of the, the most interesting

ways to convert an organization from

554

:

like, you know, arbitrary ville to

like, let's generate value for someone

555

:

ville is like, You know, communicating

to them that everything's integrated.

556

:

Um, and that like, it really is.

557

:

And, and, and it's been impossible for

like, even like, you know, the joint

558

:

staff level to really appreciate that

this concept where it's like, if we

559

:

miss spend here, you know, especially,

you know, depending on the amount of

560

:

money, if we don't convert whatever

this kind of experiment is, whether

561

:

that's like a learning case study,

an artifact that can like become a

562

:

product and people can absorb and

learn from and, and make decisions by.

563

:

Um, or legitimately, we build a platform

that like does something like P1, where

564

:

like, you know, they facilitate DevSecOps

for a ton of different customers.

565

:

Like anytime you don't convert, that money

wasted is stealing from another portion of

566

:

your system, whether you like it or not.

567

:

And that portion of your system

could be something local where it's

568

:

like, you know, now, now, now, you

know, chicken wings are a little

569

:

more expensive and it sucks for me.

570

:

And instead of like being inspired

and, and excited to do stuff, I'm

571

:

going to be like a sad sack and

like sit in the house and like just

572

:

not, not think about that thing.

573

:

I should have ideated that.

574

:

The government could purchase

someday and build, you know,

575

:

like everything is integrated.

576

:

So it's like being serious

about your business, right?

577

:

Being serious about your program office.

578

:

Even if you have like some kind of,

I don't know, very, very reasonable

579

:

civilian style, you know, mission set,

it's still contributing to something

580

:

more tactical upstream or downstream.

581

:

And like, Finding ways to kind of

create those threads between everyone.

582

:

And it's like something that you might

not think is contributing to the conflict

583

:

and like Ucom whatever, absolutely is

contributing to influence operations.

584

:

It's contributing to just like the

joy and the confidence that our

585

:

service members have, whatever,

like everything's tied together.

586

:

Like the, the second that people start

adopting that perspective, they'll

587

:

start taking their stuff more seriously.

588

:

Ken, over to you.

589

:

Ken Kato: So the government

fully, you know, is.

590

:

The weird organization and that

it's got the most nonlinear

591

:

longest distance to a custom.

592

:

So if you're thinking about delivering

to like, especially like the defense

593

:

agencies, your ultimate delivery should

be to somebody that's really need this.

594

:

But as a developer, we

don't ever have that.

595

:

Apparently, like customer is unique that

we got to talk to for the operation basis.

596

:

That was, that's what made

customer successful, right?

597

:

So, We're not the only

organization who does this.

598

:

There are plenty of large bureaucracies

who does this on a regular basis.

599

:

I think about, you know, people who have

to lead large companies, like Len Roberts.

600

:

He ran RadarShack, most successful

CEO for RadarShack ever.

601

:

And he said this, This thing all the

time, they're really stuck with me.

602

:

You either are serving a customer or

serving someone who serves a customer.

603

:

So with that in mind, every time I

think about building anything for the

604

:

Department of Defense, for the White

House, any part of the government, I don't

605

:

think about what I want to do with it.

606

:

I can't, right?

607

:

And I also don't necessarily

have a customer to speak to.

608

:

So that means relying on that

20 plus year folks, like, Hey,

609

:

how have you done this and why?

610

:

And that why is what

makes it really revealing.

611

:

Because when you walk into any

government agency as a technologist,

612

:

it's easy to be looking at it and

going, okay, this is old quality tech.

613

:

Sure, it's easy to dismiss it.

614

:

But if you, when you dig deep, there is a

legitimate reason why it's the way it is.

615

:

It's not human laziness.

616

:

It's not the government's

bad in doing software.

617

:

It's not the above.

618

:

It's.

619

:

A lot of really smart people that came

up with the decision maybe a long time

620

:

ago, maybe they haven't updated since,

but there's also a risk to updating it.

621

:

So again, like they still get to

serve the customer mission, and that's

622

:

what we tend to forget to look at.

623

:

So when we look at all the program,

all the technology, especially, No

624

:

one asks a fundamental question,

are their customers happy?

625

:

Because at the end of the day, who

truly gives a shit if I make the

626

:

front end look shiny and newer?

627

:

Like that's just changing

the visual appearance.

628

:

That's not necessarily improving delivery

to the customer or delivering value.

629

:

I just made someone shiny.

630

:

Okay.

631

:

I can wax a car and make it shiny, it

doesn't make the car going faster, right?

632

:

So I keep thinking about that.

633

:

And then looking at those large companies.

634

:

And looking at how they consistently

deliver the same value, like when

635

:

we go to large theme parks, we're

almost guaranteed to have a great

636

:

experience short of the long lines.

637

:

But that being said, think about

the ridiculous logistics, right?

638

:

We're talking like tens of thousands

of employees who all Understand

639

:

the North Star of the theme park.

640

:

The customer has to have fun.

641

:

And they deliver on that every

single time because everyone

642

:

understands the North Star.

643

:

When we go to Castle Run, the North

Star is really well defined, right?

644

:

Deliver software to everyone we love.

645

:

When I did Black Pearl for the

Department of Navy, North Star

646

:

was really, really simple.

647

:

I want to teach the Navy how to do DevOps,

and then I frankly want to retire the

648

:

program because mission accomplished.

649

:

But without understanding the purpose of

why we do something, which is something

650

:

we often overlook, especially as a

technology going into older programs.

651

:

So, the thing that I always like

think about is, I remove myself

652

:

and go, hey, why do you do this?

653

:

Like, just tell me why, and

this is not a criticism, but

654

:

you need to hear why you do it.

655

:

And then at the end of it, that's when

I get to finally start thinking about,

656

:

okay, Let me buy some ideas off of you.

657

:

Is this something that's

going to be valuable to you?

658

:

If I change this way,

is this frustration bad?

659

:

Like tell me what's so hot right

now that you can't get away from it.

660

:

So that's kind of stuff.

661

:

Okay.

662

:

Mike Gruen: Yeah.

663

:

It's interesting.

664

:

Cause like when I, again, going back to

some, a little bit of my experience with

665

:

the government, I, in some cases, some

programs, I felt like I was just wearing

666

:

like these big heavy, like Mittens where

I couldn't actually touch or interact

667

:

with, have the fine grain, like feedback.

668

:

And I'm curious, like, as you work

with, as you, as you think about that,

669

:

if you were going to give advice to,

you know, a company that's trying to

670

:

get into the government, like, how do

you, how do you sort of deal with that?

671

:

Like I was blessed in some ways,

like some of the programs I worked

672

:

on, I did get to talk to the FBI.

673

:

I got to talk to like the analyst

that was going to be the end user.

674

:

And in other cases, they were so

distant and so compartmentalized.

675

:

I just, it was just, it was

a guessing game, and I'm just

676

:

curious, like, what advice you have.

677

:

Ken Kato: The first thing I taught

everybody coming into the White

678

:

House Veterans Innovation Fellowship,

so we mentor the new classes.

679

:

The first thing I teach is

ask a really, really simple

680

:

question and be genuine about it.

681

:

How can I help?

682

:

Those words are surprisingly powerful

because you have, you know, senior

683

:

bureaucrats who spent decades

in the government and just get

684

:

in by just defending themselves,

their decision, their funding.

685

:

So when someone walks in

and says, how can I help?

686

:

And zero agenda, simple question,

they actually hesitate to answer.

687

:

When you ask them again, when they

finally realize, I actually do want to

688

:

know, they It's a long conversation.

689

:

Sorry.

690

:

Mike Gruen: I'm smirking.

691

:

Cause I remember when we asked a similar

question and we did not get the response

692

:

we expected, basically the response

was, I don't, you can't help me.

693

:

Uh, I just have 2 million

I got to spend on you.

694

:

And I don't have time to explain

all the ways you can help me.

695

:

Ken Kato: I remember like

that's still an opening.

696

:

You have a long problem.

697

:

So let's get this.

698

:

Immediate problem solved, but

as I solve it, tell me more.

699

:

Mike Gruen: Right, exactly.

700

:

Right.

701

:

It took a lot of time to build that

trust and get them to really open up and

702

:

realize that we really were there to help.

703

:

We didn't have some agenda.

704

:

It wasn't just us trying to grab 2 million

because it was earmarked by Congress.

705

:

You know, it was like, we really

wanted to help solve problems.

706

:

So, yeah,

707

:

Tim Winkler: I'm curious, just in terms

of like for defense, uh, customers and

708

:

specifically specifically, I guess, um,

like Palantir is trailblazers in this

709

:

in terms of, you know, actually getting

out there and, um, sitting within users

710

:

when they're being deployed, uh, what,

how do you all get, how do you all get

711

:

into, uh, how do you gain access to those

folks that maybe, you know, might be more

712

:

difficult to, you know, to tap into if

there's, if you feel like there's these

713

:

layers that you have to cut through.

714

:

Um, is it something that you

can do off of a discovery call?

715

:

Does it take a little bit of time?

716

:

Like, what are some of the hacks or

strategies like when you're trying

717

:

to, to build, to, to get into that

mindset of those, of those end users?

718

:

Rob Murtha: I could, I could take

this one, Ken, and I'll pass it over.

719

:

Um, I think there's a variety of

things, you know, it's, I think it's,

720

:

it's, it's, you know, I think we both

have cheat codes cause we've kind of

721

:

been in the industry a little bit.

722

:

Um, and I, and it's, you know, I

constantly have to like remind myself how

723

:

kind of intimidating it might be sometimes

for people just because how everything's

724

:

like, it's everything's so theatrical,

you know, like all these like positions

725

:

and like, you know, for someone who

hasn't, you know, you know, been in the

726

:

military or, or kind of supported these.

727

:

Program offices, you, you hear these

ranks and these people and you, you

728

:

start, you know, it, it becomes just,

it's foreign to a lot of people.

729

:

So, you know, my advice, um, what, you

know, a, let me go back to Palantir

730

:

where I think they did really well.

731

:

Um, because you know, I was a user, I'm

actually a big fan of like the company.

732

:

I think they're very practical, um,

and, and they've, They've provided a

733

:

lot of value for a lot of people and

a lot of national security capability.

734

:

Just being like honest.

735

:

I know they have like a wild reputation.

736

:

Um, but

737

:

Tim Winkler: they have a role called

like forward deployed engineer,

738

:

like forward deployed engineer.

739

:

So it's totally around the user.

740

:

Rob Murtha: Yeah.

741

:

And outside of that, like startup,

um, That the startup space, right.

742

:

That's commonplace for a

lot of these companies.

743

:

You look at Sierra Nevada corporation

or any, you know, Magiera space for some

744

:

of the companies I worked for early on.

745

:

They have a bunch of forward, like,

uh, field service engineers that are

746

:

embedded into like more it ops type

stuff, but still it's like just,

747

:

it's, it's, it's kind of a part of,

part of the last, you know, 20 years

748

:

counterinsurgency and Centcom is just

like something you had to do because

749

:

there's a bunch of kind of ragtag, you

know, tactical operations center set up

750

:

all over the place, but I think what.

751

:

What Palantir did well was like solve,

like solve problems and create value.

752

:

Like, you know, people, people

cite, like, you know, the, the, the

753

:

ownership of data and like the price

point and all these different things.

754

:

It's like, they just like produce value.

755

:

Like, I can't think of many

mission systems that people can

756

:

like turn on and solve a national

security problem with like.

757

:

10 years later, you know, I

don't care what anyone says.

758

:

Like there's just very few companies

that can actually provide that level

759

:

of support and capability to people.

760

:

Ken's company is one of them,

like Omni, Omni federal actually

761

:

build software that people use.

762

:

They have user accounts.

763

:

You ask them like how many

people are using digital

764

:

university to think of things.

765

:

They can cite a user account.

766

:

That's very impressive.

767

:

Very interesting.

768

:

Um, there's, you know, there's a handful

of companies out there that can do that.

769

:

And that's starting to form.

770

:

Force the community to create

more capabilities that are

771

:

usable, tangible, can cite success

metrics, those types of things.

772

:

Palantir falls into that category

in their level, like a million.

773

:

Um, they've done really well.

774

:

Uh, and then to, to go back to the go

to market question, I actually, um, kind

775

:

of made a post about this on LinkedIn

recently, but it's like, just kind

776

:

of, you know, spread around like your

capability a little bit, like, like

777

:

government acquisitions is so chaotic.

778

:

Um, and any one.

779

:

Um, acquisition stakeholder, I kind of

break like the different POCs or kind

780

:

of stakeholders into three categories.

781

:

There's like acquisition POCs, operational

POCs, um, and, and technical POCs.

782

:

And so like any one of those kind

of archetypes or personas are so

783

:

interesting, but like you need to not

just focus on one program office and it,

784

:

and it, as, as humans, it feels like.

785

:

It feels good from a dopamine

perspective when someone's like,

786

:

Oh, I really like what you have.

787

:

I love your tech.

788

:

Like funding's coming up.

789

:

It's around the corner.

790

:

We're going to like set

this all up for you.

791

:

And we have this money set aside.

792

:

And people are like,

all right, job's done.

793

:

They did, you know, drop, drop all like

the, uh, the shovels, dig in the trenches,

794

:

fighting, looking for new customers.

795

:

And.

796

:

I, I, we, I think Ken would agree.

797

:

I recommend the opposite, like continue

to share your capabilities, continue

798

:

to network with people just in case,

because even if you perfectly align and

799

:

logic says like, you will be selling

to this stakeholder because they

800

:

have this burning problem, you know,

acquisition issues can side, like.

801

:

You know, totally broke her volunteer

plans, other stakeholders that are

802

:

kind of like vying for influence and,

and kind of can, can wrestle that away

803

:

from the stakeholder, the funding.

804

:

I mean, there's so many

crazy things that can happen.

805

:

It's like spread your investment

from like a relationship and

806

:

social currency perspective, go

out and meet a ton of people.

807

:

Yeah.

808

:

Understand other customers

that may have similar problems.

809

:

If you stumbled upon like a really

interesting market research signal about

810

:

your capability, doing something really

well for a public sector customer.

811

:

Um, and then I'd say like, and

then the, the, I guess the second

812

:

or third one is like, um, just.

813

:

Be authentic and be yourself.

814

:

Like, you know, the community

needs to change if they want to

815

:

have like more legitimate success.

816

:

It can't be this whole like hollow,

um, like let's, let's put on a show and

817

:

pretend we're progressing in it from a

modernization perspective, or, you know,

818

:

let's put on a show, use the right words

and then never build anything like.

819

:

Everyone's evolving.

820

:

And I think that's one of

the areas we're evolving in.

821

:

Um, like extremely well now for,

it took years for us to get there.

822

:

And so they're, they want to be authentic.

823

:

They don't want to have BS conversations.

824

:

They don't, they don't want to

talk about nonsense anymore.

825

:

So they're expecting people to come

to the table and just be like, Hey, I

826

:

have no idea about the U S military.

827

:

I love national security.

828

:

I love everything.

829

:

Like y'all have done for me.

830

:

I'm super grateful.

831

:

Let's build together.

832

:

Let's make something amazing.

833

:

I have this cool tech.

834

:

Will it work for your mission?

835

:

Too easy.

836

:

Ken Kato: So.

837

:

One of the things that I do is to

explicitly put into the contract

838

:

that I put the sponsor on the hook

to organize users I can speak to.

839

:

So when I go to do user discovery,

user interviews, it's their job to

840

:

get me the users I can speak to.

841

:

So versus trying to hunt and peck

for the right people and trying to

842

:

find the answers and all that stuff.

843

:

Now the sponsor has to participate.

844

:

And it's two fold, right?

845

:

So one thing is that they're

there to go on the same ride.

846

:

They're there to learn how

we do things, all that stuff.

847

:

Also, they also get to see first

hand from their own end users that

848

:

they might not regularly speak to.

849

:

And they actually hear first hand

account like, Oh, this doesn't

850

:

work the way you think it does.

851

:

Like we saw a lot of that in KR days

and so the product in Omni Federal

852

:

Digital University is a great product

and I'm not saying it because I'm

853

:

in Omni Federal, generally speaking,

the sentiment from every user I spoke

854

:

to was like, I love this product.

855

:

I wish I could use this instead

of the current like, you know,

856

:

scripted Air Force training.

857

:

So DU, as we call it, this university,

has been like the go to learning

858

:

platform for any digital stuff.

859

:

So coding, all the stuff,

we cover all the stuff.

860

:

There's another online platform that the

Air Force uses that no one likes, right?

861

:

There's a lot of users saying, I don't

like this, here are the problems, why?

862

:

Here are the problems that DU solves.

863

:

So, you know, we have a lot of

personal accounts, but let's

864

:

say we do a new project, like

AI stuff, it's all greenfield.

865

:

So, I don't have any use to speak

to, even speak to the CDAO's office,

866

:

there's a lot of questions around

what it is, like, I'm in a tech field

867

:

right now with basically no use cases.

868

:

We have novel technology that's

been democratized, but what's next?

869

:

So, I'm now trying to answer questions

about what's next, and the only

870

:

way I can do that sanely is just

talk to people and go, hey, what

871

:

do you expect to get out of this?

872

:

If I build you a private, you know,

instance for a language model, what

873

:

do you think you're going to do?

874

:

And then start to discuss the, you

know, the actual use cases of AI.

875

:

And this is no different than doing

DevOps, like, um, I would try my best

876

:

not to grow my eyes when I say this,

but it got pretty gross when people

877

:

said, I want to buy acquired DevOps.

878

:

I'm like, it's not something you buy.

879

:

The really gross part is the.

880

:

You know, the defense services

industry saying, yeah, we're

881

:

going to sell you a DevOps.

882

:

I'm like, Oh, that's just super fast.

883

:

So that's the kind of

stuff I'm not into doing.

884

:

I'm not into this whole bullshit

marketing just to be able to

885

:

meet a demand from an app shop.

886

:

And what often happens is that you have

acquisition professional in the government

887

:

making tech decisions, not because

they want to, but because they have to.

888

:

And it's also.

889

:

Their job to write out this

contracts get everything in place

890

:

and they get the feedback from

their own internal source, right?

891

:

So they get their text folks,

but they're not available.

892

:

If they're not there to

answer these questions, they

893

:

have to go on the internet.

894

:

So you now seen these pretty wide array

of contract languages, especially around

895

:

like AI and any virtual technology

where without defined use cases.

896

:

So the danger now becomes, no matter

how authentic I want to be and how I

897

:

want to help people, the true help I

can actually lend to the government is

898

:

to tell them, hey, Take a step back.

899

:

Don't rush into this.

900

:

You don't have to just because you

feel like you have to compete on the

901

:

global stage and I understand that

902

:

Mike Gruen: that's exactly everybody

903

:

Ken Kato: else is feeling the same thing.

904

:

So let's, you know, let's take a

much more concerted step together.

905

:

Rob Murtha: Dude, I totally

have a thought in there.

906

:

I just want to, I want to jump in and

just say like, absolutely can like that.

907

:

That I think is one of the most.

908

:

Um, like forward leaning things,

um, that, that the government

909

:

and these program offices can do.

910

:

And it's really hard to do because

it's tough to admit like, Oh, I don't

911

:

understand something or whatever.

912

:

But we saw it a lot through

like the DevSecOps era.

913

:

Like we talk about like

it being commoditized now.

914

:

It's something adopted.

915

:

It's something we're like using day

to day kind of, a lot of organizations

916

:

are still implementing it because it

is challenging with all the policy

917

:

barriers they have and whatnot.

918

:

It's like a new way of doing things.

919

:

But you're starting to see the same stuff

with artificial intelligence where it's

920

:

like, you know, Cringe Fest 9000, where

it's like, everything's generative AI.

921

:

There's no nuance.

922

:

There's no understanding.

923

:

There's no difference between generative

AI and, you know, predictive AI.

924

:

And, you know, what's a regression like

model training and like, what's, you

925

:

know, all these, like, uh, like how is a

dirty algorithm relate to an artificial

926

:

intelligence and automation strategy?

927

:

There's like so much value and

details everywhere where people can

928

:

use artificial intelligence to solve.

929

:

real problems.

930

:

Um, I call it like practical AI,

where it doesn't have to be this

931

:

like strange kind of like, you

know, commercial interpretation

932

:

of this white paper or something.

933

:

It's like, no, you can start small.

934

:

Like you did with DevOps, you know,

like KR, like, you know, start

935

:

deploying what, like essentially

like really like Gucci web forms, you

936

:

know, to in a production environment.

937

:

And that's a definite, that's a, a

first test case, um, of, of success.

938

:

We could do the same thing with

artificial intelligence, like.

939

:

They it's, there's actually approaches

called like lean AI and stuff where

940

:

you leverage the same, like lean

methodologies to approach experimentation.

941

:

And it's what we need to do if

we, if we want to realize it fast.

942

:

Tim Winkler: Yeah.

943

:

One of the things that you kind of

hit on too, Ken, I think is just

944

:

like, sadly, there's a lot of.

945

:

Bad players out there that are

just selling snake oil, right.

946

:

Because there's money in it.

947

:

And it's like, Oh, well, you know, if we

can just get it through this one program

948

:

office, whatever, like, yeah, well, they

see, they see, uh, you know, they see, uh,

949

:

the pot of gold at the end of the rainbow,

but they don't see the value and they

950

:

don't really care to like, make sure that

it's being implemented or roll it out.

951

:

So we see a lot of, I've

seen a lot of companies just.

952

:

It's almost like a facade, like, well,

I'm really sure what the hell you're

953

:

doing, but you have this relationship

with this, you know, this one agency and

954

:

it's, it's, you know, it comes back to the

root of like, what we were first started

955

:

talking about is like, you know, making

sure that that value is there and that

956

:

you're, you're, you know, that's what

you're delivering at the end of the day.

957

:

Um, I think Rob might, might've had

to sign off, but at the, at the end

958

:

of it, um, you know, I think can, it

sounds like what you guys are doing at

959

:

OmniFederal is, uh, you know, On a very

different scale than what a lot of these

960

:

other maybe, you know, consultancies

might be, might be rolling out.

961

:

Um, one of the things that I think

comes to mind for me, uh, when I

962

:

think about, you know, Some of these

preconceived notions of government

963

:

is, you know, we've got meetings

upon meetings upon meetings, right?

964

:

So it's like, how do you overcome

these, these older habits, like during

965

:

an engagement with, with some of the,

you know, some of the partnerships that

966

:

you've had, or some of these engagements

that you've had, what is it that.

967

:

You know, from a cadence perspective,

I'm just generally curious on like,

968

:

how often are you and checking in?

969

:

Like what's the level of engagement

that you all take when you're, when

970

:

you're trying to implement something?

971

:

Ken Kato: Great question.

972

:

Uh, so when I built Black Pearl for

the Department of Navy, you know,

973

:

it was, it wasn't like it went from

zero to build day one, I got there.

974

:

And so when I got there, it

was part, it was detailed.

975

:

There is a white house fellow

and the expectation is that we'll

976

:

be doing by husband, the way

things live with that might be.

977

:

I also came with having

just left Casa rock.

978

:

So having had, you know, had the hand and

building out the infrastructure there,

979

:

there's a lot of natural questions.

980

:

And the literal question that was

asked to me was, can we do a Casa run?

981

:

Like everybody.

982

:

And I have to tell Secretary of

the Navy, CNO, DCNO, CIO, CTO,

983

:

all the same thing, I don't know.

984

:

Like, what do you mean you don't know?

985

:

I'm like, well, without knowing what

the Navy is doing, I'm not going to

986

:

come in and make an assumption that

you're not doing it, or that you are

987

:

doing it, it's amazing, I don't know.

988

:

So I'm telling you that I don't

know that I need to go to Discovery.

989

:

And I wound up finding this

O5, my friend Jason Thurst, who

990

:

helped me, my friend Devin Brand.

991

:

Devin was the pimp who was

also in the Navy with me.

992

:

Travel across the Navy and just go dig in.

993

:

Find out what people are doing.

994

:

So when you look at Super

Hornet, right, how is software

995

:

being developed on Super Hornet?

996

:

Well, the answer lies in China Lake.

997

:

It's a very long, awful

trip to go to China Lake.

998

:

If we're talking sub development,

well, there's the Virginia class and

999

:

the Columbia class is near my neck

that was in the East Coast, so we

:

00:46:55,494 --> 00:47:00,470

went to talk to those folks, like, bit

by bit by bit to get that knowledge.

:

00:47:00,490 --> 00:47:03,390

And then after that, I was

finally able to check back in

:

00:47:03,420 --> 00:47:04,870

to the original stakeholders.

:

00:47:05,240 --> 00:47:07,600

CIO.

:

00:47:07,600 --> 00:47:11,040

I'm ready, and I think here's

where I can, I think I can help.

:

00:47:11,390 --> 00:47:14,110

I think I want to build a paper

concept platform so that you can

:

00:47:14,110 --> 00:47:18,730

just go on it, do development, do

communication, practice doing actual

:

00:47:18,730 --> 00:47:20,860

stuff, and bring that back with you.

:

00:47:20,980 --> 00:47:23,750

Like, I want to build everything

open source and just give it to

:

00:47:23,840 --> 00:47:25,390

you, but there's no money involved.

:

00:47:27,355 --> 00:47:29,935

But even that, there is

still money involved, right?

:

00:47:30,165 --> 00:47:33,375

The hard truth is that government

employees make money and they still,

:

00:47:33,735 --> 00:47:35,835

their money has to come from somewhere.

:

00:47:36,235 --> 00:47:40,725

So I wound up having to, you know,

identify new stakeholders and champions.

:

00:47:40,785 --> 00:47:45,445

And the person I found, he had me

start looking into contract renewals,

:

00:47:45,465 --> 00:47:48,840

because I was waiting after, you

know, the Point to be able to

:

00:47:48,970 --> 00:47:50,380

say, Hey, Congress, give me money.

:

00:47:50,410 --> 00:47:53,460

So I had to go look on the

couch missions, but where I

:

00:47:53,460 --> 00:47:54,780

found it was licensed renewals.

:

00:47:54,840 --> 00:47:58,870

It's a licensed renewals is that weird

murky war in it, where a lot of people

:

00:47:58,900 --> 00:48:01,680

overplay the numbers to make sure they

can buy all the things we need to do.

:

00:48:02,700 --> 00:48:05,340

And if that's true in private

industry, that's also got to

:

00:48:05,340 --> 00:48:06,520

be true in government, right?

:

00:48:06,540 --> 00:48:07,900

And that's exactly where I found this.

:

00:48:07,900 --> 00:48:10,000

So I found a couch

question for that money.

:

00:48:10,230 --> 00:48:15,740

And I actually, Was able to build,

deploy, and run BlackQuery, year

:

00:48:15,740 --> 00:48:19,130

one, for, I tell you what, you guys

have been in this business, no one

:

00:48:19,130 --> 00:48:21,850

else, if I had to build a DevSecOps

program, how much do you think I spent,

:

00:48:24,850 --> 00:48:25,620

whole program?

:

00:48:25,970 --> 00:48:27,110

Mike Gruen: Mike, you

would, you gotta guess?

:

00:48:27,210 --> 00:48:32,660

I mean, I, whatever, I guess it's gonna

be so off, I have no, I mean, for, for

:

00:48:32,660 --> 00:48:34,880

that size, I don't know, I have, it's,

:

00:48:39,865 --> 00:48:40,435

Um,

:

00:48:43,785 --> 00:48:45,485

uh, yeah, I wouldn't even

be able to hazard a guess,

:

00:48:45,485 --> 00:48:47,995

honestly, just, uh, you'd call it

:

00:48:49,505 --> 00:48:50,715

Ken Kato: millions, tens of millions,

:

00:48:51,655 --> 00:48:55,064

Mike Gruen: probably tens of

millions, like somewhere, and

:

00:48:55,445 --> 00:48:57,775

Ken Kato: that's another thing I

wanted to change your mind on and

:

00:48:57,775 --> 00:49:01,375

the government, it doesn't have to be

that expensive, but it is 400, 000.

:

00:49:03,735 --> 00:49:05,454

Mike Gruen: Impressive

:

00:49:05,455 --> 00:49:06,015

Ken Kato: operation.

:

00:49:06,015 --> 00:49:06,285

Thank you.

:

00:49:06,285 --> 00:49:09,165

But that's also like me and a couple

of people have been put hands on

:

00:49:09,165 --> 00:49:11,025

keyboard, build out everything.

:

00:49:11,305 --> 00:49:12,495

No licensing involved.

:

00:49:12,755 --> 00:49:15,905

And for the license stuff

is calling in favors, right?

:

00:49:16,525 --> 00:49:17,475

Version of the Red Hat.

:

00:49:17,485 --> 00:49:20,195

So I called in favors

to friends over Red Hat.

:

00:49:20,205 --> 00:49:21,845

Like, Hey, how do I get a dev license?

:

00:49:22,315 --> 00:49:22,855

Like, Oh, here's

:

00:49:22,855 --> 00:49:23,994

Mike Gruen: that.

:

00:49:24,275 --> 00:49:26,455

Ken Kato: So just being creative

about that kind of stuff.

:

00:49:26,775 --> 00:49:30,500

And then that's You know, that

was the initial part of like,

:

00:49:30,500 --> 00:49:31,560

how do you launch a new product?

:

00:49:31,610 --> 00:49:34,290

And so the answer to your question

about how often you check in

:

00:49:34,290 --> 00:49:38,250

thereafter, all the time, because

once you build a program like that,

:

00:49:38,870 --> 00:49:40,720

I have to go down and pony it, right?

:

00:49:40,760 --> 00:49:44,070

Now it's going back to the same

tool registered to discover

:

00:49:44,070 --> 00:49:45,700

who's doing DevOps in the Navy.

:

00:49:45,930 --> 00:49:49,260

Now let's go back through this

same group of people and go, here's

:

00:49:49,260 --> 00:49:50,550

the thing, does this help you?

:

00:49:50,570 --> 00:49:52,870

Yes, no, if it doesn't,

tell me how it does help.

:

00:49:53,180 --> 00:49:53,420

Tim Winkler: Right.

:

00:49:54,890 --> 00:49:57,860

Yeah, you bring up a good point, Ken,

because it's like, uh, I was talking

:

00:49:57,860 --> 00:50:01,930

to somebody the other day that's pretty

deep into, into defense tech space.

:

00:50:01,930 --> 00:50:06,320

And One of the biggest things that

he was an advocate for was finding

:

00:50:06,340 --> 00:50:09,330

agencies that don't have colors of money.

:

00:50:09,670 --> 00:50:12,830

So it's like, you know, everything in

the government's got to have, you know,

:

00:50:12,880 --> 00:50:20,180

this been tied to this thing, which

makes it really hard to innovate if they

:

00:50:20,180 --> 00:50:23,450

can't find that correlation of like, Oh,

well, I don't know what, what was this?

:

00:50:23,770 --> 00:50:25,200

Was this really R and D or?

:

00:50:25,515 --> 00:50:28,215

Or, you know, was this

operation and maintenance?

:

00:50:28,215 --> 00:50:30,115

I don't know what,

what's my line item here.

:

00:50:30,455 --> 00:50:35,815

So there's, there are, there are

few, uh, agencies in defense that are

:

00:50:35,845 --> 00:50:41,125

kind of like this, uh, almost like a,

uh, sandbox for innovation, defense

:

00:50:41,125 --> 00:50:42,785

innovation unit is one of them, DIU.

:

00:50:43,695 --> 00:50:45,925

Uh, where they have colorless money.

:

00:50:46,095 --> 00:50:49,795

So they do a lot of work with

commercial startups in terms of,

:

00:50:50,105 --> 00:50:53,085

you know, experimenting with this

technology here, or like, Hey, let me

:

00:50:53,085 --> 00:50:56,795

see what I can see, how I can maybe

prototype with this technology from

:

00:50:56,795 --> 00:51:00,875

this one company here versus having

to find a line item to connect it to

:

00:51:00,875 --> 00:51:03,935

and make sure that it's, yeah, but

you know, it's, is it in the budget?

:

00:51:04,405 --> 00:51:06,225

Um, so it is really tough.

:

00:51:06,255 --> 00:51:08,995

And I think that's one thing that a lot of

folks don't really understand or maybe not

:

00:51:08,995 --> 00:51:12,535

realize when they come from a commercial

setting into a government setting is that.

:

00:51:12,985 --> 00:51:14,475

There are these colors of money.

:

00:51:14,475 --> 00:51:15,685

You can look it up.

:

00:51:15,685 --> 00:51:17,675

What does it, what does

government color of money mean?

:

00:51:17,675 --> 00:51:20,895

And it's got to be tied to,

you know, one of these buckets.

:

00:51:21,295 --> 00:51:26,295

Um, so when you kind of, you know,

describe like how to get something

:

00:51:26,295 --> 00:51:31,045

across, you know, uh, across the

finish line, that just, You know,

:

00:51:31,045 --> 00:51:33,915

it's not, it's not a matter of spam,

but just like, just once you get a

:

00:51:33,915 --> 00:51:37,525

taste of the value, I think that's,

it's a really interesting perspective.

:

00:51:37,525 --> 00:51:40,605

When I, when I'm coming from like a world

of like a lot of commercial startup and

:

00:51:40,605 --> 00:51:42,465

innovation, that's moving very quickly.

:

00:51:42,465 --> 00:51:44,105

And let me just give you a taste of it.

:

00:51:44,105 --> 00:51:45,935

You can try it and then we can scale it.

:

00:51:45,945 --> 00:51:49,815

So not how it works traditionally,

uh, when we're talking about, you

:

00:51:49,815 --> 00:51:51,810

know, big Big implementations here.

:

00:51:52,280 --> 00:51:54,810

Ken Kato: Now, to your point about

speed, like a little funny, you know,

:

00:51:54,820 --> 00:51:58,080

adding to it about building out Black

Pearl, like, the story officially in

:

00:51:58,080 --> 00:52:02,785

the Department of Navy is it took,

I want to say, 45 days to launch it.

:

00:52:03,005 --> 00:52:03,335

Tim Winkler: Wow.

:

00:52:03,345 --> 00:52:04,735

Ken Kato: And to build

all that stuff, right.

:

00:52:04,795 --> 00:52:05,775

Which is still fast.

:

00:52:05,835 --> 00:52:06,905

But here's the actual truth.

:

00:52:06,925 --> 00:52:12,925

That's me and my friends took a long

weekend to actually write and AWS.

:

00:52:13,575 --> 00:52:15,425

So, you know, that's four days.

:

00:52:15,685 --> 00:52:19,015

So I spent the other 41 days

getting back on the CNO's calendar

:

00:52:19,015 --> 00:52:20,015

to tell the guy I was done.

:

00:52:23,045 --> 00:52:23,555

Tim Winkler: That's funny.

:

00:52:25,565 --> 00:52:30,005

Um, yeah, that's, that's a pretty, uh,

that definitely puts perspective in terms

:

00:52:30,005 --> 00:52:32,045

of like the amount of time to value.

:

00:52:32,700 --> 00:52:34,950

Ken Kato: Now, on the Congress

money parcel, when you're talking

:

00:52:34,960 --> 00:52:37,800

DIU, and I remember them from the

days where they had the X and it

:

00:52:37,810 --> 00:52:39,150

was still experimental, right?

:

00:52:39,150 --> 00:52:41,550

So KR came out of the IUX model back then.

:

00:52:41,990 --> 00:52:45,840

So, you're talking OTA, other

transcriptional authority, and

:

00:52:45,840 --> 00:52:48,740

that's another, like, really

hairy topic in government.

:

00:52:49,100 --> 00:52:52,990

So, Or I'm not sure how familiar

your listeners are to OTAs

:

00:52:52,990 --> 00:52:54,140

and different mechanisms.

:

00:52:54,290 --> 00:52:54,680

Maybe just

:

00:52:54,680 --> 00:52:56,970

Tim Winkler: quickly spell it out

because it is an area that I think

:

00:52:56,970 --> 00:53:01,410

is, um, comes up a couple of times

through the Castle Run former episodes.

:

00:53:01,490 --> 00:53:01,750

Okay.

:

00:53:02,280 --> 00:53:05,580

Ken Kato: So let's touch the high level

OTA, other transactional authority.

:

00:53:05,760 --> 00:53:09,310

It is a perfectly legal way for

the government to buy something.

:

00:53:09,540 --> 00:53:10,720

Usually it's technology.

:

00:53:11,170 --> 00:53:14,540

It's called other transactional

authority because it is a fully

:

00:53:14,560 --> 00:53:15,920

legal authority to buy stuff.

:

00:53:16,750 --> 00:53:19,480

It's other transactional also

because it's not traditional.

:

00:53:20,155 --> 00:53:20,705

Acquisition.

:

00:53:20,745 --> 00:53:25,325

So FAR, Federal Acquisition Regulation,

and DFAR is a defense supplement.

:

00:53:25,735 --> 00:53:29,405

It's a very scripted,

structured way to buy something.

:

00:53:29,475 --> 00:53:30,805

It's pretty gnarly to get through.

:

00:53:31,185 --> 00:53:32,565

OTAs, you don't have to.

:

00:53:32,585 --> 00:53:37,145

So you are now legally not obligated to

have to do all the DFARs and FAR stuff.

:

00:53:37,445 --> 00:53:38,855

That's what's sexy about OTAs.

:

00:53:38,895 --> 00:53:39,935

But here's the problem.

:

00:53:40,235 --> 00:53:42,895

Most ag shops have no idea how OTAs work.

:

00:53:43,115 --> 00:53:46,425

So even if you find an ag shop going

to do an OTA, they make you jump to

:

00:53:46,425 --> 00:53:49,515

the hook like FAR and DFARs because

they don't know the difference.

:

00:53:50,300 --> 00:53:54,350

So even though you can find

colorless money like an OTA funds,

:

00:53:54,480 --> 00:53:57,970

you still up against people who

still manage money the same way.

:

00:53:58,040 --> 00:53:58,420

Uh,

:

00:53:58,500 --> 00:53:58,890

Mike Gruen: gotcha.

:

00:53:59,040 --> 00:54:00,550

Ken Kato: It still comes

down to the application of

:

00:54:00,610 --> 00:54:01,830

professional knowledge about it.

:

00:54:01,830 --> 00:54:03,750

And OTAs are pretty out there.

:

00:54:04,000 --> 00:54:05,780

There's a lot of people

who really don't like them.

:

00:54:05,830 --> 00:54:08,130

And we're talking even

congressional representatives

:

00:54:08,130 --> 00:54:09,500

who really don't like the idea.

:

00:54:10,030 --> 00:54:12,930

It's not for lack of

transparency and any above.

:

00:54:12,970 --> 00:54:15,445

It's just the, Lack of

commitment and money.

:

00:54:15,475 --> 00:54:19,295

Because OTAs are so flexible, people

hasn't been handing them out regularly.

:

00:54:19,765 --> 00:54:21,575

So there's, because there's

no legal enforcement.

:

00:54:21,585 --> 00:54:22,545

There is, but there isn't.

:

00:54:22,595 --> 00:54:24,195

So that's OTAs in a nutshell.

:

00:54:24,895 --> 00:54:28,865

Castle Run, but there is a way to use,

you know, Colorado money in a smart way.

:

00:54:28,905 --> 00:54:31,015

So Castle Run, we have 3, 600 money.

:

00:54:31,225 --> 00:54:33,755

So 3, 600 is just, you know, R& D.

:

00:54:34,210 --> 00:54:37,450

So as long as we could fit into

the software R& D, that's just

:

00:54:37,450 --> 00:54:40,330

that pot of money, it's really

flexible to be able to move around.

:

00:54:40,620 --> 00:54:45,480

So there is a way to do it, but it also

means getting an application professional

:

00:54:45,620 --> 00:54:47,440

who understands this field well.

:

00:54:47,510 --> 00:54:51,410

Like it's the same difference as

hiring a really well seasoned CFO,

:

00:54:52,010 --> 00:54:56,220

especially a CFO who understands

international trade laws and taxes.

:

00:54:56,730 --> 00:55:00,340

Because when you run a business,

it's not the, it's frankly not the

:

00:55:00,350 --> 00:55:01,480

business itself that will kill you.

:

00:55:01,480 --> 00:55:02,250

It's the taxes.

:

00:55:02,775 --> 00:55:04,975

Especially when we start

making international money.

:

00:55:05,015 --> 00:55:08,635

So how do you reconcile international

income into the United States?

:

00:55:08,955 --> 00:55:11,055

Having a seasoned CFO

to answer that is great.

:

00:55:11,225 --> 00:55:13,395

Same difference in the government

having a seasoned acquisition

:

00:55:13,405 --> 00:55:16,535

professionals who actually

understand OTAs is super critical.

:

00:55:18,145 --> 00:55:19,295

Tim Winkler: Yeah, that's good intel man.

:

00:55:19,335 --> 00:55:23,885

And I think that's probably an area

we could really dive deeper into

:

00:55:23,895 --> 00:55:27,365

on an entire episode, just because,

you know, I think there's a lot

:

00:55:27,365 --> 00:55:29,445

of folks that have figured it out.

:

00:55:29,485 --> 00:55:32,375

Some that are still trying to figure

it out, but I think there is a

:

00:55:32,375 --> 00:55:36,465

lot that can be done in terms of

navigating those waters and, and,

:

00:55:36,465 --> 00:55:38,065

uh, you know, how to innovate by.

:

00:55:38,465 --> 00:55:40,135

Yeah, pulling on the right strings.

:

00:55:42,455 --> 00:55:44,915

Ken Kato: I could think of two people

would be perfect for you to talk to.

:

00:55:45,055 --> 00:55:47,245

My buddy, Russell Long,

he runs Long Capture.

:

00:55:47,385 --> 00:55:50,085

He came out about, he's a

former contract officer.

:

00:55:50,365 --> 00:55:52,574

And my friend, Tori Cush is over at Sage.

:

00:55:52,575 --> 00:55:54,995

Tori was the main, like,

act person for Castle Run.

:

00:55:54,995 --> 00:55:57,875

So, she's the one who

defined Agile Acquisition.

:

00:55:58,165 --> 00:56:01,355

Another person would be Max,

DIU, formerly at Castle Run.

:

00:56:01,695 --> 00:56:03,235

Same thing, right, the Agile Acquisition.

:

00:56:03,245 --> 00:56:04,955

Like, those are the folks who

speak to you about that stuff.

:

00:56:05,340 --> 00:56:07,720

Tim Winkler: I'll have to, that's

what I love about, man, this

:

00:56:07,720 --> 00:56:11,660

is, and that, in my opinion, it

kind of like defines the space.

:

00:56:11,660 --> 00:56:14,940

It's like, everybody's always

willing to like pass forward a name

:

00:56:14,940 --> 00:56:16,920

or two or three of somebody else.

:

00:56:16,920 --> 00:56:19,140

It's, it's doing something in some area.

:

00:56:19,580 --> 00:56:24,220

I mean, it, it really is a theme of,

of, uh, you know, uh, work, working

:

00:56:24,220 --> 00:56:27,890

in tech and government or defense,

what, what have you, it's truly a

:

00:56:27,890 --> 00:56:30,080

very networking driven space, man.

:

00:56:30,080 --> 00:56:30,359

Yeah.

:

00:56:30,730 --> 00:56:32,220

And, uh, I love that.

:

00:56:32,220 --> 00:56:36,070

I think it's, it's, uh, it's also

shows your passion too, like willing

:

00:56:36,070 --> 00:56:38,040

to like, Hey, like pay it forward.

:

00:56:38,040 --> 00:56:41,210

Also, like, I want to keep the

conversation going because everybody

:

00:56:41,210 --> 00:56:45,630

seems to be on the same thread that,

you know, we want to help innovate.

:

00:56:45,630 --> 00:56:46,420

We want to do it.

:

00:56:46,430 --> 00:56:49,090

Like, how do we, how do

we build the ecosystem?

:

00:56:49,090 --> 00:56:51,080

Like, here's some people that

you might want to talk to.

:

00:56:51,405 --> 00:56:55,195

Um, so I, I appreciate that and I,

I will, I will take you up on that.

:

00:56:55,195 --> 00:56:57,665

I'll, I'll, I'll, uh, connect

with you offline on it.

:

00:56:58,385 --> 00:56:59,015

Um, all right.

:

00:56:59,015 --> 00:57:03,595

Well, in the essence of, of time, I am

going to just kind of transition us down

:

00:57:03,595 --> 00:57:05,905

to, uh, to our, our final segment here.

:

00:57:06,155 --> 00:57:09,415

I'll, I'll have to tap Rob at a later

date here to get his, uh, five seconds.

:

00:57:09,425 --> 00:57:10,075

Scramble, but.

:

00:57:10,440 --> 00:57:12,750

Uh, we still have you on,

on the hook here, Ken.

:

00:57:12,750 --> 00:57:16,820

So Mike, uh, go ahead and, uh,

and lead us off with the, with

:

00:57:16,820 --> 00:57:18,000

the five second scramble segment.

:

00:57:18,630 --> 00:57:20,080

Uh, for the new year, a little

:

00:57:20,080 --> 00:57:20,450

Mike Gruen: change.

:

00:57:20,450 --> 00:57:20,810

I get

:

00:57:24,980 --> 00:57:25,164

to actually participate.

:

00:57:25,164 --> 00:57:28,460

So, yeah, so, uh, I'm going to fire

some questions off at you, uh, and

:

00:57:28,470 --> 00:57:29,950

try to answer as quickly as possible.

:

00:57:30,210 --> 00:57:34,190

Uh, it'll be a mix of, um, uh,

company and personal questions.

:

00:57:34,610 --> 00:57:39,395

Um, So, uh, here we go, uh,

explain OmniFederal to me as

:

00:57:39,395 --> 00:57:40,365

if I were a five year old.

:

00:57:41,895 --> 00:57:46,775

Ken Kato: We build tech that

people really, really want to use.

:

00:57:46,925 --> 00:57:49,395

That's really, really

critical to their success.

:

00:57:49,505 --> 00:57:52,835

So we like to go out and find out

what it is that you want to use

:

00:57:52,905 --> 00:57:55,584

and we build it for you because

that's where our passion is.

:

00:57:56,715 --> 00:58:00,565

Mike Gruen: Uh, what type of

technologist thrives at, uh, OmniFederal?

:

00:58:02,825 --> 00:58:03,775

Ken Kato: A wide range.

:

00:58:03,985 --> 00:58:06,935

Uh, what kind of technologists thrive?

:

00:58:07,325 --> 00:58:12,065

Really, people who are willing to just

dive in and really dig into a problem.

:

00:58:12,075 --> 00:58:16,255

Not just a surface, cure a problem, space,

and then I'm going to go make something.

:

00:58:16,485 --> 00:58:20,575

Really, really dig in to really

understand the customer, the end user.

:

00:58:22,450 --> 00:58:24,690

Mike Gruen: Uh, what's the best piece

of advice you've ever been given?

:

00:58:26,410 --> 00:58:28,960

Ken Kato: When I first joined

the fellowship, I was told to,

:

00:58:29,260 --> 00:58:34,300

uh, that every fellowship class

has a crisis and I was prepared.

:

00:58:34,330 --> 00:58:36,180

I was not prepared for a pandemic though.

:

00:58:37,700 --> 00:58:40,470

Mike Gruen: Uh, what's the most important

skill you look for in a new hire?

:

00:58:42,200 --> 00:58:46,320

Ken Kato: The ability to explain

complicated tech in a really simple way.

:

00:58:46,430 --> 00:58:49,750

Like as if you're going to explain to my

mom or grandma, that's the kind of people

:

00:58:49,750 --> 00:58:53,685

I like to talk to because well, I'm You

don't have to sound smart to be smart.

:

00:58:55,295 --> 00:58:57,385

Mike Gruen: Uh, what do we

have to look forward to, uh,

:

00:58:57,435 --> 00:58:59,095

coming, uh, at OmniFederal?

:

00:59:00,445 --> 00:59:03,595

Ken Kato: We're really excited

to start thinking about how to

:

00:59:03,605 --> 00:59:07,315

get DEU into the hands of other

users and to other missions.

:

00:59:07,565 --> 00:59:12,015

We're super excited to start building

out an internal product launch structure

:

00:59:12,015 --> 00:59:15,965

so that we can start moving towards a

product centric organization as well.

:

00:59:16,025 --> 00:59:19,215

I am personally interested and very

excited about building different

:

00:59:19,215 --> 00:59:20,895

AI and ML related capabilities.

:

00:59:20,895 --> 00:59:21,114

Thanks.

:

00:59:22,375 --> 00:59:23,845

Mike Gruen: What was

your dream job as a kid?

:

00:59:24,835 --> 00:59:26,025

Ken Kato: To be a motorcycle cop.

:

00:59:27,785 --> 00:59:29,165

Mike Gruen: That's a sweet answer.

:

00:59:30,165 --> 00:59:30,665

Love it.

:

00:59:30,665 --> 00:59:31,764

Yeah,

:

00:59:31,765 --> 00:59:32,625

Ken Kato: I knew it, but yeah.

:

00:59:35,105 --> 00:59:37,005

Mike Gruen: What's the largest

land animal you think you

:

00:59:37,005 --> 00:59:38,015

could take in a street fight?

:

00:59:38,805 --> 00:59:42,435

Ken Kato: Ooh, largest land

animal in a street fight, my god.

:

00:59:45,745 --> 00:59:47,045

That's a great question, man.

:

00:59:48,435 --> 00:59:50,545

I think I'm pretty comfortable with a cat.

:

00:59:50,555 --> 00:59:53,485

I think I have a good chance, but

I don't, I love my fur babies.

:

00:59:53,485 --> 00:59:57,315

You know, we have, I would have

to run away because I'm not

:

00:59:57,505 --> 00:59:58,335

going to hurt the fur baby.

:

01:00:03,225 --> 01:00:05,035

Mike Gruen: What was your

favorite cereal as a kid?

:

01:00:06,325 --> 01:00:07,365

Ken Kato: Uh, funny thing.

:

01:00:07,405 --> 01:00:10,985

I didn't really experience Syria until I

moved to the United States when they did

:

01:00:11,135 --> 01:00:12,735

recent peanut butter puffs all the way.

:

01:00:12,905 --> 01:00:13,725

Mike Gruen: Oh, awesome.

:

01:00:13,725 --> 01:00:15,255

That's cool.

:

01:00:15,925 --> 01:00:19,695

Um, what's a charity or corporate

philanthropy that you're a,

:

01:00:19,735 --> 01:00:20,535

that's near and dear to you?

:

01:00:20,965 --> 01:00:21,455

Ken Kato: Oh man.

:

01:00:21,505 --> 01:00:22,635

Uh, donate to Spookstock.

:

01:00:23,315 --> 01:00:25,655

Uh, I have a bunch of friends

who run the organization.

:

01:00:25,745 --> 01:00:28,935

Uh, they give money to phone

Intel officers, totally worth it.

:

01:00:30,315 --> 01:00:32,355

Mike Gruen: Um, and we'll get that

in the show notes, right, Tim?

:

01:00:32,780 --> 01:00:33,120

Yeah.

:

01:00:33,420 --> 01:00:33,660

Cool.

:

01:00:33,720 --> 01:00:33,940

Cool.

:

01:00:34,070 --> 01:00:38,670

Um, and then finally, if you could live

in a fictional world from a book or

:

01:00:38,670 --> 01:00:40,230

movie, which world would you choose?

:

01:00:40,900 --> 01:00:41,360

Ken Kato: Oh man.

:

01:00:41,400 --> 01:00:44,484

But because we're talking horror early

in the night, that's when my brain's

:

01:00:44,484 --> 01:00:46,080

like, that's not a good space to live in.

:

01:00:48,120 --> 01:00:49,140

That's not a good idea.

:

01:00:49,570 --> 01:00:51,200

Uh, world to live in.

:

01:00:51,410 --> 01:00:52,380

Let's go with my childhood.

:

01:00:52,490 --> 01:00:55,550

I mean, I would love to be able

to have an actual like world where

:

01:00:55,550 --> 01:00:58,160

like the Gundam mechs are available.

:

01:00:58,160 --> 01:00:58,210

Cool.

:

01:00:58,380 --> 01:00:58,730

Right.

:

01:00:59,550 --> 01:01:00,350

Versus a car.

:

01:01:00,410 --> 01:01:00,640

Yeah.

:

01:01:00,740 --> 01:01:01,740

Give me that any day of the week.

:

01:01:03,420 --> 01:01:03,940

Mike Gruen: Awesome.

:

01:01:03,940 --> 01:01:04,780

Well, thanks so much.

:

01:01:05,210 --> 01:01:05,700

Tim Winkler: Good stuff.

:

01:01:06,120 --> 01:01:06,930

Uh, all right.

:

01:01:06,930 --> 01:01:07,700

Well, that's a wrap.

:

01:01:07,720 --> 01:01:09,630

Yeah, we're gonna, we're

gonna close on that note.

:

01:01:09,670 --> 01:01:10,990

Thanks again for joining us.

:

01:01:10,990 --> 01:01:13,190

Ken and Rob, you guys

have been a great guest.

:

01:01:13,280 --> 01:01:18,090

Uh, uh, thanks for keeping, keep

keeping on, on, on moving that needle.

:

01:01:18,090 --> 01:01:20,440

Uh, when it comes to digital

transformation and the public

:

01:01:20,440 --> 01:01:24,000

sector, uh, it's a long road,

but, uh, you guys are walking it.

:

01:01:24,000 --> 01:01:25,120

So appreciate the work you're doing.

:

01:01:25,860 --> 01:01:26,860

For joining us on the pod.

:

01:01:27,520 --> 01:01:28,230

Ken Kato: Thanks for having me.

:

01:01:28,230 --> 01:01:28,910

This is great.

:

01:01:28,950 --> 01:01:29,600

Thank you again.

Chapters

Video

More from YouTube