Building Productive Teams

𝗠𝗼𝘀𝘁 𝗚𝗖𝘀 𝗧𝗵𝗶𝗻𝗸 𝘁𝗵𝗲 𝗖-𝗦𝘂𝗶𝘁𝗲 𝗝𝘂𝘀𝘁 𝗪𝗮𝗻𝘁 𝗟𝗲𝗴𝗮𝗹 𝗔𝗱𝘃𝗶𝗰𝗲 They're wrong. This is what they actually expect… For years, I’ve asked my C-suite peers this question: "𝗛𝗼𝘄 𝗰𝗮𝗻 𝗜, 𝗮𝗻𝗱 𝘁𝗵𝗲 𝗹𝗲𝗴𝗮𝗹 𝘁𝗲𝗮𝗺, 𝗮𝗰𝘁𝘂𝗮𝗹𝗹𝘆 𝗺𝗮𝗸𝗲 𝘆𝗼𝘂𝗿 𝗷𝗼𝗯 𝗲𝗮𝘀𝗶𝗲𝗿?" The answers surprised me. They didn’t want more memos. They didn’t want more case law. Here’s what I’ve learned they wanted me to do: 1/ 𝗖𝗵𝗶𝗲𝗳 𝗘𝘅𝗲𝗰𝘂𝘁𝗶𝘃𝗲 𝗢𝗳𝗳𝗶𝗰𝗲𝗿 ⤷ Align advice with vision and growth goals ⤷ Turn complexity into clarity under pressure ⤷ Tell hard truths, even when they sting ⤷ Spot risks before they hit the business ⤷ Command respect in the boardroom 2/ 𝗖𝗵𝗶𝗲𝗳 𝗙𝗶𝗻𝗮𝗻𝗰𝗶𝗮𝗹 𝗢𝗳𝗳𝗶𝗰𝗲𝗿 ⤷ Eliminate financial surprises from litigation or fines ⤷ Impose fiscal discipline on the legal budget ⤷ Tie legal risk to cost, revenue, valuation ⤷ Control outside counsel spend with predictability ⤷ Support deals, M&A, and capital readiness 3/ 𝗖𝗵𝗶𝗲𝗳 𝗢𝗽𝗲𝗿𝗮𝘁𝗶𝗻𝗴 𝗢𝗳𝗳𝗶𝗰𝗲𝗿 ⤷ Keep operations moving with pragmatic solutions ⤷ Strip friction from contracts and approvals ⤷ Spot supply chain and delivery risks early ⤷ Escalate only what truly needs attention ⤷ Be a partner in execution, not a bottleneck 4/ 𝗖𝗵𝗶𝗲𝗳 𝗥𝗲𝘃𝗲𝗻𝘂𝗲 𝗢𝗳𝗳𝗶𝗰𝗲𝗿 ⤷ Accelerate deals while managing legal risk ⤷ Flag contract and regulatory landmines early ⤷ Build flexible contracts and sales playbooks ⤷ Align legal with go-to-market strategy ⤷ Safeguard trust with customers and partners 5/ 𝗖𝗵𝗶𝗲𝗳 𝗧𝗲𝗰𝗵𝗻𝗼𝗹𝗼𝗴𝘆 𝗢𝗳𝗳𝗶𝗰𝗲𝗿 ⤷ Speak fluently on IP, data, AI, cybersecurity ⤷ Clear legal paths that enable innovation ⤷ Keep tech roadmaps regulatory-ready ⤷ Move fast on digital transformation contracts ⤷ Lead crisis playbooks for breaches or disputes 6/ 𝗖𝗵𝗶𝗲𝗳 𝗛𝘂𝗺𝗮𝗻 𝗥𝗲𝘀𝗼𝘂𝗿𝗰𝗲𝘀 𝗢𝗳𝗳𝗶𝗰𝗲𝗿 ⤷ Design people-first compliance policies ⤷ Show judgment in sensitive HR matters ⤷ Balance risk while enabling initiatives ⤷ Reinforce ethics and company values ⤷ Guide the board on succession and compensation The lesson? GCs who only give advice stay invisible. GCs who remove barriers become indispensable. Too many stay in the “advice bubble.” The few who break out? They amplify the entire C-suite. Here’s my challenge to you: Ask your execs what they really need. Then deliver. That’s how legal stops being “support”… …and starts being 𝘀𝘁𝗿𝗮𝘁𝗲𝗴𝗶𝗰. 𝗣.𝗦. This is what I have derived from my conversations. 𝗪𝗵𝗮𝘁 𝘄𝗼𝘂𝗹𝗱 𝘆𝗼𝘂 𝗮𝗱𝗱 𝘁𝗼 𝘁𝗵𝗶𝘀 𝗹𝗶𝘀𝘁? ♻️ Like and Repost to help other lawyers grow. 🔔 Follow Adrian Moffatt for more in-house insights. #Leadership #GeneralCounsel #CSuite #inhousecounsel

I used to train budtenders to increase average basket size. Then I realized I was training them to lose customers. Three months ago, I sat in on a transaction that changed the game: Our "top performer" convinced a first-time customer to buy a $60 eighth when they came in for a $15 pre-roll. The numbers looked great. The customer never came back. Meanwhile, our "underperformer" spent 10 minutes educating a nervous newcomer, recommended a single $10 gummy to start, and earned a customer who now visits twice a week. The difference wasn't sales skills. It was relationship skills. I rebuilt our training from the ground up: - Always suggest the premium option → Match products to actual needs  - Add-on at every transaction → Educate for the customer's journey  - Maximize today's ticket → Build tomorrow's regular Instead of only focusing on upselling techniques, we added on customer education. Instead of pushing premium products, we taught needs assessment. Results after 90 days: Average ticket increased 8%. Customer retention increased 34%. At C3 Industries, we train budtenders to be educators, not salespeople. Your team's performance isn't measured in today's transactions. It's measured in tomorrow's relationships. Stop training for the transaction. Start training for the customer. #BudtenderTraining #CannabisEducation #RetailDevelopment 

SOME leaders got it ALL WRONG 🔥 Perks like pizza and bean bags? Cool, but they’re not what keeps people invested. The real glue is respect, fairness, and opportunity - the kind of fundamentals that build culture, not just vibes. 1. Respect and Fairness • Let them be heard: Make space for voices. When people feel seen, trust grows. • Keep it real: Recognition should be earned, not handed out like party favours. Reward merit - it’s what keeps the culture honest. 2. Opportunities That Matter • Growth isn’t optional: People need to see a way forward. Create space for them to level up in skills and responsibility. • Access for all: Don’t gatekeep. Give everyone the same shot to thrive. 3. Pay What They’re Worth • Respect their value: Competitive pay isn’t a bonus - it’s the baseline. Undervalue people, and you lose them. 4. Balance is Power • Flexibility is the future: Time is currency. Respect their personal lives as much as their output. • Support > Pressure: Build a culture that lets people take care of themselves without guilt. 5. Well-being is Non-Negotiable • Safety is everything: From mental health to physical spaces, make sure they know they’re protected. 6. Feedback That Hits • Guide, don’t micromanage: Feedback should empower growth, not tick a box. • Open up the floor: Honest conversations build stronger teams. 7. Empowerment Through Trust • Let them own it: Autonomy isn’t just freedom - it’s a vote of confidence in their skills. • Push for bold ideas: Back their risks with resources and belief. 8. Recognition With Depth • Make it personal: A thank-you isn’t enough. Show them you see the real work behind the scenes. • Celebrate like it matters: Forget cookie-cutter celebrations. Honour wins in ways that reflect your team’s energy. The extras are surface-level. The essence is what sticks. When you nail the fundamentals - respect, fairness, and opportunity - you’re not just building a team. You’re building culture. Something real, something lasting. 💡Reno Perry

How ACP (Agent Communication Protocol) Compares to MCP & A2A First, why protocols matter? AI is racing from single-model hacks to fleets of specialized agents. Without a common standard, every integration is costly duct tape. Enter three emerging standards: 𝗠𝗖𝗣 (𝗔𝗻𝘁𝗵𝗿𝗼𝗽𝗶𝗰) • Core goal: Pump extra memory, tools, or RAG into one model • Best when you need: Super-charging a single foundation model 𝗔𝗖𝗣 (𝗟𝗶𝗻𝘂𝘅 𝗙𝗼𝘂𝗻𝗱𝗮𝘁𝗶𝗼𝗻) • Core goal: Let many agents talk across orgs with zero lock-in • Best when you need: Open, multi-vendor ecosystems 𝗔𝟮𝗔 (𝗚𝗼𝗼𝗴𝗹𝗲) • Core goal: Peer-to-peer agents tuned for Google’s stack • Best when you need: Deep GCP alignment and services Now, let's compare them but remember, in most cases they are complementary and not competitive. Think of them as layers in a full-stack agent system 👷♂️ 𝗠𝗖𝗣 𝘃𝘀. 𝗔𝗖𝗣 - 𝗔𝗿𝗰𝗵𝗶𝘁𝗲𝗰𝘁𝘂𝗿𝗲: MCP rides JSON-RPC and SDKs. ACP sticks to plain REST so curl just works. - 𝗦𝘁𝗿𝗲𝗮𝗺𝗶𝗻𝗴: MCP streams but skips token deltas; ACP roadmap covers fine-grained updates. - 𝗦𝗰𝗵𝗲𝗺𝗮: MCP accepts any JSON, great for speed but tough for UI interoperability. ACP pins down message shapes for plug-and-play orchestration. - 𝗔𝗻𝗮𝗹𝗼𝗴𝘆: MCP gives a single employee a better toolbox; ACP creates a dream team. 🌐 𝗔𝗖𝗣 𝘃𝘀. 𝗔𝟮𝗔 - 𝗣𝗵𝗶𝗹𝗼𝘀𝗼𝗽𝗵𝘆: ACP is vendor-neutral under open governance. A2A optimizes for Google’s cloud gravity. - 𝗜𝗻𝘁𝗲𝗴𝗿𝗮𝘁𝗶𝗼𝗻: ACP’s lightweight REST fits air-gapped or multi-cloud deployments. A2A shines if you are already all-in on Google services. - 𝗘𝗰𝗼𝘀𝘆𝘀𝘁𝗲𝗺: ACP powers BeeAI and other Linux Foundation projects. A2A is young but will likely deepen inside GCP. 🚀 Takeaway 1. Use MCP to make a single model smarter. 2. Use ACP to weld diverse agents from different vendors into one brain trust. 3. Use A2A when your agents live primarily inside Google’s universe. Interoperability is the next productivity multiplier. Choose your protocol stack wisely

Over the past few months, we've seen rapid advancements in the Agentic AI landscape—especially around how autonomous agents communicate, coordinate, and complete complex tasks. As these systems grow more capable, choosing the right agent communication protocol becomes critical to designing scalable, intelligent applications. Let’s break down the 4 most talked-about protocols in this space—each addressing different levels of autonomy, coordination, and execution logic. ⮕ 𝗠𝗖𝗣 – 𝗠𝗼𝗱𝗲𝗹 𝗖𝗼𝗻𝘁𝗲𝘅𝘁 𝗣𝗿𝗼𝘁𝗼𝗰𝗼𝗹 This is the most centralized approach. A single agent (like a “Travel Agent”) directly invokes different tools (e.g., flight, hotel, and weather services). The logic and orchestration are embedded within one agent’s context, making it simple to manage, but less flexible when scaling across domains or teams. ✔️ Best for: Simpler tasks with fewer dependencies ❌ Limitation: Limited cross-agent collaboration ⮕ 𝗔𝟮𝗔 – 𝗔𝗴𝗲𝗻𝘁-𝘁𝗼-𝗔𝗴𝗲𝗻𝘁 𝗣𝗿𝗼𝘁𝗼𝗰𝗼𝗹 This is where things get collaborative. The travel agent delegates sub-tasks to specialized agents (Flight Agent, Hotel Agent, Weather Agent, etc.). Each agent handles its own responsibility and reports back. This protocol supports structured task division and deep specialization within a single organization or domain. ✔️ Best for: Departmental collaboration within the same domain ❌ Limitation: Primarily structured for intra-domain collaboration; cross-domain extension may require additional wrappers ⮕ 𝗔𝗡𝗣 – 𝗔𝗴𝗲𝗻𝘁 𝗡𝗲𝘁𝘄𝗼𝗿𝗸 𝗣𝗿𝗼𝘁𝗼𝗰𝗼𝗹 ANP enables agents to operate across domains. Imagine a travel agent that doesn't just talk to internal systems but communicates with agents at external organizations—like hotel chains or airline APIs. Each agent is capable of independent crawling, data fetching, and even coordination without requiring central logic. ✔️ Best for: Cross-domain, dynamic environments ❌ Limitation: Complex error handling and security coordination 𝗡𝗼𝘁𝗲 - ANP (Agent Network Protocol) is not a formal standard like ACP, but rather a design pattern used to describe decentralized agent communication across domains. It reflects how agents autonomously interact with external systems or services without centralized orchestration. ⮕ 𝗔𝗖𝗣 – 𝗔𝗴𝗲𝗻𝘁 𝗖𝗼𝗺𝗺𝘂𝗻𝗶𝗰𝗮𝘁𝗶𝗼𝗻 𝗣𝗿𝗼𝘁𝗼𝗰𝗼𝗹 ACP formalizes communication among agents using a defined vocabulary like request, inform, and collaborate. Agents exchange structured messages and often interact with external systems to complete workflows. This creates a highly decoupled, yet synchronized agent environment—ideal for enterprise-grade multi-agent systems. ✔️ Best for: Modular, enterprise-scale applications involving third-party integrations ❌ Limitation: Requires strict message schema and orchestration rules 𝗪𝗵𝗮𝘁 𝗱𝗼 𝘆𝗼𝘂 𝘁𝗵𝗶𝗻𝗸 𝗮𝗯𝗼𝘂𝘁 𝘁𝗵𝗶𝘀 𝗰𝗼𝗺𝗽𝗮𝗿𝗶𝘀𝗼𝗻?Your feedback helps me create more useful content like this going forward.

Let’s just start and see where it goes. It sounds agile. It feels lean. But for SMBs, it’s often the reason projects stall When you're working with limited time and team capacity, direction matters more than speed. That’s why I borrow a principle from Amazon’s playbook: Working backwards. At Amazon, before any team writes a line of code, they write a press release. Not for marketing. For focus It forces one hard question upfront: If this succeeds, what will the customer actually experience? Now imagine what that unlocks for your business: → No more “building for the sake of building” → Clear decisions anchored to outcomes → Alignment without 50 meetings How do we adapt it for smaller teams: ✔️We skip the fluff, no decks, no endless planning ✔️We write a simple customer story that defines success clearly ✔️We avoid corporate jargon, just real language and real outcomes ✔️We reverse-engineer from the goal to decide what’s actually needed ✔️We align fast, so small teams don’t waste time chasing the wrong thing Example:Project: Improve client handoff process →Instead of “Improve client handoff,” We write: “Clients say the new handoff is so smooth, they felt taken care of from day one. Suddenly, everyone knows what we’re aiming for. And what not to waste time on. Because when you're small, clarity isn’t a luxury. It's your strategy. 👉 Want to test this with your next project? DM me, I’ll show you how we do it 

This Steps for Restaurant Manager Before starting the Shift. 1. Prioritize Team Morale: Managing people is more important than managing plates. A happy team ensures smooth service. 2. Master the Floor Plan: Know every table number, seat position, and section. This precision builds respect among your team. 3. Understand P&L Statements: Your real performance is reflected in the Profit & Loss statement. Monitor food costs, labor percentages, and wastage closely. 4. Conduct Daily Pre-Shift Briefings: Spending five minutes daily can prevent fifty minutes of chaos. Communicate specials, VIPs, and expectations clearly. 5. Build Trust with the Kitchen: The chef is your ally. A strong relationship between service and culinary teams is essential. 6. Maintain Stock Control: While you don't need to memorize every item, you should be aware of inventory movements to manage costs effectively. 7. Handle Guest Complaints Constructively: View complaints as valuable feedback. Listen actively, resolve issues, and follow up to turn dissatisfaction into loyalty. 8. Lead by Example: Your body language, tone, and pace set the standard for your team. Consistency and calmness are key. 9. Implement Effective Systems: Develop Standard Operating Procedures (SOPs), checklists, and side duties to ensure smooth operations during peak times. 10. Commit to Continuous Learning: Stay updated on coffee trends, service innovations, technology, and industry developments to grow as a leader.

How I hire someone - from the person who hired 9 out of 10 of Steven Bartlett’s best team members. I took a team of 30, whilst being MD at Social Chain, to a team of 130. That’s a lot of hires, isn’t it? And the stakes were high. But here’s the thing: the secret to building an exceptional team isn’t about CVs, qualifications, or fancy job titles. It’s about people. Here’s my advice for when the time comes: 1️⃣ Hire for values, not just skills. Get crystal clear on your values. If someone doesn’t align with what your business stands for, no amount of experience will make them a good fit. 2️⃣ Look for passion and care. Look for the people with a glisten in their eye when they talk about their work. You need people that care, it means they’ll care for, not just work for your business. 3️⃣ Think about the team, not just the role. It’s easy to hire someone who fills a gap in the workload. But the real question is: how will they elevate the team? 4️⃣ Hire good people, not just “qualified” people. The most skilled person in the world won’t make an impact if they’re not kind, collaborative, and driven. At Social Chain, we found the best people. Then we binded them with a culture that got the best out of them. What’s your biggest sticky point when it comes to hiring?

In high-growth environments, it’s easy for legal to become a service desk. Requests come in. Answers go out. Boxes get checked. Everyone moves on. Until the same issue reappears. Different team. Slightly different shape. Same root cause. I remember sitting in a product postmortem where this happened—for the third time. We hadn’t delayed anything. We hadn’t missed anything. But we also hadn’t changed anything. So I shifted the conversation. “This is the third time this has come up. Here’s what that tells us. Here’s what it’s costing us—in friction, in credibility, in time. Here’s how we can improve our position and influence if we design this process differently. Here’s how to get ahead of it.” It wasn’t just about risk anymore. It was about rhythm. Reputation. And reach. That moment taught me something about legal leadership: The real work isn’t just delivering answers—it’s building systems that prevent the question from being asked again. In this week’s newsletter, I explore: What it looks like when legal moves from reactive expert to proactive integrator How pattern recognition becomes a tool for strategic influence Why we created the Product Counsel Syllabus—and how it helps legal teams scale their thinking And what AI contracts are quietly teaching us about how governance is already being shaped This is about more than legal ops. It’s about legal impact—and the kind of leadership that sticks. What’s one system you built that helped your team move from “just in time” to “just ahead”? #LegalLeadership #SystemsThinking #ProductCounsel -------- 🚀 Olga V. Mack 🔹 Building trust in commerce, contracts & products 🔹 Sales acceleration advocate 🔹 Keynote Speaker | AI & Business Strategist 📩 Let’s connect & collaborate 📰 Subscribe to Notes to My (Legal) Self