Gainsight
Build survey creation into the platform — so users stop leaving for an outside vendor.
A broad interview prompt — add survey creation to the customer-success platform — that I turned into a scoped, constraint-aware concept. The interesting work wasn’t the survey UI; it was interrogating my own assumption and designing only what the underlying platform could really build.
I caught the untested bet inside my own hypothesis.
The easy version of this exercise is to assume you know what users want and start drawing. Instead I named the assumption baked into my hypothesis — that people wanted to build surveys in-platform at all — and grounded the concept by talking to real users before designing, so the feature answered a real need rather than a guessed one.
Reading Salesforce developer docs — as a designer.
The platform sat on Salesforce, so the constraint was concrete: design only what the platform could actually build. I read the developer documentation as a designer would read a style guide — to learn the real edges — so the concept was buildable, not a fantasy that would collapse on handoff.
The whole survey lifecycle, not just a builder.
I scoped the concept to the full arc a survey actually travels, because a create screen alone isn’t a feature — it’s a demo.
Create
Start a survey from scratch or a pattern.
Design & preview
Build the questions and see them as a respondent would.
Distribute & publish
Get it out to the right audience.
Drafts
The in-between state real work actually lives in.
Close
Ending a survey cleanly, not just abandoning it.
From sketch to wireframe — the survey homepage
My hand sketches on the wireframe-sketch sheet, and the clean coded wireframes built from them — the Salesforce-hosted survey homepage, with tab-contextual row actions.
The strongest concept is one you already know can be built.
The output was a scoped, constraint-aware survey-engine concept covering the full lifecycle — grounded in real user input and in the platform’s genuine capabilities. Reading the developer docs as a designer is a habit I’ve kept: it’s the fastest way to make sure a design can actually ship.
Honest framing: this was an interview design exercise, so there’s no launch or metric — the intended success measure (feature adoption) was hypothetical.