Confidently defending your turf

- If your work title has phrases like data science, predictive analytics, or advanced analytics in it, you should realize that not everyone is going to define your role the same way. In fact, maybe your title was really quite vague, but you belong to a team with one of those phrases in its name. In fact, very possibly, your role has a description that has never been reduced to writing. The way your role was described to you during interviewing might not match the reality of what your role has become. Do any of these sound like issues that you might be facing at work? If you only share your concerns with your friends, you aren't going to resolve them. You're going to have to discuss them with your management. Most likely you face these challenges because your organization may still be struggling with analytics in general, and who should be assigned which projects. As a result, you may get projects that aren't really what you signed up for. This is a very difficult position to be in. Nothing is going to make it easy. But you can take some solace in the fact that you are not alone. Arguably, the majority of data scientists feel this way. Typically, what's happening is that the data science team takes on the backlog of BI and IT. If your boss is an analytics middle manager, they're afraid to turn down the work because they want their boss to know that the team is busy. That leaves you walking a tightrope of being a team player while trying to map out a career path that will get you increasingly involved in the kinds of projects that you will find rewarding and challenging. So proactively describe the kinds of projects that you have in mind. Remind your boss of the kinds of things that you discussed during interviewing. Perhaps suggest some projects that you think would benefit the team and the whole organization, show initiative. Chances are good that you your boss wants this for you too but he's having trouble getting senior management aligned with the mission of the team. Consider describing what you would like your role to become over the next year or so. Try to be willing to play along somewhat between now and then. But at the right moment, perhaps during review periods revisit this topic. Now there is one way that you can risk going too far. If you will only do the fanciest algorithms using the latest software, you aren't giving your boss much room for manoeuvre. But what is reasonable is to work on projects that showcase your analytical skills, focusing on projects where something is being predicted. Take on that attitude and work hard and you increase your chances of being taken seriously as a predictive modeller.