newsfilter.io
Lecture, Tutorial

Adora Cheung - How to Prioritize Your Time

  • Core Premise: Time is the most critical resource for startups as it directly burns money; high opportunity costs make optimizing time usage essential for survival and success.
  • Scope Definition: The advice assumes founders have already determined their total weekly hours for the startup and focuses strictly on prioritizing how those specific hours are allocated among tasks.

Distinguishing Real vs. Fake Progress

  • Real Progress: Defined as activities that directly move the needle on the primary KPI (revenue or active users).
    • High-Leverage Actions: Almost exclusively involve talking to users and building/iterating the product.
    • Goal Setting: Founders should set specific weekly goals for their primary KPI.
  • Fake Progress: Activities that do not directly correlate to growing the primary KPI.
    • Common Examples: Attending conferences, winning awards, networking events, and optimizing secondary or vanity metrics.
    • Risk Factor: These activities are often multiple steps removed from delivering customer value and result in wasted time.

Method for Prioritization

  • Journaling Exercise: Log every hour of the previous week in detail to identify "autopilot" low-value work that feels good to check off but yields minimal impact.
  • Idea Tracking: Maintain a spreadsheet of all ideas that could move the primary KPI; do not execute immediately to avoid context switching and "whiplash."
  • Grading Criteria: Rate each task based on two dimensions:
    • Impact:
      • High: High probability of helping meet the weekly goal.
      • Medium: Okay probability of helping meet the weekly goal.
      • Low: Very low probability of helping meet the weekly goal.
    • Complexity:
      • Easy: Completable in less than one day.
      • Medium: Takes one to two days.
      • Hard: Takes many days or may not be completable within the week.
  • Stack Ranking Strategy: Prioritize tasks with "High Impact + Easy" or "High Impact + Medium" complexity.
    • Avoid: Tasks with Low Impact and High Complexity.
  • Scope Management: Select enough tasks to complete with conviction; attempting too many tasks simultaneously prevents completion and obscures weekly progress.

Implementation and Review

  • Success Metric: Consistent achievement of weekly goals indicates effective time prioritization.
  • Weekly Updates: Founders should write consistent updates covering:
    • The weekly goal and whether it was met.
    • The biggest blocker if the goal was missed.
    • Predicted vs. actual impact of tasks.
    • Key learnings from the week.
  • Periodic Audits: Review all historical weekly updates to detect:
    • Stagnation in learning or repeating the same mistakes.
    • Creep of low-value work or fake progress into the schedule.
    • Consistent prediction errors regarding task impact.
  • Handling Failure: If tasks consistently run over time:
    • Break complex tasks down into smaller, manageable chunks.
    • Rejigger the schedule to minimize context switching.

Operational Tactics

  • Maker-Manager Schedule: Adopt a time-blocking strategy (e.g., full days or half-days) for specific task types to reduce the high cognitive cost of switching contexts (e.g., separating coding days from user meeting days).
    • Critical for: Solo founders who cannot distribute workload across a team.

Strategic Direction

  • Speed of Learning: The primary objective in the early stage is to move fast to validate product-market fit or pivot.
  • Decision Making:
    • It is superior to choose a task quickly, realize it is wrong, learn, and pivot than to spend weeks deliberating and working on low-value items.
    • Indecisiveness is a primary waste of time.

Summary of Actionable Rules:

  • Always work on tasks that directly impact the primary KPI.
  • Prioritize high-impact tasks (talking to users and building product) that are easy to execute.
  • Avoid optimization of vanity metrics and secondary KPIs.
  • Use weekly updates and periodic reviews to validate task selection accuracy.