Read on Twitter
there!As part of the Product team @okta, I spend my days thinking about how to build a better no-code platform.
I've loved lurking within the no-code community and am excited to share what we're doing - focused on Identity and the Enterprise.
A thread below
I'm a strong believer that no-code is more than just a fad.
It's lowered the barrier to entry for anyone to build an app or complex automation. It's reduced the maintenance burden of custom code.
It's lowered the barrier to entry for anyone to build an app or complex automation. It's reduced the maintenance burden of custom code.
While there's been a ton of focus on individual builders, there hasn't been as much focus on the Enterprise (at least on Twitter).
How does the adoption of no-code differ in the Enterprise? Am glad you asked
Here are 5 ways.
How does the adoption of no-code differ in the Enterprise? Am glad you asked
Here are 5 ways.
1) Enterprises are...slower. Mind blowing, I know.
Demos, POCs, testing, and deployment cycles all take time. With no-code, think weeks instead of hours from start to "live in production".
Demos, POCs, testing, and deployment cycles all take time. With no-code, think weeks instead of hours from start to "live in production".
2) To solve a problem, Enterprises have many choices when it comes to tooling.
A no-code automation platform is more likely to be replacing an existing tool with all the history and baggage that comes along with it than solving something totally greenfield.
A no-code automation platform is more likely to be replacing an existing tool with all the history and baggage that comes along with it than solving something totally greenfield.
3) Enterprises have budget, and those dollars can get big, with purchasing often happening top-down. 
The "builders" are important influencers but often need approval from the C-suite (CIO/CTO).
The "builders" are important influencers but often need approval from the C-suite (CIO/CTO).
4) In customer conversations, three areas always come up: Scalability, Reliability and Performance.
Enterprises treat any automation platform, no-code or not, as core infrastructure, and these non-functional requirements are as critical as whether we can solve their problem.
Enterprises treat any automation platform, no-code or not, as core infrastructure, and these non-functional requirements are as critical as whether we can solve their problem.
5) The value prop of no-code leans towards easing the maintenance burden of automation.
Building is easy - they could hire a team of developers - but maintenance is the challenging piece. Shit breaks.
No-code extends the # of ppl who can understand and maintain automation.
Building is easy - they could hire a team of developers - but maintenance is the challenging piece. Shit breaks.
No-code extends the # of ppl who can understand and maintain automation.
I hope this helps relay my experience at @okta over the past few years.
I'm inspired by a growing and active community ( @edavidpeterson @wadefoster @bentossell), and a great set of companies ( @zapier @Workato @boomi @bubble @webflow) and am looking forward to contributing!
I'm inspired by a growing and active community ( @edavidpeterson @wadefoster @bentossell), and a great set of companies ( @zapier @Workato @boomi @bubble @webflow) and am looking forward to contributing!