1
00:00:09,700 --> 00:00:12,500
You're listening to the identity
of the center podcast. 

2
00:00:12,700 --> 00:00:15,600
This is a show that talks about 
identity and access management 

3
00:00:15,700 --> 00:00:18,600
and making sure you know who has
access to what let's get 

4
00:00:18,600 --> 00:00:24,800
started. 
Welcome to the identity of the 

5
00:00:24,800 --> 00:00:26,800
center podcast I'm Jeff. 
And that's Jim. 

6
00:00:26,800 --> 00:00:29,900
Hey Jim hey Jeff, how are you? 
Oh, not so bad yourself. 

7
00:00:30,500 --> 00:00:32,700
I think we have an issue with 
temperature control. 

8
00:00:32,900 --> 00:00:34,300
I don't feel like there's an 
issue at all. 

9
00:00:34,300 --> 00:00:36,100
Fill. 
It feels crazy your way 

10
00:00:37,300 --> 00:00:40,300
sometimes. 
This is happening. 

11
00:00:40,300 --> 00:00:44,700
There are certain 
non-negotiables 665 degrees in 

12
00:00:44,700 --> 00:00:45,700
York. 
It's, I'm looking at the 

13
00:00:45,708 --> 00:00:50,400
thermostat 66 degrees in here. 
It's like an icebox in here. 

14
00:00:50,400 --> 00:00:52,000
It's nice. 
This is cool. 

15
00:00:52,200 --> 00:00:54,800
This is like, you're going to 
write your user me out of here. 

16
00:00:55,000 --> 00:00:58,400
Well, I've got a lot of 
technology in here, you know, we

17
00:00:58,400 --> 00:01:00,500
have to keep it cool. 
To make sure that things are 

18
00:01:00,500 --> 00:01:03,400
operating at a consistence 
level. 

19
00:01:03,400 --> 00:01:05,600
Here's something most people 
probably don't know about. 

20
00:01:05,600 --> 00:01:08,100
You is, you're pretty 
environmental Jeff. 

21
00:01:08,100 --> 00:01:12,100
It's 110 degrees outside and in 
her room is like 66. 

22
00:01:12,100 --> 00:01:13,600
Yeah. 
And there's three air 

23
00:01:13,600 --> 00:01:16,100
conditioners in this week. 
By the way, there's three 

24
00:01:16,100 --> 00:01:19,500
different thermostats and I have
them all set to 66 because I 

25
00:01:19,500 --> 00:01:21,900
need to be cool and I have my 
fan running here next to me. 

26
00:01:22,200 --> 00:01:27,900
I've spoken my piece. 
All right, so we're here at the 

27
00:01:27,900 --> 00:01:31,000
Gartner. 
I am Summit AT a lot of 

28
00:01:31,008 --> 00:01:33,100
different conversations with 
very cool people in the 

29
00:01:33,100 --> 00:01:36,000
industry. 
Our next one is no different. 

30
00:01:36,100 --> 00:01:38,600
It's with Jamie Lewis grow. 
She's the vice president 

31
00:01:39,100 --> 00:01:41,700
Solutions engineering and 
strategy with sabian's. 

32
00:01:41,700 --> 00:01:45,700
She's also a great friend and 
family of the program welcome 

33
00:01:45,700 --> 00:01:47,800
back. 
Jamie thank you for having me. 

34
00:01:48,000 --> 00:01:51,000
This is fun. 
Yeah so this is the original I 

35
00:01:51,000 --> 00:01:54,500
think not original I was I was 
probably the add-on but the 

36
00:01:54,500 --> 00:01:57,400
strategy team for identity 
strategy team. 

37
00:01:57,400 --> 00:01:59,900
Exactly. 
So it's been a little bit of 

38
00:01:59,900 --> 00:02:02,100
like a homecoming. 
I think for a lots of the former

39
00:02:02,100 --> 00:02:04,500
ident rope Ian's that have been 
a Shore House. 

40
00:02:04,500 --> 00:02:07,700
We've done like different areas 
but the three of us were the 

41
00:02:07,900 --> 00:02:13,500
strategy team for Gartner. 
We were we developed a strategy 

42
00:02:13,500 --> 00:02:16,100
and roadmap for Gardner the. 
I think that the Eternal 

43
00:02:16,100 --> 00:02:18,800
identity and access management 
but there's still something to 

44
00:02:18,800 --> 00:02:20,400
be proud of. 
I'm not sure if we can say that 

45
00:02:20,400 --> 00:02:22,300
but we just did some. 
You just said that due to 

46
00:02:22,300 --> 00:02:26,700
limitations have maybe a 
elapsed, it was probably for 

47
00:02:26,700 --> 00:02:28,700
what five years ago, maybe 
roughly. 

48
00:02:29,400 --> 00:02:31,900
But yeah, kind of a cool little 
feather and all of our campuses 

49
00:02:31,900 --> 00:02:34,300
like hey thanks. 
So who did Gartner go to to 

50
00:02:34,300 --> 00:02:35,600
create their? 
I am strategy. 

51
00:02:35,600 --> 00:02:39,300
Oh, they went to Jamie Jim and 
Geoff. 

52
00:02:39,300 --> 00:02:40,000
Yes! 
Lord. 

53
00:02:40,000 --> 00:02:44,100
Remember, people used to say you
have to have the first initial J

54
00:02:44,100 --> 00:02:48,300
to work at your company. 
He had also Jeff Chang and a few

55
00:02:48,300 --> 00:02:51,800
others. 
Anyway, we digress. 

56
00:02:51,900 --> 00:02:53,700
All right, let's get back. 
Let's get, let's get on top. 

57
00:02:53,700 --> 00:02:55,200
Let's get to it. 
Yeah, let's talk identity. 

58
00:02:55,200 --> 00:02:59,900
So Jamie, how's the conference 
going so far for the conference 

59
00:02:59,900 --> 00:03:02,600
is going? 
Well, there's a lot of energy. 

60
00:03:03,600 --> 00:03:07,700
It's certainly keeping us busy. 
There's a lot of people wanting 

61
00:03:07,700 --> 00:03:11,000
to talk to us in the booth. 
So, it's exciting. 

62
00:03:11,000 --> 00:03:16,800
We get to, you know, tell 
customers about the benefits of 

63
00:03:16,800 --> 00:03:19,100
our organization. 
How to solve? 

64
00:03:19,300 --> 00:03:23,600
Business problems and just a lot
a lot happening. 

65
00:03:24,500 --> 00:03:28,400
I did notice that your booth had
a lot of foot traffic, so I'm 

66
00:03:28,400 --> 00:03:30,000
trying to have you been spending
at the booth? 

67
00:03:30,000 --> 00:03:33,700
First going on, striking up 
conversations with people? 

68
00:03:33,800 --> 00:03:38,400
I would say 90% of my time has 
been striking up conversations 

69
00:03:38,400 --> 00:03:41,700
in the booth in the booth. 
Okay, yeah, yeah, I mean, I 

70
00:03:41,700 --> 00:03:46,300
think, you know, I fantasize 
everybody is like, pretty open 

71
00:03:46,300 --> 00:03:51,000
to, you know, conversations like
Sit down with some folks today 

72
00:03:51,700 --> 00:03:54,700
at breakfast. 
And one of the people was 

73
00:03:54,700 --> 00:03:57,700
wearing a shirt with the little 
Hershey's kiss on his, they do 

74
00:03:57,700 --> 00:04:00,300
you work for her. 
She's as like, ya know, just the

75
00:04:00,300 --> 00:04:03,200
fan did, you know our shirts? 
I hope you saw. 

76
00:04:03,200 --> 00:04:06,100
I'm pretty sure I saw you. 
You have like a t-shirt shaped 

77
00:04:06,200 --> 00:04:08,000
like beer, koozie. 
We have beer cozy. 

78
00:04:08,000 --> 00:04:10,400
Yeah, that's cool. 
Beer koozies for the Beer Garden

79
00:04:10,400 --> 00:04:16,800
tonight, but no, the, I know Pam
shirts and I know, Pam to mmm. 

80
00:04:16,800 --> 00:04:18,899
Yeah, mmm. 
You should check them out, 

81
00:04:18,899 --> 00:04:19,800
right? 
Thank you. 

82
00:04:19,800 --> 00:04:22,200
Each need a shirt. 
I'm sure we'll stop by get. 

83
00:04:22,200 --> 00:04:23,900
Get some get some right? 
That's the one thing I haven't 

84
00:04:23,900 --> 00:04:27,000
done yet is go really through 
the vendor home or the expo 

85
00:04:27,000 --> 00:04:29,700
hall, whatever we're calling it.
And actually, like talk with a 

86
00:04:29,700 --> 00:04:33,100
vendor's, I feel like I've just 
been working the whole time and 

87
00:04:33,100 --> 00:04:35,500
not only had a chance to like, 
actually explore and talk with 

88
00:04:35,500 --> 00:04:38,100
some of the vendors out there, I
was hanging out the one Cosmos 

89
00:04:38,600 --> 00:04:43,200
one Cosmos Booth. 
I can say that one Cosmos booth 

90
00:04:43,200 --> 00:04:46,500
for like five minutes and I saw 
there's people who go around 

91
00:04:46,500 --> 00:04:49,200
from Booth to Booth who just 
yeah. 

92
00:04:49,400 --> 00:04:53,000
My badge so I can get this way. 
Although swaggered of the you 

93
00:04:53,000 --> 00:04:56,700
have and throw them bag so I 
know why do they want to carry 

94
00:04:56,700 --> 00:05:00,200
all those home? 
I don't I just don't know what 

95
00:05:00,200 --> 00:05:02,100
were no. 
I mean early in my conference 

96
00:05:02,100 --> 00:05:05,800
going days I would try to get 
the t-shirts and you wash them 

97
00:05:05,800 --> 00:05:09,200
twice and then you have to throw
them out because they fall 

98
00:05:09,200 --> 00:05:11,100
apart. 
Not that savings t-shirts like 

99
00:05:11,100 --> 00:05:13,500
that I'm sure they're very high 
quality and are very high 

100
00:05:13,500 --> 00:05:15,900
quality. 
High quality cotton gold and 

101
00:05:15,900 --> 00:05:18,200
platinum threads yes stuff like 
that. 

102
00:05:19,300 --> 00:05:21,900
I don't know, every conference 
seems to have those folks who 

103
00:05:21,900 --> 00:05:24,400
like to just accumulate all the 
stuff that is. 

104
00:05:24,400 --> 00:05:26,100
That is true. 
It's like RSA was the same way. 

105
00:05:26,100 --> 00:05:28,900
I remember walking through like 
if you've been RSA it's at the 

106
00:05:28,900 --> 00:05:31,700
Moscone Center downtown San 
Francisco and they have this 

107
00:05:31,700 --> 00:05:34,800
tunnel that basically connects 
North and South which is 

108
00:05:34,800 --> 00:05:37,300
typically where they have like 
the Thunder halls and I remember

109
00:05:37,300 --> 00:05:40,600
walking through a couple years 
ago and they'll the walls were 

110
00:05:40,600 --> 00:05:47,600
lined with people with bags of 
stuff like big shopping bags to 

111
00:05:47,600 --> 00:05:52,300
handers both. 
Hands like loaded with Just Junk

112
00:05:53,100 --> 00:05:56,000
and I'm like, okay, how are you 
going to get that anywhere and 

113
00:05:56,000 --> 00:05:58,900
it is that how is that worth 
anything to anyone, right? 

114
00:05:59,400 --> 00:06:02,700
I don't get it stress. 
Squeeze balls. 

115
00:06:03,600 --> 00:06:06,600
Yeah, when I was stupid stuff, I
mean Jeff you forgot to mention.

116
00:06:06,600 --> 00:06:08,900
Also we are in this luxurious 
Suite. 

117
00:06:08,900 --> 00:06:13,800
We are 66 degrees and our 
friends at our SM are paying the

118
00:06:13,808 --> 00:06:16,000
bill for us. 
So we're very appreciative of 

119
00:06:16,000 --> 00:06:16,800
that. 
They are. 

120
00:06:16,900 --> 00:06:19,100
Thank you very much Artisan for 
keeping me cool while. 

121
00:06:19,300 --> 00:06:20,800
We're putting out this hot 
podcast. 

122
00:06:20,800 --> 00:06:24,800
Yeah yes I don't think we have 
to pay extra for sure our 

123
00:06:24,800 --> 00:06:28,700
conditioning but well I we've 
got technically cops too. 

124
00:06:28,900 --> 00:06:31,300
So we trade this Cubs for 
t-shirts. 

125
00:06:31,700 --> 00:06:33,900
That's a good trait. 
And icid, tumblers, we've been 

126
00:06:33,900 --> 00:06:37,700
given away to folks who have 
been appearing on VIPs, only 

127
00:06:37,700 --> 00:06:40,600
VIPs only, yes. 
And anyone else who we can get 

128
00:06:40,600 --> 00:06:45,400
up here. 
So, let's get back to the 

129
00:06:45,407 --> 00:06:46,900
conference because you 
mentioned, you were having 

130
00:06:46,900 --> 00:06:49,200
conversations one of the 
conversations that you had was 

131
00:06:49,300 --> 00:06:52,900
Actually a presentation. 
Yes, it was a panel that you 

132
00:06:52,900 --> 00:06:55,900
hosted yesterday that was called
stories of cloud identity 

133
00:06:55,900 --> 00:06:58,200
transformation. 
And you had representatives from

134
00:06:58,200 --> 00:07:03,200
brown-forman Wawa and Phillips 
66 for folks who didn't catch it

135
00:07:03,200 --> 00:07:05,800
live. 
I guess, what's the synopsis 

136
00:07:05,800 --> 00:07:07,600
from from that conversation? 
Yeah. 

137
00:07:07,600 --> 00:07:11,700
So I would say that overall 
theme was really about 

138
00:07:11,800 --> 00:07:16,700
technology using technology to 
enable a larger Cloud 

139
00:07:16,700 --> 00:07:21,400
transformation strategy. 
However, it's not just about 

140
00:07:21,400 --> 00:07:24,400
technology so it goes back to 
some of the principles that the 

141
00:07:24,400 --> 00:07:28,000
three of us are very familiar 
with, as we did Consulting with 

142
00:07:28,000 --> 00:07:31,900
our customers, is that it's all 
about policy. 

143
00:07:31,900 --> 00:07:34,900
You need to nail a policy. 
The policy that needs to be 

144
00:07:34,900 --> 00:07:38,300
supported by the process, the 
process needs to be supported by

145
00:07:38,300 --> 00:07:41,600
the data and then you have 
success with technology. 

146
00:07:42,000 --> 00:07:45,200
So it was, it was a pretty 
interesting conversation. 

147
00:07:45,200 --> 00:07:47,400
They came with different 
perspectives. 

148
00:07:48,200 --> 00:07:51,700
Certainly, there is A lot of 
discussion around, you know, how

149
00:07:51,700 --> 00:07:57,100
do you approach moving from 
Legacy to Cloud, you know, to 

150
00:07:57,100 --> 00:07:59,400
support those initiatives? 
Was there? 

151
00:07:59,400 --> 00:08:02,000
Anything surprising? 
I'm sure you prepped for it. 

152
00:08:02,000 --> 00:08:04,400
But, you know, with, with the 
folks are on a panel but was 

153
00:08:04,400 --> 00:08:06,100
anything surprising? 
That came from a story 

154
00:08:06,100 --> 00:08:08,000
perspective was like, oh, I 
hadn't really kind of like, 

155
00:08:08,000 --> 00:08:10,300
thought of that or was it? 
Yeah. 

156
00:08:10,300 --> 00:08:12,900
I kind of knew what I was 
getting into and sort of what to

157
00:08:12,900 --> 00:08:17,300
expect or maybe it was even the 
panel themselves were they 

158
00:08:17,300 --> 00:08:19,100
didn't realize really what they 
were getting into. 

159
00:08:19,200 --> 00:08:21,500
I sort of had some realizations 
after the fact. 

160
00:08:22,400 --> 00:08:30,300
Yeah, I think that what often 
goes on not unnoticed. 

161
00:08:30,300 --> 00:08:33,900
But I think what organizations 
don't think about is the support

162
00:08:33,900 --> 00:08:38,400
that's necessary from a 
multitude of various resources 

163
00:08:38,400 --> 00:08:41,000
to be successful. 
And that's something that each 

164
00:08:41,000 --> 00:08:46,400
of them touched on it at one 
point or another is, how do you 

165
00:08:46,400 --> 00:08:49,600
bring together the right 
collections of people You be 

166
00:08:49,600 --> 00:08:54,000
successful and whether that's to
streamline onboarding, whether 

167
00:08:54,000 --> 00:08:58,800
it's to do data correlation, 
whether it's to do, clean up, it

168
00:08:58,800 --> 00:09:05,700
goes back to realistic, time, 
schedules and how you lead your 

169
00:09:06,600 --> 00:09:10,100
team's through those programs 
because you have so many touch 

170
00:09:10,100 --> 00:09:15,600
points that often the often 
aren't thought about, I guess. 

171
00:09:15,800 --> 00:09:19,800
Yeah, I was also thinking is 
there sitting that session We 

172
00:09:19,800 --> 00:09:21,900
talk about those three 
organizations. 

173
00:09:21,900 --> 00:09:24,700
You measure was a brown-forman. 
Wow. 

174
00:09:24,700 --> 00:09:26,900
And while well until it's. 
Yeah. 

175
00:09:26,900 --> 00:09:29,500
So I mean, there's our 
organizations that were already 

176
00:09:29,500 --> 00:09:35,700
Big 10, 15 years ago so they've 
already had IM systems probably 

177
00:09:35,700 --> 00:09:39,200
Legacy systems that were 
replaced by Saving. 

178
00:09:39,200 --> 00:09:41,700
I'm obviously guessing right. 
I don't know the background, 

179
00:09:41,700 --> 00:09:47,200
man, but my perspective is when 
you're going to drop in a new 

180
00:09:47,200 --> 00:09:51,300
system, you have to be willing. 
Open-minded to change and that 

181
00:09:51,300 --> 00:09:55,500
change includes a, maybe the way
we've been doing things is not 

182
00:09:55,500 --> 00:10:00,000
the way we should do them in the
future for some people that's 

183
00:10:00,200 --> 00:10:01,200
common sense. 
Right? 

184
00:10:01,300 --> 00:10:03,800
For other people. 
That's like sacrilege, like 

185
00:10:03,800 --> 00:10:07,800
there's no way we're to change 
how he on board people, right? 

186
00:10:08,000 --> 00:10:11,200
Ya know there's a lot of 
business process reframing that 

187
00:10:11,200 --> 00:10:13,400
has to happen. 
Because why Port something over 

188
00:10:13,400 --> 00:10:17,900
from a legacy solution into 
something that is going to give 

189
00:10:17,900 --> 00:10:23,100
you the advantage. 
Age of intelligence and make 

190
00:10:23,100 --> 00:10:27,900
suggestions to you, in terms of 
what users should have access to

191
00:10:27,900 --> 00:10:30,000
what users shouldn't have access
to. 

192
00:10:31,100 --> 00:10:33,200
You know, you certainly don't 
want to pour it over bad 

193
00:10:33,200 --> 00:10:36,200
processes and bad data into a 
new solution. 

194
00:10:36,400 --> 00:10:39,600
So certainly process 
re-engineering and I think that 

195
00:10:39,600 --> 00:10:43,300
goes overlooked to, I don't 
think a lot of customers, spend 

196
00:10:43,300 --> 00:10:47,700
a lot of time realizing that 
there's there's work that they 

197
00:10:47,700 --> 00:10:53,000
need to consider as part of 
their Yeah, a lot of y'all to 

198
00:10:53,000 --> 00:10:55,400
make garbage, what do you got 
garbage? 

199
00:10:55,400 --> 00:10:59,200
Exactly this more of it, more 
efficient garbage, generation 

200
00:10:59,200 --> 00:11:02,600
minutes, you've talked a few, 
you know, we talked a little bit

201
00:11:02,600 --> 00:11:06,700
about, I guess your role here 
with save Ian's, tell us about 

202
00:11:06,700 --> 00:11:08,400
Sabian. 
I think one thing that we want 

203
00:11:08,400 --> 00:11:10,300
to kind of bring to folks 
especially this week of 

204
00:11:10,300 --> 00:11:12,500
Gartner's, getting getting 
people familiar with some of the

205
00:11:12,500 --> 00:11:15,900
vendors that are in this space. 
What a Sabian do how you guys 

206
00:11:15,900 --> 00:11:18,300
different from others that are 
that are competing in the same 

207
00:11:18,300 --> 00:11:19,900
area. 
Yeah, it's funny. 

208
00:11:19,900 --> 00:11:25,400
So it was roughly, I don't know,
five six years ago where a sad 

209
00:11:25,400 --> 00:11:29,200
day oh where Jeff? 
And I discovered save Ian and we

210
00:11:29,200 --> 00:11:34,100
were looking at the fine grain 
entitlements and s0d capability.

211
00:11:34,100 --> 00:11:38,700
That was specific to sap. 
And we thought, huh? 

212
00:11:38,700 --> 00:11:40,300
This is interesting. 
They're doing something a little

213
00:11:40,300 --> 00:11:42,500
bit different, it's very 
configurable. 

214
00:11:42,500 --> 00:11:46,300
There's a lot of visibility. 
There's a lot of orientation 

215
00:11:46,300 --> 00:11:50,700
around key indicators, and 
Health of programs. 

216
00:11:51,100 --> 00:11:55,300
And as we peel back the onion, 
we had more and more interest so

217
00:11:55,300 --> 00:11:56,900
much. 
So that I said, I think I'm 

218
00:11:56,900 --> 00:11:58,200
going to go work for this 
company. 

219
00:11:58,200 --> 00:12:02,600
So here I am four years later 
and I think that was one aspect.

220
00:12:02,600 --> 00:12:07,400
It was they were already 
converging you know years ago 

221
00:12:07,700 --> 00:12:12,100
where they started, we started 
with fine green entitlements 

222
00:12:12,100 --> 00:12:14,500
management. 
We realized very quickly that we

223
00:12:14,500 --> 00:12:19,000
had to wrap identity governance 
and administration around that. 

224
00:12:19,100 --> 00:12:22,500
At, and then we've continued to 
converge from there. 

225
00:12:22,500 --> 00:12:26,400
So, you know, being a solution 
that was architected born from 

226
00:12:26,400 --> 00:12:29,500
the cloud. 
And, and it had the inherent 

227
00:12:29,500 --> 00:12:32,900
intelligence that, you know, 
these types of platforms need 

228
00:12:33,000 --> 00:12:37,000
were some of the, you know, very
early reasons why I thought it 

229
00:12:37,000 --> 00:12:40,400
was going to be a pretty 
interesting company and and 

230
00:12:40,400 --> 00:12:43,200
start to shake up the industry a
little bit. 

231
00:12:43,500 --> 00:12:45,500
Remember sitting in that demo 
with you and I was like, oh, 

232
00:12:45,500 --> 00:12:49,400
this is, this is different. 
This is interesting, like it Is 

233
00:12:50,800 --> 00:12:52,900
it showed a lot of Promise? 
Remember seeing it the first 

234
00:12:52,900 --> 00:12:55,700
time, just because of the, the 
approach that was being taken 

235
00:12:55,700 --> 00:12:57,600
with the sap rules, for example,
right? 

236
00:12:57,600 --> 00:13:01,400
And that was a weakness that 
others in the space had and it's

237
00:13:01,500 --> 00:13:05,500
a notoriously difficult system 
for any IGA vendor to really 

238
00:13:05,500 --> 00:13:07,100
kind of get, right? 
And it was, it was interesting. 

239
00:13:07,100 --> 00:13:09,800
It's, it's always fascinating to
see, you know these, these 

240
00:13:09,800 --> 00:13:12,400
vendors and out there saving 
included, but others, you know, 

241
00:13:12,400 --> 00:13:15,300
playing in the same space and 
their evolution on the different

242
00:13:15,300 --> 00:13:20,600
capabilities and I look at save 
Ian and I see A platform, right?

243
00:13:20,600 --> 00:13:25,000
And we were talking with, we saw
maida and clear skies built on a

244
00:13:25,000 --> 00:13:27,500
platform, they're built on the 
servicenow platform, right? 

245
00:13:27,500 --> 00:13:30,500
So, I see this is sort of like 
the other side of that coin, 

246
00:13:30,500 --> 00:13:32,600
which is okay. 
We want to have our identity 

247
00:13:32,600 --> 00:13:35,300
system, be the platform, right? 
Yeah. 

248
00:13:35,300 --> 00:13:38,800
And we've done it in a way that 
it's been very organic in 

249
00:13:38,800 --> 00:13:44,300
nature, you know, we're our own 
platform, we haven't done a 

250
00:13:44,300 --> 00:13:47,600
number of, you know, Tech 
Acquisitions, but we then have 

251
00:13:47,600 --> 00:13:52,400
to fold into Our solution. 
So it's all been very natural. 

252
00:13:52,400 --> 00:13:56,700
We have some Visionaries, you 
know, in the organization and 

253
00:13:56,700 --> 00:14:02,800
that's what brought us to Pam, 
you know, needing and seeing the

254
00:14:02,800 --> 00:14:07,100
the need for that single 
Enterprise journey and the 

255
00:14:07,100 --> 00:14:10,400
appropriate context that you 
apply to that single Enterprise 

256
00:14:10,400 --> 00:14:12,900
Journey. 
So that, you know, if you're a 

257
00:14:12,900 --> 00:14:16,400
regular user doing regular user 
things, you can do it very 

258
00:14:16,400 --> 00:14:21,700
easily versus if you need Need 
to perform something that's 

259
00:14:21,700 --> 00:14:25,000
administrative in nature. 
Well, we only want to give you 

260
00:14:25,000 --> 00:14:27,400
the access that you need for 
that moment in time and that 

261
00:14:27,400 --> 00:14:30,200
moment in time might be five 
minutes, it might be 10 minutes 

262
00:14:30,600 --> 00:14:34,600
and giving the visibility to 
ensure that whatever was done 

263
00:14:34,600 --> 00:14:38,300
with the access that was granted
for that period of time or just 

264
00:14:38,300 --> 00:14:41,300
generally speaking. 
If you're a regular user that we

265
00:14:41,300 --> 00:14:45,000
have the history you know behind
it to support that Enterprise 

266
00:14:45,000 --> 00:14:47,500
Journey. 
Can you prove what you said you 

267
00:14:47,500 --> 00:14:49,000
did? 
It happened in the way. 

268
00:14:49,200 --> 00:14:50,800
You said it was going to happen.
Rent. 

269
00:14:50,900 --> 00:14:54,200
Exactly, yeah. 
One of the things that I've 

270
00:14:54,200 --> 00:14:58,800
always felt when I saw saving, 
was that, you could really 

271
00:14:59,100 --> 00:15:01,900
configure the system to work the
way you want. 

272
00:15:02,100 --> 00:15:05,400
And I think like this, why? 
There are so many parts, so many

273
00:15:05,400 --> 00:15:08,600
products in the imc's, there's 
different ones that suit 

274
00:15:08,600 --> 00:15:12,900
different needs and different 
organizations wants and desires.

275
00:15:13,300 --> 00:15:17,100
So my thought on the 
configurability is like I love 

276
00:15:17,100 --> 00:15:19,700
that personally. 
I'm like, I want It to be able 

277
00:15:19,700 --> 00:15:24,200
to tune the system to the way I 
want others want. 

278
00:15:24,200 --> 00:15:29,300
Like, give me the exact, you 
know, Simple Simon way to 

279
00:15:29,300 --> 00:15:32,500
configure the system, and I 
don't want that configurability,

280
00:15:32,500 --> 00:15:37,500
but I think that as a product, 
or as a platform, you have to 

281
00:15:37,500 --> 00:15:39,700
decide which end of the 
spectrum. 

282
00:15:39,700 --> 00:15:41,600
Are we going to be on? 
Or we're going to try to 

283
00:15:41,900 --> 00:15:44,900
restrict your ability to 
configure the system, or we 

284
00:15:44,900 --> 00:15:50,100
going to enable that and it 
seems to me that Savings more on

285
00:15:50,100 --> 00:15:53,700
the, we're going to enable you 
to have the system work, the way

286
00:15:53,700 --> 00:15:55,500
you want. 
Yeah, 100%. 

287
00:15:55,500 --> 00:15:59,000
There's a lot of configuration 
capability, but there's also the

288
00:15:59,000 --> 00:16:03,600
movement towards, you know, 
continuing to be very API 

289
00:16:03,600 --> 00:16:10,200
friendly as an example and the 
the thought around bring your 

290
00:16:10,200 --> 00:16:13,700
own. 
So now, you know, we want to 

291
00:16:13,700 --> 00:16:18,300
encourage customers and partners
to do things like build their 

292
00:16:18,300 --> 00:16:21,300
own integration. 
Nations build their own, you 

293
00:16:21,300 --> 00:16:23,600
eyes and bring those things 
along. 

294
00:16:23,600 --> 00:16:28,700
So, you know, not only can you 
configure the 80% of the 

295
00:16:28,700 --> 00:16:33,700
standard capability that you 
might require the other 20% that

296
00:16:33,700 --> 00:16:36,900
you might want to make very 
specific to your unique business

297
00:16:36,900 --> 00:16:39,600
problems. 
You can bring it along with you 

298
00:16:39,600 --> 00:16:42,500
because we have that 
extensibility layer to do so. 

299
00:16:43,200 --> 00:16:47,400
Building your own UI that is 
bold because I think that's 

300
00:16:47,400 --> 00:16:50,600
something that normally most 
people would associate. 

301
00:16:50,600 --> 00:16:53,500
It was the identity space with 
more of a consumer based 

302
00:16:53,500 --> 00:16:56,400
approach where you've got like 
marketing and communication 

303
00:16:56,400 --> 00:16:58,700
seems everyone. 
I like craft the customer 

304
00:16:58,700 --> 00:17:01,600
experience and usually you'll 
see things like apis and stuff, 

305
00:17:01,600 --> 00:17:03,000
kind of power and things behind 
the scenes. 

306
00:17:03,700 --> 00:17:05,599
And I guess this is maybe a 
little bit of news to me, so you

307
00:17:05,599 --> 00:17:08,700
can educate me. 
When you say build your own UI, 

308
00:17:09,200 --> 00:17:13,300
what are you talking about? 
So I would say that At a likely 

309
00:17:13,300 --> 00:17:19,000
scenario would be mostly or more
along the lines of third-party 

310
00:17:19,000 --> 00:17:23,900
access governance. 
So, you know, it's not science 

311
00:17:23,900 --> 00:17:27,800
necessarily but you have 
delegated Administration and you

312
00:17:27,800 --> 00:17:32,100
have diverse different business 
entities, different types of 

313
00:17:32,100 --> 00:17:36,600
third, party users. 
And perhaps you want to create a

314
00:17:36,600 --> 00:17:42,700
very simplistic UI for the third
party users. 

315
00:17:42,800 --> 00:17:45,700
Who are accessing your system. 
That's just that's one thing 

316
00:17:45,700 --> 00:17:49,000
that comes to mind but, you 
know, there's a lot of 

317
00:17:49,000 --> 00:17:51,900
configuration within the UI 
itself. 

318
00:17:51,900 --> 00:17:55,500
So there's not a necessity to 
bring your own, we just wanted 

319
00:17:55,500 --> 00:17:58,300
to give that extensibility to 
customers. 

320
00:17:58,600 --> 00:18:02,600
I would say, you know, 
Integrations are probably more 

321
00:18:02,600 --> 00:18:05,700
popular than say, bring your 
bring your own UI. 

322
00:18:05,800 --> 00:18:09,000
So here's the topic that Jeff 
and I run into a time, right? 

323
00:18:09,000 --> 00:18:14,400
You have the potential client 
where Their HR Group is saying 

324
00:18:14,400 --> 00:18:18,600
our HR System is for employees 
only, we're only going to manage

325
00:18:18,600 --> 00:18:22,400
employee data yet. 
They have all these non-employee

326
00:18:22,400 --> 00:18:30,000
users contractors Consultants 
guests and you as an IGA vendor 

327
00:18:30,200 --> 00:18:33,100
or really is like a consultant 
to your clients. 

328
00:18:33,800 --> 00:18:36,700
How do you recommend that they 
address that problem? 

329
00:18:36,700 --> 00:18:41,600
Is it manage those people in our
solution or look at some other 

330
00:18:41,600 --> 00:18:43,300
solution created? 
The base. 

331
00:18:43,800 --> 00:18:46,300
What what is your approach to 
that problem? 

332
00:18:47,300 --> 00:18:50,400
It's often managing an hour 
solution, you know, we have 

333
00:18:50,400 --> 00:18:53,900
third party access management, 
so you can do the whole 

334
00:18:53,900 --> 00:18:59,300
cradle-to-grave full lifecycle 
management of those identities. 

335
00:18:59,600 --> 00:19:03,300
So, that's kind of the 
Consulting role of working with 

336
00:19:03,300 --> 00:19:06,600
your clients and one of the big 
themes here at Gartner. 

337
00:19:06,600 --> 00:19:11,900
This week was talking about 
selling and I am program within 

338
00:19:11,900 --> 00:19:14,700
the business rate. 
I think the way you know I've 

339
00:19:14,700 --> 00:19:18,300
referred to how Rebecca who is 
Talk about Bri, you know, 

340
00:19:19,000 --> 00:19:22,700
there's this value of I am, was,
you know, we're going from 

341
00:19:22,700 --> 00:19:25,600
having a seat at the Kids Table 
to having a seat at the adults 

342
00:19:25,600 --> 00:19:28,800
table. 
I am is being taken seriously 

343
00:19:28,800 --> 00:19:30,300
now, right? 
But the way we need to 

344
00:19:30,300 --> 00:19:36,400
communicate the value is in 
terms of the business value that

345
00:19:36,500 --> 00:19:39,100
I am praying, so business 
results. 

346
00:19:40,000 --> 00:19:44,500
Are you helping your clients 
with in terms of like expressing

347
00:19:44,500 --> 00:19:46,500
that value? 
Explain that value? 

348
00:19:46,500 --> 00:19:49,900
Is that something that's in your
wheelhouse or something? 

349
00:19:49,900 --> 00:19:52,900
They're doing ahead of time? 
No, it's in our wheelhouse. 

350
00:19:52,900 --> 00:19:57,300
I would say, oftentimes 
customers Focus so much on very 

351
00:19:57,300 --> 00:20:02,300
explicit requirements because 
you're talking to technology 

352
00:20:02,300 --> 00:20:04,100
folks. 
So we, it is our responsibility 

353
00:20:04,100 --> 00:20:08,200
as subject matter experts to 
take those requirements and 

354
00:20:08,200 --> 00:20:09,900
really understand what's at the 
root. 

355
00:20:10,000 --> 00:20:14,800
Roots of them wanting to do 
something in a certain manner 

356
00:20:14,800 --> 00:20:17,700
or, you know, supporting a 
particular use case. 

357
00:20:18,000 --> 00:20:22,900
So, you know, we always have to 
explain business value. 

358
00:20:22,900 --> 00:20:26,200
I go back to my days of 
Consulting, the the so, what 

359
00:20:26,300 --> 00:20:29,000
you're going to do this. 
So what, you know, what does it 

360
00:20:29,000 --> 00:20:32,800
mean to the business? 
Well, you know, if you're going 

361
00:20:32,800 --> 00:20:37,400
to implement, you know, Pierre 
analytics as part of your access

362
00:20:37,400 --> 00:20:41,300
request process. 
The so what it is that it is 

363
00:20:41,300 --> 00:20:45,300
going to suggest you the 
appropriate access and it makes 

364
00:20:45,300 --> 00:20:49,900
it faster more efficient and 
then there's less work for your 

365
00:20:49,900 --> 00:20:54,100
end users and therefore they're 
spending less time managing 

366
00:20:54,100 --> 00:20:56,500
their access. 
So we always have to go back to 

367
00:20:56,500 --> 00:20:58,300
the. 
So what and the business value 

368
00:20:58,300 --> 00:21:02,600
and ensuring that you know, we 
have the right level of risk 

369
00:21:02,600 --> 00:21:06,500
balance with the right level of,
you know, business process and 

370
00:21:06,500 --> 00:21:07,800
efficiency. 
Yeah. 

371
00:21:07,800 --> 00:21:09,800
I think that's the big 
partnership. 

372
00:21:10,600 --> 00:21:15,500
We're a technology vendor or 
Consulting partner can bring to 

373
00:21:15,500 --> 00:21:20,900
their clients has you know being
able to help articulate that 

374
00:21:20,900 --> 00:21:24,500
message and kind of, you know, 
one of the thoughts. 

375
00:21:24,500 --> 00:21:27,000
I was also having a sure you 
kind of run into this. 

376
00:21:27,000 --> 00:21:32,300
A lot is, how do you help 
clients hit the ground quickly, 

377
00:21:32,500 --> 00:21:35,700
rather than like buying software
and then kind of coming up to 

378
00:21:35,700 --> 00:21:37,600
me? 
It's like, you know, you need to

379
00:21:37,600 --> 00:21:39,700
have that roadmap, you need to 
have that plan. 

380
00:21:39,900 --> 00:21:44,300
Before you, you know, execute 
your contract and that clock 

381
00:21:44,300 --> 00:21:47,800
starts ticking read the bills. 
Start piling up pretty quickly 

382
00:21:48,500 --> 00:21:52,300
and you want to get something 
out there in production as 

383
00:21:52,300 --> 00:21:56,000
quickly as possible. 
And reality like the scenario 

384
00:21:56,000 --> 00:21:59,800
where you buy the software and 
it becomes self-aware for your 

385
00:22:00,800 --> 00:22:03,000
the technology vendor doesn't 
want that, right? 

386
00:22:03,000 --> 00:22:05,400
That's it's like not like our 
goalie. 

387
00:22:05,400 --> 00:22:08,300
Hey like was like gym, 
memberships, like I think Jim's 

388
00:22:08,300 --> 00:22:11,800
like to sell memberships and The
people stop dumbbell upright, 

389
00:22:11,800 --> 00:22:13,900
they don't show up, that's their
bhisma. 

390
00:22:13,900 --> 00:22:17,300
I don't think that technology 
vendors want that, right? 

391
00:22:17,700 --> 00:22:23,200
We don't and in fact, we've done
a lot of things to be able to 

392
00:22:23,300 --> 00:22:27,900
implement micro phases 
microprojects and six eight, ten

393
00:22:27,900 --> 00:22:31,400
weeks to drive that value. 
So something that I think is 

394
00:22:31,400 --> 00:22:35,400
interesting that, you know, we 
do as an organization is you 

395
00:22:35,400 --> 00:22:38,500
know, the concepts in selling. 
You have mutual action plans. 

396
00:22:38,500 --> 00:22:40,900
So what are the steps that are 
required Acquired to 

397
00:22:41,700 --> 00:22:45,900
essentially, get a customer to 
buy a solution and and what we 

398
00:22:45,900 --> 00:22:50,500
do is we create a technology 
aspect of that. 

399
00:22:50,700 --> 00:22:54,400
What are the things that need to
happen for the customer to, 

400
00:22:54,400 --> 00:22:58,300
truly understand the advantage 
of the solution? 

401
00:22:58,300 --> 00:23:01,000
And then break it down into 
little teeny, tiny Parts. 

402
00:23:01,300 --> 00:23:03,600
Because we're still in a 
situation where all the 

403
00:23:03,600 --> 00:23:07,400
education that we're doing is 
really being done through Zoom. 

404
00:23:07,400 --> 00:23:09,700
There's still a lot of fatigue 
in these, these room. 

405
00:23:09,900 --> 00:23:13,200
Meetings. 
People don't want to be in 345 

406
00:23:13,700 --> 00:23:18,300
our Workshop settings so we 
break it down into technical 

407
00:23:18,300 --> 00:23:21,600
action plans, so that we peel 
back the onion. 

408
00:23:21,700 --> 00:23:24,600
We really can focus in on the 
pain points and then we can 

409
00:23:24,600 --> 00:23:30,500
drive a strategy that aligns 
with essentially, like a quick 

410
00:23:30,500 --> 00:23:33,600
start approach to getting 
something laid down for the 

411
00:23:33,600 --> 00:23:38,300
customer, so that we don't take 
time between, you know, a 

412
00:23:38,300 --> 00:23:41,600
customer being on board. 
Added as a saving a customer and

413
00:23:41,600 --> 00:23:45,500
then seeing that value. 
So we try to set that up in 

414
00:23:45,500 --> 00:23:49,500
advance through those workshops.
I love that idea that what you 

415
00:23:49,500 --> 00:23:53,400
call it quick action plan, but 
like four weeks six weeks, eight

416
00:23:53,400 --> 00:23:56,500
weeks of value. 
Give us some examples of like 

417
00:23:56,500 --> 00:23:59,400
what the scope of something like
that might look like. 

418
00:24:00,600 --> 00:24:04,600
Yeah. 
So I would say, for example, you

419
00:24:04,608 --> 00:24:10,100
know, taking some number of 
critical applications and Just 

420
00:24:10,100 --> 00:24:12,700
going back to what is your data 
look like. 

421
00:24:12,700 --> 00:24:15,700
So something that's very easy as
you start with the data. 

422
00:24:15,700 --> 00:24:20,800
What does that mean? 
Well, let's look at your risky 

423
00:24:21,400 --> 00:24:27,100
entitlements for particular 
number of applications and let's

424
00:24:27,100 --> 00:24:30,600
get it through a certification. 
Let's get the revokes in place 

425
00:24:30,600 --> 00:24:36,100
and let's clean up the data. 
So very very quick way to get a 

426
00:24:36,108 --> 00:24:39,700
win in eight to ten weeks. 
Yeah, for an organization that's

427
00:24:39,800 --> 00:24:45,100
About to spend money on an IGA 
solution, you can be pretty sure

428
00:24:45,500 --> 00:24:48,600
there's some data issues, right?
There's going to be some say 

429
00:24:48,600 --> 00:24:50,600
it's always cobs. 
What I'm talking about man. 

430
00:24:50,700 --> 00:24:53,700
Yeah, you give me some cobwebs 
in that data. 

431
00:24:53,700 --> 00:24:57,500
So they get data cleanup 
exercise, where you can leverage

432
00:24:57,500 --> 00:25:00,500
that investment is a fantastic 
idea. 

433
00:25:00,600 --> 00:25:02,800
You need to do the cleanup, 
right? 

434
00:25:02,800 --> 00:25:05,900
But you don't want to take six 
months and that's all you do, 

435
00:25:06,000 --> 00:25:07,800
right? 
So if you can kind of lay down, 

436
00:25:07,800 --> 00:25:12,200
some technology footprint, sir. 
To import that data correlated, 

437
00:25:12,200 --> 00:25:18,200
look for the bad stuff and maybe
gate your user interface out to 

438
00:25:18,200 --> 00:25:22,600
some business users. 
Who can start to, you know, 

439
00:25:22,600 --> 00:25:25,700
knock out the cobwebs. 
Great idea. 

440
00:25:25,700 --> 00:25:28,400
Yeah. 
And a super high-value activity 

441
00:25:28,400 --> 00:25:32,600
is around, you know, Pam remove 
standing access standing 

442
00:25:32,600 --> 00:25:35,600
privilege. 
Get just-in-time laid down, you 

443
00:25:35,600 --> 00:25:39,700
know, for a series of users and 
we turn that on and get it. 

444
00:25:39,800 --> 00:25:41,800
Implemented for customers in six
weeks. 

445
00:25:41,800 --> 00:25:45,000
So now you've just taken some of
that privilege and 

446
00:25:45,000 --> 00:25:51,400
administration burden away from,
you know, your classic users 

447
00:25:51,400 --> 00:25:54,100
that have just too much 
privilege. 

448
00:25:54,100 --> 00:25:58,200
So eliminate that very quickly. 
Yeah, what I'm hearing is 

449
00:25:58,200 --> 00:26:00,600
Jamie's going to come to your 
house and in six weeks all, 

450
00:26:00,600 --> 00:26:04,200
while your identity problem. 
Not going to try here, she's 

451
00:26:04,200 --> 00:26:06,100
gonna get in there. 
She should clean your data. 

452
00:26:06,600 --> 00:26:09,700
Everything's gonna be just in 
time micro phases. 

453
00:26:09,900 --> 00:26:12,400
Projects, build, success, build 
momentum. 

454
00:26:12,400 --> 00:26:17,000
We all want to, I'm sorry if you
think that, then if you think 

455
00:26:17,000 --> 00:26:19,900
it's gonna all be done in six 
weeks, like I've got some 

456
00:26:19,900 --> 00:26:23,500
beachfront property in Nebraska,
I've got a saw you, but you can 

457
00:26:23,500 --> 00:26:25,700
get stuff done. 
You can get stuff done. 

458
00:26:25,700 --> 00:26:27,100
It doesn't always have to be 
like this. 

459
00:26:27,300 --> 00:26:30,600
Gee whiz, you know, huge public 
facing thing. 

460
00:26:30,600 --> 00:26:33,200
It could be. 
Yeah, we got the data cleaned up

461
00:26:33,500 --> 00:26:36,100
and that's a precursor and guess
what the data is clean now. 

462
00:26:36,200 --> 00:26:38,100
Like it's going to be used other
places to that could be an 

463
00:26:38,100 --> 00:26:41,400
example, could be a very basic 
Workflow to do basic onboarding 

464
00:26:41,400 --> 00:26:43,900
basic off-boarding. 
I feel like sometimes we get 

465
00:26:43,900 --> 00:26:46,900
lost in the grand picture that 
we forget to celebrate the 

466
00:26:46,900 --> 00:26:49,800
little lens on the way, I think.
That's where the best road maps 

467
00:26:49,800 --> 00:26:52,800
come in is, how do you show 
iterative improvements, right? 

468
00:26:52,800 --> 00:26:55,400
Can't just go say, Hey, you go 
me to give me 2 million dollars 

469
00:26:55,400 --> 00:26:58,000
and I'll come back with a night.
And I am platform in two years, 

470
00:26:58,100 --> 00:27:00,800
like, that's not gonna happen. 
Yeah, we talked about it is, get

471
00:27:00,800 --> 00:27:01,700
clean. 
Stay clean. 

472
00:27:02,000 --> 00:27:03,400
Mmm. 
Yeah. 

473
00:27:03,400 --> 00:27:08,500
Well I also think that in 
certain situations as the I am 

474
00:27:08,500 --> 00:27:13,600
program manager or Of you know 
the practitioner, it takes some 

475
00:27:14,100 --> 00:27:18,500
some bold leadership, sometimes 
to, you know work up the chain 

476
00:27:18,500 --> 00:27:21,800
and say we're not going to be 
flipping a switch and nine 

477
00:27:21,800 --> 00:27:24,200
months, all of our problems 
aren't going to go away. 

478
00:27:24,700 --> 00:27:29,200
It is a matter of we're going to
be running an IM program from 

479
00:27:29,200 --> 00:27:32,800
now. 
Until we both retire, we're 

480
00:27:32,800 --> 00:27:36,800
always going to be in this game 
and we're going to get 

481
00:27:36,800 --> 00:27:39,300
ourselves, you know, make the 
path to better. 

482
00:27:40,300 --> 00:27:43,200
But in nine months all of our 
problems are going to be solved.

483
00:27:43,300 --> 00:27:46,200
That's sometimes hard just 
delivering bad news, right? 

484
00:27:46,200 --> 00:27:49,400
That nobody wants to hear my 
spending a million dollars to 

485
00:27:49,400 --> 00:27:52,400
get better. 
Well, that's that's the world we

486
00:27:52,400 --> 00:27:54,300
live in. 
Now, there's always look the 

487
00:27:54,300 --> 00:27:57,600
look for guarantees, right? 
It's, if I give this to you, I 

488
00:27:57,600 --> 00:28:00,100
will never have another audit 
finding again. 

489
00:28:00,200 --> 00:28:04,000
Ya know, you're reducing the 
risk. 

490
00:28:04,000 --> 00:28:06,700
The chance of it happening, 
maybe, but it's not a real like 

491
00:28:06,700 --> 00:28:08,800
realistic expectation. 
Yeah. 

492
00:28:09,300 --> 00:28:10,500
All right. 
Let's And start to wrap things 

493
00:28:10,500 --> 00:28:12,500
up. 
But before we go why know that 

494
00:28:12,500 --> 00:28:15,000
we have Star Wars Super Fan over
here next to me. 

495
00:28:15,500 --> 00:28:17,300
So we're going to close it on a 
lighter note. 

496
00:28:17,300 --> 00:28:20,600
I've got actually a couple, the 
first one. 

497
00:28:21,100 --> 00:28:24,300
Yes. 
Who or what is your favorite 

498
00:28:24,300 --> 00:28:27,800
Star Wars character? 
I know what you're going to say.

499
00:28:27,900 --> 00:28:29,100
I'm going to ask you for an 
alternate. 

500
00:28:29,100 --> 00:28:33,200
I don't want rules. 
I mean it has to be Leia. 

501
00:28:33,400 --> 00:28:37,000
Okay? 
Every little girl loved Princess

502
00:28:37,000 --> 00:28:43,600
Leia because she embodies 
empathy and she brings together 

503
00:28:43,900 --> 00:28:47,200
people for the greater good. 
And that's what I like to think.

504
00:28:47,200 --> 00:28:50,900
I do. 
You still have those big buns on

505
00:28:50,900 --> 00:28:52,500
the side of your when I can you 
can't? 

506
00:28:52,500 --> 00:28:56,000
I've seen the pictures. 
All right? 

507
00:28:56,000 --> 00:28:58,800
And then my My second question, 
still in the Star Wars Universe 

508
00:28:59,000 --> 00:29:02,200
you have a daughter. 
What order did you show her? 

509
00:29:02,200 --> 00:29:05,400
The Star Wars movies and 
obviously we started with 

510
00:29:05,400 --> 00:29:08,700
episode for the true first 
episode. 

511
00:29:08,700 --> 00:29:15,100
The true first episode A New 
Hope and then we moved on to 

512
00:29:15,200 --> 00:29:19,600
five and six and then we went 
seven, eight and nine because 

513
00:29:19,600 --> 00:29:21,200
one, two and three, they just 
don't exist. 

514
00:29:21,200 --> 00:29:23,400
Slow curveball here. 
Hmm. 

515
00:29:24,200 --> 00:29:27,300
I liked what I mean look I I 
like Star Wars. 

516
00:29:27,300 --> 00:29:29,000
I like them all. 
Sure, there were some annoying 

517
00:29:29,000 --> 00:29:31,600
things. 
Even 789 had some weird stuff 

518
00:29:32,500 --> 00:29:35,700
somehow Palpatine returned. 
This is the ladies. 

519
00:29:35,700 --> 00:29:38,600
Yes, piece of writing, I think 
I've ever heard in a major like 

520
00:29:38,600 --> 00:29:41,500
franchise, but I still enjoy it 
for what it is. 

521
00:29:42,000 --> 00:29:47,200
Well, I can tell you that Ray is
also very well-liked in the 

522
00:29:47,200 --> 00:29:48,000
household. 
Okay. 

523
00:29:48,100 --> 00:29:51,500
Mhm. 
I would say she's a second 

524
00:29:51,500 --> 00:29:53,500
favorite. 
Okay, I can see it. 

525
00:29:53,800 --> 00:29:55,100
Jim favorite Star Wars 
character. 

526
00:29:55,400 --> 00:30:00,400
Captain Picard I'm not expect it
boy. 

527
00:30:00,800 --> 00:30:02,100
There goes all of our 
credibility. 

528
00:30:03,600 --> 00:30:06,200
You've been listening to the 
last episode of Daredevil in 

529
00:30:06,200 --> 00:30:07,700
certain pockets. 
It's right. 

530
00:30:08,100 --> 00:30:10,600
It's gonna be a solo show going 
forward and I like to look at my

531
00:30:10,600 --> 00:30:14,800
new clothes. 
Jamie I'm gonna go with Han Solo

532
00:30:14,800 --> 00:30:16,600
just cause I always thought he 
was bad ass. 

533
00:30:16,600 --> 00:30:19,500
And, you know, any orange 
jumpsuit known on the orange 

534
00:30:19,500 --> 00:30:21,900
jumpsuit. 
That was the best console. 

535
00:30:22,000 --> 00:30:23,100
What. 
Yeah. 

536
00:30:23,100 --> 00:30:25,200
What are you talking about? 
We know that's wrong. 

537
00:30:26,900 --> 00:30:29,900
Captive card. 
All right, we're going to call 

538
00:30:29,900 --> 00:30:31,700
this one because it's gone off 
the rails. 

539
00:30:31,700 --> 00:30:34,400
Yep. 
We're we've gone off the tracks.

540
00:30:34,600 --> 00:30:37,100
All right, thank you very much 
for joining. 

541
00:30:37,300 --> 00:30:39,400
It's good to see you again. 
Lovely to see you. 

542
00:30:39,400 --> 00:30:43,100
Another part of the family here 
from Identity, as far as we go, 

543
00:30:43,100 --> 00:30:45,300
you can find us on the web 
identity to center.com. 

544
00:30:45,300 --> 00:30:47,700
We're on Twitter at idea. 
See podcast. 

545
00:30:47,900 --> 00:30:52,300
If you want to learn more about 
savings and connect with, Jamie 

546
00:30:52,300 --> 00:30:55,300
will have Shola links in the 
show notes, but you can find 

547
00:30:55,300 --> 00:31:00,800
save Aunt, essay, Avi ynt.com 
and we'll go ahead and leave it 

548
00:31:00,800 --> 00:31:03,100
there for this week. 
Thanks everyone for listening 

549
00:31:03,200 --> 00:31:04,700
and we'll talk with everyone in 
the next one. 

550
00:31:08,700 --> 00:31:11,600
Thanks for listening to the 
identity at the center podcast. 

551
00:31:11,700 --> 00:31:14,000
If you like what you heard, 
don't forget to subscribe and 

552
00:31:14,000 --> 00:31:17,100
visit us on the web and identity
at the center.com.