(responding to Robin)
I've just picked out two bits of your posting...
> One of the key issues faced by many teams is creating well
> written user stories. It can be difficult to clearly describe
> problem without invoking some solution in describing the
> Usability changes seem to arrive in two ways: - as part of a
> user story (initial spec), or as customer feedback (iterative).
These both have a whiff about them of problems with the
'conversation' part of "Card, Conversation, Confirmation". In
first case there might be an over-reliance on the 'card'. There
might not; that's for someone closer to the context to judge.
The card should be a placeholder for the conversation; one
should not need to do much more than identify the problem
so we all know what conversation needs to take place.
In the second case, there seems to be no allowance for changes
in usability to arise as part of the conversation. Maybe this
a problem because of the connotations of the word 'changes' in
this context - perhaps usability requirements arise during the
conversation that are not regarded as 'changes'. Again, it
take somebody closer to the context to judge.