If you do, then that should be a sufficient motivator. If not, then prepare your exit.
Other questions to consider: Do you need the paycheck? Is this position beneficial to your long term career growth?
21–30 of 108 posts
If you do, then that should be a sufficient motivator. If not, then prepare your exit.
Other questions to consider: Do you need the paycheck? Is this position beneficial to your long term career growth?
You're not working with 0.1X colleagues, you're working at a 0.1X company. If that's too slow for you but acceptable for your manager, talk with them about it; in the best case, consider yourself free to spend the henceforth-saved time doing something else.
The members of your team are not reporting to you, so it isn’t your problem, or maybe isn’t a problem at all and the “big” company has enough money and people to get done what needs to get done at whatever pace is normal to them.
It's a job, if the execs are happy with the output that's enough, not everyone gets a hard on from typing code all day long.
Attempting to create accountability or meaningful changes to velocity in a “don’t rock the boat” org is usually a one-way ticket to workplace politics hell. If you value building things, small-startup style, you will likely want to avoid this.
Finding a good manager who is willing to give you special-mission style projects to execute on quickly and effectively is often a far better strategy than trying to deal with widespread molasses speed dev culture. Even better, typically, is moving to an organization where the culture and peers match up better with your desired speed and quality of execution.
There seems to always be a finite amount of completable work at any workplace. Let's say for purpose of your example it's 72 story points worth of work.
By completing about 30 story points yourself in a 4 member team you might inadvertendly end up taking work that could be comfortably completed by your team mates leaving them with work that is either very challenging or work that they are not motivated to complete.
At the same time they see you overperforming and basically "carrying" the team. Imagine yourself in your next job, after this experience, having a team mate that is able to do 400% of the work you can do.
Would you fight this teammate for the finite amount of completable work or would you sit back letting them do all the work ?