Think business, first.
You need to define a clear and concise business use case for your cloud projects before you build your landing zone. Which teams, users and customers will be affected by it? What is your roadmap for cloud migration into this landing zone? Will these future plans cause increased bandwidth and architectural requirements? What business outcome are you trying to generate with it? And how will you measure success?
By answering these questions, you’ll have a series of objective insights that will inform all your upcoming design and deployment decisions.
With this approach, your cloud environments will be easier to adopt and more relevant to the business, and your users, for longer. By understanding which teams will be using it and for what purpose, you’ll also be able to prevent “architecting yourself into a box,” which means building a landing zone that simply doesn’t meet the actual needs of your users and soon becomes irrelevant.