Stacker
Small parts of a no-code builder that every customer ends up touching.
- Role
- Product executive, UX designer
- Years
- December 2018 to December 2019
- Scope
- Permissions, page layouts and onboarding
- Worked with
- Product and engineering
Website redesign
- Client
- Harbour & Vine Ltd
- Owner
- TMThandi Mokoena
- Due date
- 14 March 2019
- Budget
- £18,500
- Description
- New marketing site and client sign-in. Phase one covers the home page, pricing and the portal.
Tasks 3 linked records
The builder. A customer’s app in the middle, its pages on the left, and the layout of the open page on the right.
Overview
Stacker is a no-code platform that turns the data a business already has into a custom web app. I worked across product and design on a handful of features. Each was small in scope, and each sat on a path every customer walks.
The problem
Customers arrived with a spreadsheet and a clear idea, usually a portal for clients or a tool for the team. Most got a first version working quickly and then stalled in the same three places: deciding who could see what, arranging a page, and knowing what to do first.
What I did
I defined and designed improvements to those three places from inside the product team. It was a year of small, well-aimed changes rather than one large launch, and I have tried to describe it at that size.
- +34%more new apps reached a first published version
- −41%fewer support conversations about permissions
- 6 minmedian time from connecting data to a working first page, down from 19
Sample figures for illustration, not reported company data.
How I worked
My title had “product” in it before it had “design”, and the work reflected that. Deciding which small thing to fix was at least half the job.
- Read the support inbox. A month of conversations, each tagged by where the customer was stuck when they wrote in.
- Watch people build. I sat in on new customers making their first app over a shared screen, and said nothing unless asked.
- Fix the smallest thing that removes the stall. Every change had to fit inside one release, which kept the designs honest.
- Measure the stall, not the feature. Success was fewer people stuck at that step, whether or not they noticed what had changed.
What the research said
- Permissions were set in one place and felt in another.People changed a rule and had no way to see what a client would now see, short of logging in as one.
- A layout is an opinion about what matters.Customers knew which three fields mattered most. The editor made them say so in rows and columns.
- The first ten minutes decide everything.People who saw their own data in the shape of an app early kept going. People who met settings first often did not.
See it as they will
The fix for permissions was mostly a matter of distance. I put the consequence of a rule next to the rule, so nobody had to hold the two in their head or sign in as a test client to check.
What each role can do with Projects
What they will see
- Website redesignHarbour & Vine Ltd, £18,500In progress
- Brand refreshMeridian Components, £9,200Done
- Portal sign-inHarbour & Vine Ltd, £6,400Not started
- Annual reportLisboa Freight, £12,000In progress
Internal note on Website redesign: client asked to hold phase two until April.
A client sees 2 of 4 projects.
Permissions with a live preview. Flip a few rules, then switch between Admin, Team and Client to see what each one gets.
- Rules are phrased as things a person can do, in the order people ask about them: what can they see, then what can they change.
- The preview sits beside the rules and switches role in one click, so a change and its consequence are on screen together.
- The last line says in words what this role ends up with. It is the sentence customers used to send to support to check they had it right.
Arrange a page by moving what is on it
The old layout settings asked for column counts and positions. Customers did not think in grids. They thought “budget should be near the top”, so the editor became a list you put in order.
Fields on this page
Drag a row by its handle, or use the arrows. The eye hides a field without deleting it.
- Client
- Owner
- Due date
- Budget
- Stage
- Description
- Internal notes
Website redesign
6 fields shown- Client
- Harbour & Vine Ltd
- Owner
- TMThandi Mokoena
- Due date
- 14 March 2019
- Budget
- £18,500
- Stage
- In progress
- Description
- New marketing site and client sign-in. Phase one covers the home page, pricing and the portal.
- Internal notes
- Client asked to hold phase two until April.
Layout editor. Drag Budget to the top, hide a field, or bring Internal notes back.
- Fields are rows you drag by a handle. The arrows do the same job from the keyboard, one step at a time.
- A hidden field stays in the list, struck through, so hiding never feels like deleting.
- The page on the right is the real layout and rearranges as you go. There is no separate preview to open.
Your spreadsheet, as an app, in the first minute
New customers used to connect their data and land on settings. I moved the proof to the front. The first thing they now saw was their own rows rearranged as an app, with nothing to configure yet.
The same four rows
What a customer arrives with: rows in a spreadsheet.
First run. Switch between Spreadsheet and App. Every value travels to its new place, which is the whole pitch of the product in one movement.
What it taught me
Scope and impact are different measurements. None of these changes would have made a launch announcement, and each one moved a number that mattered.
- Start from where people stall. The support inbox is the most honest research a product has.
- Put the consequence next to the control. Most confusion I found was distance between the two.
- Show people their own data early. It does more than any tour or empty state.