Delegate, automate, eliminate, and its four-box cousin, do, decide, delegate, delete, sort tasks by how urgent and how important they are. They work well on Monday's to-do list. They do not work on what produces the list: a board seat, an advisory role, a standing monthly update. Those are commitments, and they need a different set of outcomes, applied differently: keep, delegate, automate, consolidate or exit.
Choosing the outcome is the easy part. Most people can say in a minute which role should go. What stalls is applying the decision, so that is what this article covers, one outcome at a time.
How the task frameworks work, and where they stop
In its common form, the four-box version asks two questions of each task: is it urgent, and is it important. Urgent and important, you do it. Important but not urgent, you decide when and schedule it. Urgent but not important, you delegate it. Neither, you delete it. The shorter delegate, automate, eliminate version skips the grid and asks what can leave your hands.
Point either one at a commitment and it breaks in four places.
- A commitment produces tasks in every box. An advisory seat generates an urgent call, an important strategy review and a pile of email that is neither. Sorting the tasks leaves the seat untouched.
- People are attached. Deleting a task affects you. Leaving a role affects a founder, a chair or a team, and they need notice.
- There is no box for combining. Two roles that ask for the same thing in different meetings are one decision, not two tasks.
- Elimination is not a click. Leaving a commitment takes a date, a conversation and someone to hand over to.
So keep the task frameworks for the tasks. For the commitments themselves, use five outcomes, and give each one a first action and a way to tell whether it held.
An illustrative founder
An illustrative founder, not a real person, makes this concrete. She runs a venture-backed, 45-person payments company, two years after her Series A. Alongside it she holds two advisory seats. One is with a seed-stage startup run by her former head of product, who texts her whenever something breaks. The other came through her lead investor: an advisory role with a later-stage company whose market has moved away from anything she knows. She also writes a monthly investor update, hosts recruiting dinners, and prepares for her own quarterly board meeting on Sunday nights.
She has decided what each of these should become. Here is what applying each decision looks like.
Applying each of the five
Keep: the board meeting
Keeping something is a decision too, and it needs an action. Hers: block the preparation as a fixed slot in the week before each board meeting and tell her assistant it does not move. It has held when the board pack is ready before the weekend, not after it.
Delegate: the recruiting dinners
She keeps the part that needs her: the welcome at the table and the follow-up note to the best candidate. Her head of people takes everything else: the guest list, the venue, the invitations, the reminders. The first action is a half-page note on what a good dinner looks like and an introduction to the venue contact, so the relationship moves with the work. It has held when two dinners happen without her touching the logistics.
Automate: the investor update
The update has the same shape every month: metrics, wins, hires, asks. Her finance lead sets up a template that pulls the monthly metrics into a first draft. She writes the narrative and approves the whole thing before it goes out. Automation prepares the routine part. It never sends anything in her name. It has held when the update takes an hour instead of a Saturday afternoon.
Consolidate: the seed-stage advisory seat
She wants to keep helping her former colleague. What she does not want is ten unscheduled texts a week. The two of them agree one standing monthly call, plus a shared document where questions collect in between. Same relationship, a fraction of the interruption. It has held when the texts stop being the default.
Exit: the second advisory seat
The company needs an adviser who knows its new market, and that is not her. She calls its CEO first, before anything in writing. She offers to finish what she started, helping with the VP search under way, and to step back at the end of the quarter. She names two people who would fit the seat better. Anything in her advisory agreement touching equity or obligations goes to her own lawyer before she signs anything. It has held when the quarter ends and the calls stop, with the CEO still happy to take hers.
Start the exit first, finish it last
The five outcomes do not take the same time. Keep and automate involve nobody else and can start this week. Consolidate takes one conversation. Delegate takes a handover. Exit takes the longest: a date, a conversation, a handoff and a notice period. For a committee seat at work, how to politely leave a committee walks through that exit.
So open the exit conversation in week one, even though it will finish last. The quick changes free hours while the slow one runs. Waiting until the easy wins are done is how an exit slides into next year's renewal.
When applying them is the part that stalls
Applying five decisions across several roles is exactly the follow-through a chief of staff exists for. Executive Capacity is a fractional chief of staff, powered by AI, for founder-CEOs and others who've outgrown their calendar. The Capacity Audit settles the outcome for each commitment, with you. The retainer then does the applying: we carry out what you approved, with a short brief each week.
The applying arrives as decisions, not projects. In a five-minute weekly review, decisions come to you on your phone, one at a time: approve a draft, confirm a delegation, confirm an automation. The sample brief on the Executive Capacity page holds three of them, one exit, one automation and one delegation.
The exit gets the most care. Exits happen in stages, with a clean handoff, so relationships stay intact. The call to the CEO is still yours to make. The note that follows it is prepared in your voice, and you read, edit or decline it. Once you approve it, the draft is placed in your own Drafts folder. You press send. Stepping back without burning relationships covers that part in detail.
Each change is then read against the week you started with, measured rather than estimated, so you can see which of the five actually gave hours back.
GradeCircle builds and runs six products of its own: AfroSynergy, CallerBridge, HealthSquire, Heyzl, Lexfora, and LukeAPI, two of them in beta. The assumptions in our models come from operating those systems, not from a framework. See what we run.
If your commitments have outgrown your week, answer six quick questions to see whether Executive Capacity is a fit.



