Capabilities and Process Architectures "Old Chestnut"

There have been many posts in recent forum discussions within the business architecture community which describe the commonality,within some organisations, between higher level process blocks and capabilities.
Some have suggested that this makes capabilities less useful. This is due to a combination of factors either because the organisation is very process dominant with low levels of physical things like, manufacturing or logistical activities or perhaps even due to poor analysis.
Process folks think process and when searching for capabilities use their reference point, process in current organisational structures, to search for capabilities. In many cases it is not surprising that they "low and behold" discover capabilities fairly identical to their high level process and say " well that was a pointless task wasn't it ".Quite often they have missed a lot of capabilities that the organisation has that could be instrumental to a step change in business model. 
Thus the introspective continual reference to to current physical state of the business constrains the thinking of the logical. Peter Checkland recognised this feature in his Soft Systems Methodology in Action (P.Checkland, Jim Scholes, 1999, Wiley, Chichester).
To model capabilities properly it is necessary to detach from what you know and the current context that you work within i.e. process and look in at the business from the outside through a fresh set of eyes lifting up to root definitions and conceptual models. This is not easy when your analysis team are steeped in operational thinking.