When is a microservices architecture actually a bad idea for a small to medium sized team?

We always hear about how great microservices are, you know, for scaling things up, deploying stuff on its own, and using different tech. But honestly, for smaller teams or projects that aren't, like, Google big, it feels like managing everything can just get too much, and the good stuff gets lost. I'm really interested in what people have seen in the real world. At what point, thinking about how many people are on a team, how complicated a project is, or how much traffic it gets, do microservices actually start causing more problems than they solve? What are the huge traps for smaller teams trying to do microservices, and when would you just say, "stick with a good old monolith, just make sure it's well-organized"?