Incredibly generic procress description
Excerpted from the first draft of my experience report for leankanbanconference.com:
Somebody has an idea to add value. Somebody approves the idea has merit, requests that it be built. Somebody transforms the idea into a set of specific changes that need to be made to the application from a user’s perspective. Somebody identifies how those changes need to relate to the existing technical implementation. Somebody causes chose changes to occur to the system. Somebody confirms that those changes were indeed made. Finally, somebody agrees that the changes did indeed provide the desired value.
It may not stick, but for the moment the incredible level of generic writing has a purpose in the document.