After Oath aquired Tumblr (via Yahoo) in June 2017, the general prioritization of product design work shifted to accomodate for the various backend systems that needed to be integrated between Oath and Yahoo/Tumblr. These systems included the inclusion of GDPR onboarding processes for all users, the addition of more pervasive advertising throughout the site, and the integration of “reporting and security” pipelines that all of Oath’s subsidary organizations used.
The prioritization of Oath’s comprehensive “integration” work, in a nutshell, was basically net-harmful to the existing experience Tumblr users had come to expect. By early 2018, a cohort of developers and the creative team internally lobbied to begin work on "New Tumblr" initiatives that would reboot the overall experience and align the product itself with the new branding work that had already been completed by Doug Richard's team in late 2017.Source: Douglas Richards
Long story short, through persuasive arguments on our part, the “New Tumblr” cohort had been able to secure organizational backing and time set aside for visioning work while Oath’s infrastructural work was completed with existing design components.
Throughout the last year or so of my involvement at Tumblr, the product design team had the opportunity to take several threads of work in our generally-defined “Community” space and unite them into a totalizing vision of how a redefined Tumblr might look and feel.
Our focus areas for new work involved most of the post creation interfaces, the main feed, new conceptions of “groups”, and new user onboarding.
While the product design team at the time — Matt Clifton, Neil Voss (Our design director), and myself — collaborated on most aspects of Tumblr 2 in an interwoven manner, we each focused on particular aspects of Tumblr's experience we had more radical ideas about.
In my work for Tumblr 2, I focused on the following functionalities:
- Overall Information Architecture
- Informed from my previous experience of weaving cross-platform security features across Tumblr, I had several specific ideas for how to decrease Tumblr's user-perceived surface area. The design work I produced for a renewed "Tumblr 2" information architecture was for the most part written and abstracted in the form of models/maps, but some interface design work I produced reflected these models well.
- Post Creation Interfaces
- For Tumblr 2 post creation, I was inspired deeply by a sentiment expressed by Doug often that he wanted to one day create all of Tumblr's branded content with Tumblr tools natively. As Tumblr stands, it uses a dated and partitioned mechanism of post creation affectionately named the "post flower". In my "New Post Form" works, I wanted to create a single interface for the collaging of various content types, such that Doug and his team could one day design Tumblr with Tumblr.
- In-feed communications (New replies):
- New user onboarding was one of the last major product areas I was given to design outright. Prior to my involvement, it was a project which had been in ongoing development for two years. Integrating GDPR-required interfaces and prototyping "Tumblr 2" style interfacing was one of the last projects I took on before I left Tumblr.