If you want to provide the most value and impact possible, it depends on the project.
If the project is actually not addressing real business value that users will benefit from, then pointing that out and learning about how businesses work and provide value, in general, will be useful.
Is your team/organization struggling to release projects on time? Or perhaps they take a long time to get out to users? Then looking at more agile / iterative approaches to the entire product cycle might help.
Basically, find a problem and learn about that thing. The farther away from code and closer to business outcomes and strategies it is will mean more impact.
For example, what has more value? Helping your dev team figure out how to write to a file? Or helping your team deliver software projects faster (using devops, agile like tools, etc.)? Or helping your entire org realize it's marketing to the wrong market all-together?
So basically you are suggesting that every project is different.
So I should investigate which specific problems the organization is facing.
Then I pick the one closer to business outcomes.
And then what?
Present a solution(just a plan) to all the team, maybe?
I would need to convince them that we need to spend time on it.
————————————
That is great, sounds like a good plan and makes me think that the hardest part is convince the team.
So that is a key skill that I could practice, without the ability to influence the team the previous steps would be a waste of time.
If you want to provide the most value and impact possible, it depends on the project.
If the project is actually not addressing real business value that users will benefit from, then pointing that out and learning about how businesses work and provide value, in general, will be useful.
Is your team/organization struggling to release projects on time? Or perhaps they take a long time to get out to users? Then looking at more agile / iterative approaches to the entire product cycle might help.
Basically, find a problem and learn about that thing. The farther away from code and closer to business outcomes and strategies it is will mean more impact.
For example, what has more value? Helping your dev team figure out how to write to a file? Or helping your team deliver software projects faster (using devops, agile like tools, etc.)? Or helping your entire org realize it's marketing to the wrong market all-together?
So basically you are suggesting that every project is different.
So I should investigate which specific problems the organization is facing.
Then I pick the one closer to business outcomes.
And then what?
Present a solution(just a plan) to all the team, maybe?
I would need to convince them that we need to spend time on it.
————————————
That is great, sounds like a good plan and makes me think that the hardest part is convince the team.
So that is a key skill that I could practice, without the ability to influence the team the previous steps would be a waste of time.
Thanks for your feedback!
Yes, convincing the team or manager is the hardest part. 😂