1
00:00:09,800 --> 00:00:12,160
Welcome to the podcast Inside 
SAP. 

2
00:00:12,240 --> 00:00:16,560
As for HANA Cloud, there is no 
customer success without product

3
00:00:16,560 --> 00:00:20,720
success and project success. 
I'm your host, Salina Kailbach, 

4
00:00:20,800 --> 00:00:24,760
and today we are diving into a 
topic that is crucial for 

5
00:00:24,760 --> 00:00:26,520
success in the partner 
ecosystem. 

6
00:00:26,880 --> 00:00:30,360
It's partner coaching. 
We've all heard the stories, 

7
00:00:30,360 --> 00:00:34,040
right? 
A partner starts an exciting ACP

8
00:00:34,040 --> 00:00:38,840
Cloud ERP project and soon 
things starts to feel 

9
00:00:38,840 --> 00:00:42,320
challenging. 
Maybe you haven't been there. 

10
00:00:43,280 --> 00:00:48,600
Suddenly, a project in distress 
lands on the desk of a special 

11
00:00:48,600 --> 00:00:53,160
task force team and it needs 
immediate attention. 

12
00:00:53,560 --> 00:00:57,760
The problem is, by that point 
the project might already be in 

13
00:00:57,760 --> 00:01:02,640
serious trouble. 
And let's be honest, the first 

14
00:01:02,640 --> 00:01:07,280
cloud ERP project is like 
stepping into a brand new game. 

15
00:01:07,600 --> 00:01:10,640
It's not a traditional on 
premise implementation. 

16
00:01:10,720 --> 00:01:14,520
There is a fresh methodology to 
get your head around. 

17
00:01:14,840 --> 00:01:19,320
You've got a three system 
landscape plus central business 

18
00:01:19,320 --> 00:01:21,760
configuration. 
And the functionality is 

19
00:01:21,760 --> 00:01:24,080
different because the code lines
are different. 

20
00:01:24,720 --> 00:01:29,080
And those mandatory 6 months 
upgrades, they're great for 

21
00:01:29,080 --> 00:01:32,680
innovation, but they require 
totally different discipline. 

22
00:01:33,280 --> 00:01:37,240
They mean a new rhythm for 
testing and analysis. 

23
00:01:37,240 --> 00:01:39,360
And it's actually a paradigm 
shift. 

24
00:01:40,120 --> 00:01:43,080
And it requires what we love to 
call a cloud mindset. 

25
00:01:44,280 --> 00:01:47,560
And you can no longer stick to 
this is how it worked in the 

26
00:01:47,560 --> 00:01:51,240
past. 
That's precisely why our partner

27
00:01:51,240 --> 00:01:55,520
coaching service exists. 
And today with me, Sebastian 

28
00:01:55,520 --> 00:01:59,360
Verdel, finance consultant, 
implementing SAP Cloud ARP at 

29
00:01:59,360 --> 00:02:03,640
our customers and doing partner 
coaching for our partners, the 

30
00:02:03,640 --> 00:02:07,120
partners who are starting their 
first Cloud ARP project. 

31
00:02:08,120 --> 00:02:10,840
So, Sebastian, would you like to
say a couple of words about 

32
00:02:10,840 --> 00:02:12,280
yourself? 
Sure. 

33
00:02:12,520 --> 00:02:14,520
Hi, Ali. 
Now first of all, thank you for 

34
00:02:14,520 --> 00:02:16,680
the invitation. 
It's a pleasure to have the 

35
00:02:16,680 --> 00:02:19,160
chance to talk about partner 
coaching in this format. 

36
00:02:19,760 --> 00:02:24,040
About me, I'm working in the SAP
industry since 2017. 

37
00:02:24,040 --> 00:02:27,320
Since the beginning of my 
professional career, I started 

38
00:02:27,320 --> 00:02:30,960
at a medium sized implementation
partner as a finance consultant.

39
00:02:31,640 --> 00:02:36,200
IN2023I switched to SAP where I 
first continued in Adobe Finance

40
00:02:36,200 --> 00:02:39,120
Consulting. 
Since last year, my focus has 

41
00:02:39,120 --> 00:02:42,480
shifted to partner coaching. 
In this role, I can leverage the

42
00:02:42,480 --> 00:02:46,400
knowledge I've gained in the SAP
Cloud ERP environment, 12 

43
00:02:46,400 --> 00:02:50,560
partners support their customers
and alternatively Dr. SA PS 

44
00:02:50,560 --> 00:02:52,480
strategy to become a cloud 
company. 

45
00:02:52,920 --> 00:02:57,080
Sebastian, let's start with the 
challenges that the partners 

46
00:02:57,080 --> 00:03:01,240
face during their first SAP 
Cloud ARP implementation. 

47
00:03:01,880 --> 00:03:05,520
What are those challenges and 
how do you tackle them in your 

48
00:03:05,600 --> 00:03:10,840
partner coaching engagements? 
There are several topics we must

49
00:03:10,840 --> 00:03:12,960
address in each partner coaching
engagement. 

50
00:03:13,400 --> 00:03:16,280
To give you some example, one of
the first topics we have to 

51
00:03:16,280 --> 00:03:19,600
address in each engagement is 
the fit to standard workshop 

52
00:03:19,600 --> 00:03:22,040
execution. 
Of course, fit to standard 

53
00:03:22,040 --> 00:03:25,000
workshops are standardized 
component in the SAP Activate 

54
00:03:25,000 --> 00:03:28,120
methodology, but it's not 
defining in detail how to 

55
00:03:28,120 --> 00:03:31,680
prepare and execute them. 
This is crucial because during 

56
00:03:31,680 --> 00:03:34,400
these workshops the data 
configuration items are 

57
00:03:34,400 --> 00:03:38,120
collected for the realized face.
Another crucial topic is the 

58
00:03:38,120 --> 00:03:41,520
initial system setup. 
This is very important because 

59
00:03:41,560 --> 00:03:44,840
some scope items can only be 
activated during the initial 

60
00:03:44,840 --> 00:03:48,640
setup and activation at a later 
stage is not possible. 

61
00:03:49,120 --> 00:03:52,320
In addition, we notice that 
cross functional topics are 

62
00:03:52,320 --> 00:03:55,480
often underestimated. 
These include authorizations, 

63
00:03:55,480 --> 00:03:59,400
migration and reporting. 
This is not totally AP specific,

64
00:03:59,400 --> 00:04:01,800
but we still address them when 
we have the chance to. 

65
00:04:02,560 --> 00:04:05,360
Sebastian, you mentioned 
Activate methodology. 

66
00:04:05,640 --> 00:04:09,040
Can you explain the key 
differences between SAP Cloud 

67
00:04:09,040 --> 00:04:12,200
Therapy methodology and the on 
premise version? 

68
00:04:13,320 --> 00:04:16,760
Traditional SAP projects are 
usually based on a waterfall 

69
00:04:16,760 --> 00:04:19,839
methodology, which is linear and
sequential. 

70
00:04:20,320 --> 00:04:23,680
In contrast, Activate 
methodology is an agile approach

71
00:04:24,040 --> 00:04:27,560
still with sequential phases, 
but within these phases the 

72
00:04:27,560 --> 00:04:29,680
execution is based on agile 
sprints. 

73
00:04:30,240 --> 00:04:34,480
On top of that, the methodology 
contains tailored milestones and

74
00:04:34,480 --> 00:04:38,920
content for Claudia P For 
example the sign of the backlog 

75
00:04:39,000 --> 00:04:41,480
and the already mentioned 
initial system activation at the

76
00:04:41,480 --> 00:04:44,720
end of the explore phase or how 
to approach the half yearly 

77
00:04:44,720 --> 00:04:46,800
release cycles. 
So. 

78
00:04:46,800 --> 00:04:49,400
The Activate methodology 
actually supports the 

79
00:04:49,840 --> 00:04:53,480
implementation from the kick off
until the go live and even 

80
00:04:53,480 --> 00:04:56,480
after. 
And why is it important to 

81
00:04:56,480 --> 00:05:00,000
involve the customers at the 
very early stage of the project?

82
00:05:00,320 --> 00:05:04,000
First of all, Cloudy RP is a 
highly standardized software, 

83
00:05:04,360 --> 00:05:07,160
more than any other SAPERP 
solution. 

84
00:05:07,680 --> 00:05:11,200
Customers benefit from pre 
delivered content and processes 

85
00:05:11,440 --> 00:05:14,040
which lead to faster 
implementation cycles. 

86
00:05:14,520 --> 00:05:18,040
But this requires the customer 
to familiarize themselves with 

87
00:05:18,040 --> 00:05:19,720
the standard processes and 
content. 

88
00:05:20,120 --> 00:05:23,280
Therefore, the involvement of 
key users is crucial for the 

89
00:05:23,280 --> 00:05:27,480
success of the implementation. 
Typically, a lack of customer 

90
00:05:27,480 --> 00:05:31,240
involvement leads to extended 
test and hyper care phases. 

91
00:05:31,800 --> 00:05:35,000
In partner coaching, we 
emphasize the importance of 

92
00:05:35,000 --> 00:05:39,000
customer involvement and safe 
enablement, which is crucial for

93
00:05:39,040 --> 00:05:41,720
activate success. 
But to be honest, it still 

94
00:05:41,720 --> 00:05:43,600
remains a typical project 
challenge. 

95
00:05:44,600 --> 00:05:48,800
And you say that the partner 
coaching is actually adapted 

96
00:05:48,800 --> 00:05:51,840
specifically based on the 
partner and the customer and the

97
00:05:51,840 --> 00:05:56,080
project requirements. 
Can you give us more insights on

98
00:05:56,080 --> 00:05:59,000
how you're working with the 
partners during this engagement?

99
00:05:59,800 --> 00:06:01,760
Sure. 
What makes partner coaching 

100
00:06:01,760 --> 00:06:05,280
unique is it's proactive and 
continuous approach. 

101
00:06:05,640 --> 00:06:07,640
We don't wait until something 
goes wrong. 

102
00:06:07,920 --> 00:06:11,520
We're more like a navigation 
system for the partners to have 

103
00:06:11,520 --> 00:06:13,720
the best possible impact. 
We ideally start the 

104
00:06:13,720 --> 00:06:16,160
collaboration at the beginning 
of the explore phase. 

105
00:06:16,560 --> 00:06:20,160
Usually, we align on regular 
calls to proactively address 

106
00:06:20,160 --> 00:06:23,760
current topic dependent on the 
project phase and continuously 

107
00:06:23,760 --> 00:06:25,920
build a reliable cloud mindset 
together. 

108
00:06:27,080 --> 00:06:30,360
It means that the partner 
coaching involves regular calls 

109
00:06:30,360 --> 00:06:33,600
to address the partner 
challenges and enhance the cloud

110
00:06:33,600 --> 00:06:36,080
mindset. 
Would you like to add something 

111
00:06:36,080 --> 00:06:39,000
about the partner coaching, What
it is and what it's not? 

112
00:06:39,640 --> 00:06:41,160
Yeah, that's a very good 
question. 

113
00:06:41,400 --> 00:06:45,520
So partner coaching is primarily
methodological coaching for 

114
00:06:45,520 --> 00:06:49,400
implementation partners. 
We are not customer facing and 

115
00:06:49,400 --> 00:06:51,680
do not work directly in the 
customer system. 

116
00:06:52,080 --> 00:06:55,520
The goal is to ensure the right 
information is available at the 

117
00:06:55,520 --> 00:06:59,200
right time in the right place. 
Partner coaching is definitely 

118
00:06:59,200 --> 00:07:02,480
not free of charge consulting 
manpower provided by SAP. 

119
00:07:03,120 --> 00:07:06,520
To return to the metaphor, the 
partner remains in the driver's 

120
00:07:06,520 --> 00:07:09,960
seat, but we provide the route 
to a successful cloudy IP 

121
00:07:09,960 --> 00:07:14,520
implementation. 
And you are driving all together

122
00:07:14,520 --> 00:07:16,960
to the successful implementation
and go live. 

123
00:07:18,040 --> 00:07:20,760
We've already heard about the 
cloud mindset couple of times 

124
00:07:20,760 --> 00:07:22,760
today. 
Can you elaborate on that 

125
00:07:22,760 --> 00:07:27,200
concept and why is it important 
to leave behind the old on 

126
00:07:27,200 --> 00:07:32,560
premise way of thinking? 
Essentially, the cloud mindset 

127
00:07:32,560 --> 00:07:36,240
means customers should build as 
much as possible on standard 

128
00:07:36,240 --> 00:07:40,320
functionalities. 
However, partners with long term

129
00:07:40,320 --> 00:07:44,040
on premise experience tend to 
propose developments and 

130
00:07:44,040 --> 00:07:46,080
extensions much faster, as they 
should. 

131
00:07:46,720 --> 00:07:49,880
This collides with the cloud 
mindset and can lead to negative

132
00:07:49,880 --> 00:07:54,200
impacts such as additional 
effort during implementation and

133
00:07:54,200 --> 00:07:57,640
the recurring release cycles. 
Therefore, we continuously 

134
00:07:57,640 --> 00:08:01,240
highlight the need to build a 
strong cloud mindset to ensure a

135
00:08:01,240 --> 00:08:03,880
successful implementation and 
long term success. 

136
00:08:04,920 --> 00:08:07,600
OK. 
Can you maybe say a couple of 

137
00:08:07,600 --> 00:08:11,400
words about a fit to standard 
workshops, how they are 

138
00:08:11,560 --> 00:08:15,320
structured, What is critical in 
the cloud ERP implementation 

139
00:08:15,320 --> 00:08:17,640
project and what is their 
clustering? 

140
00:08:18,440 --> 00:08:20,960
Sure. 
To begin, the overall goal of 

141
00:08:20,960 --> 00:08:24,400
Fit to Stand Up workshops is to 
define all the relevant 

142
00:08:24,400 --> 00:08:26,760
configuration items for the 
realized phase. 

143
00:08:27,280 --> 00:08:30,160
To achieve that goal, of course 
every consultant has their own 

144
00:08:30,160 --> 00:08:34,200
style, but what has proven to be
successful is a short 

145
00:08:34,200 --> 00:08:37,080
theoretical presentation 
followed by a process 

146
00:08:37,080 --> 00:08:40,640
demonstration in the starter 
system and in the end 

147
00:08:40,640 --> 00:08:44,000
collaboratively recording the 
configuration items in the 

148
00:08:44,000 --> 00:08:46,760
backlog. 
When I was preparing myself for 

149
00:08:46,760 --> 00:08:50,560
fit to standard workshops, I was
already noting down all the 

150
00:08:50,560 --> 00:08:54,040
items I know I had to check with
the customer without the risk of

151
00:08:54,040 --> 00:08:56,720
missing something. 
Regarding the clustering. 

152
00:08:57,080 --> 00:09:01,480
Functionalities are bundled into
so-called scope items in Cloudy 

153
00:09:01,480 --> 00:09:05,200
RP, but these scope items do not
always correspond to the process

154
00:09:05,200 --> 00:09:07,880
perspective. 
For example, in finance, there 

155
00:09:07,880 --> 00:09:11,720
are many separate scope items. 
Especially in asset accounting. 

156
00:09:12,320 --> 00:09:14,760
It is the partners 
responsibility to cluster the 

157
00:09:14,760 --> 00:09:18,920
scope items in a meaningful, 
process oriented and digestible 

158
00:09:18,920 --> 00:09:21,240
way. 
This is where we support during 

159
00:09:21,240 --> 00:09:24,200
the coaching sessions. 
Thank you for this insight, 

160
00:09:24,200 --> 00:09:26,760
Sebastian. 
And now to put a front spin on 

161
00:09:26,760 --> 00:09:29,240
all this, it's time for my 
favorite section. 

162
00:09:29,920 --> 00:09:34,080
This is the first five. 
I'm going to throw out five 

163
00:09:34,160 --> 00:09:38,600
quick quirky questions about our
topic, and you should answer the

164
00:09:38,600 --> 00:09:41,440
questions with just one word or 
a short sentence. 

165
00:09:41,680 --> 00:09:45,440
Let's go. 
What's 1 phrase you would banish

166
00:09:45,440 --> 00:09:48,280
from a public cloud project to 
sharpen the cloud mindset? 

167
00:09:49,120 --> 00:09:52,080
I have to go with this has 
worked on on premise. 

168
00:09:52,640 --> 00:09:55,920
What's the most common Houston 
We have a problem moment that 

169
00:09:55,920 --> 00:09:57,760
the partner coaching helps to 
avoid? 

170
00:09:58,320 --> 00:10:01,320
Selecting the wrong initial 
scope and Ledger set up during 

171
00:10:01,320 --> 00:10:04,760
the system activation. 
That's a very good point, 

172
00:10:04,760 --> 00:10:07,160
Sebastian. 
We put the link to our blog in 

173
00:10:07,160 --> 00:10:10,160
the show notes. 
If partner coaching was a movie 

174
00:10:10,160 --> 00:10:14,000
genre, what would it be? 
A body cop film, a training 

175
00:10:14,000 --> 00:10:18,720
montage or a suspense thriller? 
Yeah, good question. 

176
00:10:18,720 --> 00:10:23,160
But I think I would go for the 
body cop film as we are building

177
00:10:23,160 --> 00:10:26,600
a close relationship with our 
partners at eye level which is 

178
00:10:26,600 --> 00:10:29,920
even fun sometimes. 
In the world of partner 

179
00:10:29,920 --> 00:10:33,200
coaching, what initial hurdle 
often becomes the most rewarding

180
00:10:33,200 --> 00:10:37,640
challenge for the newcomers? 
The first implementation itself.

181
00:10:38,080 --> 00:10:40,600
After that, you can leverage the
gained experience. 

182
00:10:41,240 --> 00:10:45,320
And finally, what's the quickest
light bulb moment you see when 

183
00:10:45,320 --> 00:10:48,440
coaching a partner on the cloud?
ARP methodology. 

184
00:10:49,440 --> 00:10:53,880
Hard to say, but maybe the fact 
that business role templates are

185
00:10:53,880 --> 00:10:57,120
not meant for productive use. 
Thank you, Sebastian. 

186
00:10:57,400 --> 00:10:59,520
Thank you very much Elena, it 
was a pleasure. 

187
00:10:59,520 --> 00:11:02,120
Hope to talk to you soon. 
Thank you for listening to 

188
00:11:02,120 --> 00:11:05,080
today's episode. 
If you enjoyed the insights, 

189
00:11:05,080 --> 00:11:08,320
make sure you follow and 
subscribe to Insight SAP. 

190
00:11:08,440 --> 00:11:12,360
As for Anna Cloud on Spotify or 
Apple Podcast so you'll never 

191
00:11:12,360 --> 00:11:17,280
miss an update on Spotify, you 
can use our Q&A and poll 

192
00:11:17,280 --> 00:11:19,160
features directly in the 
episode. 

193
00:11:19,720 --> 00:11:22,720
Tell us what you think or vote 
on the next topics you want us 

194
00:11:22,720 --> 00:11:25,880
to explore. 
And on Apple Podcast, feel free 

195
00:11:25,880 --> 00:11:27,640
to drop a quick rating or 
review. 

196
00:11:27,800 --> 00:11:30,040
It really helps others discover 
the show. 

197
00:11:30,880 --> 00:11:35,520
Stay tuned, stay curious, and as
always, be inside SAPS for Mono 

198
00:11:35,520 --> 00:11:35,920
Cloud.
