3 ms·
> Not all work can be done asynchronously, and often the most important work is important because it's a blocker for other things. This sounds like a project m
by ryandrake 2y ago
> Not all work can be done asynchronously, and often the most important work is important because it's a blocker for other things.
This sounds like a project management failure. One of the cardinal rules of the remote programs I run is: Never let the critical path be blocked by one person having to physically do some synchronous task. If Task X requires Person Y to approve it by Date Z, then you obtain that approval asynchronously, waaaaay before Date Z, where you would otherwise become blocked.
> In practice this kind of mindset simply increases the critical path of the project
I mean, I think that's what you're getting at here, so design your business processes just like you'd design a multi-threaded program: such that there are no locks and mutexes.
- zeroCalories 2y ago1. Management is hard and failure is common. Now what? Just let the projects fail? 2. You can't always parallelize work, and even if you can, that doesn't mean it will be faster/more efficient