Ask HN: How to deal with a bottleneck like a shared public API project

We have microservices that our team owns end to end but for those to be used from our UIs we have to build public API routes/contracts in a separate shared project. Those pull requests are merged by a specific set of people in the company and it's always a bottleneck for us.

I assume this is fairly common. Here are some ideas I've had:

- hire more people on the shared project team

- redesign the public API in a way where the microservice team itself owns/deploys the routes that they "own" (hard to get API consistency this way)

What are some ways your organization has solved this?