Platform engineering is the discipline of designing and building toolchains and workflows that enable self-service capabilities for software engineering organizations in the cloud-native era.

Platform Engineering

Hey folks! I'm a Technical Program Manager looking for "marketing" tips for our internal platform. Did some of you give a name to the internal platform so that anyone in the company can start using the right glossary? Another question: how do you announce new features? (async messages in :slack:  / some written pages somewhere / videos)

hi!  I’m in the same role with an internal platform team as well. Happy to share what has worked for us. 
naming the internal platform- definitely! ours had a name from before I got there.. we do some fun ‘branding’ stuff like have a logo for it too 

originally we had all the docs about the platform in my team’s confluence space (the name of the team is not the same name as the platform and they own some other services too).  Later, we created a separate confluence space for the platform. 

I use confluence’s blog feature to write an ‘internal blog’ about the platform- user spotlights, feature announcements, etc and then share those links in relevant slack channels.. now that the platform has become pretty prominent I occasionally send engineering-wide emails 

once you’ve done marketing for a bit, it’s great to send a survey about the platform and ask “how do you remember hearing or learning about the platform?”  That helped me realize that word of mouth and a (very short) presentation we did inside of a company meeting, actually helped drive a lot of awareness. 

Hi <@U06TR4FBZ4G>, In my previous role as PM for DevEx, we were exploring backstage as the IDP. For naming the platform, I would go with the team's interests. My team was very much into pokemon, we even used to name our sprints with pokemon characters. so go with what your team might be receptive too, do some research, come up with a few suggestions and have the team vote on it. For Major launches, I usually attack all surface areas - emails, slack channels, Notion pages. Based on the audience, (business stakeholders versus engineering), i highlight whats relevant to them. If your team implemented a new service development framework, you can speak to how it improves your company's GTM velocity for new products. But if the audience is purely technical, go deeper and highlight the success metrics and how it alleviates developer toil. I also tend to make it fun to drive engagement. Add Gifs, Images that the audience can relate to. Hope this helps. Cheers!

#1 we always had names. I’ve managed few platforms past 5 years: avalaunch, starboost, comeet, starboost-for-ai
#2 I do not recommend a big doc in confluence to be public, create few pages for users - that’s all. But keep the change log and announcements on slack channel, you can also do a periodic meeting about Platform new features. I also do a demo every sprint for representatives of each team, so I can gather feedback 

&gt; you can also do a periodic meeting about Platform new features
yes sure, I was only thinking that probably in an ideal world users must be able to pull those kind of info from somewhere / source of truth (like a sort of obeya room) instead having to push those info every time, but I see your point :thankyou-1:

You can run roadshows and also talk about major
Achievements in company newsletters