Conditional logic

client

Seismic

Role

UX Design

UI Design

Web/Mobile
Dev

Tools

Figma

Micro

Timeline

Discovery 11/21
Design 12/21 – 02/22
Public release 05/22

Summary

Custom properties are driving many of the key value propositions for Seismic today.

project goals

– Utilize technology to refine the dining out experience
– Bring the 2D menu onto a 3D AR space
– Clean up the time customers are in the restaurant: seating, searching, ordering, checkout and leaving.

PROJECT GOALS

– Utilize technology to refine the dining out experience
– Bring the 2D menu onto a 3D AR space
– Clean up the time customers are in the restaurant: seating, searching, ordering, checkout and leaving.

User can add properties to a piece of content for easy discovery
The previous way to add logic was cumbersome and limited. Nested conditions were not possible

Voice of Customer — a mere ~$160M

user priorities

As an admin:
I want to enable sellers to easily create personalized content.

I want to see a place to manage global metadata custom properties.

I want to enable sellers with the right content at the right time.

When managing my custom properties I want to define which properties should be used for content, projects, tasks, and users.

I want to audit, optimize and update my stale content.

I want to define the order my properties are displayed in content, projects and tasks.

main painpoints

Flax taxonomy woes

  • All properties and values visible at all times
  • Created overwhelming tagging experience
  • Leads to incorrect tagging or NO tagging at all

Hard to share content across teams

  • Duplicate content created across teams
  • Manual and time confusing process to manage and paintain
  • Content properties MUST match across teams in order to publish

IBM has 40+ content properties and some properties have over 2000 values.

PNC has six different Teamsites and the frequently must duplicate content in order to allow multiple business groups to use it.

discovery

Assembling user flows and studying best pracitces for handing custom properties.

Matching the CRM capabilities to increase acquisition of users

Connections between properties and values

Exploring how custom properties are treated in other platforms like:

Airtable
Jotform
Lucidchart

Smartsheet
Asana rules
Typeform

user flows

Showing one of many different kinds of diagrams to refine the steps users may take when building custom properties.

design explorations
and phasing

Iterating on simple mockups allow for many ideas to surface. We can then explore as a team the options and test with users to help guide next steps.

Designs were structured in phases so engineering could  build while we started designs for next phase

Blocking out major sections to best understand initial layout and flows between screens.

frequent user testing

documentation and hand off

customer sentiment

Team, just got tour of a Custom Property setting customer review  and wanted to share a few of the comments from Lauren (Sales Asset Manger) and Katherine (SalesEnablement Associate):

This is the best conversation I’ve ever had!

This is exactly what we wanted the last couple years.

Yes please!!! when asked to be in pilot

This is absolutely phenomenal. This is what we need.

This is going to save lives.

This is amazing and I’m really excited in case you can’t tell.

Thank you Seismic for taking this enhancement seriously. The fact you are listening goes miles and we appreciate that.

Way to go team!!

takeaways

This project was just a single modal...albeit a VERY powerful modal :)

I initially had no idea how many sub-layers logic can go and I am very proud to provide users with a simple experience when adding logic to content.

Next case study

Pages website builder

Patch app

@2025 Joshua Weber