One-Pager #1: Digital Work Portfolio
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, stop or make decisions about it.
Clarity before scale.
What counts as a digital asset here?
Anything repeatable that produces an outcome people rely on.
Quick test: if it disappeared tomorrow and work would break or degrade, it probably counts.
Counts vs doesn’t count (yet)
Dashboards used for recurring decisions
One-off decks and ad hoc analysis
Workflows, automations, scripts, integrations
Temporary trackers and project admin sheets
Internal tools, forms, bots, and agent workflows
Tool licences by themselves
Data pipelines, datasets, metric definitions
Prototypes not used in live work
System-embedded SOPs
Prompt lists not tied to a repeatable workflow
The minimum viable table
You do not need a programme. You need a table that makes digital work comparable.
Comparability beats perfection.
Decision rules (minimum)
- No owner = fix ownership first.
- High risk = explicit owner + review cadence.
- High value + low reuse = scale candidate.
- Low value + high noise / effort = stop by a date.
- Duplicates = consolidate or retire.
The first move (≤ 60 minutes)
- Pick one boundary (team, function, or product area).
- List 10–15 assets people already rely on.
- Score quickly: Owner + Reuse / Risk / Value.
- Make one keep / fix / stop decision.
- Write one next action under 30 minutes.
Example row
Want the deeper why, the failure modes, and the copy/paste internal note?
