{"id":921,"date":"2019-07-05T08:54:09","date_gmt":"2019-07-05T08:54:09","guid":{"rendered":"http:\/\/janbosch.com\/blog\/?p=921"},"modified":"2019-07-05T08:54:10","modified_gmt":"2019-07-05T08:54:10","slug":"business-starts-with-engineers","status":"publish","type":"post","link":"https:\/\/janbosch.com\/blog\/index.php\/2019\/07\/05\/business-starts-with-engineers\/","title":{"rendered":"Business Starts With Engineers"},"content":{"rendered":"\n
\"\"
Image by rawpixel from Pixabay\n<\/figcaption><\/figure>\n\n\n\n

On a regular basis, I run into engineers who refuse to talk about business, monetization, customer value and related topics. All they want is to get a requirement specification, put on their headphones and start building. Their perspective is that business is the responsibility of others and that their job is to build what they\u2019re told to build.<\/p>\n\n\n\n

Anyone who has read my posts and articles may be aware of the fact that I think that the aforementioned is a fundamentally flawed point of view for at least three reasons. The first reason is that, in practice, R&D sets business strategy. It often takes years for R&D decisions to be fully materialized in the product or system architecture. Consequently, if architects and engineers take the wrong decisions, business opportunities and strategic options that occur sometimes years later are impossible to realize. As I\u2019ve written about this before<\/a>, I don\u2019t want to deep dive into this reasoning, but for R&D staff to make decisions resulting in the largest set of business strategy options requires a deep understanding of the business the company is in as well as a visionary outlook.<\/p>\n\n\n\n

The second reason engineers need to understand the business has to do with R&D effectiveness. Many R&D organizations focus on efficiency in terms of developing as many features per unit of R&D resources. However, building many features that are never used by customers is, obviously, a colossal waste of time and effort. Instead, the focus in R&D should be on generating as much business value per unit of R&D and this is best achieved by building highly differentiating functionality rather than commodity. Unfortunately, our research shows that many companies spend north of 80 percent of their R&D resources on commodity functionality. Although some of that investment is unavoidable, a significant part if driven by engineers who don\u2019t know what functionality is differentiating and what is commodity.<\/p>\n\n\n\n

The third \nreason is that it leads to missed business opportunities. Typically, \nthose in the company with a business background are unaware of \nopportunities offered by new technologies. Even though the \u2018lean \nstart-up\u2019 and broader entrepreneurial community is concerned with \nproblem\/solution fit and product\/market fit and is focused on the \ncustomer, the fact remains that new business opportunities are initiated\n by technology breakthroughs. Engineers and R&D staff, in general, \nunderstand technology and find it easier to hypothesize new and relevant\n applications that benefit customers.<\/p>\n\n\n\n

As engineering is moving from a requirement specification oriented way of working to focusing on quantitative outcomes, it\u2019s critical that everyone in R&D is aware of these desired outcomes as these \u2013 often through a hierarchical value model \u2013 are derived from what we\u2019re looking to accomplish in the business. Consequently, as an engineer, architect or R&D manager, you can no longer afford to be ignorant of the business your company is in.<\/p>\n\n\n\n

Of course, there\u2019s a similar message for those on the business side: even though you may think that you\u2019re in control of the company, in practice it\u2019s decisions made in R&D sometimes years ago that will dictate your success today. Hence, ensuring that your colleagues in R&D understand what the business entails and what is coming in terms of customer, user and business trends is a critical part of your job. View it as an investment in your future success!<\/p>\n\n\n\n

To get more insights earlier, sign up for my newsletter at<\/em>jan@janbosch.com<\/em><\/a> or follow me on<\/em> janbosch.com\/blog<\/em><\/a>, LinkedIn (<\/em>linkedin.com\/in\/janbosch<\/em><\/a>) or Twitter (<\/em>@JanBosch<\/em><\/a>).<\/em><\/p>\n","protected":false},"excerpt":{"rendered":"

On a regular basis, I run into engineers who refuse to talk about business, monetization, customer value and related topics. All they want is to get a requirement specification, put on their headphones and start building. Their perspective is that business is the responsibility of others and that their job is to build what they\u2019re … Read more<\/a><\/p>\n","protected":false},"author":2,"featured_media":0,"comment_status":"open","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\/921"}],"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=921"}],"version-history":[{"count":1,"href":"https:\/\/janbosch.com\/blog\/index.php\/wp-json\/wp\/v2\/posts\/921\/revisions"}],"predecessor-version":[{"id":923,"href":"https:\/\/janbosch.com\/blog\/index.php\/wp-json\/wp\/v2\/posts\/921\/revisions\/923"}],"wp:attachment":[{"href":"https:\/\/janbosch.com\/blog\/index.php\/wp-json\/wp\/v2\/media?parent=921"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/janbosch.com\/blog\/index.php\/wp-json\/wp\/v2\/categories?post=921"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/janbosch.com\/blog\/index.php\/wp-json\/wp\/v2\/tags?post=921"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}