{"id":2156,"date":"2025-12-15T08:01:16","date_gmt":"2025-12-15T08:01:16","guid":{"rendered":"https:\/\/janbosch.com\/blog\/?p=2156"},"modified":"2025-12-15T08:01:16","modified_gmt":"2025-12-15T08:01:16","slug":"end-of-year-reflections","status":"publish","type":"post","link":"https:\/\/janbosch.com\/blog\/index.php\/2025\/12\/15\/end-of-year-reflections\/","title":{"rendered":"End-of-year reflections"},"content":{"rendered":"\n
\"\"
Image by Gerd Altmann from Pixabay<\/figcaption><\/figure>\n\n\n\n

As we approach the end of 2025, it\u2019s clear that the context in which software-intensive companies operate is shifting faster than ever. Over the year, working closely with businesses in domains such as automotive, telecom, industrial equipment and security, I\u2019ve seen a growing divergence. Some organizations are accelerating, embracing data and AI to transform their products and R&D systems, while others remain stuck in incremental improvements, understandably cautious but increasingly vulnerable to global competition.<\/p>\n\n\n\n

Across the Software Center companies and the various startups and scale-ups I engage with, the speed of learning has once again proven to be the most important predictor of future performance. In a world where models evolve weekly, customers expect continuous updates and regulatory requirements tighten, staying with the old way of doing things is the real risk. We need to change faster, but this isn\u2019t about hero culture or pushing people harder. It\u2019s about designing systems \u2013 organizational, technical and data-driven \u2013 that allow companies to operate in radically different ways.<\/p>\n\n\n\n

As an end-of-year reflection, I thought I\u2019d share five technology breakthroughs that made 2025 pretty exciting from my perspective. In addition, I pose five questions that I believe would be good to reflect on during the Christmas break as we prepare for the new year.<\/p>\n\n\n\n

1. AI code generation becomes a reliable contributor<\/strong><\/p>\n\n\n\n

During the year, AI-based development tools matured significantly. Following my experiences, as well as what can be read in the media, such tools generate 30\u201340 percent of routine coding, test scaffolding and documentation. I know of cases where engineers contribute to code bases that they have little to no experience in and that may even have been written in languages that they don\u2019t know (well). Teams move faster with higher quality, not just because of automation but because engineers get to focus on the hard problems.<\/p>\n\n\n\n

2. Automated architecture and system modeling reach practical viability<\/strong><\/p>\n\n\n\n

Several research prototypes and early industrial tools can now generate interface definitions, executable models and alternative architectural designs in software. Not only that, AI-driven co-design environments can now propose alternatives in mechanics, electronics and system control loops. The boundaries between software, electronics and mechanics are starting to become more fluid as these tools identify better designs and more optimally allocate functionality to different technologies.<\/p>\n\n\n\n

3. High-quality synthetic data becomes standard practice<\/strong><\/p>\n\n\n\n

Using real-world data is hard in many use cases, either because of regulatory compliance, such as GDPR and the Data Act, or because of low incidence rate, such as in autonomous vehicles. Therefore, it\u2019s good to see that we\u2019re getting better at generating domain-specific synthetic data, especially for sensor-heavy products, that closely mirrors real-world data. It allows companies to escape the bottleneck of rare-event collection and avoid violating regulations.<\/p>\n\n\n\n

4. Real-time compliance validation enters the CI\/CD pipeline<\/strong><\/p>\n\n\n\n

With the AI Act, Data Act, cybersecurity requirements and sector-specific regulations intensifying, compliance is shifting from annual audits to continuous validation. Tools that scan artifacts, pipelines and model behavior in real-time materially reduce compliance overhead and risk. For example, I\u2019m involved with Kosli, concerning regulations in fintech, and ExplorAI, concerning the AI Act, to develop solutions that reduce manual effort by companies.<\/p>\n\n\n\n

5. The first real AI-first product patterns emerge<\/strong><\/p>\n\n\n\n

In 2025, several companies launched products architected around AI from the outset. Perception, decision-making and user interaction rely on ML components as first-class citizens. These early examples foreshadow a phase where entirely new product categories will emerge \u2013 particularly in mobility, industrial automation and engineering tools. Although it\u2019s still early days, we see companies deploying ML into cameras, ECUs, controllers and other constrained devices as the cost and time required to reach production-quality performance have dropped dramatically. Tools that monitor ML model performance in production and trigger safe retraining have become stable enough for early adoption, allowing companies to deploy ML that evolves rather than degrades over time.<\/p>\n\n\n\n

As I wrote last week<\/a>, I\u2019m worried about the situation in Europe and the slow changes I\u2019m seeing in industry. As most of us are soon taking some time off during the holiday season, I wanted to share some questions for all of us to reflect on while we\u2019re out, in the hope that 2026 will show a significant acceleration.<\/p>\n\n\n\n

Question 1. Where can AI realistically double our productivity and what stands in the way?<\/strong><\/p>\n\n\n\n

This isn\u2019t about ambition but about identifying concrete domains, such as coding, testing, documentation or ML in the product itself, where AI can unlock measurable acceleration. As I shared in [the series during the fall](https:\/\/bits-chips.com\/article\/the-ai-driven-company-conclusion\/), AI isn\u2019t only relevant in R&D but should also be used to reinvent business processes as well as the business ecosystems in which we operate.<\/p>\n\n\n\n

Question 2. Are we still organized around agile rituals or do we use fast data-driven learning loops?<\/strong><\/p>\n\n\n\n

Many of you will know that I feel that Agile has reached the end of its useful life. Many of the principles, such as fast feedback loops, are still relevant, but rather than practicing Agile mechanically, we need to focus on continuous, data-driven learning loops. The real shift is toward continuous value delivery, fast experimentation and learning from operational data.<\/p>\n\n\n\n

Question 3. Do we treat data as a strategic asset with clear ownership, quality control and lifecycle management?<\/strong><\/p>\n\n\n\n

Although the embedded-systems industry increasingly collects vast amounts of data, the actual use of that data is still quite poorly realized in many of the companies I work with. Whenever data and opinions collide, still the opinions win in most cases I\u2019ve been part of. Of course, we need to move toward using data as a strategic asset.<\/p>\n\n\n\n

Question 4. How much of our compliance burden can we automate?<\/strong><\/p>\n\n\n\n

Although there\u2019s significant progress in integrating the compliance burden in the CI\/CD chain, the amount of manual effort in most companies is still incredibly high. Especially in highly regulated industries, the cost for automated compliance can reach 10 percent of revenue, according to some studies. The only way that I see to reduce cost and risk while enabling faster releases is through automation.<\/p>\n\n\n\n

Question 5. What are we doing to increase organizational learning speed?<\/strong><\/p>\n\n\n\n

For all the talk about AI, the fact remains that it\u2019s humans and organizational change that are on the critical path. Adoption is slow, not because the technology isn\u2019t there, but because the people in organizations fail to adopt it at the necessary pace. We need shorter feedback loops, smaller batches, faster experimentation and more autonomy to change faster. Rather than for efficiency, we need to optimize for learning speed.<\/p>\n\n\n\n

2025 confirmed what many of us already sensed: the companies that treat AI and data as structural enablers are pulling ahead. The good news is that the tools are becoming more accessible, the workflows clearer and the potential benefits more quantifiable. But capturing this potential requires more than technology adoption. It demands rethinking how products are conceived, how R&D is organized, how data flows through the organization and how compliance is integrated into the development process. As we head into 2026, the challenge and opportunity for software-intensive companies is the same: design organizations and systems that learn faster than the competition. Those who do will help define the next decade of innovation. To end with a quote from Peter Senge: \u201cA learning organization is an organization that\u2019s continually expanding its capacity to create its future.\u201d<\/p>\n\n\n\n

Want to read more like this? Sign up for my newsletter at\u00a0jan@janbosch.com<\/a>\u00a0or follow me on\u00a0janbosch.com\/blog<\/a>, LinkedIn (linkedin.com\/in\/janbosch<\/a>) or X (@JanBosch<\/a>).<\/em><\/p>\n","protected":false},"excerpt":{"rendered":"

As we approach the end of 2025, it\u2019s clear that the context in which software-intensive companies operate is shifting faster than ever. Over the year, working closely with businesses in domains such as automotive, telecom, industrial equipment and security, I\u2019ve seen a growing divergence. Some organizations are accelerating, embracing data and AI to transform their … Read more<\/a><\/p>\n","protected":false},"author":2,"featured_media":0,"comment_status":"closed","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"generate_page_header":"","footnotes":""},"categories":[8,10],"tags":[],"_links":{"self":[{"href":"https:\/\/janbosch.com\/blog\/index.php\/wp-json\/wp\/v2\/posts\/2156"}],"collection":[{"href":"https:\/\/janbosch.com\/blog\/index.php\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/janbosch.com\/blog\/index.php\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/janbosch.com\/blog\/index.php\/wp-json\/wp\/v2\/users\/2"}],"replies":[{"embeddable":true,"href":"https:\/\/janbosch.com\/blog\/index.php\/wp-json\/wp\/v2\/comments?post=2156"}],"version-history":[{"count":1,"href":"https:\/\/janbosch.com\/blog\/index.php\/wp-json\/wp\/v2\/posts\/2156\/revisions"}],"predecessor-version":[{"id":2157,"href":"https:\/\/janbosch.com\/blog\/index.php\/wp-json\/wp\/v2\/posts\/2156\/revisions\/2157"}],"wp:attachment":[{"href":"https:\/\/janbosch.com\/blog\/index.php\/wp-json\/wp\/v2\/media?parent=2156"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/janbosch.com\/blog\/index.php\/wp-json\/wp\/v2\/categories?post=2156"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/janbosch.com\/blog\/index.php\/wp-json\/wp\/v2\/tags?post=2156"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}