I designed a slash command menu for PureBlazor to improve workflow efficiency. Through extensive usability testing and feedback, the menu was optimized to reduce navigation time and streamline key tasks, significantly enhancing the user experience for developers.
PureBlazor, a .NET, AI-native CMS for developers who want to use C# as their single programming language to build anything.
1 Lead Designer
1 Product Manager
1 Software Engineer
Figma
Qualtrics
Connect CloudResearch
Prolific
Slash command menus (SCMs) have become essential tools for enhancing productivity and reducing workflow friction in modern platforms like Slack and Notion. These menus allow users to quickly execute commands and navigate tasks without leaving their workspace, cutting down on time spent switching between tools. Studies have shown that features like real-time messaging, workflow automation, and streamlined command interfaces can increase team efficiency by up to 30%, improving decision-making and reducing manual tasks.
In developing the slash command menu for PureBlazor, I aimed to bring similar productivity benefits to developers. By creating an intuitive, accessible menu, we significantly reduced navigation time and improved overall workflow efficiency, aligning with the goal of enhancing user experience. This case study details the process of designing, testing, and refining the menu to meet user needs while streamlining key tasks.
To begin my design for the slash command menu in PureBlazor, I conducted a competitive audit of existing platforms such as Slack, Notion, and Discord, which have well-established slash command systems. This audit helped me identify key features and best practices for an efficient and user-friendly command interface.
I structured my research around several key “How Might We” (HMW) questions to guide the design process:
This research process helped me answer key design questions and lay the groundwork for an intuitive, efficient slash command menu tailored to developer needs.
With the competitive audit insights in hand, I transitioned to creating the initial wireframe to imagine the workflow and developed the first iteration of the prototype.
The prototype was presented to the team for feedback, focusing on ease of use, functionality, and the clarity of the command categories. Some feedback / considerations with the design:
Based on the discussion with my team, I created prototype iteration #2 to explore how grid view might look:
To gather insights about the remaining unanswered questions we had, I conducted a survey with 85 responses but 34 participants disqualified, leaving 51 responses.
Summarized findings:
Based on the survey results, I created various possibilities/versions of what the SCM might look like and conducted a follow-up survey with users:
Based on the survey results:
My team agreed with the results of the polling and we settled on Choice 1.
I’m incredibly happy and grateful to have been a part of this project. It’s been such a rewarding experience to see the growth and evolution of the SCM, from initial brainstorming sessions to the final implementation. Working on this project has not only allowed me to refine my design skills but also to collaborate with an amazing team that values feedback and continuous improvement.
I especially want to thank Cody and Nick, the cofounders of PureBlazor, for their constant support, insightful feedback, and genuine receptiveness throughout the entire process. Their openness to new ideas and their commitment to creating a user-friendly and innovative product have made this journey a truly collaborative one. Their leadership and vision have inspired me to push the boundaries of what we could achieve with this project, and I’m excited to see where PureBlazor goes from here.
This project not only sharpened my skills but gave me a chance to laugh, learn, and occasionally yell at my screen.