I recently was defining the interfaces for backend services that were being built for 3rd party users. Much of that work was adding descriptions that would make sense for the user, not the service provider. The focus was on consistency in terminology, definitions and usage across all the service interfaces we provided - and much of my work was developing procedures for the developers to fall back to make sure their first deliveries were effective for our customer.

Much of my history spans technical (design, development, delivery and support) applications, and have been moving in the past 15 years from an online application (AOL Video program) to the service interfaces based on business flow definitions. I moved from define/design/code/test to scrum and have been working to find ways to make that work with 3rd parties, rather than just in-house. At one point I took on people management, however, I found out that I really preferred tech!

While the last jobs have involved less technical, the focus stayed on the understanding and definition of business - between the business professionals and the dev team designers. Most of my work has been architecture work in the creation of the user stories, and active participation in the design results via the service documents. By pushing this forward in the process I found that we had more acceptance in the customer reviews. My wording may not be the best, but the key here was communication both ways!

Overall, I really like projects that encourage me to keep learning.