Crikey, what on earth does that mean? In short, I take the needs of ordinary people and convert those needs them into a language people who make things can understand. Most of the time, these needs are met by software, but sometimes a simple, well thought out process works just as well.

So why do you bother? Quite frankly, some of the people out there who make things aren't very good at understanding what people want. It takes time to get good at making stuff. It also takes time to learn how to communicate well with people, to ask the right questions and to present information in the right way.

How do you do that then? You have to start by truly understanding the needs of the people you're talking to. If you find it difficult to understand them, then you're not asking the right questions. The key skill of any business or systems analyst is communication. Written communication, verbal communication, communicating in groups, communicating with individuals - it's all about the communication.

Any Tips? Of course. Be clear, be consistent and be transparent. Knowing things like UML and how to write IEEE 830-1998 compliant requirements helps, but brush up on your people skills first. Also know and understand that you're a cog in a much larger process, and the easier you can make life for the other cogs, the more valued you'll be.

Where do you do this stuff, and who do you do it for? I'm based in the Bristol Area, in the South West of England. I've spent the last few years working with numerous Public Sector customers to deliver high impact, high value solutions that meet their needs. The Public Sector presents certain enjoyable challenges, but I'm open to all comers.