Conversation

It was an essential mechanism for abstraction at Apple: many people work on many projects; you need a single point of contact and responsibility. Hard to compose many projects without—contact us too diffuse. KA tried a finer-grained model, but it often just confused things.
1
27
It’s more appropriate for bounded, execution-oriented work, rather than open-ended creative work. In the latter context concentrating ownership can be premature; can discourage surprising ideas from individuals during generative phases.
4
23
Agreed. DRIs were a means to assign responsibility and authority as a package once it had been decided we wanted a specific project accomplished in a given time frame. It makes less sense to have a DRI for an ill-defined thing that doesn’t have a ship date.
1
2
10
I suspect the DRI was Scott. The DRI is not the one doing the job, he is the one pushing and organizing to get a result. The role of the DRI is to remind everyone what the goal is, and remove roadblocks. Nothing more.
1
2
2
Show replies