1
00:00:00,000 --> 00:00:01,180
Why don't you introduce yourself?

2
00:00:01,520 --> 00:00:01,940
Yeah, sure.

3
00:00:02,100 --> 00:00:02,760
My name is Tai Lange.

4
00:00:02,840 --> 00:00:05,180
I work in the credit bank IT team.

5
00:00:05,320 --> 00:00:10,020
I am responsible for software architecture, cloud and middleware, database and storage

6
00:00:10,020 --> 00:00:11,460
and the DevOps teams.

7
00:00:11,600 --> 00:00:13,620
You've got a big stable of things.

8
00:00:13,760 --> 00:00:16,340
How do you structure that organization?

9
00:00:16,700 --> 00:00:21,680
Before my current role, I was the director of the software infrastructure and architecture.

10
00:00:22,060 --> 00:00:27,840
And there we started working with cloud and also the software part, the new architecture,

11
00:00:27,980 --> 00:00:28,720
software architecture.

12
00:00:28,720 --> 00:00:35,040
So I believe that today with the DevOps and that kind of methodologies, infrastructure,

13
00:00:35,260 --> 00:00:38,600
middleware and also the software part come together.

14
00:00:39,080 --> 00:00:43,140
There are too many common goals and objects to work on.

15
00:00:43,380 --> 00:00:49,400
After I worked in this position more than three years, but after that, the infrastructure part

16
00:00:49,400 --> 00:00:56,320
also came under my responsibility so that the team, we have now a bigger team and also we

17
00:00:56,320 --> 00:00:59,640
work more closely and we are going to the same direction.

18
00:00:59,640 --> 00:01:05,560
It is not a common organization, I can say, because in the enterprises, generally, the software

19
00:01:05,560 --> 00:01:08,340
part and the infrastructure part are separated.

20
00:01:08,580 --> 00:01:14,580
But in order to work more efficiently, we structured like this and we are working in this organization

21
00:01:14,580 --> 00:01:16,400
around one and a half year now.

22
00:01:16,640 --> 00:01:18,260
It is so far so good, I can say.

23
00:01:18,260 --> 00:01:23,580
I agree with you completely that most large organizations and particularly banks, most large

24
00:01:23,580 --> 00:01:29,140
organizations, there's no particularly, but definitely banks that I talk with, they all of those

25
00:01:29,140 --> 00:01:32,580
functions are, am I exaggerating, are very separate.

26
00:01:32,740 --> 00:01:38,040
Some of them are like a little less separate, but definitely infrastructure and applications and

27
00:01:38,040 --> 00:01:40,380
development tend to be very separate.

28
00:01:40,380 --> 00:01:46,580
The question they often have is a little bit that you're alluding to is we know we shouldn't

29
00:01:46,580 --> 00:01:50,600
be operating this way, but like we can't figure out changing.

30
00:01:50,840 --> 00:01:55,100
And since you're saying like, you know, you recently moved over to consolidating all this,

31
00:01:55,240 --> 00:01:55,940
what was that like?

32
00:01:56,000 --> 00:02:00,680
How did you kick that off and get across any barriers that, how did you pull that off?

33
00:02:00,740 --> 00:02:01,480
It's a rare feat.

34
00:02:01,760 --> 00:02:05,520
It's a good question because when there's something happen, there are some changes.

35
00:02:05,720 --> 00:02:11,140
Everyone, especially the teams, when you assign to a team, there's a fear, I can say.

36
00:02:11,240 --> 00:02:13,540
And also some reflections to change.

37
00:02:13,820 --> 00:02:15,880
Maybe it is not so easy, I can say.

38
00:02:16,080 --> 00:02:19,740
We are, by the way, we are doing it not for just my underlying responsibility.

39
00:02:20,160 --> 00:02:23,660
We are also changing the organization for the delivery teams as well.

40
00:02:23,720 --> 00:02:25,540
We are switching to product teams.

41
00:02:25,680 --> 00:02:27,080
We say it's product teams.

42
00:02:27,460 --> 00:02:27,540
Right.

43
00:02:27,840 --> 00:02:33,100
Under these product teams, before this organization, the analyst teams, business analyst teams,

44
00:02:33,220 --> 00:02:36,020
and the software development teams were separate.

45
00:02:36,320 --> 00:02:39,780
And also there was a central testing team, for example.

46
00:02:40,260 --> 00:02:47,620
But now, today, we are switching to product teams, which all of these functionalities are

47
00:02:47,620 --> 00:02:48,980
consolidated in one team.

48
00:02:49,120 --> 00:02:51,520
And there is a product manager at the head of that team.

49
00:02:51,620 --> 00:02:52,620
This is the delivery side.

50
00:02:52,740 --> 00:02:55,740
And the other side, the infrastructure part is this.

51
00:02:55,740 --> 00:03:02,120
In this kind of an organization, the most challenging part is, especially, you have to give new

52
00:03:02,120 --> 00:03:05,860
responsibilities and also new abilities to people.

53
00:03:06,180 --> 00:03:10,520
And basically, when they are in their comfort zone, it is not so easy for everyone.

54
00:03:10,840 --> 00:03:13,400
Of course, we are a young company.

55
00:03:13,880 --> 00:03:17,880
There are too many volunteers for new technologies, responsibilities, etc.

56
00:03:18,080 --> 00:03:21,340
But there is also some people who don't want to change.

57
00:03:21,720 --> 00:03:24,380
So, that kind of cases we had, I can say.

58
00:03:24,640 --> 00:03:26,140
But how do we figure out it?

59
00:03:26,260 --> 00:03:31,220
First of all, as a leader, we always said that we are always together with them.

60
00:03:31,480 --> 00:03:32,420
We will educate it.

61
00:03:32,480 --> 00:03:34,220
We will give time to them.

62
00:03:34,460 --> 00:03:36,960
And we will give what they need.

63
00:03:37,160 --> 00:03:40,940
And they will be part of this change.

64
00:03:41,100 --> 00:03:42,360
So, there is nothing to fear.

65
00:03:42,400 --> 00:03:43,360
It will be all good.

66
00:03:43,600 --> 00:03:45,120
And now, we are doing it.

67
00:03:45,200 --> 00:03:50,480
For these, for example, we set up different education programs, internal education programs,

68
00:03:50,660 --> 00:03:51,960
external education programs.

69
00:03:52,220 --> 00:03:56,540
And we are making lots of sessions, especially with the COVID.

70
00:03:56,720 --> 00:03:59,660
We can make sessions very easily with huge audience.

71
00:03:59,960 --> 00:04:00,700
So far, so good.

72
00:04:00,760 --> 00:04:02,080
But it is not so easy, I can say.

73
00:04:02,080 --> 00:04:06,200
One of the things you touched on that I think is, that I've been interested in sorting out

74
00:04:06,200 --> 00:04:11,380
recently is, one way of putting it is, you gave people psychological safety.

75
00:04:11,620 --> 00:04:14,540
Like, they felt safe and changing and going through learning things.

76
00:04:14,900 --> 00:04:19,780
And so, I'm curious, like, how do you, how do you make people trust you?

77
00:04:19,920 --> 00:04:24,600
That you actually, we're going to provide you this training and we will support you in doing

78
00:04:24,600 --> 00:04:24,860
this.

79
00:04:24,900 --> 00:04:26,500
Like, how do you win that trust over?

80
00:04:26,600 --> 00:04:28,180
Or, maybe I shouldn't be so cynical.

81
00:04:28,180 --> 00:04:32,700
How do you maintain that trust to make people feel comfortable that you actually will be

82
00:04:32,700 --> 00:04:34,420
supporting them and you mean what you're saying?

83
00:04:34,720 --> 00:04:34,880
Correct.

84
00:04:35,100 --> 00:04:35,600
Good question.

85
00:04:35,760 --> 00:04:37,640
I think we are lucky at this, at that point.

86
00:04:37,780 --> 00:04:41,200
Because in Waikibi, people trust each other, I can say.

87
00:04:41,540 --> 00:04:42,960
There's a good culture here.

88
00:04:43,080 --> 00:04:44,620
So, I am lucky at that point.

89
00:04:44,900 --> 00:04:50,020
So, when I came to this organization, first, I also adopted this.

90
00:04:50,220 --> 00:04:54,280
In my previous organizations, I am always very transparent to my team.

91
00:04:54,440 --> 00:04:55,960
I, we always talk everything.

92
00:04:55,960 --> 00:04:59,300
And not only for the business, but also for their personal life.

93
00:04:59,420 --> 00:05:02,080
I don't separate the personal life and the business life.

94
00:05:02,300 --> 00:05:05,760
So, in order to give trust, you have to be transparent.

95
00:05:06,000 --> 00:05:07,280
I think it's so important.

96
00:05:07,460 --> 00:05:09,860
And also, you have to do what you say.

97
00:05:09,980 --> 00:05:13,940
If you say something, but you don't do it, it will crush trust.

98
00:05:14,080 --> 00:05:16,460
I can say, we always do what we say.

99
00:05:16,640 --> 00:05:22,120
So, after you work with people and they observe this, it is the rest of the thing.

100
00:05:22,220 --> 00:05:23,940
This is the result, I can say.

101
00:05:23,940 --> 00:05:27,360
So, I am here in this organization almost in five years.

102
00:05:27,480 --> 00:05:28,780
So, people know me.

103
00:05:29,120 --> 00:05:31,760
It is not the first time I, something I promised.

104
00:05:31,960 --> 00:05:33,300
It is my part.

105
00:05:33,500 --> 00:05:37,580
But the most important part is, as an organization, people trust each other.

106
00:05:37,820 --> 00:05:40,020
Commonly, we don't have any issue there.

107
00:05:40,120 --> 00:05:41,900
So, people are used to it.

108
00:05:42,100 --> 00:05:44,320
Also, our top management behaves like that.

109
00:05:44,400 --> 00:05:49,160
So, it was a good point, but it was not so difficult for us.

110
00:05:49,240 --> 00:05:53,420
The idea of transparency comes up a lot in this kind of realm.

111
00:05:53,520 --> 00:06:00,160
And I think the part that you added that I think was all effective, common sense things sound ridiculously simple once you figure out what they are.

112
00:06:00,240 --> 00:06:02,060
It's figuring out what they are and actually doing them.

113
00:06:02,140 --> 00:06:03,200
That is the problem, I find.

114
00:06:03,580 --> 00:06:13,000
But as you were saying, to put it another way, being reliable in doing what you know, doing what you say you're going to do seems valuable to maintaining that trust.

115
00:06:13,000 --> 00:06:19,620
And it reminds me of, there's a lot of people who, there's a lot of theorizing about habits and creating new habits and maintaining them nowadays.

116
00:06:19,840 --> 00:06:25,280
There's one little thing in habit folklore, which is, it's okay to not do a habit for one day.

117
00:06:25,500 --> 00:06:28,200
But once you skip two days, it's not going to be good.

118
00:06:28,320 --> 00:06:35,080
And in thinking about people I've trusted in organizations, like, it's not so much that they're perfect all the time.

119
00:06:35,220 --> 00:06:38,640
They might skip a day, so to speak, but they never skip two days.

120
00:06:38,780 --> 00:06:40,880
There's a certain consistency and reliability.

121
00:06:41,240 --> 00:06:48,500
It's hard to do anything perfectly all the time, but it really is, it's extremely important to maintain that trust and be mindful of it.

122
00:06:48,500 --> 00:06:58,940
Instead of just, I think the problem a lot of people fall into is they rely on policy and governance instead of, like you're saying, just like person-to-person interactions to make things happen.

123
00:06:59,200 --> 00:07:02,520
I sort of skipped us just right into the center of things.

124
00:07:02,820 --> 00:07:10,320
I should have started, like, you know, with these product teams, like, what are the actual products and services that you and the infrastructure area are supporting,

125
00:07:10,320 --> 00:07:11,800
but also the product teams?

126
00:07:11,800 --> 00:07:14,640
There is two sides of these products, I can say, as a bank.

127
00:07:14,860 --> 00:07:17,440
One of them is our digital channels.

128
00:07:17,620 --> 00:07:20,000
I mean, we have different digital channels.

129
00:07:20,340 --> 00:07:21,880
For example, we have a mobile app.

130
00:07:22,080 --> 00:07:23,040
We have a wallet app.

131
00:07:23,240 --> 00:07:26,040
We have our ATM channels, call center channels, etc.

132
00:07:26,340 --> 00:07:30,540
These are all standalone products which maintain by different teams.

133
00:07:30,840 --> 00:07:32,060
This is the one thing.

134
00:07:32,060 --> 00:07:40,860
But the other thing, and I think the most important part for the banking, as a bank, now, for example, we have different teams under domains.

135
00:07:41,280 --> 00:07:43,060
But what I mean by domain?

136
00:07:43,280 --> 00:07:45,440
For example, credits is a domain.

137
00:07:45,680 --> 00:07:48,220
Credit cards is another domain, etc., etc.

138
00:07:48,580 --> 00:07:50,160
Campaign management is a domain.

139
00:07:50,160 --> 00:07:51,500
Document management is a domain.

140
00:07:51,640 --> 00:07:55,200
So under these domains, we have different product teams.

141
00:07:55,480 --> 00:07:56,640
What do I mean by product?

142
00:07:56,740 --> 00:08:08,380
For example, if there is a domain which is responsible for document management and also the workflow management, and under this, there is a document product, document product team, and workflow product team.

143
00:08:08,500 --> 00:08:11,500
Even the granularity of these products may be more.

144
00:08:11,500 --> 00:08:14,580
Last year, we had, how can I say, blueprint study.

145
00:08:14,760 --> 00:08:17,300
It took almost four or five months.

146
00:08:17,700 --> 00:08:20,820
So now, we have a blueprint of the core banking.

147
00:08:21,180 --> 00:08:25,600
We have almost more than 300 products under these domain teams.

148
00:08:25,920 --> 00:08:30,620
And each of these domain teams are responsible for more than one product, of course.

149
00:08:30,860 --> 00:08:35,780
But each of these teams are responsible to make this product great.

150
00:08:36,120 --> 00:08:36,980
This is our aim.

151
00:08:36,980 --> 00:08:39,840
Under YKB, there are small startups.

152
00:08:40,200 --> 00:08:42,600
If you have a startup, how would you behave?

153
00:08:42,760 --> 00:08:44,320
You will try to make it perfect.

154
00:08:44,680 --> 00:08:50,540
And now, each of these teams are responsible, are trying to make their products better and better.

155
00:08:50,820 --> 00:08:52,280
Of course, we have a legacy.

156
00:08:52,780 --> 00:08:57,460
We are a big bank, and we have a legacy code base and systems, etc.

157
00:08:57,760 --> 00:09:00,580
But we also start the transformation journey.

158
00:09:00,840 --> 00:09:06,260
There is a very good, these product teams are very lucky, because each of them may start from scratch.

159
00:09:06,260 --> 00:09:11,400
And design their products with architectural studies, basically like that.

160
00:09:11,780 --> 00:09:19,820
So you started off figuring out, let's see, the actual architecture of the business, so to speak, right?

161
00:09:19,880 --> 00:09:21,300
This is the business as is.

162
00:09:21,480 --> 00:09:22,880
And what all of the...

163
00:09:22,880 --> 00:09:29,720
I always struggle with words, with phrases for this stuff that don't sound, I don't know, like jargon and a bunch of business talk.

164
00:09:29,840 --> 00:09:34,320
But you figured out the business-facing thing or the customer-facing thing.

165
00:09:34,320 --> 00:09:38,740
And then you took the step of like, all right, that's how we should organize IT, right?

166
00:09:38,840 --> 00:09:40,840
To very directly deliver that.

167
00:09:41,060 --> 00:09:46,780
And hence, I think you walked through a good example of what it means to think in a product versus a project way.

168
00:09:47,000 --> 00:09:54,380
How would you contrast to, before you did the blueprinting and shifted over, like how were you operating in like more of a classic project way?

169
00:09:54,460 --> 00:09:59,100
Or like, how were things arranged and how did those apps get worked on and the infrastructure managed and everything?

170
00:09:59,600 --> 00:10:00,240
Yeah, exactly.

171
00:10:00,500 --> 00:10:02,960
As you said, based on the projects, mainly.

172
00:10:03,240 --> 00:10:05,820
Of course, there were some domains, of course.

173
00:10:06,000 --> 00:10:09,580
But each of these domains, the roles and the responsibilities are separated.

174
00:10:09,800 --> 00:10:12,100
Especially based on the functions they do.

175
00:10:12,240 --> 00:10:16,060
You are a business analyst domain, so you just write the business analyst.

176
00:10:16,320 --> 00:10:19,140
You are a software development domain, you just make the software.

177
00:10:19,140 --> 00:10:22,560
The product was not the main issue there.

178
00:10:22,680 --> 00:10:25,960
Each of these domains were doing projects internally.

179
00:10:26,380 --> 00:10:29,020
And of course, there are some issues, as you can guess.

180
00:10:29,280 --> 00:10:33,360
But at that point, we were also working mostly with Waterfall.

181
00:10:33,480 --> 00:10:40,060
During this time, during these organization changes, of course, we started switching to agile methodologies, etc.

182
00:10:40,360 --> 00:10:42,380
It is not a new methodology.

183
00:10:42,680 --> 00:10:44,920
For example, Amazon, Netflix, etc.

184
00:10:45,100 --> 00:10:48,620
They are working like that for Spotify for a long time.

185
00:10:48,620 --> 00:10:51,240
It is very similar for us for the banking part.

186
00:10:51,380 --> 00:10:56,700
Also, in these product teams, we are aiming to have the business side as well into these teams.

187
00:10:57,180 --> 00:10:58,760
What I mean, when we do that.

188
00:10:58,960 --> 00:11:01,960
All of the parties of this product team will be completed.

189
00:11:01,960 --> 00:11:04,260
It is another part of the story.

190
00:11:04,440 --> 00:11:07,280
But it is not so easy for the big banks, as you can guess.

191
00:11:07,580 --> 00:11:09,000
Very legacy institutions.

192
00:11:09,100 --> 00:11:09,360
You'll see.

193
00:11:09,480 --> 00:11:11,900
But as an IT, we are ready for this, I can say.

194
00:11:12,160 --> 00:11:15,400
Another issue is that the main issue is not the technology.

195
00:11:15,520 --> 00:11:16,760
Technology is important, of course.

196
00:11:16,820 --> 00:11:20,220
We are adopting the best technologies and the latest ones.

197
00:11:20,440 --> 00:11:22,280
But the main issue is the business.

198
00:11:22,480 --> 00:11:29,020
For this, we also set up another team under architecture team, which is a business architecture team.

199
00:11:29,020 --> 00:11:30,580
We also set up this team.

200
00:11:30,580 --> 00:11:38,640
They are now closely working with our business teams and also analyst teams together and making the designs, the product designs together.

201
00:11:38,980 --> 00:11:43,820
It is also important for us because otherwise it is just a technical conversion.

202
00:11:43,980 --> 00:11:46,280
But now it is a business conversion at the same time.

203
00:11:46,280 --> 00:11:47,240
Yeah, that's interesting.

204
00:11:47,380 --> 00:11:50,300
That would be interesting, that topic to talk more on.

205
00:11:50,540 --> 00:11:57,040
Because I think what I've noticed in recent years is there's some bottlenecking in that area you were just talking about.

206
00:11:57,200 --> 00:12:02,140
And essentially, we've made our IT organization agile and product centric.

207
00:12:02,500 --> 00:12:05,560
And now we need the business side to talk with us more.

208
00:12:05,680 --> 00:12:10,040
And it sounds like you all are getting past and in some cases have gotten past.

209
00:12:10,180 --> 00:12:18,320
But what was the initial sort of work to go to the business side and say, we're ready to do stuff for you?

210
00:12:18,500 --> 00:12:22,260
To be honest, I think we have still too many gaps there.

211
00:12:22,440 --> 00:12:24,540
There is still a road to go.

212
00:12:24,540 --> 00:12:31,240
But we started, for example, it is also interesting story because generally requests come from the business to IT.

213
00:12:31,620 --> 00:12:36,700
But today we have also the request comes from IT to business side as well.

214
00:12:36,920 --> 00:12:42,300
For example, there is a project that we did with our new architecture and cloud environment.

215
00:12:42,520 --> 00:12:48,760
It's a very important project for us, which is we renewed our personal loans from scratch.

216
00:12:48,760 --> 00:12:58,520
But at that point, especially our IT team was very, how can I say, active to make this project and make it make a better loan system.

217
00:12:58,840 --> 00:13:00,860
They were very patient about it.

218
00:13:01,100 --> 00:13:06,080
And they also worked very closely and pursued most of the things to the business.

219
00:13:06,300 --> 00:13:09,720
As you said, at some point, it is surprising.

220
00:13:09,840 --> 00:13:10,680
It seems surprising.

221
00:13:10,900 --> 00:13:15,780
But with this new mindset, I think a business side will also get used to it.

222
00:13:15,960 --> 00:13:19,140
And I think there is still some things to do there.

223
00:13:19,420 --> 00:13:20,480
But at least we started.

224
00:13:20,800 --> 00:13:24,760
And for a bank, a personal loan is a very critical project.

225
00:13:25,060 --> 00:13:29,580
So if any problem there, we have really a problem, we can say.

226
00:13:29,780 --> 00:13:31,980
So it was also good for us.

227
00:13:32,160 --> 00:13:37,340
The operating model, we proved the operation model and also the technologies.

228
00:13:37,740 --> 00:13:39,000
We will see how it will go.

229
00:13:39,080 --> 00:13:40,220
But it is not so easy.

230
00:13:40,460 --> 00:13:41,680
But so far, so good.

231
00:13:41,680 --> 00:13:45,560
Yeah, arguably, loans are the core of banking, right?

232
00:13:45,600 --> 00:13:50,760
If you're not doing loans, you can't really generate most of the capital that you need to do everything else.

233
00:13:50,760 --> 00:13:51,920
Like it's core to it.

234
00:13:52,080 --> 00:14:01,440
So another thing, it's interesting going over this because you all are either in the middle of or you've gotten to a lot of the change that people are always striving for.

235
00:14:01,440 --> 00:14:18,280
And another thing, as you were going over examples that you're reminding me of is there's some people at large organizations I've been talking about recently, and they struggle with taking on more of a product mindset or figuring out the infrastructure that they should provide for more of a DevOps-y way of doing things.

236
00:14:18,280 --> 00:14:28,100
To put it in more boring language, having developers be able to use self-service to set up their infrastructure instead of having to file tickets and not to minimize all the DevOps stuff to that.

237
00:14:28,260 --> 00:14:41,600
But it's been occurring to me recently that one of the struggles that these people I'm talking with have is if you were to say who owns the end-to-end process of everything, I don't know if they would know who that was.

238
00:14:41,640 --> 00:14:51,060
Each little unit, like the storage people, the networking, the database people, the app people, they just do their own job and hope that somehow magically it all fits together.

239
00:14:51,060 --> 00:14:55,140
You have a lot of things underneath you, like a bunch of functions.

240
00:14:55,640 --> 00:15:03,920
And did you have any struggles or any, how did you get people to say, we want to have someone owning this end-to-end thing, right?

241
00:15:03,960 --> 00:15:14,340
Because that seems very non-traditional to have someone say, we need to pay attention to the whole process, not just these little parts, because otherwise we won't be able to do very much.

242
00:15:14,340 --> 00:15:27,340
In fact, our organization, in fact, this role is under my responsibility, checking each of these small units are working together, is the process okay, et cetera, et cetera.

243
00:15:27,700 --> 00:15:40,460
Yes, but the more important is there are too many people who came to me and said that, okay, I am doing storage, I am doing middleware, I am doing application, doesn't matter.

244
00:15:40,460 --> 00:15:48,780
But I want to learn the other side as well, not maybe not very deeply, but at least I want to see the whole process.

245
00:15:49,140 --> 00:15:51,100
So I want to see the big picture.

246
00:15:51,380 --> 00:15:55,560
And of course, at that point, I will be some part of it, I will be doing some part of it.

247
00:15:55,660 --> 00:16:02,220
But when I see this big picture, I feel I will be more excited and also I will also feel more trusted.

248
00:16:02,220 --> 00:16:12,860
So people are also, what I see, my experience is people want to change themselves as well, want to gain new abilities, new technologies maybe.

249
00:16:13,040 --> 00:16:16,540
They also see it as a chance, that is what I see.

250
00:16:16,880 --> 00:16:25,820
So when I collect this information, we started internal sessions, especially for this next generation project, next generation banking, we call it.

251
00:16:25,820 --> 00:16:29,700
We have a group of people from different teams.

252
00:16:30,080 --> 00:16:35,140
In this team, we are weekly, we are doing these discussions.

253
00:16:35,560 --> 00:16:41,720
Everyone is coming to this session and sharing their experiences, what they have done this week.

254
00:16:41,820 --> 00:16:44,600
And maybe another thing, it doesn't matter.

255
00:16:44,780 --> 00:16:47,880
Maybe they can share new technologies, it doesn't matter.

256
00:16:47,980 --> 00:16:53,560
We are trying to make transparent and, how can I say, removing these borders between teams.

257
00:16:53,760 --> 00:17:03,220
It is, until now, I get very good feedback from my team because they say that now there are some black boxes in the environment, but now it is all clear.

258
00:17:03,220 --> 00:17:04,380
There are two sides of it.

259
00:17:04,500 --> 00:17:11,620
I mean, the team wants it and also I agree with them and now we are running it like that.

260
00:17:11,880 --> 00:17:12,500
Yeah, it's interesting.

261
00:17:12,740 --> 00:17:25,440
One connection that occurs to me is you did what you said in the sense that sort of what you're saying at one point is we care about things from a product standpoint, which means we care about an end-to-end view of things.

262
00:17:25,440 --> 00:17:27,100
We don't want to have silos set up.

263
00:17:27,500 --> 00:17:37,100
And one of the ways of demonstrating that maybe someone like yourself or someone in a leadership position can do is to say, and I've done the work to figure out what the end-to-end process is.

264
00:17:37,100 --> 00:17:43,460
Like, I'm not going to go to all of the different silos and tell them to figure it out, right, to map out what this is.

265
00:17:43,660 --> 00:17:49,800
Instead, I'm going to try to figure out what this process is and then show it to them and get their input about it and their participation.

266
00:17:49,800 --> 00:17:59,940
So it's almost like, it's interesting, like, that a lot of the problems I talk with people about is we can't work together because we're still in silos.

267
00:18:00,460 --> 00:18:05,100
And it almost points to like, then you need management to do that first, right?

268
00:18:05,140 --> 00:18:14,100
Like, you need management to maybe do some of that work that they're expecting you to do instead, and then show you what that complete process is instead of relying on other people to do it.

269
00:18:14,340 --> 00:18:15,300
Yeah, I'm totally agree.

270
00:18:15,380 --> 00:18:19,200
Management, okay, it is important, but the thing is we are all part of a team.

271
00:18:19,340 --> 00:18:21,560
My role is the management and some other stuff.

272
00:18:21,880 --> 00:18:23,660
Some of my teams are more technical.

273
00:18:23,900 --> 00:18:24,620
It doesn't matter.

274
00:18:24,620 --> 00:18:29,860
But if we are going to do something, we will be doing it on hands.

275
00:18:30,120 --> 00:18:32,800
I think I am very serious about it.

276
00:18:32,880 --> 00:18:35,580
So I am trying to still be staying hands-on.

277
00:18:35,760 --> 00:18:37,200
So we are a team.

278
00:18:37,340 --> 00:18:38,300
It doesn't matter.

279
00:18:38,660 --> 00:18:42,660
But yes, it is also important when you are at the management, you decide.

280
00:18:42,900 --> 00:18:44,820
But we are all part of a team.

281
00:18:44,940 --> 00:18:46,160
It is so important.

282
00:18:46,160 --> 00:18:51,000
And having this experience together hands-on is very important.

283
00:18:51,500 --> 00:18:53,120
It also affects the people, I think.

284
00:18:53,480 --> 00:18:59,260
When they see the management is also doing it with them, it also affects.

285
00:18:59,420 --> 00:19:02,040
I think it encourages them as well.

286
00:19:02,320 --> 00:19:06,840
Yeah, it helps win that trust over ongoing, that you are all in it together.

287
00:19:06,840 --> 00:19:13,260
And you share the success and you share overall responsibility, good and bad, that things are happening as things are going.

288
00:19:13,480 --> 00:19:23,100
So another topic that comes up all the time in banking, but as I found in every organization, is worrying about compliance and security and following those sort of things.

289
00:19:23,100 --> 00:19:29,560
And in this discussion of doing things in a more product-driven, agile way, that's always one of the first questions.

290
00:19:29,620 --> 00:19:37,560
If we have, like, if we're pushing down a lot of decision-making and we're making it faster for developers to do things, like, that sounds bonkers.

291
00:19:37,820 --> 00:19:41,560
That sounds like it's going to be problems for enforcing security and compliance.

292
00:19:41,680 --> 00:19:43,760
Like, what have you all done in that area?

293
00:19:43,900 --> 00:19:47,920
Because it's not, it's, there's not an option to not be secure and compliant.

294
00:19:48,140 --> 00:19:51,760
You're right, regulations and security is the core of the banking.

295
00:19:52,100 --> 00:19:54,320
You cannot have any mistake there.

296
00:19:54,320 --> 00:20:04,000
What we have done in this new journey, I can say, we have legacy systems and all of these regulations and security issues are mapped in this legacy system.

297
00:20:04,300 --> 00:20:05,280
So it's okay.

298
00:20:05,660 --> 00:20:15,860
But when you set up a system from scratch with our new architecture, we change our infrastructure part, software part, middleware, cloud, and everything.

299
00:20:15,860 --> 00:20:23,660
So what, you have to figure out all of these issues from scratch with the new technologies, with the new mindsets, maybe.

300
00:20:23,880 --> 00:20:30,400
If it is necessary, you go to regulatory, and you also discuss with them.

301
00:20:30,520 --> 00:20:35,040
I mean, it takes time, it takes effort, but at the end, it makes sense.

302
00:20:35,280 --> 00:20:42,480
In this journey, what we have done, due to regulations, we cannot use public cloud providers outside Turkey.

303
00:20:42,480 --> 00:20:52,260
So we set up our private cloud in our data center, but private cloud technology, all of the technologies are different, containerization, et cetera, et cetera.

304
00:20:52,540 --> 00:20:56,060
So with our security team, we set up a project group.

305
00:20:56,060 --> 00:21:01,520
And with this project group, we studied all the new technologies around security.

306
00:21:01,520 --> 00:21:10,640
But we are very careful at that point, because everything must be secure, but also it doesn't have to affect the general working environment.

307
00:21:10,920 --> 00:21:18,440
We are lucky that, I can say, we have a very good, I mean, they are all open to new technologies, new ideas, our security team.

308
00:21:18,580 --> 00:21:22,200
So we work very closely with the good for us, and also regulations.

309
00:21:22,200 --> 00:21:27,640
We are also talking with our regulatory teams, and we are also checking these new technologies.

310
00:21:27,900 --> 00:21:39,140
But I can say it takes time, because as a bank, you have to, as I said, rethink all of these technologies, processes, not only the technologies, but also the processes from scratch.

311
00:21:39,140 --> 00:21:40,620
It is our journey until now.

312
00:21:40,820 --> 00:21:44,240
Now we are all compliant and secure, I can say.

313
00:21:44,400 --> 00:21:47,840
Even more secure, maybe, with the new technologies and elements.

314
00:21:48,100 --> 00:21:48,960
So far, so good.

315
00:21:49,160 --> 00:21:56,440
But also we are now, today, we are also talking with regulatory government, how can I say, for the public cloud issue.

316
00:21:56,840 --> 00:21:56,880
Right.

317
00:21:56,960 --> 00:21:59,060
Now, currently, we are working on this area as well.

318
00:21:59,140 --> 00:22:03,400
It takes time, but we are almost aligned with the rest of the world, I can say.

319
00:22:03,400 --> 00:22:04,940
What is the kind of timeline for that?

320
00:22:05,020 --> 00:22:13,020
How long did it take from thinking, we need to go talk with the security people and the auditors and regulator people, to like, all right, we got it.

321
00:22:13,220 --> 00:22:16,740
It is not so easy to say how long did it take.

322
00:22:16,880 --> 00:22:21,100
We are working on this project since 2016, I can say.

323
00:22:21,360 --> 00:22:24,700
But we see it as a journey, what I say.

324
00:22:24,760 --> 00:22:27,500
We started with some processes and technologies.

325
00:22:28,100 --> 00:22:33,540
But during this journey, now in the world, especially the software world, is changing so fast.

326
00:22:33,720 --> 00:22:35,440
New technologies, new opportunities.

327
00:22:35,740 --> 00:22:36,980
It is an endless journey.

328
00:22:37,280 --> 00:22:38,220
We see it like that.

329
00:22:38,400 --> 00:22:39,360
It is not completed.

330
00:22:39,680 --> 00:22:40,580
It will continue.

331
00:22:40,740 --> 00:22:42,460
And there is no deadline for this.

332
00:22:42,460 --> 00:22:49,480
The most important principle in our new world, I can say, architecture and technology, it will be adaptable.

333
00:22:49,780 --> 00:22:51,660
It is our first main strategy.

334
00:22:52,020 --> 00:23:01,320
All of our software components and infrastructure components, virtualization components, we always keep abstraction layers.

335
00:23:01,720 --> 00:23:07,320
So when there is a new technology, I don't know, or a better option, we can change it.

336
00:23:07,380 --> 00:23:09,240
So it is so important for us.

337
00:23:09,240 --> 00:23:10,980
So we started this journey.

338
00:23:11,240 --> 00:23:14,820
We are very good point there, but it will also continue, I can say.

339
00:23:15,100 --> 00:23:16,040
But how long did it take?

340
00:23:16,240 --> 00:23:18,440
Until now, it took almost four years.

341
00:23:18,540 --> 00:23:19,600
Yeah, that sounds about right.

342
00:23:19,660 --> 00:23:29,320
When I talk about this with people, I somewhat flippantly tell them, when they ask about security and compliance and what do we do about that, my first flippant answer is basically, yeah, that's a problem.

343
00:23:29,480 --> 00:23:30,640
It takes a lot of work.

344
00:23:30,640 --> 00:23:42,480
And I think your experience is what everyone else who's figured it out says is like, yeah, you need to go talk with the security people and the auditors and just start talking with them.

345
00:23:42,940 --> 00:23:47,100
And you even touched upon, there's that bidirectional thing, right?

346
00:23:47,100 --> 00:23:52,240
In the same way that, like you were saying earlier, like traditionally the business asks IT for things.

347
00:23:52,240 --> 00:23:56,440
And now every now and then you're getting IT asking the business for things, suggesting things.

348
00:23:56,720 --> 00:24:11,720
And I think what in more mature organizations that are getting closer to a product way of doing things, it's also a bidirectional thing, as you're alluding to, that the technical staff starts to say, this is, I understand the requirements for security and compliance stuff.

349
00:24:11,720 --> 00:24:13,960
And here's something new we could try out, right?

350
00:24:14,040 --> 00:24:22,180
There's actually some new functionality that might make what you're doing better rather than just waiting to be told what they can't do by, by people.

351
00:24:22,320 --> 00:24:24,040
But yeah, it's a major component.

352
00:24:24,040 --> 00:24:31,260
I think it's, I think it's part of what makes so-called enterprise stuff different than just like regular old tech companies.

353
00:24:31,460 --> 00:24:32,960
I like the way you put it a while back.

354
00:24:33,040 --> 00:24:41,700
You're like, technology is of course important because a lot of people like to say it's to misappropriate the old phrase, culture each technology for breakfast, to say it some other way.

355
00:24:41,720 --> 00:24:43,060
What is the technology?

356
00:24:43,500 --> 00:24:45,040
Like, how do you evaluate it?

357
00:24:45,140 --> 00:24:46,120
What do you look for?

358
00:24:46,280 --> 00:24:48,420
What are y'all using that helps out with all of this?

359
00:24:48,620 --> 00:25:00,380
It is a very important part for us because when you decided to change almost everything in banking, you build up from secret, you have to be very careful about the technologies that you choose.

360
00:25:00,560 --> 00:25:03,720
Especially for our new framework, we choose all new technologies.

361
00:25:04,640 --> 00:25:07,840
I can say we use open source and we are all open.

362
00:25:07,960 --> 00:25:09,560
We also contribute to open source.

363
00:25:09,720 --> 00:25:11,160
We are a fan of open source today.

364
00:25:11,160 --> 00:25:16,280
But also the underlying, underlayer part, the infrastructure part is much more important.

365
00:25:16,540 --> 00:25:23,480
Because today we have more than 8 million digital customers, very, very high number of transaction numbers.

366
00:25:23,840 --> 00:25:30,000
So when you set up something from scratch, you have to be sure that it will be rock solid.

367
00:25:30,340 --> 00:25:32,420
So otherwise you cannot take that risk.

368
00:25:32,680 --> 00:25:36,100
And also you will do some investments at that point.

369
00:25:36,200 --> 00:25:37,440
And it is not so easy.

370
00:25:37,440 --> 00:25:43,360
For the special cloud part, we had almost one year, how can I say, POCs with different vendors.

371
00:25:43,360 --> 00:25:51,800
And at that point, we chose Pivotal at that point, but today Tanzu.

372
00:25:52,000 --> 00:25:53,620
And now we are using Tanzu.

373
00:25:53,740 --> 00:25:57,560
Especially why we chose Tanzu, there are so many reasons.

374
00:25:57,800 --> 00:26:00,100
But two main reasons I can explain.

375
00:26:00,200 --> 00:26:02,560
One is it was a very mature product.

376
00:26:02,820 --> 00:26:06,180
And also the other part is it is easy to use.

377
00:26:06,180 --> 00:26:12,140
For the developers, when you say DevOps, you say that you will give new responsibilities to developers.

378
00:26:12,140 --> 00:26:14,300
So it must be user-friendly.

379
00:26:14,580 --> 00:26:18,380
So we see that developers can use Tanzu products very easily.

380
00:26:18,600 --> 00:26:20,720
It was so important for the developers part.

381
00:26:20,940 --> 00:26:29,280
But also for the operations part, for the infrastructure teams, most of the things can be automated easily with pipelines technologies.

382
00:26:29,280 --> 00:26:33,320
We saw that we have that kind of features in Tanzu.

383
00:26:33,500 --> 00:26:35,480
In the cloud part, we are using Tanzu.

384
00:26:35,660 --> 00:26:39,520
And also we are using different technologies in different layers.

385
00:26:39,720 --> 00:26:44,420
For the logging part, for the monitoring part, and also the networking part.

386
00:26:44,500 --> 00:26:45,840
For example, we are using NSX.

387
00:26:46,240 --> 00:26:46,760
Why?

388
00:26:46,920 --> 00:26:51,780
Because we can make, for example, micro-segmentation with NSX.

389
00:26:51,900 --> 00:26:55,000
We can put walls between products.

390
00:26:55,260 --> 00:26:58,840
Each team has their own area in the Tanzu.

391
00:26:58,840 --> 00:27:01,100
Their own products in this area.

392
00:27:01,260 --> 00:27:05,620
Especially in banking, authorization and authentication is so important.

393
00:27:06,000 --> 00:27:08,360
So we are at this tech now for the technology.

394
00:27:08,460 --> 00:27:11,100
And just as one minor thing, because people ask me this a lot.

395
00:27:11,220 --> 00:27:15,980
You said you also, in the cluster of things you worry about, you work on.

396
00:27:16,160 --> 00:27:17,740
You have databases as well.

397
00:27:17,860 --> 00:27:20,200
So what's been the, what have you done in that area?

398
00:27:20,280 --> 00:27:22,620
What do you do with databases?

399
00:27:23,020 --> 00:27:25,380
And I don't know, what's the data story that y'all have?

400
00:27:25,380 --> 00:27:27,620
Database is a huge part of the story.

401
00:27:27,740 --> 00:27:29,220
We are basically Oracle customers.

402
00:27:29,580 --> 00:27:30,600
Mainly we are using Oracle.

403
00:27:30,980 --> 00:27:34,780
But we have also a huge farm for the SQL server as well.

404
00:27:34,920 --> 00:27:36,380
This is the legacy part.

405
00:27:36,800 --> 00:27:40,460
Also for the big data part, we are adopting new technologies.

406
00:27:41,000 --> 00:27:43,080
We have Hadoop environment, for example.

407
00:27:43,400 --> 00:27:46,420
And also we are adopting new technologies such as MongoDB.

408
00:27:46,820 --> 00:27:50,540
We are also using these technologies as well in the database part.

409
00:27:50,780 --> 00:27:57,520
And it is evolving because what we see, especially different big players are attacking this area.

410
00:27:57,760 --> 00:28:00,020
Especially Amazon and Microsoft.

411
00:28:00,300 --> 00:28:03,220
They are providing today context-aware databases.

412
00:28:03,220 --> 00:28:06,920
We will see what will be our main strategy for future.

413
00:28:06,920 --> 00:28:10,440
But we are watching all of these changes very closely.

414
00:28:10,540 --> 00:28:15,520
Especially our migration transformation project is also very important for this.

415
00:28:15,680 --> 00:28:22,000
Because with our new transformation project, each of these products, as I said, will be running their own databases.

416
00:28:22,460 --> 00:28:25,700
So there will be no common database, maybe.

417
00:28:25,920 --> 00:28:31,100
So maybe we will be using context-aware databases in near future.

418
00:28:31,220 --> 00:28:31,760
I don't know.

419
00:28:32,000 --> 00:28:37,260
But the thing is, our software will be ready for this in the near future.

420
00:28:37,340 --> 00:28:39,380
Because there are too many homeworks to do.

421
00:28:39,740 --> 00:28:42,540
The first one is, as I said, creating this product.

422
00:28:42,540 --> 00:28:46,520
The main principle at that point is the domain-driven design, I can say.

423
00:28:46,800 --> 00:28:48,760
We are applying these principles today.

424
00:28:49,100 --> 00:28:53,120
And with this domain-driven design, we are making products.

425
00:28:53,360 --> 00:28:56,080
And each of these products will have their own databases.

426
00:28:56,260 --> 00:28:57,440
Today, it is like that.

427
00:28:57,640 --> 00:29:00,600
So we don't need to make a big bank.

428
00:29:00,740 --> 00:29:05,260
Today, if, for example, let's say, change our database, it's not so easy.

429
00:29:05,500 --> 00:29:06,720
Because it will be a big bank.

430
00:29:06,880 --> 00:29:09,100
Probably no one will take this risk.

431
00:29:09,320 --> 00:29:12,080
But in the near future, we will be in another position.

432
00:29:12,080 --> 00:29:12,520
Yeah.

433
00:29:12,660 --> 00:29:18,220
And also by doing your domain-driven design and figuring out all the different products that you have.

434
00:29:18,300 --> 00:29:20,000
Tell me if this seems true.

435
00:29:20,220 --> 00:29:31,320
But it seems like you're making it a lot easier to connect directly, like, the business value, like, the business that you have to the decisions you're making in your architecture.

436
00:29:31,780 --> 00:29:45,640
And so when it comes to something as difficult as database choices, you can say, we're going to, people might have different databases per product instead of one centralized database because it's invaluable for the outcome that we want, which we can now understand, right?

437
00:29:45,640 --> 00:29:58,860
Like, you can start to evaluate the risks of things versus the benefits of them and the difficulty of changing technology based on, is it going to be useful for the business versus just, like, other criteria, which is a nice side effect of all that analysis.

438
00:29:59,240 --> 00:30:01,040
At the end of the day, we are a bank.

439
00:30:01,260 --> 00:30:04,940
Each of these technology changes must affect your business.

440
00:30:05,240 --> 00:30:08,740
It must be, there must be some value added on your current business.

441
00:30:08,740 --> 00:30:19,840
For example, before, I don't exactly remember the number, but I think it was around 30 to 45 seconds when you give your credit as a bank to our customers.

442
00:30:20,220 --> 00:30:24,460
But with our new architecture, it is now almost eight seconds.

443
00:30:24,740 --> 00:30:30,560
And we are trying to make it six seconds because mobility, a customer cannot wait so much.

444
00:30:30,700 --> 00:30:34,960
We are making these changes in our technology and it also affects our business.

445
00:30:34,960 --> 00:30:40,000
It is so important and it will also get the support from the business as well.

446
00:30:40,180 --> 00:30:45,220
Yeah, I guess, as you say, that's the other thing that's important is it makes budget discussions a little easier.

447
00:30:45,600 --> 00:30:48,880
They're probably still difficult, but they could always be a little easier.

448
00:30:49,280 --> 00:30:50,340
So, well, this has been great.

449
00:30:50,460 --> 00:30:54,220
I appreciate you letting me ask questions here and there and fill in details.

450
00:30:54,440 --> 00:31:02,240
If people wanted to, like, check out more or follow up on things, do you have anything you'd point them to that you're interested in having people look at?

451
00:31:02,240 --> 00:31:08,060
Do you have any accounts like, hey, if you want to follow what I'm doing or do you have any job postings you want to direct people to?

452
00:31:08,300 --> 00:31:08,540
Sure, sure.

453
00:31:08,700 --> 00:31:11,960
Thailand, Gunayet, Twitter, you can find me and also LinkedIn.

454
00:31:12,160 --> 00:31:13,140
Basically, I am using Twitter.

455
00:31:13,480 --> 00:31:14,900
I am doing postings there.

456
00:31:15,140 --> 00:31:15,620
Very good.

457
00:31:15,700 --> 00:31:15,920
All right.

458
00:31:15,960 --> 00:31:16,520
Well, thanks again.

459
00:31:16,720 --> 00:31:17,760
I really appreciate it.

460
00:31:17,880 --> 00:31:18,360
Yeah, me too.

461
00:31:18,440 --> 00:31:19,060
It was my pleasure.

462
00:31:19,200 --> 00:31:19,520
Thank you.

463
00:31:19,600 --> 00:31:21,520
As always, this has been Tanzu Talk.

464
00:31:21,580 --> 00:31:24,820
If you want to get the archives for this show, you can go to TanzuTalk.com.

465
00:31:24,940 --> 00:31:26,720
And with that, we'll see everyone next time.

466
00:31:26,920 --> 00:31:27,280
Bye-bye.

467
00:31:32,240 --> 00:32:02,220
Thank you.