1
00:00:00,000 --> 00:00:06,520
You know, the one of the ideas that I think is nicely percolated in the I wonder if that's based on Latin.

2
00:00:06,620 --> 00:00:10,060
I should look up percolation. Doesn't that seem like I wonder where that comes from.

3
00:00:10,060 --> 00:00:26,020
But over in the past year, in the Latin America, percolate, I think it's from the coffee language, you know, that you want your drip percolation coffee.

4
00:00:26,580 --> 00:00:34,220
I was reading some, you know, the old Tinker, Taylor, Soldier, Constant Gardener, and someone wanted coffee from a percolator.

5
00:00:34,220 --> 00:00:40,340
And that was that was an odd sort of specification. I guess shaken, not stirred, but from a percolated.

6
00:00:40,720 --> 00:00:54,140
Yes. Anyhow, in the past year, related to percolation news, in so much as it shares the first letter, I think in the platform world, there's been a stronger idea,

7
00:00:54,260 --> 00:01:00,180
kind of a pulling forward of a notion that's existed for a while, you know, since back in the platform as a service, the cloud foundry days.

8
00:01:00,180 --> 00:01:04,820
And that is thinking about your platform as a product. Right. And I haven't watched them all.

9
00:01:04,820 --> 00:01:12,200
But in the most recent, like, you know, huge multiple bucket smorgasbord of platform con.

10
00:01:12,400 --> 00:01:17,560
I think there were a couple of talks on this and always, always, you know, you got the team topology people who show up with this.

11
00:01:17,560 --> 00:01:22,760
And you got you got Paula Kennedy, who we used to work with, bringing that in some other people, always good.

12
00:01:23,240 --> 00:01:30,280
But I think there's an aspect of like product. Like, it's fun to play around with, like, so what does that mean product?

13
00:01:30,280 --> 00:01:38,160
Right. And there's and this is especially great because I don't know about you, Ben, but I find the one, not the only, but one of the most enjoyable.

14
00:01:38,480 --> 00:01:47,120
If you were to draw a diagram and on, let's say, let's say the vertical axis, that would be the Y axis up and down.

15
00:01:47,440 --> 00:01:59,220
That was that was fun. And then the horizontal axis, the X axis, that was ease of executing as in doing, not the other executing.

16
00:01:59,360 --> 00:02:08,780
I think I think for you and I, having worked in software for so long at a vendor, perhaps talking about what a software product is, is way up in the in the upper right.

17
00:02:08,780 --> 00:02:13,040
Because we just talk about ourselves, like what what what we basically do. It's very easy.

18
00:02:13,260 --> 00:02:20,860
And I think I think that is that is other than the the diagram that I just went over, your two by two there.

19
00:02:21,020 --> 00:02:27,120
I think it's it's actually very beneficial to the platform world because it means that you don't have to, like, reinvent stuff.

20
00:02:27,420 --> 00:02:35,220
And also, as I'm fond of pointing out, it means that all of these vendors and by vendor, I mean, cloud providers, you know, people who want to sell you IT stuff.

21
00:02:35,460 --> 00:02:40,040
They're always looking for an excuse to talk with you. Right. As long as you're talking, you might be buying.

22
00:02:40,380 --> 00:02:46,140
And so like what you can do is you can ask them about that and get a whole bunch of like free advice. Right.

23
00:02:46,680 --> 00:02:53,540
And so it's great. There's this it's not like, you know, it's not like, oh, like not ALM.

24
00:02:53,920 --> 00:02:57,520
That's an older thing. The LLMs, the AI stuff is like this brand new thing.

25
00:02:57,600 --> 00:03:03,960
We've got to spend a lot of time to understand how to apply. It's like, nope, if you want to figure out what as a product means, we've known about that forever.

26
00:03:03,960 --> 00:03:12,560
You can just do it now. I think I think the first thing that I one of the things I like to talk about a lot is the idea of marketing your platform.

27
00:03:12,560 --> 00:03:21,380
Right. Again, and this is why I went to that whole spiel of vendor stuff is like any vendor knows that if you have a product or a platform, it's very important.

28
00:03:21,900 --> 00:03:25,820
Number number one task is to tell people that exists. That's always good.

29
00:03:26,600 --> 00:03:35,200
And then and then the after that, if you want to achieve momentum and get usage, you basically just apply basic marketing knowledge.

30
00:03:36,200 --> 00:03:45,160
Right. And that is, you know, talking about I mean, I mean, tell you I'm going to go over, but you tell me what you think basic marketing things are.

31
00:03:45,200 --> 00:03:49,100
Right. For for people who aren't practiced in marketing.

32
00:03:49,100 --> 00:04:01,480
But, you know, the basics are basically like the basics are basically the the the rudimentary things are you have to tell people what what your product does.

33
00:04:01,960 --> 00:04:05,840
Explain to explain to them how it helps them solve problems and do things better.

34
00:04:05,960 --> 00:04:07,620
The value props. Right.

35
00:04:07,900 --> 00:04:16,480
And then the third major category is essentially like telling them why you're the best choice amongst all the competition.

36
00:04:16,720 --> 00:04:19,080
Right. Doing some some competitive marketing.

37
00:04:19,460 --> 00:04:25,940
And I think that all of these apply if you're running an internal developer platform and you're trying to promote it.

38
00:04:25,980 --> 00:04:28,000
What what what's what's your take on that, Ben?

39
00:04:28,060 --> 00:04:30,300
I mean, you you've worked with people who are.

40
00:04:32,600 --> 00:04:36,220
Using platforms going from zero to to a lot.

41
00:04:36,920 --> 00:04:44,120
And, you know, now now you work on this side of doing it, like when you think about like marketing a platform for internal use,

42
00:04:44,120 --> 00:04:47,840
we don't want to give up the secrets of how we're so successful marketing our platforms.

43
00:04:48,040 --> 00:04:53,880
But for internal use as an organization, like what's the marketing thing that you you've seen people do well and poorly?

44
00:04:54,780 --> 00:04:57,320
Well, and I know I know where it always starts.

45
00:04:57,520 --> 00:05:03,480
I think the point where, you know, you've got a product is when you start thinking about giving it a name.

46
00:05:04,480 --> 00:05:06,560
The naming part is the fun part.

47
00:05:06,620 --> 00:05:13,400
Right. It's like at that point, you know, you've got a product because you've got to think of a name and you want your name to be excellent.

48
00:05:13,400 --> 00:05:18,520
In every way, you know, has to be cool and serious at the same time.

49
00:05:19,580 --> 00:05:20,620
Yes, yes.

50
00:05:21,480 --> 00:05:25,720
And, you know, meaningful and vague so that you can copyright it.

51
00:05:26,080 --> 00:05:29,800
And, you know, all these things all have to apply at the same time.

52
00:05:29,920 --> 00:05:47,200
You know, Tanzu is a great brand, you know, the kind of the kind of word didn't really exist, you know, before we sort of cooked it up to describe describe our, you know, our brand and how it and then it's been, you know, used across a whole bunch of different products.

53
00:05:47,200 --> 00:05:51,920
So I think I think, you know, you've got a product when you start talking about names for it.

54
00:05:51,920 --> 00:06:00,800
And the naming part is very exciting because, you know, you can have little competitions and try and figure out what you want to what you want to put on your T-shirts.

55
00:06:00,980 --> 00:06:02,500
You know, what should your T-shirts say?

56
00:06:02,580 --> 00:06:02,780
Right.

57
00:06:03,420 --> 00:06:07,200
Yeah, you bring up a good point that I skipped over, and that is brand, right?

58
00:06:07,420 --> 00:06:16,440
And having the brand part of it, which is like, and, well, first of all, first of all, they introduce another, you know, to underline what you're doing, what you're saying there.

59
00:06:16,540 --> 00:06:29,660
Like my teammate, Deshaun, he has this funny way of doing it is whenever he's talking with people or introducing platforms, I mean, you know, Deshaun's demeanor, so you can almost envision him saying this as he'll say, like, well, do you have a T-shirt yet?

60
00:06:29,980 --> 00:06:30,380
Right.

61
00:06:30,480 --> 00:06:43,040
And, you know, what he's the, I guess, pun intended, the thread that he's pulling out there is that a manifestation of the brand, meaning that you have done a brand is often a T-shirt, right?

62
00:06:43,080 --> 00:06:46,080
And what do we know about developers that love T-shirts?

63
00:06:46,300 --> 00:06:50,420
It's just like, that's, it's, and here's a little insider marketing thing.

64
00:06:50,880 --> 00:06:58,240
People at vendors hate T-shirts, and they hate T-shirts, not you and me, because we benefit from them.

65
00:06:58,240 --> 00:07:10,740
They hate T-shirts because, one, they're expensive, and two, they're complicated because you're always like, all right, if we get the T-shirts, how many XS, how many S, how many medium, how many large, how many X, you know, you got to do the size division.

66
00:07:11,120 --> 00:07:14,480
Then you're also like, is this conference in America or is it in the rest of the world?

67
00:07:14,480 --> 00:07:15,980
Because that determines your shirt size.

68
00:07:16,060 --> 00:07:23,400
Like, do we, how many, do we get unisex shirts or do we get like, you know, like, like women shirts?

69
00:07:23,540 --> 00:07:25,040
Like, and what's the split that we have?

70
00:07:25,080 --> 00:07:30,220
So first you've got that, and then they're also expensive per unit, and then you have to ship them.

71
00:07:30,340 --> 00:07:34,840
And if you're shipping them across borders, oh my God, all sorts of problems, right?

72
00:07:34,940 --> 00:07:44,840
Over the years, I've been in numerous situations, not that many, but enough where like someone was like, I don't know, there's somewhere in UK customs, maybe we'll never see them again.

73
00:07:45,060 --> 00:07:47,480
And they'll just be like boxes of T-shirts.

74
00:07:47,660 --> 00:07:50,820
And then, you know, it's great if it's within the same borders.

75
00:07:50,820 --> 00:07:57,960
But, and then once you're done with the conference, you often have a lot of leftover T-shirts that are all like, you know, excess or triple X large.

76
00:07:58,460 --> 00:08:00,340
And then you've got to ship those back.

77
00:08:00,820 --> 00:08:08,260
And so this is why, however, you know, the point being that it's, you know, marketing has a lot of effort that goes into it.

78
00:08:08,460 --> 00:08:12,300
And if you, you know, of more magnitude than the T-shirts there.

79
00:08:12,380 --> 00:08:15,240
But you're right, brand, very important to have a name.

80
00:08:15,240 --> 00:08:41,860
And I think one of the other little overly clever, but I think practical things that I've been told multiple times over the years by people who do platforms is one of the most important things about a brand, as you're getting to, is not only that you're coming up with your own name, as you were saying, but it's important to also have your own name for what this platform effort is, what this digital transformation effort is.

81
00:08:41,860 --> 00:08:50,240
To distinguish it from having to be orthodoxed, whatever methodology you're using, right?

82
00:08:50,240 --> 00:09:00,880
So the example of that is, I remember I was in, I guess, during a SpringOne at some point when we had, I forget his name, but there was a colonel from the Air Force who came to talk about the work that they were doing.

83
00:09:01,540 --> 00:09:07,520
And he had talked about this actually on the keynote and in the session as well, I think.

84
00:09:07,880 --> 00:09:09,680
But he was saying, like, you got to be really careful.

85
00:09:10,080 --> 00:09:12,320
You don't ever want to call something you're doing agile.

86
00:09:12,900 --> 00:09:20,880
Because the moment you call it agile, what's going to happen is everyone's going to pick their favorite agile book, and then they're going to tell you why you're doing it wrong.

87
00:09:20,880 --> 00:09:32,900
And you're going to spend way too much time talking about, like, yes, we're not following the crystal method, like, or no, we're not following the 1989 edition of Extreme Programming.

88
00:09:33,220 --> 00:09:38,100
Or, yes, I didn't realize about release trains and safe, and on and on and on, right?

89
00:09:38,160 --> 00:09:54,740
And instead, his point, which I've heard over and over again, was that, and I believe this, which is like, yeah, those books are supersets of, he wasn't saying this explicitly, but those guidelines, those practices are supersets of what you're going to end up doing.

90
00:09:54,900 --> 00:10:03,700
And the reason they're supersets is because how you apply it is going to be unique to the constraints and the opportunities of your organization, right?

91
00:10:03,780 --> 00:10:06,180
Like, there's just going to be things.

92
00:10:06,180 --> 00:10:09,800
Like, maybe you can adopt all of the practices, and maybe you can't, right?

93
00:10:09,900 --> 00:10:31,720
And I think we've seen that over the years, where, like, you know, whenever there's, like, a DevOps engineering group, or probably also, like, a site reliability engineer, an SRE group, I'm sure there's numerous people who are like, well, according to Chapter 7 of the Google SRE book, we are not following those practices, so therefore, your entire existence is invalidated, right?

94
00:10:31,740 --> 00:10:33,440
It's the old, my hair is a bird situation.

95
00:10:34,080 --> 00:10:37,060
So I think a brand, it's good to detract it.

96
00:10:37,960 --> 00:10:38,800
Is that the right word?

97
00:10:38,880 --> 00:10:44,480
It's good to disassociate it from, like, the Bible of the methodology you're trying to follow.

98
00:10:45,160 --> 00:10:50,720
Yeah, and also, you know, your platform is custom to you, right?

99
00:10:51,200 --> 00:10:51,520
Exactly.

100
00:10:51,960 --> 00:10:53,340
That's what you're saying, isn't it?

101
00:10:53,340 --> 00:11:03,900
It's your choices of what are important based on your context, which is different for every organization out there, you know?

102
00:11:04,480 --> 00:11:04,660
Yeah.

103
00:11:04,660 --> 00:11:09,160
So, yeah, it's your brand and your actual platform, your actual product.

104
00:11:10,160 --> 00:11:13,680
They are kind of unique to you, and you need to own them, right?

105
00:11:13,720 --> 00:11:22,260
In terms of not just, you know, provide them, but also like them and want folks to use them and want to sort of promote that.

106
00:11:22,940 --> 00:11:37,220
And so further into the whatever, the guidebook for platform marketing, like another thing that I've learned from talking with people over the years is, so what does that look like to market?

107
00:11:37,300 --> 00:11:52,980
So we've gone over, like, you know, you've got to have the brand, the name, and part of that is, and this is something that I picked up from, like, you know, UK GDS people talking about stuff is it's important to think about a set of principles that you have.

108
00:11:53,220 --> 00:12:00,640
And the principles, like, you know, it's fine to have principles, and I don't mean my tone to be dismissive, but I'm just saying that's not the area I'm talking about.

109
00:12:00,680 --> 00:12:06,340
It's great and fine to have principles like, you know, we should be good to each other, right?

110
00:12:06,340 --> 00:12:13,160
Like, the kind of, like, basic human things, or as I often think about it, like, well, I mean, if you're not doing that, that's unfortunate, right?

111
00:12:13,240 --> 00:12:21,420
Like, you know, every time we have to take our annual training about, you know, don't do embezzlement, I think, like, hmm, I like how positively you think about me.

112
00:12:23,000 --> 00:12:37,120
But anyways, like, you want to have that, but these principles, and I forget the name of the book, but there's a great book written by some people who had done a lot of the UK GDS work, and if you look at the list of principles that they have, they are, like, actionable principles.

113
00:12:37,460 --> 00:12:49,320
They're not just, like, I mean, you know, Pivotal had some great principles, like, do kind, keep it simple, be kind, keep it simple, like, I embarrassingly forget what they are, but those were high-level principles.

114
00:12:49,320 --> 00:13:01,120
But these principles are more things like, you know, this wasn't one of them, but it would be, like, minimize the time it takes a customer to finish a task, right?

115
00:13:01,160 --> 00:13:05,220
Like, it's a guiding principle of, like, focus on this kind of thing.

116
00:13:05,220 --> 00:13:20,460
Or, I mean, it could be all the way down to something like, allow a developer to get their own database or their own middleware completely on their own, right?

117
00:13:20,700 --> 00:13:24,420
Yeah, like the principle of self-service, you know, that sort of thing.

118
00:13:24,520 --> 00:13:25,160
Yeah, absolutely.

119
00:13:25,400 --> 00:13:37,020
Right, and that may seem kind of obvious, but as I was going through that, I was thinking, like, you know, back in the 2000s when I worked in the systems management, as we called it, space,

120
00:13:37,400 --> 00:13:47,120
and there was business service management, you know, and BSM, and also, like, ITIL stuff, like, more of a principle there.

121
00:13:48,080 --> 00:14:02,740
And I don't know if the sages of ITIL and ITSM, IT service management, would, like, like this, but there is an implicit principle of have a request system.

122
00:14:03,000 --> 00:14:08,640
I mean, they probably would, because there was a whole book in the 10, 12-volume set of ITIL v2 that was, like, service requests.

123
00:14:08,700 --> 00:14:14,400
And it was, like, we have a principle that the way that IT works is people request things, right?

124
00:14:14,680 --> 00:14:21,240
Which is the, not the opposite, but it's much different than people self-service get things, right?

125
00:14:21,240 --> 00:14:25,560
So, and that's where the rise of the ticket desk and the workflow to do that.

126
00:14:25,660 --> 00:14:33,080
And a lot of things come through is you have this principle of the way that people get stuff is they request it.

127
00:14:33,480 --> 00:14:43,540
I guess you could make a, I don't know if it's silly, but a silly analogy of, like, you know, it used to be you'd go to the grocery store in, like, 1892,

128
00:14:43,540 --> 00:14:50,540
and everything was behind the counter, and you would have to request your little bag of coffee or your beans.

129
00:14:50,700 --> 00:14:58,700
And so that's a request mentality for a platform, whereas nowadays you just go get what you want and you check out, right?

130
00:14:58,840 --> 00:15:03,820
And so, like, figuring out in your platform, like, what those principles are.

131
00:15:03,880 --> 00:15:09,380
And they can be operational principles, but, like, they're kind of like the goals or the principle behavior that you have.

132
00:15:09,420 --> 00:15:16,260
Like, that's also very much so not only to guide the way that you're doing things, but it's also part of the marketing, right?

133
00:15:16,260 --> 00:15:30,780
Because it's something that you use to kind of talk about with your community, with your customers, developers, and other people to kind of explain, back to marketing, like, what the deal is, what the value props are,

134
00:15:30,840 --> 00:15:42,780
the positioning of your platform is, how it thinks and how it can help people out, which I think is a valuable thing to, I think, I usually have the little book over there.

135
00:15:42,780 --> 00:15:55,060
But Duke Energy, who we worked with, and I think we still do, they had, like, this little book they would give people, like, once they got into the, not only the platform world, but, like, the new way of doing things, which was nice.

136
00:15:55,560 --> 00:16:17,380
Yeah, and together they form a sort of a charter, don't they, in a way, they sort of form a contract, as such, in that, you know, you use our platform, you can expect these things, and also expect that we'll continue to work on these things, so that it follows these guiding principles and delivers on the promises being made by them, right?

137
00:16:17,920 --> 00:16:29,260
Yeah, absolutely. And, you know, this principles thing, as you were kind of getting to this sort of, like, I guess to use, like, fancy pants operations term, these promises being made, right?

138
00:16:29,340 --> 00:16:41,540
Like, like, it falls into the line of, like, community management, and, like, your platform team's own internal operations, and I think it's also, like, a large part of the marketing that exists, right?

139
00:16:41,540 --> 00:16:56,160
It helps form, and this gets into the territory of marketing, where if you're, like, kind of cynical, then you do identify, like, the, whatever, the manipulative stuff of some marketing, right?

140
00:16:56,240 --> 00:17:06,000
But, like, of course, you don't want to be manipulative, but, like, there is a value in marketing of creating an identity that people identify with, right?

141
00:17:06,000 --> 00:17:25,060
And especially in technology, if you're not overly cynical about it, and you know how to do it, you can realize that, like, developers and operations people, like, identifying with the technology in that marketing sense happens all the time and is super valuable for everyone, right?

142
00:17:25,080 --> 00:17:32,320
So, for example, you know, if someone's a developer, you immediately ask, oh, what do you develop in, right?

143
00:17:32,320 --> 00:17:42,640
Because what you're asking is what their developer identity is, and usually they'll say, like, oh, I'm a Java developer, or I'm a, you know, Rails developer, or, you know, whatever, right?

144
00:17:42,680 --> 00:17:51,240
Like, some people, like, will be, like, oh, but you can eventually pin them down and be, like, what do you spend most of your time developing in and know the most about, and what do you get paid to develop in?

145
00:17:51,280 --> 00:17:53,840
It's just, like, that's what you are, right?

146
00:17:53,840 --> 00:18:05,360
Like, and, you know, also, you know, people will say they're, like, a VMware person, or they're a Linux administrator, or whatever, all these various things, and you get certified in Red Hat or certified from the CNCF.

147
00:18:05,460 --> 00:18:15,380
So, that's another thing that when it comes to the platform that you want to do is you think about how can we start building up that identity that people have around it, right?

148
00:18:15,380 --> 00:18:21,320
Like, I use, like, in JPMorgan Chase, they have, like, the Gaia platforms, right?

149
00:18:21,380 --> 00:18:26,000
And, you know, you want people to start thinking, like, I use the Gaia platform, right?

150
00:18:26,020 --> 00:18:31,340
Or in Mercedes-Benz, they have a Cloud Foundry platform and a Kubernetes platform.

151
00:18:31,540 --> 00:18:32,620
They have multiple platforms.

152
00:18:32,720 --> 00:18:35,800
But they have a Cloud Foundry platform, you know, the Tanzu Application Service.

153
00:18:36,440 --> 00:18:42,540
And so, those developers, you know, they can identify a little bit with, like, oh, I use the Cloud Foundry platform, right?

154
00:18:42,560 --> 00:18:44,440
Like, that's the kind of platform that I use.

155
00:18:45,180 --> 00:18:55,600
And having, as you were saying, the brand name, the principles, but then actively, like, and this gets into the area that my team works in and that you work in a bit, right?

156
00:18:55,600 --> 00:19:01,620
But having, like, you know, you need to, like, have that thought leadership, right?

157
00:19:01,640 --> 00:19:21,420
Which I think often leads to another thing that I see in most all, let's just be super hyperbolic and say all, you know, 90, you know, an SLA is worth 99.9999% of organizations is they have at least one, if not multiple, let's call them platform advocates.

158
00:19:21,840 --> 00:19:37,140
And this is, like, a full-time person whose job is to not only do, like, training and workshops, but they are supposed to, like, be enthusiastic about the platform, right?

159
00:19:37,140 --> 00:19:45,580
Like, like, all these, like, thought leaders and people out there that you see talking about various technologies and things like that, right?

160
00:19:45,580 --> 00:19:53,200
Like, their job is to, like, with enthusiasm, show people why the platform is good and how it can help them out.

161
00:19:53,940 --> 00:20:04,740
And, you know, oftentimes, like, I remember talking with people at BT or, you know, formerly British Telco or Telcom, like, there was a person who full-time did this.

162
00:20:04,820 --> 00:20:14,980
And they would travel around to the various offices and, you know, you would have, like, a meeting with, like, you know, it could be anywhere from, like, six to 20 people, if not more, right?

163
00:20:15,000 --> 00:20:18,120
And you're just kind of doing a road show and presenting things.

164
00:20:18,120 --> 00:20:35,460
And, you know, they do a similar thing where they're always thinking about how can we be an advocate for this and explain it to people.

165
00:20:35,520 --> 00:20:48,640
And then it gets to another aspect of the as a product, which is, and this is where it's fun to be a vendor and talk about things, is, like, when you're developing a product, a software, an IT product, you have this role called a product manager.

166
00:20:49,280 --> 00:21:01,140
And part of what a product manager, a product manager's job, there's lots of things, but the most important job for a product manager is to figure out for this release, what features are we going to work on and release?

167
00:21:01,140 --> 00:21:11,700
And there's all sorts of criteria and inputs that go into that, like, one of the inputs, as a business, one of the most important inputs is talking to your salespeople to see what people want to buy.

168
00:21:12,320 --> 00:21:20,760
But, you know, another very important input is actually talking to your customers and getting feedback about what works and doesn't work.

169
00:21:20,760 --> 00:21:36,040
And that's where a role of an advocate also is valuable, because the reason they're called an advocate is, and they're often called a developer advocate, is because they're supposed to be advocating for developers and to them, I guess.

170
00:21:36,560 --> 00:21:47,560
But, you know, so as these advocates go around and they work closely with the customers of the platform, the developers, hopefully what they're gathering up is like, oh, I talked to this person and they said that and this person said that.

171
00:21:47,560 --> 00:21:56,900
And you bring that back to the product manager of the platform, and it's another type of input that allows them to basically prioritize the backlog to figure out what they're working on.

172
00:21:57,220 --> 00:22:06,280
But, you know, I mean, I think all of those things are a large part of, like, what it means to do marketing for a platform, right?

173
00:22:06,360 --> 00:22:22,440
And I think it's worth going over those things, because again, when I was part of the traditional IT management world, which I think still largely exists in this way, like, people wouldn't say you didn't have those goals,

174
00:22:22,440 --> 00:22:29,460
but the way you would achieve them would be more with, like, a knowledge base, or like a center of excellence, right?

175
00:22:29,460 --> 00:22:43,620
It would be more of a, more of like a lecture, here's the way that you do it, kind of academic way of doing stuff, rather than, like, going out into the field and thinking about how you apply marketing to things, right?

176
00:22:43,620 --> 00:22:53,740
It's a lot, it's a lot more engineering, and I don't know, I have a lack of words for it, but it's a different way of thinking about how you're marketing than in the traditional way of doing things.

177
00:22:54,880 --> 00:23:03,620
Yeah, and it could be quite, like you said, quite dry and quite kind of academic when you do it that way.

178
00:23:03,760 --> 00:23:13,260
I do remember being part of organizations that had centers of excellence, for example, in service orientation or, you know, things of that nature.

179
00:23:14,040 --> 00:23:30,560
And, yeah, it's a very different way of thinking from the more proactive advocacy route, where, you know, you can't just publish a paper on a topic, like, I don't know, XML parsing, using XSLT.

180
00:23:30,560 --> 00:23:58,200
You actually have to have, you know, the ability to talk about that in coding terms, in terms of what it actually means to apply that idea or to, you know, use that idea in a practical way with practical examples, but also gathering information about where that breaks down, you know, which parts of it don't work as well as they should, and how could it work better and all that sort of stuff.

181
00:23:58,200 --> 00:24:00,940
So, yeah, it's definitely, I've seen plenty of that, yeah.

182
00:24:01,220 --> 00:24:04,520
And then there's two other things in my, that I wanted to go over.

183
00:24:05,020 --> 00:24:24,260
And one of them is, well, one of them is another aspect of marketing that I think is important, that I like to emphasize, because I think people would assume they're doing it, but not to the degree that I think is required to do to be successful.

184
00:24:24,260 --> 00:24:27,660
And that is thinking about conferences that you have.

185
00:24:27,880 --> 00:24:38,480
And what I mean by that, and this is one of those instances where I think it's very literal, like people should do literally the following until they are adept at it enough to figure out to do otherwise.

186
00:24:38,480 --> 00:24:42,080
It's the old, you know, you got to know the rules in order to break the rules situation.

187
00:24:42,080 --> 00:24:58,520
And that is, like every quarter, your platform group, and hopefully more than just your platform group, but it also should be inclusive of the group who is like working on applications and wants to do your software better.

188
00:24:58,600 --> 00:25:06,580
Who wants to actually like have your software be strategically part of the business and not just like some projects that they're, they're delivering.

189
00:25:06,580 --> 00:25:16,440
But anyways, like you want to have a conference every quarter and like, it's great if you have the will and the budget for it to actually be in person.

190
00:25:16,440 --> 00:25:19,540
Right. So in large organizations, there's always multiple sites.

191
00:25:19,540 --> 00:25:28,160
Right. And a very good thing to do if you can is to have this conference rotate at all of your major big sites globally and then broadcast it online.

192
00:25:28,280 --> 00:25:39,280
Right. But what you do at this conference, and again, this is, this is where it's this, this type of marketing that you learn at a tech company is you do a couple of things.

193
00:25:39,280 --> 00:25:56,920
Uh, one, the first thing that you want to do is you're just raising awareness that the thing exists, right? That, that it is there, which is easy to be dismissive about, but in a large organization, there's a lot of things and you have to really, uh, spend a lot of time telling people it exists.

194
00:25:57,260 --> 00:26:06,720
And then the, the, the next thing that you want to do is you want to build up trust that the platform is good and that people will benefit from it.

195
00:26:06,780 --> 00:26:21,140
And the way that you do that, uh, and this is what us tech vendors know is it's great to, to have people like Coté and Ben make claims and tell you why something is awesome, but it's even better if you have actual customers going over how it worked.

196
00:26:21,140 --> 00:26:39,060
And so in this instance, that means finding developers who have used the platform and just having them present everything, not everything, but you know, not only the good, but, but also the bad, just go over the story of how they use the platform, what they learned from it and what worked and didn't work and what their recommendation was.

197
00:26:39,060 --> 00:26:50,880
Because what you're doing here is you're building up, uh, the best type of marketing, at least according to the Seth Godin's and the clue train people of the world is, uh, your, your word of mouth marketing.

198
00:26:51,000 --> 00:26:51,400
Right.

199
00:26:51,440 --> 00:27:03,020
And that's the best type of marketing because one, uh, well, there's all sorts of reasons, but it's just, if you think about the dynamics of it, right, what you're trying to do is win over developers to use your technology.

200
00:27:03,020 --> 00:27:07,220
And I'll, and I'll get to why that even exists in the second, the second, the second last thing I wanted to go over.

201
00:27:07,880 --> 00:27:21,440
Uh, and really they're going to trust other developers, their peers the most about what works because hopefully because they trust and respect them, or at least don't think they're bozos.

202
00:27:21,440 --> 00:27:28,180
Um, and then two, because they have a similar, they have the same job as them.

203
00:27:28,180 --> 00:27:34,040
And so they can start to ask them very insider expert questions like, well, what about this thing?

204
00:27:34,040 --> 00:27:35,220
And what do you do when this happens?

205
00:27:35,220 --> 00:27:36,280
And did you think about that?

206
00:27:36,280 --> 00:27:41,160
And so like, you know, those are the people you want experts selling to other experts.

207
00:27:41,760 --> 00:27:42,680
So you do that.

208
00:27:43,440 --> 00:27:43,840
Yeah.

209
00:27:43,920 --> 00:27:44,120
Sorry.

210
00:27:44,260 --> 00:27:46,220
Well, they have like a shared domain, don't they?

211
00:27:46,260 --> 00:27:52,000
And I think, uh, I've, I've heard it, uh, termed social proof.

212
00:27:52,200 --> 00:27:54,020
You know, they're looking for social proof.

213
00:27:54,240 --> 00:27:58,600
Others in the same peer group that are doing the same things with the same technology.

214
00:27:59,440 --> 00:28:04,760
It all helps to reinforce the idea that it's a golden path and that it's good.

215
00:28:05,100 --> 00:28:05,200
Right.

216
00:28:05,380 --> 00:28:05,780
Absolutely.

217
00:28:06,040 --> 00:28:11,180
And, and, you know, to, to, to reinforce, and then, so the third thing you have at the conference

218
00:28:11,180 --> 00:28:13,100
is just educational content, right?

219
00:28:13,100 --> 00:28:16,320
Like just sort of, uh, training content.

220
00:28:16,320 --> 00:28:19,860
Like you're, you know, obviously your advocate people would be there and they would go over

221
00:28:19,860 --> 00:28:24,020
like, you know, now let's go over how to deploy to the platform.

222
00:28:24,020 --> 00:28:24,300
Right.

223
00:28:24,300 --> 00:28:26,640
Like, so now you have an application running on the platform.

224
00:28:26,720 --> 00:28:31,140
How do you gather the, what, to whatever degree we want of the, you build it, we run

225
00:28:31,140 --> 00:28:31,300
it.

226
00:28:31,300 --> 00:28:34,880
Like, uh, what's the word for it?

227
00:28:35,040 --> 00:28:38,520
Uh, riddle of, of, of, uh, cloud philosophy.

228
00:28:38,880 --> 00:28:43,780
Like how, what does it mean to like, look at your application and production?

229
00:28:43,780 --> 00:28:45,820
How do you manage like API gateways?

230
00:28:46,080 --> 00:28:48,600
How do you integrate with our weird certificate system?

231
00:28:48,600 --> 00:28:51,920
Just straight up training stuff, uh, that people will be interested in.

232
00:28:52,000 --> 00:28:56,340
And then of course, you know, the benefit of an in-person conference and actually making

233
00:28:56,340 --> 00:28:59,220
the time for it is then you have a lot of conversation afterwards.

234
00:28:59,220 --> 00:28:59,700
Right.

235
00:28:59,700 --> 00:29:07,120
And what I've observed firsthand in a lot of these, um, events is that it's that unscheduled

236
00:29:07,120 --> 00:29:13,240
time that is most valuable for like the team leads and the architect types, right?

237
00:29:13,580 --> 00:29:19,700
Because the team leads and the architect types, the ones who are like, um, who are not individual

238
00:29:19,700 --> 00:29:24,540
developers, but worrying about how a team of developers or how several teams of developers

239
00:29:24,540 --> 00:29:25,620
will be operating.

240
00:29:25,620 --> 00:29:30,720
I mean, they're, they're programmers of the system of people of the meatware stack.

241
00:29:30,860 --> 00:29:35,640
And they often have a lot of questions, right?

242
00:29:35,740 --> 00:29:38,960
And their questions are not really things that you can gather in a presentation.

243
00:29:38,960 --> 00:29:43,020
They need to be more of a discussion about that are very particular, how they're doing things.

244
00:29:43,120 --> 00:29:49,340
So again, like having those quarterly conferences, hopefully in person where you kind of go, you

245
00:29:49,340 --> 00:29:52,740
go over those four things, I think is a very valuable.

246
00:29:52,740 --> 00:29:58,260
And then the fourth thing to consider from a marketing standpoint is the reason all of this

247
00:29:58,260 --> 00:30:05,680
is important is because whether you accept it or not, especially in size, large organizations,

248
00:30:05,680 --> 00:30:08,680
you have a lot of competition for a platform, right?

249
00:30:08,820 --> 00:30:13,300
So the first type of competition you have is doing nothing, right?

250
00:30:13,340 --> 00:30:17,420
Like not changing to a new platform, just keeping doing what you're doing.

251
00:30:17,880 --> 00:30:24,100
Um, and it could be as, as I think is the case very frequently nowadays, it could be because

252
00:30:24,100 --> 00:30:25,200
that platform works.

253
00:30:25,520 --> 00:30:30,320
And it's very frequently the case when you're talking about mainframe stuff that like over

254
00:30:30,320 --> 00:30:34,920
the decades, we've already modernized and moved a lot of stuff off of mainframes, right?

255
00:30:34,940 --> 00:30:39,620
So as you, as you start to chip away and try to modernize more and more stuff on a mainframe,

256
00:30:39,760 --> 00:30:44,940
like it has a Darwinian nature of usefulness to it, right?

257
00:30:45,000 --> 00:30:47,860
That if, if an application, this is not universally true.

258
00:30:47,940 --> 00:30:52,160
There are still many applications, many, there's still a significant amount of services and

259
00:30:52,160 --> 00:30:56,100
applications that exist on a mainframe that should be modernized and have good reasons

260
00:30:56,100 --> 00:31:02,120
for it, especially in large government, uh, agencies and some financial organizations that

261
00:31:02,120 --> 00:31:04,660
haven't really like been keeping up with things.

262
00:31:05,160 --> 00:31:10,220
However, like a lot of those things that exist on mainframes now, like it, they've survived

263
00:31:10,220 --> 00:31:12,100
and it's because they work well.

264
00:31:12,100 --> 00:31:16,840
But so you have that kind of like mentality of just doing what you're currently doing.

265
00:31:16,840 --> 00:31:20,900
But the, and then there's also, as I was kind of mentioning with JP Morgan Chase and Mercedes

266
00:31:20,900 --> 00:31:23,240
Benz, they have multiple platforms, right?

267
00:31:23,240 --> 00:31:24,340
For various reasons.

268
00:31:24,340 --> 00:31:28,680
And so you're competing against other platforms, but the biggest competition that you're probably

269
00:31:28,680 --> 00:31:32,160
having is competing with the developers themselves.

270
00:31:32,160 --> 00:31:37,180
And you compete with them in two areas, one, and I, I've joked about this kind of throughout

271
00:31:37,180 --> 00:31:43,260
you're competing with developers who are like, Hmm, don't think you're smart enough to listen

272
00:31:43,260 --> 00:31:44,960
to, right.

273
00:31:45,140 --> 00:31:48,360
And, and, or, you know, they might've been like burned in the past.

274
00:31:48,460 --> 00:31:53,160
They might be annoyed about things, but they're sort of like, you know, they don't, they're

275
00:31:53,160 --> 00:31:57,260
not really interested in using your platform because they don't, they just assume it's going

276
00:31:57,260 --> 00:31:57,880
to be bad.

277
00:31:58,400 --> 00:31:59,580
And platform skeptics.

278
00:31:59,840 --> 00:32:00,700
Yeah, there you go.

279
00:32:00,700 --> 00:32:07,460
And, and then the, what's, what's, what usually is holding hands with that is that these developers

280
00:32:07,460 --> 00:32:12,880
will be building their own platforms or aligned with other people that are building things,

281
00:32:12,880 --> 00:32:19,340
or at the very least, they won't see the value in a standardized centralized platform as, or

282
00:32:19,340 --> 00:32:24,080
as we used to call it an opinionated platform, or as we used to even call it longer ago, a platform

283
00:32:24,080 --> 00:32:24,780
as a service.

284
00:32:24,780 --> 00:32:25,120
Right.

285
00:32:25,620 --> 00:32:30,180
And so, you know, that's the kind of competition that, that, that you're dealing with.

286
00:32:30,180 --> 00:32:34,580
And why, for all the benefits you're going to have with the platform, I think it's important

287
00:32:34,580 --> 00:32:37,340
to think about how do we deal with that competition.

288
00:32:37,340 --> 00:32:37,600
Right.

289
00:32:37,620 --> 00:32:42,820
And especially the last type, because the last type is this competition of not believing

290
00:32:42,820 --> 00:32:45,440
in the idea of a platform.

291
00:32:45,440 --> 00:33:01,000
And then, like, you're going to have to go in there and, like, do, and do the right thing

292
00:33:01,000 --> 00:33:02,640
with it, essentially.

293
00:33:03,840 --> 00:33:04,240
Yeah.

294
00:33:04,280 --> 00:33:07,780
Again, it's a super expensive choice, that last one, isn't it, as well.

295
00:33:08,000 --> 00:33:08,120
Yeah.

296
00:33:08,120 --> 00:33:10,820
There's other, there's other drawbacks with that.

297
00:33:11,180 --> 00:33:17,300
And, and you end up, you know, arguing on the head of a pin about very specific technologies,

298
00:33:17,520 --> 00:33:19,560
you know, oh, I prefer this one.

299
00:33:19,800 --> 00:33:21,440
Oh, the platform's got that one.

300
00:33:22,300 --> 00:33:24,560
It's, therefore, I'll just build my own, you know.

301
00:33:25,440 --> 00:33:29,180
But people often underestimate just how expensive that is, I think.

302
00:33:30,800 --> 00:33:31,480
So, yeah.

303
00:33:31,540 --> 00:33:39,600
That sort of alignment is helpful if you can, if you, if you can reduce the skepticism and,

304
00:33:39,600 --> 00:33:44,340
and show the value and bring folks along on that journey.

305
00:33:44,340 --> 00:33:47,800
It's very, it's very cost effective as well, right?

306
00:33:47,880 --> 00:33:52,560
There's a, there's a, there's a bottom line, uh, quotient to this.

307
00:33:53,960 --> 00:33:54,320
Exactly.

308
00:33:54,800 --> 00:33:55,200
Exactly.

309
00:33:55,300 --> 00:33:59,000
And so, so, you know, the reason we're talking about all this is, is you and I were, we're,

310
00:33:59,040 --> 00:34:01,900
we're catching up a little bit and we realized that, like, you know, I've, I've spent a lot

311
00:34:01,900 --> 00:34:06,980
of time, obviously, uh, either that I'm really good at just making stuff up as I talk, which

312
00:34:06,980 --> 00:34:12,120
maybe is about 15% of my abilities and pre-trained.

313
00:34:13,880 --> 00:34:14,240
Exactly.

314
00:34:14,780 --> 00:34:17,060
But, you know, I spend a lot of time thinking about that marketing thing.

315
00:34:17,060 --> 00:34:20,440
And I, and I think, I think recently you've been spending a lot of time thinking about,

316
00:34:21,000 --> 00:34:26,400
okay, so let's say we get the chance to like get in front of the developers every day and

317
00:34:26,400 --> 00:34:27,700
they actually want to use it.

318
00:34:27,940 --> 00:34:35,640
Like, what is the, I hesitate to say the word marketing, but what is the usability of

319
00:34:35,640 --> 00:34:38,380
the platform, the UX, the design of the platform?

320
00:34:38,840 --> 00:34:43,420
Uh, like what are the components of that so that we make it, uh, easier for them to use

321
00:34:43,420 --> 00:34:45,280
and to make it more successful at them?

322
00:34:45,380 --> 00:34:47,600
So what, what, what have you been thinking about in that area?

323
00:34:47,600 --> 00:34:52,600
Yeah, I've been working on a, on a few bits and pieces, but I liked what you said earlier

324
00:34:52,600 --> 00:35:00,140
about, you know, the, the thing that the, your, your opinion is that folks perhaps under cook

325
00:35:00,140 --> 00:35:06,180
the whole, the whole, um, conference idea, you know, actually getting people to confer about

326
00:35:06,180 --> 00:35:08,940
what, what it is that you're building and get that shared.

327
00:35:09,160 --> 00:35:15,660
The thing that, uh, that I have a bit of a bugbear about is, um, actually documenting what

328
00:35:15,660 --> 00:35:16,220
you have.

329
00:35:17,100 --> 00:35:18,000
Right, right, right.

330
00:35:18,000 --> 00:35:25,200
So the folks, because documentation is 24, seven, three, six, five self-service, right?

331
00:35:25,280 --> 00:35:30,720
So, so if your principle is run around sort of self-service, then having good documentation

332
00:35:30,720 --> 00:35:37,340
about it all is really important because you don't need the advocate to be there 24, seven.

333
00:35:37,340 --> 00:35:39,740
You can't have an advocate there 24, seven.

334
00:35:39,860 --> 00:35:44,600
You know, you can't have that sort of that care and assistance all the time.

335
00:35:44,600 --> 00:35:50,060
So you need a fallback plan and the fallback plan is, okay, how do you, you know, you actually

336
00:35:50,060 --> 00:35:55,600
have to create content around what this thing actually, you know, does.

337
00:35:55,600 --> 00:36:01,480
And it's, it's not the same as technical documentation, you know, press button X and then do button Y

338
00:36:01,480 --> 00:36:03,700
and then Bob's your uncle, here's your thing.

339
00:36:04,280 --> 00:36:10,760
It's not just the sort of technical documentation, which of course you sort of need, but it's also

340
00:36:10,760 --> 00:36:17,560
the, the sort of questions around the platform, you know, like why, why would I use this exactly?

341
00:36:17,560 --> 00:36:19,800
And what benefit is there in it for me?

342
00:36:19,860 --> 00:36:26,020
And how should I think about this particular problem in a, in a, in a platform, uh, manner?

343
00:36:26,020 --> 00:36:31,320
So, so I've been sort of working on, I do a lot of work with, uh, backstage cause we have

344
00:36:31,320 --> 00:36:37,620
backstage, um, GUI as part of some of our products, uh, uh, terms of application platform,

345
00:36:37,760 --> 00:36:38,920
uh, terms of application service.

346
00:36:39,820 --> 00:36:45,640
Uh, so we, we, you know, that's a, for folks who haven't seen it before, go check it out.

347
00:36:45,640 --> 00:36:48,380
Um, backstage.io is the website.

348
00:36:49,280 --> 00:36:57,040
Um, but basically that gives you, uh, uh, uh, a place, you know, a website where all the developers

349
00:36:57,040 --> 00:37:01,060
can come together and share information about their context.

350
00:37:01,060 --> 00:37:06,120
You know, we were talking about context earlier is things like, okay, how is our organization

351
00:37:06,120 --> 00:37:11,040
structured and how do they, what applications do we have and how do they relate to each other

352
00:37:11,040 --> 00:37:15,660
and which ones are integrated with which other ones and how are they integrated and where do

353
00:37:15,660 --> 00:37:16,140
they run?

354
00:37:16,240 --> 00:37:17,380
Do they run on Cates?

355
00:37:17,500 --> 00:37:19,160
Do they run on cloud foundry?

356
00:37:19,280 --> 00:37:21,420
Where do they run on, you know, bare metal?

357
00:37:21,580 --> 00:37:22,920
Where are they exactly?

358
00:37:22,920 --> 00:37:31,600
So it's starting to bring together lots of information about the context of developing so that you

359
00:37:31,600 --> 00:37:33,240
can discover more quickly.

360
00:37:33,600 --> 00:37:36,680
You know, you can discover what's going on in other teams more quickly.

361
00:37:36,880 --> 00:37:40,040
You can discover the parts that are relevant to you more quickly.

362
00:37:40,760 --> 00:37:43,260
It lets you sort of create stuff as well.

363
00:37:43,420 --> 00:37:49,320
You know, you can create, for example, nice documentation spaces where you can talk about

364
00:37:49,320 --> 00:37:55,540
your application and have folks be able to self-serve information about what it is that's

365
00:37:55,540 --> 00:37:56,020
on offer.

366
00:37:56,200 --> 00:37:57,780
There are APIs in there.

367
00:37:57,860 --> 00:37:59,780
So you've got API listings and things.

368
00:38:00,000 --> 00:38:06,420
So it's really useful and it does bring developers together into a place where, um, they can,

369
00:38:06,420 --> 00:38:11,900
uh, you know, do their work more productively, but also understand, you know, what's around

370
00:38:11,900 --> 00:38:12,120
them.

371
00:38:12,120 --> 00:38:14,220
So, so I've been working a lot on that recently.

372
00:38:14,980 --> 00:38:20,380
Um, we, we have, uh, like I said, we have a couple of products, uh, that, that use, um,

373
00:38:20,380 --> 00:38:21,400
the backstage portal.

374
00:38:21,400 --> 00:38:27,600
So I've been working on things like, um, service catalogs, uh, um, which basically tell, sorry,

375
00:38:27,600 --> 00:38:32,920
software catalogs, which basically tell you about, um, what is all the software that we

376
00:38:32,920 --> 00:38:33,240
have?

377
00:38:33,300 --> 00:38:36,160
Like what, what are the software applications that we're working on?

378
00:38:36,160 --> 00:38:38,540
And how do they relate to each other?

379
00:38:38,540 --> 00:38:44,920
So it handles things like relationships between individual pieces and components of that software

380
00:38:44,920 --> 00:38:51,940
relationships to APIs that are offered relationships to the people that actually code this stuff

381
00:38:51,940 --> 00:38:58,180
and look after it on a day-to-day basis, either operationally or from a, from a sort of a code

382
00:38:58,180 --> 00:39:00,520
perspective, which is really handy.

383
00:39:00,520 --> 00:39:05,300
If at three in the morning, you need to find out who looks after this thing and can they help

384
00:39:05,300 --> 00:39:10,760
us with this vulnerability that we're seeing, you know, so lots of interesting stuff in software

385
00:39:10,760 --> 00:39:12,220
catalogs, I think can be done.

386
00:39:12,220 --> 00:39:14,060
And it's, like I said, it's 24 seven.

387
00:39:14,060 --> 00:39:22,820
So folks can just go and self-serve and then related to that also is, um, another feature, um, called

388
00:39:22,820 --> 00:39:31,440
tech docs, which allows you to sort of document in a rich sort of websitey format information about

389
00:39:31,440 --> 00:39:35,820
your, um, about your software applications or about your platform.

390
00:39:35,820 --> 00:40:05,220
And this is where I think it perhaps is underutilized, you know, I think a lot of teams articulate very well, the software that they're working on, but for platform teams, platform engineering teams, that's a good place where you could actually document the platform itself, say what the platform is and why you put it together and how it was put together and what pieces are in there and, um, how they, uh, relate to each other.

391
00:40:05,220 --> 00:40:19,420
And also getting started information, stuff that's not necessarily in regular technical documentation, but is more about, you know, why should you be interested in this?

392
00:40:19,520 --> 00:40:23,160
It'd be a really good question to answer for someone visiting for the first time.

393
00:40:23,160 --> 00:40:27,900
Like if you're a platform advocate and you go out there and you say, Oh, you should check out our platform.

394
00:40:28,020 --> 00:40:28,800
Here's a URL.

395
00:40:29,320 --> 00:40:35,080
Like it'd be really nice if the landing page for that URL is like, Hey, this is our platform.

396
00:40:35,080 --> 00:40:47,840
And this is why we think you should like it, you know, and this is the sort of stuff that it can deliver for you rather than sort of, you know, some, some cold login screen or, or some, you know, baffling information.

397
00:40:47,840 --> 00:40:50,660
Uh, that that's, that's, that's too, uh, low level.

398
00:40:50,660 --> 00:41:05,600
So, so I think some of these features are underutilized, you know, having a good landing page, it's marketing and it, it really helps to, uh, help people get comfortable more quickly with your platform.

399
00:41:05,820 --> 00:41:10,420
And therefore actually consume it because that's what you want at the end of the day.

400
00:41:11,260 --> 00:41:17,000
You mentioned at the start of this, uh, the recent platform con, you're absolutely right.

401
00:41:17,820 --> 00:41:25,120
Presentation after presentation was all about, okay, I've built this platform, but how the hell do I get people to consume it?

402
00:41:25,500 --> 00:41:28,640
And because I, because I'm, I'm great at building it.

403
00:41:28,640 --> 00:41:30,960
I've answered all the technical questions.

404
00:41:31,380 --> 00:41:32,980
It's an awesome platform.

405
00:41:32,980 --> 00:41:37,180
You know, it's got all the bells and whistles and everything that everyone wanted is in there.

406
00:41:37,420 --> 00:41:39,800
And still I've got 5% usage.

407
00:41:39,800 --> 00:41:53,720
So why, you know, how do I make them go through the process of getting interested in a platform and actually, you know, first of all, kind of trying it, but hopefully ultimately respecting it.

408
00:41:53,720 --> 00:41:56,580
And then participating in improving it.

409
00:41:57,500 --> 00:41:57,940
Yeah.

410
00:41:58,060 --> 00:42:07,460
You know, that, that, that, that, well, first of all, that's, that's a great list of everything there that there was, uh, I'm going to have to go back and, uh, uh, list those out at some point.

411
00:42:07,460 --> 00:42:13,280
But I, I think on this last point, this is another one of those, like, you know, life hacks.

412
00:42:13,420 --> 00:42:16,260
I wouldn't, let's call it enterprise life hacks.

413
00:42:16,380 --> 00:42:30,940
Not, not like your everyday life, which is, uh, you know, the, the, the word, whenever someone who's, uh, nowadays at a vendor and again, public cloud or, or software vendor, when they hear the word consumption, that means a very precise thing.

414
00:42:30,940 --> 00:42:40,500
Not the sickness, of course, that was a problem back in the 1800s and whatnot, but what, what, what they know that means is the future success of my business.

415
00:42:40,680 --> 00:42:41,080
Right.

416
00:42:41,080 --> 00:42:49,720
Uh, because what, what you want to do in, in larger enterprise sales nowadays, uh, you know, you want to sell on a subscription versus a perpetual license.

417
00:42:49,940 --> 00:42:55,400
And so what you're very concerned with is you want to sell as big a deal as possible for as many years right away.

418
00:42:56,780 --> 00:42:58,540
There's good and bads about why you do this.

419
00:42:58,700 --> 00:43:00,320
We'll, we'll traipse over all of that.

420
00:43:00,380 --> 00:43:00,880
It's another thing.

421
00:43:00,980 --> 00:43:08,440
If you really want to get your software, your vendor, people thinking, ask them about this and they'll be up all night explaining both sides of it, but you sell a big thing.

422
00:43:08,440 --> 00:43:16,080
And what you want is at the end of that two or three year term, you want the person you sold it to, to not only renew it, but to buy more of it.

423
00:43:16,080 --> 00:43:22,460
And so what that means is that you need them to consume that product and not have it be as we used to call it shelfware.

424
00:43:22,580 --> 00:43:22,920
Right.

425
00:43:23,280 --> 00:43:31,080
So this has sprung up a whole realm of, uh, a whole new, like, um, what do you call it?

426
00:43:31,400 --> 00:43:34,160
Function in vendors called customer success.

427
00:43:34,460 --> 00:43:44,260
And what customer success does, they're not like professional services, people who help you set up and run something, but there's someone who works with the big customers to make sure they're actually using the product.

428
00:43:44,580 --> 00:43:45,020
Right.

429
00:43:45,020 --> 00:43:53,300
And, and that they're using an increasing amount more of it so that when the contract ends again, the customer renews it and they buy a little bit more.

430
00:43:53,400 --> 00:43:53,600
Right.

431
00:43:53,600 --> 00:43:59,900
And some of the best, uh, vendors out there in the world are masters at this whole thing, right?

432
00:43:59,920 --> 00:44:06,900
They not only have technology that's good, but they make sure to manage that complete life cycle, uh, of, of what's going on there.

433
00:44:06,900 --> 00:44:10,340
So we in the vendor space know all about that.

434
00:44:10,380 --> 00:44:20,320
So this is another area where, uh, you know, you could call up your vendor friends, have them buy you a free steak dinner or lunch and teach you all about this kind of stuff.

435
00:44:20,320 --> 00:44:29,760
And I think, you know, putting, putting, putting a lot of what I was saying, like, you know, uh, in, in, in, in the bowls that you are, uh, spinning up there.

436
00:44:30,040 --> 00:44:42,160
Like what that means has been was saying is you do think a lot on this platform team about how do I get people developers to start using the platform to use more and more of it.

437
00:44:42,160 --> 00:44:52,360
Now you've got to temper that a little bit, if you're not a vendor, because your goal isn't to maximize the expense, right?

438
00:44:52,360 --> 00:44:59,600
Like, so at some point you don't actually need to have them use more and more, but you want them using it and you want to focus on consumption.

439
00:44:59,600 --> 00:44:59,820
Right.

440
00:44:59,820 --> 00:45:09,040
To some extent, not to some extent, like that I've noticed over the years that that becomes a metric that people track on the platform team is how much usage do we have of it.

441
00:45:09,200 --> 00:45:21,560
Right. Not just to, to a point you were kind of making, uh, Ben, you don't just track the metric of, we delivered the service and the service has uptime and the service is meeting the budgetary goals that we have.

442
00:45:21,560 --> 00:45:25,860
You also want to track the metric of our people using it, right?

443
00:45:25,920 --> 00:45:29,340
Like is, and are they using it more and more each time?

444
00:45:29,340 --> 00:45:39,040
Um, and, and, and once you do start tracking that metric that has some interesting, uh, effects, like, like a while ago, uh, uh, uh,

445
00:45:39,200 --> 00:45:51,560
there was a presentation that, um, uh, Tony, uh, at the Home Depot at the time, now he, he works with us, but he was saying when they were introducing, uh, uh, a platform, their cloud foundry based platform back then, the pivotal cloud foundry.

446
00:45:51,560 --> 00:45:59,580
Now the Tonsu application service, uh, that they were tracking consumption and they had noticed that like developers weren't using very much of it.

447
00:46:00,140 --> 00:46:07,700
So again, from this very product mentality thing, uh, they, they, you know, they went and talked to them, you know, big mind blowing event there.

448
00:46:07,800 --> 00:46:11,440
They went and talked to the developers and asked them what the deal was.

449
00:46:11,440 --> 00:46:17,080
And what they found out is that the developers, like they thought it was too expensive and what that meant.

450
00:46:17,080 --> 00:46:19,700
So that means something different inside an enterprise.

451
00:46:19,700 --> 00:46:26,040
What that means is that the internal funny money of it is more expensive.

452
00:46:26,040 --> 00:46:34,600
So they had, it wasn't like at some point it becomes kind of actual money, but, but inside large organizations, there's also like a lot of like internal accounting,

453
00:46:34,600 --> 00:46:40,220
which is just like a number that appears in one cell in a spreadsheet versus another cell in a spreadsheet.

454
00:46:40,220 --> 00:46:40,640
Right.

455
00:46:40,660 --> 00:46:43,260
And it's literally like copy paste accounting.

456
00:46:43,480 --> 00:46:43,780
Right.

457
00:46:44,040 --> 00:46:48,920
And so like realizing that like Tony and the team were like, Oh, right.

458
00:46:49,200 --> 00:46:56,720
Well, our goal is to have people use this because when they use it, we know they will be running more efficiently and therefore our business will be running more efficiently.

459
00:46:57,280 --> 00:46:58,940
So what if we don't charge them?

460
00:46:59,240 --> 00:46:59,680
Right.

461
00:46:59,680 --> 00:47:03,820
Cause we're already, we're like, it's all just silly money anyways.

462
00:47:04,180 --> 00:47:07,200
And sure enough, people started consuming it more and more.

463
00:47:07,200 --> 00:47:07,460
Right.

464
00:47:07,460 --> 00:47:12,580
And now, you know, towards the out years of it, once people see the value of it, they put the effort into it.

465
00:47:12,660 --> 00:47:14,440
This is another exciting tactic.

466
00:47:14,540 --> 00:47:22,120
Some vendors use, then it's easier to have them pay for it in real money or otherwise, because they're like, well, yes, of course it's valuable.

467
00:47:22,120 --> 00:47:22,500
Right.

468
00:47:22,520 --> 00:47:27,420
Like, and the amount of money that I'm going to pay for it is negligible for like the benefits that I get from it.

469
00:47:27,500 --> 00:47:33,800
But you only get to that point, as you were saying, Ben, if you are focused on consumption, right.

470
00:47:33,800 --> 00:47:40,560
Like focused on people actually using stuff, which immediately trickles down into what you were saying is like, all right, why are they not using it?

471
00:47:40,560 --> 00:47:48,600
Maybe because as you, as you said, there's a cold login page and so we should make it more hospitable and explain what it is and we need better documentation.

472
00:47:48,800 --> 00:47:49,160
Right.

473
00:47:49,200 --> 00:47:55,420
And so you have that goal of consumption and that drives all these things that you might be otherwise neglecting.

474
00:47:56,280 --> 00:47:56,680
Yeah.

475
00:47:56,700 --> 00:47:57,920
But I like what you're saying there.

476
00:47:58,000 --> 00:48:00,660
There should be no toll booths on the golden path.

477
00:48:01,080 --> 00:48:02,800
Oh, Hey, I like that.

478
00:48:03,260 --> 00:48:04,220
Type that one up.

479
00:48:04,220 --> 00:48:05,600
Put it in your threads.

480
00:48:05,600 --> 00:48:08,200
That's a talk title just waiting to happen, isn't it?

481
00:48:08,300 --> 00:48:11,580
Yeah, exactly.

482
00:48:12,300 --> 00:48:12,560
Yeah.

483
00:48:12,700 --> 00:48:30,460
And, and, you know, the other thing that I thought was like, that I'm, I'm really interested in what you're saying is, is you were, you, you, you were, you were starting to go over something new and different that this whole backstage thing is attempting to do.

484
00:48:30,460 --> 00:48:30,740
Right.

485
00:48:30,740 --> 00:48:41,560
Like, like, like what you were talking about is almost a good example of figuring out what the principles and the identity of your platform is.

486
00:48:41,560 --> 00:48:41,920
Right.

487
00:48:42,360 --> 00:48:49,060
And that is that, I mean, what you're going over is, is what backstage deal is.

488
00:48:49,060 --> 00:48:56,360
And, and another thing I'm always interested in, in technologies is how does, how does, how does, how does it want me to think?

489
00:48:56,500 --> 00:49:05,600
Because as a developer, especially one of the things that is like sort of half true that you're taught early on is you should always use the right tool for the job.

490
00:49:05,800 --> 00:49:09,860
And like, you should, you shouldn't like let the tool dictate how you do something, right?

491
00:49:09,860 --> 00:49:14,960
Like you've got to control the tools, which I think is, you find is right 30 to 40% of the time.

492
00:49:15,600 --> 00:49:15,960
Right.

493
00:49:16,740 --> 00:49:21,280
Because instead what you're often faced with is you have a tool, right?

494
00:49:21,280 --> 00:49:24,580
And you don't want to fall into the fallacy of when all you have is, is a hammer.

495
00:49:24,680 --> 00:49:25,640
Everything looks like a nail.

496
00:49:25,740 --> 00:49:31,220
Instead you want to think like, well, if I have a hammer, maybe I shouldn't go buy screws.

497
00:49:31,580 --> 00:49:31,980
Right.

498
00:49:32,000 --> 00:49:35,740
And, and you want to think like, how does this technology want me to think?

499
00:49:35,900 --> 00:49:38,840
And so for example, you're going over the backstage stuff.

500
00:49:38,840 --> 00:49:39,100
Right.

501
00:49:39,100 --> 00:49:53,560
And what, what, what I'm like detecting from what you're saying, and you can kind of decode this from how Spotify has talked about it originally is backstage wants you to be as microservice-y as possible, right?

502
00:49:53,700 --> 00:49:58,260
If you just have a bunch of monoliths, whatever that means.

503
00:49:58,260 --> 00:50:11,540
If you just have a bunch of teams of people working in your organization and they don't really ever have to coordinate with each other, let alone like share services, like backstage is like a lot of work to get kind of nothing.

504
00:50:12,040 --> 00:50:12,520
Right.

505
00:50:12,620 --> 00:50:20,100
Cause, but if you want to have all these teams coordinate more and know about each other, you want them using the services that they have.

506
00:50:20,240 --> 00:50:23,660
You've got like various components of your system that you need to find out.

507
00:50:24,160 --> 00:50:29,680
Like backstage, that's like how it wants you to think and therefore it's going to do something good for you.

508
00:50:29,680 --> 00:50:29,900
Right.

509
00:50:30,060 --> 00:50:43,420
And so I always think it's important, especially with something seemingly as simplistic as backstage, like to figure out like, what is the complex, the good complexity it wants me to have that it's trying to help me do.

510
00:50:43,560 --> 00:50:53,360
And I don't know, like what you're saying is making me think that it really like, it wants you to have that highly distributed microservice-y cloud native way of thinking about things.

511
00:50:53,360 --> 00:50:55,260
It's what it's really trying to help out with.

512
00:50:56,180 --> 00:50:56,620
Maybe.

513
00:50:57,000 --> 00:50:59,580
I don't know if I fully subscribe to that.

514
00:50:59,680 --> 00:51:07,760
Maybe our listeners can tell us what they think, but I think there's another case where I was an integrator for a long time.

515
00:51:07,900 --> 00:51:14,040
So I was working with lots and lots of third parties and the larger the organization, the more third parties you've got.

516
00:51:14,500 --> 00:51:14,660
Yeah.

517
00:51:14,820 --> 00:51:15,040
Yeah.

518
00:51:15,400 --> 00:51:25,480
And those that you need to know what those third parties offer and they sometimes need to know something about what you offer in order to make that integration happen.

519
00:51:25,560 --> 00:51:25,740
Right.

520
00:51:25,740 --> 00:51:41,860
If they've got APIs and there will be, you know, usually thousands of them out on the Internet somewhere, you know, you've got someone who specializes in fraud detection or someone who specializes in, you know, cleaning data in particular ways or whatever it might be.

521
00:51:41,860 --> 00:51:48,300
You could have someone where you order stuff, you know, an order API where you're ordering things from them or vice versa.

522
00:51:48,300 --> 00:51:49,380
They're ordering from you.

523
00:51:49,440 --> 00:51:57,800
You've got all this stuff, all these APIs that you're offering, regardless of whether it's microserviced or not.

524
00:51:58,780 --> 00:51:59,180
Yeah.

525
00:51:59,300 --> 00:52:09,200
No, I think I think that's a better way of putting it in the sense of if you're if you need to collaborate and use a bunch of other stuff, that's what it wants.

526
00:52:09,740 --> 00:52:10,140
Right.

527
00:52:10,200 --> 00:52:12,260
Like that is that is what it's valuable.

528
00:52:12,260 --> 00:52:18,700
And then and then you could, you know, the further potential refinement of that is and that's all the time.

529
00:52:19,600 --> 00:52:20,000
Right.

530
00:52:20,140 --> 00:52:25,120
And so like like like and your point would be of doing SI work is a good one.

531
00:52:25,120 --> 00:52:25,300
Right.

532
00:52:25,300 --> 00:52:27,820
Is like I mean, it's right there in the title integrator.

533
00:52:27,960 --> 00:52:28,340
Right.

534
00:52:28,360 --> 00:52:34,260
Like so if you're like pulling together a bunch of stuff like it's it.

535
00:52:35,720 --> 00:52:42,940
Maybe to put it another way is like it feels like a lot of the functionality built into backstage is working with other groups.

536
00:52:43,100 --> 00:52:53,580
Whereas there's plenty of like things that are like your project management documentation stuff that's more about what's the word intra group stuff.

537
00:52:53,580 --> 00:52:53,820
Right.

538
00:52:53,820 --> 00:52:58,240
Like helping your group inside, like keep track of what they're doing in their own stuff.

539
00:52:58,420 --> 00:53:02,700
Whereas like what's layered on in backstage is like, well, there's other people in the world.

540
00:53:02,700 --> 00:53:05,740
And so it's almost like the landing page for your project.

541
00:53:05,740 --> 00:53:06,080
Right.

542
00:53:06,080 --> 00:53:10,700
Like how do you apply all the stuff we've been talking about to your own the thing that this group is working on?

543
00:53:11,200 --> 00:53:14,000
Yeah, I think I think backstage goes very wide.

544
00:53:14,000 --> 00:53:18,560
And I think I think it's you hit the nail on the head when you said collaboration, really.

545
00:53:18,560 --> 00:53:20,420
That's sort of what it's all about.

546
00:53:21,120 --> 00:53:25,900
But it's got a great use case in in the whole self-service thing as well.

547
00:53:25,900 --> 00:53:35,780
Like if you're going to have a self-service button to create a database or whatever it might be, where better to put it than in the portal where all the developers go every day.

548
00:53:36,720 --> 00:53:45,880
So, you know, it provides you that focal point that otherwise is disparate in an enterprise.

549
00:53:46,000 --> 00:53:53,120
You know, it's in wikis or, oh, no, that was a Word document that lives on this drive that you need to get access to through the VPN.

550
00:53:53,860 --> 00:53:58,540
Or it's blown up and all over the place.

551
00:53:58,540 --> 00:54:01,860
And this starts to bring it together into a focal point.

552
00:54:01,980 --> 00:54:07,000
So, yeah, your documentation might be a little bit insular.

553
00:54:07,100 --> 00:54:09,820
It might just be about the component that you're working on.

554
00:54:09,880 --> 00:54:17,340
But perhaps don't underestimate how useful it is for someone else to be able to get access to that in the middle of the day.

555
00:54:17,340 --> 00:54:24,200
While you're, you know, tucked up in bed and they're on call trying to, you know, keep the lights on.

556
00:54:24,360 --> 00:54:36,220
So I think it's easy to, I think it's a useful thing for a very broad gamut of situations and problems.

557
00:54:36,960 --> 00:54:37,920
And I love it.

558
00:54:37,960 --> 00:54:38,840
I love working in it.

559
00:54:38,880 --> 00:54:40,260
It's a really nice place to be.

560
00:54:40,400 --> 00:54:44,540
It's well thought out and it has a lot of value to it.

561
00:54:44,600 --> 00:54:47,680
And I think it brings a lot of value to a platform.

562
00:54:47,860 --> 00:54:52,920
If your platform doesn't have something like this, maybe it's time to think about including it.

563
00:54:53,680 --> 00:54:53,880
Yeah.

564
00:54:54,200 --> 00:54:54,940
Yeah, yeah.

565
00:54:55,080 --> 00:54:57,820
No, that's interesting.

566
00:54:59,400 --> 00:55:02,320
Well, I think that's what we have to say on this topic, Ben.

567
00:55:03,960 --> 00:55:04,400
Okay.

568
00:55:04,620 --> 00:55:05,040
All right.

569
00:55:06,560 --> 00:55:07,480
I made it.

570
00:55:07,480 --> 00:55:10,460
I've unlocked level two, end of level Guardian now.

571
00:55:11,820 --> 00:55:13,740
We defeated the level boss or whatever.

572
00:55:16,060 --> 00:55:18,020
I managed to exhaust a Coté.

573
00:55:18,120 --> 00:55:18,360
Brilliant.

574
00:55:18,660 --> 00:55:18,880
Yeah.

575
00:55:19,040 --> 00:55:21,300
You know, sometimes you just got to be like, well, we're done.

576
00:55:21,720 --> 00:55:23,720
That's, we've wrapped it up.

577
00:55:24,720 --> 00:55:27,100
On that bombshell, maybe it's time to end.

578
00:55:28,960 --> 00:55:32,320
Well, as always, this has been a episode of Tanzu Talk.

579
00:55:32,420 --> 00:55:35,720
You know, maybe you watch the video of it or you're watching it.

580
00:55:35,720 --> 00:55:42,400
But we stream these live if you go to the VMware Tanzu channel, which is just go to YouTube and search for VMware Tanzu and you'll find it.

581
00:55:43,060 --> 00:55:45,460
And, you know, so you can watch the video of it.

582
00:55:45,500 --> 00:55:46,300
You can watch it live.

583
00:55:46,300 --> 00:55:55,400
Or if you're subscribed to the podcast and you listen to it there, you must know that you would go to TanzuTalk.com to find the podcast or just search around.

584
00:55:55,640 --> 00:55:58,520
If you'd like to listen to the podcast, you can search around there.

585
00:55:58,640 --> 00:56:02,320
And it's always nice if you want to help us promote and share this stuff.

586
00:56:02,740 --> 00:56:05,620
I think there was a lot of fun stuff in this episode that's useful.

587
00:56:05,920 --> 00:56:08,800
So you should share it with people and be like, we need that.

588
00:56:09,280 --> 00:56:15,820
And look, it ends because they just exhausted the topic, which is thrilling.

589
00:56:16,420 --> 00:56:18,800
So, yeah, we'll see everyone next time.

590
00:56:18,940 --> 00:56:19,380
Bye-bye.

591
00:56:19,380 --> 00:56:19,440
Bye-bye.

592
00:56:19,440 --> 00:56:19,540
Bye-bye.