I believe that the more people (especially those in leadership positions) who understand how to build human-centric products, the brighter our future looks.
I hope this article inspires tech leaders with a new perspective on how they can accelerate their development cycles and build lucrative products with design.
This quote means that saving — whether it’s money, resources, time, or anything valuable — should be the number one priority without considering the sacrifices to be made–even if those sacrifices are extremely significant.
In the context of product development, this mentality is often carried down by senior leaders to their teams and is about time.
Two of the most common questions that product leaders get asked by their bosses, investors, and founding partners today are:
- “How fast can you build it?”, which is immediately followed by…
- “Can it be done faster?”
The answer to the second question is always yes–anything can be built faster, but we rarely ask ourselves at what cost.
If a product gets deployed quicker, what risks are associated with the corners that got cut to make it happen?
With pressure put on developers to speed up their cycles, shortcuts and temporary solutions need to be made.
When projects are viewed on a roadmap or spreadsheet, faster development time reduces spend and puts profits in the bank sooner (since fewer resources are needed and there is a quicker time to market).
In the short term, it seems like a win-win. However, when the project is finally complete and retrospectives are being made to compare the original estimated timelines and costs with the actuals, a drastic difference usually comes to light.
Mistakes are more expensive than they appear.