My role:
Worked with:
Overview:
When I joined the Twitter Developer Platform team in October of 2021, I realized we had a lot of opportunity to expand on the functionality for the Portal. We had a new strategy to open the platform to more developers, whereas the old version of the site had been purposefully closed off to all but our enterprise data licensing customers. I sold the idea to leadership that we should run a design sprint to create a vision for the new site. Once I had buy-off, I organized and moderated the sprint. Then myself, and my design partners created a vision in collaboration with partners. After the design was complete, we ran the designs through concept testing, and the team is now executing to design and build several of the most requested features, with more work prioritized in the coming quarters.
Prototypes:
GIF of the onboarding experience in development (Q4 2022)
Process:
I pitched the idea to the leads on the project that I could run a design sprint to generate some new ideas for the Portal. Once I had buy-off, I coordinated with my teammates to do a 1-week design sprint. I hosted the sprint, inviting partners from Product, Engineering, Research, and more to participate in the process. At the end of the 1-week sprint, my 2 product design teammates and myself had a great vision for what the product could be. We spent another week polishing our designs, and then took them on a tour with the Developer Platform leadership team. The senior directors were all really excited by the vision and got behind the idea of concept testing.
We worked with our research manager to get AnswerLab involved to moderate the concept testing with 8 new users to the Twitter API and Developer Portal. I also worked with the Program manager for our Insiders program to simultaneously recruit 5 Insiders (or power users), and I moderated those 5 sessions myself. At the end of each concept test, we had participants participate in a “Buy a feature” exercise to help us prioritize the list of features we had generated. We got clear insights from customers on their top priorities, and myself and the other designers on my team worked together with product to get the highest priority items on the backlog for the following quarter.
I began designing the most-voted for feature in Q3 of 2022, and the engineering team is currently building out the designs for a Q4 2022 launch.
Outcome:
I’ll have more outcomes data in the coming months when the designs go live and we get the results back from our A/B test. When the features go live, we will be sending 50% of traffic to our control and 50% to our new treatment as seen below. We seek to increase the number of API calls developers make in their first 10-days to more than 19 API calls, as our data science team has found that when a dev makes more than 19 calls in the first 10-days, they’re more likely to be retained at 60 days. Thus far, we’ve conducted usability testing (in addition to the original concept testing we did after the visioning sprint. Devs have had a positive reaction to the samples, with 8 out of 8 participants choosing to utilize the Sample Apps, rather than skipping them in favor of following a self-directed path.
