When building software, a key question often arises: how much of your development resources should go towards maintaining the tech and platform stack versus focusing on features and functionality for the app domain? Ideally, only about 10% should be spent on work outside the app domain, while 90% should be dedicated to creating improvements that directly benefit your users. This balance ensures that the product evolves in meaningful ways, addressing user needs and maintaining competitiveness.

However, reality often looks different. Teams sometimes allocate the bulk of their attention to the platform stack, neglecting app functionality. Features the users care about may be delayed or underdeveloped because too much time is spent on infrastructure and internal systems. This tendency can create a disconnect between the system’s technical brilliance and what users experience.

The rise of DevOps has also played a role in these misaligned priorities, as merging development and infrastructure responsibilities has blurred traditional boundaries. While the intention is to streamline workflows, it can lead to a drain on resources. Developers are often absorbed by platform stack tasks that become overly complex and expensive without necessarily adding proportional value to the users.

The temptation to over-engineer is a common pitfall. Teams often ask themselves if the stack needs to be sophisticated or costly, but many times the answer is no. A simpler, lean stack can be more maintainable and sufficient for current needs while leaving room for future adjustments. Overcomplicating things usually comes at the cost of focus on app functionality.

An important factor to consider is the psychological comfort developers find in tech-only tasks. Working in the platform stack feels safer, as mistakes are often less visible than in user-facing areas. The app domain, on the other hand, can feel risky. Errors in the app can directly impact users, making developers more hesitant to focus their efforts there. Yet, this avoidance often leads to resource misallocation and slower progress where it matters most.

To restore balance, teams should prioritize user value when allocating resources. Metrics that emphasize feature use and customer satisfaction rather than internal stack achievements can help shift focus back to user needs. Collaboration between developers working on the tech stack and those focused on app functionality can ensure both areas remain aligned. Additionally, fostering a culture where developers feel safe tackling user-facing challenges can ease the fear of mistakes and encourage innovation.

Finding the right balance is critical. The stack should empower the app domain, not overshadow it. By dedicating the majority of resources to building and improving features that matter to the users, teams can create products that deliver real impact while keeping the underlying infrastructure lean and efficient.