Closing the Distance Between Business Stakeholders and IT: Why It Matters and How to Do It
Your IT department can talk in business terms and propose new or better ways of handling particular business cases. All it takes is closing the distance between IT and stakeholders.
Modern companies rely more and more on technology. Whether you build a product or provide a service, you probably have an IT team that helps your business deliver value to customers. That holds even for organizations whose offer is not purely digital. Ignore technology, and you may fall behind your competitors. Use it, and you most likely run a lot of processes that IT has to build, maintain, and keep evolving as the business landscape keeps shifting.
As the organization grows, its IT systems unavoidably get more complex. New teams appear and specialize to serve various business needs, yet they also start to depend heavily on each other. Gradually, the agility you had at the start may disappear. Making changes or shipping new features takes longer and frequently requires more people and teams. This typically stems from complexity that piles up as features are added or existing systems are changed. You cannot fully avoid the essential complexity of the business, but you can keep the accidental complexity introduced at the technical level under control.
This is why it pays to invest not just in outstanding engineering skills but also in close cooperation and end-to-end partnership. Correctly identifying domain areas, uncovering business processes, sharing knowledge, and setting teams up with care can deliver substantial long-term gains for your organization.
Using a shared language and working toward a shared goal
Business stakeholders often complain that IT is cut off from ‘real business’ and lives purely in a technical bubble. They may feel that IT talks in convoluted jargon, does not grasp what the product needs, or fails to deliver as expected. Consequently, IT departments are sometimes regarded as a ‘necessary evil’ and nothing more than a cost center.
Must it be like that, though? Imagine your IT department speaking your language and proposing new or better ways to handle particular business cases, drawing on what it knows about technical details and possibilities. Imagine it noticing untapped potential for features that could give your business a competitive edge. Ideally, everybody should be pulling in the same direction, shouldn’t they?
Fortunately, this is achievable. Proven approaches and techniques exist that bring business and IT closer, build a common understanding of business problems, and eventually merge them into a genuinely unified product team. It is not a quick fix – it takes time, effort, and discipline on both sides – but the payoff can be considerable. For example, when business and tech teams work together in Event Storming workshops, or when teams create Context Maps (from DDD toolbox), misunderstandings and hidden, implicit assumptions tend to come to light. Uncovering them during a ‘sticky notes on the wall’ workshop is far better than weeks or months later, after code tackling the wrong problem has already been written. Tech people who are genuinely aligned with the business are a huge asset.
The right boundaries limit the impact of change and improve delivery flow
Have you ever had to involve most of the teams, each working on its own services, just to build a single new business feature? That may be warranted for large, strategic changes affecting the whole business, but it should not be the rule. Why, then, does it happen so often? One possible cause is that the system has been split up incorrectly: boundaries, responsibilities, and domain areas are poorly defined or have worn away over time.
Say you want to add a new payment method, and suddenly your inventory or shipment services have to be changed to deal with payment details, even though how an order was paid should not concern them at all. Or the teams responsible for customer services have to make changes so that customers are notified correctly depending on the new payment method.
And if you are wondering – it makes no difference whether you use microservices. If you fail to identify and maintain the right boundaries, sooner or later teams become coupled in ways nobody intended. That, in turn, reduces their independence and agility, slows down delivery, and blocks experimentation and trying out new features. Worse still, changes made to such badly partitioned systems frequently call for extra code to work around the unwanted coupling, adding to the accidental complexity mentioned earlier.
Investing in thorough domain and business discovery, identifying boundaries, and accurately mapping real dependencies is worth it. It is fairly inexpensive, because you acquire that knowledge before anyone writes code, sparing your teams from building on a faulty foundation. Naturally, this is not only for greenfield projects. Changing direction on existing products can be harder because of the setups, constraints, and codebases already in place. Then again, it can be easier in that you likely already have answers to most business questions, and many hidden assumptions have come out during the project. So even for an existing project, it is worth starting now if you have not done so yet. Moreover, enriching discovery and modeling techniques with lessons from approaches such as Team Topologies, and organizing teams along those lines, can bring measurable improvements in delivery and effectiveness.
Evolving and adjusting to shifting business requirements
Earlier, I mentioned the chance of uncovering hidden opportunities that can help your business grow. Once again, such opportunities are much easier to notice when your system is well partitioned and has clear boundaries that show exactly how the various business areas work together. Techniques such as Event Storming or strategic Domain-Driven Design (with its Bounded Context and Context Map concepts) make it far simpler to build systems that can evolve quickly and allow experimentation and iteration without pulling in every team.
Since business never stands still, your priorities and areas of focus will shift too. Some areas gain strategic importance, new ones appear to support existing ones, and others gradually become commodities. Tools such as Wardley Maps help you visualize and anticipate this evolution by modeling how your business context changes as market conditions or competitors’ moves change. Still, noticing possible changes is not enough – you also need a system and a team structure able to adapt.
Suppose you predict, and bet on, a particular area of your business soon becoming a commodity because off-the-shelf software for it is starting to appear. You might then choose to concentrate on your core business domain and wind down in-house development of that commodity – perhaps buying it, or outsourcing its maintenance and slowing down development that is no longer a priority. Here too, clear and well-kept boundaries make such a transition easier and help you retain some of the agility you started with.
Seeing the legendary ‘big picture’ from both perspectives
In large companies, developing specialized areas of expertise can lead to knowledge silos. Experts in particular areas are valuable, but it is just as important that teams grasp the bigger picture. Do your teams know where their work sits in the overall value chain? Do they understand how processes work from end to end, or just their own piece?
Closer cooperation between business and tech helps break down silos. It also pushes people to look past their own domains, which yields valuable insights, reveals potential problems, and uncovers new opportunities. Collaborative modeling approaches such as Event Storming are especially helpful when applied consistently and properly.
The Context Maps mentioned earlier (a Domain-Driven Design concept) are useful as well. They may look purely technical at first, but I am convinced stakeholders can get value from them too. Because they focus on business areas and how they interact (instead of technical services and deployment units), everyone can understand these maps. You can see which team is responsible for each area, which teams a new feature will need, and how information and team dependencies move through the system. That visibility lets you get a rough sense of how a feature will affect the system.
Engineers get extra insights from Context Maps, such as relationships between teams and integration styles, which feed into decisions about future changes. They also act as living documentation for new joiners and for team members moving between areas.
Summary
Hopefully, the advantages of bringing your tech teams closer to the business are now clear. Doing so can improve delivery flow, cut down on misunderstandings, and help you avoid shipping technically sound solutions to the wrong problem. A shared language, a clear common view of the business, and well-defined boundaries around business concepts all lead to better strategic decisions, correct solution design, and more effective long-term maintenance and development of systems.
At our company, we do more than deliver robust, high-performance software that meets our clients’ demanding technical requirements. Our teams become their genuine technology partners, helping them achieve their goals by building software that suits their businesses best both now and as they grow. We know that code is not the end goal – it is usually just the vehicle needed to get there. The vehicle we build speeds up reaching the goal rather than slowing it down, and it can go the distance as the business evolves. None of this would be possible without excellent engineers who are able to – and know how to – really understand the business, working hand in hand with stakeholders and business experts.