Cross-Functional Productivity

"Marketing bolse eta banate hobe" is not a brief. If you’ve worked cross-functionally, you’ve heard some version of this. A request is passed along word-for-word, with no added context. But just acting as a courier rarely moves work forward. What actually helps is connecting the dots. For example – let’s say Marketing asks Sales for a new report. If you just pass the line “Marketing wants this,” Sales has no reason to treat it seriously. But if you add: Context: “Marketing wants to understand which channels are underperforming.” Impact: “Without this, we risk overspending next month.” Success: “The report should show conversion by channel, weekly.” Options: “We could start with last 3 months’ data only, or run the full year – here’s the trade-off.” When: “Needed by next Monday for the budget review.” Now the other team knows why it matters, what’s at stake, and how to help. If you’re on the receiving end, don’t accept vague asks either. Push back gently: “What’s the risk if this doesn’t get done? What’s the main outcome you need from this?” That not only protects your priorities, but also forces the person asking to frame the impact clearly. Authority can push. But clarity pulls. Have you seen “courier-style” requests in your org – and how did you handle them? #Collaboration #Leadership #Productivity #WorkingBetter

A common partnership snafu is that companies want partnership success, but don’t provide the resources to get there. I heard of a case where a whole marketing team quit, the partnerships team was given no marketing support, and they didn't yet have an integration with product -- and yet, the CEO expected the partnership strategy to deliver instant revenue. Wild. But not uncommon. Partnerships can't thrive in a vacuum. They need cross-functional support—marketing, product integration, sales enablement—all aligned to succeed. Before you set revenue targets for your partnerships, ask yourself: Do we have the resources to support them? If the answer is no, you have to help your leadership teams to reconsider their expectations. To help create the cross-functional support needed for partnerships to thrive, here are four strategies: 1. Involve Cross-Functional Leaders from the Very Beginning Bring key leaders from marketing, sales, and product into the partnership planning phase. Early involvement gives them a sense of ownership and ensures they understand how partnerships align with their own goals. Strategy: Schedule a kick-off meeting with stakeholders from each relevant department. Create a shared roadmap that outlines how partnerships will impact each team and their specific contributions. 2. Tie Partnership Success to Department KPIs To gain buy-in, tie partnership goals directly to the KPIs of each department. Aligning partnership outcomes with what each team is measured on ensures they have skin in the game. Strategy: During planning sessions, ask each department head how partnerships can contribute to their targets. Build specific KPIs for each function into the overall partnership strategy. 3. Create a Resource Exchange Agreement Formalize the support needed from each department with a resource exchange agreement. This sets clear expectations on what each function will contribute—whether it's a dedicated product team member for integrations or marketing resources for co-branded campaigns. It turns vague promises into commitments. Strategy: Draft a simple document that outlines the roles, responsibilities, and deliverables each team will provide, then get sign-off from department heads and the executive team. 4. Demonstrate Early Wins for Buy-In Quick wins go a long way toward securing ongoing resources. Identify a small pilot project with an internal team that shows immediate impact. Whether it's a small co-marketing campaign or a limited integration, these early successes build momentum and demonstrate the value of supporting partnerships. Strategy: Select one or two partners to run a pilot with, focused on delivering measurable outcomes like leads generated or product adoption. Use this success story to demonstrate value to other departments and secure further commitment. Partnership success requires cross-functional alignment. Because partnerships don’t happen in a silo.

Over the years, I've discovered the truth: Game-changing products won't succeed unless they have a unified vision across sales, marketing, and product teams. When these key functions pull in different directions, it's a death knell for go-to-market execution. Without alignment on positioning and buyer messaging, we fail to communicate value and create disjointed experiences. So, how do I foster collaboration across these functions? 1) Set shared goals and incentivize unity towards that North Star metric, be it revenue, activations, or retention. 2) Encourage team members to work closely together, building empathy rather than skepticism of other groups' intentions and contributions. 3) Regularly conduct cross-functional roadmapping sessions to cascade priorities across departments and highlight dependencies. 4) Create an environment where teams can constructively debate assumptions and strategies without politics or blame. 5) Provide clarity for sales on target personas and value propositions to equip them for deal conversations. 6) Involve all functions early in establishing positioning and messaging frameworks. Co-create when possible. By rallying together around customers’ needs, we block and tackle as one team towards product-market fit. The magic truly happens when teams unite towards a shared mission to delight users!

The CEO's voice crackled with anxiety over the video call. "𝑾𝒆 𝒏𝒆𝒆𝒅 𝒂𝒏𝒐𝒕𝒉𝒆𝒓 𝒔𝒕𝒓𝒂𝒕𝒆𝒈𝒚 𝒔𝒆𝒔𝒔𝒊𝒐𝒏. 𝑵𝒐𝒘." I sighed inwardly. Our 3rd emergency meeting in 11 weeks. 𝐀 𝐩𝐫𝐨𝐦𝐢𝐬𝐢𝐧𝐠 𝐛𝐮𝐬𝐢𝐧𝐞𝐬𝐬, 𝐩𝐚𝐫𝐚𝐥𝐲𝐬𝐞𝐝 𝐛𝐲 𝐢𝐭𝐬 𝐥𝐞𝐚𝐝𝐞𝐫'𝐬 𝐚𝐧𝐱𝐢𝐞𝐭𝐲. The pattern was clear: ↪ Market shift triggers uncertainty in business model ↪ Anxious CEO calls for full strategy overhaul ↪ Team scrambles to re-plan everything ↪ Brief illusion of control ↪ New market shift.  ↪ Rinse. Repeat. The CPO was frustrated: "𝑾𝒆'𝒓𝒆 𝒅𝒓𝒐𝒘𝒏𝒊𝒏𝒈 𝒊𝒏 𝒓𝒆𝒘𝒐𝒓𝒌." The CSO was exasperated: "𝑵𝒐𝒕 𝒂𝒏𝒐𝒕𝒉𝒆𝒓 𝒘𝒐𝒓𝒌𝒔𝒉𝒐𝒑..." Innovation stalled. Base business thudded. The team was burning out. My role as advisor? 𝐓𝐮𝐫𝐧 𝐭𝐡𝐢𝐬 𝐚𝐧𝐱𝐢𝐞𝐭𝐲 𝐥𝐨𝐨𝐩 𝐢𝐧𝐭𝐨 𝐚 𝐠𝐫𝐨𝐰𝐭𝐡 𝐞𝐧𝐠𝐢𝐧𝐞. Inspired by an aha moment in my morning walk, I posed a question. "𝐖𝐡𝐚𝐭 𝐢𝐟 𝐲𝐨𝐮𝐫 𝐚𝐝𝐚𝐩𝐭𝐚𝐛𝐢𝐥𝐢𝐭𝐲 𝐭𝐨 𝐜𝐡𝐚𝐧𝐠𝐞 𝐰𝐚𝐬 𝐲𝐨𝐮𝐫 𝐮𝐧𝐟𝐚𝐢𝐫 𝐚𝐝𝐯𝐚𝐧𝐭𝐚𝐠𝐞?" Confused looks all around, but I also saw a glimmer of intrigue. 🧠 𝐎𝐮𝐫 𝐍𝐞𝐰 𝐅𝐫𝐚𝐦𝐞𝐰𝐨𝐫𝐤: • Embrace uncertainty as a catalyst for innovation • Replace rigid plans with adaptive strategies • Cultivate team resilience over leader omniscience 🛠️ 𝐏𝐫𝐚𝐜𝐭𝐢𝐜𝐚𝐥 𝐒𝐭𝐞𝐩𝐬 𝐖𝐞 𝐈𝐦𝐩𝐥𝐞𝐦𝐞𝐧𝐭𝐞𝐝: • Weekly "uncertainty check-ins" to normalize change • Rapid prototyping instead of endless planning • Celebrating adaptive wins, not just meeting targets 👏 𝐓𝐡𝐞 𝐑𝐞𝐬𝐮𝐥𝐭𝐬 • Endless strategy sessions cut by 70% • Two major product launches in 6 months • CEO anxiety noticeably lowered • Team cohesion and creativity skyrocketed 𝐓𝐡𝐞 𝐋𝐞𝐬𝐬𝐨𝐧: 𝐀𝐧𝐱𝐢𝐞𝐭𝐲 𝐭𝐡𝐫𝐢𝐯𝐞𝐬 𝐨𝐧 𝐭𝐡𝐞 𝐢𝐥𝐥𝐮𝐬𝐢𝐨𝐧 𝐨𝐟 𝐜𝐨𝐧𝐭𝐫𝐨𝐥. 𝐓𝐫𝐮𝐞 𝐥𝐞𝐚𝐝𝐞𝐫𝐬𝐡𝐢𝐩 𝐢𝐬 𝐚𝐛𝐨𝐮𝐭 𝐚𝐝𝐚𝐩𝐭𝐢𝐧𝐠 𝐭𝐨 𝐮𝐧𝐜𝐞𝐫𝐭𝐚𝐢𝐧𝐭𝐲, 𝐧𝐨𝐭 𝐞𝐥𝐢𝐦𝐢𝐧𝐚𝐭𝐢𝐧𝐠 𝐢𝐭. 𝐘𝐨𝐮𝐫 𝐓𝐮𝐫𝐧: What leadership anxiety can you transform into the rocket fuel of adaptability? Photo: me recreating my face when hit by the Anxiety♻️Adaptability aha that morning! #Entreprenurship #Anxiety #AdaptiveLeadership #Transformation #EmotionalIntelligence

✈️What If Everyone in Aviation Understood How the Business Works? (Why cross-functional learning is the industry's untapped advantage) In aviation, we don't wait for turbulence to inspect the wings, so why wait until performance dips to invest in cross-functional learning? What would change? Silos dissolve. Innovation accelerates. Decisions align with strategy, and performance improves. Across airlines, airports, and aviation authorities, organizational development is evolving rapidly, moving beyond mere regulatory compliance and senior management development. Forward-thinking organizations build business fluency at every level, from executives to pilots, cabin crew, ground ops, airport teams, and regulators. Here's what leading aviation organizations are prioritizing in 2025: 🧠 Cross-functional business literacy When ground ops understand commercial strategy, cabin crew grasp safety analytics, pilots understand network economics, airport staff understand turnaround economics, and regulators understand commercial pressures, silos dissolve. Innovation emerges. Frontline staff make better decisions, spot opportunities, and drive results. 🔧 Learning grounded in real challenges Practical training mirrors complexity: optimizing networks when ops, commercial, and sustainability priorities conflict. Or recovering from disruptions requiring real-time coordination. People build judgment and problem-solving capability, not just knowledge. 🌐 Accessible, flexible learning formats Digital learning, asynchronous modules, and virtual cohorts enable cross-functional teams to learn together, breaking barriers of time, location, and hierarchy. 🤝 Breaking organizational and sectoral silos When airline managers, airport teams, ground handlers, and regulators learn together, shared language, empathy, and lasting networks emerge. This is culture-building and collaboration at scale. 𝗪𝗵𝘆 𝗶𝘀 𝘁𝗵𝗶𝘀 𝗮𝘃𝗶𝗮𝘁𝗶𝗼𝗻'𝘀 𝘂𝗻𝘁𝗮𝗽𝗽𝗲𝗱 𝗮𝗱𝘃𝗮𝗻𝘁𝗮𝗴𝗲? Most organizations still treat training as function-specific or compliance-driven. Cross-functional literacy remains rare, yet it's one of the few tools that improves performance before crises, not after. In aviation's interdependent ecosystem, shared understanding builds trust, accelerates innovation, reduces risk, and creates lasting resilience. That's why organizations investing here aren't just building capability, they're building strategic differentiation. This isn't theory. In 15+ years teaching aviation business management to everyone from airline executives and network planners to pilots, cabin crew, airport teams, legal, and regulators, I've witnessed a consistent pattern: organizations investing in cross-functional learning build resilience, culture, and competitive advantage that lasts. Is your organization's training building business fluency across all levels or leaving capability on the table? #Air52Insights #Aviation #AirlineManagement #OrganizationalDevelopment

What do you do with a customer who asks for a new feature… every single month? Not bugs. Not onboarding help. I’m talking about ongoing enhancement requests, complex edge-case use cases, and one-off "must-haves" that somehow become your team's priority. You’ve probably seen it: – The team is constantly escalating their asks – Product is getting pulled into one-off builds – The customer renews, but your roadmap suffers – And the CS team feels stuck between being helpful and being used Here’s the uncomfortable truth I had to face as a CS leader: If you don’t draw a line, these requests will shape your product and your burnout. So we made a shift: Every enhancement request now goes through a filter: Is this core to our product vision? Or is this custom work? If it’s custom, we scope it and price it. Not to upsell. To separate real business needs from “it would be nice if…” We even productized it. In QBRs, we walk in with a menu of paid engagements: advanced integrations, roadmap accelerators, and custom reports. The conversation changes when the customer sees: 1. We take their need seriously 2. We have a structured way to support it 3. It comes with investment and clarity Not everything should be free. Not everything should be built. Some requests are actually an opportunity for revenue, for partnership, and for focus. What’s your move when feature requests get out of hand? Do you price them? Or absorb them quietly?

It feels natural to put your function first. It’s also what holds organizations back. Leaders invest deeply in the teams that report to them—coaching, advocating, delivering wins. But they often overlook the team they lead with. Here’s the shift that separates good managers from enterprise leaders: → Your peer leadership team is your first team → Your function is your second This isn’t about abandoning your function. It’s about realizing you serve it better when you act in the best interest of the whole business. And this mindset isn’t reserved for execs. If you lead people, it applies to you. So why do so many leaders default to function-first? Because it’s where they came up. It’s where they feel most accountable. It’s where wins—and promotions—tend to show up on paper. But function-first thinking creates ripple effects: → Turf battles → Conflicting priorities → Slower collaboration → Fragmented trust First-team leadership flips that: → Shared ownership → Aligned decisions → Real execution power How do you make the shift? → Redefine success. Don’t just track your function’s wins. Ask: Did we help move the company forward this week? → Share context. Help your team see the pressures and priorities across functions—not just their own. → Model trade-offs. Make your cross-functional decisions visible—especially when they benefit the company more than your department. If you lead a team of leaders, make sure your incentives support the culture you want. People follow incentives, even when you say otherwise. You can’t say “collaborate” and reward silo wins. To reinforce a first-team culture: → Tie part of bonuses or MBOs to shared leadership outcomes → Recognize integrators, not just individual performers → Make it easier to collaborate than compete (tools, meetings, forums) Then layer in behavior: → Shared goals → Cross-functional accountability → Regular reflection: What did we do this week to help the business—not just our team—succeed? When your leaders start acting like stewards of the business—not just heads of functions—alignment, execution, and trust all get easier. The org stops behaving like a collection of departments. It starts operating as a team of teams. Want to try this? Open your next leadership meeting with this question: “If we were truly operating as a first team, what would we do differently today?” Watch how quickly the conversation shifts. #Leadership #Execution #TeamOfTeams #OrgDesign #CrossFunctional #FirstTeamMindset

Sales closes the deal. CS gets handed the mess. That's not a people problem — it's a design problem. And it's exactly why so many companies are leaving NRR on the table. When sales gets paid on ARR and CS gets measured on retention, you've built two teams optimizing for different finish lines. Someone will lose. It's usually the customer. Here's how to actually fix it: 1. Put NRR on both scorecards. CS shouldn't carry NRR alone. When sales has skin in the retention game — even partial weighting — bad-fit deals stop looking attractive. Start with a clawback on churn within the first 90 days. It changes behavior fast. 2. Build a formal handoff protocol. Not an email. A structured process. Before a deal closes, CS should know the customer's stated goals, the promises made during the sale, and any red flags that surfaced. That information shouldn't live in a Slack thread — it should be in the CRM, every time. 3. Define expansion ownership before you need it. Upsell motion without clear ownership is just hope. Decide in advance: who identifies the signal, who leads the conversation, and how credit is shared. Document it. Comp it. 4. Build a comp structure that reflects the full revenue lifecycle. Sales quota on new ARR only is a half-finished incentive model. Consider: clawbacks tied to early churn, co-sell bonuses when sales and CS close expansion together, and CSM variable comp tied to NRR — not just CSAT. When the money moves, behavior follows. If your comp plan doesn't reward retention, don't be surprised when no one prioritizes it. 5. Align on deal quality metrics — and make them visible. Track time-to-value and 90-day retention by rep. Put it in the same place leadership reviews pipeline. Sales leaders who see deal quality data attached to their team's name start caring about fit — fast. 6. Speak one health language. If sales is calling an account hot while CS has it flagged red, you don't have an alignment problem — you have an information problem. Shared health scoring tied to real product adoption data closes that gap before it becomes a churn event. The companies winning on NRR aren't doing it because CS is exceptional in a vacuum. They built a revenue structure where both teams are playing the same game — with a comp plan that proves it. Alignment isn't a feeling. It's a compensation model, a shared dashboard, and a conversation that happens before the contract is signed. Operationalizing toward scalable + predictable outcomes = winning at revenue metrics that matter (eg. cost to serve, NRR, CLTV) Rebels of SaaS™️ #customersuccess #leadership

Leaders, if you think your company is growth-focused, ask yourself one uncomfortable question 👇🏽 Are you really building growth, or are you only pushing sales? I say this cuz in many companies, sales gets the spotlight, while execution, quality, planning, HR, and finance get pressure. And the moment that balance goes, growth may still look good from the front, but it starts weakening from inside. When management gives most of its time and seriousness to one function, the rest of the organisation starts carrying pressure without equal support. This is what it usually looks like in real life: ↳ sales closes faster than operations can deliver ↳ capacity is not checked properly before new orders are pushed in ↳ execution teams are not asked enough whether commitments are actually deliverable ↳ customers get vague or over-ambitious promises on delivery or technical capability ↳ planning keeps getting disturbed ↳ quality starts getting squeezed ↳ HR keeps handling burnout instead of building capacity ↳ management spends more time pushing orders in than making delivery stronger And that is where the real problem begins: late deliveries increase, teams stay stressed, coordination weakens, margin starts leaking quietly, and customer trust becomes harder to hold. The top line may look fine for some time, but the system underneath starts losing strength. The best example of this, in an extreme way, was Wells Fargo. Sales pressure became so dominant that controls and culture got compromised. That is what happens when one function starts overpowering the whole system. That is why I believe management should do 9 things differently: 1) review sales, execution, quality, HR & finance with equal seriousness 2) check real capacity before pushing aggressive order targets 3) take execution input before making customer commitments 4) align commitments with actual delivery capability 5) avoid vague promises on delivery timelines or technical feasibility 6) make execution & people metrics as visible as sales metrics 7) stop rewarding order inflow without delivery health 8) strengthen HR before the people problem becomes urgent 9) treat cross-functional balance as a management responsibility, not a departmental issue That is where the difference starts showing. Cuz when management gives equal seriousness to the full chain, growth becomes: ↳ more stable ↳ more deliverable ↳ more sustainable And when growth becomes all 3, it stops being only a sales achievement. It becomes an organisational strength. #businessgrowth #crossfunctionalalignment #salesexecution #organizationalperformance #growthmanagement #businessoperations #sustainablegrowth

💡 "𝐓𝐡𝐞𝐫𝐞 𝐢𝐬 𝐧𝐨 𝐰𝐨𝐫𝐥𝐝, 𝐭𝐡𝐞𝐫𝐞 𝐚𝐫𝐞 𝐨𝐧𝐥𝐲 𝐬𝐢𝐱 𝐛𝐢𝐥𝐥𝐢𝐨𝐧 𝐮𝐧𝐝𝐞𝐫𝐬𝐭𝐚𝐧𝐝𝐢𝐧𝐠𝐬 𝐨𝐟 𝐢𝐭." The same applies to #projects. When you bring people together from different functions, countries, with different roles and perceptions, the chances of misunderstandings and miscommunication are super high. Last week, I co-facilitated a 𝟐-𝐝𝐚𝐲 𝐎𝐩𝐩𝐨𝐫𝐭𝐮𝐧𝐢𝐭𝐲 𝐅𝐫𝐚𝐦𝐢𝐧𝐠 𝐖𝐨𝐫𝐤𝐬𝐡𝐨𝐩 with my colleague and coach from Australia Neil Maxfield. The team we worked with was dealing with a highly complex situation: - Different perspectives - Misaligned priorities - Competing assumptions But guess what? We had a full toolkit for tackling complex problems, and one of the tools that stood out was the 𝐃𝐞𝐜𝐢𝐬𝐢𝐨𝐧 𝐇𝐢𝐞𝐫𝐚𝐫𝐜𝐡𝐲. 𝐖𝐡𝐚𝐭 𝐢𝐬 𝐭𝐡𝐞 𝐃𝐞𝐜𝐢𝐬𝐢𝐨𝐧 𝐇𝐢𝐞𝐫𝐚𝐫𝐜𝐡𝐲? It’s a tool that helps distinguish between: - Past decisions (constraints and givens) - Future decisions (choices and possibilities). Instead of rushing to solutions, it encourages teams to pause, break apart what they "think they know," and organize their approach to the problem. 𝐇𝐞𝐫𝐞’𝐬 𝐡𝐨𝐰 𝐰𝐞 𝐮𝐬𝐞𝐝 𝐢𝐭: - Identified issues: Teams explored what wasn’t working in each problem area. - Analyzed impact: Teams prioritized high-value issues and assessed how they affected plant performance. - Clarified decisions: Team distinguished between constraints, available choices, and future decisions. - Defined success: For each problem area, we defined success measures, scope, value drivers, and overall objectives. Then, brainstorming solutions became far more effective: - Solutions were specific and directly linked to problem areas. - The team evaluated each solution against key drivers to ensure alignment with the project’s scope and boundaries. The result? Clarity, shared understanding and alignment—no matter the differences in roles or perspectives. 𝐓𝐡𝐞 𝐥𝐞𝐬𝐬𝐨𝐧? Far too often, we rush into "fixing" things without fully understanding: - What’s broken? - What’s the real impact? - What do we actually want to achieve? Tools like the Decision Hierarchy and a well-structured framing process help bring clarity and alignment before diving into solutions. 👉 What strategies do you use to align cross-functional teams? Let’s share insights in the comments! #opportunityframing #decisionhierarchy