To add to the previous thoughts here, one of the biggest mistakes made with CDE/ICP involved ISD. I don't even know who's responsible: Systems? Business? Both?
The end result was that State Farm, as an organization, took business people from Corporate and dumped them into Corporate South without giving them any Systems training, and then they expected those business people to be able to participate in Systems processes. At the same time, the organization took all of our experienced business analysts and moved them into different roles, opening a huge black hole in requirements analysis.
To give you my perspective on the impact: Before CDE, I worked with extremely competent business analysts. They would produce extremely detailed requirements documents that helped me create the architecture and application design. If I uncovered a missing requirement, the BAs knew how to get answers fast -- they were experts at working directly with the business to figure out what they wanted. Our projects were almost always successful using this model, using any metric available to me as a Systems employee. We delivered the objectives in our charter on time, often under budget.
Unfortunately, CDE/ICP made a mess of everything. I'm not exaggerating when I say that I haven't seen good business requirements since our old BAs moved to other positions. I haven't worked with a single ISD BA who comes anywhere close to providing the level of analysis required. As a result, I am left trying to architect/design systems based upon little to no information.
I'm not exaggerating when I say that I have done complete projects with ZERO requirements. That is not normal, nor is it any way to foster success.
The problem here is that many of the business people brought over into ISD still act like business partners, instead of productive team-mates on a systems team. They sit there like judges holding a gavel ready to sit in judgement of the end product -- but if that's all they're going to do, they SHOULD have stayed over at Corporate. Systems projects need business analysis. These days, they do not receive it.
I suppose someone up top finally figured out that they made a huge mistake, but the damage is done. Our good BAs have either left or, in true State Farm fashion, moved on to roles where they have lost much of their edge.
What really blows my mind about all of this is that the business requirements process WORKED before CDE, and it worked EXTREMELY well, at least in the areas where I worked. There was no need for an overhaul.
Like much of CDE/ICP, leadership created a solution in search of a problem, and in the result, actually CREATED the problem.
All of this ties directly back to people like Pettit. Why is she still here?