Cross-Functional Squads: From Silos to Speed. Collaboration is a pivotal principle in innovation leadership, largely because major customer challenges rarely fit neatly within a single department. For instance, consider common scenarios like a frustrating onboarding experience for new users, lengthy delays in service requests, a checkout process that confuses customers, or a product feature that fails to deliver reliability. Each of these issues typically affects multiple functional areas, including product management, design, technology, operations, customer support, data analytics, compliance, and marketing. When these departments operate in isolation, the organisation often becomes entangled in bureaucratic hand-offs, waits for approvals, and optimises tasks at the individual level rather than focusing on a seamless overall customer experience.
To address and break free from this fragmented approach, organisations can leverage the concept of a cross-functional squad. A cross-functional squad consists of a diverse group of team members with the skills and authority to tackle a specific problem end to end, from initiation to resolution. Unlike traditional processes that pass projects from one functional silo to another, a squad takes collective responsibility for diagnosing the issue, selecting appropriate solutions, testing them, learning from the results, and continuously refining outcomes based on real-time feedback. This methodology is especially critical in environments where speed, experimentation, and the ability to respond swiftly to customer needs are paramount. By using cross-functional teams, organisations can reduce friction from conventional functional barriers, enabling faster product development and iterative improvements.
It’s essential to underscore that a squad is more than a project group rebranded with a different title; it is a temporary, purpose-driven team assembled with a defined mission and measurable impact in mind. These squads have a degree of autonomy that lets them make decisions and move quickly without escalating every minor choice to higher management. Innovation leaders play a crucial role in creating the right conditions for these squads to operate decisively, while ensuring they remain aligned with the organisation’s broader strategic goals, adhere to established standards, and fulfil customer commitments. By fostering this environment, organisations can improve agility and responsiveness, ultimately boosting customer satisfaction and strengthening their competitive position in the market.
Designing Squads for Optimal Outcomes
To build effective squads, centre their mission on achieving specific, high-impact outcomes rather than merely overseeing fragmented tasks within a broader operational framework. Instead of assigning a squad to perform a narrowly defined task, such as “redesigning the account-creation page,” a more impactful mission would be to “reduce customer abandonment during the account creation process and enhance the rate of successful activations.” This refined objective encourages the squad to consider the entire user journey and experience. They would investigate elements such as the clarity and effectiveness of the language used, the usability and design of forms, the performance of underlying technologies, the content of confirmation emails, support documentation, and internal follow-up processes.
Defining a Primary Outcome Metric
Each squad must focus on a single, primary outcome metric that serves as a guiding beacon for their efforts. A visible, distinct metric helps prevent the team from getting caught up in busywork that doesn’t drive real effectiveness. Depending on the specific mission, the metric selected might include:
- Increasing the percentage of customers who complete a critical task during their interactions with the service or product is essential for driving overall satisfaction and loyalty. This involves identifying key tasks within the user journey and implementing strategies, such as intuitive design and targeted support, to guide customers toward successful outcomes.
- Reducing the time it takes to resolve customer inquiries or requests is vital to improving operational efficiency. This can be achieved through streamlined processes, better training for support staff, and technology such as chatbots or ticketing systems, which enable quicker resolutions and help maintain customer engagement.
- Minimising repeat contacts to customer support is a strong indicator of improved first-contact resolution. By proactively addressing common issues, implementing thorough training programs for support staff, and analysing customer feedback, organisations can improve first-contact resolution rates, leading to a more positive customer experience.
- Improving first-time user activation is crucial to ensuring new users can effectively navigate and use the product. This can involve onboarding processes with tutorials, guided walkthroughs, and personalised assistance to help users build confidence and maximise product usage from the outset.
- Reducing errors, rework, and failed transactions helps streamline processes and improve customer satisfaction. By conducting thorough quality checks, refining workflows, and leveraging automation, organisations can reduce the likelihood of errors, ensuring a more seamless customer experience and fostering trust in the brand.
- Higher adoption rates of valuable product features indicate the effectiveness of engagement strategies. This could involve targeted marketing campaigns, user education initiatives, and feedback loops to encourage customers to explore and benefit from advanced features, ultimately promoting more robust interaction with the product.
This metric must be specific enough to provide clear direction and support decision-making, while also including sensible guardrails. For example, if a squad is tasked with reducing the average handling time for customer calls, they should simultaneously monitor customer satisfaction and repeat-contact rates. Ignoring these aspects could lead to a scenario where calls are shorter, but service quality diminishes, leaving customers feeling underserved.
Evaluating Effectiveness
In high-performing product teams, assessing effectiveness goes beyond activity counts. Instead, it is rooted in measurable outcomes that reflect delivery predictability and realised business value. Teams should prioritise achieving tangible results that ultimately drive value for the organisation and its customers.
Implementing a Time-Boxed Mission
Additionally, a time-boxed mission is essential for maintaining momentum and fostering urgency within the squad. Time-boxing helps teams avoid drifting into an endless cycle of transformations without clear endpoints. A mission length of around six weeks is typically ideal, as it allows the squad to understand the specific problem they are addressing, develop and test potential interventions, and measure initial results while staying focused.
At the conclusion of the time box, leadership can then assess the outcomes and make strategic decisions regarding the next steps: whether to scale the solution if successful, conduct further experimentation if additional learning is required, transition the work to a permanent team for ongoing management, or close the mission and leverage the insights gained for other initiatives. This structured approach to squad design and management keeps the organisation agile, focused, and results-driven.
Include the Right Roles
A squad’s makeup can vary significantly based on the unique challenges or problems it addresses. However, a balanced team typically encompasses a blend of skills and perspectives from various functions: product management, design, engineering, operations, and data analysis. The goal isn’t to gather every conceivable specialist for every discussion; rather, the squad must have easy access to the expertise and decision-making power needed to move from insights to actionable results.
Role Contributions to the Squad
Product: The product role is fundamental in defining and articulating the customer’s problem. This individual not only ensures the squad’s mission aligns with the organisation’s overall strategic goals but also prioritises trade-offs essential for effective decision-making. They maintain focus on the intended outcomes, ensuring the team stays on track as they develop solutions.
Design: The design role introduces a deep understanding of the customer experience through empathy, research, journey mapping, and prototyping. This individual prioritises usability and clear communication, ensuring the solutions developed are not only functional but also resonate with the end user. Their insights are crucial in making design choices that enhance user satisfaction and engagement.
Engineering: Engineers in the squad evaluate the technical feasibility of proposed solutions. They build or configure these solutions while identifying potential risks along the way. Their expertise supports rapid prototyping and testing, which is vital for validating ideas quickly and efficiently.
Operations: The operations representative serves as a critical link between the squad and the real-world execution of strategies. This individual brings insights into delivery processes, frontline constraints, and service quality, ensuring that implementation requirements are met. Their knowledge helps the squad navigate operational limitations and ensures that the solutions created are practical and sustainable.
Data: The data role establishes a solid analytical baseline. This individual plays a critical role in supporting experiments that help the team distinguish between valid signals and assumptions, ultimately guiding data-driven decision-making.
Subject-Matter Experts: When specialised knowledge is necessary, subject-matter experts join the squad as needed. These individuals provide insights into areas such as legal compliance, risk management, financial implications, procurement strategies, security issues, customer service challenges, or marketing tactics. Their contributions are often crucial for navigating complex decisions that require expertise outside the core team.
Time Commitment and Accountability
Not every role must be filled full-time. What matters most is clarity on each member’s availability, decision-making rights, and accountability. If an engineer is only nominally assigned to the squad but is unavailable to contribute for an extended period—such as two weeks—this can hinder progress. Similarly, if an operations representative has no authority to modify the processes under review, the squad may quickly lose momentum. Leaders must prioritise squad members’ time, protecting them from being evaluated solely on the demands of their primary roles in the organisation.
Shared Leadership and Facilitation
Implementing rotating facilitation can help build a culture of shared leadership within the squad. For instance, one person might lead the weekly planning session, another might oversee the customer-insight review, and yet another could guide the retrospective meetings. This rotation of roles reduces dependence on a single facilitator, broadens the squad’s leadership capabilities, and reinforces that collaboration is a collective responsibility.
While shared leadership emphasises collaboration and inclusivity, roles and responsibilities must remain well defined. The squad must be clear on who owns the mission, who makes final decisions in cases of disagreement, and how decisions are documented. This structure ensures that while everyone is encouraged to participate actively, accountability and leadership remain clear.
Create Disciplined Ways of Working
For cross-functional squads to thrive, they need to implement lightweight yet effective discipline. Without this structure, collaboration can devolve into a series of unproductive meetings where team members merely exchange updates, leaving actual progress stalled. To address this, adopt three key practices: a shared backlog, regular demo days, and a decision log.
A Shared Backlog
A shared backlog serves as a single, transparent repository of the squad’s work. This centralised list should include a variety of tasks and items, including customer research initiatives, hypotheses that require validation, necessary process changes, technical implementations, experimental projects, potential risks, and decisions pending input from team members.
The backlog should be organised by the estimated impact each item will have on the squad’s overall mission. For example, if the primary goal is to alleviate customer friction points, the next task on the list should be prioritised by which action is most likely to contribute to that goal, rather than defaulting to the easiest task available for any given department. This approach keeps the squad focused on tangible outcomes that directly improve the customer experience.
Regular Demo Days
To maintain visibility over the squad’s progress and to foster a culture of continuous learning, implementing regular demo days is essential. These demonstrations can occur weekly or bi-weekly, giving the squad a platform to showcase what has been discovered, tested, built, modified, or measured in the interim.
The presentations can be intentionally straightforward: examples include a prototype of a new product, a refined customer journey map, updates to support scripts, newly developed dashboards, trial results from process changes, or feedback from real customers. The objective is not to deliver a polished, rehearsed presentation, but to make progress observable, solicit timely feedback, and minimise the chance of surprising stakeholders with incomplete or unexpected results at the end of a project. Moreover, end-to-end demos help team members visualise solutions, gather insights, and build a shared understanding across diverse perspectives.
Establishing a Decision Log
To address the common issue of revisiting decisions already made, maintaining a decision log is vital. This log should document every significant decision by recording essential details such as the issue at hand, options considered, the evidence that informed the decision, the designated decision owner, the final choice, the decision date, and any necessary follow-up review points.
This practice is particularly beneficial in diverse squads, as members often have different professional backgrounds and may present varied opinions on the same matter. By documenting decisions clearly, the squad can maintain clarity in their direction without necessitating total agreement. Atlassian’s DACI framework can also be used to distinguish the roles of the decision driver, approver, contributors, and those who must be kept informed, while preserving the reasoning behind the conclusion.
Establishing a Predictable Rhythm
In addition to these practices, squads should create a predictable workflow rhythm. A short weekly planning session is recommended to assess key metrics, review the backlog, identify blockers to progress, and outline the next experiment. Separate working sessions can then focus specifically on problem-solving rather than merely reporting status.
Furthermore, conducting a brief retrospective at the conclusion of each sprint or bi-weekly period allows the team to reflect on both their collaboration methods and the outputs they have produced. The overarching goal is to establish a dependable cadence in which ongoing learning informs future decisions, those decisions lead to concrete actions, and those actions yield verifiable evidence of success.
Enable Collaboration in Practice
For leaders aiming to foster effective collaboration within a squad, it’s crucial to understand that systems rewarding siloed behaviour can severely hinder cross-boundary teamwork. Simply put, the structural and organisational frameworks must support collaboration as much as the squad’s organisational chart does.
One practical approach to encourage collaboration is through designated collocated workdays. These days are particularly effective at building trust and strengthening the squad’s problem-solving capabilities, especially at the start of a project or ahead of pivotal decisions. This approach does not require abandoning flexible work arrangements; instead, it encourages intentional team gathering. When physical presence is feasible, this might mean a day spent together in a shared space. When that isn’t possible, highly interactive virtual workshops can serve as a strong alternative. These engagements are invaluable for establishing shared context, fostering creative problem-solving, or addressing conflicts directly. For instance, dedicating a day to collaboratively map the customer journey, review supporting evidence, and agree on the initial experiments can drastically reduce weeks of misunderstandings and fragmented communication that might follow.
Equally critical is establishing shared incentives. If individual functions such as product development, operations, engineering, and customer service are rewarded based on metrics such as feature delivery, cost reduction, system stability, or contact duration, this can lead to outcomes where each team makes sound decisions in isolation, ultimately undermining the overall customer experience sought by the squad. To mitigate this, the squad’s mission metric should be prominently displayed in all performance discussions, team evaluations, and leadership reports. Research indicates that successful cross-functional collaboration hinges on shared performance measures and a commitment to regularly reviewing cross-functional key performance indicators.
Moreover, establishing conflict protocols is essential to manage disagreements constructively and prevent them from devolving into personal or political disputes. A team can, for example, agree to challenge assumptions rather than individuals, back up claims with evidence whenever possible, articulate trade-offs openly, and escalate issues only when decision-making authority is ambiguous or when risk levels surpass the squad’s capacity. Once a decision is reached, all team members should fully embrace it. In an innovation squad, healthy conflict is not just acceptable but necessary. Different disciplines bring unique perspectives on risks, opportunities, and customer needs, and only by exploring these viewpoints openly can true innovation arise. The real challenge occurs when teams sweep disagreements under the rug, postpone them, or approach them through the lens of functional power dynamics rather than resolving them through a unified strategy focused on shared outcomes.
Finally, fostering psychological safety is crucial for effective collaboration. Squad members must feel empowered to voice uncertainties or challenge existing ideas with statements like, “We do not know,” “This assumption may be incorrect,” or “This idea is not yielding the desired results.” Innovation depends on rapid learning, and this process thrives on confronting uncertainties proactively and early. Leaders play a pivotal role in shaping this environment by rewarding openness, regularly inquiring about the team’s learning experiences, and treating well-structured experiments that do not succeed as valuable insights rather than wasted endeavours. This mindset is foundational to cultivating an innovative culture within the squad.
A Comprehensive Six-Week Squad Challenge
Objective: Establish a dedicated six-week, cross-functional squad to address a specific, clearly defined customer friction point. Select a problem that is visible and meaningful, but also manageable within the given timeframe. Examples include customers abandoning online forms because they’re too complex, long wait times for customer support responses, difficulty finding essential information on the website, or the frustration of repeating the same information to multiple staff members.
Week 1: Define and Analyse the Problem
In the first week, the squad’s primary focus will be to articulate the customer problem clearly. This involves collaborating to define the issue precisely, ensuring all squad members share the same understanding. Establish a baseline metric to quantify the problem, such as the percentage of customers who abandon a form. Furthermore, map the end-to-end customer journey to visualise all touchpoints and interactions. Clarify decision rights within the squad to streamline decision-making and ensure accountability. Finally, agree on a working rhythm that includes regular check-ins and updates to maintain momentum and alignment throughout the challenge.
Weeks 2 and 3: Gather Insights and Develop Solutions
During weeks 2 and 3, the squad will shift focus to gathering insights from customers and frontline staff. This could involve interviews, surveys, or focus groups to understand customer experiences and pain points better. As insights are collected, the squad will identify the root causes of the friction point, prioritising key assumptions to test. This phase includes brainstorming and designing a limited number of practical experiments to address the identified issues, ensuring proposed solutions are feasible and align with customer needs.
Weeks 4 and 5: Test and Iterate
In weeks four and five, the squad will implement the most promising changes derived from the previous insights and experimentation design. Monitor and review early data to assess the impact of the changes. Throughout this testing phase, the squad should resolve any blockers swiftly to avoid delays. Additionally, the squad should maintain open communication with relevant stakeholders, demonstrating ongoing progress and facilitating feedback, which can be invaluable in refining their approach.
Week 6: Evaluate and Share Learnings
In the final week, the squad will conduct a thorough assessment of the outcomes against the original metric established at the outset. This evaluation will help determine the effectiveness of the solutions implemented and provide concrete insights into what worked well and what did not. Based on these reflections, the squad should craft recommendations for next steps, ensuring a clear path forward for continued improvement. Finally, the squad should document its learnings and share these insights across the organisation, fostering a culture of continuous improvement and collaboration.
Conclusion
The true value of this structured approach extends beyond developing a solution within six weeks. It lays the foundation for an enduring organisational habit: cultivating an environment where teams collaboratively tackle customer problems, make data-informed decisions, learn from their experiences, and embrace collaboration as a critical driver of innovation, rather than a mere abstract concept of leadership. This method fosters a proactive mindset across the organisation, ultimately enhancing customer satisfaction and operational efficiency.
This Post is 10/20. Tomorrow’s post will be: Beyond Your Walls: How Open Innovation Accelerates Business Growth
