Employee Experience

𝗡𝗮𝗶𝘃𝗲 𝗥𝗔𝗚 𝘄𝗼𝗿𝗸𝘀 𝗶𝗻 𝗮 𝗱𝗲𝗺𝗼. 𝗜𝘁 𝗳𝗮𝗶𝗹𝘀 𝘁𝗵𝗲 𝗺𝗼𝗺𝗲𝗻𝘁 𝗿𝗲𝗮𝗹 𝘂𝘀𝗲𝗿𝘀 𝘀𝗵𝗼𝘄 𝘂𝗽. Embed → retrieve → generate looks clean in a notebook. Real requirements break it: → Questions whose answer is spread across many documents → Industry terms that embeddings get wrong → Bad chunks the pipeline never catches → Answers that live in how things connect, not in any single chunk → PDFs full of tables and images a text-only index cannot read These 5 architectures are how serious teams stay ahead in the agentic AI era: 𝟬𝟭 𝗛𝘆𝗯𝗿𝗶𝗱 𝗥𝗔𝗚 → Dense vectors find meaning. BM25 finds exact words. → Reciprocal Rank Fusion combines both ranked lists. → A safe baseline for almost every team. 𝟬𝟮 𝗚𝗿𝗮𝗽𝗵𝗥𝗔𝗚 → Pull entities and their relationships into a knowledge graph. → Retrieve subgraphs and community summaries, not chunks. → Best when the answer lives in how things connect. 𝟬𝟯 𝗔𝗴𝗲𝗻𝘁𝗶𝗰 𝗥𝗔𝗚 → A planner agent picks the right tool: vector, web, or SQL. → A reasoner agent keeps trying until the answer is solid. → Retrieval becomes a plan, not a single step. 𝟬𝟰 𝗖𝗼𝗿𝗿𝗲𝗰𝘁𝗶𝘃𝗲 𝗥𝗔𝗚 (𝗖𝗥𝗔𝗚) → Grade every retrieval before you trust it. → Correct → answer. Unclear → rewrite the query. Wrong → search the web. → This is what production RAG actually looks like. 𝟬𝟱 𝗠𝘂𝗹𝘁𝗶𝗺𝗼𝗱𝗮𝗹 𝗥𝗔𝗚 → One embedding model (CLIP, ColPali) for text, images, and tables. → One vector index. One multimodal LLM. → No more separate pipelines for PDFs with charts. I built a runnable example for each of the five patterns. GitHub link in the first comment. The best teams in 2026 do not pick one. They combine them — hybrid retrieval inside an agentic loop, with a corrective grader, over a multimodal index. Naive RAG is a starting point, not a finish line. That is why most enterprise GenAI projects stall at the demo. Which of these five becomes the default RAG stack in the next 18 months — and which stays a specialized tool?

I Can Spot a Great Candidate in 30 Seconds - Without Looking at Their Resume. At Vicco Laboratories, the first few interview rounds are handled by our HR and leadership team. They assess skills, experience, performance history - all the standard checkboxes. But when someone reaches my room, I’m not evaluating capability. I’m evaluating character. Because skills can be trained. Character can’t. So in the final round, I deliberately observe three things before we even get into formal questions: 𝐓𝐫𝐚𝐢𝐭 1: 𝐇𝐨𝐰 𝐓𝐡𝐞𝐲 𝐓𝐫𝐞𝐚𝐭 𝐭𝐡𝐞 𝐒𝐦𝐚𝐥𝐥𝐞𝐬𝐭 𝐏𝐞𝐫𝐬𝐨𝐧 𝐢𝐧 𝐭𝐡𝐞 𝐑𝐨𝐨𝐦 Before they enter, I always ask our receptionist to make them wait for a few minutes. Not to trouble them — but to observe: Do they greet her or ignore her? Do they show gratitude or entitlement? Do they smile or stay blank? Do they thank her when being called in? If someone is only respectful upwards, they’re not fit for leadership. 𝐓𝐫𝐚𝐢𝐭 2: 𝐇𝐨𝐰 𝐓𝐡𝐞𝐲 𝐇𝐚𝐧𝐝𝐥𝐞 𝐒𝐢𝐥𝐞𝐧𝐜𝐞 During the conversation, I pause intentionally. A great candidate: Doesn’t panic when things go quiet Holds eye contact without overcompensating Thinks before responding, instead of rushing to impress Silence is a pressure test.  Silence exposes a person’s comfort with themselves. And self-assured people make better decisions under pressure. 𝐓𝐫𝐚𝐢𝐭 3: 𝐖𝐡𝐞𝐭𝐡𝐞𝐫 𝐓𝐡𝐞𝐲 𝐀𝐬𝐤 “𝐖𝐡𝐚𝐭 𝐂𝐚𝐧 𝐈 𝐆𝐢𝐯𝐞 𝐭𝐨 𝐕𝐢𝐜𝐜𝐨”, 𝐍𝐨𝐭 𝐉𝐮𝐬𝐭 “𝐖𝐡𝐚𝐭 𝐖𝐢𝐥𝐥 𝐈 𝐆𝐞𝐭?” I watch closely when compensation and responsibilities are discussed. If the questions are only about salary, perks and timings, they’re employees. If they ask about learning culture, values, decision-making structure…they are already thinking as an owner. I’ll always choose alignment over achievement. So if you’re ever preparing for your final round anywhere — don’t just prepare your resume. Prepare your presence. Because long after your words fade, your character stays in the room. Sanjeev Pendharkar  Just sharing what I’ve learnt #values #business #hiring #hr #decisionmaking #cv #leadership #skills

In the early years of Marico, I made a decision that shaped everything that followed. I gave young people serious responsibility. Not after years of proving themselves. Right at the start. Real roles. Real ownership. Real consequences. Some of them made mistakes. That was expected. But they learned fast. They asked for feedback. They iterated. They took initiative. Many of them went on to become some of the best leaders in the organisation. My view is simple. If someone makes an error, but they take ownership, improve, and do not repeat it, they have earned the right to grow. If someone avoids responsibility or hides from mistakes, they are not ready. Empowerment is not about handing out titles. It is about giving people the room to fail safely and the support to recover intelligently. You cannot build a high-performance organisation if every decision needs your approval. The real test of leadership is not in how well you control outcomes. It is in how confidently you let others lead. #leadership #hiring #talent #growth #future #team #success

AI won’t kill the Scrum Master role. But it will expose the ones who were just glorified Jira babysitters. You know the type: • Runs the Daily. • Shares the Burndown. • Asks, “Any blockers?” like a broken record. AI can summarize standups, track metrics, and even write user stories The bar has moved. Permanently. What high-performing SMs are doing in 2025 to stay relevant? --------------------------------------------------------------------- 🔹 1. Sprint Planning is a Strategy Room — not a calendar block → Use AI to surface delivery risks based on historical velocity → Guide trade-offs: “Here’s the scope we can commit to with 85% confidence” → Train teams on capacity forecasting using actual throughput 🔹 2. Backlog Refinement = Opportunity to Level Up Your PO → Use ChatGPT to draft acceptance criteria, or flag logical gaps → Run backlog refinement like a product-thinking workshop → Push for clarity, not just ticket grooming 🔹 3. Retrospectives Should Feel Like a Coaching Session, Not a Routine → Go beyond “what went well” → Use AI to analyze sprint data or retro notes for patterns → Start with: “What’s draining our energy right now?” 🎯 Agile isn’t about ceremonies. It’s about conversations that lead to outcomes. Your edge as a Scrum Master isn’t your ability to remove blockers — It’s your ability to elevate the thinking of the team. In a world where tools are getting smarter… Make sure your impact isn’t just seen — but felt. 👇 What’s one AI-powered move you’re using today as an SM?

This Teacher Changes 30 Lives Each Morning Here's Why This Works Every morning, a teacher greets her students one by one - not with rules, but with choice: A hug, A high-five, a nod, or quiet. A ritual so simple. Yet it tells 30 children: You are seen. You are safe. You belong. Here’s what this teaches us about leadership - and how to apply it at work: 1. Honor Autonomy (Self-Determination Theory) When people get to choose how they engage, they show up with more agency. Autonomy isn’t about letting go of structure - it’s about giving room to opt in. Try this: 🔷 Let people set their own work cadence - async, deep focus, or collaborative sprints 🔷 Ask: “What support looks best for you right now?” *** 2. Create Micro-Moments of Connection (Broaden-and-Build Theory) We don’t need hour-long one-on-ones to build trust. A genuine check-in. A name spoken with intention. That’s the glue. Try this: 🔷 Pause to celebrate effort, not just outcomes - a quick voice note, a public thank-you 🔷 Remember small details - a kid’s soccer game, a partner’s surgery - and follow up *** 3. Signal Safety in Small Ways (Polyvagal Theory) The nervous system responds before the intellect does. Safety is felt first. And safe leaders create brave spaces. Try this: 🔷 Ask: “Is now a good time?” before giving feedback or asking for decisions 🔷 Stay calm and present, especially when tensions rise - your tone sets the tone *** 4. Design for Anticipatory Joy (Affective Forecasting) The brain lights up for what’s coming next. The ritual at the door gave students a reason to show up smiling. Try this: 🔷 Drop a kind, unexpected message in the team chat - just because 🔷 Celebrate mundane milestones - 100 days in the role, 50th client call, 1st brave no *** 5. Anchor Culture in Meaningful Rituals (Harvard Research on Rituals) Rituals are memory-makers. They codify values in action - they say, this is who we are. Try this: 🔷 End each quarter with storytelling: what stretched us? what did we learn? 🔷 Welcome new hires not with logistics, but with a story of your team's "why" *** This teacher didn’t redesign the curriculum. She redesigned how people enter the day. You don’t need a big title to lead like that - Just the courage to meet people at the door. 💬 What’s one ritual you’ve seen shift the energy of a space - or want to create where you work? 🔁 Repost to inspire kind actions in the workplace. 🔔 Follow Bhavna Toor for more on conscious leadership.

We don’t need to apologize for having children. After all, we didn’t make a mistake. We didn’t mess up a project. We brought life into this world - and that’s extraordinary. ❤️ Children are the future of our society. What I find much more questionable? Parents who don’t pick up their kids from kindergarten. Who never show up at football practice or piano lessons. That, too, says something. So instead of rushing out of a meeting with guilt in our voice to pick up our children or drive them to their hobbies, we should reshape the culture itself. Block pick-up times and kids' activities into your calendar like you would a board meeting - with clarity and zero apology. Label it not just “Personal,” but “CEO Duty: Future Generation” or “Leadership at Home.” Yes, it sounds bold. That’s the point. Even better: 💡 Bring it up in team stand-ups. Normalize it. 💡 Create a shared “Parent Hours” visibility board within your team, so others can align around it 💡 Rotate critical meeting times to avoid consistently disadvantaging caregivers. 💡 Don’t ask for permission. Model it so others stop feeling they need to either. Make your responsibilities visible, not hidden. There’s no shame in parenting. Only power in presence. Have you ever caught yourself apologizing for being a parent? I have. It took me a long time to rewire that guilt. But now I choose visibility. And so can you. #WorkingParents #Leadership #WorkLifeIntegration #NoMoreApologies #RewriteTheNarrative

In our new paper we ran an experiment at Procter and Gamble with 776 experienced professionals solving real business problems. We found that individuals randomly assiged to use AI did as well as a team of two without AI. And AI-augmented teams produced more exceptional solutions. The teams using AI were happier as well. Even more interesting: AI broke down professional silos. R&D people with AI produced more commercial work and commercial people with AI had more technical solutions. The standard model of "AI as productivity tool" may be too limiting. Today’s AI can function as a kind of teammate, offering better performance, expertise sharing, and even positive emotional experiences. This was a massive team effort with work led by Fabrizio Dell'Acqua, Charles Ayoubi, and Karim Lakhani along with Hila Lifshitz, Raffaella Sadun, Lilach M., me and our partners at P&G: Yi Han, Jeff Goldman, Hari Nair and Stewart Taub Subatack about the work here: https://lnkd.in/ehJr8CxM Paper: https://lnkd.in/e-ZGZmW9

Some SQL commands are dangerous. Like, lose your job if you mess it up dangerous. How can you avoid messing these things up? 1. If your database supports it, wrap your DELETE statements in a transaction so you can use ROLLBACK 2. Protect vital data, don’t allow your unrecoverable tables to be dropped or deleted from 3. Limit who can use the DROP or DELETE command. Yourself included if you’re untrustworthy😂 4. Don’t develop in Prod. Have two schemas, one for production data and another for development 5. Practice every DELETE and MERGE on a duplicate of the table you’re about to edit. This can you can make sure you alter what you intend 6. If your company has the ability, keep a rolling seven day backup/snapshot of your key tables. That way if something catastrophic happens, you at least have something to recover from I once deleted an aggregate table too early before I was actually ready to delete it. I ended up needing to recreate it and it was a bit painful. These little things I listed above can make SQL a lot safer. #analyticsengineering

The ability to create clarity when there’s no shortage of chaos, opinions, and competing priorities is a rare skill. In any reasonably competent company, this skill alone will help take you quite far, fairly quickly. Concretely, this means creating clarity on the main problems, clarity on the right solutions, and clarity on the action plan & priorities. Very few people can do this well even though most people possess the intelligence necessary to do it. This is because most people in the workplace have been conditioned to add more information, sound more clever, satisfy more stakeholders, and feign more precision & certainty than is possible. Few understand that clarity in a chaotic situation can only emerge from subtraction, never from addition. Clarity comes from communicating what stands out as most important, why it is most important, how it will be achieved, and last but not the least, giving people a way of thinking about why it is okay, even great, that we aren’t doing All The Other Things.