When to Build New Features
19 August, 2021
I ran a team that was delivering top-notch features pretty fast. The problem arose when we realized that our customers were not using those features. Naturally, it led to team frustration; they worked on a feature for about 2 - 3 months; that is great, but not everyone uses it. The worst part? We don't even know why. I focused on these aspects to transfer my team from a delivery team to a product team. It was essential to make features that were not only used by our customers but also solved their problems.
To break down more about the team frustration, some of the team members were tech-oriented and wanted to deliver high-quality technical features that were scalable. It is unfavourable to work on something and then move on to something else, and a year later, coming back to work on the first thing. In the meantime, some leave the team because they don't feel recognized, whereas it has nothing to do with what they ship.
My first take on this situation was building a flawless relationship with the PM and UX designer. I must admit that my business knowledge was not perfect, for which I could not convince my PM as to why I think a specific feature was necessary and why it was not significant. I wanted to improve the business through the edge and slowly explain the problems we tried to solve to my team members. Hence, I had grown a strong relationship with the PM.
I conducted weekly meetings to discuss the technical aspects we were working on. Also, I prepared discussions on what we were going to work on next; even if it meant solving a problem 一 not a technical issue or a feature 一 we would find a structured approach to work towards it.
After everything, we defined a vision. It would help us figure out what was the problem, and where we wanted to go with the problem. Once we had all of those, we would present that in front of the team to find a solution. We needed to work with hypotheses and not on strong beliefs.
When we released a feature, we wanted to know the number of people using those features, why they were using them, etc. This would be our way to measure everything. Besides, it would provide us with some qualitative and quantitative feedback, further helping us to know if we should spend more time on the feature. If the answer was yes, we had to figure out the following steps, and if no, we should not waste our time on it anymore.
Measuring everything from the technical and product perspective would reduce complications for the future. Google Analytics and some other external tools were of great help when it came to this. We could finally figure out that 10 people clicked or viewed our feature. Something more specific that we implemented on our website was a data pipeline, which collected information and stored it in a database that we used as a tool to visualize it.
On top of that, we wanted to keep things agile and work by iteration. If one of the priorities changed, we could switch easily by releasing a small iteration and have less frustration among team members. The agile process was essential to keep the processes straightforward; test, learn and fail fast.
Last but not least, I stopped building a roadmap for the longer term. Previously, I used to create a well-defined roadmap for 2 quarters, but I didn't do it anymore as soon as I learned my lesson. I realized that it was not feasible to create a roadmap for such a long term in our industry because something changes every day. We had a vision roadmap for a quarter, but I did not put too much detail into it. I would only have a general outline, and later the team would decide which subjects were necessary and how to define them.
- Make sure that the team understands the goals. That would help them perceive their responsibilities and know what others (or the rest of the group) are working on alongside them. No one should feel burdened by a team's objectives.
- In a fast-paced company environment, create a shorter yet strategic roadmap. It should include the major milestones and steps needed to reach a goal, but nothing too comprehensive. It should work as a document to help articulate strategic thinking.
Scale your coaching effort for your engineering and product teams
Develop yourself to become a stronger engineering / product leader
Vineet Puranik, Senior Engineering Manager at DocuSign, discusses the impact of roadmaps, organization, and proper management for your teams to procure growth.
Senior Engineering Manager at DocuSign
Otavio Santana, Distinguished Software Engineer at Zup Innovation, shares his best practices for upskilling without stretching yourself too thin.
Java champion, software engineer, architect, and open-source Contributor at Independent Technical Advisor
Saikrishna Desaraju, Engineering Manager at Marks & Spencer, draws from his personal experience to advise new managers on thriving in their roles.
Engineering Manager at Marks and Spencer
Pavel Safarik, Head of Product at ROI Hunter, discusses the frequently overlooked role of product marketing in getting high user adoption rates for your product.
Head of Product at ROI Hunter
Muhammad Hamada, Engineering Manager at HelloFresh, addresses the uncertainties brought on by the pandemic, how these have affected our work environments, and how we can adapt.
Engineering Manager at HelloFresh