Skyler Tse

Hi I’m Skye! A product designer that transforms 
research-driven designs into unforgettable journeys.


 Chat with me


back



Solutions Workspace
Community Profile


A unified, single destination for ‘Solutions’ to manage their business, while leveraging insights to provide a perspective next-best action and value-based approach to selling.



6 months of design, 2 user testing rounds, 14 interviews, 26 pgs of annotations, 900+ minutes of analyses.
Salesforce Specialized Tech & Programs (STP)
New York City ID# 0924-0225
Web Product 6 months 
Project Lead & Designer
Figma
Profile
Contents Hub
User Testing




Here, let me catch you up!Solutions Workspace, with over 24k users, had a flagship community forum that had lost its luster over time. Tasked with leading the redesign as one of two designers, my first strategic move was to reimagine the user profile—transforming it from a static card into a dynamic content hub. This foundational work was crucial for driving user engagement and setting the stage for a full community renaissance. 



Prologue: Understanding & organizationTo establish a clear foundation for the wireframes and subsequent high-fidelity designs, I lobbied for three key artifacts to start the project off:



①  A designated hub for all documents, Figma files, presentations, links, etc. into where all teams creative have access to.

② A hierarchical structure for the features within a Figma design file, with the pages sections by atoms, molecules, organisms, patterns, pages, and prototypes. 

So as the product team works through future sprints, many components would already have a lovely home to live in.



③ A component / content flow chart with a new structure, that designated all the feature priorities on our backlog awaiting for design critiques, development feasibility confirmations, reviewing feedback / suggestions, and revisions.

This step took up around 1/4 of our timeline, but was a necessary push to ensure that obstacles are cleared up before engaging in quick weekly design sprints. 




Ex. How good labelling and documentation leads more efficent teamwork
Quick sitemap of Profile and Contents Tab



As a result, the project interactions in Figma, were blowing up quite a bit. And I’m glad that it did. Because every emoji, @, and annotation, proves that the team are always on the same page, and in support of not just the product, but of each others ideas and opinions. Designer annotation is also an excellent method for tracking each step of the process for our prouduct partners, as timelines can unexpectedly change.

 And I wouldn’t have it any other way, so PING ME, let me get all the Slack notifications. 


Amazing collaboration

Worked FeaturesI worked on 6 key profile features, and in this project snippet I’ll provide some insights into the 3 highlighted features:
① Display of Profile
② Display of Contents Table
③ Collaboration, Permissions, Version History
④ Content Archiving, Restoration, & Deletion
⑤ Collections
⑥ Drafts & Publication Statuses

*Disclaimer: Details are blurred out for protection purposes.
③ Collaboration / Permissions, and Version History
In the Collaboration and Permissions experience, users co-authoring posts had no clear visibility into collaborator management or draft ownership. This led to confusion, duplication of work, inconsistent team groupings, and ultimately, abandoned drafts.

To tackle this pain point, was to design the “best of” layout, that enables users to seamlessly manage collaborators, maintain clear ownership, and receive immediate feedback on their actions. Working within an established design system, the focus is narrowed to assembling the right components and interaction patterns to create a cohesive, intuitive flow that felt both efficient and familiar to users. Of course along the way, with any components or features that do not exist, the subtask is to streamline them through a smaller DIRT (design, iterate, review test) workflow. 

Because most times, an essental smaller component, is a cruicial piece of the larger design ecosystem. My job is to build, update, and uphold those components (atoms, molecules, organisms, or patterns) according to the core design system, so that it doesn’t become an obstacle for future project members. 
In addition to a default state and selected state for new components, I also have to consider how it visually performs when someone interacts with it. And what kind of validation needs to be shown when there is an error, warning, or success. 



Ever-changing pattern
For the Version History experience, the process was similar — with the added task of designing appropriate toasts for validation messages, and defining how post-publication labels should appear. Within the larger Solutions Workspace design ecosystem, many components can function as “labels.” One of the challenges lay in identifying the right one without overlapping with existing definitions. 

And the pattern is constantly evolving — it’s about the thoughtful planning, refining details, and ensuring it continues to adapt to new feature requests and shifts in the broader tech landscape. But just because a feature will evolve in the future doesn’t mean it can’t be smoothly integrated now. That’s where careful alignment with the design system come in, it’s for ensuring flexibility without sacrificing consistency.

Users who frequently create and modify posts need a clear way to revert to earlier drafts or review how a post has evolved over time. In the current state of SW Communities, there was no true method to access version history or see detailed modification records. 

To address this, a version history list was used to surfaces key metadata for each save point — including publication status, version number, creator, and timestamp. I also included an accessible sub-menu for each version, allowing users to delete, copy a direct link, or restore that version as the current live draft.

With this, it gave users control over their content's lifecycle, reducing the fear of accidental edits and empowering them to experiment and iterate freely.

④ Content Archiving, Restoration, & Deletion


⑥ Drafts & Publication Statuses
User Interviews, Analysis, 
Data Visualization, and Validation


With Profiles looking to launch at the end quarter, it was ultimately decided at a handful of carefully selected members within our targeted audience, would move forward with 1-1.5 hour moderated user interviews. 

A script was written out, extra materials prepped (along with if there were any technical bugs that may appear during testing), and a dry run was completed in organizing each team members roles. 

There were 2-3 roles established: an interviewer (to help guide the user into certain tasks visually and verbally), a notetaker (in charge of recording, sending links), and an observer. 


A total of 2 rounds, 14 interviews, 26 pages of annotations were performed.


and man let me tell you, sifting over 900 minutes of footage for analyses on: 

 card sorting, 
quote catching, and 
ranking

is one heck of a task!


*Details are blurred out for protection purposes.


TakeawaysAlthough I hit the ground running, catching this project, I found it both rewarding and theraputic. I’ve been wanting to dive back into the intense testing environment, and the second Solution Workspace’s Community was looking for a designer to spice things up in their profile section, SAY NO MORE. I was onboard before the news even made it out to the boarder team. 

Working with a veteran ux researcher—it opened up my eyes on deeper ways to test products, and mini interactions—and it made this journey all the more meaningful. It also helped me solidify what broad or narrow user testing truly means to the overall design.


Postitive Sentiments on Profiles“More user-friendly than what I’ve been dealing with for SW [launch 1]...and you bring in some of the stuff I was familiar with for Solution Central.”
- Diana, Senior Visual Designer

“It’s very similiar to what I would do in Solution Central...it covers what I need.”
- Vanessa, Senior Demo Architect, FINS

“Discoverability, quick and easy, like on my profile, my content [and] features are there...how easily I can leverage that feature.”
- Vamsidhar, Lead Product Manager, Data Cloud

“Really easy to manage and...not take much time to make sure your stuff is up to date.“
-  Tom, RFP Manager

End of Project Preview
Oh dang, you’ve hit the end of the story! 

But don’t worry, this is the tldr version since some of the contents are restricted—there is much more in the longer version just waiting to be heard, so don’t be shy to connect!




product design & sys             product design & sys            

archives        archives    

big scoop        big scoop