We've just launched plato for individuals

🔥

login


Google Sign inLinkedIn Sign in

Don't have an account? 

Improving Product Release and Functionality

Feedback
Dev Processes
Product Team

4 February, 2019

Igor Naverniouk, tech lead at Google, identifies the most important feature of a product as its release point. From there, he details the importance of keeping the process organized and sensical.

Problem

A common error in releasing a product is doing so with an excess of added features that nobody is going to use and subsequently, wasting time.

Actions taken

  • Launch the first version of the product and start learning from it.
  • Get the absolute minimum necessary into the hands of users and start iterating.
  • Make changes with the feedback that you get from users. Do so in a way that it remains simple and modular. It should be organized in such a way where you can have pieces that can be removed and replaced separately.
  • Use shortcut decisions to help you make changes without disrupting the entire code process.

Lessons learned

  • It is better to give someone something that isn't good enough and have them tell you that directly, than to give them something that they do not need.
  • Most users understand really well, that when they get new software, it will be beta and that there will be a follow-up conversation with the developer.
  • If the code is heavily intertwined it becomes increasingly more difficult to make changes.
  • If you can make a shortcut decision in order to change the internals of code later, while keeping the API the same, you will be able to manage the technical debt aspect.
  • Most of the time you will find out that your short cut decision was actually fine and you can live with it for many years. Once in a while, however, you will see that your decision has become such a thing that you will have to make a choice to improve it, without redesigning the entire thing.

Related stories

Balancing Tech Debt and Feature Development
14 September

Mason Mclead, CTO at Software.com, delves into how to take care of tech debt while pushing out new features and products.

Managing Expectations
Dev Processes
Mason Mclead

Mason Mclead

CTO at Software.com

When Shared Ownership No Longer Works
28 August

Catherine Miller, VP of Engineering at Flatiron, recalls how she fixed the problem of shared ownership and recurring common problems by creating a new team that took over the ownership of the common systems.

Team reaction
Dev Processes
Ownership
Catherine Miller

Catherine Miller

VP of Engineering at Flatiron Health

Architecture Council: An Idea for Advancing Organizational Strategic Orientation
28 August

Brad Henrickson, CTO at Scoop, shares how by establishing the Architecture Council he advanced strategic thinking of the engineering team and overall strategic orientation of his organization.

Impact
Productivity
Feedback
Brad Henrickson

Brad Henrickson

CTO at Scoop

Hiring the Right Product Person for Your Team
18 August

Alessandro Pintaudi, Product Management Director at Payfit, dissects all the aspects of the hiring process that will enable you to hire a product person who will take your product to the next level.

Product Team
Hiring
Alessandro Pintaudi

Alessandro Pintaudi

Product Management Director at PayFit

Building a New Product Hub From Scratch
18 August

Alessandro Pintaudi, Product Management Director at Payfit, shares some of his tips for setting up a new product team from scratch at a location other than the headquarters.

Product Team
Alessandro Pintaudi

Alessandro Pintaudi

Product Management Director at PayFit

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.