OpsLevel Logo
Product
Developer portal
Software catalog
Understand your entire architecture at a glance
Standards
Your guide to safe, reliable software
Developer self-service
Empower developers to move faster, risk-free
Integrations
Connect your most powerful third-party tools
Use Cases
Ownership
Build accountability and clarity into your catalog
Standardization
Set and rollout best practices for your software
Developer Experience
Free up your team to focus on high-impact work
Customers
Resources
All Resources
Our full library of resources
Pricing
Flexible and designed for your unique needs
Podcast
Podcast
Conversations with technical leaders
Blog
Blog
DevOps resources, tips, and best practices
Demo
Demo
Videos of our product and features
Tech talk
Tech talk
Our POV on technical topics
Guide
Guide
Practical resources to roll out new programs and features
DocsLog In
Talk to usTry for free
No items found.
Share this
Table of contents
 
Resources
Guide

When and why to use Scorecards

Product
Standardization
Developer
DevOps
Platform engineer
When and why to use Scorecards
OpsLevel
|
August 15, 2023
When and why to use Scorecards

Service maturity isn’t one-size-fits-all, which is why we allow customers to build service standards into the centralized Rubric, individual scoped Scorecards, or a combination of both. Our model gives you flexibility where you want it, and consistency where you need it to gauge service health adequately. Here, we’ll show you how Scorecards work, when to use them, and how they help you achieve service maturity.

Looking for technical guidance? You can find our Scorecards docs here. 

What are Scorecards and how do they work?

Scorecards are a set of checks scoped to a specific team, group, category, or whatever else makes sense for your organization’s Service Maturity model.They’re designed to give you insight into your services’ current maturity levels and what’s needed to improve them. Scorecards give teams the autonomy to create their own service standards, without impacting the global Rubric.

To see how any given service is tracking against all relevant Scorecards, check out its Maturity Report page. 

How are Scorecards different from the Rubric?

While Scorecards and the Rubric both give you insight into service health, Scorecards aren’t global in nature—meaning they won’t apply to the entire organization. You can have multiple Scorecards across different services, teams, and cross-functional groups versus just one org-wide Rubric.

Though Scorecards offer team autonomy, they are built on a shared taxonomy with the Rubric (i.e., the underlying concept of what makes something “Bronze” is universally applied and understood). This means you can have apples-to-apples reporting between Scorecards and the Rubric, and as teammates switch services or teams, they don’t have to relearn anything.

Why OpsLevel’s Scorecards are ideal

By having Scorecards and a global Rubric, OpsLevel simultaneously provides team autonomy and global standardization, making it easier to scale and grow your Service Maturity program. Additionally, Scorecards and the Rubric are built on a shared taxonomy, meaning:

  • You can have apples-to-apples comparisons across teams and Scorecards for reporting (i.e., while the individual checks comprising any given “Bronze,” “Silver,” and “Gold” levels are different, the underlying concept of what makes something “Bronze” is universally understood and applied).
  • As teammates switch between services or teams, no context is lost and they don’t have to relearn a new grading system.
Service Maturity levels and their definitions are shared across Scorecards and the Rubric, providing shared context and improved reporting functionality.

Scorecard use cases and examples 

1. Let teams go at their own pace

If you’re just getting started or Rubric administration is limited to specific users, or requires org-wide and leadership approval, Scorecards can help your teams start rolling out maturity faster, and feel a little less intimidated to get started.

2. Create scoped standards

Sometimes specific dev teams or guilds have unique standards they want to set and track, outside of a global view.

3. Perfecting your rubric

In other instances, using Scorecards can help you to perfect and improve your rubric overall

With an idea of how and when to use Scorecards, you can start to determine where it makes the most sense to use them for your organization. Paired with the guidance in our Rubric article, you’re set up for a smooth and scalable service maturity program from day 0, giving you org-wide and team-specific coverage all at once.

More resources

Guide
September 18, 2023
by
OpsLevel
Finding your IDP: A comprehensive guide to choosing an internal developer portal

This guide (and Notion template) will help you choose the right developer portal for your needs.

Guide
March 14, 2023
by
OpsLevel
How to build your catalog

Learn all the ways you can import your service metadata into OpsLevel.

Guide
March 7, 2023
by
OpsLevel
Champion's guide: How to navigate an internal developer portal rollout

Navigate your role as a champion and build partnerships across the org to ensure you can successfully implement OpsLevel and achieve your goals.

OpsLevel Logo
Subscribe
Join our newsletter to stay up to date on features and releases.
By subscribing you agree to with our Privacy Policy and provide consent to receive updates from our company.
SOC 2AICPA SOC
Product
Software CatalogMaturityIntegrationsSelf-serviceRequest a demo
Company
About usCareersContact UsCustomersPartnersSecurity
Resources
Docs
Blog
Demo
© 1999 J/K Labs Inc. All rights reserved.
Cookie Preferences
Terms of Use
Privacy Policy
Responsible Disclosure
By using this website, you agree to the storing of cookies on your device to enhance site navigation, analyze site usage, and assist in our marketing efforts. View our Data Processing Agreement for more information.
Okay!