This article examines the issue of friction in software development and proposes, as an alternative and complement to top-down initiatives, the bottom-up enhancement of Developer Experience (DevEx). Large-scale productivity losses caused by cognitive overload, tool inefficiencies, and organizational misalignment translate into big bucks when it happens on an industrial scale. That is what makes this study relevant. The objective is to provide theoretical and practical justification for empowering engineers as agents of change within DevEx governance. The study’s novelty lies in integrating three analytical frames—DevEx, Cognitive Load Theory, and the socio-technical congruence model—into a unified, multi-level model of friction, and in proposing practical instruments (a friction log and the DX-champion role) that transmute local engineer-led initiatives into mechanisms for diagnosing and correcting systemic incongruences. The main takeaways speak to the constraints of solely top-down efforts which depend on accumulated measures and choices that disregard the daily worker's perspective. The suggested bottom-up method demonstrates awareness of small-scale mental blocks and establishes ways to leverage nearby worker insights into company progress. An optimal configuration likely combines both approaches. Top-down initiatives provide empirical grounding and organizational commitment. Bottom-up efforts offer concrete means of change and organic growth. The article will be useful to software engineering researchers, technology organization leaders, and practicing engineers interested in systematically elevating the quality of DevEx.

Developer Experience, cognitive load, socio-technical congruence, bottom-up approach, software development productivity, engineering practices

Atlassian. (2025). State of Developer Experience Report 2025. Atlassian. https://www.atlassian.com/teams/software-development/state-of-developer-experience-2025

Baxter, K. A., Sachdeva, N., & Baker, S. (2025). The Application of Cognitive Load Theory to the Design of Health and Behavior Change Programs: Principles and Recommendations. Health Education & Behavior, 52(4), 469–477. https://doi.org/10.1177/10901981251327185

Cataldo, M., Herbsleb, J. D., & Carley, K. M. (2008). Socio-technical congruence: a framework for assessing the impact of technical and work dependencies on software development productivity. Proceedings of the Second ACM-IEEE International Symposium on Empirical Software Engineering and Measurement - ESEM ’08, 2-11. https://doi.org/10.1145/1414004.1414008

Fagerholm, F., & Münch, J. (2013). Developer Experience: Concept and Definition. Arxiv. https://doi.org/10.48550/arxiv.1312.1452

Forsgren, N. (2024, January 23). Quantifying the impact of developer experience. Microsoft Azure. https://azure.microsoft.com/en-us/blog/quantifying-the-impact-of-developer-experience/

Forsgren, N., Storey, M.-A., & Maddila, C. (2021). The SPACE of Developer Productivity. ACM. https://queue.acm.org/detail.cfm?id=3454124

Gerdemann, D., McLaren, L., Werner, S., & Hesse, D. (2024, August 19). Speeding up software development. Kearney. https://www.kearney.com/service/digital-analytics/article/speeding-up-software-development

Gkintoni, E., Antonopoulou, H., Sortwell, A., & Halkiopoulos, C. (2025). Challenging Cognitive Load Theory: The Role of Educational Neuroscience and Artificial Intelligence in Redefining Learning Efficacy. Brain Sciences, 15(2), 203. https://doi.org/10.3390/brainsci15020203

Harvey, N. (2025). DORA’s software delivery metrics: the four keys. DORA. https://dora.dev/guides/dora-metrics-four-keys/

Ju, A., Sajnani, H., Kelly, S., & Herzig, K. (2021). A Case Study of Onboarding in Software Teams: Tasks and Strategies. Arxiv. https://doi.org/10.48550/arxiv.2103.05055

KubeCon. (n.d.). Keynote Speakers. LF Events. Retrieved August 11, 2025, from https://events.linuxfoundation.org/archive/2024/kubecon-cloudnativecon-north-america/program/keynote-speakers/

Mark, G., Gudith, D., & Klocke, U. (2008). The cost of interrupted work. Proceedings of the Twenty-Sixth Annual CHI Conference on Human Factors in Computing Systems - CHI ’08, 107–110. https://doi.org/10.1145/1357054.1357072