My Job

This is from a recent assignment I submitted. I thought it was relevant and decided to share. Enjoy!

~~

Business Intelligence Developer Position

My position is a Business Intelligence Developer, which means that I build analytical database systems, which allows business people to make better decisions based on the improved visibility into the measures of their business. I first started this career as an analyst building reports in Microsoft Excel. My curious mind and ambitious nature lead me to quicker and more efficient ways of delivering these analyses. Ten years later I have built many relationships, done consulting, presented at many events, and am currently working on my first book. With that context provided, here are my interpretations of how my position measures up against Hackman and Oldham’s Job Characteristics model.

Skill Variety

Business Intelligence is a highly specialized field. This field still contains however, much variety. From a pure technical perspective, being a Business Intelligence Developer can require Relational Database Management Systems (RDBMS) knowledge, Multi-Dimensional Database Design (OLAP), Extract Transform and Load practice (ETL), and presentation layer / report design. Doing the job of a Business Intelligence developer well also requires a solid understanding of the business. This is where Business Intelligence is unique in its attempt to bridge the gap between the business side and the technology side.

Task Identity

In small BI shops, the BI developer may be responsible for designing, building, and delivering the entire solution. In larger organizations, the one I work in, tasks are a bit more segregated however goals are still defined at a team level which encourages the team to work together and gain an understanding of the entire process.

Task Significance

The goal of Business Intelligence is to improve decision making in the company that eventually leads to increased revenue, reduced costs and increased profits. The correlation between BI efforts and these eventual outcomes however, is not always so clear.

Autonomy

Similar to most Business Technology Services (BTS) projects, Business Intelligence traditionally is managed from a program and project approach. Programs define the strategy and overall goal of the BI program while projects make up the individual deliverables all working towards the same goal. Depending on the project management method being used (eg. waterfall or agile) it can be difficult to have much autonomy over organizing your tasks. In my position we are lucky to use an Agile project management methodology that allows the core team, including myself, to have a great say in what tasks are required to do my job well.

Feedback

The most common way feedback is received by the BI team is when something goes wrong with the nightly ETL processing that updates the data in the presentation layer. This feedback of course is always negative however, positive feedback is also received when the data is on time and accurate. There is some gray area here where no feedback is given and the data being presented is assumed to be correct when in fact it is not. This is why we have placed a laser like focus on the quality of our data being presented.

Where to improve

Since I have had a lot of input into the processes and procedures, we have in place currently it is difficult for me to say where we can improve much.  I will note however that the challenges we face with relating task significance and feedback are common among all Business Intelligence programs and can always use some more attention.