All Notes

How I get things done

Last updated

Jun 04, 2026

This simple and minimal project management setup has kept many of my teams on track and shipping fast:

1. List all active workstreams

Every active workstream goes on the list. Not just โ€œbigโ€ projects, also the messy cross-functional things that are eating attention. If something needs coordination, it needs to be visible.

2. Assign one accountable owner

Every workstream has exactly one accountable owner.

I like ARCI for this: Accountable, Responsible, Consulted, Informed. There can be many people responsible for pieces of the work, many people consulted, and many people informed.

But there is exactly one person accountable.

Some people call that person the DRI. I donโ€™t care what the title is. The important thing is that one personโ€™s head is on the line if the project is not going well.

Not because they have to do all the work. They can make other people responsible for every part of it. But they are accountable for the overall success by themselves.

If there are multiple accountable owners, there are zero accountable owners. Chaos ensues.

3. Give every workstream a deadline

Every project needs a deadline, even if it is synthetic.

Deadlines force tradeoffs. They make it obvious when scope, resources, or expectations need to change. The deadline can move when reality changes, but it has to exist.

4. Get regular green/yellow/red updates

At some regular cadence, each accountable owner gives a status update of the project compared to its deadline:

  • Green: on track

  • Yellow: at risk

  • Red: off track

Async works. Sync works. The mechanism matters much less than the fact that you have a mechanism to manage change in each individual project.

5. Do weekly demos

I like weekly demos: one strict 2 minute demo per workstream every week.

The accountable owner is accountable for making sure the demo happens. They do not have to give the demo themselves. Just like every other part of the project, they can make somebody else responsible for it.

The strict 2 minute limit matters. It keeps the meeting fast, it forces people to summarize what actually happened, and it makes the updates much less boring. It makes the whole thing more fun.

It sounds short, but Iโ€™ve found that every project can fit their weekly update demo into that timeframe.

My default is every Friday: one workstream, one demo, two minutes. Repeat until done.

Other notes about Company Building

  • ๐ŸŒฟ
    How to be better at making decisions

    What can I do before, during, and after making decisions to be better at making them?

  • ๐ŸŒฒ
  • ๐ŸŒฟ
    How to present to executives

    1. Know all your details Know and be able to speak to all the details. Review your own work and ask yourself what somebody else might ask you about it, then make sure you have a solid answer to all those questions. Even things that are technically ou...

  • ๐ŸŒฟ
    Developer tools startups are playing on hard mode

    How do you build a business selling tools to people who can technically build anything you can?

  • ๐ŸŒฒ
    Being unreasonably responsive has made my projects more successful

    Creators who respond to feedback quickly unlock two virtuous cycles that allow them to build better solutions more quickly.

  • ๐ŸŒฑ
    How I manage my todos as a CEO

    Kanban board with five columns: Inbox, Backlog, Blocked, Delegated, Done Most importantly: GTD-style โ€œif it takes less than 2 minutes, do it immediately.โ€ Create todos for everything (and I mean, everything, including replying to people) that go in...

  • ๐ŸŒฟ
    Message me whenever

    Send me messages whenever inspiration strikes or when it makes sense for your workflow. I'll respond when I'm back online. This isn't about being "always on," quite the opposite: it's about respecting that we each know how to structure our own work l...

  • ๐ŸŒฑ
    How to run recurring virtual meetings efficiently

    Start with a checkin question for connection (10% of the meeting length) Capture decisions made Capture open action items and check in on open ones every time, otherwise they get lost/forgotten due to poor personal execution Align on discussion ...

  • ๐ŸŒฟ
    How I run gratitude circles

    Credit to Sue Ko who taught me this many years ago. Gratitude circles are a beautiful way to get team members feel seen by their peers. I run them in-person at least once a year with each of my teams. Quote from one of my engineers after their first ...

  • ๐ŸŒฟ
    How we make brainstorming work

    Brainstorming usually fails. But, I noticed a pattern in the times that it worked exceptionally well. Here's how to make it work.

  • ๐ŸŒฟ
    How we foster deeper connections in our remote team

    I believe that teams that are more connected perform better and that remote teams have worse connections. How can we improve that?

  • ๐ŸŒฒ
    Why I'm vigorous about giving feedback

    Every day, you will find me hunting down a founder's email to send them feedback about my experience with their product. Why?