Origin of a Platform team - Deepstash
Ultimate Guide to Reducing Churn

Learn more about product with this collection

How to analyze churn data and make data-driven decisions

The importance of customer feedback

How to improve customer experience

Ultimate Guide to Reducing Churn

Discover 62 similar ideas in

It takes just

9 mins to read

Origin of a Platform team

Origin of a Platform team

With growing pains, software entropy 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

9

112 reads

MORE IDEAS ON THIS

Team formation questions

Team formation questions

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

7

33 reads

Align with vision and goals

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...

8

10 reads

How? — Platform principles (values)

How? — Platform principles (values)

How do we operate?”

We now define our core values and operating principles that help set the right culture and mindset in our team.

8

16 reads

Platform Goals

Platform Goals

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.

8

33 reads

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

UNKNOWN ENGINEER

9

29 reads

“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!”

PROF RICHARD FEYNMAN

8

14 reads

Code Governance

Code Governance

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.

8

23 reads

Collaborate Openly

Collaborate Openly

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 teammate...

8

14 reads

Controlled Experimentation

Controlled Experimentation

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.

8

17 reads

CURATED FROM

CURATED BY

datsquire

Tech enthusiast, engineering leader, family guy, podcast listener, market enthusiast, binge watcher, 🍕🍕🍕 lover

Read & Learn

20x Faster

without
deepstash

with
deepstash

with

deepstash

Access to 200,000+ ideas

Access to the mobile app

Unlimited idea saving & library

Unlimited history

Unlimited listening to ideas

Downloading & offline access

Personalized recommendations

Supercharge your mind with one idea per day

Enter your email and spend 1 minute every day to learn something new.

Email

I agree to receive email updates