First Principles of SaaS UX · CHAPTER 1 OF 7

Getting started

A framework by Upslide Design Studio

Data Principles of SaaS UX

How to break complex B2B SaaS and enterprise software down into data, actions, priorities, and dependencies.

Enterprise SaaS

Ux Principles

Illustration accompanying Data Principles of SaaS UX

Data Principles of SaaS UX

How to break complex B2B SaaS and enterprise software down into data, actions, priorities, and dependencies.

Enterprise SaaS

Ux Principles

Illustration accompanying Data Principles of SaaS UX

Who This Guide Is For

Illustration accompanying This guide is for teams building or redesigning SaaS software.

This guide is for teams
building or redesigning SaaS software.

This guide is for teams building or redesigning SaaS software.: Low Feature Adoption Legacy UI Long Onboarding Cycles Complex Workflows Heavy Training Dependency Confusing Navigation

Low Feature Adoption

This guide is for teams building or redesigning SaaS software.: Low Feature Adoption Legacy UI Long Onboarding Cycles Complex Workflows Heavy Training Dependency Confusing Navigation

Legacy UI

This guide is for teams building or redesigning SaaS software.: Low Feature Adoption Legacy UI Long Onboarding Cycles Complex Workflows Heavy Training Dependency Confusing Navigation

Long Onboarding Cycles

This guide is for teams building or redesigning SaaS software.: Low Feature Adoption Legacy UI Long Onboarding Cycles Complex Workflows Heavy Training Dependency Confusing Navigation

Complex Workflows

This guide is for teams building or redesigning SaaS software.: Low Feature Adoption Legacy UI Long Onboarding Cycles Complex Workflows Heavy Training Dependency Confusing Navigation

Heavy Training Dependency

This guide is for teams building or redesigning SaaS software.: Low Feature Adoption Legacy UI Long Onboarding Cycles Complex Workflows Heavy Training Dependency Confusing Navigation

Confusing Navigation

Whose Software Has

This guide is for teams building or redesigning SaaS software.

Whose Software Has

This guide is for teams building or redesigning SaaS software.: Low Feature Adoption Legacy UI Long Onboarding Cycles Complex Workflows Heavy Training Dependency Confusing Navigation

Complex Workflows

This guide is for teams building or redesigning SaaS software.: Low Feature Adoption Legacy UI Long Onboarding Cycles Complex Workflows Heavy Training Dependency Confusing Navigation

Heavy Training Dependency

This guide is for teams building or redesigning SaaS software.: Low Feature Adoption Legacy UI Long Onboarding Cycles Complex Workflows Heavy Training Dependency Confusing Navigation

Confusing Navigation

This guide is for teams building or redesigning SaaS software.: Low Feature Adoption Legacy UI Long Onboarding Cycles Complex Workflows Heavy Training Dependency Confusing Navigation

Low Feature Adoption

This guide is for teams building or redesigning SaaS software.: Low Feature Adoption Legacy UI Long Onboarding Cycles Complex Workflows Heavy Training Dependency Confusing Navigation

Legacy UI

This guide is for teams building or redesigning SaaS software.: Low Feature Adoption Legacy UI Long Onboarding Cycles Complex Workflows Heavy Training Dependency Confusing Navigation

Long Onboarding Cycles

Illustration accompanying This guide is for teams building or redesigning SaaS software.

Why This Guide Exists

Helping You Break Down Complex Software

While redesigning enterprise and B2B SaaS products, we repeatedly see the same challenge:

​

The software has too many features, screens, roles, workflows, permissions, and dependencies to understand at once.

​

So instead of starting with screens, we break the product down to its fundamentals.

Helping You Break Down Complex Software: This guide explains how

This guide explains how

Helping You Break Down Complex Software

While redesigning enterprise and B2B SaaS products, we repeatedly see the same challenge:

The software has too many features, screens, roles, workflows, permissions, and dependencies to understand at once.

So instead of starting with screens, we break the product down to its fundamentals.

Helping You Break Down Complex Software: This guide explains how

This guide explains how

First Principles Simplify the Complexity

When we strip all of that complexity down to its most fundamental level, almost everything happening inside software revolves around one thing: data

Because software, at its core, is data.

Data

Logo

Logo

Logo

Logo

Logo

First Principles Simplify the Complexity: Data Logo Logo Logo Logo Logo
First Principles Simplify the Complexity: Data Logo Logo Logo Logo Logo
First Principles Simplify the Complexity: Data Logo Logo Logo Logo Logo
First Principles Simplify the Complexity: Data Logo Logo Logo Logo Logo
First Principles Simplify the Complexity: Data Logo Logo Logo Logo Logo
First Principles Simplify the Complexity: Data Logo Logo Logo Logo Logo

First Principles Simplify the Complexity

When we strip all of that complexity down to its most fundamental level, almost everything happening inside software revolves around one thing: data Because software, at its core, is data.

Data

Logo

Logo

Logo

Logo

Logo

First Principles Simplify the Complexity: Data Logo Logo Logo Logo Logo
First Principles Simplify the Complexity: Data Logo Logo Logo Logo Logo
First Principles Simplify the Complexity: Data Logo Logo Logo Logo Logo
First Principles Simplify the Complexity: Data Logo Logo Logo Logo Logo
First Principles Simplify the Complexity: Data Logo Logo Logo Logo Logo
First Principles Simplify the Complexity: Data Logo Logo Logo Logo Logo

Think About a Gym Tracking App

You enter: Workout type, Exercise, Weight, Reps, Sets

These are all data being added to the software.

​

The next time you work out, you look at your previous data and decide to increase the weight or reps.

​

So software is not just about storing data. We also take actions based on it.

Illustration accompanying Think About a Gym Tracking App
Illustration accompanying Think About a Gym Tracking App

Think About a Gym Tracking App

You enter: Workout type, Exercise, Weight, Reps, Sets

These are all data being added to the software.

The next time you work out, you look at your previous data and decide to increase the weight or reps.

So software is not just about storing data. We also take actions based on it.

Illustration accompanying Think About a Gym Tracking App
Illustration accompanying Think About a Gym Tracking App

The Core Software Pattern

Most Software Interactions Follow the Same Pattern

Users: Create Data, View Data, Modify Data, Act on Data

​

The software may become much more complicated, but this basic relationship remains the same.

Create Data

View Data

Modify Data

Act On Data

Users

The Core Software Pattern: Create Data View Data Modify Data Act On Data Users

The Core Software Pattern

Most Software Interactions Follow the Same Pattern

Users: Create Data, View Data, Modify Data, Act on Data

The software may become much more complicated, but this basic relationship remains the same.

Create Data

View Data

Modify Data

Act On Data

Users

The Core Software Pattern: Create Data View Data Modify Data Act On Data Users

FRAMEWORK CONTENTS

First Principles of SaaS UX

Search documentation

Search scope

Search across all eight guides.

Diagram detail