Cross-Functional Agenda Planning

When I was CPO, I was frustrated that I was never meeting wth the right person or teams at the right time. My calendar was packed. Yet the person or team I needed to talk to was always scheduled for at least three days away. The team needs a decision, but you just had a 1:1 and won't meet your engineering partner for another four days. A controversial Product Review happens on a Thursday afternoon, and there isn’t time to get back together before Tuesday AM. I needed to create an operating cadence throughout the week that maximized productivity. After many years, here are some best practices: ➡️ Start the week with calendar review, emails, and logistics to set up the week well. If you have an admin, meet them then. ➡️ Executive team meeting early on Mondays to triage the weekend and the week. Weekly update meetings with teams on Monday afternoons, after the executive leadership meeting. This allows me to bring context, decisions, and asks from the leadership to the teams immediately. ➡️ Tuesdays are for external and cross-functional meetings. Having these meetings after the team and leadership syncs allows me to bring the latest updates and context to my cross-functional peers and externally. ➡️ Wednesday mornings are for large group decision-making meetings. This gives the team time in the week to prepare and have their pre-meetings. It also allows for any necessary follow-up meetings to happen during the same week. ➡️ Thursday is reserved for 1:1s. These are also the most easily moved if urgent, critical meetings come up from earlier in the week. ➡️ Friday is for interviews and org work. There is almost always at least one interview on Friday, and it’s a good time to think about people and culture. ➡️ Friday afternoon is when pre-reads, weekly updates, and any critical context sharing material are due to be emailed out for the meetings the following week. This ensures everyone who attends has the time to review and prepare. Remember, the intent is to try to create themes that allow you to better prepare for meetings and have the right information. When the week operates on a loose drumbeat, everyone is better able to prepare and have productive conversations. ----- 👋 Hi! I'm Yue. I am a Chief Product and Technology Officer turned Executive Coach. I help women and minority aspiring executives break through to the C-suite. 🚀  🔔 Follow me for more content on coaching, leadership, and career growth.

𝗛𝗼𝘄 𝘁𝗼 𝗕𝗿𝗲𝗮𝗸 𝗗𝗼𝘄𝗻 𝗦𝗶𝗹𝗼𝘀 𝗶𝗻 𝗠𝗲𝗱𝗧𝗲𝗰𝗵 𝗗𝗲𝘃𝗲𝗹𝗼𝗽𝗺𝗲𝗻𝘁: (𝗖𝗿𝗲𝗮𝘁𝗶𝗻𝗴 𝗰𝗿𝗼𝘀𝘀-𝗳𝘂𝗻𝗰𝘁𝗶𝗼𝗻𝗮𝗹 𝗵𝗮𝗿𝗺𝗼𝗻𝘆 𝘄𝗶𝘁𝗵𝗼𝘂𝘁 𝘁𝗵𝗲 𝗵𝗲𝗮𝗱𝗮𝗰𝗵𝗲𝘀) Ever notice how Quality, R&D, Regulatory and Marketing teams seem to speak completely different languages? This disconnect isn't just frustrating, it's costing your medical device company time, money, and potentially regulatory approval In my personal experience, I've seen how departmental friction can derail even the most promising innovations 𝗧𝗵𝗲 𝗥𝗲𝗮𝗹 𝗖𝗼𝘀𝘁 𝗼𝗳 𝗦𝗶𝗹𝗼𝘀 👉 Delayed submissions and market entry 👉 Regulatory surprises late in development 👉 Documentation rework and compliance gaps 👉 Increased development costs 👉 Team frustration and burnout Here's how to create seamless collaboration across your MedTech organization: 𝗦𝘁𝗲𝗽 𝟭: 𝗘𝘀𝘁𝗮𝗯𝗹𝗶𝘀𝗵 𝗖𝗿𝗼𝘀𝘀-𝗙𝘂𝗻𝗰𝘁𝗶𝗼𝗻𝗮𝗹 𝗚𝗼𝘃𝗲𝗿𝗻𝗮𝗻𝗰𝗲 Create a development council with representatives from Quality, Regulatory, R&D, Manufacturing, Marketing and Clinical. Meet bi-weekly with a structured agenda (top tip keep the minutes to use towards management reviews). 𝗘𝘅𝗮𝗺𝗽𝗹𝗲: A Class II device manufacturer implemented this model and reduced their development timeline by 30%, if not more, by identifying regulatory concerns during concept phase rather than pre-submission. 𝗦𝘁𝗲𝗽 𝟮: 𝗜𝗺𝗽𝗹𝗲𝗺𝗲𝗻𝘁 𝗦𝘁𝗮𝗴𝗲-𝗚𝗮𝘁𝗲 𝗥𝗲𝘃𝗶𝗲𝘄𝘀 𝘄𝗶𝘁𝗵 𝗔𝗹𝗹 𝗦𝘁𝗮𝗸𝗲𝗵𝗼𝗹𝗱𝗲𝗿𝘀 Don't move to the next development phase without formal sign-off from every department. This prevents costly backtracking 𝗘𝘅𝗮𝗺𝗽𝗹𝗲: During a stage-gate review (Design Review), a clinical specialist identified that the intended claims presented by the regulatory team would require further clinical data. By catching this early, the company adjusted their development plan rather than facing a surprise 6-month+ delay come submission time 𝗦𝘁𝗲𝗽 𝟯: 𝗖𝗿𝗲𝗮𝘁𝗲 𝗮 𝗦𝗵𝗮𝗿𝗲𝗱 𝗗𝗲𝘃𝗲𝗹𝗼𝗽𝗺𝗲𝗻𝘁 𝗟𝗮𝗻𝗴𝘂𝗮𝗴𝗲 Develop a glossary of terms that bridges departmental jargon. This prevents miscommunication that leads to rework. 𝗘𝘅𝗮𝗺𝗽𝗹𝗲: One client I worked with created a “MedTech Translation Guide” with input from each department. Not only did it reduce confusion, but it also built mutual respect engineers finally understood what the regulatory team meant by “intended use” and marketers stopped using terms that could trigger a knock on the door by Competent Authorities 𝗧𝗵𝗲 𝗕𝗼𝘁𝘁𝗼𝗺 𝗟𝗶𝗻𝗲? When this is done right, it accelerates development, strengthens compliance, and builds a more engaged team ✅ Faster to market ✅ Fewer compliance surprises ✅ Less internal friction If you're building your next-gen device and struggling with internal disconnects, it’s time to rethink how your teams work 𝘵𝘰𝘨𝘦𝘵𝘩𝘦𝘳 💬 I'd love to hear: How does your team keep cross-functional collaboration on track? #MedTech  #MedicalDevice #ProductDevelopment

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.

Not to ruin your Thursday, but there are about 68 working days left until Jan 1. Unless of course you are one of the psychos doing 996, then you have more days but your thursday is probably already awful. Which means one of two things is happening inside most companies right now: > Everyone is blissfully ignoring 2026 planning. > Or…the CFO/CEO are already sharpening their pencils to hand down growth targets that will make everyone sweat. Here’s the ugly truth: the way most SaaS companies do planning is broken. The usual cycle looks something like this: > The CEO or CFO picks a number to hit some magical valuation. > Sales & Marketing leaders are told, “Here’s your number, go figure it out.” > The number almost always requires growth rates the company has never pulled off before. > Sales & Marketing leaders backload their plans, praying momentum will magically appear. Shockingly…targets are missed, burn is too high, headcount is bloated, and the company ends up cutting back hard. Sound familiar? But it doesn’t have to go this way. Here are 5 ways to avoid it: 1. Flip the Model: Go Bottom-Up Don’t start with top-down fantasy targets. Ask GTM leaders to build a model with their actual budgets. Then ask: > What could accelerate this number? > Could earlier key hires make a difference? > What if you doubled down on a program that’s working? This gets you grounded in reality—and shows you where true upside exists. 2. Bring Everyone to the Table Planning isn’t just a Sales + Marketing exercise. Loop in: > Product → New launches, upsell opportunities, pricing/packaging shifts > Support → Can they handle the volume? How does this impact churn? > People/HR → Can you even hire fast enough to support the plan? Cross-functional input prevents “surprise problems” that derail execution later. 3. Ask the Hard Questions (Nobody Does This Enough) If your plan assumes everything goes right, you’re already screwed. Push your team: > What’s the worst-case scenario? > What are the biggest risks? > What’s keeping you up at night about this plan? A little paranoia early saves a ton of pain later. 4. Don’t Obsess Over Net-New Logos Spend as much time modeling revenue expansion from current customers as you do on acquisition. Upsell, cross-sell, reduce churn, those levers compound faster than chasing shiny new logos. 5. Remember the Human Factor A realistic model = better team morale, clearer board expectations, and tighter alignment. When people feel like the targets are achievable, execution improves. When they know they’re running at a brick wall? Burnout, misalignment, and attrition follow. Don’t let 2026 planning be another round of miss big, cut hard. You’ve got 68 working days to get this right.

How I run larger cross-functional meetings as Chief of Staff at a company that is moving fast: 1) Align with execs before the meeting. Quick 1:1's or async slack alignment. The goal is clarity on what we’re solving for. (Earlier in my career, I avoided this; I didn’t want to waste their time. But skipping it made the meeting less efficient every time because we would burn the first 10 minutes getting on the same page) 2) Send a pre-read 24–48 hours in advance. Include: – Agenda – Materials to review – Decisions or asks The more specific, the better. 3) Use meeting time for decisions, not updates. This isn’t a meeting to go line-by-line through your status doc. If the goal is just updates, you can just send a doc. This live time is for discussion! Unblocking, prioritizing, or choosing a path. 4) Turn on AI notes. I use Google Gemini so I can stay off my keyboard and pay attention to the room. 5) Ask for deadlines. People hesitate or avoid this point because they don’t want to seem like they’re assigning work. But without dates, there is more room for confusion. Push for clarity while the room is still full. 6) Send a recap within 24 hours. AI drafts it, I edit and send. Keep it short: what got decided, who’s doing what, by when. As you can see, most of the work should happen before the meeting. In the room, my job is to keep us from drifting. I'm curious though, what do you do before a meeting to make sure it’s worth holding?

→ 𝐇𝐨𝐰 𝐈 𝐀𝐥𝐢𝐠𝐧 𝐂𝐫𝐨𝐬𝐬-𝐅𝐮𝐧𝐜𝐭𝐢𝐨𝐧𝐚𝐥 𝐓𝐞𝐚𝐦𝐬 𝐀𝐫𝐨𝐮𝐧𝐝 𝐎𝐧𝐞 𝐒𝐡𝐚𝐫𝐞𝐝 𝐆𝐨𝐚𝐥 𝐎𝐧𝐞 𝐆𝐨𝐚𝐥. 𝐌𝐚𝐧𝐲 𝐓𝐞𝐚𝐦𝐬. In a multi-squad setup, alignment isn’t automatic, it’s designed. 🔹 𝐒𝐭𝐞𝐩 1: 𝐒𝐭𝐚𝐫𝐭 𝐰𝐢𝐭𝐡 𝐭𝐡𝐞 “𝐖𝐡𝐲” Every sprint kickoff begins with the outcome, not the output. I ensure every team knows why their work matters to the bigger picture. 🔹 𝐒𝐭𝐞𝐩 2: 𝐂𝐫𝐞𝐚𝐭𝐞 𝐚 𝐒𝐡𝐚𝐫𝐞𝐝 𝐕𝐢𝐬𝐢𝐨𝐧 𝐁𝐨𝐚𝐫𝐝 A visual roadmap connects business goals → epics → sprint deliverables. No confusion. Just context. 🔹 𝐒𝐭𝐞𝐩 3: 𝐃𝐞𝐟𝐢𝐧𝐞 𝐎𝐰𝐧𝐞𝐫𝐬𝐡𝐢𝐩 𝐂𝐥𝐞𝐚𝐫𝐥𝐲 Each squad owns a specific value stream, not random tasks. This reduces overlap and accountability gaps. 🔹 𝐒𝐭𝐞𝐩 4: 𝐒𝐲𝐧𝐜 𝐓𝐡𝐫𝐨𝐮𝐠𝐡 𝐑𝐢𝐭𝐮𝐚𝐥𝐬 Weekly syncs are not status meetings - they’re alignment forums. We discuss dependencies, blockers, and cross-squad priorities. 🔹 𝐒𝐭𝐞𝐩 5: 𝐌𝐞𝐚𝐬𝐮𝐫𝐞 𝐖𝐡𝐚𝐭 𝐌𝐚𝐭𝐭𝐞𝐫𝐬 Shared KPIs across teams → Shared success mindset. We track impact, not just delivery speed. 𝐑𝐞𝐬𝐮𝐥𝐭? Teams stop working in silos and start delivering in harmony - All rowing toward one shared goal. follow Shraddha Sahu for more insights

Most organisational problems don’t sit inside functions. They sit between them. Sales blames Operations. Operations blames Supply Chain. Support blames Product. And the customer? Gets a delayed, diluted experience. The issue is not capability. It is the failure to manage interface areas. From what I’ve seen, organisations don’t break due to weak teams; they break due to weak handoffs. 👉 Work doesn’t fail in silos 👉 It fails in transitions What poor interface management looks like: • “This is not my responsibility” • “We didn’t get complete information” • “They didn’t respond on time” 👉 Result: Delays, rework, frustration Practical tools to fix it: 1. Define Clear “Handover Points” Document: • What is handed over • In what format • By when 👉 Clarity eliminates friction 2. Interface SLAs (Service Levels) Set: • Response time • Turnaround time 👉 Makes interdependence measurable 3. Joint Accountability (Not Just Functional) For key outcomes, assign: 👉 Shared ownership across functions 👉 Breaks the “us vs them” mindset 4. Weekly Cross-Functional Sync (30 mins) Focus only on: • Bottlenecks • Delays • Dependencies 👉 Solve before escalation 5. “One View” Dashboard Track end-to-end flow: 👉 From start → handover → completion 👉 Visibility across functions builds alignment 6. Escalation Clarity Define: • When to escalate • To whom 👉 Prevents silent delays 👉 Average organisations optimise functions 👉 Strong organisations align functions 👉 High-performing organisations manage interfaces seamlessly Excellence is not built in silos. It is built at the intersections. 👉 Tell me your view : Where is your biggest delay—within a function or between functions? #LeadershipEssentials #CrossFunctional #ExecutionExcellence #Collaboration #Management #OrganisationalEffectiveness

A Plant Head plays a key role in eliminating this gap and creating "One Team – One Goal". Let me elaborate step by step: 1. Define and Communicate a Clear Common Goal The Plant Head must articulate one unifying objective (e.g., “95% Mill Availability with 0 Safety Incidents, On-time Delivery, and Minimum Rework”). Translate high-level KPIs into department-wise contributions: Production: throughput, yield Maintenance: MTTR, MTBF, availability Quality: defect %, customer complaints Logistics: on-time dispatch Utilities: uninterrupted power, water, hydraulics Everyone must see how their role impacts the same target, not just their silo. 2. Break Down Silos with Cross-Functional Platforms Daily Joint Review (Production + Maintenance + Quality + Utilities) for hot issues – max 15 minutes “stand-up” style. Weekly Plant Coordination Meeting chaired by Plant Head where each department reports progress on the same KPIs. Introduce “War Room” concept – one physical or digital dashboard displaying all departments’ performance toward the common goal. 3. Recognition and Visibility Across Departments Many times, teams don’t even know who contributed to success. Plant Head should: Publicly appreciate inter-departmental support (e.g., “Production target achieved because Maintenance team cut breakdown time and Utilities ensured uninterrupted cooling water”). Rotate recognition: Team of the Month across functions, not just production. 4. Joint Problem-Solving & Kaizen Instead of “Maintenance blaming Production” or “Quality blaming Maintenance,” set up cross-functional problem-solving teams for chronic issues. Use RCA (Root Cause Analysis) with mixed teams → Everyone learns dependencies. 5. Shared Training & Awareness Many people don’t know the role of other departments. Plant Head should organize: Cross-department orientation sessions (e.g., “Day with Maintenance” for production engineers). Training on system thinking – showing how mill output depends on every node. 6. One Plant Culture – Not Departmental Culture Create a cultural shift with slogans, boards, and repeated messaging: “We are not Maintenance / Production / Quality – We are Hot Rolling Mill Team.” Encourage team-building activities, joint safety drives, and inter-departmental contests. 7. Digital Integration Implement a common digital dashboard (Production, Maintenance, Quality, Utilities, Safety). Transparency eliminates “I didn’t know” gaps – everyone sees the same truth in real time. ✅ Summary for Plant Head Action Set one clear goal → Translate into departmental contribution. Establish joint platforms (daily review, weekly coordination). Recognize cross-functional contributions. Build culture of one plant – one team. Leverage digital tools for transparency. Over time, this alignment removes “departmental blindness” and builds a true ownership mindset across the mill. 🙏

Your cross-functional plan is 60 slides. No wonder nobody reads it. It's often confusion dressed up in jargon and PowerPoint. In Pharma, long decks give comfort. (We've all seen those brand plans ...) Lofty ‘Cross-Functional Strategic Imperatives/Objectives’.  Pages of SWOTS and Market Research. Is it any wonder leaders get lost and overwhelmed? Clear plans create clear impact.   When I work with cross-functional teams, we get clear on what’s really needed for success - It starts with one page: 👇 1️⃣ Purpose • One clear objective in plain language • One key patient or HCP outcome 2️⃣ Stakeholder Gaps we want to address • The key pain-points we need to close. • Each move linked to the objective 3️⃣ Measurable roadmap • Clear activities that address those gaps • Clear metrics that demonstrate success. 4️⃣ People + timing • Owner for each move • First key milestone date ⏱️ We then test every new idea against the question: Does it bring us closer to our objective? If not, it goes on a “parking lot” list, not in the plan. Teams get greater clarity, strong alignment, better focus, more progress. Leaders get time back for real strategic thinking. In your team do you jump to solutions first or do you pressure test them against your objectives?

The most powerful growth engine I've ever seen wasn't a brilliant marketing campaign, revolutionary sales approach, or customer success initiative. It was getting all three functions to actually talk to each other. I've watched companies invest millions in sophisticated tech stacks and expert teams, yet still struggle with the basics. Marketing creates leads that sales doesn't want. Sales makes promises customer success can't deliver. And customer success discovers insights that never make it back to marketing. These departmental silos are growth killers. Breaking down these walls doesn't require a complex restructure or expensive technology. It starts with something far more fundamental. Creating shared goals and genuine human connections. Through years of working across different organizations, I've found several approaches that have consistently helped bridge these divides. They're not universal solutions, but they've made a meaningful difference: 1. Unified Metrics That Matter When each department has different success measures, conflict is inevitable. Marketing celebrates lead volume, while sales focuses on deal size, while customer success prioritizes retention. Instead, align around shared metrics like customer lifetime value or revenue from existing customers. 2. Regular Cross-Pollination Nothing builds understanding like walking in someone else's shoes. Create regular opportunities for team members to experience life in other departments: - Have marketers join sales calls - Bring salespeople into customer success reviews - Include customer success in marketing planning sessions 3. The Customer Journey Council Establish a cross-functional team with representatives from each department that meets regularly to discuss specific customer experiences. Review actual customer journeys, identify gaps, and collectively solve problems. 4. Shared Celebration Rituals Create traditions that celebrate cross-functional wins, not just departmental victories. When a customer renews and expands their contract, that's a win for the entire revenue team. 5. Language Matters Pay attention to how people talk about other departments. Replace "they don't understand what we need" with "we haven't effectively communicated our needs." This subtle shift transforms blame into responsibility. Breaking down silos creates a fundamentally better customer experience. When all revenue functions work as one team, customers feel understood, supported, and valued throughout their entire journey. What's one step you've taken to improve cross-functional collaboration in your organization? --- This cross-functional approach guides my work as an on-demand CMO. I help growth-focused leaders build marketing strategies that align seamlessly with sales and customer success goals. If you're looking to transform siloed departments into a unified revenue engine, let's connect.