Digital Work Portfolio Companion Sheet
If you can’t list it, you can’t govern it. If you can’t govern it, you can’t prioritise or make clear decisions about it. Clarity before scale. Manage digital work like a portfolio.
Copy this into a doc. Use it in a meeting. Make one decision.
If you can’t list it, you can’t govern it.
If you can’t govern it, you can’t prioritise it or make clear decisions about it
What this is for
Use this sheet to make one quick operator move: surface the digital assets already running work, compare them fast, and make one keep / fix / stop call without turning it into a giant inventory project.
What counts
Anything repeatable that produces an outcome people rely on. Quick test: if it disappeared tomorrow and the work would break, slow down, or get noisy, it probably counts.
Counts vs doesn’t (yet)
Counts: dashboards used for recurring decisions
Doesn’t yet: one-off decks and ad hoc analysis
Counts: workflows, automations, scripts, integrations
Doesn’t yet: temporary trackers and project admin sheets
Counts: internal tools, forms, bots, and agent workflows
Doesn’t yet: tool licences by themselves
Counts: data pipelines, datasets, metric definitions, embedded SOPs
Doesn’t yet: prototypes not used in live work
The minimum viable table
- Asset — name it the way you’d say it in a meeting.
- Owner — outcome owner, not platform owner.
- Reuse / Risk / Value — Low / Medium / High is enough.
- Decision — Keep / Fix / Stop.
Decision rules (minimum)
No owner = fix ownership first.
High risk = explicit owner + review rhythm.
High value + low reuse = scale candidate.
Low value + high noise = stop by a date.
The first move (≤ 60 minutes)
- Pick one boundary: one team, one function, or one product area.
- List 10–15 assets people already rely on.
- Score quickly: owner + reuse / risk / value.
- Make one keep / fix / stop call.
- Write one next action under 30 minutes.
Example row
Asset: Monthly close dashboard | Owner: Finance Ops lead | Reuse: High | Risk: High | Value: High | Decision: Fix — add a monthly validation cadence.
Want the full move?
Open the playbook for the method, the failure modes, and the internal note you can reuse with your team.
