Big ideas

Let’s consider a model for how organizations should be prioritizing their work and investments in the Microsoft Cloud. The imperative here could not be greater. Technological advancements are now moving on timelines that in some instances can be measured in weeks. Not months. Not years. But weeks. This both accelerates and is accelerated by the shift to system-based value. In other words, getting the platform ecosystem right in an organization is both necessary to creating the greatest likelihood that the organization can absorb rapid innovation, whilst simultaneously creating the conditions that drive that rapid innovation forward. But too many organizations have misallocated their focus up and down the value chain, prioritizing workload implementation either at the expense of or out of ignorance to architecting strategic foundations, building the platform ecosystem, and creating the conditions for success. That’s a bit esoteric, so let’s visualize this phenomenon as the “strategic pyramid”…

I have come to understand strategic thinking as more art than science. Strategy is surely informed in part by data, but I find that our society in general and the technology industry specifically too often confuse data and wisdom, that we foolishly (though understandably) seek heuristics or processes so that we can turn the art of strategic thinking into a game of color by numbers so simple that anyone can do it. When it comes to strategic thinking, better that we seek methods of framing our thoughts rather than shortcuts to the answers themselves. So in this piece I have sought to offer practical approaches to injecting strategy into your organization’s Cloud journey, indeed, a selection of the same approaches I take with my clients.

Too many organizations are still struggling to go big with Power Platform not because of limitations in technology, but because of their own outmoded ways of doing business, though I know of no other move that IT decision makers in organizations across the economy and around the world can make that is likely to achieve results of this magnitude by—in effect—doing more with less. But the benefits of adoption are often dampened by three big, non-technical reasons that I see so many organizations failing or underperforming in their scaled, enterprise Power Platform adoption.

The Power Platform Landing Zone is the beginning of the path to overcoming these barriers. A foundation, if you will, the Landing Zone is the initial technical infrastructure plus governance of that infrastructure that allows an organization to begin “landing” workloads in Power Platform. With that in mind, a while back I set out to create a reference architecture for a Power Platform Landing Zone. In other words, if an organization were to build their Power Platform infrastructure properly, it would look a lot like this reference architecture.

Here we’ll lay out a common framework (which we’ll refer to as “C-Frame”) for managing Power Platform solution development. This approach is best suited for solutions that classify as important or critical according to the Environmental Architecture Model found in the Power Platform Adoption Framework. If you take nothing else away from this approach, let it be this: Solution development of important and critical workloads produces far better outcomes and is significantly easier to manage when your team has in its own way accounted for all of these project activities.

We are experiencing a seismic, generational transition in the way that organizations buy, use, and enable their own success via technology. We’re now living in the Cloud Application Platform era, wherein organizations plan more strategically, make technical choices today that reduce the risk of being painted into a corner tomorrow, absorb new requirements rapidly, better fix costs across their ecosystem, and buy down the risk of unknown future needs. That’s what the Cloud Application Platform is all about.