Productivity System Audit SKILL.md

This is the exact file agents read, including the credit header and licence notice. Save it as productivity-system-audit/SKILL.md.

---
name: productivity-system-audit
description: "Audit how a person or small team plans and gets work done: capture, clarify, prioritise, plan, focus, review, goals, energy, tools and team requests scored 0 to 3, the biggest leaks, a minimal one-source-of-truth system, daily and weekly rhythms, a gradual rollout and handoffs to specialist skills. Use whenever someone feels busy but behind, keeps missing deadlines, has too many productivity tools, starts a new role or wants to set up an AI-assisted planning system."
license: CC-BY-4.0
metadata:
  author: Afeez Adebayo
  author_url: https://afeezadebayo.com
  author_linkedin: https://www.linkedin.com/in/afeez-adebayo/
  author_x: https://x.com/za_icon
  source: https://afeezadebayo.com/skills-md/productivity/planning-tasks/productivity-system-audit/
  category: productivity
  subcategory: planning-tasks
  version: "1.0.0"
  created: "2026-10-10"
  updated: "2026-10-12"
---

# Productivity System Audit

Most people do not have a productivity problem; they have a system problem. Tasks live in five places, the calendar shows meetings but not the work, priorities change daily, nothing gets reviewed, and the to-do list grows until it is ignored. New apps and techniques rarely fix this, because the gaps sit between the parts: capture, decisions, planning, focus and review.

This skill audits how a person or small team plans and gets work done, finds the few breakdowns that cost the most time and stress, and recommends a minimal system and the specialist skills to fix each gap. It is the entry point for the Planning and Task Management set.

## Operating principles
1. **Fewer tools, one source of truth.** Every task should live in one trusted place.
2. **Fix the biggest leak first.** Usually capture, prioritisation or review, not the app.
3. **Fit the person's real week.** Plans must survive meetings, interruptions and energy dips.
4. **Small, sustainable habits.** A 20-minute weekly review beats an elaborate system abandoned in a fortnight.
5. **Measure outcomes, not activity.** Finished priorities and calmer weeks matter more than ticked boxes.

## Audit areas
| Area | Questions | Typical finding |
|---|---|---|
| Capture | Where do tasks and ideas land? How many places? | Tasks spread across email, chat, notes and memory |
| Clarify | Are tasks written as next actions? | Vague items such as "marketing plan" sit for weeks |
| Prioritise | How are the day's and week's priorities chosen? | Urgent requests always win over important work |
| Plan | Is work scheduled, or only meetings? | Calendar full of meetings, no time for priorities |
| Focus | How often is deep work interrupted? | Notifications and chat break every hour |
| Review | Is there a weekly review? | No review; lists go stale |
| Goals | Do daily tasks connect to goals? | Busy weeks with little progress on goals |
| Energy | When is the person sharpest? | Hardest work scheduled in low-energy hours |
| Tools | Which apps are used, and are they trusted? | Three task apps, none trusted |
| Team | How are requests and handoffs managed? | Requests arrive by chat with no owner or date |

## When to use, and when not to
Use it when someone feels busy but behind, is starting a new role, keeps missing deadlines, has too many tools or wants to set up an AI-assisted planning system.

Don't use it for clinical concerns such as burnout, anxiety or attention difficulties; suggest speaking to a qualified professional while still helping with practical planning. Don't use it for team project management at scale (the Product Management category).

## Inputs to ask for, in one message
1. Role, typical week and main goals for the next quarter.
2. Where tasks, notes and requests currently live.
3. A week of calendar (or a description of it).
4. The current to-do list, even if messy.
5. What feels most broken.
6. Tools the person must use for work.

## Workflow

### Step 1. Map the flow
Trace how a request becomes a finished task: where it arrives, where it is captured, how it is decided, when it is scheduled, how it is reviewed.

### Step 2. Score each area
Score each audit area 0 to 3 (0 missing, 1 ad hoc, 2 working, 3 strong) with one line of evidence.

### Step 3. Find the biggest leaks
Pick the two or three lowest-scoring areas that cost the most time or stress.

### Step 4. Design the minimal system
One task list, one calendar, one notes place, one inbox for requests and a fixed weekly review slot. Name the tools.

### Step 5. Set the daily and weekly rhythm
For example: five-minute morning plan, two focus blocks, end-of-day shutdown, 30-minute weekly review.

### Step 6. Plan the rollout
Introduce one change a week for three to four weeks rather than everything at once.

### Step 7. Hand off
Point each gap to a specialist skill.

## Scorecard template
```
| Area | Score (0-3) | Evidence | Fix | Skill |
| Capture | 1 | Tasks in 5 places | Single inbox | task-capture-clarify |
| Review | 0 | No weekly review | Friday 30 minutes | weekly-review |
```

## Evidence behind the rhythm
| Practice | Why it helps |
|---|---|
| Writing a concrete plan for unfinished tasks | Research by Masicampo and Baumeister found that making a specific plan reduced intrusive thoughts about unfinished goals [Research, 2011] |
| If-then plans ("If it is 9am Monday, then I draft the report") | A meta-analysis by Gollwitzer and Sheeran found implementation intentions improved goal attainment with a medium-to-large effect [Research, 2006] |
| Adding buffer to estimates | People routinely underestimate how long tasks take, known as the planning fallacy [Research, Kahneman and Tversky; Buehler and colleagues] |
| Weekly review | Keeps lists trusted, so the mind stops tracking open loops |

## Signs the system is working
- Every task the person cares about can be found in one place.
- Each morning starts with two or three clear priorities.
- At least one focus block a week goes to the most important project.
- Waiting-for items are chased on time.
- The weekly review happens most weeks.
- The person reports less stress about forgotten tasks.

## Team version
For a small team, add: one place where requests arrive, an owner and due date for every request, a short weekly priorities meeting, and visible Waiting for items so handoffs do not stall.

## Edge cases and judgement calls
| Situation | What to do |
|---|---|
| Meeting-heavy role | Protect two focus blocks a week first; audit meetings |
| Many interruptions by design (support, operations) | Plan in short sprints; batch requests |
| Tool mandated by employer | Work within it; add a personal capture inbox if needed |
| Person wants a new app | Fix habits first; switch only if the tool blocks the system |
| Signs of burnout or overwhelm | Reduce commitments before adding systems; suggest professional support |

## Handoffs to specialist skills
- Agent-maintained task list: `task-system-setup`
- Capture and clarify: `task-capture-clarify`
- Prioritisation: `prioritisation`
- Breaking down projects: `project-breakdown`
- Daily plans: `daily-planning`
- Calendar and focus time: `time-blocking`
- Weekly review: `weekly-review`
- Goals: `goal-setting-okrs`
- Deep work: `focus-deep-work`
- Getting unstuck: `procrastination-unblocking`
- Routines: `habits-routines`
- Quarterly planning: `quarterly-planning-review`

## Worked example
A marketing manager felt constantly behind. The audit found tasks in email flags, a notebook, chat messages and two apps; no weekly review; and a calendar full of meetings with no time for the quarterly launch. The plan moved all tasks into one list, rewrote vague items as next actions, blocked two mornings a week for launch work, added a Friday 30-minute review and a five-minute morning plan, introduced one change a week, and connected the list to an AI agent that updates it from meeting notes. Within a month, launch work was on schedule and the backlog had halved.

## Output format
```
# Productivity audit: <person or team>, <date>
## Summary (biggest leaks, first moves)
## Flow map
## Scorecard
## Minimal system (tools and rules)
## Daily and weekly rhythm
## Rollout plan (week by week)
## Handoffs
```

## Common mistakes
- Switching apps instead of fixing habits.
- Trying every technique at once.
- Planning a perfect day that ignores meetings.
- No weekly review, so the system decays.
- Treating every request as urgent.

## Questions to ask before you recommend changes
- Where does work arrive, and where does it go?
- What did you finish last week that mattered?
- When in the day do you do your best work?

## Self-check before you answer
- Is there one trusted place for tasks?
- Are the top two or three leaks fixed first?
- Does the rhythm fit the person's real week?
- Is the rollout gradual?

---
Created by Afeez Adebayo, Marketing, SEO & Growth Expert
Website: https://afeezadebayo.com
LinkedIn: https://www.linkedin.com/in/afeez-adebayo/
X: https://x.com/za_icon
Source: https://afeezadebayo.com/skills-md/productivity/planning-tasks/productivity-system-audit/

Licence: CC BY 4.0 (https://creativecommons.org/licenses/by/4.0/). You may copy, share and adapt this skill, including for commercial use, as long as you credit Afeez Adebayo and link to the source URL above. Keep this notice in any copy or adapted version.