Broadcom Knights3 min read

The Best VMware Cloud Foundation Deployments Start Way Before the First Click

Photo for Gareth LewisGareth Lewis
3D cloud icon glowing on a circuit board with blue and purple lighting, representing cloud computing infrastructure and digital transformation
An ongoing blog series by our Broadcom Knights, an elite group of Partner Technical Professionals with deep technical expertise in Broadcom’s portfolio and recognized as experts in their field.

The Siren Call of the Click-simple UI

The easier a technology becomes to deploy, the more dangerous it gets. That is the Planning Paradox, and nowhere is it more visible right now than with the new VCF Installer in VMware Cloud Foundation (VCF) 9. This interface is, quite frankly, brilliant – a ‘click-simple’ solution that replaces the legacy Cloud Builder and manual worksheets with automated deployment workflows.

The paradox is this: the simpler the technology becomes to deploy, the more tempted teams are to skip the rigorous discovery that makes that deployment viable. There is an understandable urge to dive straight in, hitting next-next-next to see a private cloud appear in hours. However, as a Broadcom Knight, my mantra has been and always will be, that it’s all in the planning. While the technology is proven and automated, a lack of deep environmental validation remains the primary cause of project failure. Success is decided in the discovery phases, long before the first server is ever racked.

Navigating the Guardrails: The Workbook as a Shepherd

The most critical utility in a VCF 9 architect’s arsenal isn’t actually the installer; it’s the VCF 9 Planning and Preparation Workbook. This isn’t just a static collection of fields; it is a dynamic environment specification utility that acts as your source of truth.

I often describe the workbook as a shepherd. It provides the technical guardrails that prevent you from jumping across lanes and into an operational failure. If you try to step off the validated track by inputting a configuration that the platform can’t support, the workbook logic tells you ‘no bueno’ long before you start the automated engine.

An example would be if a team ignored the workbook’s emphasis on DNS hygiene. If they were to assume their internal records were fine. But VCF 9 requires bidirectional lookup for every single management component. The resulting carnage during the pre-validation check could stall the project for days – burning through budget and goodwill in equal measure – while legacy PTR records that should have been caught in week one are cleaned up. With both the VCF Installer and the Planning Preparation Workbook protecting us via the guardrails from Day 0, you ensure a fully rubber-stamped solution that is consumption-ready almost immediately.

From Building Stacks to Delivering Outcomes

To achieve true cloud agility, we must adopt a discovery-first mindset. This means moving away from simply building a stack, to developing an outcome-led design.

When I meet with a CTO, I don’t start the conversation with technical specifications; I start with their business intentions. VCF 9 allows us to perform intention mapping, where high-level goals are translated directly into technical reality. Take data sovereignty as an example: that single strategic imperative maps to specific network segmentation decisions, jurisdiction-aware workload domain placement, and encryption policies – all of which must be locked in before the first line of automation runs.

The Discovery Process has Three Layers:

  1. The vision: We document the target state, identifying quick wins such as VCF Automation to prove value to the business immediately.
  2. The bridge: We use discovery to bridge the gap between current technical debt and the idealised future state.
  3. The team: This shift requires a unified platform team that owns the workbook together, breaking down the traditional departmental silos that often lead to ‘lane jumping’ and configuration errors.

Avoiding the Shelfware Trap

One of the greatest risks in any enterprise software deployment is the shelfware phenomenon, where organisations acquire licenses but fail to realise their full value. With VCF, this looks a little different: one license now gets you a lot more technology, but complex components often sit idle because the operational model isn’t ready. The planning paradox strikes again – this time not at the deployment stage, but afterwards.

The correct journey to VCF 9 mitigates this through a structured ‘crawl-walk-run’ adoption which is, in essence, the planning paradox solved operationally:

  1. Crawl: Establish a stable management domain and foundational operations.
  2. Walk: Release operational efficiencies through the creation of workload domains, isolating production from development.
  3. Run: Transition to a true cloud-like consumption model using Virtual Private Clouds (VPCs) and self-service portals.

By following a prioritised implementation plan, we ensure that the private cloud evolves at the same pace as the organisation’s maturity. This prevents the project from stalling and ensures a continuous return on investment that justifies the strategic pivot.

The Strategy of Certainty

Successful VCF 9 implementation is not a technology upgrade; it is an organisational shift towards predictable agility. Rigorous discovery and planning are the prerequisites for delivering an on-premises environment that finally rivals the public cloud experience.

As a Broadcom Knight, my role is to provide that safety net – the one that sits between a brilliant piece of automation and the environment it’s about to land in. By combining expert-led planning with the platform’s prescriptive architecture, we transform a box of software into a strategic engine for business innovation.

So, if you want a validated, standardised, and hardened environment that gives you the public cloud feel with private cloud certainty, it’s VCF every day of the week. Just make sure you’ve done the work before you hit next.

Read More from the Broadcom Knights