https://platformengineering.org logo
Join SlackCommunities
Powered by
This message was deleted.
# platform-blueprints
s
This message was deleted.
a
#2 is the same as #1 ;)
if you want #2 you need high leadership engagement. The funny thing is almost anything is possible if you have #1 (high leadership engagement)
another way of looking at the problem is if #1 is lacking and i want to see systemic change can a scorecard help them engage and be more active, if they are will they help guide to better outcomes. The scorecard then is a teaching tool for leadership
t
Yeah agreed on principle
I’ve talked with a few mega-scale backstage orgs where they seemed to hit a tipping point where everyone wants their stuff looking great for social proof / metadata quality
Long-term leadership buy-in obviously helps the IDP
I’ll rephrase and ask if we know of any bottoms-up scorecard adoption (for production readiness? cost tagging?)
a
what’s the goal? what prevents localized teams from doing it
also why not have all platform teams do it for themselves first and dogfood
whatever your sphere of influence is start there, expand organizational reach later
t
Nothing blocks it, I’m wondering if scorecards/readiness have value aside from a common dashboard with leadership
Seems no
a
it creates transparency and holds the teams setting rules accountable
this way you avoid the sre on tuesday told me Y and the SRE on thursday told me X
d
I’ve observed that the “when” on scorecards causing action relies on a set of events outside your control. Ie, don’t create a scorecard and expect something to happen immediately. Create it; and then keep it updated and inject it into as many conversations as possible for a period of time (eg; 6 months). Eventually some event will happen that focuses all eyes on the scorecard’s topic and voila; action will suddenly happen.
t
That's interesting, it's a nice paper trail / teaching mechanism
p
I’d reverse the question. Scorecards are into themselves just summaries of information and rules. If the info and rules are valuable to C suite but not devs that’s more of a design challenge So what can be put into a scorecard that a single dev or team would need or want? That’s somewhat organizational dependent, but there are certainly common elements I can think of that I’d focus on (think best practices for dev workflows)
t
Right, dumb scorecard criteria is only useful for alignment
3 Views
Open in Slack
PreviousNext
Powered by