Limiting costs and waste when developing digital products "Product people - Product managers, product designers, UX designers, UX researchers, Business analysts, developers, makers & entrepreneurs 2 February 2016 True Reducing Costs, Research, Mind the Product Mind the Product Ltd 738 Monthly tools spend breakdown by company size Product Management 2.952
· 3 minute read

Limiting costs and waste when developing digital products

Reid Hoffman once remarked, “As the networked age has increased the competitive importance of speed, the key secret is now scaling up at speed.”

In other words, the internet has enabled consumers to rapidly and easily access and assess new technologies that in turn become exponentially more valuable via network effects. It’s therefore more important than ever to get a validated product to market and iterate effectively before the competition. Therein lies the potential and promise of lean methodologies: the ability to learn what users want in the most efficient manner possible.

But that begs the question: from a practical perspective, what progress has product management as an industry made to reduce the waste during throughout the development lifecycle? And what opportunities are there still to improve? We asked more than 100 product managers to establish some benchmarks, and we found five points of interest.

1. Moving fast isn’t cheap

Contrary to what you may have thought, large organizations on the whole don’t take longer to develop digital products than smaller, supposedly more ‘nimble’ companies.

Project duration breakdown by company size

But that speed comes at a significantly higher cost. And in case you’re wondering if product teams have been able to reduce monthly costs by spreading development out over a longer time horizon, just the opposite happens.

Monthly costs breakdown by company size and project duration

As project durations increase, apparently so does complexity which leads to additional costs. Product managers at large organizations should expect that moving faster will come at a cost, and that the best way to lower costs is to decrease the scope of projects into smaller chunks.

2. Building products in-house can reduce costs

In our study we found that more than 80% of respondents develop products in-house while less than 20% outsource to agencies for either parts of or the entire process. Making the digital investment in digital product capabilities seems to be a priority, and it costs less on average per month.

Monthly cost breakdown of in-house vs agency development

Although building product development capabilities in-house is capital and effort-intensive upfront, it could pay off if your organization intends to invest in developing more than just a couple products.

3. Investments in tools grow as companies get bigger

Of the tools our respondents reported most commonly using, the top 15 were dominated by project management, collaboration, cloud, and source code management. And spending on tools begins very modestly before increasing rapidly with company size.

Monthly tools spend breakdown by company size

Interestingly, the percentage of respondents who reported “I don’t know” also spiked in step with number of employees. For large organizations, product managers aren’t necessarily expected to budget for tools, and it would seem that sharing tools and resources across the organizations becomes increasingly common. Considering tools that can scale with the organization should be a point of focus for product managers in growth stage companies.

4. Engineers are apparently chief estimators

When it comes to budgeting, over half of our respondents rely on an estimate from engineering teams, despite the fact that such estimates are notoriously unreliable. Best practice would dictate an iterative approach to budgeting, so that products can be validated in steps, but only 12% of respondents reported budgeting that way.

Budgeting process for product design

In the coming months, we’ll further explore if budgeting methodologies have any correlation with product development efficiency. For now, we know that product managers with iterative budgeting structures are a potentially cutting-edge minority.

5. The stress of failure isn’t confined

We asked product teams to tell us about the other departments that were impacted by a recent product failure. Marketing and sales departments were the most commonly affected, while the C-suite was surprisingly insulated.

Departments involved in product design

No matter how many best practices you adhere to, failure is always a possibility. Product managers that want to limit the potential fallout would be wise to build rapport and buy-in from the teams that could be seriously impacted (not to mention the fact that sales and marketing teams are also instrumental to a product’s success).

Where do we go from here?

The findings above from our report provide insight into how product managers are currently working toward and/or missing opportunities for limiting waste in product development. As speed to market becomes increasingly important, it’ll be worth tracking these benchmarks in the coming years to better identify how companies increase efficiency. In next year’s report we’ll be looking for indicators to determine whether large organizations are able to find ways to develop products quickly without encumbering proportionately large costs, and whether budgeting methodologies will evolve with lean methodologies.

Comments 0

Join the community

Sign up for free to share your thoughts

About the author