Scorebot, a unique, free SlackApp that makes everyday Slack conversations a company-wide competition, had a problem. They had a team dedicated to V3.0, but they still weren’t totally sure what direction they wanted their app to go. Was Scorebot an HR solution to evaluate team morale? Was it a fun culture-add that made the workplace more fun? Was it something the team hadn’t yet considered? And, above all… would people pay to use it?
Enter the Design Sprint.
The team decided the following as their Long Term Goal and Sprint Question to answer during the Design Sprint:
Long Term Goal: In 2 Years Time, we want Scorebot to be making $100K revenue/yr with a
Sprint Question: Can we find the right set of features that people will actually pay for?
Matching objectives to process
During initial conversations, it became clear that Kudelski had a clear set of challenges they needed to tackle. These included:
Showcasing the technical abilities and business value of the platform
Providing clarity and momentum to key internal stakeholders
Casting vision for developers who are actively building the solution
With these objectives in mind, the Crema team identified the quickest path to realizing these goals: a Design Sprint. We took several key activities of traditional Design Sprints, paired with some of our more typical deliverables in our Prototyping & Testing engagements, and created an engagement that would deliver the Kudelski group with the assets they needed in an expedited timeline.
Objectives & goals of the work
Product branding, prototyping, validating
When our two teams began working together in late 2016, the original focus was to further refine the Solarhood product concept and design unique product branding that is still being used to this day. By creating a high-fidelity mobile prototype and testing it with real users to glean feedback on the application, we were able to measure a response on the product in two solar markets – Kansas City and Portland.
The outcomes of this 5-week phase were:
A defined business model and unique value proposition
Initial brand direction, including brand logo, iconography and brand guidelines
A high-fidelity, clickable prototype that was tested with real users in two solar markets to ensure the mobile experience is intuitive, efficient, and enjoyable to use
A high level product roadmap and budget for initial release of the application, leveraging a dedicated product team at Crema
Recordings of all user testing sessions and access to all assets created
At the end of this, the Solarhood team decided to shift their resources and allocate some of the development to an offshore team. We remained in touch & kicked off conversations for phase two almost 18 months later.
“I was very skeptical of the whole thing… but the process spoke for itself, and I absolutely loved it. This would have easily been 6 months of meetings."
By the end of Monday morning, the team decided to limit the scope of the solution to the web-app portion of Scorebot, how users get there, and what happens when they do (Map & Set the Target).
On Tuesday morning, the team entered to see each of their solutions on the wall (Art Gallery). The ideas were amazing. From a whole new Scorebot universe to a Slack-only option, the team had created solutions that were unthinkable when the Design Sprint started. The team voted on which one to move forward with, and on Wednesday, our Designer got to work.
On Wednesday, our Designer got to work.
On Thursday, we held 4 user tests (one couldn’t show…). The users were a unique mix of HR professionals, university staff members, co-founders of software companies, and designers. Each one brought a new perspective to the table, and each had their own “aha!” moment. The university employee said that her team (who already used Scorebot) would love this update, because it would help them have more fun together. The HR professional said that being able to observe employee engagement and interactions without making people fill out a questionnaire would be a valuable tool. The co-founder said that Scorebot would help save his internal communication team several hours a week following up with teammates about whether they had or hadn’t read an internal memo.
The User Testing Observation Room was a joyous one, and the Scorebot Team was laughing and celebrating when each person said “we like these new features!” and “yeah, we would pay for this.”
Debriefing on Thursday afternoon, the Scorebot team was quick to say that “the process just works.” The team had pivoted their understanding of what people wanted, and the users unanimously responded, “we want it.”
Scorebot is currently developing V3.0, and is looking forward to providing more features soon.
The greatest aspect of this design challenge was knowing that we had to design for situations nobody on the team could predict; that is, we had to be sure the design worked equally well in a wide variety of situations as the product grew and changed without us.
Brand wasn’t a high priority, but since this was a new product that would benefit from strong competitive differentiation, we set out to provide some core identity work that would enable the product to stand out in a sea of similarity and differentiate the entire product experience.
Cybersecurity work is often surrounded by darkness, fear, and unfortunate stereotypes. To stand out from that pack, this new mark & lockup combo, with its stylized shield & checkmark, points toward a brighter world of security & confidence. The monospace typeface Fira Mono recalls a developer’s terminal without being “too techy.”
“I walked in assuming I knew what was best. Then a switch in my brain flipped halfway through the Sprint. The users loved the new direction, and we haven’t looked back.”
CEO of Scorebot
After just a couple weeks into the engagement, the team was ready to put the work in front of some real users. These sessions began with an inquiry into the analysts’ workflow, and moved quickly into exposure to the lightweight prototype hosted in InVision.
These interviews quickly provided data that fueled a few defining insights:
A new paradigm for threat-hunting & event evaluation. This paradigm quickly became a centerpiece of the experience architecture and several components in the design system.
Consistent terminology was more difficult to develop than expected. As we were pulling from many different tools — some of which use the same word for different things — we had to give more consideration to words & phrases we had taken for granted.
Some significant distinctions that emerged in research & discovery didn’t play out in design the way we had expected. Fortunately, this enabled us to simplify the experience significantly.
After taking time to refine the work against this feedback, we were able to provide a more highly-detailed prototype with additional workflows.
Given the tight time frame of the project (and hectic summer schedules), keeping our feedback loops short was essential. Clients were brought into a dedicated Slack channel, and given full visibility into the team’s Asana board. For daily standup, we used a Slackbot called Status Hero and designs were posted and discussed through InVision prototypes & boards.
Clients were engaged and excited throughout the process, leading to some new ways to think about the work they had been planning. Even before the end of our engagement, they quickly began implementing the design system in React components.
In March 2019, CYDERES announced a partnership with Chronicle, an Alphabet business. This partnership meant that while Crema’s work was helpful to the CYDERES team, the client’s broader strategy led them in a different direction.
Let's talk about your business and technology goals.