Earlier quoted context omitted.
It's funny because microservices are explicitly targeted at solving problems for development with many teams, and lots of single team companies cargo cult them. Did they miss the first paragraph when they were reading up on what microservices are?
Who says only multiple teams need microservices, and who put them in charge of what people find helpful? If the 'app' has enough different 'bits' I'd favour a SOA no matter the team size. Somebody now wants to say that isolation doesn't necessitate distinct services; they're probably right, but the alternative is great discipline - why not make it easy? It's a form of defensive programming isn't it? - if widget facto…
If you can't trust your team to follow a process correctly, you're fucked in a way microservices can't save you from.