First and foremost, I would keep the Four Elements Of Organizational Learning at the top as the metric for the organization to move towards the path of distributed architecture and then may be Microservices.

Is their communication cross-functional and inter-domain? Are they giving and receiving feedback within organization as well as from the customers on the products and services? Are those feedback shared, communicated? These activities are the foundations of learning organization where there is no boundary set.

Even legends like Martin Fowler advocate to build a working monolith first as the cognitive load of distributed systems supersedes exponentially.

A recommendation I always give is raise the monolith well before adopting Microservices.

To be distributed, it is not just about separating system but organization culture itself, how individuals functions, how they perceive situations and identify problems and build process to solve them.

Systems Thinking is an important view to understand the holistic feedback loops and reinforce positive activities to lower, and or keep balance, incurred technical debt while removing any organizational silos to promote DevOps philosophies that mitigates cognitive load in their work.

Comprehensive read. Good references. Thanks.