First, a business analyst is a name that means different things to different companies. Some use “Business Analyst (BA)” and “Business System Analyst (BSA)” to describe the same job. When refering to a BSA, they have a stronger technical background.

 ".im assuming youre in a BA role already"

I consider myself a Generalist, able to take a project from Idea to implementation. I serve in various roles during the Project Lifecycle .... from Developer to Project Management ... depending what they need at the moment in a particular phase. Sometimes I'm the Product Owner and produce deliverables independently ... "Hey NitWitNick - go see what Sammy wants and help her out".

To be a BA and get things done, you need Great Soft Skills, Listening, Communications, Collaboration ... someone who can talk to both Technical and Non-Technical people. When you have both sides working with you (instead of trying to be a Stuck-Up, Tech-Talking Guru), then it is easy to do project work. Remember, you don't work in secrecy and then come out of a room with a hand-full of documentation and say "Develop This" ... you need to go talk to people, brainstorm, get project advice and see if you are on the right track with the users or not. Don't be afraid to ask questions ... you need to know the details.

Analytical skills would be next - analyzing the problem and suggesting a solution. This does not have to be technical, but has to be stated clearly for someone to understand what has to be done to solve a problem - (ie: a billing system: The total amout due for each month shall be displayed on the right side of the payment screen whenever 3 or more months are delinquent for customers with the exempt code "ZZY").

Documenting stuff for others to develop the system from. 

Remember - system work can go from Chaos to smooth sailing ... or the other way.