On-demand webinar61 minutesForrester 2022

2022 process automation trends uncovered, with Forrester

Forrester's John Bratincevic and FlowForma CTO Gerard Newman on empowering citizen developers, building a culture of innovation, governance at scale, integration and overcoming resistance to change.

What does the 2022 process automation trends webinar cover?

2022 Process Automation Trends Uncovered, feat. Forrester is a 61-minute on-demand webinar from January 2022. Forrester senior analyst John Bratincevic and FlowForma CTO Gerard Newman answer questions on empowering citizen developers, building a culture of innovation, governing development at scale, speeding up integration, why digitizing makes standard work real and how to overcome resistance to change, with customer success stories and FlowForma's 2022 roadmap. FlowForma is the no-code process automation platform native to Microsoft 365. Watch the July 2021 session in the series.

~£80,000saved by one process on a single project, on one of the UK's biggest infrastructure projects (46:10)
50+processes that same customer went on to automate after the first one paid for the investment (46:19)
~5,000hours a year saved by a college after automating six processes (47:08)
35 daysfrom initial concept to a live process for one customer, including training, through SureStart (59:27)

Advice from Forrester and FlowForma

Two questions the speakers kept coming back to: who your citizen developers should be, and how to govern what they build.

1

enthusiastic person is enough to start a center of excellence

Who should be your citizen developers?

  • Natural problem solvers who want to make things better
  • People with the time and motivation to improve things
  • Process improvement, analyst and project teams
  • Hackathon volunteers, mentored as they start
  • Not necessarily the people writing macros
“Find your natural problem solvers, the people who want to make things better.”John Bratincevic, Forrester

From the session, 02:43 to 06:40 and the Q&A at 58:05

3

questions to answer first: who, what and how

Governance: how to control what citizen developers build

  • Who can develop: everyone, or people with certain training
  • What they can build: use cases, data, complexity, audience
  • How they build it: process, testing and support
  • Different rules for different levels of risk
  • Policies built into the platform as you scale
“You've got to have different rules apply to different things.”John Bratincevic, Forrester

From the session, 13:33 to 20:06

Ready to empower your citizen developers?

Book a demo with our process experts and see one of your own processes digitized live, with no code.

  • A demo built around one of your processes
  • A walkthrough of approvals, forms and reporting in Microsoft 365
  • Advice on choosing your first process and your champions
  • No cost and no obligation

Want to try it yourself? Start a free trial

Pick a time that suits you

00:00

Welcome and housekeeping

Watch this part

Ursula Cullen00:00

Hello everyone, and welcome to today's webinar, Process Automation Trends Uncovered. Before we get started, some housekeeping. The webinar is being recorded, and you'll receive a copy of the recording afterward. If you have any trouble during the webinar, please email info@flowforma.com for assistance.

Ursula Cullen00:24

Your lines will be muted. You can use the Q&A function on the right-hand side of your screen to ask questions, and we'll cover them at the end. After the webinar, a short survey will pop up, and we'd be grateful if you filled it in.

00:40

Meet the speakers

Watch this part

Ursula Cullen00:40

I'm absolutely delighted to welcome John Bratincevic. John is a senior analyst at Forrester, and his research focuses on citizen developers, low-code development platforms and digital process automation, lots of themes we'll be covering today. We're also joined by Gerard Newman, CTO here at FlowForma. Gerard has over 20 years of experience designing and delivering process automation solutions that have allowed businesses to integrate and automate their operations, deliver a better customer experience and improve efficiency. Welcome, both.

01:21

Empowering citizen developers in 2022

Watch this part

Ursula Cullen01:21

We'll get straight in with our first question. The democratization of development is accelerating. Gerard, could you start by sharing how you'd recommend listeners empower developer strategies for process automation, especially in 2022?

Gerard Newman01:46

Sure. Looking back at 2021, we saw real growth in understanding of the citizen developer role. Businesses understand more about what it means to them and the benefits they get from encouraging that role. In 2022 we'd expect the trend to continue, with organizations investing more in building out their citizen developer teams.

Gerard Newman02:17

So how do you actually empower these people? Like most change projects, the first thing is senior-level buy-in: an enthusiastic supporter who has bought into the benefits of business people doing application development and automating their processes, rather than relying on scarce professional IT resources.

Gerard Newman02:43

The second point is establishing what I'll call a center of excellence. That might sound daunting, but it can start with just one enthusiastic individual who's willing to try things, take the first steps and mentor other people as they begin their citizen development journey.

Gerard Newman03:35

And the third point is: start. Get an initial project going, because the sooner you do, the sooner you understand the benefits of citizen development. No-code tools support iterative development: you start, you measure, you improve, and you continue that cycle, across not just one process but many. So those are my three pointers.

John Bratincevic04:31

Top-down support is interesting. In the last couple of weeks I've had multiple clients, usually architects, tell me their CIO asked them about citizen development. In the past it sat a couple of levels down, with people thinking about developer capacity. At the C-level it's become a very hot topic.

John Bratincevic05:04

One thing I always remind people: if your company isn't very lean, people are at full capacity, or they aren't expected or allowed to improve the processes around them, that's a really hard starting point. In any environment, the key to empowering people and getting momentum is finding people who have the time and the motivation and are good problem solvers: people who really understand the business problem, or are hot under the collar about making something better. Start small with them and expand from there.

John Bratincevic05:36

Concretely, that can mean a hackathon, a common technique we've recommended for years: the people who are motivated show up, and you mentor them. Or there are logical teams, like process improvement people, analysts, special project people or project managers, for whom improving things is part of the job. It's very logical to give them technology to do that better.

John Bratincevic06:17

Then you build on those successes and evangelize them. If you want to empower people, they have to want to do it and believe it's a good thing, that you're there to help them and it's not just another corporate program.

Gerard Newman06:25

I agree. In the projects we get involved in, finding the people with the right motivation and enthusiasm can make a project very successful.

John Bratincevic06:40

Same as any other maturation: you have your early adopters, and you want to find them, because they'll be your leaders and evangelists, and over time they'll probably become experts, if you let them.

06:56

Building a culture of innovation

Watch this part

Ursula Cullen06:56

Question two is about rising customer expectations and market competition, which require organizations to be more innovative and invest in continuous improvement. A question we're asked all the time, and Gerard, maybe you'll take this one: how do organizations foster that kind of culture?

Gerard Newman07:21

In my experience with process automation projects, it's often difficult for organizations to get an engine of innovation going. It's not that people are short of ideas. There's often a shortage of skills, funding and time to act on them. Organizations are addressing that: more and more we talk to heads of innovation, people with innovation in their title, which shows they're formalizing their approach and making continual innovation a key capability. I'd expect that to continue in 2022.

Gerard Newman08:16

How do you enable it? Make it strategically important, and appoint someone with innovation in their role who proactively seeks it out. The way you capture ideas, bring them forward and let people see them acted on is vital too. And early success: people want to see their ideas go through a process and actually deliver benefit. Once you can demonstrate that, it primes the pump. More people come forward with more ideas, and they go through your standard evaluation so you can prioritize the ones you want to progress.

John Bratincevic09:32

I cover technology, and what's sometimes missed is that low code, because it's so much faster than other development styles and has quality built in, has that natural iteration cycle. It's a very logical medium for innovation, for trying things out and experimenting. I actually have research kicked off on the intersection between low code, agile and innovation. When the medium changes, it naturally instills behavioral changes, whether you intend it or not.

John Bratincevic10:29

But looking at the people and the practices: if you want an innovation culture, with people coming up with ideas and those ideas being executed, you have to show rather than tell. Some of the firms I've spoken to have a standard for turning around an application idea or improvement in low code of a few hours. You submit an idea, and within a few hours it's done.

John Bratincevic11:09

If you do that often enough, and show people in the real world, not on PowerPoint, that if they want to try something you'll do it, or give them a way to do it and help them, that creates the cultural understanding that an idea will actually happen. It won't languish somewhere under bureaucracy and justification.

John Bratincevic11:41

Tactically, teams also consciously build those mechanisms into their solutions. You'd be surprised how often this comes up: teams that do really well build feedback mechanisms directly into the software. There's a design standard that every page has a suggested-improvement button, and they have to act on it. So do rather than tell, and use the fast medium to your advantage: the improved economics let you experiment like crazy. Then people come up with ideas naturally, because if they say something, it happens.

Gerard Newman12:21

That's a powerful message. Condensing the cycle from an idea coming forward to it being implemented gives people a really good example of how innovation can take hold in an organization.

John Bratincevic12:44

Near live is kind of the standard.

Gerard Newman12:51

It's nearly a scary concept compared with traditional development, where things take a long time. In larger organizations with an application backlog that IT is working through, people don't see their ideas bubble to the top for quite a while. So it's a really powerful message.

John Bratincevic13:07

It's a natural way of encouraging it. And as you mentioned innovation teams: I've seen innovation teams that specifically use low code as their medium for this reason. Got an idea? Low code becomes the medium for doing it, because it's the logical one.

13:33

Governing citizen development

Watch this part

Ursula Cullen13:33

Moving on: with no code driving the citizen development movement, governance is definitely trending. Would you both agree, and how do organizations manage the development process?

Gerard Newman13:50

Governance comes up again and again, last year and in the years before: what controls can you put around a citizen development environment? CIOs and IT leaders are all too familiar with end-user application development and shadow IT. They want to avoid finding out that the business depends on an application built by someone who's no longer in the business.

Gerard Newman14:38

So the key questions are how you develop, test and deploy citizen developer applications, and, equally important, how you support them. If those aren't addressed, the organization is exposed to unreliable or unsupported applications that are critical to the business. So we'll see growth in tools and processes that put controls in place, without locking things down so much that you restrict the innovation we just talked about.

Gerard Newman15:03

We encountered this a few years ago with a client who wanted to automate hundreds of processes in a very short space of time. They needed a framework and tools to make sure the processes being automated went through a rigorous set of checks, from development through testing into the live environment. So we built governance capabilities into our product, and this year we'll continue to invest in them for the citizen development community. John, what are you seeing?

John Bratincevic16:07

This is so hard, especially at scale. It's the question I get all the time, and I usually tell people I don't have a perfect prescriptive answer. But we do have principles. The questions to ask are who, what and how. Who can develop: everybody, or people with certain titles, training or certification? What can they develop: which use cases, with questions about data, complexity, size, architecture, and customer-facing versus internal? And how: what's the development process, and what architectural and technical requirements apply, like testing?

John Bratincevic17:21

If organizations take one version of those answers, they can usually execute on it pretty well: anyone can develop if they ask, but no integrations, only spreadsheet replacement, you made it, you own it, and you can't give it to outside people. But when you scale to more people, it has to be more dynamic. What you're building should determine how you build it, or who builds it, or whether you need someone to help. I've met organizations getting to that point: if you're building something of this complexity or this risk profile, you need help, or don't do it.

John Bratincevic18:08

What's really needed isn't just frameworks on paper, which consultancies, services companies and independent firms are working out. The tools themselves need to mature to the point where all of that is baked in: the policies, processes and business rules on what you develop, how and when. The biggest I've seen are companies with one or two thousand developers. They're getting good results, but it's messy, because they manage it manually and sometimes have to unwind or rebuild things. That works for a few thousand people, not for 50,000.

John Bratincevic18:55

So it needs to be baked into platforms as a product: here's your governance suite, everything executed through the SDLC, policies on who, what and how that are dynamic, enforced in the platform and visible, like a spider at the center of a web. These products aren't just selling development abstraction. They're selling safe, effective development at scale by lots of people.

Gerard Newman19:28

There's a lot to learn from software development and the stages it goes through. We don't have to reinvent it all for no code; we can take the best practices and build on them.

John Bratincevic19:35

But having everybody do dev, test and prod, with testing requirements and sign-off before deploying everything, is ridiculous. Then everything stays in spreadsheets, because people won't want to go through it. You've got to have different rules apply to different things.

Gerard Newman19:50

Absolutely. It's about assessing that risk from the CIO and IT leader perspective and making sure it's under control, to avoid the end-user development and shadow IT problems of the past.

John Bratincevic20:06

And then it has to be tactically managed.

20:15

Developing a digital workforce

Watch this part

Ursula Cullen20:15

Next question: hybrid working. It's definitely a global initiative. We're based in Dublin, Ireland, and it's been in the news here the last couple of days. What would your tips be for developing and advancing a digital workforce? Gerard, any ideas?

Gerard Newman20:37

Sure, three or four things spring to mind. First, education. You can educate people in tools, approaches and methods, but one of the best ways is showing them examples. Get started, digitize some of your processes, and bring other people along so they can see what's been achieved and understand the art of the possible. Then support them with training, and mentor them to make them successful.

Gerard Newman21:42

Second, measure the results. What motivates everybody is seeing that a change is delivering measurable benefits you can articulate. Compare against the before situation, whatever statistics you have on how your processes behaved before automation, and make the results tangible to everyone in the organization. John, do you want to chip in?

John Bratincevic22:22

I'm the low-code analyst, so I always think about that. What I've observed is this: when you go through the exercise of finding people, enabling them and mentoring them, not just in application development but in design thinking, problem solving, experimenting and empathizing with users, over time, especially if they embrace it, it teaches them systems thinking. They become systems thinkers organically.

John Bratincevic22:56

I think of it as the intersection between lean transformation and digital transformation. With lean, you want a management system where everyone is iterating all the time and people bring their brains to work, constantly experimenting toward the target condition. Businesses have wanted that for years. When you give people a medium to build applications, where they design processes and systems and connect them, and see how flipping one lever affects something downstream, they become systems thinkers, because they're building systems.

John Bratincevic23:44

So when people tell me they want people to think digitally, I say: have them build systems in these abstracted environments. If they take to it and you mentor them, they'll become those people. Not everyone becomes a top-notch engineer, but they'll resemble that person a lot more. I've seen it happen with people you wouldn't think of as methodical problem solvers. Low code tends to change how people view the business and think about software and technology.

Gerard Newman24:30

I was wondering whether you'll see citizen developer skills popping up on resumes. It's obviously something desirable to look for when recruiting, because people who've been there and done that can bring a lot of knowledge and accelerate an organization's transformation.

John Bratincevic24:53

My expectation is that over the next several years it'll start becoming a job requirement. Whether you're an operations director or a project manager, you'll need skills in platform X, or be willing to use it.

Gerard Newman25:11

One other point: creating internal influencers. You need people in the organization who will evangelize, try things out and always look at things with a digital mindset. If you create that group, they spread the word, educate more people and convince them to get on board and move their processes from manual to automated.

John Bratincevic25:50

I agree.

25:58

Speeding up integration

Watch this part

Ursula Cullen25:58

Organizations need to be able to push and pull information between systems, and I think this is going to be a trending topic in 2022. What trends or advancements do you see speeding up integration? Gerard, would you like to kick us off?

Gerard Newman26:21

Sure. There's continuing growth in demand for integrating processes with all sorts of applications; we're asked about it every day. Integrating cloud applications with other cloud applications isn't that difficult, as there are lots of hooks built in. On-premises applications are trickier, and legacy applications harder still, and the skill level goes up across those three. You don't have to integrate to be successful and get a significant return from digital process automation, but many organizations see process as a layer across a whole range of applications that pulls them together and lets people interact with them simply.

Gerard Newman27:51

One trend is the consumerization of integration. A couple of well-known integration platforms on the web tie into hundreds of applications and let citizen developers configure what were traditionally complex integrations in a couple of clicks, with preconfigured templates. I'd expect those to go from strength to strength this year.

Gerard Newman28:22

Legacy apps are a little more difficult, but still very achievable. With one recent customer it looked like we'd have difficulty integrating with some legacy apps, but when we engaged we found they'd built a common interface into those applications that we could simply reuse. That gave us really good integration for one of their processes at very low cost.

Gerard Newman29:01

At FlowForma, what we invested in during 2021 was building out our integration capabilities, particularly around REST API, which opens us up to integrate with thousands of other applications. We'll continue that, and keep delivering it all in a no-code way, so you don't need specific technical skills. There's constant demand from our customers for more integration. What are you seeing, John?

John Bratincevic29:33

Integration is hard; there's a reason there are products focused on just that. Our survey data shows that on low-code or no-code platforms, whatever label people apply, most things can be done through the tooling. But where people consistently need to code is integration. That last five percent or so is often integration. I think low-code and DPA platforms will keep investing in more, and more complex, connectors.

John Bratincevic30:16

On working practices, a lot of vendors and companies talk about trained developers moving off basic application work, which business people should do, and onto the more complex things. One of those tends to be integration, especially in legacy environments. So in environments that are maturing, I absolutely anticipate the coders doing less application definition and more of the complex integration problems: getting this old system to talk to this new system.

John Bratincevic30:51

In service of that, I also expect acquisitions: some low-code and DPA players buying iPaaS players to expand their capabilities. And I wouldn't be surprised if some iPaaS players get into low code, by building or acquiring. App-building platforms, process platforms and integration platforms all need things from each other, and everyone's converging toward a mega product. So I think that'll happen more between iPaaS and low code.

Gerard Newman31:23

Very interesting. Some of those iPaaS platforms are very impressive in what they do and how quickly you can get integrations up and running. We'll see more and more support for them in no-code and low-code environments; it's something we're particularly interested in at the moment.

31:45

Why digitize: making standard work real

Watch this part

Ursula Cullen31:45

We've been talking about citizen developers, adoption and speed. But John, why is digitization actually important to organizations? Why should they start digitizing their processes?

John Bratincevic32:01

I always say being digital means you turn everything about a business into software, and then change it as the business changes, in near real time. People have historically seen software as a high-risk, selective investment, and that view needs to change. Through the process lens, there's one very important reason you can clearly articulate: the principle of standard work. You have a standard for how something is done, and that's your foundation for continuous improvement.

John Bratincevic32:42

The reality is, if something isn't done by a machine or encoded digitally, there is no standard. It's imaginary, a theory. You write it down, execute it manually or semi-manually, then audit and train to try to get back up to the standard, constantly beating things back up to meet it.

John Bratincevic33:05

When you digitize, turning a process into an application or workflow, the standard work is real. In the immediate term it's inflexible: there's no other way to do it. But if it's built in low code, it's absolutely flexible in the short term, because you can change it. If you want to add another approval, you can, and now that's the new standard. The improvement has happened and it's permanent; you don't slide back.

John Bratincevic33:44

So through the process lens it's simple: processes need to be digitized, because that's your foundation of standard work and continuous improvement. Many people think of processes as a construct on paper they have to train people on. Really, they should reflexively turn into bits and bytes, because that's a fundamentally different medium. That's how standard work really happens.

34:18

Digitize, experiment, improve

Watch this part

Gerard Newman34:18

That traditional approach is interesting. The BPM projects of old were about understanding exactly what the existing process was, getting agreement with the business, redesigning the process, and only then looking at how you could automate it.

John Bratincevic34:34

I often get into minor debates with people who say you don't just digitize how we do it today, you need to re-engineer it. I'm not saying do stupid things or turn a defect into software. But the old-school separation between process and technology, where you engineer your ideal on paper and then turn it into technology, isn't right. Look at it, make the obvious improvements, turn it into a process, see what isn't right, improve it. You digitize, experiment, digitize, experiment.

Gerard Newman35:37

Same thing with those traditional BPM projects: by the time you'd expended all that effort and actually got to automating, you were always in trouble maintaining momentum and enthusiasm. With no code and low code, the approach is automate, measure, improve, and iterate through that cycle.

John Bratincevic36:03

There's a really interesting analogy in the physical world. To enable future continuous improvement, some manufacturing plants would build the plant and the machines with change in mind, rather than making everything absolutely automated and inflexible. They built flexibility into the plant so they could reconfigure it and improve processes. It's very similar here: if you're not pouring it in concrete and you can develop quickly, you can just do it. It's a very different mindset.

Gerard Newman36:51

Absolutely, it's much more agile. And as you digitize your processes, that ultimately delivers a better customer experience, because you have consistent engagement with customers and they know what results to expect. It helps the workforce too, eliminating a lot of manual workarounds and gaps in understanding of how the business works.

John Bratincevic37:38

Yes, you don't have all your DNA hidden in paper, spreadsheets and workarounds, which is the reality.

Gerard Newman37:46

It sure is. When you see what people actually use to run their businesses, spreadsheets are filling the gaps in many cases, because they're an environment people know how to use. When you give them tools that are as easy as, or easier than, spreadsheets, a lot of possibilities open up.

John Bratincevic38:02

Some of the great companies you think of as really digital still run some things on spreadsheets. They're realizing they need to turn those into apps but don't have time, so they use low-code tools in some areas. It's everywhere.

38:28

Overcoming resistance to change

Watch this part

Ursula Cullen38:28

That leads nicely to our next question, on employee resistance. Resistance to change can lead to poor adoption of digital solutions. Can you share some tips on achieving process digitalization by overcoming barriers to change? Gerard, do you want to kick off?

Gerard Newman38:52

It's very natural to resist change; you're changing what people are used to. What you want to do is lead people there. Show them what can be achieved by creating lighthouse processes that people are drawn to, so they see the benefits and how automation improves the way they work. And articulate those benefits in a way that's relevant to them.

Gerard Newman40:07

Communication is really important. That applies to most change, but keep reiterating what you're trying to do, what it will achieve and the next steps, so people understand it's an ongoing initiative that's important to the organization, vital to its future and potentially to its survival.

Gerard Newman40:45

Another question when you're starting out is which process to pick. You want one people can relate to and that becomes an internal reference. It should be important to the organization, understood by a wider audience, and deliver a benefit in a defined period. It doesn't have to be overly complex. And finally, find your champions: enthusiastic people who want to improve things and are happy to mentor others, talk to them and understand their concerns and requirements. They're the internal influencers who can overcome these barriers. John, what would you add?

42:04

Get your stakeholders' DNA on it

Watch this part

John Bratincevic42:04

One important thing: if you're approaching process digitization and automation as a way to reduce headcount, it will never work. People will know. You need a solid cultural foundation that you're doing this to make your product and your internal and external experiences excellent, not to get rid of people. If that isn't sincere, you're stuck.

John Bratincevic42:43

Assuming you're past that barrier, you always want to start where people want to do it: find the willing participants and build momentum. That's just the principle of change. "Look for the pull" is how someone put it to me recently, and I thought that was a good way to put it.

John Bratincevic43:23

The other thing I recommend, a little technical but near magic, I call getting their DNA on it. Find the people who are most important to have on board, whether particular influencers or your user base. Because low-code development is much less risky, cheaper and faster than high code, you can put in things that may not be critical to the goal. If an important stakeholder says "we need this feature" and you do it to show you care, all of a sudden it's their baby and they really care about the solution.

John Bratincevic44:04

It's not manipulative. As a consultant I did this all the time: that's not the reason I'm here, but it's important to you, so I'll put it in. And someone who was out to get me would become the biggest advocate for the project. If it's really a bad idea, explain thoroughly why you're not doing it: this group has this need, there's this implication. You have to pick your battles at scale, but if your overriding ethos is to start with people who are willing, not to reduce headcount, and get people's DNA on it, the buy-in can be remarkable.

45:10

Audience question: success stories

Watch this part

Ursula Cullen45:10

The last question: we reached out to everyone who attended or registered for this webinar and asked if they had questions for you, and one that kept coming up was success stories. People want to hear about the efficiencies and savings organizations have seen once they started to digitize. Any that come to mind?

Gerard Newman45:44

Sure, I have a couple. One is in the construction sector: an organization involved in one of the UK's biggest infrastructure projects. They were enthusiastic about process automation and identified one particular process where, on just one project, they saved just under £80,000. That saving was enough to justify the overall investment in process automation, and they subsequently went on to automate over 50 processes. That one process also took a lot of risk out of their internal processes and administration.

Gerard Newman46:35

Hard cash savings are one way to measure. A potentially easier way to measure return on investment is time saved. One customer, a college, spent a lot of time measuring their processes before automation. After automating six core processes, for administration staff and processes students were directly involved in, they were saving just under 5,000 hours a year. They did a great job of understanding the before situation and measuring against the after. John, I'd be interested to hear some of yours.

47:30

Three stories from Forrester's research

Watch this part

John Bratincevic47:30

I've got some good ones. An auto dealer group in the UK, 50 or 60 dealerships rolled up under one of the big automakers. Their citizen development lean team started as one guy, who realized everything needed to be digitized, because it was all manual, paper-based, highly variable and invisible across the dealerships. His very first low-code project was an experiment: he digitized the trade-in valuation process, which every salesperson did differently. He wired together the APIs and put the logic in, and with just that first experiment they improved profitability on used cars by 60%.

John Bratincevic48:24

Since then they've digitized lots of their value streams, his team is six or seven people, and CX and profitability are much higher. I don't know how all of it is quantified, but that first experiment was a big boom. The value of digitizing everything is almost immeasurable.

John Bratincevic48:47

Another example: a big telecom in Asia, 8,000 people. They ran a hackathon and started building apps on the platform. They now have about 200 apps, about 700 people trained and about 100 active developers. They estimate about an 80% efficiency improvement across the processes those apps cover. They also estimated the development savings, compared with coding those apps and minus licensing, at about 7 million, though they never would have built them otherwise.

John Bratincevic49:35

One of my favorites is a big manufacturer that bought a manufacturing execution system, spent a few million on it and tried to roll it out across seven plants. Each plant improves its processes differently, so they couldn't align to the standard software, and after several years they canned it. Instead, manufacturing engineers and continuous improvement coordinators, people just out of college learning the business, built the manufacturing execution system on a low-code platform: about 45 apps, around a million transactions a month, at about 10% of the cost. They have a continuous improvement culture in the plants and make apps to solve problems, including IoT use cases and machine interfaces. It's real.

50:55

FlowForma's approach: one process at a time

Watch this part

Ursula Cullen50:55

I'm sure we could chat all day about success stories, but we're tight on time. A reminder: if you have questions, pop them into the Q&A and we'll squeeze in as many as we can at the end. For now, I'll hand over to Gerard to talk a little about FlowForma process automation.

Gerard Newman51:26

Thanks. As you've probably picked up, at FlowForma we strongly believe in no code. The original product was designed to let business people take control of process digitization and do it themselves, in response to the traditionally slow rollout of BPM initiatives that John and I were just discussing. Everything we do being no code is core to our values.

Gerard Newman52:07

We like to talk about automating one process at a time. Customers who have achieved really large-scale process automation all took that first step with one process, which became a cornerstone of their digital transformation. Automating one process at a time helps manage change and ensure success. It also sharpens minds and unleashes innovation: once people see what no-code automation can achieve, how you can iterate on ideas and respond quickly to change requests, they wake up to what they can ask for and what they can do themselves. And that leads to better customer experiences, because your internal processes are strong, efficient and effective.

53:43

About FlowForma

Watch this part

Ursula Cullen53:43

For those of you who don't know FlowForma: we're an award-winning provider of process automation solutions, and our FlowForma tool has been recognized for revolutionizing how business process management can be achieved. Our approach is no code, and has been from the very start. Over 200,000 people use our product across the globe, we've received multiple awards from Microsoft for the innovations we've brought to its platforms, and we feature in the Forrester Waves as one of the no-code providers.

54:38

FlowForma in 2022: Engage, analytics and REST API

Watch this part

Gerard Newman54:38

Thanks. For those already using our product, there are three areas we're looking at in 2022. First, Engage. A lot more organizations are using Engage, part of the FlowForma platform, which lets you involve people outside the boundaries of your organization in your processes. Quite a few customers built it out in 2021. It makes internal processes more efficient, gives you better-quality data coming into your processes at the start, and engages your customers in a different way. We'll invest more in it in 2022. If you're not using it yet, talk to customer services about how it could apply to you.

Gerard Newman55:34

Second, analytics. We capture a whole layer of process and operational data, and we're working to make sure people can use it in the tools they want to analyze it with. Third, integration: we had considerable success with the REST API integration we launched in 2021. We'll keep working on it, and integrate with other integration platforms to extend our capabilities further. If you're an existing customer and haven't looked at the REST API integration, I'd suggest you do.

56:20

Customer examples: Dresser and Morgan Construction

Watch this part

Gerard Newman56:20

Here are some of our customers. Dresser, an engineering company based in the US, has some good testimonials. They developed their own citizen development capability, which accelerated their transformation and let them automate their processes much faster and more effectively than the platform they had been using.

Gerard Newman56:59

There's also a great webinar with Morgan Construction on our website. They're a Canadian company, and their reason for automating was contractor onboarding: they do a huge amount of it, and were running the whole process on spreadsheets and whiteboards. Automating it quickly gave them much more insight into the process, and that information is eagerly awaited by their senior management team, who track how onboarding is going and how many people they've recruited.

57:40

Q&A: Who makes a good citizen developer?

Watch this part

Ursula Cullen57:40

Thank you, Gerard. I know we were tight on time. We have literally two minutes left, so we might get through a question or two. One question that came in: how would you pick who's the best person to become a citizen developer in an organization?

John Bratincevic58:14

Find your natural problem solvers, the people who want to make things better. You can give them an aptitude test if you want, and people have done that. But the people who want to change things are motivated. It's not necessarily the people writing macros; it's the people who understand the problem and want to fix it.

Ursula Cullen58:30

Perfect. Gerard, do you agree?

Gerard Newman58:33

Very much. That's our experience too. When we engage people in our SureStart program, we like to see problem solvers who understand the business and want to get things done. They're always good people to work with.

John Bratincevic58:45

The macro jockeys could be, but that's not necessarily what you're looking for.

58:53

Q&A: How quickly can you go live?

Watch this part

Ursula Cullen58:53

Quickly, Gerard, you might take this one. With a no-code process automation strategy, how quickly can organizations go live with a digitized process?

Gerard Newman59:10

This is actually one of our core internal business measurements: we work with customers to achieve a return on investment in a very short space of time. One recent example: a customer took 35 days working with us through our SureStart program to get from initial concept to a live operational process, and that included training their people on the FlowForma platform. It depends on the organization, but it's something you can definitely push and achieve quickly.

59:52

Thanks and close

Watch this part

Ursula Cullen59:52

Brilliant, thank you. That's all we have time for. I'm sorry if we didn't get to your question; someone from our team will get back to you as soon as possible. Thank you all for watching, and thank you, John and Gerard, for your great insights. I really loved the Q&A style and hearing your trends for 2022.

Ursula Cullen60:16

There are some resources in the column on the right-hand side, including some case studies, and if you'd like to sign up for a free trial, pop over to the FlowForma website. Please fill in the short three-question survey at the end; it really helps us create fresh content for you. Thanks again, Gerard and John, and hopefully we'll see you very soon.

Frequently asked questions

Who presented this webinar?

John Bratincevic, Senior Analyst at Forrester, and Gerard Newman, CTO at FlowForma, with FlowForma's Ursula Cullen hosting. The webinar took place on January 25, 2022.

Who makes a good citizen developer?

John's advice is to find your natural problem solvers: the people who understand the problem and are motivated to fix it, not necessarily the people writing macros. Gerard agreed, adding that problem solvers who understand the business and want to get things done are the best people to work with in FlowForma's SureStart program.

How quickly can you go live with a digitized process?

It depends on the organization, but Gerard shared a recent example: a customer took 35 days working with FlowForma through its SureStart program to go from initial concept to a live process, and that included training their people on the platform.

What results have organizations seen from digitizing their processes?

Gerard shared two FlowForma customers. On one of the UK's biggest infrastructure projects, one process saved just under £80,000 on a single project, enough to justify the overall investment, and the customer went on to automate over 50 processes. A college saved just under 5,000 hours a year after automating six processes. John added examples from his research in auto retail, telecoms and manufacturing.

How should organizations govern citizen development?

John suggests answering who, what and how: who can develop, what they can build (use cases, data, complexity, internal or customer-facing) and how they build it (the development process, testing and support). Different rules should apply to different levels of risk, and at scale those policies need to be built into the platform. Gerard noted that IT leaders want to avoid business-critical apps that nobody supports.

How do you overcome resistance to change?

Gerard recommends lighthouse processes that show what's possible, constant communication, a first process that matters and that people understand, and internal champions. John adds that automation aimed at cutting headcount will never win buy-in: start where people want the change, and build in what key stakeholders ask for so they feel ownership.

Ready to automate, one process at a time?

Book a tailored demo, or start a free trial and build it yourself.