Miles To Go Promises To Keep

How I Actually Use a Frost-Inspired Commitment System

I've been running a fairly rigid personal productivity system for about seven years now, built around a principle most people encounter in high school English class. The concept isn't exactly novel, but the way it translates into daily work habits is where things get interesting. The core idea comes from Robert Frost's poem and boils down to this: you have obligations that demand completion before you allow yourself rest, and the distance to those obligations matters less than the fact that you intend to travel them. What I built is a commitment tracking framework. It's not a piece of software I recommend downloading — it's a method. You write down your promises, which are your real obligations, then you quantify the miles, which are the effort or time estimates attached to each one. That's the entire structure.

Miles To Go Promises To Keep

In practice, I use a simple spreadsheet combined with a weekly review ritual. The spreadsheet has three columns: promise, estimated miles, and status. A promise might be "complete Q3 financial report for the client" or "fix the auth bug in the staging environment." Miles isn't hours — it's a subjective weighting from 1 to 10 based on how much mental overhead the task carries. A promise rated 8 miles will eat your day even if it only takes two hours of actual work, because the cognitive load is high. This distinction between time and effort is something most people miss when they first try this. Every Sunday evening, I review the sheet. Any promise marked complete moves to an archive column. Anything that hasn't been touched in three weeks gets flagged for re-evaluation. The flag isn't a punishment — it's a signal that the promise may no longer be real, and you should either commit to it properly or drop it. Carrying dead weight in your system creates drag that compounds over time.

Why This Approach Actually Works

Most productivity systems fail because they track tasks, not commitments. Tasks are things you do. Commitments are things you owe — to yourself, to a team, to a deadline. The emotional and psychological difference is significant. When you frame something as a promise, you're acknowledging the obligation explicitly. That changes how you prioritize it. The miles component forces honesty. If every promise gets a 10-mile rating, the system breaks. You have to calibrate. I learned this the hard way after I spent three weeks convinced I was overwhelmed when the data showed my average mile rating was 2.1 across all active promises. The problem wasn't volume. The problem was that four of my promises were actually relationship debts I'd been avoiding — things like returning a call from a collaborator or following up on a contract clause. Those scored low on effort but carried high emotional miles. Once I identified them and handled them, my entire week felt lighter.

The Edge Case That Broke My System

About two years in, I hit a wall where multiple high-mile promises kept colliding. A client deadline landed the same week as a critical production incident, and both were rated 9 miles. My system had no collision protocol. I was burning through evenings and weekends and the spreadsheet just kept growing. That's when I realized the framework was missing a bottleneck rule. Here's what I added: a hard cap of three active promises above 7 miles at any given time. If a new high-mile commitment comes in, something already at 7+ has to be paused, delegated, or cut. This isn't elegant. It feels arbitrary. But it works because it forces a decision instead of letting everything queue up until you're drowning. I've never gone back from implementing this rule. It's saved me from at least two situations where I would have dropped the ball professionally.

Common Pitfalls

The biggest mistake people make is treating miles as a measure of duration. They aren't. Miles measure commitment weight. A two-hour meeting with a difficult stakeholder might be 6 miles. A straightforward coding task that takes six hours might be 3 miles. The distinction matters because it affects how you schedule your week. If you fill every slot with low-mile easy tasks, you'll feel productive but unfulfilled because the heavy promises are still waiting. Front-load the high-mile items. Do them when your energy is highest, not when you have spare time. Another issue is the review ritual. If you skip the weekly check-in, the system decays within a month. Promises accumulate without context. The archive column becomes meaningless. I set a recurring calendar event for Sunday at 7 PM and treat it as non-negotiable. It takes about fifteen minutes. Skipping it costs far more than the time investment.

When This Method Fails Completely

This framework doesn't work for team-level project management. It's designed for individual accountability. If you're trying to coordinate a department or run an agile sprint board, use a proper tool. The simplicity that makes this effective for personal use becomes a liability at scale. For teams, I'd recommend something like Linear or even a well-structured Notion database with proper assignment and deadline fields. The Frost principle still applies conceptually — people still have promises and distances to cover — but the mechanics need different infrastructure. It also struggles with creative work where the output isn't clearly defined. Writing a novel or designing a product featureset doesn't map cleanly onto discrete promises with mile estimates. In those cases, I break the work into smaller deliverable-based promises. "Draft chapter one" instead of "write the book." The mile rating applies to the deliverable, not the vague activity. This requires discipline to define deliverables honestly instead of padding them to feel safer.

Getting Started

All you need is a spreadsheet or a notebook. Write down every obligation you're currently carrying. Rate each one 1 through 10 on effort weight. Set a three-active-high-mile cap. Review weekly. Archive completed items. Flag stale ones. That's it. No app to install. No subscription. The system is the discipline of maintaining it, not the tool you use to maintain it. If you want something more structured than a blank spreadsheet, I've shared a basic template on my personal site. It's just a Google Sheet with conditional formatting that turns high-mile promises red when they pass two weeks without a status update. The template itself is straightforward and you can copy it without any setup. The real work happens in the weekly review, not in configuring the tool.