Everything you’ve learnt at work and in training about doing good business analysis is about writing the specification, delivering on the requirements, getting the quality right, doing the specific thing for the specific technical purposes.
“What do you do” is about a title, a task, a deliverable thing.
Consider this job description from an insurance company:
Understanding the business requirements, and through a structured process, modelling, validating and translating it into business requirement specifications that are used by developers to craft a technical solution.
Work on solutions supporting multiple business areas, integration points and a large number of affected components. Required to work under general direction within a clearly defined accountability framework. Gather and interpret requirements from the business. Participate in the solution design process. Prepare the requirements specifications. Define the success criteria for solution testing. Analyse and decompose relevant business processes. Performing business analysis and process improvement within assigned solution project. Provide assistance to solution delivery on implementation and training. Assist (when necessary) with systems testing. Ensure that proposed test solutions cover all aspects of delivered business specification
While this is the description of a job, it’s not the description of a dream or a desire. While it’s specific, it could easily be altered without changing what it delivers.
This is how education works as well. MBA degrees are meaningless. It’s the doors that they open that we strive for.
The same is true of your product or service. You may say you’re building a feature, but don’t believe it. When you’re enabling business change, you’re offering your stakeholder a new opportunity, a step closer to their dreams and desires, not a feature.
We enable change, utility, possibility, not tasks or papery stuff.