1
00:00:10,360 --> 00:00:14,040
Hello and welcome to our podcast
insight SAP Svahana. 

2
00:00:14,800 --> 00:00:18,360
There is no Customer success 
without Product success and 

3
00:00:18,360 --> 00:00:21,800
Project Success. 
My name is Marcus Ertold and 

4
00:00:21,800 --> 00:00:26,400
today we have a special episode.
This is part of our Cloud ERP 

5
00:00:26,520 --> 00:00:30,630
close Up series. 
This series is designed to share

6
00:00:30,630 --> 00:00:34,750
product highlights and project 
insights based on hands on 

7
00:00:34,750 --> 00:00:38,190
experience. 
And for that I have with me 

8
00:00:38,190 --> 00:00:41,790
today Axel Herman, Product 
Management Lead for Product 

9
00:00:41,790 --> 00:00:46,390
centric Cloud EAP at SAP. 
In this podcast you will get 

10
00:00:46,390 --> 00:00:51,390
insights about who is Axel, how 
its transition into his new role

11
00:00:51,390 --> 00:00:54,950
is going to what rise and grow 
with SAP means from product 

12
00:00:54,950 --> 00:00:58,640
management perspective. 
And of course his strategy for 

13
00:00:58,640 --> 00:01:01,200
the future and welcome Axel and 
it's good having you. 

14
00:01:01,680 --> 00:01:04,640
Marcus, thanks for having me and
giving me the chance to speak to

15
00:01:04,640 --> 00:01:07,120
you today. 
Let's see, what do I know about 

16
00:01:07,120 --> 00:01:09,880
you, Axel, your former leader 
for SAP? 

17
00:01:09,920 --> 00:01:14,440
As for HANA cloud services, me 
at SAP, also a former basketball

18
00:01:14,440 --> 00:01:16,720
player. 
Is it OK if I tell the secret 

19
00:01:16,720 --> 00:01:18,920
Axel here? 
Yes, of course. 

20
00:01:18,920 --> 00:01:21,270
Go ahead. 
If my understanding is correct, 

21
00:01:21,270 --> 00:01:23,870
we played for the same 
basketball club in our youth. 

22
00:01:23,990 --> 00:01:27,030
I think so, yeah, yes, the great
bigots here and off. 

23
00:01:27,350 --> 00:01:29,790
But for Full disclosure, you 
were playing the first team and 

24
00:01:29,790 --> 00:01:32,590
I was in the 15th, so that's it.
I don't remember that, but you 

25
00:01:32,590 --> 00:01:36,430
also rode biking enthusiast. 
You're a Berliner like myself. 

26
00:01:36,670 --> 00:01:39,070
If I would meet you at the bus 
stop somewhere in the world, 

27
00:01:39,070 --> 00:01:40,670
what else would you tell me 
about yourself? 

28
00:01:41,430 --> 00:01:43,670
Good question. 
Let me start with saying I think

29
00:01:43,870 --> 00:01:45,990
it would actually be quite 
likely we would meet at a bus 

30
00:01:45,990 --> 00:01:49,270
stop because I'm a great fan of 
public transport people. 

31
00:01:49,660 --> 00:01:52,380
Always wonder why I say that 
because I think public transport

32
00:01:52,420 --> 00:01:55,900
is a nice and standardized way 
to get from A to B. 

33
00:01:55,940 --> 00:01:59,260
Obviously there is a last mile 
topic, but I'm not so concerned 

34
00:01:59,260 --> 00:02:01,580
about that, that for the last 
mile you have a bus or sometimes

35
00:02:01,580 --> 00:02:04,420
a road bike or a bike. 
So yes, I think that's most 

36
00:02:04,420 --> 00:02:07,060
important. 
I like standardization and um, 

37
00:02:07,060 --> 00:02:10,380
the other day there was a blog 
post by Bash Witzer about 

38
00:02:10,380 --> 00:02:13,940
comparing the Esfana public 
cloud with public transport map 

39
00:02:14,300 --> 00:02:18,160
and seldomly has a blog post. 
Spoken closer to my heart than 

40
00:02:18,160 --> 00:02:19,880
that one is just terrific spot 
on. 

41
00:02:20,160 --> 00:02:23,080
And yeah, so we would speak, 
hopefully would join the bus 

42
00:02:23,080 --> 00:02:25,240
ride with me because that would 
be a nice time that we could 

43
00:02:25,240 --> 00:02:27,680
spend together. 
Brilliant Axel. 

44
00:02:28,080 --> 00:02:31,200
Sure So would like to join. 
If you stay on the topic of 

45
00:02:31,200 --> 00:02:34,560
describing, can you maybe 
describe your new role and how 

46
00:02:34,560 --> 00:02:37,560
did you experience your first 
two months in the new job and 

47
00:02:37,720 --> 00:02:40,960
maybe what was very positive, 
maybe also something challenging

48
00:02:40,960 --> 00:02:42,240
for you? 
First of all, our product 

49
00:02:42,240 --> 00:02:44,520
management is a pretty wide area
and. 

50
00:02:44,930 --> 00:02:47,810
I want to start by saying I had 
the absolute joy and pleasure to

51
00:02:47,810 --> 00:02:51,370
get the chance to work and meet 
so many fantastic new people. 

52
00:02:51,570 --> 00:02:55,210
Always thought I had a big 
network with NSAP and UH, lo and

53
00:02:55,210 --> 00:02:57,650
behold, it's growing by the day.
So this is really great. 

54
00:02:57,650 --> 00:03:00,530
And with this, the first two 
months have passed in no time. 

55
00:03:00,890 --> 00:03:03,690
I was trying to spend as much, 
listen and learn quality time 

56
00:03:03,690 --> 00:03:06,610
with many people. 
Uh, still continuing that and 

57
00:03:06,610 --> 00:03:08,930
this is just a pleasure to work 
with so many nice people and the

58
00:03:08,930 --> 00:03:12,210
people are so knowledgeable. 
It's absolutely fantastic and 

59
00:03:12,210 --> 00:03:16,120
super motivating now. 
The role itself is actually also

60
00:03:16,120 --> 00:03:19,120
quite exciting. 
My team is responsible for all 

61
00:03:19,120 --> 00:03:22,600
product related processes with 
an S1 or cloud, whether it's 

62
00:03:23,040 --> 00:03:26,400
planning, producing, storing, 
transporting, quality 

63
00:03:26,400 --> 00:03:28,560
management, all those things. 
Anything that has to do with a 

64
00:03:28,560 --> 00:03:31,800
product in an ERP. 
Those are the processes and 

65
00:03:31,800 --> 00:03:33,480
areas that my team are 
responsible. 

66
00:03:34,120 --> 00:03:37,320
And um, As for the challenging, 
yes, it is challenging. 

67
00:03:37,320 --> 00:03:39,360
I think time is the most 
challenging thing. 

68
00:03:39,740 --> 00:03:42,220
I'm super eager try to meet as 
many people. 

69
00:03:42,260 --> 00:03:44,660
If I meet people, I also want to
understand what they're doing, 

70
00:03:44,660 --> 00:03:47,740
where their challenges lie 
better, understand what 

71
00:03:47,740 --> 00:03:49,340
motivates people, and that takes
time. 

72
00:03:49,340 --> 00:03:52,380
And time is something that I 
currently don't have the time as

73
00:03:52,380 --> 00:03:54,940
much as I would like to, but 
that's something that will grow 

74
00:03:54,940 --> 00:03:57,260
out over time. 
So nothing that is 

75
00:03:57,260 --> 00:04:00,540
unsurmountable as a challenge. 
Thanks Axel. 

76
00:04:00,620 --> 00:04:04,380
I wished I could give you more 
time but. 

77
00:04:05,650 --> 00:04:07,210
Unfortunately, I'm not in that 
position. 

78
00:04:08,010 --> 00:04:10,090
You already mentioned it or we 
mentioned it. 

79
00:04:10,090 --> 00:04:12,690
You coming from the 
implementation side, which in my

80
00:04:12,690 --> 00:04:15,290
opinion is a big advantage 
because you bring a lot of 

81
00:04:15,290 --> 00:04:17,610
customer feedback with you into 
this new role. 

82
00:04:18,130 --> 00:04:20,570
Yeah, now the question is what 
are you doing with all this 

83
00:04:20,570 --> 00:04:23,130
implementation feedback? 
That's a good question. 

84
00:04:23,250 --> 00:04:24,890
Well, let me answer it pretty 
simple. 

85
00:04:25,170 --> 00:04:27,730
What I've learned in the 
implementation that everything 

86
00:04:27,730 --> 00:04:31,410
we as a solution provider as SAP
as being a solution provider in 

87
00:04:31,410 --> 00:04:35,050
the sauce environment, we have 
to keep the customer. 

88
00:04:35,370 --> 00:04:38,530
In every decision we take, yeah,
have to put them at the center 

89
00:04:38,530 --> 00:04:42,210
of our decisions, which features
to develop, which UI to adopt 

90
00:04:42,210 --> 00:04:45,730
next, even which meeting I 
prioritize or is there a certain

91
00:04:45,730 --> 00:04:47,810
activity I do or maybe also 
don't do. 

92
00:04:48,210 --> 00:04:51,850
If you ask yourself does that 
have a direct impact on customer

93
00:04:51,850 --> 00:04:54,690
satisfaction on being able to 
solve customer issues that they 

94
00:04:54,690 --> 00:04:56,330
have. 
And I mean if we're all aware of

95
00:04:56,330 --> 00:04:59,050
the ever changing environment in
which our customers are 

96
00:04:59,050 --> 00:05:02,890
currently acting, that should be
your guiding measure on all the 

97
00:05:02,890 --> 00:05:06,510
activities you do and. 
What I take from my experience 

98
00:05:06,510 --> 00:05:09,350
is I mentioned earlier that I'm 
grateful to work now with so 

99
00:05:09,350 --> 00:05:13,150
many new people, obviously that 
in the last years I've had the 

100
00:05:13,150 --> 00:05:16,750
chance to meet so many great 
customers that went on the 

101
00:05:16,750 --> 00:05:19,550
journey, that went together with
SAP on the journey into the 

102
00:05:19,550 --> 00:05:20,870
cloud. 
They transformed their 

103
00:05:20,870 --> 00:05:23,790
businesses, they standardized 
their businesses, which is hard 

104
00:05:23,790 --> 00:05:25,990
work and they reaped from the 
benefits now. 

105
00:05:26,310 --> 00:05:28,670
And that's something that I will
always have close to my heart 

106
00:05:28,950 --> 00:05:31,990
and this is something that also 
motivates me to push the product

107
00:05:31,990 --> 00:05:33,990
management side even further to 
sake. 

108
00:05:34,280 --> 00:05:36,520
Listen, we have so many 
customers that put their trust 

109
00:05:36,520 --> 00:05:38,320
in us. 
Let's try to make the product 

110
00:05:38,320 --> 00:05:40,720
even better. 
In essence, I want to remain a 

111
00:05:40,720 --> 00:05:43,400
customer advocate while I'm in 
product management. 

112
00:05:44,520 --> 00:05:48,440
Great to hear, Axel. 
Let's move from the requirements

113
00:05:48,440 --> 00:05:52,160
engineering implementation side 
in product management more to 

114
00:05:52,160 --> 00:05:56,320
the commercial side in product 
management rights with SAP was 

115
00:05:56,320 --> 00:06:01,680
launched I think in 2021 by us. 
And yeah, so like as a business 

116
00:06:01,680 --> 00:06:05,120
transformation as a service 
solution and we just recently 

117
00:06:05,120 --> 00:06:09,560
launched GROW with SAP with the 
goal that any size company can 

118
00:06:09,560 --> 00:06:13,720
successfully adopt cloud EAP. 
What is your understanding of 

119
00:06:13,720 --> 00:06:17,640
GROW with SAP maybe from product
management side and maybe you 

120
00:06:17,640 --> 00:06:19,880
can explain that a little bit 
more in detail as well? 

121
00:06:20,120 --> 00:06:21,160
Yeah, I'd love to. 
Thanks. 

122
00:06:21,200 --> 00:06:23,360
Good question. 
Before I go to GROW, let me just

123
00:06:23,360 --> 00:06:27,000
say that we have rise as you 
rightly put, rise with SAP and 

124
00:06:27,000 --> 00:06:30,470
grow with SAP. 
Those are very strong commercial

125
00:06:30,470 --> 00:06:34,470
models and both of them feature 
public cloud That's important. 

126
00:06:34,750 --> 00:06:38,790
RISE was naturally focused 
because of the address of a 

127
00:06:38,790 --> 00:06:41,030
market was more focused on the 
private cloud. 

128
00:06:41,270 --> 00:06:45,790
And we still have many customer 
use cases where we can also 

129
00:06:45,790 --> 00:06:49,390
position public cloud in RISE 
for existing companies. 

130
00:06:49,390 --> 00:06:53,190
That's why this especially for 
the existing market and existing

131
00:06:53,190 --> 00:06:56,170
customer base. 
The model that we call 2 tier, 

132
00:06:56,210 --> 00:06:58,690
we can discuss this a little bit
later, but just in short have a 

133
00:06:58,690 --> 00:07:01,930
headquarter on an S4 whether 
it's on premise or private cloud

134
00:07:01,930 --> 00:07:04,290
edition and then we have 
subsidiaries on public cloud. 

135
00:07:04,290 --> 00:07:07,290
That's a model that works under 
rise and it's I think a great 

136
00:07:07,290 --> 00:07:10,770
model to help customers and 
companies to partially 

137
00:07:10,770 --> 00:07:13,730
transition into the cloud where 
possible or where needed. 

138
00:07:14,370 --> 00:07:19,450
And then grow clearly for me 
describes our valuable offering 

139
00:07:19,450 --> 00:07:22,810
for mid market and net new 
customers which is um. 

140
00:07:23,360 --> 00:07:25,520
May be a different starting 
point if you compare that to the

141
00:07:25,640 --> 00:07:31,920
existing customer base when it 
comes to SAP, ERP systems and 

142
00:07:31,920 --> 00:07:34,600
funnily enough they have the 
similar changes in the market 

143
00:07:34,600 --> 00:07:36,360
that we see with the existing 
installed base. 

144
00:07:36,360 --> 00:07:41,640
So when we see this rise is 
actually targeting A dedicated 

145
00:07:41,640 --> 00:07:45,000
customer segment and we will be 
solving most of the same 

146
00:07:45,360 --> 00:07:48,000
problems, not all of them but 
most of the same and that's why 

147
00:07:48,320 --> 00:07:50,960
for this net new mid market we 
developed. 

148
00:07:51,490 --> 00:07:55,610
Grow to allow them to start 
their cloud transformation with 

149
00:07:55,610 --> 00:07:58,450
the latest and greatest 
state-of-the-art cloud ERP, 

150
00:07:58,530 --> 00:08:02,170
which we have with public cloud.
And that's why we want to help 

151
00:08:02,170 --> 00:08:05,170
them grow in their journey. 
And that's why I actually really

152
00:08:05,170 --> 00:08:09,570
also like the name GROW, because
we commit to the growth of our 

153
00:08:09,570 --> 00:08:11,490
customers when they're 
successful. 

154
00:08:11,810 --> 00:08:13,890
We as a solution provider are 
successful. 

155
00:08:14,220 --> 00:08:16,020
That's the clear commitment from
our side. 

156
00:08:16,100 --> 00:08:19,340
Yeah, I think rights and grow 
with SAP sounds like a very good

157
00:08:19,340 --> 00:08:21,500
initiative or commercial 
offering for me. 

158
00:08:22,900 --> 00:08:26,340
If I would be a customer, I 
would call you up and ask him, 

159
00:08:26,340 --> 00:08:30,420
hey, what does it take for me to
have the right cloud mindset? 

160
00:08:30,420 --> 00:08:33,980
What are the recommended steps 
you just suggest if I want to 

161
00:08:34,020 --> 00:08:36,780
implement as a PS100 cloud 
public edition, what would you 

162
00:08:36,780 --> 00:08:39,419
tell me? 
You're asking a former 

163
00:08:39,419 --> 00:08:42,380
consultants, so you can already 
imagine the answer it would be 

164
00:08:42,380 --> 00:08:44,620
it depends. 
But obviously I want to give you

165
00:08:44,620 --> 00:08:47,700
some more insight, but again 
there is no A1 size fits all 

166
00:08:47,700 --> 00:08:50,460
answer for that question. 
You really have to take case by 

167
00:08:50,460 --> 00:08:55,060
case depends on where you are as
a customer knowledge wise, what 

168
00:08:55,060 --> 00:08:57,900
is your business like. 
So the all the influencing 

169
00:08:57,900 --> 00:09:00,540
factors but customers and 
partners will be aware of those.

170
00:09:01,140 --> 00:09:03,260
I think what holds true for 
pretty much all the customers 

171
00:09:03,260 --> 00:09:06,020
are a couple of things and I'll 
just you know mention them and 

172
00:09:06,020 --> 00:09:12,260
that probably 98 to 99 times out
of 100 would be applicable #1 

173
00:09:12,260 --> 00:09:14,240
is. 
Starting with the scope 

174
00:09:14,240 --> 00:09:18,080
definition and understanding 
also the basic fit of a public 

175
00:09:18,080 --> 00:09:21,560
cloud solution, because there 
are some areas where we also as 

176
00:09:21,560 --> 00:09:24,760
a provider would recommend to 
customers maybe look into a 

177
00:09:24,760 --> 00:09:27,680
private cloud option. 
But as providers we're there and

178
00:09:27,720 --> 00:09:31,760
we have developed from our side 
a tool based guided procedure 

179
00:09:31,760 --> 00:09:33,640
which is called digital 
discovery assessment. 

180
00:09:33,920 --> 00:09:37,480
It's part of the discovery phase
from subactivate being our 

181
00:09:37,880 --> 00:09:40,680
implementation and 
transformation methodology if 

182
00:09:40,680 --> 00:09:42,700
you will. 
And this digital discovery 

183
00:09:42,700 --> 00:09:45,820
assessment is really, really 
important for customers to 

184
00:09:45,820 --> 00:09:48,820
understand what is the actual 
scope of my transformation 

185
00:09:48,820 --> 00:09:51,220
project. 
And besides the scope, you can 

186
00:09:51,220 --> 00:09:56,020
also validate if features and 
functions coverage match your 

187
00:09:56,020 --> 00:09:58,060
requirements. 
From a business perspective, 

188
00:09:59,700 --> 00:10:02,380
that's number one. 
Number two, as much as I like to

189
00:10:02,380 --> 00:10:07,740
talk about IT and IT, processes 
and architecture, etc, this 

190
00:10:07,740 --> 00:10:10,800
always comes second. 
Those projects that when you 

191
00:10:10,800 --> 00:10:14,200
engage in a cloud project, it is
first and foremost a business 

192
00:10:14,200 --> 00:10:17,680
transformation project. 
Moving the core business 

193
00:10:17,680 --> 00:10:22,440
processes of a company into a 
predefined standard works, it 

194
00:10:22,440 --> 00:10:24,360
works. 
We've shown this for several 100

195
00:10:24,360 --> 00:10:29,240
customers. 
It works and it still requires a

196
00:10:29,240 --> 00:10:32,040
lot of work, not so much that's 
a new thing in the cloud with 

197
00:10:32,040 --> 00:10:35,600
standardization, not so much on 
the IT side, but businesses have

198
00:10:35,600 --> 00:10:37,980
to adjust. 
Maybe even some organizations 

199
00:10:37,980 --> 00:10:41,580
have to morph into future 
organizations and that's why it 

200
00:10:41,580 --> 00:10:44,580
is first and foremost more than 
ever a business project. 

201
00:10:44,980 --> 00:10:48,820
Then next to that it is really 
important on how you staff the 

202
00:10:48,820 --> 00:10:53,060
project understanding again this
is a business project, we 

203
00:10:53,060 --> 00:10:56,180
recommend typically to do a 
three in a box model. 3 in a box

204
00:10:56,180 --> 00:10:59,940
model means you have one person 
dedicated per area and you 

205
00:10:59,940 --> 00:11:01,820
define as a customer how big 
that area is. 

206
00:11:01,820 --> 00:11:04,380
But typically I don't know, 
finance or controlling would be 

207
00:11:04,380 --> 00:11:06,860
1. 
Depending on the size, you have 

208
00:11:06,860 --> 00:11:11,660
three people or three main areas
that should work together and 

209
00:11:11,820 --> 00:11:15,780
generate the success of the 
project area #1 business. 

210
00:11:16,220 --> 00:11:19,100
You need someone or group of 
people who are able to take 

211
00:11:19,100 --> 00:11:22,260
decisions and they need to 
understand the current business 

212
00:11:22,260 --> 00:11:26,500
processes and need to be able to
assess how to transform into the

213
00:11:26,500 --> 00:11:28,860
new ones new standardized 
processes. 

214
00:11:29,500 --> 00:11:34,340
Second pillar in this three in a
box model would be IT you need. 

215
00:11:34,760 --> 00:11:37,040
IT support, I mentioned it's 
first and foremost a business 

216
00:11:37,040 --> 00:11:41,040
project, but still it is also 
there are some IT aspects that 

217
00:11:41,040 --> 00:11:43,920
you should be aware of, whether 
it's interfaces, whether it's a 

218
00:11:43,920 --> 00:11:46,640
data management, whether it's 
roles and authorizations, 

219
00:11:46,640 --> 00:11:49,440
reporting, et cetera. 
So there's a full list of topics

220
00:11:49,440 --> 00:11:51,320
that are relevant for the IT 
department. 

221
00:11:51,600 --> 00:11:54,640
And then thirdly, this being a 
transformation project, we would

222
00:11:54,640 --> 00:11:57,040
highly recommend you ask for 
help from NSI. 

223
00:11:57,040 --> 00:12:01,360
So an integrator as the subject 
matter expert for certain areas 

224
00:12:01,360 --> 00:12:03,040
to really guide you along the 
journey. 

225
00:12:03,400 --> 00:12:05,240
And be available for detailed 
questions. 

226
00:12:05,320 --> 00:12:09,520
So I mentioned scope definition.
Secondly, I mentioned the 

227
00:12:09,520 --> 00:12:11,800
business project, I mentioned 
the three in a box model. 

228
00:12:12,200 --> 00:12:15,840
And then the one thing that 
above and beyond everything else

229
00:12:15,840 --> 00:12:18,200
stands out is training and 
enablement. 

230
00:12:19,480 --> 00:12:24,040
Take the time, give enough space
for those three in a box that I 

231
00:12:24,040 --> 00:12:28,680
mentioned earlier to be properly
trained and enabled if you go 

232
00:12:28,680 --> 00:12:31,640
into a fit to standard mode you 
need. 

233
00:12:32,060 --> 00:12:35,580
Everyone to understand how the 
new standard works and then to 

234
00:12:35,580 --> 00:12:38,860
analyze the delta between where 
are you currently and how you 

235
00:12:38,860 --> 00:12:40,420
need to transform into the 
future. 

236
00:12:40,740 --> 00:12:44,020
If people go in a project and 
are not properly enabled on how 

237
00:12:44,020 --> 00:12:48,820
the standard looks like, the 
quality of the project is less 

238
00:12:48,820 --> 00:12:51,820
than it has to be. 
So that's why enablement. 

239
00:12:52,140 --> 00:12:55,500
Giving time for enablement for 
all the different resources is 

240
00:12:55,500 --> 00:12:58,420
absolutely key. 
Then you get the right decisions

241
00:12:58,420 --> 00:13:00,660
to have the right setup going 
forward and you don't have to 

242
00:13:00,660 --> 00:13:03,510
worry about the future. 
Thanks Axel for those great 

243
00:13:03,510 --> 00:13:07,790
recommendations. 
The last couple of years SAP 

244
00:13:07,790 --> 00:13:11,230
focused on professional service 
and finance led cloud earpiece 

245
00:13:11,230 --> 00:13:14,430
scenarios. 
This has changed as I can also 

246
00:13:14,430 --> 00:13:17,710
confirm now on product centric 
industries. 

247
00:13:17,750 --> 00:13:20,470
They have a stronger focus now 
at SAP. 

248
00:13:21,150 --> 00:13:24,030
And where do you see the 
strength of SA PS100 cloud 

249
00:13:24,030 --> 00:13:27,070
public edition for customers in 
your area and the product 

250
00:13:27,070 --> 00:13:30,050
centric industries? 
Yeah, you're absolutely right on

251
00:13:30,050 --> 00:13:32,010
the service industries. 
I think that is an industry 

252
00:13:32,050 --> 00:13:36,690
where we've seen much earlier 
that the industry itself is 

253
00:13:36,690 --> 00:13:40,330
willing to transform into more 
standardized processes and hence

254
00:13:40,330 --> 00:13:45,010
the desire of customers and the 
wider market to move into a 

255
00:13:45,010 --> 00:13:47,810
standardized SaaS product. 
Like as far as a public cloud 

256
00:13:47,810 --> 00:13:50,890
was there, discussions were much
easier, there was more of a 

257
00:13:50,890 --> 00:13:53,300
pull. 
And this put it gradually is 

258
00:13:53,300 --> 00:13:57,260
growing on the more product and 
operational LED companies which 

259
00:13:57,260 --> 00:14:00,220
is great to see. 
We see a huge demand coming from

260
00:14:00,220 --> 00:14:03,140
this companies and from the 
market and you know that more 

261
00:14:03,140 --> 00:14:06,420
traditional industries like 
component manufacturing, milk 

262
00:14:06,420 --> 00:14:09,780
product just to name a few. 
And when you ask about the 

263
00:14:09,780 --> 00:14:13,500
benefits from product centric, I
think here comes into play that 

264
00:14:13,500 --> 00:14:16,420
we as SAP have been in this 
market for decades. 

265
00:14:16,660 --> 00:14:19,300
We have a very strong experience
in industries. 

266
00:14:19,700 --> 00:14:22,860
We have been working with more 
manufacturing and product and 

267
00:14:22,860 --> 00:14:26,740
operational that focused 
companies over decades and we 

268
00:14:26,740 --> 00:14:29,700
are in excellent position to 
help them move into the cloud. 

269
00:14:30,100 --> 00:14:34,220
We have the breadth and depth in
many areas to address their 

270
00:14:34,220 --> 00:14:36,580
business needs. 
We have the experience again 

271
00:14:36,580 --> 00:14:39,380
especially also with the 
industries and we can really 

272
00:14:39,420 --> 00:14:43,180
help them transform where needed
and where beneficial for them 

273
00:14:43,260 --> 00:14:47,380
into a standardized to US 
environment and transform into 

274
00:14:47,380 --> 00:14:50,430
the cloud so. 
Why and how we do that is pretty

275
00:14:50,430 --> 00:14:51,950
simple. 
We combine 2 flavors. 

276
00:14:51,950 --> 00:14:56,750
One is obviously, we have the 
depth in a lot of functional 

277
00:14:56,750 --> 00:14:59,510
areas. 
We have capabilities that are, 

278
00:14:59,510 --> 00:15:02,230
you know, above and beyond what 
the competition has. 

279
00:15:02,630 --> 00:15:07,190
And we mix this now with a very 
broad end to end process view 

280
00:15:07,190 --> 00:15:10,710
where we bring end to end 
processes into the mix to really

281
00:15:10,710 --> 00:15:13,670
guide customers and say we 
understand your business. 

282
00:15:13,670 --> 00:15:16,350
Here's how you deal with those 
businesses and end to end view 

283
00:15:16,750 --> 00:15:18,350
and we bring together the 
various. 

284
00:15:18,680 --> 00:15:21,120
Functionalities in the right 
sequence and I think that's what

285
00:15:21,120 --> 00:15:24,320
we see resonating very, very 
well both with partners and 

286
00:15:24,320 --> 00:15:26,560
customers. 
Where you mentioned already the 

287
00:15:26,560 --> 00:15:31,200
robust end to end processes, 
yeah we already have or support 

288
00:15:31,200 --> 00:15:35,240
end to end best practices like 
sell from stock not size 1 and 

289
00:15:35,240 --> 00:15:37,930
engineer to order scenarios. 
So what? 

290
00:15:37,930 --> 00:15:40,850
Kind of efforts. 
Are you taking as the leader of 

291
00:15:40,850 --> 00:15:44,690
putting it or to streamline our 
current best practice approach 

292
00:15:45,090 --> 00:15:48,210
to be able to deliver end to end
business processes or scenarios 

293
00:15:48,210 --> 00:15:51,850
to our customers in the future? 
I think it's the natural next 

294
00:15:51,850 --> 00:15:53,450
evolution to be perfectly 
honest. 

295
00:15:53,450 --> 00:15:55,530
I think this is almost a no 
brainer that we do this. 

296
00:15:55,530 --> 00:15:59,370
Hell, we have quite naturally 
during the last couple of years 

297
00:15:59,370 --> 00:16:03,850
focused on making sure that the 
solution as one of public cloud 

298
00:16:03,850 --> 00:16:06,170
is very robust from a functional
coverage. 

299
00:16:06,780 --> 00:16:10,860
And now we're trying to bring 
those functionalities into 

300
00:16:10,860 --> 00:16:15,260
really an end to end value 
adding value chain value adding 

301
00:16:15,260 --> 00:16:17,340
view. 
So it's bringing the various 

302
00:16:17,340 --> 00:16:20,260
scope items that we see are 
necessary to achieve a certain 

303
00:16:20,260 --> 00:16:23,300
end to end process into a 
logical flow. 

304
00:16:23,300 --> 00:16:26,380
Making sure that there is the 
right handshake and hand over 

305
00:16:26,380 --> 00:16:29,860
from 1 functionality to the 
other that if there are any gaps

306
00:16:29,860 --> 00:16:31,620
that we close those gaps and 
then. 

307
00:16:32,100 --> 00:16:35,300
Also very important, this is 
also our messaging, how we 

308
00:16:35,300 --> 00:16:39,140
approach customers because my 
saying is an end to end process 

309
00:16:39,140 --> 00:16:43,140
gets us a seat at the table and 
the functional coverage, the 

310
00:16:43,140 --> 00:16:46,780
depth ensures that we stay 
invited to that table. 

311
00:16:46,780 --> 00:16:50,060
So that's really how we want to,
yeah, develop those end to end 

312
00:16:50,060 --> 00:16:53,420
scenarios and it's really about 
allowing A holistic view on the 

313
00:16:53,420 --> 00:16:56,660
overall value chain as I 
mentioned and then wherever we 

314
00:16:56,660 --> 00:16:58,700
need, we do a deep dive. 
So if you do. 

315
00:16:59,190 --> 00:17:02,790
Let's say sell from stock, very 
comprehensive end to end 

316
00:17:02,790 --> 00:17:06,349
scenario and then if there are 
specific questions on how do we 

317
00:17:06,349 --> 00:17:09,430
do warehousing in that 
particular scenario, we then 

318
00:17:09,430 --> 00:17:12,790
have the depth to go in and 
describe our capabilities and 

319
00:17:12,790 --> 00:17:15,470
help customers solve their 
issues in that area with the 

320
00:17:15,470 --> 00:17:18,190
functional depth. 
If we can move to another 

321
00:17:18,190 --> 00:17:20,829
scenario, actually if companies 
want to start their 

322
00:17:20,829 --> 00:17:24,550
transformation journey, would 
you suggest A2 tier ERP strategy

323
00:17:24,550 --> 00:17:28,470
starting with subsidiaries with 
SPS100 cloud public edition? 

324
00:17:29,060 --> 00:17:31,660
1st to drive innovations and 
then the transformation 

325
00:17:32,380 --> 00:17:34,780
respectively change management 
to the whole organization. 

326
00:17:34,940 --> 00:17:38,300
Well, the whole organization, 
I'm not so sure, but let me just

327
00:17:38,300 --> 00:17:40,900
pick up what I said earlier 
Marcus, on the two tier, you're 

328
00:17:40,900 --> 00:17:45,060
right, A2 tier for us is 
integrating A speedboat, the 

329
00:17:45,060 --> 00:17:49,500
public cloud into an overall 
company architecture where we 

330
00:17:49,500 --> 00:17:52,220
believe the headquarter for 
example in that example, the 

331
00:17:52,220 --> 00:17:55,780
headquarter runs on an S4 HANA 
on Prem or private cloud 

332
00:17:55,780 --> 00:17:58,010
edition. 
And we integrate certain 

333
00:17:58,010 --> 00:18:02,050
subsidiaries or certain business
units in and we use the public 

334
00:18:02,050 --> 00:18:05,290
cloud to map their business 
process into a system. 

335
00:18:05,650 --> 00:18:08,890
Now two tier as I mentioned 
earlier is core of our rise 

336
00:18:08,890 --> 00:18:12,210
offering for the installed base 
and we just recently had a 

337
00:18:12,210 --> 00:18:15,770
survey among customers who 
already have or are planning to 

338
00:18:15,770 --> 00:18:18,690
embark on their two tier 
strategy and top reasons for 

339
00:18:18,690 --> 00:18:22,490
them were agility also lower 
TCO, higher degree of 

340
00:18:22,490 --> 00:18:26,400
standardization and. 
These benefits, all those you 

341
00:18:26,400 --> 00:18:29,040
get a tick in the box when you 
look at the public cloud and the

342
00:18:29,040 --> 00:18:32,400
SaaS model and that's why I 
think this is a really nice 

343
00:18:32,560 --> 00:18:35,120
endeavor for companies. 
Then you asked about the whole 

344
00:18:35,120 --> 00:18:36,640
organization. 
One aspect is the change 

345
00:18:36,640 --> 00:18:39,040
management. 
We have to understand that some 

346
00:18:39,040 --> 00:18:42,560
of those customers possibly will
never move their main 

347
00:18:42,840 --> 00:18:46,160
headquarter businesses into a 
public in a highly standardized 

348
00:18:46,160 --> 00:18:50,200
public domain, but others are 
quite relevant and to manage 

349
00:18:50,200 --> 00:18:53,320
that. 
Both a very traditional on Prem 

350
00:18:53,320 --> 00:18:58,680
mindset plus a very standard 
focused public cloud mindset. 

351
00:18:59,000 --> 00:19:01,880
Also requires some effort on the
organizations, yeah, on the 

352
00:19:01,880 --> 00:19:05,440
businesses, on the IT 
departments, on the internal 

353
00:19:05,440 --> 00:19:08,120
governance models, etc. 
So starting with smaller 

354
00:19:08,120 --> 00:19:10,840
subsidiaries can actually be 
quite beneficial because it's 

355
00:19:10,840 --> 00:19:14,040
also a learning curve for the 
whole company, how to deal with 

356
00:19:14,040 --> 00:19:18,040
standardization and more let's 
say historically grown on 

357
00:19:18,040 --> 00:19:22,100
premise solutions. 
Let's move from end to end, the 

358
00:19:22,100 --> 00:19:25,540
Intel 2 tier more maybe on the 
SAP partner side. 

359
00:19:25,620 --> 00:19:29,020
And here I see that more and 
more SAP partners are actually 

360
00:19:29,020 --> 00:19:32,860
getting certified, which is a 
nice thing to sell and implement

361
00:19:32,860 --> 00:19:34,820
SAP as on a cloud public 
edition. 

362
00:19:35,420 --> 00:19:38,140
We also see that more and more 
developer extensibility 

363
00:19:38,140 --> 00:19:41,460
possibilities are shaped, 
meaning we release more and more

364
00:19:41,460 --> 00:19:44,420
Rbos. 
So Haba press for application 

365
00:19:44,420 --> 00:19:47,570
programming models which are. 
Really stable of course. 

366
00:19:47,570 --> 00:19:51,250
And do you or your team have a 
strategic plan which you might 

367
00:19:51,330 --> 00:19:54,850
can share for SAP partners to be
able to develop release 

368
00:19:54,850 --> 00:19:58,090
independent in the core in the 
future or starting right now? 

369
00:19:58,730 --> 00:20:00,490
Great question. 
First of all, I think it's 

370
00:20:00,490 --> 00:20:04,970
important that partners know 
that we count on them going 

371
00:20:04,970 --> 00:20:06,930
forward. 
And this is from 2 angles 

372
00:20:07,210 --> 00:20:10,010
obviously on the product side 
very well as you mentioned the 

373
00:20:10,010 --> 00:20:12,730
extensibilities I've seen that 
in recent projects that I've 

374
00:20:12,730 --> 00:20:15,730
done in my previous job we 
discussed about their. 

375
00:20:16,170 --> 00:20:18,410
The bus stop and the public 
transport, it's really for 

376
00:20:18,410 --> 00:20:21,130
customers, the last mile if you 
will. 

377
00:20:21,130 --> 00:20:26,690
So if 98% are standard, filling 
that remaining 2% getting on a 

378
00:20:26,690 --> 00:20:29,370
bus or maybe a taxi and that if 
used that and then getting to 

379
00:20:29,370 --> 00:20:31,690
your final destination. 
That's where we see the 

380
00:20:31,690 --> 00:20:34,330
extensibility kick in. 
And then really I'm super, super

381
00:20:34,330 --> 00:20:37,610
grateful that we were able to 
ship that as a new feature with 

382
00:20:37,610 --> 00:20:41,530
the three system landscape which
is essential for being able to 

383
00:20:41,530 --> 00:20:45,370
address even more customers. 
As it comes for when we talk 

384
00:20:45,370 --> 00:20:49,610
about you know developing on top
of that, I think right now we're

385
00:20:49,610 --> 00:20:51,490
fully focusing on the 
extensibility. 

386
00:20:51,890 --> 00:20:55,130
And going forward something that
is close to my heart as well is 

387
00:20:55,130 --> 00:20:59,970
that we discuss strategic areas 
where partners can also develop 

388
00:20:59,970 --> 00:21:02,850
their own products and sell 
their own products to complement

389
00:21:02,850 --> 00:21:04,370
what we deliver in the public 
cloud. 

390
00:21:04,370 --> 00:21:09,290
Those could be as specific niche
area topics in an industry or 

391
00:21:09,290 --> 00:21:12,090
also in certain functionality. 
So it's definitely something 

392
00:21:12,090 --> 00:21:15,170
we'll be looking into. 
But I want to mention this in 

393
00:21:15,170 --> 00:21:20,770
the public cloud more than ever.
We also need a large and 

394
00:21:20,770 --> 00:21:24,410
scalable number of partners to 
help us meet the customer 

395
00:21:24,410 --> 00:21:27,490
demand. 
We see the proverbial hockey 

396
00:21:27,490 --> 00:21:29,730
stick now kicking in. 
So the market demand has 

397
00:21:29,730 --> 00:21:33,170
significantly grown over the 
past two quarters. 

398
00:21:33,530 --> 00:21:36,450
The question is who helps those 
customers to be successful? 

399
00:21:36,890 --> 00:21:39,650
We cannot as a solution provider
as if he cannot do other 

400
00:21:39,650 --> 00:21:42,330
projects on ourselves, it would 
be impossible. 

401
00:21:42,720 --> 00:21:47,120
That's why we need experienced 
and pragmatic partners to help 

402
00:21:47,120 --> 00:21:49,440
customers on their 
transformation journey into the 

403
00:21:49,440 --> 00:21:51,840
cloud. 
And this is more than ever 

404
00:21:51,840 --> 00:21:53,520
important at this moment in 
time. 

405
00:21:53,520 --> 00:21:56,400
I think it's even more important
to have the implementation 

406
00:21:56,760 --> 00:21:59,160
partner side than the product 
partner side. 

407
00:21:59,160 --> 00:22:01,640
I'm not ruling out that the 
partner on the product side is 

408
00:22:01,640 --> 00:22:03,460
not important. 
I think that's clear. 

409
00:22:03,740 --> 00:22:07,060
But the implementation part is 
that where we this year and next

410
00:22:07,060 --> 00:22:10,740
year have to really shift gears 
and be even more scalable. 

411
00:22:10,740 --> 00:22:14,940
Otherwise we will possibly lose 
customers because we cannot help

412
00:22:14,940 --> 00:22:16,740
them transform. 
So this is really a call to 

413
00:22:16,740 --> 00:22:18,740
action. 
If partners are listening, we 

414
00:22:18,740 --> 00:22:22,580
need you to help us get the 
product out into the market and 

415
00:22:22,620 --> 00:22:26,380
successful adoption can only be 
done with a lot of partners. 

416
00:22:26,980 --> 00:22:29,540
Like actually said, if you 
listen to this reach out to us, 

417
00:22:29,580 --> 00:22:32,480
please come with your questions.
Let's stay on the topic of 

418
00:22:32,480 --> 00:22:34,840
strategy. 
What are your most important 

419
00:22:34,840 --> 00:22:37,440
strategic topics that you want 
to focus on this year? 

420
00:22:38,120 --> 00:22:39,920
Everything at once? 
No, that was a joke. 

421
00:22:41,520 --> 00:22:44,120
No, Let's stick with two things.
One thing we discussed earlier, 

422
00:22:44,320 --> 00:22:46,800
GROW has been launched. 
There are still some countries 

423
00:22:46,800 --> 00:22:48,520
where we're launching GROW as we
speak. 

424
00:22:49,040 --> 00:22:52,040
And I think as a product 
management unit, we need to help

425
00:22:52,040 --> 00:22:56,640
the field and partners convey 
the message and be there as a 

426
00:22:56,640 --> 00:22:59,120
trusted advisor for field and 
partners. 

427
00:22:59,580 --> 00:23:02,980
But also for customers, if there
are certain questions, again, we

428
00:23:02,980 --> 00:23:05,180
from a product management 
perspective, we are very 

429
00:23:05,180 --> 00:23:08,340
convinced that we have a very 
competitive product that has a 

430
00:23:08,340 --> 00:23:11,580
lot of breadth and to end 
scenarios in depth the um, 

431
00:23:11,660 --> 00:23:14,380
different functionalities. 
And we are convinced that this 

432
00:23:14,420 --> 00:23:18,420
is capable of solving many, many
customer issues and that's why 

433
00:23:18,420 --> 00:23:20,980
we just want to reach our 
helping hand to everyone 

434
00:23:20,980 --> 00:23:23,980
involved and help them come to 
the same conclusions we've done.

435
00:23:24,100 --> 00:23:26,660
So that would be the market 
focus growing with growth. 

436
00:23:27,270 --> 00:23:29,390
And then internally, obviously, 
it's about doing the right 

437
00:23:29,390 --> 00:23:31,910
things, right? 
That's easier said than done. 

438
00:23:32,190 --> 00:23:35,710
I think as a SAS provider, we 
always have to find the right 

439
00:23:35,710 --> 00:23:39,510
balance between quality and 
functional growth. 

440
00:23:39,870 --> 00:23:42,190
And this is where we need to 
find a good balance. 

441
00:23:42,990 --> 00:23:45,550
It'll be always finite 
resources. 

442
00:23:45,550 --> 00:23:47,230
How much do we invest in 
quality? 

443
00:23:47,430 --> 00:23:50,190
How much do we invest in 
functional innovations? 

444
00:23:50,830 --> 00:23:53,750
That's a very interesting topic 
that probably will keep us busy 

445
00:23:54,390 --> 00:23:55,870
for much more than only this 
year. 

446
00:23:57,280 --> 00:23:58,480
Awesome. 
Very good. 

447
00:23:59,360 --> 00:24:01,840
If you had one wish from SAP, 
what would that be? 

448
00:24:02,360 --> 00:24:06,880
That's a good question. 
Well, continue to transform is 1

449
00:24:06,960 --> 00:24:09,360
because we are as a company also
in the middle of a 

450
00:24:09,360 --> 00:24:13,280
transformation and for a 50 year
old company this is quite quite 

451
00:24:13,280 --> 00:24:15,960
something. 
If we are not able to adjust to 

452
00:24:16,120 --> 00:24:19,080
changing market trends then that
is an issue for our customers. 

453
00:24:19,080 --> 00:24:22,680
So we need to continue to 
transform and. 

454
00:24:23,280 --> 00:24:27,280
One thing that is made as a PA 
great company and will be of 

455
00:24:27,760 --> 00:24:30,720
essence remaining a great 
company is the empathy for 

456
00:24:30,720 --> 00:24:32,840
customers. 
So as I mentioned earlier, 

457
00:24:33,080 --> 00:24:36,280
anything we do start with the 
customer in mind. 

458
00:24:36,400 --> 00:24:39,080
Which meeting do I go to, which 
decision do I take, which 

459
00:24:39,080 --> 00:24:42,040
investment do I plan, which 
investment do I also maybe enter

460
00:24:42,040 --> 00:24:43,880
a stop. 
Those are all things that 

461
00:24:43,880 --> 00:24:46,080
decision should be always made 
with the customer in mind. 

462
00:24:46,800 --> 00:24:50,800
Unfortunately, we already at the
end could talk with you forever.

463
00:24:51,000 --> 00:24:55,150
But. 
Maybe one more question which 

464
00:24:55,150 --> 00:24:57,670
just came to my mind. 
Do you have a special quote or 

465
00:24:57,670 --> 00:25:01,830
something which keeps you going?
Yes, it is something that is a 

466
00:25:01,830 --> 00:25:05,870
quote that everyone knows and 
unfortunately only a few people 

467
00:25:06,710 --> 00:25:09,750
really take up and live 
accordingly and it's love it, 

468
00:25:09,910 --> 00:25:12,590
change it or leave it. 
Keep that in mind. 

469
00:25:13,070 --> 00:25:16,070
Every decision, every customer 
situation, every life situation.

470
00:25:16,350 --> 00:25:18,830
You always have those three 
decisions that you can take. 

471
00:25:18,870 --> 00:25:22,430
I always try to love it. 
Have the change, then leave it 

472
00:25:22,430 --> 00:25:24,910
and sort come second and third. 
I like that. 

473
00:25:24,910 --> 00:25:25,950
Excellent. 
I like that. 

474
00:25:26,710 --> 00:25:30,070
Thank you so much again and 
yeah, all the best in your role 

475
00:25:30,230 --> 00:25:32,550
and hope to see you in Waldo for
Zurich. 

476
00:25:32,790 --> 00:25:34,350
Thank you. 
Thank you Marcus for having me. 

477
00:25:34,350 --> 00:25:36,750
Good luck. 
As always, feel free to drop us 

478
00:25:36,750 --> 00:25:41,430
an e-mail via inside S4 at 
sap.com and let us know which 

479
00:25:41,430 --> 00:25:45,430
topics are of your interest 
TuneIn next time and be inside 

480
00:25:45,510 --> 00:25:46,750
SAP S for HANA.
