Our company is starting to set quarterly goals at a more individual level. For many engineers on the team, these goals will include product impact, automation and code coverage, new responsibilities, etc. I am considering working with individuals to set quarterly story point goals as well. On the surface, this makes sense: as a team quarter to quarter we're always trying to improve velocity, so it makes sense to attempt to improve velocity at an individual level as well.
However, I have reservations (... as evidenced by the fact that I'm asking a question on Stack Exchange... :) ). Completing stories is generally a team effort and relies on different roles within the team (engineering, design, QA, etc) coming together, so the goal isn't entirely within an individual's control. I also wonder if setting these individual goals creates a bad culture within the team where people are optimizing for individual story point credit rather than total team accomplishments or velocity.
Does anyone have experience in this kind of set up, or have knowledge on whether it's a good idea or a bad idea?