When teams look to improve how they manage their mobile release cycle their attention often focuses on tooling, which from there usually makes a quick turn to CI/CD, which can feel like a great spot to pile on various automations for the wider mobile dev lifecycle.

Or so the thinking goes.

But the idea that your mobile org will just hum along if you spin up a fancy bit of tooling is alluring, but the reality is that CI/CD is just one piece of a complex puzzle. And teams often get caught up on just this one piece of the puzzle in a way that clouds the bigger, more human picture.

Automation as a “north star” used to make more sense.  But these days most of it is lower-hanging fruit and the disproportionate focus on automation as the be-all end-all keeps teams from engaging with more complex, foundational work.

Solutions to the tough stuff — the human factor, the way team members communicate, build together, collaborate — can’t be automated away. How can you better equip your team to solve these more difficult problems?