Skip to content

Instantly share code, notes, and snippets.

@kashaziz
Created December 23, 2025 10:36
Show Gist options
  • Select an option

  • Save kashaziz/9f997338bc76f4d1d98e6b9eda28ac77 to your computer and use it in GitHub Desktop.

Select an option

Save kashaziz/9f997338bc76f4d1d98e6b9eda28ac77 to your computer and use it in GitHub Desktop.

Monthly Backlog Review - TickTick Task Setup

Create this recurring task in TickTick to ensure you review your exploration backlog regularly.


Task Details

Task name: Monthly backlog review

List: Personal (or Work – Personal if you prefer)

Due date: 1st of every month at 9am (adjust to your preference)

Repeat: Monthly (from due date)

Reminder: On due date

Priority: Medium


Task Description

Copy this into the task description field:

Review exploration backlog document

Link: [paste your Google Doc or Gist link here]

Monthly checklist:
□ Scan Tools to Try - anything urgent?
□ Scan Courses to Take - ready to start any?
□ Scan Content Ideas - ready to write?
□ Scan Project Ideas - time to scope/start?
□ Scan Reading List - allocate reading time?
□ Move actionable items to TickTick Work lists with dates
□ Delete stale/irrelevant items
□ Update "Last reviewed" date in backlog doc

Time needed: 10 minutes

Tips

  • Do this first thing on the 1st - don't let it slide
  • Set aside 10 minutes - it's quick if you're decisive
  • Be ruthless with deletion - most things won't get done
  • Move only 2-3 items max - don't overcommit
  • Update the document immediately - don't leave it for later

Alternative: Weekly Review

If monthly feels too infrequent, adjust to:

Due date: Every Sunday at 11am Repeat: Weekly Time needed: 5 minutes (quicker scan)

Weekly is better if:

  • You're in a fast-moving phase of your business
  • You have many active client projects
  • Your ideas/opportunities change frequently

Monthly is better if:

  • Your work is relatively stable
  • You prefer less administrative overhead
  • You trust yourself to capture urgent items as they arise
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment