Department Scorecard

What a team owns, and how it supports the rest of the org

Steps
1
Last edited
Jul 13, 2026
Created by
Nova

About this process

Department Scorecard. Does the same one level up: it defines what an entire team is accountable for. Captures the department's mission, its owned KPIs and targets, the capabilities it must be great at, and how it works — plus a dedicated section mapping how it serves other departments (who it supports, the service level it commits to, and what it needs back). Use it to align a function, expose cross-team dependencies, and make sure no team operates in a silo.

The process in detail

1 step
  1. 1

    Department Scorecard - How We Support Other Departments

Read the full text
1. Department Scorecard - How We Support Other Departments

Fill Mission → Outcomes → Capabilities → Values top-down, then do the support grid with the other departments in the room if you can — the "what we need back" column is where silos actually get surfaced and fixed.

Department / Function — the team this card is for. One word or two. e.g. Marketing.

Mission · Purpose — why the department exists, its single core charge.

Formula: This department exists to [core outcome] so that [company impact].

e.g. Marketing exists to generate qualified pipeline so that Sales can hit its number predictably.

Key Outcomes / KPIs (3–5) — the measurable results the department owns, each with a target on the dashed line.

•Formula: [Result] — target [number] by [when]
•e.g. Generate $2M in sourced pipeline → target: $2M by end of Q3.

Core Capabilities (3–5) — what the team must be excellent at to deliver those outcomes. Derive these from the outcomes above.

•Formula: [Capability] — so we can [which outcome it enables]
•e.g. Marketing analytics — so we can prove which channels drive pipeline.

Operating Values (3–4) — how the team works day to day; the behavior line makes it concrete.

•Formula: [Value] → In this team that means: [observable behavior]

e.g. Speed → ships a campaign draft in days, not weeks.

How We Support Other Departments — the hero section. One row per internal customer, and always state the SLA both ways:

•Internal customer — which department depends on you. e.g. Sales.
•What we provide + SLA — the deliverable and its quality/speed standard. [Deliverable] — [quantity/quality], within [timeframe].
•What we need back — your dependency on them, so it's a two-way contract. [What you need] within [timeframe].
Use this process
Capabilities
Fully editableAdapts as work changesAdd more sessions anytimeAI can be assigned
N
Created byNova·Official process
Last edited Jul 13, 2026·1 step