Progressive enhancement: a mindset for designing no-code platforms - No Code Conf 2019

DESIGNING NO CODE TOOLS | @lizkhoo
👋 I’m Liz
Damien Newman, “The Design Squiggle”

This presentation may contain forward-looking statements that involve risks, uncertainties, and assumptions. If any such uncertainties materialize or if
any of the assumptions proves incorrect, the results of salesforce.com, inc. could differ materially from the results expressed or implied by the forward-
looking statements we make. All statements other than statements of historical fact could be deemed forward-looking, including any projections of
product or service availability, subscriber growth, earnings, revenues, or other financial items and any statements regarding strategies or plans of
management for future operations, statements of belief, any statements concerning new, planned, or upgraded services or technology developments
and customer contracts or use of our services.
The risks and uncertainties referred to above include – but are not limited to – risks associated with developing and delivering new functionality for our
service, new products and services, our new business model, our past operating losses, possible fluctuations in our operating results and rate of
growth, interruptions or delays in our Web hosting, breach of our security measures, the outcome of any litigation, risks associated with completed and
any possible mergers and acquisitions, the immature market in which we operate, our relatively limited operating history, our ability to expand, retain,
and motivate our employees and manage our growth, new releases of our service and successful customer deployment, our limited history reselling
non-salesforce.com products, and utilization and selling to larger enterprise customers. Further information on potential factors that could affect the
financial results of salesforce.com, inc. is included in our annual report on Form 10-K for the most recent fiscal year and in our quarterly report on
Form 10-Q for the most recent fiscal quarter. These documents and others containing important disclosures are available on the SEC Filings section of
the Investor Information section of our Web site.
Any unreleased services or features referenced in this or other presentations, press releases or public statements are not currently available and may
not be delivered on time or at all. Customers who purchase our services should make the purchase decisions based upon features that are currently
available. Salesforce.com, inc. assumes no obligation and does not intend to update these forward-looking statements.
Forward-Looking Statement
Statement under the Private Securities Litigation Reform Act of 1995

DESIGNING NO CODE TOOLS | @LizKhoo
Most investors would tell us that
Webflow was either too hard to
use for non-technical people, or
not powerful enough for
professional use cases.
- Vlad Magdalin, Webflow

Simplicity 
No Code
Capability
Code

$16+ B
FY20 annual revenue guidance

10

Admins Developers

user research

user research
~40%
Of respondents code
~30%
Identified as developers

user research
~90%
Of coders also use click-based tools

“It’s not just
code vs.
no-code
anymore.”

Clicks Code

Builders
People who customize
and enhance Salesforce
using no code tools.

🤔…

Business Logic
Data Model
App Dev Stack
User Interface

Business Logic
Data Model
User Interface
App Dev Stack

Process Builder Flow Builder

Process Builder Flow Builder Code

Progressive Enhancement

Progressive Enhancement is
the principle of starting with a
rock-solid foundation and then
adding enhancements to it if
you know certain visiting user-
agents can handle the
improved experience.
- Sam Dwyer 
Smashing Magazine, 2009

for
No Code Tools
Progressive Enhancement

30
🥾 Stepping Stones
🧠 Smart Defaults
⚙ Transparent Automation

Guide users through their
learning journey, providing the
next step at the right time.
🥾 Stepping Stones

Start

Progressive enhancement: a mindset for designing no-code platforms - No Code Conf 2019

DESIGNING NO CODE TOOLS | @LizKhooGIF by Brady Sammons | @soulrider911

Prioritize the 20% of features
that meet 80% of use cases.
🧠 Smart Defaults

Trigger Types, a pro-code concept

Before Trigger Type After Trigger Type

80% Use Case

20% Features

Start this flow when
a record is saved
Before Trigger Type

a record is saved
Start this flow after
a record is saved
Advanced Options
Before Trigger Type

Start this flow after
a record is saved
a record is saved
Advanced Options
After Trigger Type
Before Trigger Type

Automate the complex stuff
but give users a way to inspect
and override defaults.
⚙ Transparent Automation

x=

{Data.value_1; 
value_2;
value_3;
Etc} 
x = VariableName
{Type:Text;
Array:Yes;
Etc.}
Get Records
Lookup Data

🌬 phew…

DESIGNING NO CODE TOOLS | @LizKhooDESIGNING NO CODE TOOLS | @LizKhoo

What are your users saying  
that can help you…

64
🥾 Stepping Stones?
🧠 Smart Defaults?
⚙ Transparent Automation?

Thank
You
Liz Khoo
@lizkhoo
Salesforce UX
@salesforceux
👋

Progressive enhancement: a mindset for designing no-code platforms - No Code Conf 2019

More Related Content

What's hot (20)

Similar to Progressive enhancement: a mindset for designing no-code platforms - No Code Conf 2019 (20)

More from Webflow (19)

Recently uploaded (20)

Progressive enhancement: a mindset for designing no-code platforms - No Code Conf 2019