I’ve worked for a company that had a significant need for developers (18% growth per week sustained over three years). Most of the needs were not addressed by p

I’ve worked for a company that had a significant need for developers (18% growth per week sustained over three years). Most of the needs were not addressed by product team because no one had to time to notice them. So, some of the guys decided to use no-code tools to set up processes: Google Docs, Zappier, IFTTT were popular, connected haphazardly to the Reporting tools -- up to a point where half of the process complexity was hidden in those areas that the CTO had no idea existed. Was it good, scalable, usable? Not really, it was a heart-stopping inconsistent mess, but it held while the company was hiring. It gave to the newly hired product managers patterns to follow, experience in which processes to follow, impact estimates of what needed to be prioritised. I’ll readily agree that the circumstances were exceptional, and the communication with the product teams could have been more helpful, but the no-code approach provided prototyping. I can imagine a tech lead push back on some requests by asking project managers to implement some options with no-code tools and come back with more insights, before committing developper time.