With growing pains, <a href="https://en.wikipedia.org/wiki/Software_entropy">software entropy </a>kicked in and product developers had to manage several cross-cutting concerns along with their feature work and timelines. We need to solve problems holistically to handle multiple teams and applications instead of just the projects at hand

Origin of a Platform team

But what does improving the platform really mean?It is too broad of an avenue to chase after and what we need here is direction and focus. To help answer this, start with these three simple questions

Team formation questions

We should know why we are doing what we are doing and the impact it brings to our developers. Now ruthlessly prioritize our short-term goals and activities so that they support our long-term vision.Always be asking “Is this absolutely necessary to do?”

Align with vision and goals

“How do we operate?”We now define our core values and operating principles that help set the right culture and mindset in our team.

How? — Platform principles (values)

What are our key focus areas?With this, we list down key goals that help achieve our overarching mission. These goals help provide much needed focus, that in turn translates to identifying the right avenues to tackle.

Platform Goals

“The secret to becoming a 10x eng﻿ineer is to help 10 engineers around you to become twice as productive .”

“No idea is true just because someone says so. Test ideas by the evidence gained from observation and experiment. If a favorite idea fails a well-designed test, it’s wrong!”

Define best practices and architectural guidelines . Advocate and enforce them via tooling, reviews, documentation. Provide coaching, participate in slack discussions and help engineers deliver high quality code.

Code Governance

The platform we build is our product and teams we support are our users. We collaborate like an Internal Open Source (aka Inner source) Team. We do not want any one person or team making decisions on how we solve problems for all teams. The key is to share your plan with teammates and encourage open feedback and suggestions through design reviews or other communication channels.

Collaborate Openly

Whenever we identify promising approaches to any problem, it’s encouraged to try them out through POCs, review results afterwards and make choices accordingly. Key features should always be AB tested and analyzed before complete rollout.