How much complexity can Enterprise Low Code support?

By their nature:

Low Code and No Code solutions minimise the number of decisions a user needs to make in order to simplify the design process, but maximise the leverage of those decisions to speed up the outcome.

They do this by making assumptions to transform the smaller number of decisions into their proprietary pattern based code.

But every enterprise has unique requirements, which cannot all be met by a standard commercial platforms with proprietary patterns optimised for a mass customer base.

So major considerations for enterprises when considering Low Code and No Code options are:

• The level of complexity they can support out of the box, and
• how much customisation and extension effort will be required to meet enterprise objectives

Generalised Code Printing complexity, however, is only limited by the complexity that its information model can readily support.

Simple Information Models

Where design templates are implemented in a simple text file, or a database or spreadsheet table, their complexity is heavily constrained. They may be associated with a simple form to assist a person to use them correctly.

A target pattern based on these structures will necessarily be simple and limited support can be provided to prefill parts of the structures from existing enterprise knowledge assets such as:

• Enterprise Data Structures
• API contracts
• Enterprise rules etc.

A mail merge is a good example of a simple information model and pattern.

The information model is just a list of names and address related fields and these are processed into a target pattern that takes the form of a letter or email.

Multi-Dimensional Information Models

Implementing information models in spreadsheets is flexible and allows for much greater levels of complexity as a spreadsheet provides natural support for mappings between data sources, API contracts etc.

Additionally, with multiple sheets per spreadsheet and the ability to refer between spreadsheets it can support:

• Reasonably complex modules with different pattern components
• Chains of modules representing more than one pattern

Additionally mapping designs can be automatically initiated and prefilled to speed up the decision-making process for an analyst. That is:

Existing enterprise knowledge assets can be selected by an analyst to rapidly flesh out designs and provide greater accuracy

As flexible as a spreadsheet is, that very flexibility can create limitations in its usability:

• It is difficult to make a spreadsheet template easy to understand so on-boarding is more complex
• Changes in design decisions are difficult to track
• Changes to templates can't readily be retrofitted to existing designs
• It is not straightforward to add access to external knowledge assets

Complex Information Models

A markup document such as XML, JSON or YAML can provide the virtually infinite complexity required by an Enterprise.

However:

• They are not very analyst friendly
• It is difficult to merge in enterprise knowledge
• It is difficult to reuse these component designs for multiple purposes

What can resolve these challenges is to implement UI/UX guide user input in the design process and provide access to enterprise knowledge. However:

• The effort to design, deliver, train and maintain and application can be significant
• It is still difficult to reuse these component designs for multiple purposes

Delivering an application to guide the design process is the most fit for purpose approach, as virtually any level of complexity can be supported in the application data structures and the optimal process can be implemented in UI/UX for any given pattern.

However, the very effort to build and maintain these applications has historically been a major barrier to adopting an internal Low Code approach.

The reality for Enterprise Low Code

The challenges in designing, delivering, training and maintaining low code in the enterprise make it almost inaccessible as an option.

Enterprises may implement point solutions for high value and volume patterns, often without UI/UX support which leaves a high on-boarding effort for new resources and undermines the sustainability of solutions.

Instead enterprises typically opt for a combination of commercial Low Code platform offerings combined with Pro Code extensions which provide some benefits, but don't enable a change in the way they deliver.

More often, they stay with the traditional hand crafted Pro Code approach, with all its shortcomings.

The future of Enterprise Low Code

Enterprise Low Code is the future of enterprise delivery for the reasons we discussed in What is Code Printing?

And the future of Enterprise Low Code has to be enabling platforms which simplify implementation of complex information models and patterns.

Also On The Blog

• What is Code Printing?
• Why has In-house Low Code now become feasible for an enterprise?
• What is Low Code?