Category: Learning and Development

How to strengthen the manager-employee relationship, in both directions

Reading Time: 6 minutesThe manager-employee relationship decides more about how people work than almost anything else a company can measure. Across 2.7 million workers, Gallup found that the manager accounts for about 70% of the variance in a team’s engagement. Not pay, not perks, not the company mission. The relationship between a person and the human they report to. It is also the relationship companies leave most to chance. The standard advice, communicate more, recognize good work, hold regular 1:1s, is reasonable and mostly useless, for two reasons. It runs one direction, as if the manager is the only one who shapes the relationship. And it is generic, the same move for every person, when the whole point is that people are different. A relationship that explains most of engagement is worth building on purpose, from both sides, one specific person at a time. Get the 2026 AI coaching playbook to see how organizations are implementing AI coaching at scale. Why the manager-employee relationship explains 70% of engagement That 70% number changes where to put your effort. Knowing only who someone reports to, you could predict their engagement and be right more often than not. The relationship is not a soft layer on top of the real work. For most teams, it is the work. Trust is not a soft outcome either. People who trust their manager are more motivated, miss less work, and are far less likely to leave their jobs. Most organizations still treat the relationship carrying all of this as something that will sort itself out, with a few tips and an annual review. It does not sort itself out. It gets built on purpose, by both people in it, or it does not get built at all. Stop trying to communicate better, get specific about one relationship “I want to communicate better” feels productive and changes nothing, because it is too broad to act on. What works is narrow: one relationship, one behavior. Not “be clearer,” but “get aligned with how my manager sets expectations before a project starts.” Not “give better feedback,” but “help one specific report understand what good looks like.” Specific is what makes a relationship coachable. When the focus is that narrow, the prompt you act on is about this person and this exact gap, not a tip you have read a dozen times. In Cloverleaf that is a Coaching Focus tied to one relationship, with daily coaching aimed at the precise mismatch. Without any tool, naming the one relationship and the one behavior is most of the work. How to build a better relationship with your manager (managing up) Managing up gets mistaken for office politics. It is simpler than that: adapting to how your manager actually works so your contributions land the way you mean them to. Picture a manager who moves fast, talks fast, and reschedules your 1:1s, three priorities ahead while you are still clarifying the first. The instinct is to keep pace and hope nothing slipped past. The better move is to meet them where they take in information. Lead with the decision, not the background. Send the summary before the meeting, not after. Ask the clarifying question early, while it is cheap, instead of guessing and redoing the work. Most people do this by instinct, and they do not have to. Cloverleaf synthesizes 13+ market leading behavioral assessments into a clear read on how each person works, and shows how you and one specific person are likely to work together, where you align and where you grind. You adapt to the real person, not a guess, and the same read works for a peer or a skip-level you need on your side. A focus like “get aligned with how my manager sets expectations” surfaces where the two of you fall out of sync: priorities shift without you being looped in, or you do not learn what “done” means until after you have handed the work over. Name the mismatch and the moves get concrete. Confirm scope in writing before you start. Raise the question earlier. Match the pace they actually work at. Small changes aimed at one person are what strengthen a relationship. How to set expectations your team can actually act on (managing down) The same thing works in the other direction, where most managers believe they are clear and their teams know better. Clarity is not something said once, and it is not one email, because email is built for notification, not communication. Clarity is what a team can act on without checking twice: “do X by Y” rather than “do more,” delivered differently to different people, because the version that lands for someone wired like you misses everyone else. One report needs the full detail up front or they stall. Another needs room to think out loud before committing. A third goes quiet under pressure and will not raise a problem unless you ask directly. Leading people well means recognizing that people take in information differently, some by talking it through, some by reading, some by seeing, and adjusting to it. That is not extra work on top of managing. It is the human side of management itself. Where the read comes from matters. A general-purpose AI assistant does not know the two specific people in your situation, so anything you tell it is your own assumption handed back with more confidence. The understanding has to come from how those people are actually wired, from their own behavioral data, not a guess. How to rehearse the hard work conversation before you have it The conversations that strengthen or break a relationship are usually the ones people avoid: pushing back on a deadline, giving feedback that will sting, naming a pattern everyone has worked around. Most of us go in unprepared and replay it that night, wishing we had said it differently. Preparation changes that, and it does not require a script. Cloverleaf’s Scenarios let you run the real conversation as a role-play grounded in how

Best employee feedback software: a 2026 buyer’s guide

Reading Time: 4 minutesIf you are comparing employee feedback software, you are not short on options. The category runs from engagement surveys to full performance suites, and analysts put continuous performance management alone on track from about $2.6 billion in 2025 to roughly $8 billion by 2033. Most of these tools differentiate on the same things: survey types, dashboards, integrations, and price. The feature list is not what decides whether the spend pays off. A harder question does: does the tool actually change behavior, or does it only collect feedback? Plenty of teams buy feedback software, watch participation tick up, and see behavior stay exactly the same. This guide is built around that distinction, the main categories of feedback software and what each is good for, and the criteria that separate collecting feedback from changing it. What most employee feedback software actually does Most employee feedback software is, at its core, a collection engine. It makes it easy to run engagement surveys, request 360 input, gather pulse data, and show the results on a dashboard. That is genuinely useful. People want feedback: only one in four employees strongly agree they get valuable feedback at work, and those who do are five times as likely to be engaged, yet nearly half say they do not get it from their manager as often as they want. Collecting more of it is a reasonable response. But collection is where most tools stop, and collection on its own does not change how anyone manages, communicates, or leads. A higher survey response rate is not the same as a manager giving clearer feedback on Tuesday. That gap, between collecting feedback and changing behavior, is what to evaluate for. Get the 2026 AI coaching playbook to see how organizations are implementing AI coaching at scale. Five criteria that separate collecting feedback from changing behavior When you compare tools, these five questions sort the ones that change behavior from the ones that just gather it: Does it help feedback land, or only collect it? Collection is a form and a dashboard. Landing means the feedback is specific and delivered in a way the person can act on. Is delivery coached for the recipient? A blank text box leaves the giver to guess. Coaching grounded in how the recipient is wired tells them how to say it so it lands. Does it live in the flow of work? Feedback that happens in Slack, Teams, and email gets used. Feedback that waits in a separate portal gets forgotten. Does it embed into moments that already exist? Onboarding, reviews, 1:1s. A tool that adds a separate process competes for time it will not get. Does it measure behavior change, not just participation? Completion and response rates are activity. The signal that matters is whether the behavior the feedback was about actually shows up later. The main categories of employee feedback software It helps to sort the market by what each type is built to do, rather than by feature count. Engagement and survey platforms Tools like Culture Amp and Officevibe are built for engagement surveys, sentiment, and people analytics. Best for: measuring how the organization feels and spotting trends over time. Tradeoff: they are designed to collect and analyze at the org level, not to change how an individual manager gives feedback in a specific conversation. Performance and continuous feedback platforms Lattice, 15Five, and Betterworks combine reviews, check-ins, goals, and feedback in one place. Best for: running structured performance cycles and tying feedback to goals. Tradeoff: feedback is organized around forms and cycles, so these are stronger at structure than at coaching the moment-to-moment delivery that actually changes behavior. Real-time and 360 feedback tools Reflektive, Trakstar, and similar tools focus on lightweight feedback requests and 360 reviews. Best for: gathering multi-source input quickly and on a cadence. Tradeoff: like the others, the center of gravity is collection, with little support for what happens after the feedback is gathered. See How Cloverleaf’s Platform Works Try a Demo Request A Cloverleaf Coach Demo Where Cloverleaf fits with employee feedback tools, and where it doesn’t Cloverleaf is not an engagement-survey tool, and it is not a performance-review suite. It is a team performance platform built on 13+ market leading behavioral assessments, and feedback is one feature within it. So it does not belong in a head-to-head on survey templates or eNPS dashboards. If what you need is org-wide sentiment surveys, one of the engagement platforms above is the better fit. Where it fits is the five criteria. Cloverleaf’s feedback is coached by the recipient’s behavioral data, so the giver gets told how to make it land for this specific person. It runs in the flow of work, in Slack, Teams, and email. It connects to practicing the conversation first and to coaching that reinforces the change between conversations, and it can check whether the behavior actually changed. It is built for the part most feedback tools skip, turning collected feedback into changed behavior. Across 45,000 teams, 86% of users report improved team performance within 30 days. If your goal is behavior change rather than collecting input, that is the category to evaluate. Questions buyers ask when choosing feedback software What is the best employee feedback software? It depends on the goal. For org-wide sentiment, an engagement platform. For structured performance cycles, a performance management tool. For feedback that changes how managers and teams actually work, a team performance or coaching platform. Match the tool to the outcome you are accountable for, not to the longest feature list. Do we need a dedicated feedback tool? If the goal is collecting sentiment, a survey tool may be enough. If the goal is changing behavior, a standalone feedback tool usually is not, because collection is only the first step. Feedback changes behavior when more happens after the request. What is the difference between a feedback tool, a performance tool, and a coaching platform? A feedback tool collects input. A performance tool structures reviews and goals. A coaching platform

Change management coaching that reaches your whole team

Reading Time: 7 minutesWalk into most change management coaching and you will find exactly one person being coached: the executive leading the change. Six sessions, a certified coach, a careful plan for the leader at the top. Meanwhile the reorg they are running has just reshaped forty teams, and not one of those forty managers, or their new reports, is getting any of it. That is the problem with how change management coaching is usually sold. It treats change as something that happens to a senior leader. Change happens to everyone on the org chart at once, the same week, and the people furthest from the coaching are usually the ones doing the most adjusting. Coaching that keeps teams performing through change has to reach everyone the change touches, in the flow of their work, starting the day the org changes. That is a different thing from what the market sells, and it is the thing that decides whether a reorg recovers or stalls. Why most change management coaching never reaches the team Most of what gets sold as change management coaching is one of two things, and neither reaches the team. The first is one-on-one coaching for the senior change leader. The second is certification, a methodology like ADKAR or Kotter taught to the people who run change for a living. Both are useful. Both stop at a handful of senior people, and neither reaches the managers and employees who have to change how they actually work, the day the change lands. It helps to separate the three things that get blurred together. Consulting designs the change plan and hands it over. Certification teaches a method. Coaching develops how people actually work through the change while it is happening. A reorg may need all three, but only the coaching piece touches the relationships and behavior that decide whether the change holds, and the versions on the market aim that coaching at one person. The evidence says the team is where change breaks. Gartner found that only 32% of business leaders report healthy change adoption, and 73% of HR leaders say their people are fatigued by change. Around 74% of HR leaders say their managers are not equipped to lead it, which is why leader and manager development has been HR’s top priority three years running. The plan is rarely where a reorg fails; the people are. Coaching everyone the change touches sounds like more than any HR team could do by hand, and it would be, by hand. It does not have to be. When coaching connects to the systems that already know about the change and shows up where people already work, reaching everyone becomes the default instead of the exception. Get the 2026 AI coaching playbook to see how organizations are implementing AI coaching at scale. The 4 rules of change management coaching that reaches the whole team Each rule maps to a moment where reorgs usually go wrong, and to the people who usually get left out of the coaching. 1. Start the day the org changes, not weeks later The people who most need support in a transition are the ones whose team just changed shape, and they are the people whose new reality is not in any system yet. Someone has to update a roster, schedule a kickoff, remember to loop in HR. By the time that happens, the team has already set its habits, often the wrong ones. Because Cloverleaf reads organizational context from your HRIS, the day a change hits the org chart it can begin coaching the new manager and their new reports, with nothing to update and no admin task to remember. Even without a tool, the move is the same: set one coaching focus for the transition and hold it for the six to eight weeks the change will take, instead of letting attention scatter. Support should show up the morning after the reorg, not a month later when the damage is already set. 2. Give every new team a read on each other from day one Every new team starts the same way. Nobody knows how anyone else communicates, decides, or behaves under pressure, so the first months go to figuring each other out through friction that was avoidable. A team expected to deliver in week two cannot spend until month four learning how its own members work. The fix is to hand people that read before the first meeting instead of after the first conflict. Cloverleaf synthesizes 13+ market leading behavioral assessments into one view of how each person works, and shows how a specific group is likely to work together, where they align and where they will grind. A manager can name those dynamics out loud and set working agreements in week one. The same read works for a cross-functional group that has to perform before it has time to gel. 3. Tailor the change to each person, not one message for everyone Resistance gets treated as one problem, so everyone gets the same announcement and the same deck. But one person needs certainty before they will move, another needs room to explore, and a third goes quiet under pressure and says nothing until they have already started looking for the door. The same message lands for the people wired like whoever wrote it and misses everyone else. Coaching everyone through change means meeting each person where they are. Knowing in advance who needs context before direction and who pulls back under pressure lets a manager shape the same change differently for different people. Cloverleaf delivers that as plain-language coaching in the moment, grounded in each person’s behavioral makeup, so a manager walking into a hard conversation knows how to make the change land for this specific person. It is the same thinking behind building relational intelligence into change, one conversation at a time. 4. Rebuild trust after a layoff, before more people leave After a layoff or reorg, the people who stay carry the same expectations with

emotional intelligence and effective leadership

The Feedback Was Right. The Framing Was Wrong.

Reading Time: 4 minutesI manage 10 direct reports. We do quarterly feedback, bidirectional, which means I start by asking them what they’d like me to continue, start, stop, or do differently. Then we flip it. I’ve run this cadence for a while. Before my last round, I was better prepared than usual. I’d been syncing Granola meeting transcripts and 1:1 notes into Claude, so I could pull themes across months of conversations, not just whatever I happened to remember from the past two weeks. I had the patterns. I knew what I needed to say to each person. I had already said most of it before. One in Three Feedback Conversations Makes Performance Worse, Not Better That’s not a rhetorical point. A landmark meta-analysis by Kluger and DeNisi examined 607 studies and found that over one in three feedback interventions actually decreased performance after they were delivered. Not neutral. Worse. Their explanation: feedback becomes less effective, and sometimes actively counterproductive, the closer it gets to the person’s sense of self. When feedback touches something someone considers core to who they are, the brain stops processing it as information and starts processing it as threat. When that happens, people don’t change. They cope. They dispute the feedback, reinterpret it favorably, lower their goals, or agree in the moment and move on. The feedback is accurate. It doesn’t matter. I had been watching this play out with one of my direct reports. Get the 2026 AI coaching playbook to see how organizations are implementing AI coaching at scale. The Same Feedback Didn’t Land — Until Managers Can Change How They Frame It  One of my direct reports is genuinely one of the most helpful people I work with. When someone asks if something is possible, they’ll say yes, enthusiastically, warmly, and then go on to explain everything they’re going to do and how. It comes from a real place. But in a startup where context switches fast, that pattern creates noise. Someone asks a quick question and gets a five-minute answer. The feedback I needed to give was simple: just say yes and move on. Not every question needs a full response. I’d said something like this before. They understood it, nodded, and seemed to take it in. It came up again anyway. This time, I prepared differently. I was using Cloverleaf’s MCP integration alongside my meeting notes, pulling together patterns from past 1:1s and layering in behavioral data from assessments into the same context. Not just what had been happening, but additional signals about how this person tends to operate and how feedback like this might land with them. The output didn’t just give me talking points. It added guidance on how to frame the feedback for this specific person. It surfaced the same theme, and then added more helpful nuance and insight: “This is the single most personality-driven behavior. This person is very people-centered in nature, and helpfulness feels like an identity to them — not just a habit. Be careful here. If they hear ‘stop being helpful,’ that will land as a rejection of who they are. Instead, frame it as how they channel their helpfulness.” See How Cloverleaf’s AI Coach Works Try a Demo Request A Cloverleaf Coach Demo When Feedback Touches Identity, It Stops Being Processed as Information I stopped when I read that. Because I realized what I had been doing, even without using those exact words, was telling someone to stop doing the thing that feels most like them. For someone whose helpfulness is core to their identity, that isn’t a coaching note. It’s an identity threat. The research on this is clear. Studies on how people respond to identity-threatening feedback consistently show the same pattern: people cope rather than change. They dispute it, misremember it more favorably, or reduce their commitment to improving, none of which is visible in the moment. They nod, they move on, and nothing shifts. The feedback wasn’t wrong. The frame was. The reframe the system suggested: “Your helpfulness is one of your superpowers. The change is about being strategically helpful, directing it where it can have the most impact, not diffusing it across every moment.” Same observation. Completely different frame. Their response when I used it: “Yeah, that’s spot on.” And then the conversation actually opened, they had thoughts about specific situations, ideas for what strategically helpful would look like day-to-day. It became a real exchange instead of something they were getting through. What Behavioral Data Does That Performance Data Can’t Most of what gets written about AI and feedback is focused on improving the data collection side: surfacing patterns across performance reviews, reducing recency bias, generating first drafts of assessments. That’s genuinely useful. Gallup research shows that employees who receive frequent, specific feedback are nearly four times as likely to be engaged, and better preparation helps managers get there. But performance data tells you what happened. It doesn’t tell you how to talk about it in a way this specific person can actually receive. That’s a different problem. The information about the helpfulness pattern was solid. What I was missing was context on how that pattern connects to this person’s identity, and therefore how I needed to frame the conversation for them to actually hear it. That’s what the assessment data surfaced. Not a profile to study before a review cycle, but a specific note in the preparation flow: here’s how this person will likely receive what you’re about to say. Before the conversation, not after. Giving Effective Feedback Gets Harder the More People You Manage I know my team. I spend real time with each person. But managing 10 people at a startup — across product, customers, recruiting, and everything else — means the nuanced detail of how each individual thinks doesn’t stay in active memory. Some of it slips. Some of it I never had clearly to begin with. This isn’t unique to me. Research on continuous feedback finds that feedback quality, specifically how well it accounts for

four people are sitting at a table while one of them shows the others something on their laptop

The 5 Gaps of Team Diagnostics and How AI Coaching Closes Them

Reading Time: 8 minutesWe’ve been getting requests lately for team diagnostics. Organizations want to understand why their teams aren’t performing, why collaboration feels difficult, why certain dynamics keep creating friction. Team diagnostics serve a purpose. They identify patterns. They give you data about where trust is lacking, where conflict is being avoided, where accountability breaks down. That baseline understanding matters. But diagnostics are a starting point, not a solution. And they’re often misused as if identifying the problem is the same as solving it. A team diagnostic tells you “your team avoids conflict” in March. It doesn’t tell you what to do in May when you’re sitting in a room with two teammates—one who communicates directly and pushes for fast decisions, another who goes quiet when tension rises—trying to make a decision about the product roadmap, and you can feel the unspoken disagreement building. The diagnostic gave you the pattern. It didn’t give you the guidance for this specific moment with these specific people and their different communication styles. That’s not a flaw in diagnostics. It’s a structural limitation of point-in-time team assessments. Understanding this limitation helps you know what infrastructure to build next. Get the 2026 AI coaching playbook to see how organizations are implementing AI coaching at scale. Five gaps between team diagnostic insights and actual team behavior change 1. Single-framework diagnostics force every team problem into the same model Most team diagnostics are built on a single framework. You’re measuring trust, conflict, commitment, accountability, and results. Or you’re assessing psychological safety and cohesion. Or you’re evaluating communication patterns. The framework determines what gets measured. What gets measured determines what gets addressed. But teams don’t fail for the exact same reasons. A product development team struggling with decision speed has different problems than a client service team struggling with handoffs. A newly formed team trying to build trust faces different challenges than a long-tenured team dealing with stagnation. When you force every team’s problems into the same diagnostic model, you miss the specific dynamics actually creating friction. The framework becomes the lens—not the team’s reality. See How Cloverleaf’s AI Coach Works Try a Demo Request A Cloverleaf Coach Demo 2. Team-specific problems don’t always fit into diagnostic frameworks Even when a framework is relevant, it’s often too broad to guide specific team interactions. “Your team lacks trust.” Okay. What does that mean when you’re managing Jordan and Alex? Is it that Jordan doesn’t believe Alex has the technical competence to execute? Is it that Alex doesn’t feel psychologically safe disagreeing with Jordan? Is it that neither of them trust the priorities because decisions keep changing? “Your team avoids conflict.” Sure. But what does that mean for tomorrow’s product roadmap meeting? Does Jordan need permission to be more direct? Does Alex need structured turn-taking so they don’t get talked over? Do you need to model productive disagreement yourself so the team sees it’s safe? The diagnostic label tells you there’s a problem. It doesn’t tell you how to manage the relational dynamic between these two specific people in this specific meeting. Consider this example: Sales team at a SaaS company. Diagnostic said “team avoids accountability.” Recommended solution: institute peer accountability practices. Have team members hold each other accountable, not just the manager. Sounds great. Here’s what the diagnostic didn’t know: This team was 100% commission-based. Highly competitive. Low trust because everyone was protecting their deals. When they tried to introduce “peer accountability,” it got weaponized. People used it to undermine each other, point out mistakes, protect their own numbers. The diagnostic recommendation assumed moderate trust and collaboration as a baseline. This team had neither. The “solution” made things worse because it didn’t account for the specific relational context and incentive structure. 3. Team dynamics change faster than diagnostic cycles can capture You run the diagnostic in March. Results say the team struggles with psychological safety. You do the debrief. Two people admit they don’t feel safe disagreeing with the manager. Manager says “I want you to push back on me.” Everyone feels good. April: Manager is under pressure from their VP. Someone pushes back on a decision in a meeting. Manager gets defensive. Shuts it down. The person who pushed back thinks “See? It’s not actually safe.” They stop engaging. May: New person joins the team. They don’t know the diagnostic happened. They don’t know the “team struggles with psych safety” context. They observe the quiet team and adapt to that norm. June: You’re still operating off March data that said “psychological safety is the issue.” But now the issue is “new team member doesn’t have context,” “manager’s behavior under pressure contradicts stated values,” and “team has adapted to silence as the norm.” The diagnostic can’t see any of that. It’s frozen in March. Teams aren’t static. They’re living systems that adapt constantly to new members, pressure shifts, reorganizations, and changing priorities. 4. Generic team recommendations ignore the context that determines whether they’ll work Ideal team behavior depends on context. What works for a team that’s been together for three years doesn’t work for a team that formed last month. What works for a high-trust environment where people can be direct doesn’t work in a low-trust environment where directness gets misread as aggression. Team diagnostics measure general patterns. They don’t account for: Whether this team is new or long-tenured Whether they’re under intense deadline pressure or in a planning phase Whether they’re co-located or distributed across time zones Whether their work requires deep collaboration or parallel execution Whether the leader has credibility or is still building it Whether compensation structures create competition or collaboration Whether team members have existing relationships or are strangers Generic recommendations applied to specific contexts don’t land. The advice makes sense in theory. It doesn’t fit the actual situation this specific team is navigating right now. This is part of a broader shift happening in talent development—away from episodic interventions and toward continuous infrastructure that adapts to real-time context. For more on this structural change, see why

people skills for managers

How to Support New Managers in Their First 90 Days

Reading Time: 4 minutesNew managers are stepping into a role they’ve never done before, expected to lead people they don’t yet understand, often without the insight or support to do it well. What makes this particularly challenging: the people who get promoted to people leadership are the people who are really good at doing the job—doing the tasks, knowing the competencies, the skills they need to perform. But not necessarily at leading people. They don’t necessarily have a track record of being really good at advocating for people, at developing people, at coaching their peers, at giving hard feedback. The first 90 days are when patterns get established. When a new manager either builds confidence or develops habits that will hold them back for years. So let’s find ways to support our managers in their first 90 days. Get the 2026 AI coaching playbook for talent development to accelerate team performance. What new managers need from day one First-time managers immediately struggle all with the same thing. And that is being able to see all of their different individual employees and know what they need for success. Know how they get motivated. Know how they handle stress and challenge. Know how they handle change. Do they embrace it? Do they hide from it? Every employee is going to be different. And the manager needs to be ready to lead every individual in their strengths and aware of their blind spots. But the managers are given no insight into this information and no support and training into how to actually implement support to every employee. Yes, we may, in the best case scenarios, train them on one-size-fits-many frameworks, but that is not helpful in the flow of work when they are just too busy to go back and recheck a training that they had and when what works for one person doesn’t work for another. Even new leaders with the best of intentions—who in interviews talked about how they want to support employees, talked about who developed them and how great it was for their career and how they want to give that back—those good intentions don’t withstand the stress of reality when the manager simply is a deer caught in headlights and does not know what to do. See How Cloverleaf’s AI Coach Can Support New Managers Try a Demo Request A Cloverleaf Coach Demo How to provide insight new managers need in the first 90 days The first 90 days are when patterns get established. When a new manager doesn’t know how to read their team, doesn’t have insight into individual differences, and doesn’t get support in those early critical conversations, they default to what feels safe: treating everyone the same, avoiding difficult conversations, or mimicking whatever management style they experienced themselves—even if it wasn’t effective. Give new managers the data they need to understand their team Today, we can take all the data that we have on what matters to that manager—who are they leading? What’s their past performance review? What’s their career path and goals? What is true in the employee engagement surveys of that team? We can combine that with real-time context: Who are they meeting with? What’s happening on their calendar? What is their own development goal? And put those together with an AI coach that can come into their flow of work and nudge them before their one-on-ones. Nudge them with the leadership competencies that matter to your organization. Give them outlets where they can practice conversations with role play or process thoughts with an AI coach that will help them understand their own unique strengths and how to approach a situation. New managers need both tactical information and behavioral insight Sometimes the information they need is tactical—yes, this is what you should focus on in your first one-on-one with this employee, or this is how this person prefers to receive feedback. But often the insight they need is more about building their inner confidence, their wisdom, their fortitude to overcome what blocks them as a leader from having successful, uncomfortable conversations. Maybe it’s helping them not to talk most of the time and not to steamroll the conversation, but helping them ask the right questions to better understand the perspective of the employee. Maybe it’s helping them understand that as a manager, they care a little too much about being liked and there are actually tactics they can employ to care more effectively about holding accountability—because that is truly caring for the employee. It’s helping them grow. Behavioral assessments reveal what new managers can’t see on their own Whatever it is, every individual has our own complicated blockers that keep us from engaging in coaching, engaging in accountability, engaging in developing the people around us. And the best informed AI coaches can know this. That’s why organizations partner with leading behavioral assessments like DISC, Enneagrams, and Clifton StrengthsFinder. These assessments help unveil the complicated thought patterns that every individual has—patterns that hold us back or make us go a little too far too fast. All of that can be exposed, understood, and used to inform the AI coach, along with all that HR data, to help every single person develop themselves and develop each other. And especially for new managers stepping into their first leadership role, this support can mean the difference between confidence and confusion in those critical first weeks. Building the foundation before the transition happens In organizations that have been equipping their managers with AI coaching for years, they have a whole culture of understanding each other, of developing each other—not depending just on leaders, but every employee being able to grow in their emotional intelligence and grow in their ability to have candid conversations with each other, upwards, downwards, or sideways, whoever they are working with. They have developed their relationships and their capacity and their wisdom and their strength to lean into the situation with the people around them. The compounding effect: culture before promotion + support during transition When