Slides from my talk at CraftConf Budapest in May 2023 about how developers can embrace and shape low code applications in their organizations to help the business automate more
5. 1. A broken end-to-end
automation
Local automations are
not integrated with one
another, the end-to-end
process is not fully
automated.
Lack of understanding
The end-to-end process
is not fully visible
and key metrics are
hard to track.
2. Lack of flexibility
Changing the end-to-end
process is difficult
since it leads to
potential changes in
many different systems.
3.
@berndruecker
13. Runs anywhere
Supports any
programming language
Available as a SaaS service
Manage it yourself (in your own
cloud, your datacenter, your
laptop)
Clients for Java, C#,
NodeJS, Go, … available
Natively integrates into
your stack
@berndruecker
31. The Process Automation Map
Unique
Standard
Desired
Unnecessary
Complex
Simple Process complexity
Process Innovation
Process
Big
Small Scale
Process
Task Scope
Planned
Ad-hoc or temporary Project setup
e.g. accounting software e.g. onboarding process that needs to
include a lot of legacy systems
e.g. insurances using telematics data
e.g. webshop selling
innovative products
e.g. integrating one
standard cloud system with
another
e.g. one business
department solving a local
pain
e.g. end-to-end loan origination
process invoking lots of other services
e.g. lots of applications, people or
developers involved. Large volume of
instances.
e.g. automating one single
task in a larger process
e.g. end-to-end processes like
customer onboarding, loan
origination, order fulfillment.
e.g. a budgeted ITproject resulting
in an application having a couple of
years life time.
e.g. a one-time data
adjustment for millions of
records
@berndruecker
33. The Process Automation Map
Unique
Standard
Desired
Unnecessary
Complex
Simple Process complexity
Process Innovation
Process
Big
Small Scale
Process
Task Scope
Planned
Ad-hoc or temporary Project setup
@berndruecker
34. Camunda’s open
platform supports our
individual needs in a way
that closed BPM suites
just cannot achieve. Our
BPMN process models are
executed directly, which
improved communication
between business and
development, which also
shortens development
cycles.
Marko Lehn
Software Engineering
Team Lead
Zalando
“
35. The Process Automation Map
Unique
Standard
Desired
Unnecessary
Complex
Simple Process complexity
Process Innovation
Process
Small Scale
Task Scope
Ad-hoc or temporary Project setup
Big
Process
Planned
@berndruecker
36. Desired
Process Innovation
Unnecessary
Commercial Off-the-shelf Unique
Process
Standard
Complex
Process complexity
Big
Scale
Process
Scope
Strategic
Ad-hoc or temporary Project setup
Simple
Small
Task
Low Code
Pro Code
Sweet
Spots
Commercial Off-the-shelf
Tailor-Made
@berndruecker
52. Improving your team topologies
Traditional
Development
Models Business
folks Business analyst Development
team
Business
folks
or:
IT
New way of
working
Diversified
solution team
Enablement
and support
Input
@berndruecker
56. Running an orchestration platform
Microservice A
Orchestration
Engine
Microservice B Microservice C
Orchestration
Engine
Ideally SaaS
(probably self-managed)
Every microservice (process solution) owns its process model, glue code, and any additional artifacts
Orchestration
Engine
@berndruecker
57. Platform or CoE does NOT mean unhealthy centralization!
@berndruecker
60. Cognitive Load
Intrinsic cognitive load
Fundamentals
(“How to program with Java?”)
Extraneous cognitive load
Environment
(“How to deploy this?”)
Germane cognitive load
The real task
(“How to solve this business problem?”)
@berndruecker
61. Cognitive Load
Germane cognitive load
The real task
(“How to solve this business problem?”)
Reduce intrinsic cognitive load
. Higher abstractions, moving technical details
. Diverse mix of people
Reduce extraneous cognitive load
. Golden paths
. Platforms, PaaS, SaaS, Cloud Services
. Center of excellence
> Free up capacity to solve the real business problems
@berndruecker
63. Microservices praise autonomy.
This does not mean to dump more cognitive load on teams.
It does mean to define proper domain boundaries.
Enable teams to concentrate on business value.
@berndruecker