You’re answering the wrong question
A new project lands. The team asks “Which cloud?” and the answer is almost always public cloud by default. That question assumes the destination before anyone checks what the workload needs. Placement becomes a habit, not a decision.
The better question starts with the workload. What does it need for performance, compliance, cost and latency, and where does that lead it.
How cloud-first became a reflex
Once cloud-first became policy, it stopped getting questioned. Every new workload inherited the same answer. Speed at the start hides the cost at scale. Placement decisions made for convenience become permanent by inertia.
Cloud-first solved a real problem: how to move fast. It just kept answering a question nobody was still asking.
The four questions that should drive placement
1. Performance – Ask what the workload demands for compute, throughput and reliability
Some workloads run best on high-performance private infrastructure, not shared public tenancy.
2. Compliance – Ask where the data must live and who can touch it
Data sovereignty and regulatory requirements often rule out certain environments before cost even enters the conversation.
3. Cost – Ask what the workload costs to run where it sits, including data egress and bandwidth charges that public cloud adds at scale.
Predictable cost matters as much as low cost. A workload with heavy data movement can quietly drain the budget.
4. Latency – Ask how close the workload needs to be to users, machines or data
Latency-sensitive workloads belong at the edge, near where the work happens, not in a distant region.
See placement as a spectrum, not a binary
“Public or private” is the wrong framing. The real answer spans private, public and edge, workload by workload. You match each workload to the environment its requirements point to, then govern all of them consistently.
The unified operating model is what makes intelligent placement possible instead of chaotic.
The answer is rarely one cloud. It’s the right environment for each workload, run under one operating model so choice does not become complexity.
Conclusion: Change the question, change the architecture
Stop starting with “Which cloud?” Start with “Which workload, and what does it need?”
Rule: Placement follows requirements, not preference.
The question you start with shapes everything that follows. Ask about the workload first, and the architecture answers itself.
