Back to resources

Why You Should Take Technology Risks in Product Development

Innovation / Experiment
Product
Scaling Team
Dev Processes

25 April, 2022

Matias Pizarro
Matias Pizarro

CTO and VP of Residents at ComunidadFeliz

Matias Pizarro, CTO and VP of Residents at ComunidadFeliz, recalls a time in his early career when he took a technology risk that had wide-ranging benefits to his product's user experience.

Getting Over the Fear of Change

Four or five years ago, our app user base started to rapidly grow. ComunidadFeliz is a software for building management. One of its features is gathering building-related payments, which administrators can export into PDFs each month. In the beginning, we generated these PDFs using AWS workers, but as we grew, we had hundreds of residences in our system. Suddenly, our admins had a wait time of one or two hours.

We had to think of alternative methods to fix this problem, yet we were scared to change our ways. We scaled horizontally by adding new machines but soon discovered that this wasn't sustainable. We knew that we had to innovate the way we worked.

Adapting to Change

At the time, serverless computing was newly trending. There was palpable skepticism around this new technology, both inside and outside of our organization. Additionally, no one in our team had any experience with it. However, we knew that more horizontal scaling wasn't an option, the costs were rapidly increasing, and our stakeholders were worried.

After analyzing our options, we decided to try serverless computing in order to solve our scaling and financial problems. Of course, it was a big bet on something we had zero knowledge of, but our engineers were thrilled to try new technology and got involved from day one. An essential part of all this new adoption was communication. The whole team needed to clearly understand what problems we were facing, why we were committing to this change, and how this could be the solution.

Introducing new technologies in product development always comes with risks, but the absence of innovation poses a bigger threat.

Since switching to serverless, our app can generate thousands of PDFs at a time. At first, our users thought we had undergone a massive infrastructure change when in fact, all we did was change our computing system. In terms of coding, it wasn't that hard. Yet it had a very high impact on the user; our customer satisfaction went through the roof.

Keep Up With Evolving Technology Trends

  • Don't just reiterate the skills and knowledge you gained in college. Follow industry trends and be curious about new technologies.
  • Try new things even if they're not widely implemented yet. A lack of wide application doesn't mean that something isn't great. It may be the perfect solution for your product. You have to learn what's out there and take risks.

Discover Plato

Scale your coaching effort for your engineering and product teams
Develop yourself to become a stronger engineering / product leader


Related stories

DevSecOps: Why, Benefits and Culture Shift

29 November

Why DevSecOps matter and what's really in it for you, the team and the organisation?

Innovation / Experiment
Building A Team
Leadership
Ownership
Stakeholders
Cross-Functional Collaboration
Vikash Chhaganlal

Vikash Chhaganlal

Head of Engineering at Xero

Mindsets of High Performance team

14 October

Teams have tremendous impact on the products on they build. T.E.A.M definition - Together Everybody Achieves More is true. A collaborative and empowered team builds great product versus the good ones.

Innovation / Experiment
Mission / Vision / Charter
Building A Team
Productivity
Feedback
Motivation
Praveen Cheruvu

Praveen Cheruvu

Senior Software Engineering Manager at Anaplan

How I failed at my startup

14 October

There are nine specific building blocks and functional areas every org/company need to work to launch the product and provide services to customers. How effectively founders tackle them determine the destiny of the company.

Mission / Vision / Charter
Scaling Team
Building A Team
Impact
Strategy
Prioritization
Praveen Cheruvu

Praveen Cheruvu

Senior Software Engineering Manager at Anaplan

Scaling a Team in Two Parts: The Product and Manager

2 August

Viswa Mani Kiran Peddinti, Sr Engineering Manager at Instacart, walks through his experience scaling a team, product and his skills as a leader.

Managing Expectations
Product
Scaling Team
Leadership
Meetings
Viswa Mani Kiran Peddinti

Viswa Mani Kiran Peddinti

Sr Engineering Manager at Instacart

(Re)Organizing Your Teams Using Domain-Driven Design

12 July

A proposal for how to create an org structure that will deliver software systems that you want, not ones you get stuck with.

Alignment
Architecture
Scaling Team
Building A Team
Internal Communication
Reorganization
Ram Singh

Ram Singh

Principal / Founder at id8 inc