diff --git a/.github/dependabot.yml b/.github/dependabot.yml
index fb39666f980..d0f70fdd13c 100644
--- a/.github/dependabot.yml
+++ b/.github/dependabot.yml
@@ -14,7 +14,6 @@ updates:
       - "christopherfujino"
       - "jmagman"
     labels:
-      - "team"
       - "team-infra"
       - "autosubmit"
     # Updating patch versions for "github-actions" is too chatty.
diff --git a/.github/labeler.yml b/.github/labeler.yml
index f6b637c2005..9ebf48cd9ad 100644
--- a/.github/labeler.yml
+++ b/.github/labeler.yml
@@ -201,14 +201,10 @@ platform-windows:
       - '**/fix_data.yaml'
       - '**/*.expect'
       - '**/*test_fixes*'
-
-team:
+'c: contributor-productivity':
   - changed-files:
     - any-glob-to-any-file:
-      - docs/about/**/*
       - docs/contributing/**/*
-      - docs/postmortems/**/*
-
 team-android:
   - changed-files:
     - any-glob-to-any-file:
diff --git a/docs/infra/Flutter-Framework-Gardener-Rotation.md b/docs/infra/Flutter-Framework-Gardener-Rotation.md
index 562c990d566..d972b51ca18 100644
--- a/docs/infra/Flutter-Framework-Gardener-Rotation.md
+++ b/docs/infra/Flutter-Framework-Gardener-Rotation.md
@@ -50,7 +50,7 @@ Unmute the [tree-gardener channel] and [hackers-infra channel] on [Discord]. Con
 Escalate to the [test owner][TESTOWNERS]. File GitHub issues if none are already open.
 1. The title should include the name of the failing test.
 1. Assign the issue to the test owner with a `P1` priority.
-1. Add the `team` label.
+1. Add the [`c: contributor-productivity`](https://github.com/flutter/flutter/issues?q=is%3Aissue%20state%3Aopen%20label%3A%22c%3A%20contributor-productivity%22) label.
 1. Include links to the failing tests. Download any relevant logs and attach them to the issue, even if the link to the failing tests has the same information. This prevents the issues from becoming stale when logs are expunged.
 1. @ mention the test owner in the [tree-gardener channel] on [Discord] with a link to the GitHub issue. If they are unavailable, escalate to another team member. Continue escalating until someone acknowledges the issue is being investigated.
 
diff --git a/docs/infra/Packages-Gardener-Rotation.md b/docs/infra/Packages-Gardener-Rotation.md
index cbcf358a065..fc85b69a1ac 100644
--- a/docs/infra/Packages-Gardener-Rotation.md
+++ b/docs/infra/Packages-Gardener-Rotation.md
@@ -89,7 +89,7 @@ If old deprecations have reached the point where they can be fixed without losin
 File GitHub issues if none are already open.
 1. The title should include the name of the failing test.
 1. Assign the issue to the test owner with a `P1` priority.
-1. Add the `team` label.
+1. Add the [`c: contributor-productivity`](https://github.com/flutter/flutter/issues?q=is%3Aissue%20state%3Aopen%20label%3A%22c%3A%20contributor-productivity%22) label.
 1. Include links to the failing tests. Download any relevant logs and attach them to the issue, even if the link to the failing tests has the same information. This prevents the issues from becoming stale when logs are expunged.
 1. @ mention the test owner in the [hackers-ecosystem channel] on [Discord] with a link to the GitHub issue. If they are unavailable, escalate to another team member. Continue escalating until someone acknowledges the issue is being investigated.
 1. Investigation updates and questions should not be posted in the [tree-status channel]. This channel should remain free of noise to discourage notification muting.