UI Prototyping Tool
I designed a drag-and-drop Miro workshop tool that helped Salesforce teams build Service Cloud screen ideas with customers instead of only presenting a demo.
The value was not just the Miro board. It was giving solution engineers a practical way to involve customers earlier.
A Miro board customers and solution engineers could build with
This public-safe reconstruction shows the workshop logic: a focused component library, two priority screen canvases, facilitator notes, and a feedback area. I designed the flow so facilitators could turn customer discussion into screen ideas in real time.
Three things that made this hard
No one knew what the new workshop tool should include, when it should be used, or what a successful session should look like.
Solution engineers already had a way to prototype, so the tool had to save time and help customer conversations.
Service Cloud had too many features to include, so I had to choose the parts customers could meaningfully discuss in a short workshop.
Three phases, two prototypes, one live client session
I interviewed five solution engineers and learned that some customers stayed unconvinced after demos because their specific needs could not be shaped live. We scoped the idea into a two-hour Miro workshop around key Service Cloud pages.
I built the first prototype and tested the component library and co-creation flow with six solution engineers. The walkthrough exposed missing components, wrong placements, and the need for clearer guidance.
A dry run showed that building three pages in two hours was too much, so I helped narrow the workshop to the most important pages. In a client hackathon, facilitators translated discussion into components, which worked better than asking customers to choose every component themselves.
Published internally at Salesforce and used in live customer-facing sessions.
What this project taught me
Involve users from the start, not at the end.
The main risk was adoption. Involving solution engineers early helped them understand the value and made the tool easier to introduce.
Rapid prototypes communicate what words can't.
No one could picture the workshop from a description. The prototype gave people something concrete to react to, test, and improve.
User feedback still needs design judgment.
Some feedback would have pushed the workshop back toward a normal demo. I had to protect the core idea: customers should co-create, not just watch.