Featured

The Latest

IBRS interviewed low-code vendor Kintone, exploring its unique capabilities. The Japanese company is looking to expand its presence in the Australian market through traditional channels and some unexpected partners.

Why it’s Important

As detailed in the ‘VENDORiQ: Cloud low-code vendor Webflow secures US$140 million’, the low-code market is growing rapidly. Kintone is a Japanese vendor, founded in 1997. The firm’s platform focuses as much on collaboration around digitised processes as it does on the development of applications - with every process having ‘conversational threads’. The firm’s clients in Australia are predominantly Japanese firms with local operations.

Who’s impacted?

  • Development team leads
  • Workforce transformation leads

What’s Next?

Kintone addresses the low to mid-range of the IBRS spectrum of services for eforms and low-code environments. It is suited for less-technical staff (including business analysts) to create structured processes that include collaboration. 

Kintone’s approach is worth noting, since many of the processes digitised by low-code platforms are replacing ad-hoc, messy processes that are often managed with manual activities and collaboration. There is an active evolution from manual, collaborative processes to digitised processes.

Kintone has a stable financial base via its strength in the Japanese market. Skills, training and support for Kintone are comparatively weak in the domestic market. However, Kintone is looking to partner with IT services organisations and partners with strengths in providing printing and digitisation technologies. 

Related IBRS Advisory

  1. How to succeed with eforms Part 1: Understand the need.
  2. Workforce transformation part 4: Non-techies are taking over your developers’ jobs – Dealing with the fallout
  3. Aussie vendor radar: Nintex joins the mainstream business process automation vendor landscape
  4. VENDORiQ: Cloud low-code vendor Webflow secures US$140 million

The Latest

IBRS interviewed Appian, a low-code vendor that specialises in providing business analysts and developers with a platform to deliver custom enterprise applications. The vendor has seen strong growth in the later half of 2020 due to organisations needing to quickly develop new applications to address lockdowns and new digital service delivery demands. The vendor also detailed how it is leveraging machine learning to guide users through the development of applications. The use of machine learning to recommend low-code application designs and workflows is a key differentiator for Appian.

Why it’s Important

As detailed in the 'VENDORiQ: Cloud low-code vendor Webflow secures $140 million', the low-code market is growing rapidly. Appian is a major global vendor in the low-code market. It positions itself above the non-technical / citizen-developer tools such as Forms.IO, but below the specialised development team platforms such as Out systems. Appian’s ‘sweet spot’ is teams of business stakeholders working with business analysts and developers to jointly prototype and then put into production applications. 

Appian has been expanding the use of machine learning algorithms to application design. During application development, the algorithms will make recommendations on fields that are needed on forms, workflow steps, approval processes, etc.

Who’s impacted

  • CIO
  • Development team leads
  • Business analysts

What’s Next?

When selecting a low-code platform, organisations should be very clear about who the stakeholders are, who will use the platform, the project management model for application development and the applications to be developed.  

In the case of Appian, there is clearly a close alignment with Agile business methodologies, which extend beyond the ICT group as outlined in the 'IBRS Snapshot: Agile Service Spectrum'.

The use of AI during the development applications is a feature more than a gimmick. This ‘guided’ approach to design not only speeds up application development, but by analysing a large body of existing applications and drawing inferences based on usage and effectiveness, it helps ensure that ‘best practices’ in workflows are not overlooked.

Related IBRS Advisory

  1. How to succeed with eforms Part 1: Understand the need.
  2. Workforce transformation part 4: Non-techies are taking over your developers’ jobs – Dealing with the fallout
  3. Aussie vendor radar: Nintex joins the mainstream business process automation vendor landscape
  4. VENDORiQ: Cloud low-code vendor Webflow secures US$140 million

The Latest

Webflow, a Cloud-based low-code vendor, has secured US$140 in investment. The new round of investment values the vendor at US$2.1 billion. 

Why it’s Important

The low-code market exploded over the last year. Newer entrants, such as Webflow (founded in 2012), are attracting significant venture capital. Just 17 months ago, Webflow took $72 million investments which valued the company at $400 million. The new investments thrust the vendor into unicorn status. At the same time, well-established low-code vendors such as Nintex and Microsoft are consolidating and expanding their portfolios to include robotic process automation, process modelling and integration tools.

The market for low-code is not yet at the peak of its feverish growth, but IBRS cautions that current rates of investment and hype are unsustainable. There will be turmoil as the mark begins to consolidate, likely in 2023 to 2026.

Who’s impacted

  • CIO
  • Development team leads
  • Workforce transformation leads

What’s Next?

Low-code development is not a new concept. However, the uptake of Cloud platforms, common data models, robot process automation and business modelling are extending the notion of low-code development from simple ‘e-forms’ tools to services that enable enterprise-grade process digitisation.  

The pandemic and working from home has supercharged the need for process digitisation, and low-code vendors are all seeing strong sales growth. 

Unfortunately, the term ‘low-code’ is starting to become meaningless, as vendors that provide very different application development tools and platforms attach the term to their products.  IBRS recommends organisations view ‘low code’ as a broad term that covers a spectrum of capabilities, as detailed in 'How to succeed with eforms Part 1: Understand the need'. It is likely that most organisations will need to acquire two low-code products to cover different parts of this spectrum: one product aimed at non-technical staff for simple e-forms, and another product to increase the agility of pro-developers in the ICT group.

Consider the financial backing and stability of a vendor when selecting low-code tools, as market consolidation is on the horizon. You do not wish to be developing business processes on a platform they will outlive.

Related IBRS Advisory

  1. How to succeed with eforms Part 1: Understand the need.
  2. Workforce transformation part 4: Non-techies are taking over your developers’ jobs – Dealing with the fallout
  3. Aussie vendor radar: Nintex joins the mainstream business process automation vendor landscape
  4. IBRSiQ: Can IBRS assist in identifying a mobility platform other than Xalt?

With the rush to deploy Teams to enable remote work in 2020, the majority of organisations have not yet fully considered the highly disruptive nature of deep collaboration. Governance has been largely overlooked in the effort to ‘just get people working’. IBRS outlines the seven critical areas of governance that must be immediately addressed for Teams to be sustainable and to mitigate the new risks (and benefits!) of deep collaboration. Find attached a PDF of the webinar to download for free. Or to view the webinar, click on the video below.

 

Conclusion: Most organisations have vast pools of data (a. k.a. information assets) lying underutilised, as many IT and business professionals are unsure where it is stored and are unaware of its value. To turn the situation around organisations must strive for data mastery1, which is the ability to embed the data into products and services to increase efficiency, revenue growth and customer engagement.

Conclusion: Regardless of its digital strategy, many organisations have not been positioned to properly leverage the digital and data assets that are available to them. A Chief Data Officer (CDO) role can improve this situation by advancing an organisation’s data portfolio, curating and making appropriate data visible and actionable.

The CDO position is appropriate for all larger organisations, and small-to-large organisations focused on data-driven decision-making and innovation. These organisations benefit from a point person overseeing data management, data quality, and data strategy. CDOs are also responsible for developing a culture that supports data analytics and business intelligence, and the process of drawing valuable insights from data. In summary, they are responsible for improving data literacy within the organisation.