Session Information:

Enterprise No-Code Automation: How to Rapidly Improve Efficiency & Adaptability Across Your Processes, People, and Technology

In a recent study conducted on hundreds of operations and IT professionals, it was determined that 95% of enterprises have already invested in or are about to invest in a no-code/low-code platform.

Why is no-code the next wave in iBPM? Because no-code platforms extend development capabilities to business operations—greatly accelerating and scaling process improvement. In this session, Tonkean will cover what the rise of enterprise no-code means for process management, and how teams can leverage this technology.

Attendees will walk away with an understanding of:

Session Transcript:

I'm very excited to welcome Brett Lee. Bradley is the Head of Marketing at ..., an enterprise, no code process orchestration platform. He has over a decade of experience in marketing, product sales at B2B companies, like Hewlett Packard, Periscope data, and perfect on mobile.

He's, he has spent his career at the intersection of no code and automation, particularly interested in how these technologists can be smartly leverage to solve complex business problems.

Brett, it's a real pleasure to have you with us. Thank you for taking the time today to share your expertise with our global audience.

Thanks, Joes, it's very nice to be here, and happy to be speaking with everyone.

Great! So, let me go ahead and get started.

So, why are we here?

Why does efficiency and adaptability matter? And, you know, I'm a big subscriber of Simon sinek's start with the why. So let me start here on this topic.

First, well, first, for businesses, efficiency and adaptability are critical.

I don't know if you guys know a stat, but two in every 5 Fortune 500 companies, we're actually no longer going to be around in 10 years.

The pace of change today is faster than ever before, and we're facing constant global disruptions.

You know, ..., being the latest prime example of a global disruption, The companies that are set up to adapt quickly to the changing conditions are going to be much better, situated to survive and thrive in the long run.

Recently, we worked with a company in the consumer travel space, and you can imagine overnight, their entire business changed.

one area where they fixed a lot of stress was in the customer support process. All the people that had tickets booked for flights, all of a sudden, had to call in and change or cancel their tickets, And that created a wave of demand, just seemingly overnight, and their customer support department, and, so, the ability for them to adapt to the changing conditions.

While facing stress, from the business perspective, so you had, again, efficiency, was critical to their survival.

Now, this is also important to people. This is not just about business outcomes.

Alright, people, I don't know, if you know, only spend 2.8 hours a day on high value work today.

And if you think about efficiency, that is insanely low, you wish that people had much more time to spend on the things that actually impacted the business rather than chasing data in different computer systems, are trying to figure out what the right processes to follow, right.

And from an adaptability standpoint, overnight, people have to go and move to start working from home and in the face of covert.

In businesses that were better set up, to enable people, to empower people to adapt what would also thrive in the law?

So, what that said?

Achieving adaptability is incredibly hard, I'm sure all of you process experts know, that change management is probably one of the hardest things to do.

And if you think about why, you know, you look across the people, the processes, and the systems that you have in your organization, things are incredibly complicated, right? A lot of times, sometimes the process isn't even well defined. So how can you change it if you don't know what the processes?

You have These systems that have been around for years and years, touch hundreds if not thousands of people, and so seemingly changing those systems overnight is also incredibly hard.

And finally, people are sometimes the hardest things to change. People are stuck in their behavior. They like what they like.

You need to train people to learn new behavior, or to adopt new systems.

And that is monumental task in many cases.

Additionally, gaming efficiency is quite complicated. You know, I took a simple sip sip Hawk example of simply send me an invoice. You think it should be easy to get an invoice, send it out to e-mail?

But if you break down all the different components that make up what sending an invoice entails, you can see that it touches multiple people. It touches multiple different pieces of technology and systems and tools. And it's a process that is very, very convoluted and actually incredibly complex, even for something as simple as sending an invoice. So, finding the areas where you can actually gain efficiency in these processes in these systems and these people is also incredibly complicated.

Now, one of the things that holds companies back and holds profit expert back are the technology options that are available today for you to actually improve the processes, to make people more efficient, actually make your systems work better for you.

And that's because technology is today are true, rigid, and inefficient.

You really only have two options at a high level, right? And this goes back to your typical kind of buy versus build.

You know, decision point, number one, you can deploy more apps. But most organizations have thousands of apps already.

And if I need to add a new application, that only adds to complexity in an ask the people, having to learn yet another system, to be able to actually work.

and deploying apps is also very rigid.

Once you have it, it's very difficult to actually change the capabilities of that system. And so as your processes shift, as your business changes, that means you have to go back and maybe take out that app and buy a new one, right? Or write a ton of custom scripts to actually change the functionality that comes out of the box of that initial application.

And that leads me to the second option.

You can build custom solutions. Well, how many developers do you really have access to, right? Every company needs more developers. They need more technical resources. In many cases, that becomes the bottleneck.

And building custom solution does not easy. It takes 6, 9, 12 months, and you have to ongoing.

You have to continue to maintain and update that system again as your business changes.

So, it creates a lot of inefficiency in the organization.

Now, this all hinders your ability as process experts, as business experts, as technology experts, to be able to adapt and optimize your operations in your business.

We recently did a survey to a national audience of business operations experts, and this included people, both from the business side, as well as the IT side. And 86% of respondents said that their plants get at least occasionally delayed because of lack of technical resources.

And so this is one of the main causes that prevents businesses and prevents process experts as yourself from moving as quickly as you want to, or adapting as quickly as you want.

Now, one of the rising sets of technology in the enterprise today is no code or low code automation.

And the promise is pretty evident.

It, if more people could actually create software, could actually build software, you allow more flexibility. And you allow more agility because you're less dependent on a core group of developers or organization of developers to solve process challenges.

But, because it's relatively new, it hasn't really entered the mainstream of the enterprise.

No tech step today, and so what I want to do is to go through some of the nuances of what automation is and what it actually means to deliver automation properly.

Now, there's actually one poll I would like to send out right now, and maybe Joseph, you're here. I'm not actually sure how to do this.

Yeah, No, I'm gonna, I will do that for you, OK, And you send out the poll about, about no code in the next 2 to 5 years, I'm curious.

So one question I wanted to ask, the audience is, how many of you believe that no code or low code is going to be kind of a game changer for enterprise over the next 3 to 5 years?

If you can tee that up and send it out, that'd be great.

We'll do that, Brad. Just so you know, there are three polls available. I believe organization has too many apps. I believe organization has enough access for development and the third one that you're mentioning, no cold platforms are going to be critical for our organization within the next 3 to 5 years. I'm gonna relaunch that one right now.

So for those of you in the audience, the poll is going is being launched, and it says, agree or disagree. No, cold platforms are going to be critical for our organization within the next 3 to 5 years. So please select one of these options, agree, disagree, or not sure.

So, click on one of this free options, and I see the first few votes coming in, go ahead and vote on one of this free options.

And I'm gonna give you a moment here to do that.

Very well.

We have most of you already voting, I will give you another NaN here to complete.

And, Brett, here we go.

I'm closing the poll, and share the results with you all now, and I'll read that for you. Brett. Us, 54% say that they agree, 4% say that they did disagree, and about 41% say they're not.

Sure, Interesting, interesting, this is actually kind of what I, what I expected.

I think for many of you that have started looking at these solutions, you can understand the game changer impact that and potential, at least that it has, And also, there's a lot of, uh, you know, folks that are relatively new to the no code, low code concept, and or, or have some uncertainties about how this can actually apply enterprises. You know, how can you leverage no code solutions to solve really complex business challenges?

You know, can you actually trust, you know, non developers, if you will, to actually build solutions that the last and that can scale to support the complex business requirements that an enterprise has, All those? You know, I've heard quite a bit. And so, hopefully, by the end of today, I can change some of those unsure, or at least highlight a little bit about, you know, what? No code automation is, and what some of the promises. And so that's, that's why I wanted to go next.

So, to break down these two components, you know, I introduced no code. But I also introduced this idea of automation, and that's why I want to start first. You know, when you think about automation, what exactly is it, right? There's a lot of news, and media, and press talking about automation is going to be replacing jobs and how, you know, robots are taking over the world, et cetera, et cetera. What I wanna clarify for everyone here is that, if you think about automation, at the end of day, it's still software technology, at least, when it comes to process automation, right? And if you compare that to what a business application is, in many cases, business applications are automating certain steps and processes within your business already.

Right? If you take a CRM, customer relationship management system. You know, there's a lot of tasks that that system is doing behind the scenes, you know, tracking opportunities, categorizing what a customer is.

You know, once you update a field, having a few other fields automatically updated for you, in effect, that's automation.

Now, it's just happening in the confines of a business application. And really, that's just a technology tool that you're using to make your business more efficient, make your people more efficient.

But in many ways, automation is the same.

If you look at process automation, right, it's about eliminating some of the mundane tasks that people have to do today. Whether it's responding to an e-mail, whether it's, you know, having to go to 4 or 5 different systems to toggle a field, just because something changed, and in many cases, process automation is actually, you know, filling in for some of the limitations of business applications. Right. You would wish that business application could automatically do some of the things that people have to do, but it can't because of technology limitations.

And so in many cases, if you look at RPA, if you look at other things in the process automation space, there are things that are actually filling in some of the gaps of that technology, right? And making people a bit more efficient in that manner.

Now, one of the other things I wanted to introduce to everyone is this idea of process orchestration. Right?

And to me, this is the layer above automation.

If you think about automation as being tasks orchestration is the choreography of those tasks. What do you do? when how do you do it? What are the business logic and business rules that's in place, in order for those tasks to be taken, when those tasks should be taken? And that is another great opportunity to introduce technology, to help you manage and streamline many of the business processes that you have, and it achieves a lot of the same outcomes, by the way, when you think about delivering new business applications. Allows you to manage an entire end to end business process, like Customer Relationship management or like a contract process.

But the difference is, it doesn't actually introduce another interface. It doesn't introduce another system, another URL, if you will, that people have to go to to be able to get work done. But rather, you can think about it as taking information and bring it to people, taking actions and bring it. And I'll show you later on in this presentation a little bit more of what that actually looks like, what that means, But I want to introduce that concept to everyone.

Now, the other question is, OK, great, what does no code, right? Does it really mean that I don't have to write any code anymore in order to build software? Well, let me tell you, there is a spectrum, right? It's not code, or no code, there isn't really a black and white.

You know, distinction between the capabilities that you have here. It's really a sliding scale.

And there's places for custom coding, right? Where you have to build code from scratch and actually write new software. There actually isn't in-between this idea of low code, which is, there are certain components that have been abstracted from the custom code such that you can re-use it. But then, add some more code, if you need to, to extend the capabilities of the components that you built.

And then, finally, there is full no code, which, you know, again, it's everything is based on these components, that you're dragging and dropping in order to build software. And each of these different types of technologies is geared towards a particular segment of people.

If you think about custom coding, of course, for professional developers, right?

Now, low code is also used in the context of professional developers. A lot of IT organizations are actually using Loko Technologies to accelerate the pace of development.

Because great, you can write code, but writing code takes time. If you can, component high's a lot of the elements of code and re-use it more quickly, that's going to speed up how quickly you can deliver software, Right, and then no code is really meant for business, folks. Now, the other, kinda misconception that a lot of people have, is, it's either one or the other, you know, you have a platform that is, all, only no code, or you have a platform that's only coding.

And over time, what you'll see is technology starting to have a spectrum, where, ideally, you have a handoff.

Imagine, you have developers IT building the components, using code, using scripts to define certain business capabilities, and then handing that component off to the business. For them to be able to use themselves in order to build out an end to end process. And so, you know, that is one thing I think you'll see, kind of evolve over time.

Now, here's what we found on that question that I asked you a little bit earlier.

95% of enterprises in our survey indicated that they've either already invested in or are about to invest in a no code low code platform.

So, this is a wave that is absolutely coming in the enterprise. More and more people are looking at it.

And, you know, it's something that really is starting to take off in in this space, but the question is, OK, you tell me this train is coming, but how can I actually use no code automation? I want to make this practical for everyone here.

So, I'm gonna break this down into four key steps: Number one, You want to identify the areas for automation or orchestration. and notice that this is not just about no code. All, right. This is also about being able to find gaps in your processes, gaps, in your systems that you can leverage automation orchestration to drive. More of, and rather, a lot of companies today are looking at, no code, kind of, as a side project. You know, let me find some low hanging fruit. Some non critical processes actually use this technology on, and I think that's the wrong approach, because we want to use no code to accentuate the people who are, you know, building out these processes. People that have a process excellence folks that are on this, You know, in this conference. And, that is where the opportunity for this is. Now, you can ask the question. Simple question. Is there a lot of manual work, And that's typically, you know, for a lot of organizations looking at automation, that first question they ask.

But, the other question that should be looked asking about is, well, this is an alternative to an application. Do you really need an app?

Do I need a new interface, or is that because, or, am I looking at an app? Because that's the only way I can solve a process challenge today. Right? Is change management going to be an issue or people liking to use e-mail or already using other systems? And, I actually want to just keep them. Well, this is a better place for automation, rather introducing new app.

Does the process evolved multiple systems there, human interaction? Is there are multiple functions in bold?

These are all places and all questions that you can start to ask to find opportunities for automation orchestration.

And, as an aside, I know Joseph mentioned process mining next week, and I think that is absolutely one area where you can levitt's process mining tools to figure out where opportunities are to improve your processes within your infrastructure.

Number two, is to create a collaborative IT and business relationship. And I know, for many can't view, this is sometimes already there, But other times, easier said than done, right?

Because IT and business have dynamically different needs, Right? On the business side, you're trying to achieve outcomes. You need more flexibility. You want to move faster. On the IT side, you're looking to ensure security and compliance, and being able to support and scale how you support the entire organization.

Um, now, there's expertise on both the sides that you absolutely have to have in order to successfully improve your processes and, and look at all three components that people, Processes, and Systems, that I talked about. Right on the business side. You have process knowledge. You understand the user needs on the IT side. You have technical knowledge and dev resources. Finding a way where you combine those two things together, where, you know, for IT, you can actually empower the business. with capabilities on the technical side and business, you can take the process knowledge actually deploy without having to translate it back to IT.

That is going to make this entire, you know, collaborative relationship work much better.

So how do you actually then make this co-operation easier? Well, what it comes down to is component ...

and thinking about like Lego blocks.

How can you break apart your entire technical stack into specific building blocks? That, again, going back to what I've shared with you about the spectrum between no code, low code, and custom code into these re-usable components? You can piece together in order to deliver, and I'll, again, explain a little bit more in a moment, and then break this down for you what this looks like.

And then, finally, sorry, that's a typo here, but continue to improve, it's about iteration.

And this is where you achieve the adaptability that you have over time as, if you can break apart, create this collaborative environment, break apart the capabilities into subcomponents, and then start to improve incrementally over time on shoes and co components. That's where you start to achieve big outcomes in the long run.

So let me break down in more practicality what this actually looks like for an organization and this is a model that you can deploy now. Tonkin as a platform, helps you deploy this immediately. But you can do this even by herself.

The ability, again, to achieve that component ization achieved that collaboration between IT and the business and then be able to iterate and quickly scale your capabilities.

So, on the left, what you see here is kind of the IT side, if you will, right?

You have your existing technology stack, your various packaged applications, custom built applications, collaboration platforms, which increasingly is where people spend their time writing an e-mail on Slack, and teams and g-chat, as well as in, as well as your databases. And what you first want to do is to connect those systems. For a lot of companies that already have APIs, it's easier, right? But you can also use things like robotic process automation to tap into the capabilities of your systems.

What you want to do is to build what eifel Enterprise components, what we call enterprise components, right? Which are a packaging of different capabilities, in your technical architecture. So, for example, this could be something like, I want to update an opportunity, right?

And that can be a, you know, a Salesforce CRM component, but then also maybe including an alert into something like a team's to say that that opportunity has been update, or has been created, right? That can be a package capability that you capture, and you start to re-use. And any combination of that, you can build into these building blocks of enterprise components.

Now, then, what you want to do is, on the other side, create a no code experience. And there's, you know, a number of different noko tools that allows you to do this. But I'm talking to one of them, to take those Enterprise components that you've built, and then be able to re-use. It.

Be able to use, a, no code interface for the business to string them together into an end to end process, that actually improves your business operations. And this, now, you hand to the various departments within your organization, marketing, sales, support, legal, finance, engineering, and IT to be able to empower them to build their own solutions.

And the beauty of this is, now that you have a standard model, it's much easier to build custom processes that satisfy your unique requirements with business input. Right? If you think about something like the contract process. Right, That touches legal, and sales, and finance, and other in HR, and having a system that captures your contract process is not the easiest way to actually solve that problem, right? Because now, you need for different departments to login to a single system in order to interact with that process.

Much better, would be taking the core capabilities of that contract management system, And then giving it to sales in the form of updates to their CRM, giving it to legal, and whatever system they're using, Giving into the HR portal and actually pushing capabilities into that, that makes things much easier for the organization.

So, one story I wanted to tell is is Google and they're using Tonkin?

to empower no code automation for specifically their legal Operations Department and actually standardized on Tonkin or this. What they were looking to achieve when they started the no coach journey is they wanted to improve flexibility and agility in many cases. Legal for most organizations were kind of an afterthought, you know unfortunately for IT support. You know, they're prioritizing revenue generating areas of the business, sales, and marketing, and other places, as a priority for where they spend development, resources. And legal.

A lot of times, is kind of left to two left to their own devices, if you will, to solve that, and they needed to reduce the reliance on IT engineer. And so they leverage no Code Automation to improve a lot of the processes that they have.

And automation was also uniquely beneficial for Google, because for legal, because legal inherently in the nature of their work is interfacing with other areas of the business. You know, they're interfacing with sales and with marketing, and with HR, and finance for a lot of the capabilities. And there are processes in their work, and so they could ask everybody to adopt a legal system.

But who would want to do that, Right? Instead, people would probably end up sending an e-mail to a legal inbox to ask a question for that legal team.

And so, rather than do that, they wanted to actually be able to connect to reduce that change management, further processes into the other systems, into the other tools, the communication platform that people are using.

And so they wanted a lot more flexibility there.

And so that's all of the things that came to mind when adopting an open platform like Tonkin is they wanted to improve these processes without requiring a lot of that change that normally occurs with implementing new technology. They are able to drive a lot of things directly from e-mail and they see massive returns and savings and one point six million savings per year. Because of productivity gains, reduced services that they were contracting out because they didn't have access to development.

And also by the way, not having to buy more apps, so. A lot of savings on the license cost as well.

So, with that, I think, we're actually a little bit out of time.

I was going to show you from some of this concept in action, but I think we can go maybe straight into the, into the Q and A, and one of the things I wanted to mention though, is, at the end of the day, no code automation immediately benefits.

You all, on this call, are the folks that are process oriented, process experts, operational experts.

You're able to actually now deliver on some of the things that you find when you map out a process. Instead of having to rely on an external resource like developer, or somebody in IT, that you build that solution for you, This is something that you can now do yourself.

And you can, actually, with the right, a model, with the right support from IT, be able to now accelerate how quickly you can impact change in the organization.

And so this is a very exciting area in technology, I think, for, for many of you on the process side. And I think it's absolutely something that organized trend to look into, to start to democratize and expand the pie of who can actually deliver software.

So with that, I am going to turn it back over to, just for the Q&A.

Very well breath. Thank you, very much. Excellent, excellent coverage here. We had several questions that have come up. I'm gonna, I'm gonna ask you breath to stop sharing your presentation.

I'm gonna come back on with my camera, and in for our audience, Thank you for the questions that you have already submitted. I'm looking for the main things that have emerged here, and I encourage you to continue to ask questions, because as long as we have Brett here for the next 10 minutes or so, take advantage of his expertise.

So, Brett, in no specific order, as you were explaining, and some of these items you have already addressed as part of your presentation, but a little bit of reinforcement here, I want to go back to the, to one of the top questions that came up.

And the, and that was Smith, and I was single out.

Francis Buganda here, who asked, who mention, no code is too good to be true. That's the worst thing.

What are the limitations, breadth and constraints of no code versus low code and custom coding?

When should we say that no code is not the right solution? So a couple of questions there. First one is maybe a reinforcement of those of those limitations, Andrea, and also where, you know, Is it too good to be true? And, you know, you have already made that point, but if you can emphasize a little bit about true, No code applications, what do they look like?

And two, and then, you know, is there a time that you say, you know, it's not the right solution for us.

Great. Great question.

So, And in many, many ways, it's about thinking about the spectrum.

Right. It's not one thing or the other, and I think I've mentioned this before, but I want to just re-emphasize that point.

It's not no code or low code or pro code, everything.

And if you can build an architecture that allows components to be written in code, then be re-used and a no coding environment where you have some technical folks that then can accelerate how quickly they develop.

But then they can in turn create maybe more components that abstract more technical knowledge into the no code environment that allows business to actually consume that on their own.

That's the ideal setup right.

And so that's of course how Tonkin thinks about it, right taking Enterprise Components and hand it off to the business for them to self serve.

But that's also you'll see a maturity of this in the in the market over time I think Today there is still kind of the separation. It's either No code or code and I have platforms that are only no code and you're absolutely right. You're gonna run into barriers, there's limitations of what no code capabilities and can do, right? A lot of no code platforms today are focused on a specific subset of capabilities. Maybe it's no code. But I can only do, you know, HR functions or I can only do things that are, you know, related to field services, whatever that is, right? And I can build as many applications there as possible.

But if I want to veer outside of it, I need to build a connection to another part of the business. Well guess what, you're out of luck? And you have to write code. So, that is the limitations that you see today with no code platforms, and open environments, and the concept itself.

So, the more you can think about it as a spectrum, you know, ability to handoff between the various aspects of no code, low code, and pro code. That is where you remove a lot of those limitations, and allow you to take advantage of the capabilities for the right.

Very good, Very good. The next question here is actually kind of a funny question, because this is someone who has been in the industry for quite some time, and he says that, Every time I ask someone to explain simply to me what no code is, they started giving me examples with, with other enterprise applications, and he feels to me that there's nothing simple about it, and it's almost like, I'm back in a computer science class, and the stock routines yields to sub routine design. So, to your point, the question really is, is there, is there something that comes to mind? Kind of a more of a business application that's more tangible, because a lot of times when people ask questions about no code the people answer with, kind of on some, some IT application. and then, And then it gets people, who have business sense, But don't have, you know, the IT specific knowledge and get a little bit lost. Is there a good example of no code on a, on a business intuitive application?

Yeah.

So I can, I can tell you, some examples of, you know, deployments that we've done, for example, in legal and customer support, and other places, If you think about legal, right? And I'll go back to Google. And this was actually the example that I ran out of time to kind of showcase legal intake as a process.

And this is the ingredients of legal intake is appearing in every part of the business. But concept is simple.

I need to be able to take incoming requests for legal support from various parts of the business.

Whether it's sales contract, whether it's an HR new employee agreement, whether it's a litigation, you know, whether it's just a question, and I need to be able to collect them, and then be able to, you know, send off and triage them through legal.

Now, you can build an application for this, and you can buy an application for this, but guess what? That application is require some way of inputting the request.

That's always going to be a form, right, And that forum is now a new thing that people have to go learn.

But guess what people do today In interfacing with legal, well, they send e-mails, they send a legal inbox if I get an e-mail saying, I need this. So, what we've been able to do with Google, for example, is with a no code environment, and the components, some, some we provide out of the box. There's others that, you know, their IT organization has to kinda define using code themselves, but that's for IT. That's not legal doing it.

They then build it once, and then they have something like, well, interpret e-mail. And behind the scenes, you know, there's, like, natural language processing, and all these complicated technology trends I'm not gonna get into. But simply it's I want to be able to read the subject, read the body, and understand what's going on, what that e-mail. Right. Is it asked me for an NDA? Or is asking for an ISO W or something else?

And that is a component that you drag in Legal defines what the keywords are that should be looking for from a business process standpoint, and then they define what happens afterwards. Right?

So these are all building blocks, and some of the follow-up material that will send you will have more examples from a talking context. But that's that's the general concept was like, how can I use, essentially, a Visio diagram or a process diagram and translate that into something that now can actually work. Right, and that's. That's the beauty of. No.

So, I hope that is another way to answer that question.

But, again, sometimes a picture is worth a thousand words, and I don't have the ability to show pictures right now, but that's, Hopefully, that makes a bit more sense.

Yeah, I think you that color, it really helps, because, especially when you start talking about, you know, a process diagram, that, you can, you know, you can use as a as the baseline for the low code application. I think that strikes a chord with a lot of the people in the audience here. So that that's very good. I'm going to, the next few questions are, looking for, the overall themes. Are emerging from those questions. one of the, one of the questions is about, it's, more of a of a curiosity. To a certain extent, this comes from William Fuller in an Oregon and he asks, he comments, first, it sounds like there's no code. Low code environment is an evolution of this service oriented architecture approach.

And his question is, I was simply moving up the maturity curve, or this is some sort of new paradigm. Yeah, no, that's actually not a bad way to think about it.

Because if you think about technology in general, there is just more and more abstractions being built, but the benefits of having abstractions built is that you have more access.

More people can build software to use kind of a consumer example, right.

Websites used to be really hard to build 20 years ago, right?

You needed to actually learn how to code, and actually understand the architecture of a website, or to build it. Nowadays, if you need a wedding website, you go to wix dot com, you go to Squarespace, you, go to any of these tools, And you can have a website out yourself easily.

And that kind of concept is making its way into the enterprise scope.

Now, with enterprises, you have a lot more complexity. There's no security, you have to worry about all of those things, which is why I talk about this kind of relationship between IT and the business, Right? You have to have that relationship.

But you're absolutely right.

This is kind of the next wave of, uh, I would, I would say, this service or an architecture, was one of the building blocks to enable this no code revolution to actually happen, without these building blocks APIs, right? And a bunch of APIs that connect to the systems. You can never get to this point, but that was actually absolute an active ingredient with this. Now, there were, there's other things that help. Right. You know, even machine learning, if you think about, I talked about an Apple in natural language processing behind the scenes, It technically very complicated to read unstructured data and be able to process it.

But if you can not abstract that and use it in a business context, well, for the legal person, again, It's just, I want to interpret my e-mail, Greg, you add this block, building the keywords, all those technical capability happening behind the scenes with this component, and I can just worry about what the outcome is. That, that process, Right. And so there's a bunch of abstractions on a lot of, you know, foundational technology that's been built over the last 10, 20 years as a way, and, you know, machine learning and, and, you know, and things like that, but that is being built impacts together into an open environment really now. Unlock the capabilities for for-profit process experts and operational.

Very good, Pratt. Erica asks a question that this theme has come up with other questions as well. So I'm going to try to kind of summarize it, but people will have BPM platforms in place. Right now, or they may have something, like, kind of, an advanced version of, kind of automated, Think of it, of, like, like you mentioned, Vizio before. Like, they have the process flows and diagrams, and they have some kind of automation built that as a business process management platform. If you bring what you're doing is key, and should that, how does that interact or, or build on, what they have? Yeah, absolutely.

So, if you think about the outcome of BPM, right, and BPM has, you know, it's been around for a long time, people have put a lot of process knowledge and things in there.

Unfortunately, most BPM's, the way they kind of automate something, is by building an app.

Here's a new interface, or hey, that you have force people to go to, where the business process behind the scenes is encapsulated and then you follow the screens to execute on their business process.

Which is fine, for some cases, in many cases, but there are times like I explained, where people have other systems already, people have, you know, are you leveraging the communication tools? And? And? And. You know. Delivering capabilities to the team's environment, to slack, to e-mail, to other, places, where instead of taking them out of that communication context, and go to a system, to do, something, you can, keep them there, actually have things being done there.

That's the extension that I'm talking about. And so in many ways, Tonkin is kind of collaborative with BPM. You know if you have the process already defined there.

There are some things that you want to build an app or there are other things that you actually want to take more of an automation approach or an orchestration approach to be kind of headless where you don't have a new interface people are going to?

So that's, that's kind of the relationship between, you know, talking in and kind of a BPM platform, that makes sense.

This is a great, this is a great view. I think it helps quite a bit, and I appreciate, appreciate that. it's a good way of wrapping up, because we're just out of time right now. Brett, What a gift to all of us to learn from an expert in the field, to kind of, distill the language and the applications to all, our global audience of excellence and innovation leaders, and business transformation leaders, who can really make good use of low code. No code applications. As you said, it's been around for some time, but I think there has been a real acceleration in the last five years or so. And thank you so much for sharing your expertise with all of us today.

Thank you. Happy to be here, and I hope to also be follow up with a lot of you after today and keeping the conversation going. So thank you very much.

We'll do that. Thank you very much, ladies and gentlemen, that was Bratley, the head of marketing for Tolkien, and the, and the very excited to have him with us and distill some of this language and applications of low code and no code in our automation efforts. So, we're gonna wrap up this session and at the top of the hour, we're going to have a great speaker coming directly from Germany. This is one of the senior leaders in Project Business for Siemens, is going to talk about speeding up their proposal phasing project business by more than 300% by using an intelligent and their documents screening approach.

So, how do we use artificial intelligence on a very important business process, business process, like proposals, to speed up the process and create value? So, I really interesting application of artificial intelligence in BPM and business process management, and I'm very excited to welcome ... Grass, Gas, and at the top of the hour, and I hope to see you back soon. Thank you.