Comments on: The Bureaucratic Scale of Corporate Process http://www.techdarkside.com/the-bureaucratic-scale-of-corporate-process Struggles of a Self-Taught Coder Tue, 07 Feb 2012 02:07:00 +0000 hourly 1 http://wordpress.org/?v=3.2.1 By: Allen http://www.techdarkside.com/the-bureaucratic-scale-of-corporate-process/comment-page-1#comment-149 Allen Tue, 05 Sep 2006 05:18:41 +0000 http://www.techdarkside.com/?p=40#comment-149 Brilliant Daymond! And so billiantly simple for the math majors. I especially love the Y Intercept of the formula ;) Very Adept... and with some refinement could put you on the road to Master ;) "Making the simple complicated is commonplace; making the complicated simple, awesomely simple, that's creativity." - Charles Mingus 4/22/1922 Brilliant Daymond! And so billiantly simple for the math majors. I especially love the Y Intercept of the formula ;)

Very Adept… and with some refinement could put you on the road to Master ;)

“Making the simple complicated is commonplace; making the complicated simple, awesomely simple, that’s creativity.”
- Charles Mingus
4/22/1922

]]> By: dave http://www.techdarkside.com/the-bureaucratic-scale-of-corporate-process/comment-page-1#comment-93 dave Mon, 31 Jul 2006 21:55:48 +0000 http://www.techdarkside.com/?p=40#comment-93 I don't even want to talk about that nasty formula, Daymond. I want to clarify one thing: not all bureaucracy is bad. It is bad, however, to not understand the amount of bureaucracy you can tolerate and still be happy. It is also bad to not evaluate your ability to tolerate bureaucracy against a prospective employer's bureaucracy. I don’t even want to talk about that nasty formula, Daymond.

I want to clarify one thing: not all bureaucracy is bad. It is bad, however, to not understand the amount of bureaucracy you can tolerate and still be happy. It is also bad to not evaluate your ability to tolerate bureaucracy against a prospective employer’s bureaucracy.

]]> By: Daymond http://www.techdarkside.com/the-bureaucratic-scale-of-corporate-process/comment-page-1#comment-92 Daymond Mon, 31 Jul 2006 20:16:10 +0000 http://www.techdarkside.com/?p=40#comment-92 Ahhh, you assume bureacracy can be / should be avoided. I think you have to differentiate appropriate deliberation vs. non value add bureacracy. After careful theorem analysis and research, I am proposing the following algorithm to understand the depth and breadth of bureacracy in a company. Daymond's Bureacracy Factor (or DBF) = X (Y * Z + (M*N) / ((R+S)*K) Where.. X = size of the project team Y = the number of business and / or VP level organizational units required to implement a typical project Z = risk or "pucker" factor - monetary / user impact of new project or change, if the solution does not work or is not deployed in time. M = the amount of time given to implement the project N = the contractor to FTE ratio on the project R = the number of levels between a software engineer on the project and the VP S = staff "churn" ratio K = organizational process maturity (1-10) <I> Ahhh, you assume bureacracy can be / should be avoided. I think you have to differentiate appropriate deliberation vs. non value add bureacracy. After careful theorem analysis and research, I am proposing the following algorithm to understand the depth and breadth of bureacracy in a company.

Daymond’s Bureacracy Factor (or DBF) = X (Y * Z + (M*N) / ((R+S)*K)

Where..

X = size of the project team

Y = the number of business and / or VP level organizational units required to implement a typical project

Z = risk or “pucker” factor – monetary / user impact of new project or change, if the solution does not work or is not deployed in time.

M = the amount of time given to implement the project

N = the contractor to FTE ratio on the project

R = the number of levels between a software engineer on the project and the VP

S = staff “churn” ratio

K = organizational process maturity (1-10)

]]>