Pausing for Innovation
31 March, 2021

Director of Engineering at Quizlet
Problem
Though notoriously under-resourced, startups are widely considered a hotbed for new ideas. However, their fast pace often makes them lose sight of innovation. Delivering the product is not nearly enough; if your product is not innovative is not competitive.
As a company, we are in a continuous CI/CD pipeline where one delivery is followed by the next, which goes ad infinitum. In that kind of hectic environment, intentional pausing for a week can help instigate innovation and boost productivity.
Actions taken
I decided to introduce week-long, team-wide pausing during which engineers, designers, and PMs from one team would come together and brainstorm. For the first day or two, they should bounce their ideas off and compare them with what the competition would be doing. Then, on the day three and four, people should translate their ideas into concrete projects. This phase should resemble hackathons and would culminate with a demo presentation and a retro of the process on the day five. The whole process would be guided by what the team would need and want to solve, and they would be provided space to explore, try different approaches, and build what they would believe would be the best solution.
During the demo on the day five, a PM or a Product Analyst would assess if a proposed idea would be feasible and if it would have the innovation potential. They would also apply the RICE scoring model calculating reach, impact, confidence, and effort. Only after those results would be studied, the team would start planning a full-fledged project.
I find intentional pausing to be a critical component in this process. It allows your mind to escape day-to-day work and focus on things you are passionate about. If your team takes a collective break and distance themselves from mere delivering, they would be able to identify gaps and potential they went unnoticed in our fast-paced environment. Also, pausing helps us connect our daily work with a broader picture and helps us understand how our daily efforts contribute to it.
For example, one of my team was working on the problem of student onboarding. Though they were exceedingly productive, they were not getting the number of users they were hoping for. We decided to pause for a week, forget what we were doing and explore new ideas within that scope. First, we looked at what the competition was doing, which led us to conclude that we were failing to reach out to our students when they needed us the most -- before starting a semester or before an important exam. The brainstorming helped us crystalize how important it was to reach students at the right time, and we decided to try different push mechanisms that we never tried before.
Lessons learned
- Pausing helps people change their vantage point and see a bigger picture. It helps them identify opportunities missed in the fast-paced environment of our daily work.
- Pausing is not only about slowing down. As you slow down, distancing yourself from the daily work, you will be galvanized by new ideas pouring in and will soon experience an adrenaline rush that resembles the one in hackathons. - The time limit only adds to the positive pressure and excitement. When you are trying to build something in a time constraint environment, the process gets hackier than your regular development cycle.
- Since you do not release into production, you don’t have to follow all quality checks and configurations, and you can move exceptionally fast trying out different new ideas.
Discover Plato
Scale your coaching effort for your engineering and product teams
Develop yourself to become a stronger engineering / product leader
Related stories
26 May
Jonathan Belcher, Engineering Manager at Curative, explains how to balance team cohesion and individual focus time, tapping into his experiences of working remotely for seven years.

Jonathan Belcher
Engineering Manager - Patient Experience at Curative
16 May
Snehal Shaha, Lead Technical Program Manager at Momentive (fka SurveyMonkey), details her short-term technical strategy to unify processes among teams following an acquisition.

Snehal Shaha
Senior EPM/TPM at Apple Inc.
4 May
Kamal Qadri, Senior Manager at FICO, drives the importance of setting expectations when optimizing large-scale requirements.

Kamal Qadri
Head of Software Quality Assurance at FICO
14 April
Suryakant Mutnal, Engineering Manager at PayPal, discusses the importance of time management and the necessary structures in order to create internal consistency.

Suryakant Mutnal
Engineering manager at PayPal
6 April
Henning Muszynski, Head of Frontend at Doist, promotes his ideas on how documentation ensures consistency, efficiency, and standardization.

Henning Muszynski
Head of Frontend at Doist
You're a great engineer.
Become a great engineering leader.
Plato (platohq.com) is the world's biggest mentorship platform for engineering managers & product managers. We've curated a community of mentors who are the tech industry's best engineering & product leaders from companies like Facebook, Lyft, Slack, Airbnb, Gusto, and more.
