Initiatives

Initiatives help you turn scorecard results into action. Scorecard checks define what “high quality” software means in your organization. When those checks fail, you need a way to track progress toward passing them. Initiatives provide this mechanism: they let you create tasks directly from scorecard checks so you can track progress toward these goals at a company level and drive meaningful change.

Common use cases for initiatives include:

  • Migration tracking: Create initiatives to drive adoption of new platforms, technologies, or standards with clear deadlines and ownership.
  • Security improvements: Operationalize security scorecard checks by creating initiatives that ensure teams address vulnerabilities within specific timeframes.
  • Operational excellence: Drive completion of production readiness checks across services with prioritized initiatives and clear accountability.
  • Compliance requirements: Track progress on regulatory or internal compliance requirements with automated progress reporting.

How initiatives work:

  1. Create scorecards with the checks you want to operationalize.
  2. Define initiatives that target specific checks or entire scorecards.
  3. Set priorities, due dates, and assign owners to drive accountability.
  4. Track progress through automated reporting and optional Slack alerts.

Getting started

Initiatives are created by scorecard admins in the DX UI. Each initiative targets one or more scorecard checks and creates actionable tasks for teams to complete.

Initiative creation form

Configuration

Basic Settings

Every initiative requires:

  • Title: A clear, descriptive name for the initiative
  • Description: Markdown-formatted details explaining the initiative’s purpose and requirements
  • Due Date: Target completion date for the initiative
  • Priority Level: P0 (Critical), P1 (High), or P2 (Medium)
  • Owner: Dedicated user responsible for driving the initiative

Targeting

Initiatives can be applied to all entities which are checked by the scorecard, or can be scoped to only specific entities. You can set an Entity Type Filter which targets specific types of entities (e.g., services, repositories, teams); or create a custom SQL query to set up advanced filtering for precise targeting.

Initiative entity filter sql example

Notifications

Optional weekly Slack alerts can be configured to notify team leads about upcoming or overdue tasks for their entities. This alert uses the entity ownership feature from the catalog. If an entity has multiple owners, each team lead will receive a notification.

Lifecycle

Draft State

New initiatives start in draft mode, allowing scorecard admins to:

  • Configure all settings
  • Test entity targeting
  • Review scope and impact
  • Collaborate on requirements

Publishing

Once published, initiatives become visible across the organization and:

  • Generate tasks for entities with failing checks
  • Begin progress tracking
  • Trigger weekly notifications

Reporting

Initiative progress report

Completion Tracking

Initiative progress is calculated as the percentage of all targeted checks that are now passing. The system automatically tracks:

  • Total number of tasks (failing checks)
  • Completed tasks (checks that now pass)
  • Remaining tasks requiring attention
  • Overall completion percentage

Detailed Breakdown

The progress report provides comprehensive visibility, enabling you to break down the results into the following views:

  • Entity View: See all entities with their task completion status
  • Team View: Track progress by responsible teams
  • Check Details: Understand which specific checks are failing

Progress reports support multiple ways to focus on relevant data:

  • Property Filters: Filter by entity properties like owner or custom metadata
  • Keyword Search: Search across entity names, descriptions, and other text fields
  • View Options: Switch between entity and team perspectives

Exemptions

Users may request exemptions for individual entities. The must provide a date and reason for the exemption.

Once they submit the request, the scorecard admin must approve or deny the request for it to take effect.

Initiative exemption request form

Catalog Entity View

Each catalog entity that has outstanding tasks will display a “Tasks” tab in the catalog.

Initiative entity tasks

Integrating with Jira or Linear

You can automatically create issues in Jira or Linear for scorecard tasks.

Using webhooks, you can also configure a two-way integration where initiatives created in DX get linked to Jira or Linear issues, and issues created in Jira or Linear are linked to initiatives, allowing for easy access from within DX.

Jira

Follow the steps below to configure webhooks in Jira.

  1. Log in as a Jira admin user.
  2. Go to Jira administration console > System > Webhooks
  3. Click Create a WebHook.
  4. Get your DX webhook endpoint URL on the API keys admin page by clicking on the Webhooks button in the top right.
  5. Copy the webhooks URL and paste it into the URL box in Jira.
  6. Select the checkboxes for Issue Created, Updated, and Deleted events.
  7. Finish setting up your webhook by clicing Create hook.

Linear

Follow the steps below to configure webhooks in Linear.

  1. Log in a Linear admin.
  2. Browse to the API settings page.
  3. Click in the + button in the webhooks section.
  4. Get your DX webhook endpoint URL on the API keys admin page by clicking on the Webhooks button in the top right.
  5. Copy the webhooks URL and paste it into the URL box in Linear.
  6. Select the checkbox for Issues.
  7. Finish setting up your webhook by clicking Create webhook.