Steve,
The direction we are moving is to also allow WCC to support a simplified interface for the more casual users like those typically using iXp. I don't envision any significant deviations from the existing security policy implementation.
The upcoming 12.0 implementation is expected to address issues with organization, reduce the number of clicks required for most frequently used tasks, improve scalability, etc. One of the fundamental differences between WCC and iXp is that WCC was designed for a team of workload automation experts, typically centralized, whereas iXp was designed more for the decentralized teams where application developers manage the subset of work in their domain.
Most organizations have migrated from the centralized automation team, that WCC was originally designed to support, to the more scalable decentralized model. WCC has not adopted to this transition. Unlike yourself, the typical application user does not strive to become an automation expert. This presents many challenges as we attempt to simplify the experience so the application developers can efficiently do their work. Supporting this model is essential to meet, what is or has become, the more common usage model.
As we implement the changes, these will be presented during the sprint reviews. These are intended to provide customers the opportunity to guide us to an amenable solution toward meeting their needs. I strongly encourage you to continue following the sprint reviews, either live or via the recordings, and provide feedback. It's through this feedback we'll arrive at a solution that provides the flexibility to meet specific needs.
Thanks for sharing your concerns. We'll keep this in mind as we proceed.
Dan