{"id":468,"date":"2021-10-17T21:02:19","date_gmt":"2021-10-17T15:32:19","guid":{"rendered":"http:\/\/nocturnalknight.co\/?p=468"},"modified":"2021-10-17T21:02:19","modified_gmt":"2021-10-17T15:32:19","slug":"business-value-delivery-by-engineering-teams-in-startups-part-1","status":"publish","type":"post","link":"http:\/\/3.10.118.248\/?p=468","title":{"rendered":"Business Value delivery by Engineering Teams in StartUps – Part 1"},"content":{"rendered":"\n

In this multi-part post, I will try to articulate my view on the importance of business value and its delivery by engineering teams. While most of this is written from the view of a StartUp, some elements of an established organisation are also used.<\/em><\/p>\n\n\n\n

Part 1: Defining Business Value & Role of Leadership in it.<\/h2>\n\n\n\n

Business value is a concept that can mean multiple things to multiple people and the tricky part is all of them could potentially be valid. A product manager may value a long list of features that his\/her customers have demanded for months. Another Product Manager working with internal teams to improve efficiency (revenue) will value the enhancements the accounting or support team was after. While the support manager may value a more stable product to keep the customers, s\/he deals with happy. <\/p>\n\n\n\n

Business value & impacts are a difficult thing to define and deliver, while it is even more difficult to measure.A collaborative effort is required to define and deliver business value, with consideration needed to ensure all voices are heard. <\/p>\n\n\n\n

While most of what I will be covering in this article is typically the purview of product management, I have learned that engineering leaders have a critical role to play in this space.<\/em> (Will write more on that in the next part<\/em>.)<\/p>\n\n\n\n

Engineering leaders bring product development experience and technical expertise to the table to provide a crucial element to the delivery of business value <\/strong>which I will try and explain in this article. <\/p>\n\n\n\n

What is Business Value?<\/strong><\/h2>\n\n\n\n

I would define “Business value” as any improvements to systems, processes or people that augment the products or the ability to deliver products or services to the customers<\/strong>, thereby increasing the revenue or experience or both. No two companies will have the same definition of business value. Forget two different companies, a company in its 5th year will have a very different perception of value to its first year. This is due to their products and customers being different and requiring different elements to add value. One company may find value in the ability to build out its new product offering quickly. While another may find value in responding to customer support requests in a timely manner. <\/p>\n\n\n\n

Due to the rapid changes around us, the things that businesses value changes often<\/em><\/strong>. Companies often face new challenges that require a quick response.<\/p>\n\n\n\n

“<\/strong>Be agile, be nimble” is the key phrase.<\/p><\/blockquote>\n\n\n\n

These challenges can come in the form of new product features released by competitors, or a specific feature request<\/em> <\/a>by a key customer, or changes in the market that render the current product\/feature obsolete. Business needs or desires, therefore change just as quickly as any of these external<\/em> changes.<\/p>\n\n\n\n

You have probably worked for a company that comes to the engineering team with new requirements, seemingly daily?<\/p>\n\n\n\n

It is not because they cannot make up their mind; It is in response to the changing business needs. <\/em><\/strong>This changing goalpost is one of the main reasons that Agile development practices have taken precedence from more traditional waterfall methodologies for software development. <\/p>\n\n\n\n

Velocity is everything<\/strong>, a report by McKinsey on how Developer Velocity fuels Business Performance <\/a>will give more insights on this. A snapshot from the report is below.<\/p>\n\n\n\n

\"\"<\/figure>\n\n\n\n

Why is business value important? <\/strong><\/h2>\n\n\n\n

Reacting to change and delivering business value with haste is a crucial area of importance for modern businesses. All companies exist for a purpose. The majority of companies exist to return a profit for their owners (individuals or shareholders), while some companies exist to provide a social service. The critical thing to note is that they all exist to fulfil a specific purpose which guides their definition of business value. <\/p>\n\n\n\n

No matter the company large or small, if they stop innovating, and their products or services stop being relevant to society at large and market in particular, that company will whiter and eventually die.<\/p><\/blockquote>\n\n\n\n

Kodak<\/a> is a prime example of this occurring in recent history. In today\u2019s world, IT, whether it be hardware or software, is the largest driver of business value. It is therefore critical that the software engineering teams keep delivering the things that the business need to fuel their innovation.<\/p>\n\n\n\n

We, as engineers, are not employed to just build that shiney app in the latest technologies, but to deliver our contribution in support of the business purpose<\/em> (If not drive it!<\/em>)<\/strong><\/p>\n\n\n\n

The importance of Engineering Leadership<\/strong> in Delivering Business Value<\/h2>\n\n\n\n

An engineering leader is, of course, a People Leader<\/strong>, and s\/he is also responsible for the Execution<\/strong>, both technology and delivery of the engineering team. However there is a third dimension which often goes unrecognised, is that great engineering executives must also be great Business Leaders<\/strong>; they help drive alignment with other leadership\/executives and shape the strategy and direction of the business itself. <\/p>\n\n\n\n

It is this underutilised\/forgotten element which I will try to detail here.<\/p>\n\n\n\n

A People Leader & an Execution Champion:<\/h3>\n\n\n\n

Engineering leadership is often naively thought of as being simply a great Architect or Engineer or a Manager.<\/em> But most of you already know it\u2019s more than that. Team leadership will involve some combination of team building, culture, leadership development, and performance management. <\/p>\n\n\n\n

For detailed coverage on Engineering Leadership – Please checkout my Previous Post<\/a><\/p>\n\n\n\n

Most of this responsibilities will be bang in the middle of the comfort-zone of a rising Engineering Leader.  But one of the hardest things for most engineering leaders as we scale is, to continue having an accurate forecast of when products and features will be delivered<\/strong> \u2013 what the business always asks for. <\/p>\n\n\n\n

That is partially because this bleeds into the third, and the least recognised dimension of engineering leadership.<\/p>\n\n\n\n

The Missing Sauce: A Business Strategist<\/h3>\n\n\n\n

Engineering leadership isn\u2019t just about delivering products faster, or making engineers more productive. It\u2019s about guiding the team in the same direction as the business<\/strong>, about continuously improving, and it\u2019s about being the voice of engineering as a part of the decision-making process of the executive team. Of course, these are all dependent on our ability to understand the work our engineering teams are doing and how it aligns to business goals.<\/p>\n\n\n\n

The third dimension \u2013 Business Alignment <\/strong>\u2013 is often overlooked or made difficult by other executives, but is absolutely necessary for the management of a successful engineering org. This is the strategic practice of engineering management, and all operational decisions depend on it. Business alignment means ensuring your organization is focused on the right projects that align with the business\u2019s goals. <\/p>\n\n\n\n

The Product org can detail\/design and Engineering org can build as many features as they can agree on, but what\/how does it matter, if they do not align with the business objectives or goals? Business alignment involves the right allocation of resources that supports business objectives, and helping to drive those business decisions of which projects are strategically important. (at itilite, this is always the First Principle<\/a>) <\/p>\n\n\n\n

How do we deliver business value?<\/strong><\/h2>\n\n\n\n

So how do we actually deliver business value? Business value isn\u2019t created by a soloist delivering a virtuoso performance, but a collaboration of the business, product, engineering and customer success teams working together to realise a shared vision. <\/p>\n\n\n\n

Below are the five ways this can take place; together, these provide a roadmap for delivering business value; <\/p>\n\n\n\n

  • Define systems development strategy<\/li>
  • Help business define requirements <\/li>
  • Visualise the work and prioritise<\/li>
  • Schedule and communicate delivery<\/li>
  • Deliver value often and get feedback<\/li><\/ul>\n\n\n\n

    I will try to articulate through each of these one at a time and dig into a little more detail in Part 2 of this article.<\/em><\/p>\n","protected":false},"excerpt":{"rendered":"

    We, as engineers, are not employed to just build that shiney app in the latest technologies, but to deliver our contribution in support of the business purpose (If not drive it!)<\/p>\n","protected":false},"author":2,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"om_disable_all_campaigns":false,"_monsterinsights_skip_tracking":false,"footnotes":""},"categories":[19,52,161],"tags":[236,300,378,491],"class_list":["post-468","post","type-post","status-publish","format-standard","hentry","category-business-value","category-engineering-leadership","category-startup-life","tag-business-value","tag-engineering","tag-leadership","tag-startup"],"aioseo_notices":[],"aioseo_head":"\n\t\t\n\t\n\t\n\t\n\t\n\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t