Jay Vergara writes about AI, leadership, and how people actually grow at work. Practical tutorials, cross-cultural insights, and L&D strategy from Tokyo.https://leadhuman.ai/https://leadhuman.ai/build/council-of-ai-advisors/https://leadhuman.ai/build/council-of-ai-advisors/What if instead of one AI chat for everything, you had a personal advisory council? Each specialist trained on your context, your voice, and your goals. Here's how I built mine using Claude and why it changed how I work.Sun, 15 Mar 2026 00:00:00 GMTI run a consulting business and I write across three platforms and I'm trying to be a present dad through all of it. A year ago all of that lived in my head and a growing pile of half finished notes. I was using AI the way most people do. Open Claude, ask a question, get an answer, move on. Every conversation started from zero. Then I tried something different. I stopped treating AI as a single assistant and started treating it as a team. I call it the Council of Jays. And it changed how I work more than any productivity app ever has. --- ## The problem with one assistant Most people use AI like a search engine with better grammar. That works for small tasks but it falls apart when you need deep, consistent support across multiple areas of your life. Here's what kept happening. I'd ask Claude to help draft a LinkedIn post and the output was great. Then I'd switch to career strategy work and it was decent, but it had no memory of my writing voice. Then leadership content and I was starting from scratch again. The AI was smart but it had no specialization and no context about what mattered to me in each domain. Every conversation felt like meeting a brilliant stranger who forgot we'd ever spoken. --- ## So I built a council The idea came from something obvious in retrospect. The best leaders don't try to be experts in everything. They surround themselves with advisors who each own a domain. I built the AI version of that. Each councilor is a specialized skill with deep context about one area of my work. They have a name and a personality and a defined domain and growing knowledge about my preferences and goals. The First Councilor coordinates everyone and owns the master plan and holds me accountable and routes questions to the right specialist. He enters conversations like a Star Trek first officer. I'm a nerd. It works. The AI Councilor handles tutorials and workflow automation. The Content Councilor guards my voice and makes sure everything I publish sounds like me. The Cross-Cultural Councilor specializes in Japan and intercultural communication. The Career Councilor knows my resume in English and Japanese. Eleven councilors total and each one is deep and each one is consistent. --- ## Why it works **Specialization creates quality.** A councilor focused only on cross-cultural content holds nuanced context about Hofstede and Erin Meyer's Culture Map and my specific experiences in Japanese business culture. A general assistant can't match that depth. **Consistency compounds.** Because each councilor has persistent guidelines, my voice stays consistent across hundreds of outputs. The Content Councilor knows I don't use hyphens ever, that I prefer diagnosis before prescription, and that I anchor posts to named concepts. **The intersections are the magic.** When the AI Councilor and the L&D Councilor collaborate on a piece about using AI for training design, you get something neither could produce alone. --- ## How to build your own Start with three councilors, not eleven. **Identify your domains.** What 3 to 5 areas of your professional life need consistent support? For most people that's your core expertise and your content or brand and your career strategy. **Write the context.** For each councilor, create a detailed prompt with their domain and your preferences and what success looks like. One page each is enough to start. **Give them personality.** Sounds frivolous but it matters. A councilor with personality is one you'll actually use instead of treating AI like a chore. **Build the coordination layer.** The most important councilor manages all the others. Without a coordinator you have isolated tools. With one you have a system. **Let them evolve.** The council I have today looks nothing like the one I started with. It's a living system. --- The council taught me something unexpected. The bottleneck in using AI isn't the AI's capability. It's the human's ability to give it enough context to be genuinely useful. Build yours and start small and let it grow and you'll wonder how you ever worked without it. --- **Sources:** - [Claude Projects Documentation](https://docs.anthropic.com/en/docs/about-claude/models) — set up persistent context for each councilor in Claude. - [Anthropic's Prompt Engineering Guide](https://docs.anthropic.com/en/docs/build-with-claude/prompt-engineering) — best practices for the detailed system prompts that make councilors effective. - [How to Use Claude to Build a Personal Knowledge System in 30 Minutes](https://leadhuman.ai/build/claude-personal-knowledge-system) — the prerequisite tutorial for setting up your foundation before building a council. - [The Culture Map by Erin Meyer](https://erinmeyer.com/books/the-culture-map/) — one of the frameworks my Cross-Cultural Councilor draws from constantly. --- *Part of the Build with AI series on [leadhuman.ai](https://leadhuman.ai).*https://leadhuman.ai/lead/why-leaders-need-ai/https://leadhuman.ai/lead/why-leaders-need-ai/You don't need to become an AI engineer. But you do need to understand what AI can and can't do well enough to make smart decisions about where it fits in your work and your team's workflow.Sun, 15 Mar 2026 00:00:00 GMTI keep hearing the same thing from senior leaders: "AI is important, sure, but I'm a people leader and the technical stuff is what my IT team is for." I get the instinct. Leadership has always been about people, and the best leaders I've worked with build trust, create psychological safety, develop talent, and make hard calls under uncertainty. None of that requires a ChatGPT subscription. But here's what I keep seeing on the ground in Tokyo working with leaders across industries. The ones who dismiss AI as 'not my department' are already falling behind, not because AI is replacing what they do but because AI is reshaping the environment they do it in. And if you don't understand the environment you can't lead in it. --- ## It's not about prompts. It's about decisions. [Zirar, Ali & Islam (2023)](https://consensus.app/papers/worker-and-workplace-artificial-intelligence-ai-zirar-ali/592b83fec1365c34aef810e0fc2a9969/) conducted a systematic review of workplace AI coexistence and found something that should reframe how leaders think about this: **successful AI adoption requires technical, human, and conceptual skills, but human and conceptual skills matter more than technical ones**. In other words, the leaders who thrive aren't the ones who learn to code but the ones who understand what AI changes about the decisions they make every day. Every leader needs to understand enough about AI to answer three questions. **What can I delegate to AI?** This isn't theory but practice, applied to their actual workflow with their actual team this quarter. The leader who identifies the right tasks to automate frees up hours of human attention for the work that actually needs human judgment. **What should I protect from AI?** This is the question most people skip, and it matters just as much. Feedback conversations, relationship building, creative ideation that requires lived experience. These get worse when you outsource them, and knowing the boundary is a leadership skill now. **How is AI changing my team's expectations?** Your direct reports are already using AI whether you've sanctioned it or not. Some are using it well and some are producing mediocre work faster, and a leader who understands the tool can tell the difference and coach accordingly. --- > 🔑 **AI fluency for leaders isn't about becoming a power user. It's about understanding enough to make better decisions, ask sharper questions, and model the curiosity your team needs to see.** The barrier to AI adoption in most organizations isn't technical. It's cultural. And culture starts with leadership. --- ## What AI fluency actually looks like Research on empowering leadership and AI readiness ([Schneider & Leyer, 2023](https://www.consensus.app/papers/details/6b4926b44c425c338b95409c6c96663b/)) found that **leaders who give their teams autonomy and development support are better positioned to manage AI-induced change**. The key insight: it's not about the leader's personal technical skill but about creating conditions where the team can experiment and adapt. It means knowing what's possible. A training needs analysis that used to take three weeks can now take three days, and that changes your planning timeline and what you promise stakeholders. It means asking better questions. When your team says "we can't do that in the timeline," the AI fluent leader asks "have we explored whether AI can handle the first 80% so our people focus on the judgment calls?" That's not a technical question but a leadership question. And it means modeling curiosity. The single biggest barrier to AI adoption in organizations isn't technical but cultural, and it's the senior leader who says "I'm too old for this." When a leader visibly experiments with AI, even clumsily, it gives everyone else permission to do the same. --- ## Four Things to Try This Month > 1️⃣ **Spend one hour experimenting.** Pick one thing you do every week that involves synthesizing information, whether that's reading reports or preparing for meetings, and try using AI to help. Notice what it does well and where it falls short. > 2️⃣ **Have one honest conversation with your team.** Ask them: "Are you using AI? What for? What's working?" The answers will tell you more than any assessment tool. > 3️⃣ **Get clear on your boundaries.** What parts of your leadership should never be automated? Answering that question makes you more confident about adopting AI for everything else. > 4️⃣ **Model it publicly.** Share what you're learning, including the failures. "I tried using AI for our quarterly planning and here's what worked and what didn't" is more powerful than any training program. --- The leaders who thrive in the next decade won't be the most technical but the most adaptive. They'll know enough about AI to ask sharper questions and create environments where human talent and artificial intelligence both do their best work. --- **Sources:** - [Zirar, Ali & Islam (2023)](https://consensus.app/papers/worker-and-workplace-artificial-intelligence-ai-zirar-ali/592b83fec1365c34aef810e0fc2a9969/) — "Worker and Workplace AI Coexistence: Emerging Themes and Research Agenda." - [Schneider & Leyer (2023)](https://www.consensus.app/papers/details/6b4926b44c425c338b95409c6c96663b/) — "Maneuvering Through the Stormy Seas of Digital Transformation: The Impact of Empowering Leadership on AI Readiness." - [How I Built a Council of AI Advisors](https://leadhuman.ai/build/council-of-ai-advisors) — what AI fluency looks like in practice for a leader managing multiple domains. - [AI Is Changing L&D Faster Than Most Leaders Realize](https://leadhuman.ai/lead/ai-changing-ld) — how AI is reshaping the learning and development function. --- *Part of the Lead Humanly series on [leadhuman.ai](https://leadhuman.ai).*https://leadhuman.ai/build/claude-personal-knowledge-system/https://leadhuman.ai/build/claude-personal-knowledge-system/Most people use AI like a search engine. I turned Claude into a personal knowledge management system that remembers my context, my career goals, and my writing voice. Here's the architecture behind it.Sat, 14 Mar 2026 00:00:00 GMTMost people treat AI conversations like disposable text messages. Ask a question, get an answer, close the tab, and next time you open it the AI has no idea who you are. I did this for months before I realized I was introducing myself to the same brilliant colleague every morning and wondering why the output felt generic. There's a better way. It takes about 30 minutes to set up. --- ## What you're building A personal context document that Claude can reference in every conversation. Instead of re-explaining your situation each time you start where you left off. The AI already knows who you are and what you're working on and how you think. --- ## Step 1: Write your context document (10 minutes) Open a doc. Notion, Google Docs, plain text, whatever you actually use. Cover four things. **Who you are.** Role, industry, location. Two sentences. **What you're working on now.** Top 3 to 5 priorities this quarter. Be specific. Not 'grow the business' but 'launch the new manager development program for Q2.' **How you like to work.** Do you want to be challenged or supported? Do you think in frameworks or narratives? This part makes the biggest difference and most people skip it. **Your professional context.** Anything the AI should know about your industry and audience and frameworks that would improve its answers. Here's a simplified version of mine: ``` I'm Jay Vergara. L&D strategist and cross-cultural communication specialist based in Tokyo. I run leadhuman.ai and consult on leadership development and intercultural communication. Priorities: 3-5 content pieces per week. New cross-cultural workshops for Q2. How I work: Challenge me. I think in frameworks. Keep it practical. Pillars: cross-cultural (32%), L&D (29%), AI (29%), leadership (11%) ``` One page. You can always expand later. --- ## Step 2: Create domain pages (15 minutes) Break your knowledge into 2 to 3 domains. For each one capture: **Frameworks you actually use.** Not the ones from school. The ones you reach for. Kirkpatrick, 70/20/10, MEDDIC, whatever lives in your real toolkit. **Your opinions.** What do you believe that others might disagree with? These make your AI output sound like you instead of like everyone else. **Tasks where you need help.** The recurring stuff where AI would be most valuable. --- ## Step 3: Connect it (5 minutes) **[Claude.ai](https://claude.ai):** Use Projects. Upload your docs as project knowledge. Every conversation in that project gets your full context automatically. **Claude Code or Desktop with MCP:** Connect Claude directly to your Notion or Google Drive. It reads the docs at session start. **Any platform:** Paste your context doc at the start of a new conversation. Takes 10 seconds and changes everything. --- ## Step 4: Keep it alive (5 min/week) Weekly: update priorities and recent decisions. Monthly: review domain pages and evolve your frameworks. After major changes: update immediately. The system only works if it reflects your actual current reality. --- ## What changes With context Claude drafts content that sounds like you and makes recommendations for your specific situation and pushes back with relevant counterarguments and connects dots across your work. Without context it's smart but generic. With context it's a genuine thinking partner. And here's what surprised me most. Building the system forced me to articulate things about my own work I'd never written down. My frameworks and my opinions and my priorities. That was valuable before I even gave it to the AI. 30 minutes. Start today. --- **Sources:** - [Claude Projects Documentation](https://docs.anthropic.com/en/docs/about-claude/models) — how to use Projects for persistent context in Claude. - [Tiago Forte's "Building a Second Brain"](https://www.buildingasecondbrain.com/) — the framework that inspired the knowledge management approach behind this system. - [How I Built a Council of AI Advisors](https://leadhuman.ai/build/council-of-ai-advisors) — takes this concept further by creating specialized AI personas with deep domain context. - [Why Every Leader Needs to Understand AI](https://leadhuman.ai/lead/why-leaders-need-ai) — the leadership case for building AI fluency, starting with systems like this one. --- *Part of the Build with AI series on [leadhuman.ai](https://leadhuman.ai).*https://leadhuman.ai/lead/ai-changing-ld/https://leadhuman.ai/lead/ai-changing-ld/Most L&D leaders still think of AI as a faster way to write course descriptions. The real shift is much bigger and organizations that figure it out in the next 18 months will have a significant advantage in talent development.Fri, 13 Mar 2026 00:00:00 GMTSomething I keep noticing in conversations with L&D leaders: they know AI is coming for their function, they just don't know how fast. Most of them are still thinking about AI as a content creation tool, a faster way to write course descriptions or generate quiz questions. And sure, it does that, but that's like saying the internet is a faster fax machine. The real shift is much bigger. --- ## The shift nobody's ready for [Zhang & Fan (2024)](https://consensus.app/papers/aidriven-learning-analytics-applications-and-tools-in-zhang-fan/f4ecc1b56ecd5ce989238a3bd1550c72/) conducted a systematic review of AI-driven learning analytics and found that **AI tools in collaborative learning environments primarily focus on tracking cognitive engagement, but most lack proper instructional design principles and intervention support**. That's the gap right now: the technology is ahead of the pedagogy, and L&D professionals who understand learning design are the ones who can close it. AI can now generate personalized learning paths for individual employees based on their actual skill gaps rather than the generic 'everyone takes the same compliance training' approach. It builds genuinely personalized development plans that adapt as the person grows. It can analyze performance data to identify skill gaps before they become performance problems, before the manager notices, before the annual review. It can create realistic practice scenarios for difficult conversations, so a new manager can rehearse giving tough feedback with an AI that responds like a defensive employee, over and over until they build the muscle memory. And it can translate and localize training content across languages in minutes. I work in Tokyo with international teams and this alone would have saved me hundreds of hours in previous roles. --- > 🔑 **The real risk isn't that AI will replace L&D professionals. It's that AI will make it easy to produce training that looks polished and says absolutely nothing.** Beautiful slides, professional scripts, perfect formatting, zero learning. Most leaders can't tell the difference yet. That's the problem. --- ## The window is closing [Guenole & Charlwood (2023)](https://consensus.app/papers/can-hr-adapt-to-the-paradoxes-of-artificial-intelligence-guenole-charlwood/9fbbe1db2ec356019363e4873fb687c4/) examined whether HR can adapt to the paradoxes of AI and identified a critical tension: **HR and L&D professionals need to develop skills to ensure that ethics and fairness remain central to AI development for people management**, but most aren't building those skills fast enough. The ones who figure this out in the next 12 to 18 months become indispensable. The ones who use AI to churn out more of the same mediocre training faster will automate themselves out of relevance. AI can generate assessments that test whether someone remembers a fact but not whether they can apply it when it matters, and it can create the appearance of a learning culture without any actual learning happening. Knowing the difference between AI that enhances learning and AI that simulates it. That's the competency that matters now. --- ## Four Things to Try This Month > 1️⃣ **Run one existing training program through an AI lens.** Take your most popular course and ask: what parts of this could AI personalize for each learner? What parts require a human facilitator? The answers will reshape how you think about your entire curriculum. > 2️⃣ **Build one AI-powered practice scenario.** Pick a skill your managers struggle with (feedback, delegation, difficult conversations) and use Claude or ChatGPT to create a realistic practice partner. Test it yourself first and notice what works. > 3️⃣ **Audit your content for 'polished emptiness.'** Review your last three training modules and ask honestly: does this change behavior or does it just check a box? AI makes it easier to produce content that feels complete but teaches nothing. > 4️⃣ **Have the skills conversation with your team.** What AI skills does your L&D function need in the next year? Not coding but prompt design, learning analytics, personalization architecture. Map the gap now. --- The window between 'early adopter' and 'too late' is shorter than most L&D leaders think. The ones who start experimenting now will define what good looks like for everyone else. --- **Sources:** - [Zhang & Fan (2024)](https://consensus.app/papers/aidriven-learning-analytics-applications-and-tools-in-zhang-fan/f4ecc1b56ecd5ce989238a3bd1550c72/) — "AI-Driven Learning Analytics Applications and Tools in Computer-Supported Collaborative Learning: A Systematic Review." - [Guenole & Charlwood (2023)](https://consensus.app/papers/can-hr-adapt-to-the-paradoxes-of-artificial-intelligence-guenole-charlwood/9fbbe1db2ec356019363e4873fb687c4/) — "Can HR Adapt to the Paradoxes of Artificial Intelligence?" - [How to Use Claude to Build a Personal Knowledge System](https://leadhuman.ai/build/claude-personal-knowledge-system) — how AI can support continuous learning at the individual level. - [Why Every Leader Needs to Understand AI](https://leadhuman.ai/lead/why-leaders-need-ai) — the leadership side of the AI adoption challenge. --- *Part of the Lead Humanly series on [leadhuman.ai](https://leadhuman.ai).*https://leadhuman.ai/lead/why-your-proposal-died/https://leadhuman.ai/lead/why-your-proposal-died/In Japan the meeting isn't where decisions get made. It's where they get confirmed. The real work happened days ago and you missed it.Thu, 12 Mar 2026 00:00:00 GMTThere's a Japanese word I use almost every day at work that has no clean English equivalent: nemawashi. The dictionary will tell you it means 'laying the groundwork' or 'building consensus in advance,' and that's technically accurate but completely insufficient. If you try to operate in Japan without understanding what it really means you'll spend months wondering why your brilliant proposals keep dying in meetings that were supposed to be formalities. I learned this the hard way early on. I showed up to a leadership meeting with what I thought was a perfectly prepared proposal (data, slides, the whole thing) and it died in under five minutes. Not because the idea was bad but because I'd skipped the part where you talk to people before the room decides. A Japanese colleague pulled me aside afterward and explained, gently, that the meeting was never where the decision was going to happen. --- ## The meeting isn't where the decision happens In most North American companies you bring a proposal to a meeting where people discuss it, there's debate, and a decision gets made. The meeting is the decision point. In most Japanese companies the meeting is the announcement, because the decision was already made through a series of one on one conversations in the days or weeks before. By the time everyone sits down the key stakeholders have already been consulted and the proposal has been quietly reshaped to accommodate their perspectives. That process is nemawashi, which is a gardening term that literally means 'going around the roots.' You tend the soil before you plant anything. [Van Scotter & Leonard (2023)](https://consensus.app/papers/culture-and-communication-scotter-leonard/a1705b76f93d54268a7c4f96ed598cc6/) reviewed research on culture and communication and found that **cultural differences remain formidable obstacles to effective communication in organizations, with social and cultural factors significantly influencing how people perceive what's being communicated and through which channels**. The nemawashi gap is a textbook case of this: same meeting, same agenda, completely different expectations about what the meeting is for. --- > 🔑 **The meeting is not where the decision happens. In consensus-driven cultures the meeting is where the decision gets confirmed. The real work happened in the hallways, over coffee, one on one.** If you're walking into a meeting hoping to persuade people in real time, you've already lost in cultures that value pre-alignment. --- ## This isn't just a Japan thing Every organization has an informal decision making process that exists alongside the formal one, and every company has stakeholders whose buy in you need before the official meeting. Every leader has experienced presenting a great idea only to have it shot down by someone who felt blindsided. Nemawashi is just the Japanese word for something universal: the work that happens before the work. Erin Meyer places Japan at the extreme end of the consensus building scale in The Culture Map, but even cultures on the 'top down' end benefit from pre-alignment on important decisions. The difference is degree, not kind. [Ayenew & Zewde (2024)](https://consensus.app/papers/managing-diversity-and-multicultural-collaboration-a-ayenew-zewde/bda351577765516f8000abee7d7c4e42/) found in their systematic review that **managing multicultural collaboration requires understanding how different cultural values shape organizational communication norms**, and that leaders who bridge these differences see measurably better outcomes in diverse teams. Nemawashi is one of those bridges. --- ## Four Things to Try Before Your Next Big Meeting > 1️⃣ **Map your stakeholders before proposing anything.** Identify everyone who will be affected or whose support you need. In Japanese organizations this often includes people several levels removed who might not seem directly relevant. Include them anyway. > 2️⃣ **Have individual conversations first.** Go to each person privately and share the idea. Listen carefully to what they say and more importantly to what they don't say. This is not a lobbying tour but a genuine consultation. > 3️⃣ **Incorporate feedback genuinely.** This is where most people get it wrong. Nemawashi only works if you're willing to reshape the proposal based on what you hear. If you're going through the motions people will know, and they'll remember. > 4️⃣ **Let the meeting confirm what's already agreed.** When the proposal finally reaches the room it should feel almost anticlimactic. That's how you know it worked. --- Before your next big leadership meeting sit down one on one with the people who matter to the outcome. Not to lobby them but to listen and give them room to think out loud privately before they're in a room full of people. You'll walk into that meeting with much better information, and the colleagues who communicate more indirectly will feel like they actually had a say. --- **Sources:** - [Van Scotter & Leonard (2023)](https://consensus.app/papers/culture-and-communication-scotter-leonard/a1705b76f93d54268a7c4f96ed598cc6/) — "Culture and Communication." - [Ayenew & Zewde (2024)](https://consensus.app/papers/managing-diversity-and-multicultural-collaboration-a-ayenew-zewde/bda351577765516f8000abee7d7c4e42/) — "Managing Diversity and Multi-Cultural Collaboration: A Systematic Review." - [The Culture Map by Erin Meyer](https://erinmeyer.com/books/the-culture-map/) — maps how different cultures approach decision making and consensus building. - [The Words You Can't Translate Are the Cultural Keys](https://leadhuman.ai/lead/words-you-cant-translate) — more Japanese concepts that shape how business actually works. --- *Part of the Lead Humanly series on [leadhuman.ai](https://leadhuman.ai).*https://leadhuman.ai/lead/words-you-cant-translate/https://leadhuman.ai/lead/words-you-cant-translate/Some of the most powerful leadership concepts don't translate into English. Words like nemawashi, kuuki wo yomu, and amae carry centuries of cultural wisdom that one-word translations can't capture. Here's why that matters for global teams.Wed, 11 Mar 2026 00:00:00 GMTI've been living in Japan for over a decade and I still run into words that stop me in my tracks. Not because I don't understand them but because I can't translate them without losing the thing that makes them matter. Nemawashi. Kuuki wo yomu. Amae. Shoganai. Every language has these, and I've started to believe they're the single fastest way to understand what a culture actually values. --- ## Reading the air Take 'kuuki wo yomu.' It literally means 'reading the air,' though the dictionary might say 'reading the room,' but that misses something important. In Japan this isn't just a nice social skill but a baseline expectation, and it's the ability to sense what's not being said, to pick up on tension or discomfort without anyone naming it out loud. If you can't do it people won't tell you you're missing it. They'll just quietly work around you. I've watched this play out in meetings dozens of times, where the Western colleague keeps pushing a point that everyone else in the room has already silently agreed to drop. Nobody says stop, but the air says stop, and the gap between those two things is where cross-cultural misunderstandings live. [Van Scotter & Leonard (2023)](https://consensus.app/papers/culture-and-communication-scotter-leonard/a1705b76f93d54268a7c4f96ed598cc6/) reviewed research on culture and communication and found that **cultural differences significantly influence individuals' perception of what's being communicated, with social and cultural factors shaping not just the content but the channels through which communication is interpreted as effective**. 'Kuuki wo yomu' is the Japanese version of this insight turned into an everyday practice. --- > 🔑 **Untranslatable words aren't just vocabulary gaps. They're windows into what a culture prioritizes, what it rewards, what it punishes, and what it considers so obvious that it doesn't need to be said out loud.** Learning these words is the fastest path to real cultural fluency. --- ## The operating system you can't see Take 'amae.' Roughly translated as presumed indulgence or the expectation that someone close to you will accommodate your needs without you having to ask directly. There's no English word for this because the concept barely exists in Western individualist cultures, but in Japan it shapes everything from how managers and subordinates interact to how favors work in business relationships. Understanding amae helped me stop interpreting certain Japanese workplace behaviors as 'passive' or 'indirect' and start seeing them as a completely different operating system for trust. Every language has these untranslatable concepts. The Filipino 'pakikisama' which is about maintaining smooth interpersonal relationships even at personal cost. The Danish 'hygge' which captures a specific quality of cozy togetherness that English can only gesture at. The German 'Fingerspitzengefuhl' for intuitive feel or situational awareness. [Kumar (2024)](https://consensus.app/papers/understanding-cultural-differences-in-innovation-a-kumar/83922667d9ce57ef9306d6076d82d731/) proposed a framework showing that **cultural differences fundamentally shape how organizations approach innovation and collaboration**, and these differences are most visible in the concepts each culture names and values. When a culture has a specific word for something, it means that thing matters enough to deserve naming. --- ## Four Things to Try When Working Across Cultures > 1️⃣ **When you encounter a word that doesn't translate cleanly, don't rush to find the closest English equivalent.** Sit with the discomfort. Ask people to explain it through stories rather than definitions. That discomfort of not having a perfect translation is the feeling of your cultural understanding getting deeper. > 2️⃣ **Start a list of untranslatable concepts from the cultures you work with.** Write down the word, the literal translation, and then a paragraph about what it actually means in practice. This becomes your cross-cultural cheat sheet. > 3️⃣ **Use these words in conversation with colleagues from that culture.** Nothing signals respect faster than showing you've taken the time to learn a concept that matters to them. Say 'nemawashi' to a Japanese colleague and watch their face light up. > 4️⃣ **Look for your own untranslatable concepts.** What does your culture value so deeply that it has a specific word for it? Asking this question reveals your own cultural programming, and that self-awareness is the starting point for genuine cross-cultural fluency. --- The untranslatable words are the keys, and they just don't fit any lock you already own. --- **Sources:** - [Van Scotter & Leonard (2023)](https://consensus.app/papers/culture-and-communication-scotter-leonard/a1705b76f93d54268a7c4f96ed598cc6/) — "Culture and Communication." - [Kumar (2024)](https://consensus.app/papers/understanding-cultural-differences-in-innovation-a-kumar/83922667d9ce57ef9306d6076d82d731/) — "Understanding Cultural Differences in Innovation: A Conceptual Framework." - [The Culture Map by Erin Meyer](https://erinmeyer.com/books/the-culture-map/) — maps how cultural dimensions shape business communication across borders. - [Takeo Doi's "The Anatomy of Dependence"](https://en.wikipedia.org/wiki/The_Anatomy_of_Dependence) — the foundational text on *amae* and its role in Japanese social relationships. - [Why Your Proposal Died Before the Meeting Started](https://leadhuman.ai/lead/why-your-proposal-died) — goes deeper into nemawashi and how it shapes Japanese business decisions. --- *Part of the Lead Humanly series on [leadhuman.ai](https://leadhuman.ai).*https://leadhuman.ai/lead/leaders-who-listen/https://leadhuman.ai/lead/leaders-who-listen/Listening isn't passive. It's the most underrated leadership behavior in organizations and a likely cause of better job performance, stronger relationships, and greater well-being. The research is clear and most leaders still get it wrong.Tue, 10 Mar 2026 00:00:00 GMTI've worked with a lot of leaders over the past decade, and I've coached some, trained others, and watched a few very closely to figure out what made them different. The best ones all had something in common: they talked less than everyone else in the room. Not because they had nothing to say, but because they understood that talking is easy and listening is the skill that actually changes outcomes. ## The Listening Gap Most leaders think they're good listeners, and I thought I was too until I started paying attention to what I was actually doing when someone was talking to me. I was waiting, formulating my response, thinking about how to fix their problem, and occasionally checking my phone. That's not listening but performing patience. [Kluger & Itzchakov (2021)](https://consensus.app/papers/the-power-of-listening-at-work-kluger-itzchakov/746e2d8afbfa5ee290ddda37309972bc/) published research on listening in the *Annual Review of Organizational Psychology* and the findings are striking. **Listening is associated with and a likely cause of better job performance, stronger leadership, higher quality relationships, deeper job knowledge, and greater well-being** for both the listener and the person being heard. They propose something called 'episodic listening theory' where when two people are genuinely listening to each other, they enter a state of togetherness and mutual creative thought process. It generates clarity, new ideas, and a stronger attachment to the conversation partner. That's not soft skill territory but a performance mechanism. --- > 🔑 **Listening isn't passive. It's the most underrated leadership behavior in organizations.** The research is clear: when leaders listen well, their teams perform better, trust more, and stay longer. The hard part isn't understanding this. It's actually doing it when you're stressed, behind on deadlines, and convinced you already know the answer. --- ## What Happens When Leaders Don't Listen [Belgasm et al. (2025)](https://consensus.app/papers/interpersonal-conflict-and-employee-behavior-in-the-belgasm-alzubi/1ce52fd9117d5f8caef0f9c4781e74f7/) studied 501 public sector employees and found that **supervisors' active empathic listening directly moderates the relationship between interpersonal conflict and deviant behavior**. When conflict arises (and it always does), teams with leaders who listen empathically experience significantly less ostracism and fewer destructive behaviors. The reverse is also true because when employees feel unheard, conflict escalates and people withdraw. The best performers start looking for the exit. I've seen this play out dozens of times: a leader who moves fast and "gets things done" wonders why their team seems disengaged and interprets the silence as agreement. It's not agreement but people who have stopped trying to be heard. --- ## Four Things to Try This Week > 1️⃣ **In your next one on one, don't solve anything for the first 10 minutes.** Just listen and ask follow up questions and reflect back what you're hearing. The urge to fix will be overwhelming. Resist it because most people don't need your solution but need to feel understood first. > 2️⃣ **Count how many times you interrupt in meetings this week.** Just track it without trying to change anything yet because awareness alone shifts behavior. Most leaders are shocked when they start counting. > 3️⃣ **After someone finishes talking, pause for three seconds before responding.** It feels like an eternity and gives the other person space to add the thing they were actually trying to say because the real thought often comes after the first thought. > 4️⃣ **Ask one question you don't already know the answer to.** Leaders fall into a pattern of asking questions to confirm what they already think, and genuine curiosity sounds different. "What am I not seeing here?" is a good place to start. --- The leaders who changed my career weren't the ones with the best ideas but the ones who made me feel like my ideas mattered. That feeling came from one thing: they listened like what I was saying was important and then they acted on it. That says more about an organization's culture than any engagement survey ever could. --- **Sources:** - [Kluger & Itzchakov (2021)](https://consensus.app/papers/the-power-of-listening-at-work-kluger-itzchakov/746e2d8afbfa5ee290ddda37309972bc/) — "The Power of Listening at Work," *Annual Review of Organizational Psychology and Organizational Behavior*. - [Belgasm et al. (2025)](https://consensus.app/papers/interpersonal-conflict-and-employee-behavior-in-the-belgasm-alzubi/1ce52fd9117d5f8caef0f9c4781e74f7/) — "Interpersonal Conflict and Employee Behavior in the Public Sector." --- *Part of the Lead Humanly series on [leadhuman.ai](https://leadhuman.ai).*https://leadhuman.ai/lead/hard-conversation/https://leadhuman.ai/lead/hard-conversation/Most managers think they're protecting their team by softening feedback. The research says the opposite. Your people are starving for the conversation you keep dodging.Mon, 09 Mar 2026 00:00:00 GMTI keep running into the same pattern in every company I work with. A manager knows something needs to be said and they rehearse it in their head and they open the one on one doc and then they soften it and water it down and wrap it in so much context that the actual message disappears. The person walks out thinking everything is fine while the manager walks out knowing it isn't and the gap between those two realities grows a little wider every week. ## The Feedback Gap Nobody Talks About Here's what makes this tricky: most managers aren't avoiding feedback because they don't care but because they care too much. They don't want to hurt the relationship and they don't want to be the bad guy and they assume the other person doesn't want to hear it. That assumption is almost always wrong. [Abi-Esber et al. (2022)](https://consensus.app/papers/just-letting-you-know-%E2%80%A6-underestimating-others-desire-for-abi-esber-abel/7136c3662d775aacaefe74102483b3ac/) ran five experiments with nearly 2,000 participants and found something that should make every manager uncomfortable: **people consistently underestimate how much others want to receive constructive feedback**. In a field study, only 2.6% of people told someone they had food on their face, not because they were cruel but because they assumed the person wouldn't want to know. Now scale that to performance feedback and career development conversations and the moments that actually shape someone's trajectory, and that's a lot of unsaid things piling up. --- > 🔑 **The core problem isn't that managers can't give feedback. It's that they misjudge how much their people actually want it. The discomfort belongs to the giver, not the receiver. And by protecting themselves from that discomfort, managers starve their teams of the information they need to grow.** --- ## Why It Lands Wrong (When It Finally Comes) When feedback does arrive, it often backfires, not because the content is wrong but because the delivery triggers the wrong response. [Xing et al. (2021)](https://consensus.app/papers/supervisor-negative-feedback-and-employee-motivation-to-xing-sun/cce0e0fc35515dcb8a812fb6885b8a2a/) studied this across 370 employees in the US and 302 nurses in China and found that **employees' response to negative feedback depends on why they think you're giving it**. If they believe it's genuinely about their performance, they're motivated to learn, but if they think it's about you and your frustration or ego or agenda, they shut down. This is where Stone and Heen's feedback triggers framework becomes useful because people reject feedback for one of three reasons: they think the feedback is wrong (truth trigger), they have a problem with the person giving it (relationship trigger), or the feedback threatens their identity and their sense of who they are (identity trigger). [Steele et al. (2025)](https://consensus.app/papers/i-am-not-who-you-think-i-am-the-role-of-appraisal-in-responses-steele-hill/b0b7fc3be80550308da09486874697bf/) confirmed this in a recent study of leaders in engineering firms and found that when feedback conflicts with someone's self view, the outcome depends entirely on whether they appraise it as a threat or an opportunity, and that same feedback can have a completely different result based on how it's framed and received. --- ## Four Things to Try This Week > 1️⃣ **Ask before you tell.** Before your next one on one, try: "What kind of feedback would be most helpful to you right now? Appreciation, coaching, or evaluation?" Let them choose because this one question from Stone and Heen's framework changes the entire dynamic and the person is opting in instead of bracing for impact. > 2️⃣ **Lead with what you're seeing, not what you're judging.** "I've noticed the last two project updates came in after the deadline" lands differently than "You're not managing your time well" because one is observable while the other triggers an identity response. Keep it specific and behavioral. > 3️⃣ **Say the thing you're afraid to say, sooner.** The longer feedback sits unsaid, the bigger it gets in your head and the more blindsided the person feels when it finally arrives, and a small, timely conversation is almost always better than a big, delayed one. > 4️⃣ **Check your motive before you open your mouth.** Xing's research is clear on this: if the feedback is really about your frustration rather than their development, they'll sense it and they won't learn from it. If you're angry, wait, and if you're genuinely trying to help, go. --- Feedback isn't about finding the perfect words but about closing the gap between what you see and what they know. Most of the time the other person already senses something is off and they just need you to name it. --- **Sources:** - [Abi-Esber et al. (2022)](https://consensus.app/papers/just-letting-you-know-%E2%80%A6-underestimating-others-desire-for-abi-esber-abel/7136c3662d775aacaefe74102483b3ac/) — "Just Letting You Know… Underestimating Others' Desire for Constructive Feedback," *Journal of Personality and Social Psychology*. - [Xing et al. (2021)](https://consensus.app/papers/supervisor-negative-feedback-and-employee-motivation-to-xing-sun/cce0e0fc35515dcb8a812fb6885b8a2a/) — "Supervisor Negative Feedback and Employee Motivation to Learn." - [Steele et al. (2025)](https://consensus.app/papers/i-am-not-who-you-think-i-am-the-role-of-appraisal-in-responses-steele-hill/b0b7fc3be80550308da09486874697bf/) — "I Am Not Who You Think I Am: The Role of Appraisal in Responses to Feedback." --- *Part of the Lead Humanly series on [leadhuman.ai](https://leadhuman.ai).*https://leadhuman.ai/lead/quiet-team-members/https://leadhuman.ai/lead/quiet-team-members/Your quietest team members might be your most insightful. Research shows that silence in meetings doesn't mean disengagement but often means the environment isn't designed for how they think. Here's how to unlock their contribution.Sun, 08 Mar 2026 00:00:00 GMTThere's a pattern I notice in almost every workshop I run with global teams: the loudest voices dominate the room, the quietest ones wait, and by the time the meeting ends, the people with the most thoughtful perspectives haven't said a word. Leaders usually read this one of two ways, either "they don't have anything to contribute" or "they agree with the direction," and both assumptions are usually wrong. ## The Silence Problem Employee silence is one of the most studied topics in organizational behavior over the past decade. [Morrison (2022)](https://consensus.app/papers/employee-voice-and-silence-taking-stock-a-decade-later-morrison/70fcfaf6ab7e53f980df610ea96bb4dd/) reviewed hundreds of studies in the *Annual Review of Organizational Psychology* and found that **employees choose silence for very specific reasons: fear of negative consequences, belief that speaking up won't make a difference, and a calculation that the social cost of voicing an idea outweighs the potential benefit**. Notice what's not on that list: "they have nothing to say." Silence is almost never about having nothing to contribute but about whether the environment makes it safe and worthwhile to contribute. --- > 🔑 **Silence is not agreement. It's not disengagement. It's a strategic decision employees make when they believe the cost of speaking up is higher than the cost of staying quiet.** The question isn't "why aren't they talking?" It's "what have we built that makes them not want to?" --- ## The Cultural Layer Nobody Talks About This gets more complicated when your team spans cultures. [Kwon & Farndale (2020)](https://consensus.app/papers/employee-voice-viewed-through-a-crosscultural-lens-kwon-farndale/6c03aab7a4815912bd66b244b3b008fe/) developed a framework showing how **national culture values directly shape organizational voice norms**, and in high power distance cultures, speaking up to a superior carries a different weight than in low power distance cultures, while in collectivist cultures, individual voice can feel like it disrupts group harmony. I see this constantly working across Japan and North America where my Japanese colleagues often process ideas privately before sharing and they consult with peers one on one and they wait for the right moment. Western colleagues sometimes interpret this as a lack of engagement or confidence when it's neither but a different communication rhythm. The problem isn't the quiet person but that most meeting structures are designed for the loudest communication style in the room. [Nechanska, Hughes & Dundon (2020)](https://consensus.app/papers/towards-an-integration-of-employee-voice-and-silence-nechanska-hughes/54f03565f3a65d2cbceaa6219a98e09b/) argue that voice and silence are two sides of the same coin and you can't understand one without understanding the other. Organizations that only design for voice through town halls and open door policies and suggestion boxes are solving the wrong problem without addressing the conditions that create silence. --- ## Four Things to Try This Month > 1️⃣ **Pre-circulate discussion topics 48 hours before important meetings.** This gives everyone time to think because reflective communicators, which includes many people from high context cultures, produce better input when they've had time to prepare. You're not slowing the meeting down but upgrading the quality of what happens in it. > 2️⃣ **Build in a written response round before the verbal one.** At the start of a discussion, give everyone 2 minutes to write their thoughts and then go around the room. This equalizes airtime and ensures quieter voices get heard before louder ones set the frame. > 3️⃣ **Follow up individually after meetings where someone was quiet.** Not with "why didn't you speak up?" but with "I'd value your perspective on what we discussed. What's your honest read?" because private channels often unlock what public ones suppress. > 4️⃣ **Audit your meeting culture for one week.** Track who speaks and how often and for how long, and most leaders are surprised by how lopsided the distribution is because awareness changes behavior. --- The most valuable insight in your next meeting might come from the person who doesn't say it out loud, and your job as a leader isn't to make everyone talk but to make sure everyone can. --- **Sources:** - [Morrison (2022)](https://consensus.app/papers/employee-voice-and-silence-taking-stock-a-decade-later-morrison/70fcfaf6ab7e53f980df610ea96bb4dd/) — "Employee Voice and Silence: Taking Stock a Decade Later," *Annual Review of Organizational Psychology*. - [Kwon & Farndale (2020)](https://consensus.app/papers/employee-voice-viewed-through-a-crosscultural-lens-kwon-farndale/6c03aab7a4815912bd66b244b3b008fe/) — "Employee Voice Viewed Through a Cross-Cultural Lens." - [Nechanska, Hughes & Dundon (2020)](https://consensus.app/papers/towards-an-integration-of-employee-voice-and-silence-nechanska-hughes/54f03565f3a65d2cbceaa6219a98e09b/) — "Towards an Integration of Employee Voice and Silence." --- *Part of the Lead Humanly series on [leadhuman.ai](https://leadhuman.ai).*https://leadhuman.ai/lead/stop-asking-start-sharing-feedback/https://leadhuman.ai/lead/stop-asking-start-sharing-feedback/Every leadership book tells you to ask for feedback. The research says that's the wrong approach. What actually builds psychological safety is sharing the feedback you've already received and it changes how your team communicates about hard topics.Sat, 07 Mar 2026 00:00:00 GMTEvery leadership book tells you the same thing: be vulnerable, ask your team for feedback, and create psychological safety. So you stand up in a meeting and say, "I want honest feedback. Tell me what I can do better," and your team stares at you and maybe someone offers something vague and safe and then everyone moves on. You did the thing the books told you to do and it didn't work. Here's why. ## The Problem with Asking [Coutifaris & Grant (2021)](https://consensus.app/papers/taking-your-team-behind-the-curtain-the-effects-of-leader-coutifaris-grant/33750b08cfff5843a1b4672821332e4b/) ran a longitudinal field experiment published in *Organization Science* that upended a lot of what we thought about feedback and psychological safety. They tested two leader behaviors: **feedback seeking** (asking your team for input on your performance) and **feedback sharing** (openly discussing criticism you've already received). Both sound vulnerable and both signal openness but only one actually worked. **Leaders who shared feedback they'd already received saw a significant increase in team psychological safety one year later while leaders who asked for feedback did not.** The researchers dug into why: when leaders asked for feedback, it created an initial moment of vulnerability that dissolved quickly because leaders got defensive and didn't act on what they heard and team members noticed and stopped offering honest input. When leaders shared feedback ("My last 360 said I tend to dominate discussions. I'm working on it."), something different happened: the vulnerability stuck and it normalized the idea that everyone has things to work on and team members started reciprocating and the door opened for more actionable, ongoing feedback conversations. --- > 🔑 **Asking for feedback initiates vulnerability. Sharing feedback normalizes it.** The difference matters. Your team doesn't need to see you ask for help. They need to see you openly working on something. That's what makes it safe for them to do the same. --- ## Why This Changes Everything About Psychological Safety [Westover (2024)](https://consensus.app/papers/how-to-create-and-maintain-psychological-safety-to-ignite-westover/4546dc8e45a059d6a9848894dbf77e2d/) identified five strategies for building psychological safety and modeling vulnerability was number one, but the Coutifaris and Grant research adds a critical detail: the type of vulnerability matters because asking "how am I doing?" feels vulnerable to you while sharing "here's what people have told me I need to work on" feels vulnerable to your team and that's the shift. I've tested this myself, and in a workshop last year I shared specific feedback I'd received about talking too fast during presentations and the room visibly relaxed and people started sharing their own challenges not because I asked them to but because I went first with something real. --- ## Four Things to Try This Month > 1️⃣ **Share one piece of feedback you've received in your next team meeting.** Not a humblebrag disguised as feedback but something real that you're actually working on like "My manager told me I need to delegate more. She's right. I'm working on it." Watch what happens to the room. > 2️⃣ **Follow up publicly on your progress.** A month later, bring it up again with "Remember when I said I was working on delegating? Here's what I've tried. Here's what's still hard." This is what Coutifaris and Grant found made the difference because sharing feedback once is a gesture but returning to it is a practice. > 3️⃣ **When someone gives you feedback, tell them what you did with it.** Close the loop by saying "Last month you told me the project timelines were too tight. I adjusted the Q2 schedule and built in buffer weeks. Thank you for saying something." This signals that speaking up has consequences, good ones. > 4️⃣ **Stop asking "any feedback?" in group settings.** It almost never works, but instead go to people individually with "I'm trying to get better at X. What are you seeing?" because specific asks in private get honest answers while broad asks in public get silence. --- Psychological safety doesn't come from saying the right words but from doing the uncomfortable thing repeatedly and showing your team that nothing bad happened. Sharing feedback you've received is one of the simplest and most powerful ways to start. --- **Sources:** - [Coutifaris & Grant (2021)](https://consensus.app/papers/taking-your-team-behind-the-curtain-the-effects-of-leader-coutifaris-grant/33750b08cfff5843a1b4672821332e4b/) — "Taking Your Team Behind the Curtain: The Effects of Leader Feedback Sharing," *Organization Science*. - [Westover (2024)](https://consensus.app/papers/how-to-create-and-maintain-psychological-safety-to-ignite-westover/4546dc8e45a059d6a9848894dbf77e2d/) — "How to Create and Maintain Psychological Safety to Ignite Innovation." --- *Part of the Lead Humanly series on [leadhuman.ai](https://leadhuman.ai).*