How CIOs and CTOs Are Bridging Cross-Functional Collaboration

For CIOs and CTOs, cross-functional collaboration is not just a communication tactic; it is a governance choice. The practical question is who owns decisions when business priorities, security, data, employee experience and cost all compete. Leaders who create recurring forums, shared vocabulary and clear escalation paths reduce the risk of technology being pulled into after-the-fact approval mode. The management trade-off is speed versus control: too little structure leads to fragmentation, while too much can slow delivery.

The strongest value comes when collaboration changes portfolio choices, not just meeting cadence. Joint reviews with finance, operations and business leaders can surface which initiatives should be funded, sequenced or stopped. That means technology leaders need visible criteria for selecting work: expected business outcome, dependency risk, operating burden and adoption likelihood. A useful next question is whether the current roadmap is still optimized for enterprise value, or simply reflecting the loudest stakeholder.

This also shifts the operating model for IT teams. Translating technical work into business language is necessary, but it is not enough if the organization still measures success only by project completion or system uptime. CIOs and CTOs should ask whether product owners, architects and business leads are jointly accountable for outcomes after go-live. If they are not, collaboration can become performative rather than durable.

For decision-makers, the test is whether cross-functional engagement produces fewer rework cycles, faster prioritisation and clearer benefits realisation. If it does not, leaders should examine decision rights, meeting design and incentive alignment before adding more forums or tools.


ITโ€™s role continues to evolve and so do the everyday things CIOs and CTOs do. Order taking is out, cross-functional problem-solving and innovation are in. At the tip of the spear is IT leadership, building stronger and more collaborative relationships with other leaders in the organization. โ€œEverything we do is in the service of the business, and I mean every function across the company. What I find interesting is that there arenโ€™t too many other functions within an organization that have the kind of vantage point that we have,โ€ says Saket Srivastava, chief information officer at work management platform Asana. โ€œWe work with everyone, so we see what their priorities are and what they are working on. We play that group thatโ€™s connecting the dots and guiding behavior or change in behavior, because we can see things like no one else.โ€ Even without ITโ€™s involvement, work has become more collaborative for both social and technological reasons. Younger generations expect it and there are more channels than ever in which to communicate — email, Slack, Zoom, Asana, and more. โ€œEmployee experience used to be thought of as an HR thing, but you cannot build a delightful, frictionless digital experience without the CIO and CHRO,โ€ says Srivastava. โ€œWhen I started in IT, there was a big conversation around how IT organizations need to be service oriented, which is still important, but weโ€™ve been thinking more from a product-minded shift where we want to build a capability and workforce that has deeper domain understanding on the business side.โ€ IT also needs to talk to the business in business terms versus IT terms, which not only involves a less technical language but also a discussion of benefits, challenges, and other matters that affect business concerns such as risk management, profitability, process efficiency, cost savings, customer loyalty, and more.
Saket Srivastava, Asana
Srivastava says the shift is an important one because IT is partnering with the business as opposed to having a series of meetings and then building something, hoping it will be acceptable. When thereโ€™s a lack of communication on both sides, those on the business side tend to lack empathy when something on the technology side breaks. But when an IT leader is brainstorming on business issues or strategy, the CIO or CTO are more likely to be involved in moving the business forward from the ground floor up. Mike Stawchansky, chief technology innovation officer at global financial services software company Finastra, says it takes significant effort to translate technical goals and projects into accessible formats without coming across as patronizing. โ€œAccessible analogies around shared experiences work well — food and media centricity are common themes for me. Even when language barriers are present, having the genuine intent and desire to communicate something you are passionate about to another person can overcome many obstacles,โ€ says Stawchansky. โ€œShared experience and shared language are core to being able to move initiatives forward. Even if departments outside of technology aren’t 100% clear on the nitty gritty of what is being done, they must be clear on the expected outcomes and benefits.โ€ By explaining in simple terms how a technology will benefit day-to-day work, people are naturally more curious about the work being done in more depth. โ€œAs a technology leader, I view my role as primarily being an evangelist for the work my teams are doing. This includes highlighting and explaining the value of their work,โ€ Stawchansky says. โ€œIf we don’t take the time to do this properly, we may not be given adequate time to โ€˜bake the cake.โ€™โ€

Be a Catalyst for Change

Sumit Johar, CIO of CFO software company BlackLine, was hired specifically to transform how IT collaborates with the rest of the business. โ€œIโ€™ve always believed that technology leadership requires more than just technical expertise. It requires the ability to connect with different parts of the organization in meaningful ways,โ€ says Johar. โ€œ[A]s CIOs, we need to fluently translate technical initiatives into business language that resonates with the CEO, CFO, board members, and other executives. This takes the conversation from operational efficiency to growth.โ€ An example of that is working with the CFOโ€ฏand emphasizing growth and ROI across departments. โ€œHistorically, the CIO was an innovator, and the CFO was in place to enforce guardrails. Together, weโ€™ve built a relationship that looks beyond margins and toward using technology as a lever for continued industry leadership,โ€ says Johar. Johar has also insisted on employee roundtables and having an internal โ€œTech Council,โ€ comprised of members of different teams to come and review new technology initiatives. These forums ensure that every department has a voice when it comes to the technology roadmap, so IT is not working in isolation. โ€œIโ€™ve found that technical jargon can often alienate business stakeholders, making it harder to get buy-in for projects. To overcome this, I focused on making technical discussions relatable. Rather than dive into the nitty-gritty of IT infrastructure, I frame our initiatives around the business impact,โ€ says Johar. โ€œFor example, instead of only discussing how an investment will alleviate technical debt, I explain how an investment will improve operational efficiency and cut costs down the road.โ€
Sumit Johar, Blackline
All departments at Blackline are expected to think more strategically and over the long term. Historically, they worked in silos, which resulted in major planning initiative disconnects. It didnโ€™t help that internal weekly meetings were the easiest to cancel, but keeping those meetings in place led to a mindset shift. Now, those meetings have become future focused on what the company wants to achieve, where itโ€™s headed, and how to build the right infrastructure and teams to support it. โ€œIn the past, CIOs were often brought into conversation only after key decisions were made. Thatโ€™s not going to work out well for anybody. Whether itโ€™s about security posture, data architecture, or automation, my role is to help define how technology can support and even drive these long-term goals, so I need a seat at that table when these discussions are happening,โ€ says Johar.

Book It

Acceldata holds regular cross-functional meetings and organizational leaders collaboratively decide the best way forward. The outcome has resulted in better cross-departmental communication and the company is able to harness diverse perspectives that lead to increased communication. โ€œThe impact has been significant,โ€ says Ashwin Rajeeva, co-founder and CTO at enterprise data observability company Acceldata. โ€œWeโ€™ve become a more agile organization, able to respond quickly to market changes and customer needs. This collaborative culture has enabled us to develop and launch products and features [faster], establishing us as a leader in our field and fostering a stronger sense of community across departments.โ€ As the company grew and more specialized functions were added, the group established a shared vocabulary and aligned on common goals through discussions with key stakeholders and leaders. Regular feedback loops have also helped ensure that everyone feels heard and valued and is committed to shared objectives. Thus far, the organization has improved productivity, enabled faster decision-making, and increased innovation. In addition, the collaborative culture has also boosted employee engagement and morale, leading to more successful project outcomes, faster response to shifting market demands and growth in a highly competitive market. โ€œEvery company is unique, but I recommend prioritizing transparency and inclusivity from the start. Encourage teams to share their ideas and concerns and create structured opportunities for collaboration,โ€ says Rajeeva. โ€œCultivating an environment where everyone feels empowered to contribute is crucial for unlocking the best ideas. This culture not only drives innovation but also builds a vibrant community that can propel your organization toward lasting success.โ€

More Collaboration Yields Higher Levels of Success

Ashwin Ballal, CIO at software company Freshworks, believes that the organizations that fail to collaborate well across departments are leaving money on the table. โ€œSiloed communications create inefficiencies, leading to duplicative work, poor performance, and a negative employee experience. In my experience as a CIO, prioritizing cross-departmental communication has been essential to overcoming these challenges,โ€ says Ballal. His team continually reevaluates the tech stack, collaborating with leaders and users to confirm that the organization is only investing in software that adds value. This approach saves money and helps keep employees engaged by minimizing their interactions with outdated technology. He also uses employees as product beta testers, and their feedback impacts the product roadmap. โ€œThe best companies thrive on constant innovation and collaboration, where all departments operate as a cohesive unit. By breaking down silos, we enhance our overall performance and create a more unified organization,โ€ย Ballal says. โ€œMy recommendation for other CIOs and CTOs is to regularly meet with departmental leaders to understand how technology interacts across the organization. Sending out regular surveys can yield candid feedback on whatโ€™s working and what isnโ€™t. Additionally fostering an environment where employees can experiment with new technologies encourages innovation and problem-solving.โ€
https://www.informationweek.com/it-leadership/how-cios-and-ctos-are-bridging-cross-functional-collaboration

Enjoyed this article? Sign up for our newsletter to receive regular insights and stay connected.