Hasty Treat - How To Refine Your Process

Episode Summary

Executive Summary: The episode argues that productivity systems should be treated like code: identify what’s slow, set clear goals, test a change, then reflect and refactor. Wes and Scott discuss practical ways to improve personal workflows—email, desk cleanup, medication tracking, note-taking, and project planning—by borrowing developer habits like functional thinking, batching, and iterative improvement.

Main Topics: Refactoring personal productivity systems: The hosts frame life/process improvement as a refactoring exercise: finding messy, inefficient routines and improving them iteratively rather than expecting a perfect first version. Identifying bottlenecks and slow processes: They emphasize spotting the most painful or time-consuming parts of daily life, such as email, appointments, desk clutter, and remembering medication. Setting measurable goals and trying changes for a fixed period: The discussion recommends clear, trackable goals (e.g., clean desk every week) and testing new habits for a week or 30 days before deciding whether they are worthwhile. Tools and systems for productivity: They compare workflows and tools like to-do lists, calendars, Streaks, ToDoist, Notion, Foam, Obsidian, and markdown-based note syncing as ways to reduce cognitive load. Reflection and evaluation after implementation: A key point is that new processes only matter if you review them afterward to see whether they actually improved productivity and are worth the time investment. Applying developer skills beyond code: The hosts suggest that habits from programming—functional consistency, efficiency, structure, and iteration—can be transferred to personal organization and time management.

Key Arguments: A process should be improved only after identifying it as slow, messy, or ineffective; otherwise effort is wasted. Small recurring problems like medication tracking can be eliminated with a simple system, saving daily mental energy. Clear goals make productivity changes testable, such as keeping a clean desk or limiting inbox size. Trying a change for 30 days is a low-risk way to evaluate whether a new habit or tool is actually valuable. Reflection after the trial period is essential; without it, new habits often fade unnoticed. Not every solution is worth the setup cost—some tools or migrations are too high-investment to justify just testing. People should learn from peers about tools and strategies because others may have already solved similar workflow problems. Developer concepts like functional programming and refactoring can be applied to everyday life and personal productivity.

Data Points: Trial period: 30 days - Suggested by Scott as a common timeframe to test a new habit or workflow and evaluate its value. Suggested desk cleanup time: 15 minutes - Scott estimates that cleaning his desk each Sunday would take about 15 minutes. Medication review cadence: Every Sunday - Scott describes filling a weekly pill container once per week to remove daily cognitive load. Weekly goal: Start each week with a clean desk - Scott offers this as a concrete, trackable productivity target. Inbox target example: No more than 10 emails - Used as an example of a measurable email-management goal. Workload constraint: Two kids / both parents need to work - Used to explain why efficient systems matter under time pressure.

Pivotal Quotes: "You have to make less decisions, things just happen, and things happen the same way every single time." — Scott: Explaining why systems and processes increase productivity and reduce cognitive load. "If I were to take 15 minutes on a Sunday to clean off my desk every single week, I think that would just about do it." — Scott: A concrete example of turning a recurring annoyance into a manageable routine. "I often say, I'm just going to try it for 30 days." — Wes: Describing his preferred method for evaluating new habits or workflows before committing.

Implications: Listeners are encouraged to treat productivity like software engineering: iterate, measure, and keep what works. The broader lesson is that small, repeatable systems can save time, reduce mental overhead, and improve consistency across work and life.