Hacker News new | ask | show | jobs
by mooreds 1064 days ago
Pretty simple:

* Find the problems

* Help with them

The problems on your new team are not the problems on the old team (code review, incident management). But I guarantee there are problems and ways to make it work better. So observe and ask to find the problems, confirm they are issues, and then start working on them.

Here's a non-complete list of possible problems for your new team:

* Too many things to build, hard to prioritize

* Not getting enough customer feedback

* Not getting the right customer feedback

* Unable or unaware of other company resources to improve their work

* Too few people to build what needs to be built

* Not staying consistent in technology

* Not exploring new technology enough

* Whipsawed by senior management with new goals every week

* Career growth stymied because they are stuck on a successful project

* Personality clashes

* Everyone does everything

* Everyone is siloed

Identifying the particular issues for this team and helping resolve them is what I'd focus on if I were in your shoes.