惯性聚合 高效追踪和阅读你感兴趣的博客、新闻、科技资讯
阅读原文 在惯性聚合中打开

推荐订阅源

L
Lohrmann on Cybersecurity
Martin Fowler
Martin Fowler
Engineering at Meta
Engineering at Meta
腾讯CDC
钛媒体:引领未来商业与生活新知
钛媒体:引领未来商业与生活新知
Microsoft Azure Blog
Microsoft Azure Blog
G
Google Developers Blog
TaoSecurity Blog
TaoSecurity Blog
博客园_首页
Vercel News
Vercel News
Hugging Face - Blog
Hugging Face - Blog
D
Darknet – Hacking Tools, Hacker News & Cyber Security
Last Week in AI
Last Week in AI
cs.CL updates on arXiv.org
cs.CL updates on arXiv.org
T
The Exploit Database - CXSecurity.com
量子位
Project Zero
Project Zero
A
Arctic Wolf
小众软件
小众软件
NISL@THU
NISL@THU
C
CERT Recently Published Vulnerability Notes
有赞技术团队
有赞技术团队
MongoDB | Blog
MongoDB | Blog
博客园 - 聂微东
OSCHINA 社区最新新闻
OSCHINA 社区最新新闻
N
News and Events Feed by Topic
宝玉的分享
宝玉的分享
freeCodeCamp Programming Tutorials: Python, JavaScript, Git & More
T
Troy Hunt's Blog
P
Privacy & Cybersecurity Law Blog
Security Latest
Security Latest
B
Blog
酷 壳 – CoolShell
酷 壳 – CoolShell
D
DataBreaches.Net
Schneier on Security
Schneier on Security
The Hacker News
The Hacker News
K
Kaspersky official blog
C
Check Point Blog
Hacker News: Ask HN
Hacker News: Ask HN
cs.AI updates on arXiv.org
cs.AI updates on arXiv.org
Webroot Blog
Webroot Blog
www.infosecurity-magazine.com
www.infosecurity-magazine.com
人人都是产品经理
人人都是产品经理
AI
AI
Cisco Talos Blog
Cisco Talos Blog
MyScale Blog
MyScale Blog
Cloudbric
Cloudbric
B
Blog RSS Feed
S
Schneier on Security
P
Palo Alto Networks Blog

Max Stoiber's Essays

Save polish for where it matters How I run gratitude circles How to present to executives Message me whenever How I manage my todos as a CEO How to run recurring virtual meetings efficiently How to have great taste How to be great at storytelling How we make brainstorming work How do you invent the future? Being unreasonably responsive has made my projects more successful Why I'm vigorous about giving feedback How to ship faster How to be better at making decisions How I tend to my digital garden David Cain: Do Quests, Not Goals Deliberate practice beats every other form of training, even via transfer learning How we foster deeper connections in our remote team Why I don't compliment people for their talent How can you slow down life? (which is perceptually half over by 23) 1:1s are for personal connection, not project updates Developer tools startups are playing on hard mode Developer tools are different than tools for any other profession You probably don't need GraphQL Why I Love Tailwind Margin considered harmful I am joining Gatsby Why I Write CSS in JavaScript Tech Choices I Regret at Spectrum Streaming Server-Side Rendering and Caching
How I get things done
Max Stoiber · 2026-06-04 · via Max Stoiber's Essays

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.