3 ms·
This being Hacker News...I'm really interested in hearing what people have to say about RASCI, something I had never heard about until the parent comment's link
by danso 12y ago
This being Hacker News...I'm really interested in hearing what people have to say about RASCI, something I had never heard about until the parent comment's link:
> Taibbi and other journalists who came to First Look believed they were joining a free-wheeling, autonomous, and unstructured institution. What they found instead was a confounding array of rules, structures, and systems imposed by Omidyar and other First Look managers on matters both trivial—which computer program to use to internally communicate, mandatory regular company-wide meetings, mandated use of a “responsibility assignment matrix” called a “RASCI,” popular in business-school circles for managing projects—as well as more substantive issues.
That doesn't sound much fun for managing business/IT projects, I can imagine journalists just hating it.
- wavefunction 12y agoThe Wikipedia entry doesn't do RASCI any favors in promoting it as any sort of useful artifact from what I can tell. It seems most like a "blame matrix."
- x0x0 12y agoit's not entirely worthless if, after a meeting, you circulate a quick set of (1) what did we agree on, (2) who is the person responsible for each of (1), (3) who requires signoff on various (1) I find it quite useful. It's good to have it written down to serve as a consensus from the meeting to reduce miscommunication about who has what commitments and who must sign off. Lots of orgs use stuff like this: github has a Primarily Responsible Person, apple has something similar. That said, I've never had to draw out a formal rasci chart, and this can easily be taken too far. In a team of maybe 1-10 people this level of formality is way overkill.
- omouse 12y agoWelcome to a corporate environment. If you know how to navigate the red tape, you can get things done, if you don't then you'll leave for greener pastures.