It's often the product team's decision. Anybody can spin up a Git repo when they need one. There's freedom there, but you miss out on a lot of tooling and healthy discipline by doing so.

Once you're in the mono repo, you have to play by its rules (well...should anyway). Like in the case of npm packages I mentioned above.