Renamed Project Capabilities to Project Categories. Recommended by two users because of terminology confusion.
Established consistent naming conventions with “Team” (as opposed to “organization” or “company”)
Removed the “Project” breadcrumb from the onboarding flow, since that became its own series of breadcrumbs itself.
Standardized UI patterns across screens: One user identified inconsistency between screens with and without input boxes. Maintain consistent visual design and component usage throughout the flow. Position instructional text close to relevant input fields.
Added "you can change this later" messaging: Another user emphasized wanting to know when he can revert changes or update client structures later. Added reassuring copy throughout that decisions aren't permanent.
Reframed source/target location of existing data as a user-friendly question like "Where is your client's data today?" and "Where are they moving to?
Adding expandable information for Connected Apps: including collapsible sections explaining what data transfers, how connections work, and limitations (e.g., no historical Slack data). These would be short explanations that assuage users’ concerns about unintended data accidentally being brought into Glossa. These explanations would explain in a few short sentences how each connected app works so that the user knows what to expect when they choose to connect it.
Reorganizing screens so that the user inputs client information before project-specific information. This allows users to create client records before projects to support real-world scenarios of clients with multiple projects over time.
Adding role definitions and permissions clarity - a short explanation of what permissions are available to a “member” vs. an “owner."
Several requests from the users were outside the scope of this UX project, and needed considerable input from the developers. We packaged up those requests seperately with our recommendations. Those included:
Creating and integrating a sample/demo project: Three out of four participants requested this. Offer it after initial setup completion but before users create their first real project. Include pre-populated requirements showing conflicts, duplicates, and different categories so users can explore hands-on without risk.
Making a short video tutorial (45-90 seconds) that tells you what the onboarding experience will entail. This could go at the very beginning of the experience to set the stage elegantly and succinctly.
Adding a Help Button in the event the user gets stuck, has additional questions about a specific screen, or wants to learn more in a different way. Glossa already has a business relationship with Intercom (using it in their Help Center) so it wouldn’t be a huge lift to incorporate it into other places on the app too.
In tandem with the “Sample/Demo project,” a tooltip walkthrough could be useful to showcase within an existing project. Since the Glossa experience is so nuanced and fundamentally “new,” the user may very well benefit from onscreen prompts that function as a guided tour through the app.
