View Recording: Pro-Code Meets Low-Code: Navigating the Full Stack Seamlessly

Brian Haydin 0:06 All right. And we are live for a second time. Welcome. Welcome everybody to the today’s webinar. Today we’re gonna hike a little bit through some punch cards all the way through co-pilots and. Talk a little bit about procode and how how procode meets the the low code you know area. I’ve been thinking a lot about this. Right now I’m actually in Europe and I love doing these like webinars from like weird crazy places. And you know, I’ve been having a lot of time to think about, you know, how this technology set is really evolving and what changes to be prepared for. So anyway, so today’s our little journey and how we’re going to fuse everything into one little seamless stack for those of you that haven’t. Haven’t listened to me or met me or had a chance to see someone of my webinars. I’m Brian Hayden. I’m a solution architect here at Concurrency. I’m definitely an outdoor aficionado, an addict, if you will. And so whether I’m fishing like Michigan for salmon or landing an AI project in my net, you know, I try to use these outdoor analogies and map, you know, map things to things that people can understand. Picking the right, you know, picking the right gear and the right ecosystem. There’s my QR code, a link to my LinkedIn. Please feel free to reach out to me if you have any questions. You want to chat about technology in general. This is something I’m just a nerd at heart. Fun little fact about me, I’m a twin. So you can see there’s two of me in the top right. That’s actually not two of me, it’s my other half. So, all right, so I’m going to start with the punch line here, actually two punch lines I’ve got. So I thought I’d do it a little bit differently and get to the closing argument and then walk you through my journey. So first point that I want to make is that I don’t know if anybody’s heard of fusion development or or this terminology yet and we’ll get into some of the description of it, but the future is fusion development. I see that cross-functional teams are going to be not just in the agile sense. Of cross functional teams with developers doing testing and testers doing other aspects of it. I’m talking about the whole stack of fusion teams working together with business owners, with developers. Citizen developers and working with IT professionals like DevOps or security, SecOps, you know, type of things. Think of them like a like a mixed party. Citizen devs are like the easy, you know, kind of switch backs. They kind of handle like most of those. Those are easier scenarios, but like if you get into something a little bit harder like you know a Cliff wall, that’s where like the pro devs are going to come in. And the other topic or the other point that I wanted to make is our programming language is dead. I made this comment a couple of weeks ago. At a talk that I was doing and I’ve really started to think about this more. And the big names out there, like people that we all should know and respect, are blunt. The next programming language is going to be English. And so you can see the list of of quotes here and how recent they’ve been made. But NVIDIA, our job is to create computing technology and so nobody actually has to program. The language is human. The hottest new programming language is English. That’s Open AIX, Tesla. A I may reduce the need for developers to code, possibly within the next 24 months. A WS and then I put myself up there with the important people, but this is my prediction. Languages like traditional programming languages like Java. And.net will be niche skill sets. They’re not going to be gone, but I think that they’re going to be niche skill sets, just like you would think that how you look at it with assembly, you know, work today still exists. There’s still use cases for it, but it’s not something that people really do a lot in. So you know I I that’s where I can I think the future is and the rest of this talk is well the next probably 20 minutes of this talk is about why I got to that conclusion and then we’ll we’ll talk about how to apply some of this in in like a real world scenario. But at the end of the day, English language is going to be the next programming language. Actually it could be Latvian or it could be Polish too. So, but human language. So let’s talk about how we’re going to get there. So here’s a trail map I’m going to give you. We’re going to do a little history lesson. I think it’ll be kind of fun. I want to look back at the last 80 years and then I want to bring out the dictionary and make sure that we’re all talking about the same topics when we get to do a little bit of that. Let’s take a look at why I think that procode and low code are converging and we’re going to do that by looking. At Microsoft Stack and what they’re actually doing in that ecosystem. And then for the last part, I’ll go through a scenario. It’s got 3 stages to it, so 3 use cases built on the same thing. And and then we’ll talk about like some of my key takeaways. In the meantime, if anybody has any questions, you know that you want me to answer or something like that, drop them in the chat, drop them in the Q&A. I like being ad hoc and getting good questions thrown at me. So all right, so I’ve got a timeline here and this is an 80 year timeline showing every sort of major milestone and abstraction layer. I was trying to build one of my own and I found this found this article that I thought was, you know, pretty intuitive and and laid this out and actually did it much better with the graphics than I could, but all the way back into the 1940s when we started having machine code. You can see that we’ve gone through assembly language, compiler, structured languages, object oriented languages that we started getting into component, you know type of development and finally in the the mid you know 2010s you know we started getting into these. Lower code environments, which I wasn’t a real big fan of, but at this point I’m starting to really have a lot of respect for the capabilities these things have, but there’s still some isolated use cases where. Or specialized use cases where I’d want to consider it. But key point here is that like software engineering has continuously been evolving into higher levels of abstraction and that’s been the progression. So where’s that going to take us in the next, you know, 10, you know, 5 or 10 years? But in the early days of programming, it actually meant like things like flipping switches, like a dude, you know, would take a wire from 1 box to another and that that was how programming was done. And so, you know, I I tried to imagine myself like being a software engineer. Writing machine code as if I was sitting in a breadboard, which I’ve, you know, done some of that stuff too, but it’s it’s very tedious. It’s very manual. It’s a lot of like trial and error. You burn out some LED lights and switches and fuses along the way and it becomes, you know, it’s almost like hacking your way through. You know the jungle with the machete. So along came assembly languages, you know, so that offered a little bit of like mnemonic codes instead of binary. It wasn’t as painstaking, but it was, you know, it was a little bit better. You know, then frying out some circuit boards. Every time you want to make a code change, you actually have something that you could persist. And so punch cards, you know, punch cards and assembly language we started getting a little bit away from. You know those tools, you know, directly with the hardware, like absolute hardware control. Then in the 1950s and 1960s, you know, started to introduce languages like Cobol and Fortran, which are still around today. Surprised. Not so surprisingly, but somewhat surprisingly. And a little fun fact about myself. The first programming language I ever did, like in a real sense, was was Fortran. That’s where I got the bug to to become a software engineer. But it wasn’t in the fixed 50s and 60s either. That was much later than that. But you know, these languages came along to make it easier for software engineers to write in more human readable ways so that, you know, they could think about solving the bigger problems, right? Rather than like direct registers, they’re trying to solve the business problems. So if I was thinking about this like in like my wilderness analogy, you know, we’ve got this bridge that we have to cross and it’s great because it gives us access to cross this big huge valley, but it’s going to get me to the place where like that’s closest to where I’m going to be, not to the exact place that I want to be. And that’s what these higher level languages did. They gave you, they gave you easy procedures and you know, more compartmentalized code that allowed you to focus on like the business things that you needed to do and but it didn’t, you know, it didn’t quite get you to to like some sort of Nirvana. Object or oriented programming gets you a little bit closer and with the rise of languages like C++ and Java and ultimately like C# that let us really just focus on the business layer and the business logic and not actually even having control over memory addresses. On C++ maybe, but not like C# and Java. So we kind of got away from that. And again, like this layer of abstraction around the hardware allowed us to focus on business problems rather than, you know, focusing in the hardware itself. And then in 2015, the mid 2020 or 2010s I should say. You know, we start to see some real investments and real opportunities in like low code platforms. And so using that same like I’m trying to get, you know, to this little mountain top on the other side of this valley, you know, kind of analogy. I don’t really care that there’s a bridge or not a bridge at the end of the day. Like I’m just saying I got to go there and and I’m going to have a shuttle that takes me there. It’s not going to be. I’m still going over the bridge, but I’m I’m sort of unaware that there’s a bridge, you know, it’s taking me there. I’m just sort of on this journey or on this ride. But I have no real control over how it’s going to be accomplished, but I don’t need to have control of it. Just want to get on the other side of the valley. So in 2015, Power Apps, you know, kind of came out and you know we at Concurrency have been playing around that since, you know, since started. And I found a lot of value, especially in things like Power Automate and you know, being able to whip up some some applications. But you know, it’s definitely nice to have the visual design and pre-built, you know, connectors, but there weren’t a lot of connectors that were available at first. And it’s integral or it’s really ingrained into the Microsoft platform and didn’t have a lot of use outside of that. So if you’re trying to build, you know, something for consumers outside of your organization, it’s probably still not the best tool, but. But you know, back when it started, it really wasn’t made for something like that. It’s gotten a lot more mature and especially after around 2020, it started taking on a lot more mainstream use cases. And today we’re really, you know, I’m really finding that most of my customers are doing. Some work in the Power Platform, maybe not in Power Apps, but definitely in Power Automate and even in Copilot Studio to take advantage of some of the low code frameworks that are available to you. So what does that mean like in the future? So now we’re starting to see co-pilots and agents and applied pretty evenly between like these pro code and low code environments. And so you know these generative coding assistants, I think you’re going to step in. To help us and narrow that gap quite a bit. So we did this talk a couple of weeks ago about using the Power Platform plan to build applications just using business requirements and natural language. And then we also did another one talking about copilot agents in more GitHub copilot agents and talking about how we can use natural language to instruct software engineering tasks or software engineering agents to be able to go out and do code for us. So I think that those two things are going to converge pretty quickly and we’re just going to be talking to some sort of a software development agent and it’s going to go and figure out what’s the appropriate tool set it needs to use in order to accomplish its goal. So here, like in this, you know, analogy, I’m not even aware that there’s a valley. I just needed to go someplace and I’m telling my AI assistant I need to go to this mountain and I walked through some magical little portal to get there. I thought it was kind of like, you know, an interesting way to look at it, but I do see that. You know, this is kind of the next step in software engineering is going to displace like all this structured code and allow us to just basically say here’s the problem I’m trying to solve and here’s the rules that I need you to adhere to and have it write the computer instructions. That are necessary in order for a user to be able to accomplish those goals. And why I’ve I’ve really started to believe this is looking back at, you know, all these different abstractions that have been put onto it and put onto it, put onto it. We’re slowly getting away from any kind of understanding of how the computer necessarily has to work. And just saying this is what the system is that you need to look like and and I see that, you know, getting rid of structured language as a barrier to some of the things you might want to do is probably the next step that’s going to come along. So I said we’re going to do a little dictionary exercise too. So I want to make sure that we’re all talking the same language for a little bit. And so I’ve got a couple of things that we’ll we’ll define. We’ve got this idea of procode and low code. I’ve dropped this out, those two words out there a little bit. So let’s First off just quantify what I mean by procode. So by procode I’m talking about traditional software, you know, development.net, C#, Java, Python, JavaScript. These are all programming languages that are the what I would consider the professional programmer’s toolkit. You know, typically requires an advanced degree, you know, and you know, or at least some sort of a training degree, I should say. And pros and cons to it are that I’ve got full control over the development ecosystem. If I want to do something that’s crazy, I go and either. Either find, you know, find a third party library that does it for me, or I create another library for myself. I can control the performance, you know, by refactoring my own code or making decisions around, you know, hardware. I guess if you want to think of it that way, like that might allow me to do things more performant. And generally speaking, when I do things in a procode, I’m I’m actually defining containers that I’m going to deploy so I can build a much more scalable system. In that case, the cons are it’s definitely more time consuming for you to build it and you know you can’t just have. Johnny off the street come and write these kind of codes. Overall, you’re gonna spend a little bit more time. It’s your code. You built it. So if it breaks, you fix it. A lot more maintenance costs. And let’s compare that to the low code. So in low code, I’m talking about things like power apps, whether that’s. Like Power Pages or traditional like Power Apps, you know apps, things like that. Power Automate, Copilot Studios in that same story. I would look at Dataverse as being something that is definitely lower code. Tool and and then Power BI as well. The nice part about these very very fast delivery mechanism. I can I can spin up an entire app in a couple of hours, you know add some business rules. And and nowadays, I don’t even really have to have a lot of understanding how the ecosystem works. I just have to have access and I can type in some instructions and it’ll build it out for me. And it’s great for that kind of like rapid prototyping, building internal applications. Some of the cons, you’re more or less dependent on the connectors and the. Our platform that are available to you, you can create custom connectors, but that’s typically now you’re bridging into the pro code and we’re going to get into that, but you’re kind of limited there. It does have very it’s more limited in the ways that you can control the performance. And it’s basically I need more performance, I’m going to have to buy more capacity, I’m going to have to buy more more SKUs, but I’m I don’t really have the ability to distribute it across multiple workload or multiple containers like it would in the pro code environment and so. You know, kind of pro and a con. I don’t have to manage hardware, but I also can’t manage hardware to get performance. And then you know the last part about it is is like this application sprawl, you know in the power platform and. We’re seeing quite a bit of discussion around this with organizations right now and it reminds me back in like the mid 2000s when everybody was building access databases to solve some sort of a business problem and this one client that I was working in at the time is. Funny little story, had an initiative to go out and clean up all of the access databases within the organization. Like full stop. No more access, no more shadow IT shadow applications. We’re cleaning all that stuff out. And then probably about three or four months after they got done cleaning all this up, they had an initiative to find efficiencies. And the person that won this little challenge that they had actually created a new access database app. And so the sprawl, you know, started over again. But that does happen and there’s strategies that we’re coaching customers through to help with this application sprawl in the low code environment and it is, but it shouldn’t prevent you from encouraging your employees to solve business problems. On their own. It’s just about how and what environments you’re gonna let them use to solve which types of problems. So best time for procode, best time for low code. I think if you wanna do some rapid prototyping. You know, and it’s going to be kind of internal only. Definitely I would start with the low code, find out what your limitations are going to be and then invite procode into it. And then you know for procode, you know if you really are going to be doing some sort of deeper on like really out there new. Setting edge technology, you’re probably gonna land in the procode to begin with, you know, so that’s a good use case for it. Very complex, very scalable systems. You know, anytime you’re gonna be working with external customers directly, I would say is you know you’re gonna want to consider the procode environment. But you know, those are some of the the sort of decision points. And the other thing I talked about was fusion development. So I want to make sure that I I talk a little bit about this. Not a really common terminology yet, but it’s not really a theory, it’s a strategy around people. So it is kind of an extension of agile development where we’ve added citizen developers and pro developers into our toolbox or our team composition. And so our core personas for a fusion. Team is really gonna be the citizen developer doing business apps that could be Power Automate, that could be Power BI, it could be Power Apps and pro developers that are gonna be doing some of the more advanced things like Data Factory jobs or Azure functions building APIs that the custom connectors can. That the custom connectors are going to have to leverage those types of workloads that are going to support these different use cases that we want to build. And then we’re not losing it out of any of this. They’re still going to help us secure and govern our environments. And help us make sure that we can keep the application lights on and running. So they’re important as well. And then I added the business owners here as well because I think there’s, you know, when you think about an analyst, you know, a citizen developer is probably gonna be somebody at an analyst level. You know, developing in a low code environment without a lot of like software engineering background. But the business owner, there’s still people there that know that the systems inside and out. And more importantly, they’re people that are going to be able to make decisions about how the a new system or a new thing should work. So these like. Four different personas are all gonna work together to work in a multidisciplinary, you know, kind of collaboration. Everybody’s pitching in pro codes, doing low code, low codes doing pro code, and they’re gonna leverage each other’s like expertise in order to to fulfill. Some sort of shared goal for the organization and without any like real predisposition to using Power Platform or Azure you know as a deployment mechanism. So I think we got those definitions and I wanna talk a little bit about the Microsoft stack as well before we get into, you know, our like our last little kinda ideation and what it would look like in the real world. So, so Microsoft stacks kind of changed over the last couple of years, especially over the last couple of years and in like 2020, so just like five years ago, if you wanted to do development, you had to make the choice kind of at the beginning and it was like, am I going to do low code or am I going to do pro code? There were some overlaps because this idea of connectors and APIs have always been there, you know, but you know we’re going to talk about a couple of like more advanced things where those those integrations that overlap is getting a lot cleaner. But you really can’t animate that choice and once you made it, you were sort of. There you weren’t gonna go back. It would just be a complete rework to switch from pro code to low code. Today though, you could start in either place and you could migrate certain components to it pretty seamlessly by just having. The the good practices we typically do today in software development. So I could leave my front end, you know, in Power Platform and kind of convert things to more of a service oriented architecture using, you know, APIs or vice versa. I could like, you know, just you know. Want to do something in a more advanced front end because they get better customer facing you know kind of actions but leverage the power of like low code you know ecosystems you know to do some of the business logic as well. So you don’t have to like choose anymore. You can kind of like mix and match if you want to and so. Help. Sort of understand that the new Microsoft Dev Stack is like the whole toolkit, like layer by layer it’s everything. So at the application I’m not just doing app services and Front Door, I’m using the Power Platform, copilot Studio, Power Pages, Power Apps as like my application. And I don’t even really have to care about too much about the data either, because we’re starting to abstract a lot of that, and a good example of that is Microsoft Fabric. Fabric supports all sorts of different database types now with. SQL databases, Cosmos databases as native components of Fabric, but still having kind of a unified system to be able to track and interact with that information. We’re starting to see like this data layer abstract quite a bit as well. And then from a watch perspective, you know, I’ve already touched base on this that you know. We could use logic apps, we could use Azure Functions, Power Automate. These are all sort of built in the same infrastructure and underlying components. And so the icons from the procode and the low code, they’re more or less like interchangeable and kind of proved that these. Silos are kind of gone that we can make these decisions and play with them. And so how do I know that that’s the case? So this is, you know, some of the latest like drops from Microsoft over the last, you know, four or five months. Some of these were at build agent orchestration and copilot studio. Haven’t been able to play around with it yet since it’s still in private preview, but yeah, you can wire up copilot agents to agents and some of those agents could be, you know, in AI Foundry and some of them could be native in copilot studio, but you can connect all these different agents. You also had the ability to develop your own models or decide and pick and choose which models you want to use. So in in the the Power Platform you can now bring your own models and fine tune them in Azure AI Foundry. So that they apply really directly to your use cases. Those agents can now be used inside of Power BI, so we’re having a lot more ability to be able to chat with your data and. The pricing model has changed a little bit more towards that consumption model that you would see similarly like in in Azure around token counts from Power BI. So you’re seeing a lot of these like you know it’s doesn’t really matter if you’re in the Power Platform or in Azure, things are starting to work. Work a little bit more cohesively and kind of like an epiphany for me was when I was at Microsoft Build talking with the Logic Apps group and they had this like agent builder inside of Logic Apps and they could add these different components and the naming conventions for all these different components seemed really. Similar to the procode environment like semantic kernel and I was like, hey, what are you guys doing in the back here? Is that just semantic kernel that you put a front end over? And they’re like, yeah, you got us, that’s pretty much what they’re doing. So a lot of these different tools in Azure are just being built on the same components. That the low code tools are being built on and that’s bringing this all together. So some further thoughts here. Power Platform’s not just for the kids table anymore, it’s made for the grown-ups as well. So you’re getting the same support for DevOps, you’re getting the same support for governance, and the result is basically that the procode assets, unlike Azure functions and models, can be exposed to exposed to the low code makers as well, not only easily, but in a governed way as well. So some things that that make me believe that Power Platform is being elevated to that first class citizen really direct concrete examples. Power Automate actions for Azure services so you can start to interact with these Azure services. You know, directly through Power Automate, I mentioned kind of like Logic Apps integration. The way that’s working with agents, you can integrate Logic Apps directly with the Power Platform as well. So we’re getting into this like world where. I can develop something in Azure, use it in Power Platform and vice versa and API management that’s matured quite a bit. We haven’t done, I haven’t talked about this in a little bit, but API APIM is, you know, has always been something that’s been directly connected to the Power Platform. And we’re seeing it make more available to people that have implemented APM as well. All right, it’s been a lot here. Need some water? So let’s talk about a use case. We’re going to do, we’re going to do 3 different scenarios and they’re going to be an evolution off this first one. So I wanted to think of an idea that was pretty ubiquitous and be industry agnostic. And so HR is one of these things that keeps coming up a lot. A lot. And so vacation requests, you know, here I’m out of the country right now. I need to take some time off. I want to have an easy way for, you know, to be able to do that and for a lot of smaller, you know, smaller businesses. They may not have like a really robust, you know, time off, you know, application or you know ADP or something like that to be able to manage it. So let’s go ahead and like let’s think about like what we would do and how we would apply this fusion team to this problem. So basically employee needs to submit time off requests and managers have to have the ability to approve to approve or reject them. And HR needs to have access to all the records so that they can pay their time off, you know type of thing so. Solution I want to outline here is basically we’re going to build this in a Microsoft Power App, a Canvas app specifically. That’s going to allow us to build like a really simple, you know, form hopefully within a couple hours and hook it up to Power Automate to handle the approval requests. I can deploy this directly in a Teams, which you’re seeing in the screenshot. So the vacation request is, you know, is pretty much up and running in a day and I don’t have to write any code in order to do that. So how would we do it? First thing you’re going to do is you’re going to set up the data. Here we’re going to create like a SharePoint list or we could do a data verse table. Data verse table would probably be my first choice if I have that available to me as a decision to be made because it gives me more options later on down the road as this application is likely going to. Mature, but then in the app I’m gonna choose a canvas app template. I can connect it to that data and it already has an understanding of what that data is and can auto generate a screen for me complete with some of the validation that I might not have to. Worry about building out myself so, but even if I have to, I can use, you know, basically Power FX to build like Excel, kind of similar to Excel expressions, but they’re not like code, it’s just basically like little formulas that you’re creating. And then power automate for those that you know, haven’t used it. It’s also kind of a drag and drop, you know, I wanna if this, you know, if somebody does this action, I wanted to do this thing and we’re gonna, we’re gonna spin that up and have it do the approvals for that. In our particular scenario here, if a manager, if somebody submits a PTO request, it’s the manager’s going to get an approval update the team’s notification. Hopefully they just click a button to say approve like you see on the screen and then it’s, you know, it’s all good to go. That would how this gets split up across the fusion team. A lot of words on this screen, but there’s there’s tasks for everybody in this, even though it’s a low code solution at first. We can even have our procode developers involved and engaged in performing certain functions here, obviously our business process function. Business process owner function. You know they got to define the KPIs what how this is supposed to work. This is probably your HR manager and but that HR manager probably has you know somebody working for them that manages the data and you know keeps track of this stuff. They’re perfect candidate to do some of this low code environment and with just a little bit of training and coaching they can spin up, you know, the wireframes and power apps and within the studio and you know, connect it to to the data that needs to be done. Pro developer, it’s kind of like, you know, debatable how much they’re going to be engaged. It’s going to be pretty minimal, you know, in in this particular use case. But you know, they’re the person that probably would say, hey, like, I wouldn’t use the SharePoint list. I would use like a dataverse table if at all possible, because I have a feeling that the next thing that we’re gonna do is stub out like some sort of a custom connector to get to the HR data that they use and maybe it’s ADP or something like that. And then we definitely have our IT team involved making. Make sure that DLP policies are in place and that we’re doing security controls, especially when you start talking about people’s money and payments and stuff. So Step 2 here or actually let’s talk about the value proposition here. So this basic use case. You know, it just shows that like low code has, you know, speed and agility on its side. I can get something up to solve like a relatively, I don’t know if I it’s common ish, you know, kind of like a business problem without a tremendous amount of effort, you know. On the development team, but I also didn’t require a developer to do it. Didn’t have to go to IT to have them build something out for me. I could have analysts do it and I don’t have to deploy assets to Azure. So I don’t have to worry about like Azure consumption or how do I configure this and it’s a public cloud and that’s all my data and stuff like that. It’s all taken care of as part of the Power Platform system and the ecosystem. We get all that data governance and support that way, and most organizations are gonna have access to Microsoft Teams and SharePoint anyway, so this is a very feasible project for some of. To do in a day to go ahead and play with. But that’s not the end of this application because just submitting approvals isn’t super useful because people can’t leverage out of the other pieces of information that might correlate with that or even like reporting. Off of it really easily. So our requirements are going to grow and we want to make sure that we can integrate this into other systems and be able to look at that data. So use case #2, we want to make a unified data platform. We want to make sure that this information is being used across the ecosystem and has consistency. So same vacation data, but instead of it being in data verse exclusively, we’re gonna start leveraging Microsoft Fabric and that gives us the ability to use not just that data that we’re storing in data verse or SharePoint lists, but also for our analytics, we can pull it. Together with the HR data, well a little bit more robust data pipeline. So we’ll be using Lakehouse and a Power BI dashboard and as a little, you know, as a little bit of a value add, we can look out for our managers and say, hey, look, 30% of your team is. Is going to be on PTO next week. You might want to, you might want to think about that before you approve this so we can do that through like data activate activator triggers in Microsoft Fabric. So what would this actually look like, you know, if I was going to build this? So we’re going to move our data into fabric data versus direct integration. It’s kind of like a a copy, not really a move, but we, you know, would pull information from a couple of other sources as well and bring it all together in our lake house. And then we can enrich that data and consolidate it into a single view, certify those data sets and expose those to the application, you know itself as a more cohesive thing. Obviously we want to build some of these reports. You can see that, you know, a nice little heat map about what my coverage is. Gonna have outage, you know an outage window that I have to to worry about if I approve this and you know and then be able to do some more advanced automations like you see like the 30% of the engineering is out next Sprint. Let’s come up with a action plan or an alert plan. To make sure that that the managers are aware of that still with the Microsoft apps, Teams apps, we’re not changing any of that, we’re just adding a couple of features. Most of the application doesn’t really change, just a new screen, but how does this break down into the? Our fusion team responsibilities, well, pretty much the same team. I split out our pro developers into maybe two different subsets of pro developers. We’ve got our data engineering and we’ve got our application stuff because we’re gonna be building out some custom APIs for our connections to that data. And then, you know, a lot of developers like procode developers in the.net world may be a little bit unfamiliar with Data Factory, so you know, probably need a couple of different individuals there. But everybody else is sort of like the same responsibilities, the citizen developers, still the HR analyst. They’re the one that are helping to, you know, build out the screens in a in a low code environment. And we do see that our DevOps engineers get a little bit more involved as we’ve got more components we have to manage. And so we’re probably going to bring in things like Purview to. Managed data as well. So I think the the real value proposition in incorporating the data, you know lower code data aspects of this and procode data data aspects is that we give ourselves more real time insight capabilities. People have like a single source of where they can go and manage their information and you know this demonstrates that I can blend some of these procode things like analytics cubes or custom connectors to an HR information system. And have a robust solution that’s still predominantly low code, but gives me the flexibility to to leverage other systems that wouldn’t that previously wouldn’t have been capable in the Power Platform. So however. However, still not perfect. People are using it today and they’re, you know, they’re kind of happy with it, but people are still hunting around for answers and they get pinged with a lot of those like approved notifications in teams and they’re wondering what you can do to to simplify things even a little bit further. So stage 3 is let’s do something with to make this a little bit more of an intuitive, you know, interface. So they still have to, you know, they still have to ask for information like do I have 5 days left or like who’s covering support for next week? And all this is information that’s available and there’s ways for us to access it. We just need to give them, we need to give the application the ability to do that. So in this solution, what we’re going to do is we’re going to turn this more into a teams bot. We still have the application, but and all these functions still, you know, are going to be reused, but we’re going to. Allow them to have a conversational experience to be able to interact with this information. And since it’s hooked up to Fabric, we can ask information about that data as well. So you know, what would that look like? I think there’s a little bit more, you know, scoping and design, you know, that needs to go into this. It’ll just start getting into more advanced functions and different use cases that, especially in a conversational mode, might, you know, be a little bit unpredictable. And we’re going to have to make sure that it’s a lot more secure because, you know, we want, we don’t want people looking up other people’s PTO balance. Balances and you know that type of stuff. So but we’re still going to low code this you know as much as possible. I think Copilot Studio comes into play pretty well and we’ll you know have to build in a few additional custom integrations you know to support this as well. And as you can see that the fusion team, their responsibilities, they’re a little bit more complex, but I haven’t added anybody else here. We still have our HR director, our HR analyst and our proco developers. Maybe it’s a different skill set, so maybe it’s a different person. That’s got a has the mindset for ChatGPT type of workloads, but essentially kind of the same thing. So hope that gives you a really good understanding of what these solutions might look like. So I’m going to start to wrap this up a little bit. Some lessons learned on this speed, depth, acceleration, that’s kind of like where my head’s at. Some of the solutions that we’re building today, a lot of the solutions that we’re building today are a low code first, you know. Analyst type of workloads and I’m looking at the speed of getting something in our customers hands to be able to see the value quicker. So speed is definitely important there, but we run into some hiccups where we can’t quite get the performance that we need. And so when we need depth, we’re going to bring the pro code into it. And you know from an an acceleration standpoint, A I can really accelerate the pace that you can develop in and it’s changing month by month the the capabilities. Earlier this year, not being able to hand off a user story to a GitHub copilot agent or using the team’s planner to be able to build an application. These are all things that have happened, you know, in the last six months and are going to continue to to accelerate. But by adopting A fusion team strategy where you’re considering and working with low code as a key skill set, you know on these fusion teams, I I’m predicting that you’re going to see up to 10X faster delivery times without necessarily. Sacrificing quality and the trick is just to know when to use low code and when to work with pro code. And keep in mind the governance is gonna be even more important as we start getting into these lower code type of toolkits. So Microsoft Purview has a lot of great features that are supporting this sort of hybrid fusion aspect as well. So what can you do? I recommend that everybody in this call probably like consider taking these these four steps. Work with your organization to launch some sort of a pilot fusion project. Start small. See how it works for you. See what kind of skill sets that you have. You know, internally to be able to support some of these things, come up with a a training plan, a scaling plan for your for your team as well. These are all new technologies and you need to stay on top of it, but helping them, you know, helping turn analysts into makers. Is something that you should definitely start thinking about and AI being a huge component of accelerating the development time. Just make sure you’re using it responsibly. It’s not. It is definitely wild, Wild West out there and you know, start looking at ways that you can. Make sure that you’re mitigating data loss, you know, for the organization and enforce the right kind of environment structure within your Power Platform environment. Need help with any of that, you know concurrencies. Done quite a bit of these not only projects but governance type of aspects as well. So embrace low code for speed. Invest in pro code foundations. Watch A I like a hawk, like just on top of it and learn the tools that are in the governance tool tool belt. To me these are the these are the the key, you know kind of thoughts that I would I would leave you with. I’m not going to read everything that’s on the screen. But uh. Been talking for quite a bit. I don’t know if there’s any any questions in the chat. All right, I don’t see any questions in the chat. So final little slide here is next steps, you know, for us, you know, to be able to help you. Concurrency would love to be a part of the journey, so Amy had dropped in a link to a brief survey. If you want a follow-up with us, that’s a great opportunity for you to let us know that you’re interested in talking about something a little bit more. But you know, most importantly, I’d love to get your feedback and what you thought of this webinar, like if I met the expectations, things that I can improve, you know, if you were looking to get something else out of this as well. But in terms of next steps, if you need some sort of a guide or a Sherpa to help you out, we can help you. You with a use case discovery session helping you evaluate is this an appropriate fusion business case where we would recommend a fusion team attack this. If you are looking for some sort of a power platform envisioning session, I don’t know where to get started. Can currency help us figure out? Throughout some of those areas, we’d love to help you out there too. We can do an envisioning session. Governance readiness review is something that we’ve been doing quite a bit this year. As people start to adopt AI, is it safe for us to use it? Do we have the right guardrails in place? What’s our exposure if we turn some of these things on? And finally, if you really want to dive deeper into just the A I, you know aspect of it, our executive A I envisioning sessions are somewhere that we typically get started and this mostly resolves revolves around getting pie in from the organization. The A I is a strategic. strategic initiative that they want to undertake. So that being said, thanks everybody for joining today and uh I look forward to hearing your comments. Amy Cousland 49:13 Thanks, Brian. Brian Haydin 49:16 Thanks, Amy