Otto

Commitment-Led Project Management: Run Work on Promises

Commitment-Led Project Management: Run Work on Promises

Colleagues agree on a project deliverable

Commitment-led project management means running work as a network of explicit promises between named people, instead of a list of tasks. Each promise has an owner, a condition for “done” and a date, and someone checks on it until it closes. It works because most projects fail in the gaps between people, not inside a single task. For a founder, chief of staff or consultant, the hard part is that promises are made in email, on calls and in chat, so the method only works if one ledger catches all of them.

Otto
Keep Every Project Promise in View
Otto brings meeting, email and calendar commitments into one shared ledger, then drafts follow-ups for your approval.
Visit

TL;DR

  • Commitment-led management treats the organization as a network of personal promises and asks you to find the critical ones, diagnose breakdowns and fix them early.
  • A promise differs from a task: it has an owner who accepted it, conditions of satisfaction, a date and evidence of completion.
  • The method needs one ledger and a steady review rhythm. Without them, plans turn into shelfware.
  • The weak point for busy professionals is capture: promises made in meetings and inbox threads never reach the tracker. We built Otto to capture them in one place, with your approval before anything goes out.
  • When a promise will slip, say so early and bring options. Review misses without blame.

Table of Contents

What commitment-led project management actually means

The idea has a precise origin. Researchers Donald Sull and Charles Spinosa, drawing on work at more than 100 organizations, argued in MIT Sloan Management Review that managers run novel cross-unit initiatives better when they see the organization as a nexus of commitments: personal promises that employees make to each other. Their method has three moves: identify the critical commitments, diagnose where they are breaking down, and intervene to repair them.

A traditional project plan lists tasks and assigns them. A commitment-led plan asks a different question for every piece of work: who has actually said yes, to whom, by when, and what will the other person accept as finished? That shift sounds small. It changes who feels responsible. The same research reports that people who see a promise as a personal pledge work harder to honor it, and that managing by commitment gives managers more flexibility, because they can choose the best people and negotiate terms that fit each piece of work.

The approach also has a long practical lineage. A 2009 presentation to the Agile Alliance describes commitment-based project management, adapted at Intel and documented by Timm Esque in No Surprises Project Management. It starts with a planning session where every deliverable gets exactly one owner, then tracks performance against commitment. The presenters report that projects can run 30 to 50 percent faster because the plan and the execution become clear to everyone. Treat that as the claim of one team’s experience, not a guarantee, but it shows why the method has lasted.

What commitment-led project management actually means

Promise versus task: the difference that matters

A task sits on a list. A promise lives between two people. Four things separate them:

  1. Someone accepted it. An assigned task can be ignored. A promise has been explicitly taken on by the person who will do the work.
  2. There is a requester. Someone is waiting for the result, so there is a person to disappoint and a person to ask.
  3. Conditions of satisfaction are stated. Leadership writer Pat Crawley describes a five-step protocol: define the outcome, request the work, accept accountability, negotiate conditions of satisfaction, commit to deliver. His point is that once the conditions are clear, how the work gets done becomes the accountable person’s job, and leaders hear about problems sooner.
  4. Completion is checked. “Done” is confirmed against the agreed condition, not declared.

The CMMI practice on obtaining plan commitment, as summarized by Wibas, makes the same point in formal language: the person committing should be confident the work fits cost, schedule and performance limits, commitments should be documented, and commitments between teams should be identified so they can be monitored.

Why top-level commitment still matters

Commitment also runs upward. Young and Jordan’s research, published through Macquarie University, found top management support to be the most important critical success factor for project success, and suggested that boards and senior managers influence outcomes more than conventional technical advice assumes. If you are the founder, your own follow-through is part of the system. When you promise an answer to your team and it sits in your inbox for a week, you teach everyone that promises are optional.

The commitment ledger: what to track

The working core of the method is a single ledger of promises. The Project Management Formula action item tracker guide lists the fields that keep such a tracker useful: an ID, a one-sentence description, a single named owner, a specific due date, a status (open, in progress, complete, blocked or cancelled), a priority, the source and notes. Commitment-led practice adds a few more:

Field What goes in it Why it matters
Promise One sentence, starting with a verb Removes ambiguity about what was agreed
Owner The one person who accepted it Shared ownership means no ownership
Requester Who is waiting for the result Tells you whom to update when it slips
Condition of satisfaction What the requester will accept as done Prevents “I thought you meant…” disputes
Due date A specific date, not “soon” Makes follow-up automatic
Source The email, call or meeting where it was made Lets you check exactly what was said
Status and next check Open, blocked, done, plus the next review date Keeps the item from going quiet
Evidence Link or note showing it was delivered Closes the loop honestly

Two habits keep the ledger honest. First, record the promise at the moment it is made, ideally while everyone is still in the meeting. The same tracker guide suggests reading the items back for two minutes before the meeting ends. Second, keep one owner per item. If two people share a promise, split it into two.

Where the method breaks for busy professionals

The ledger is easy to design and hard to feed. Think about where your promises actually come from in a normal week:

  • A client asks on a call, and you say “I’ll send that over Friday.”
  • A teammate’s email ends with a question, and you reply “will do” from your phone.
  • A direct report says in a one-on-one that they will fix something, and no one writes it down.
  • A Slack thread ends with “let me check and get back to you.”

Each of these is a commitment, and each is made in a different tool. An AI notetaker may hold the call but not the inbox. An email assistant may hold the thread but not what was said aloud. So you become the integration layer: you copy context between apps and hold the connections in your head. That is the job the method was supposed to remove, and it is why many people with a good notetaker still lose follow-ups.

This matters most for three kinds of reader. Chiefs of staff and executive assistants track other people’s promises as well as their own, so a missed capture hurts someone else. Consultants and agency owners carry promises to many clients at once, which makes the client deliverables tracker setup a natural companion to the ledger. Founders carry the heaviest inbox, so the way they prioritize emails by commitments rather than by sender decides whether urgent promises surface in time.

A weekly routine that keeps promises alive

A ledger without a rhythm is a graveyard. Here is a routine you can run with any tool, with the places where we think a connected system helps most.

Six steps for keeping work promises on track

Step 1: Capture at the source

Every promise gets logged when it is made: in the meeting, in the thread, in the chat. The failure here is the “later” that never comes. Otto listens in meetings and reads your email and calendar, then records each promise made in any of them into one ledger, so capture does not depend on you remembering to type it up.

Step 2: Confirm owner, condition and date

A captured promise is only a draft until the owner, the condition of satisfaction and the date are clear. Where any of these is missing, ask the requester one short question. Otto drafts that clarifying message for you, and nothing is sent until you approve it.

Step 3: Start the day with the ledger, not the inbox

Each morning, read what is due, what is blocked and what you are waiting on from others. Ordering the day by promises rather than by who emailed last changes what you do first. Because Otto sees email, calendar, meetings and commitments together, it can answer the question of what you should focus on today from that single view. Our guide to tracking work promises before they slip walks through the daily check in more detail.

Step 4: Protect time for the promises that matter

A promise with no time on the calendar is a wish. Block the time as soon as you accept the work, and review your meeting load against your open commitments. This short set of calendar management tips for teams covers practical ways to keep the calendar aligned with what the team has agreed to do.

Step 5: Chase until closed

Most slipped promises are not refused, they are forgotten. A follow-up on the day before the due date, then on the due date, closes most gaps. Otto chases open promises until they are closed, and it drafts the reminder for you to approve rather than sending anything on its own. The difference between a reminder and a tracked promise is explained in reminders versus tasks for founders.

Step 6: Close with evidence and review weekly

Mark an item done only when the requester has what they were promised. Then spend 20 minutes each week on the ledger: what closed, what slipped, what is blocked and why. The same tracker guide recommends a mid-week asynchronous review alongside a brief walkthrough at each status meeting, so no item waits a full week unseen.

When a promise is going to slip

Commitment-led management does not mean promises never break. It means they break loudly and early. Three practices matter.

Say so early, with options. If you cannot credibly deliver a committed goal, tell the people depending on you what will slip, why, and the options with their costs. PM Exams’ team overload guide makes a related point: an escalation should explain the constraint and the options, not just report that the team is busy, and a decision needs an owner and a deadline tied to the real dependency.

Surface blockers rather than bury them. PMI’s Disciplined Agile guidance defines an impediment as any technical, personal or organizational issue that inhibits progress, and says it is always the team’s responsibility to expose impediments as they arise. The team resolves what it can within its own influence, and the lead elevates the rest to management.

Review misses without blame. The aim of a post-mortem is to learn what happened, not to find a culprit. Etsy’s technology department, under then-CTO Chad Dickerson, adopted this practice and later extended it company-wide, assuming good will and looking for causes rather than culprits. People report slipping promises sooner when reporting does not cost them.

A worked example: a consultant promises a client a revised proposal by Thursday, then a second client escalates an urgent request on Wednesday. In a task list, the proposal simply goes overdue. In a commitment ledger, the consultant sees the conflict on Wednesday morning, messages the first client with two options (Friday morning delivery, or a shorter version Thursday), and records the new agreed date. The promise is renegotiated rather than broken.

Why one shared memory beats a stack of tools

The method is simple. The cost is the maintenance. If your commitments live across a notetaker, an inbox, a calendar, a chat app and a task manager, keeping the ledger accurate becomes another job, and the first week you are busy it goes stale. A stale ledger is worse than none, because you trust it.

That is the reason to put capture and follow-up in one system that can see all your channels. When meetings, email, calendar and commitments share one memory, a promise made on a call can be matched to the thread it refers to and the deadline on your calendar, without anyone re-explaining it. Cross-tool automation also needs care: our note on putting idempotency before AI agents explains why connected workflows should not create duplicate or conflicting actions.

Our view on commitment-led work

We think the best project management happens before the project plan: in the moment someone says “I’ll take that.” Everything after is bookkeeping, and bookkeeping is exactly what software should do for you.

The trouble is that you make promises in places no single tool sees. A notetaker has your meetings but has never seen your inbox. An email assistant has your inbox but not what you promised out loud. So you become the glue, carrying context from app to app all day.

Otto removes that job. It listens in meetings, reads email and calendar, and captures every promise into one ledger that it chases until it is closed. Because it sees everything at once, it can tell you each morning what to focus on. And because the work is yours, nothing is sent or finalized without your explicit approval: Otto drafts, you decide.

Eddie

Try the ledger with Otto

Otto is an AI chief of staff built for founders, operators and chiefs of staff whose work is scattered across many tools. It connects with more than 130 tools, including Gmail, Google Calendar, Slack, Notion, GitHub and Todoist, and it keeps meetings, email, calendar and commitments in one shared memory. There is a Free plan at $0 per month, an Upgraded plan at $20 per month and a Max plan at $50 per month, with higher usage limits, integrations and advanced features on the paid tiers. Start at ottohq.app and let the first week of meetings and email fill your ledger.

Otto

FAQ

What is commitment-led project management in one sentence?

It is a way of managing work by tracking the explicit promises people make to each other, rather than only a list of tasks. Each promise has an accepted owner, an agreed condition for done and a date, and it is followed until it closes.

How is it different from agile or traditional project management?

It does not replace them. Waterfall and agile both decide what work exists and in what order. A commitment-led layer adds the question of who has actually promised each piece and when. Agile writer Robert Galen notes that teams commit incrementally, after planning and estimating their own work at true capacity, so the two fit together well.

Does top management commitment count as commitment-led management?

It is related but narrower. Research by Young and Jordan found top management support to be the most important success factor in projects. Commitment-led management covers that and extends it to every promise between peers, clients and teams, including the small ones made in email and meetings.

What should I track in a commitment ledger?

At minimum: the promise in one sentence, a single owner, who requested it, the condition for done, a due date, the source where it was made and its status. Add a next check date so every open item has a moment when someone looks at it again.

How do I stop promises from slipping through between meetings and email?

Capture them at the moment they are made and keep them in one place. Otto does this by listening in meetings and reading your email and calendar, logging each promise to one ledger and chasing it until closed, with every outbound message waiting for your approval.

Sources