News for hackers. Stuff that matters.
Re:The Tyranny of Process Worship Within IT by dasil003 on Thursday August 06, 2009 @03:56PM (#746266)
I think a distinction needs to be made between actual process and codified process. The former always exists, and the only question is whether it is working or not. The latter is endemic to large organizations with disaffected and mediocre management and employees, which is what Netflix is actively fighting against.

However the tone of this piece and the original Netflix manifesto does not acknowledge this distinction. I think this shows a bias that is driven by product-oriented software engineers and creatives. "If the product is great then who cares how we got there?" Well that's certainly a valid viewpoint, however it shortchanges great management. Great management is not done by simply hiring the best people and turning them loose on a project. That works in a startup where everyone knows each other and so any two people can notify each other of relevant issues. It doesn't work in larger organizations where individuals have a much narrower slice of responsibility and thus lower visibility on the whole actual process going on.

I've worked with some people who take a process-oriented approach and were very talented at getting the best work out of their employees. For these people it's no more about rigid codified processes than it is about a relentless focus on product. Instead, the goal is to understand at a high level what all the various stakeholders are doing, where their individual bottlenecks are, and determining a process that maximizes everyone's productivity. People like this are incredibly valuable, because let's face it, management is much harder than programming to do well because you are not a domain expert in anything, instead you have to figure out how to help all the different domain experts operate efficiently.

I realize none of this is news to the folks at Netflix, but I think the way the manifesto is written de-emphasizes these facts to the point that the inexperienced or low-level programmer may miss the forest for the trees, which incidentally is exactly what the problem with bad actual process is.

Re:The Tyranny of Process Worship Within IT by Hume62 on Thursday August 06, 2009 @07:09PM (#746634)
Thanks for the comments. I should have made a better distinction between actual and codified process. My thoughts were toward codified, which, as you state, are endemic in larger organizations, and seem to build on themselves over the years, good and bad, until less and less actual progress toward the ultimate goals of the organization is accomplished. Process is delivered, rather than products...

Although I did not agree with everything in the Netflix deck, I was impressed by the "bias" toward great people rather than great process, which seems to me, to be a fresh take on it. There will always be necessary processes and there are certainly many great process best practices to draw from, but I do think we should all be CONSTANTLY QUESTIONING what is in place, asking ourselves if it is serving us or we serving it, and making changes as needed. It is my experience that this happens rarely in large organizations. There simply isn't the political will to take it on...

Re:The Tyranny of Process Worship Within IT by dasil003 on Thursday August 06, 2009 @07:27PM (#746674)
In the corporate world it's definitely a fresh take, and that alone is worth a lot.
Re:The Tyranny of Process Worship Within IT by Retric on Thursday August 06, 2009 @06:13PM (#746535)
Codified process help to increase efficiency by remembering the best way you solved the same problem before. This is extremely useful when you are repeating problems, but it stands in the way when you keep doing new things. The real question is not process and group productivity vs individual productivity, but how fluid your problems are.

When a random customer calls the help desk ask "Is it plugged in?" aka say "Please unplug it wait 5 seconds and then plug it back in."

When the head of R&D calls ask "How can I be of assistance?"

Re:The Tyranny of Process Worship Within IT by daemin on Thursday August 06, 2009 @11:02PM (#746920)
Yes they do that. Additionally I think in a codified process it's probably more important to write down why the process is there and what problem it attempts to mitigate/solve. Then when the problem has been solved in some other way the process should be removed.

(Written) Processes seem to be the same sort of thing as code commenting.