BLOG

Wed 24 June 2026
 “I told them that we are transitioning to this new process. Why are they still using the old process?”

“This new generation just doesn’t know how to work. When I entered the workforce, putting in 80-90 hours per week was normal and expected. These recent graduates just don’t have the same work ethic as we did when we graduated and it is causing me to question whether or not we can even hire recent graduates anymore.”

“We practice open book management! How could our people possibly think we were giving out holiday bonuses?! We have had 3 down quarters in a row! We might have to lay people off in the next few months.”

“I am pretty sure my people know the difference between the ideas I share that are future-focused and 6-12 months out and which ones are urgent.”

As a facilitator of executive mastermind groups, I hear these things ALL THE TIME.

It is easy to just fire people and write them off as a lost cause and hope the next person will fare better. But the reality of the situation is that if the next person is better, it isn’t because of the leader’s ability to develop that employee, but because of what that person brought to the table that their predecessor didn’t. 

A leader can look at the hiring and firing of individuals as criteria for future hires - e.g., if my hires with 10+ years of experience in this field consistently perform better than those who have less experience, then I will just hire only experienced people. The issue with this is that:

  1. Those people with more experience tend to be more expensive and
  2. There isn’t a guarantee that they will be successful because the system and process for developing the individuals in their role isn’t built - it is just based on the hope that their prior training will make them ready for this role.

As executives, we must be thinking about our business in terms of what we can control.

If we are frustrated with our people for not performing the way we want them to or or for making requests we believe are unreasonable, the only people we can blame are ourselves.

This article will cover 3 crucial tips for ensuring our teams actually hear, digest, and respond to the information we share with them. 

The first step to ensuring that our teams actually hear, digest, and respond to the information we share with them is aligning on the problem to be solved.

There is a major gap between the way the CEO/Owner views a change initiative compared to the way a non-owner executive views a change initiative. A CEO/Owner feels far less pressure from a failed change initiative compared to a non-owner executive. Why? Because if they own the business, they eat the cost of the mistake. It stings, but it doesn’t come with the perceived scrutiny of a non-owner failing to successfully lead a change initiative. 

When a non-owner executive gets the opportunity to drive a change initiative, it is a special opportunity. To quote Eminem, “Are you going to capture it or let it slip?”

This perceived scrutiny can lead to doubling down on failed change initiatives, creating strain on the rest of the organization, and turning a minor mistake and turning it into a catastrophe. 

These executives often feel a deep sense of ownership over the change initiative - and oftentimes it was their idea! If it fails, will they get another chance to lead another change initiative? This is the question running through their minds.

As the CEO/Owner, we must align on the problem to be solved and make it the company’s mission to solve this problem. For example, if the problem is that we need a better way to track customers and past prospects, a potential solution could be to implement Salesforce. If the Salesforce integration fails, does that mean the company doesn’t need a better way to track customers and past prospects? No! The problem is still there and it requires a pivot to a new solution to solve the problem.

This helps reduce the pressure non-owner executives face when rolling out a solution. It gives them the comfort of knowing that everyone is aligned around solving the problem and that the proposed solution is simply our first attempt at addressing it.

If Salesforce isn't working, that doesn't mean we gaslight people who are struggling with the implementation by telling them that things will eventually get better. Instead, it means we start asking questions. Why isn't it working? What alternative solutions exist? Would those alternatives face the same challenges?

If we determine that every alternative would create similar issues, but solving the problem outweighs the pain of implementation, then we stay the course. However, if the pain outweighs the benefit, or if another option exists that would avoid these issues, then we pivot.

The point is that, as CEO/Owner, we must create a culture where the organization aligns around the problem to be solved rather than becoming overly attached to a specific solution.

The second step to ensuring that our teams actually hear, digest, and respond to the information we share with them is making it clear how the ramifications of failure impact everyone at the company, not just individuals.

When consequences are individualized, it creates a lack of empathy across the organization. 

“If we don’t get this project across the line in time, it will create a major loss for our department’s Profit & Loss statement and significantly impact our team!”

“That sucks…for you. But our team isn’t measured based on your Profit & Loss statement and we are working really hard on projects for other departments.”

If we are rolling out a change initiative across the company, the consequences of failure need to be real, authentic, vulnerable, and relevant to EVERYONE IN THE ORGANIZATION. 

Bad example, “We are rolling out a new ERP (Enterprise Resource Planning) system to help us manage our inventory and make us even better than we were.” Motivation for implementation = low. Why? There is no clear driving force for why the company needs to change and no clear consequences if change isn’t followed.

Good example, “We are rolling out a new ERP (Enterprise Resource Planning) system. We are currently less profitable than our competitors and because their ERP systems allow them to be more efficient, they can charge clients lower prices while still maintaining profit margins. As a business, at this rate with our current system, we fear we will not be able to compete with our competitors and if we aren’t able to compete with our competitors, we may not be able to exist as a business moving forward. I am not sure that this new ERP system will solve all of our efficiency problems, but we have to give it a try because failure to become more efficient means failure of the business. I am leaning on everyone in the company to help endorse and embrace this change so that we can more effectively compete and continue to do what we are doing with our business.” Motivation for implementation = high. Why? There is a very clear driving force for why everyone should buy into the new ERP system. If we don’t, it isn’t just 1 or 2 people potentially losing their jobs…we all lose our jobs because the business ceases to exist.

The third step to ensuring that our teams actually hear, digest, and respond to the information we share with them is making the rewards of following the change individualized.

When rewards are grouped, it creates a lack of incentive to work hard because if we hit a group metric, we all get rewarded. 

Individual rewards ensure that those who are working their tail off to implement a change and drive the business forward get rewarded for their efforts, and those who aren’t all in on the change aren’t. 

No action is still an action. When an organization has a poor performer and does nothing about it, it quietly tells everyone at the company that poor performance is tolerated. When individuals get rewarded for strong performance and buy into new change at a higher rate than those who don’t buy in, it sends a positive message that strong performance will be rewarded.

In essence, if we are to close the gap between what leaders say and what employees hear, we must align on the problem to be solved, make the consequences of failure group-based, and reward top performers and early adopters individually.


 
Fri 19 June 2026
 Every leader has faced the moment when they need to make a tough call, and there's no one around to help. In the past, the answer was always to hire a consultant, but consultants are expensive, and the advice didn't always satisfy. Today, there's one standing right in front of us, for a fraction of the price, AI. 


​Leaders are not just using AI for proofreading emails; they are using it to think through problems and explore new ideas. The ones that implement AI into their workflow are the ones that position themselves for a real advantage.

  • Think about the last time you made an important decision and the decision really mattered. Did you get another opinion before making it?


That's one of the biggest ways AI can help. It gives a second perspective, helps you think through options, spot blind spots, and make more informed decisions.



AI is A Thinking Partner


As an executive, you need to think through some decisions carefully. Every angle and potential pitfall has to be considered before you commit. AI can be the sounding board that helps you work through decisions like these.


​For example, if there was uncertainty about hiring, price changes, or a difficult conversation, you can explain the situation to AI and ask for another perspective. It can point out risks and benefits, helping you think through how to address them to make an idea more concrete.





AI Understands Customers


Another powerful use of AI is to help businesses understand what customers are looking for and what they are saying about the company.


​Every day, your company receives various emails, suggestions, and comments. But this feedback often gets so flooded that you don't have time to go through it.


But using AI, it can help by:




  • Filtering through customer suggestions
  • Drafting responses to common questions (FAQs)
  • Summarizing customer conversations
  • Analyzing recurring complaints
  • Surfacing what customers actually want


Instead of wasting time sifting through messages one by one, AI can speed through the entire backlog of feedback and create quick summaries of what customers are experiencing and where the company can improve.

  • If there was one problem that customers were constantly complaining about, would you want to know and be able to mitigate it immediately?


If the answer is yes, then AI is there to make that happen effectively and efficiently.





How to Start Using AI


AI is something that is here to stay, and companies should consider adopting it to improve productivity.

  • Bringing Real Decisions to AI
    • Describe the actual situation that your company is facing, and use AI to think through the possible solutions.
  • Running AI Training Session 
    • The biggest hurdle with AI adoption is that people who have never used AI are less likely to start. To stay competitive, your company should start implementing training for employees so they can gradually build AI into their everyday workflow.
  • Using AI as a Communication Assistant
    • During meetings, show how AI has helped shape an idea or bridge a gap in your thinking. This helps other employees see how AI can support a more concrete and consistent idea.


AI Can Not Replace


Many leaders fear that adopting AI means replacing their people. That fear is understandable, but misplaced. AI can handle tasks, but it cannot replace what makes a company worth working for. 

  • It can never take over the relationship between an employee and their clients.
  • It can never replace a company's history and what has been built over the years.
  • It can never replace the personality and culture that the people in a company have built


The leaders who thrive won't be the ones who fear AI.  They will be the ones who learned how to use it. 


 
Fri 22 May 2026
Marcus has been in this role for six months now. He leads a variety of cross-functional initiatives. He is in charge of a team that is dependent on product, engineering, and operations. They all have clear timelines, with each production depending on the other. Every team knew what they needed to do and when they needed to deliver.


​There was agreement in the room, but progress stalled. Marcus depended on other team managers to handle their tasks, yet the work stopped. Deadlines slipped, and Marcus lacked direct authority over those teams. He watched the project he was responsible for begin to crumble.


When Authority Doesn't Follow Accountability


Cross-functional leadership
is among the most challenging roles in any organization. They are responsible for outcomes, but cannot influence the inputs. Most leaders facing this challenge either escalate issues, risking relationships, or absorb dysfunction, risking burnout.


Neither of these solutions are durable; they both fail for the same reason. They are trying to solve an accountability problem with tools, but the real issue is a structural issue. 

  • Why does cross-functional accountability break down when everyone says they are aligned?


Marcus’s situation is built on layers of complications. The CEO was a public supporter of this initiative. In every situation, like meetings and one-on-ones, the message was clear: everything was going to get done. But privately, when the other managers came to the CEO, he didn’t think the team needed to prioritize these goals, and the CEO would let it go. He would tell the managers it was okay to deprioritize it. As a result, it caused a ripple effect in Marcus’s team, where he had a mandate but no backing to enforce it, and the other team had already learned they didn't have to move.



The Root of the Problem


The problem isn’t the other managers, and it is easy to frame someone who isn’t delivering. But in this situation, they are just listening to their CEO, and teams adjust to the behavior of what they see is happening. If there are no follow-ups with missed deadlines, then they file that way.  


If employees learn that nothing will happen if they miss deadlines and avoid work, they will keep doing it. They see if leadership avoids those difficult conversations and does not enforce rules, they have no reason to change.

  • How do teams learn what is actually expected of them versus what is said out loud?


The issue is not solely with the underperforming manager. The bigger issue is the culture of the workplace, where accountability does not exist because leadership is not willing to step up and address these problems.


In Marcus’s company, this problem grew over time. The previous leader hadn’t avoided conflict. He would foster an environment built on fear. The new CEO who stepped in wanted to change that. But in the process, a lot of things got lost. The CEO confused not being toxic with not holding the line. Without anyone willing to enforce these commitments, people learned they could opt out without consequences.



CEO Ripple Effect


​When a senior leader publicly embraces an idea, but they privately undermine it, not one project is affected. On the outside, the company looks strong and buoyant, but on the inside, accountability is being negotiated.

  • What does it signal to an organization when public commitments and private decisions don't match?


​The CEO was trying to avoid being someone who creates fear and pressure. Sometimes, there are situations where a previous leader has created an environment fostering fear, and the new leader doesn’t want to replicate it. But this situation has fostered kindness and dysfunction. ​



How to Lead When the Ceiling Has Holes In It

  1. Structural Problem That Needs To Be Solved:


Rather than escalating to frustration, it is imperative to question whether cross-functional accountability works in the organization. The conversation with leadership should focus less on blaming individuals and more on understanding the process itself. That means asking questions such as who is responsible when two teams disagree, how decisions are made across departments, and what happens when an important dependency gets dropped. The goal should be to identify weaknesses in the system and improve the process so similar problems do not continue to happen in the future.

  1.  Cost of Inaction:


It is important that everyone becomes aware of the cost of poor teamwork. With leaders brushing it off and excusing delays, it can create real damage. For example, identify which customer deliverable will be delayed, how long the delay will last, and who will ultimately be affected by it. When people can clearly see the direct outcome of inaction, the issue feels more real and urgent, which often encourages faster collaboration and problem-solving. 

  1.  Building Systems Fostering Teamwork:


Creating initiatives that can foster teamwork is one of the most effective ways to mitigate such problems. Setting up peer reviews, shared goals, and cross-team meetings where problems are discussed. The most important part is making problems aware to everyone in the room, not just the individuals who are directly impacted by them. When things are openly acknowledged in front of multiple teams, social accountability often motivates people to act more quickly. 



The Deeper Issue


The goal is to build a culture where agreements mean something, where yes in the room translates to action in the work, and where the gap between public alignment and private behavior doesn’t exist.


 
Fri 22 May 2026
 In many organizations, high performance can unintentionally hide the early warning signs of burnout. When a team consistently delivers, leaders often assume the system is healthy and the workload is manageable, even when the reality underneath tells a different story. This disconnect becomes especially dangerous for middle managers, who are responsible for translating executive expectations into day‑to‑day execution while also protecting their teams from burnout. Without clear communication about capacity, leaders begin to rely on output as the only indicator of what a team can handle, creating a cycle where strong performance is met with even more work, despite the health of the team behind it. 

Take Ben, for example. Ben has a high-performing team of 5 individuals. They meet deadlines, deliver quality work, and rarely fall behind. On the outside, everything is going perfectly. But behind the high-performing team are excessive overtime hours, burnout, and unsustainable workloads. Ben goes to his executive about expanding his team to meet demands, but after the team is expanded, they’re given another huge project. In the executive’s mind, Ben’s team can handle more work now that they have extra hands, but the reason Ben requested the extra hands in the first place was that his team was struggling with the work they already had. 

The core problem in this situation is executive misinterpretation of performance signals. Because Ben’s team consistently delivers, leadership assumes expanding the team will expand their capacity. They interpret the high performance as, “they aren’t struggling, and therefore they can handle more.” What leadership fails to see is that the team is being held together with unsustainable effort. Long hours might work well in the short term for meeting deadlines and major projects, but over time, this will lead to burnout, losing high performers, and damage trust in leadership.

Every time capacity increases, leadership fills in with more work. This results in a loop of the team constantly being overloaded, no matter how much the headcount is increased. The reason this happens isn’t unfair leaders trying to overload the teams they oversee; it is instead caused by the disconnect between the metrics viewed by leaders and the lived experience of the team. Executives look at the data, and when metrics are good, they have no reason to assume the system is unhealthy. Luckily, the solution to this disconnect is simpler than one might expect. First, the team needs immediate strategies to stop the issue currently at hand, then all parties must find structural changes to prevent this from happening in the future. 

Ben’s Job: Stabilizing the Situation
Before focusing on any structural changes, the issue must first be brought to light. Here are 3 easy steps to stabilize the situation.

Step 1: Create a Capacity Report: One of the easiest ways to show your team would thrive with a lighter workload is to quantify that workload with a documented capacity report. This capacity report should show real data that can be used as evidence that the team is over capacity in the first place. This can include hidden overtime (weekends and evenings), tasks currently in backlog, tasks that have been delayed or dropped, and any impact on quality. This way, there is tangible evidence of a team being overworked, rather than having to go by someone’s word.

Step 2: Be Clear about Priorities: Understaffed teams must be very intentional with the work they prioritize, and be able to clearly communicate those priorities as well as their reasoning. Create a simple list of priorities, starting with what you must do (essential tasks), then what you should do (important but deferrable), and finally what would be nice to do. (only if the capacity exists) This way, if the CEO introduces a new task, the team can ask, “What can be deprioritized to make room for this new task?” This forces a conversation about trade-offs and acts as a gentle reminder that no one team can do it all.

Step 3: Make Boundaries Non-negotiable: For a team to be protected from burnout, clear boundaries need to be in place. Chronic overload as a result of skipping breaks and working outside of normal hours accelerates burnout and absenteeism. Having simple team norms, such as mandatory lunch breaks, no weekend work unless there's preapproval, and setting a hard stop time for evening hours, creates guardrails that protect capacity and prevent overextension. 

Leadership’s Job: Structural Fixes
Once the team has stabilized the immediate situation, the responsibility shifts upward. Executives must create the conditions where high performance doesn’t require burnout, hidden overtime, or constant crisis management. Here are some structural fixes to ensure that the organization starts managing work intentionally. 

  1. Establish a Work Intake Process:  One of the biggest contributors to chronic overload is the absence of a formal system for how work enters the team. Rather than projects being given through a quick conversation in the hallway or by a quick Slack message, having a standardized method for delegating tasks will help organizational alignment and task management. This should include:

  • A clear description of the task
  • Expected outcomes and success criteria
  • The estimated time it will take to complete
  • A realistic deadline
  • A decision on what work will be paused or deprioritized

This forces leadership to make intentional choices rather than unintentionally dealing out too much work.

  1. Use Data to Monitor Team Health: When leaders rely solely on output to determine a team’s capacity, they often miss early signs of burnout. It is important to uncover the blind spots behind high-performing teams that often hide hidden stressors that will snowball into poor performance if not caught in time. This means executives should be looking beyond deliverables and building a system that surfaces the real conditions behind the output. Leadership should routinely review:

  • Workload vs. available hours
  • Overtime patterns
  • Backlog growth
  • Dips in quality

These metrics give executives a more accurate picture of whether a team is operating sustainably or simply holding things together through overextension. 

  1. Join an Executive Mastermind Group: Executives often operate in isolation, surrounded by their own organization’s norms and blind spots. Mastermind groups break that pattern by exposing leaders to how other high‑performing organizations manage capacity, prioritize work, and prevent burnout. Benefits can include:

  • Learning proven workload management frameworks
  • Seeing how other leaders set boundaries and communicate capacity
  • Gaining peer accountability for implementing healthier systems
  • Discussing challenges without internal politics
  • Understanding how top companies maintain high performance without overworking their teams

This external perspective is often the catalyst leaders need to rethink outdated assumptions about capacity, productivity, and team health. When executives see how other organizations succeed without burning people out, they become far more willing to adopt sustainable practices. 


None of these issues are about blaming teams or leadership. They’re about recognizing that high performance can only last when the structure around it actually supports the people doing the work. When teams speak up early and leaders stay connected to what’s happening behind the metrics, it becomes much easier to catch problems before they turn into burnout or turnover. With clearer priorities, better systems, and honest conversations about capacity, organizations can keep delivering great work without running their people into the ground. 

 
Fri 8 May 2026
 Sam was sitting in his office reading over a report, but there was a ton of inconsistency. Earlier that month, he and his team were preparing for a major product launch and ready to define the next phase. Every update that came to him was confident, structured, and solution-oriented. He was beyond impressed with the work the teams had completed. It made Sam feel like the strong leader he always aspired to be.


Unfortunately, as results from the product began to roll in, Sam noticed they had underperformed. He was getting frustrated with customers calling, and internal teams were scrambling all over the place. One day, the office was in complete uniform, and before he knew it, everything was a mess.


When Leadership Style Becomes a Filter


As Sam started to think about it more, he realized that he unknowingly created a system where information was being filtered before it reached him. Sam’s expectation that leaders come prepared with solutions had subtly reshaped behavior across the organization. Problems were softened before being shared, uncertainty was reframed as confidence, and early warning signs were delayed until they became unavoidable. What he believed was a culture of ownership had, in practice, become a culture of managed perception, and this is precisely where objectivity begins to break down.


Objectivity in leadership is not just about interpreting data correctly. It is about ensuring that truth, especially uncomfortable truth, can travel upward without resistance or distortion. Without that, even the most capable executives risk operating inside a narrowed version of reality.


Organizations don’t crumble overnight. There are small things that slowly start to accumulate, and before you know it, the damage is already done. It's always so hard to detect because on the surface, it looks like everything is working. Meetings are occurring, updates are strong, and everyone is engaged. But beneath the surface, the information being communicated was changing. There was a shift from sharing what is true to sharing what is safe.

  • Why do high-performing teams sometimes hide their problems from leadership?
  • When leaders reward confidence and penalize doubt, teams learn to filter before it travels.


Sam’s situation is not unique, but is often difficult to notice. In the eyes of the leader, they believe they are the hallmark of good leadership and foster an environment of accountability. Organizations that lack objectivity create a kind of blind spot because the feedback loop between teams and leadership is broken. Leaders are making decisions on versions that do not even exist. On the other side, people on the inside of the organization who are carrying this do not disengage. They notice that this work is what rewards them and know that they need to conserve themselves accordingly.


The Mechanics of How Truth Gets Filtered Out


In the case of Sam, he told his team that he expected solutions, but he believed he was creating a proactive culture. But what he didn’t notice was how employees had created an image of certainty and confidence, because Sam had created an environment that made doubt feel unsafe.


These filter leaders then continue to encourage an environment that rewards messages over accuracy. The problem was not his intent. It was the gap between the culture he thought he was building and the one that had actually formed around him.

  • How do I know if my team is telling me what I want to hear instead of what I need to hear?  
  • Slowly, patterns will form. If every update comes in confident, structured, and solution-oriented. Sometimes it's not necessarily a strength, but the work is filtered.


Rebuilding Objectivity:


As a leader in this situation, it's important not to overhaul, but just to focus on a few structural behavioral shifts.

  1. Create Explicit Permission Information


Creating a meeting that is devoted to finding those surface gaps, miscommunications, and any questions. Rather than getting polished responses, the team can use this as a place to name what they do not know yet and where the alignment is off. It opens a community that is normalizing uncertainty.

  • What is psychological safety?

2. Build Structured Dissent


Implementing a practice that has a designated conversation where one person is explicitly tasked with arguing against the prevailing plan. The role rotates, so it does not all fall to the same individual each time. The purpose was not to be contrarian, but to create a protected space for objections that might otherwise never surface.


3. Create Early Navigation Channels


Instead of finding out the disconnects from a customer call, creating, establishing a standing check-in with each direct report. It would be a ten-minute window to gauge productivity, but also stop miscommunication from the root. It gives leaders access to an early, unpolished version of what is happening. Having an early version of the truth is far better than the cleaned version of it.


What it Means for Every Leader


Leaders who emphasize only high standards and polished output tend to cast a long shadow over their teams. People begin to optimize for the appearance and performance rather than the reality of it. They think they need to be more perfect, which leads to less accuracy. These are some of the most common leadership failures that quietly drive good people away.


Objectivity, at the end of the day, tethered a leader to reality. To control this, it's important to be intentional to ensure that every source of information is being guided through clearly in a safe and open environment. This is fostered through a safe environment for the teams, leading to long-term success.


The key is separating the standard for outcomes from the standard for communication. You can hold your team to rigorous performance expectations while simultaneously making it safe to share early, uncertain, or incomplete information. In practice, this means rewarding honesty about risk as much as you reward results. When a team member flags a problem early, even without a solution, that deserves the same recognition as a win. Over time, that signal reshapes the culture more than any policy or all-hands message ever could.


 
Wed 6 May 2026
In most organizations, managers are expected to deliver results. While it can often seem that all a manager needs to do to deliver these results is to delegate tasks, for a growth-oriented team to succeed, managers must also develop the people working for them. The position of leaders is to be the ones between the ultimate vision, and the work that actually needs to be done to achieve it, which puts a lot of weight into how they choose to delegate tasks. Delegating tasks in this case means much more than just telling their direct reports what to do. Managers must translate senior executive vision into actionable steps while also developing the team as a whole. This position comes with a unique responsibility: deciding how much control to retain and how much to give away. Many managers hesitate to hand off meaningful ownership because it feels risky. Delegating real responsibility requires trust and a willingness to let others make decisions that you could easily make yourself. But in reality, giving your direct reports something to own is one of the most essential functions of a manager. It helps to strengthen performance, build confidence, and transform employees from task‑takers into leaders. Autonomy is a developmental tool that elevates the entire team.


When managers fail to give their direct reports proper opportunities to share ownership over a project, it only makes it worse for themselves. Without autonomy, employees become overly dependent on direction, waiting for instructions instead of anticipating needs or solving problems proactively. Work slows down because every decision funnels back to the manager, creating bottlenecks that limit productivity and frustrate both sides. Over time, employees begin to disengage, feeling more like cogs in a machine than contributors to something meaningful. They lose the intrinsic motivation that comes from having a stake in the outcome. Meanwhile, managers become overwhelmed by the sheer volume of decisions they’ve kept for themselves, leaving little room for strategic and creative thinking. Because of this, holding on too tightly to control can be far riskier than learning to let go.


Why Managers Need to Give Away Ownership
 Because managers operate at the intersection of execution and development, one of the most critical leadership skills they must cultivate is the ability to delegate responsibility, which is different than just delegating tasks. Ownership is not about offloading work; it is about giving someone the authority, context, and trust to make decisions within a defined space. Some of the most important reasons to do this include:


  • Meaningful Work
    : When employees have something that is truly theirs to run, they feel connected to the outcome. This sense of meaning drives engagement far more effectively than external pressure or oversight. People work harder for something they believe they own. 
  • Decision‑Making Skills: Ownership forces employees to prioritize, evaluate trade‑offs, and make choices. These are the foundational skills of leadership, and they cannot be developed through instruction alone. They require practice.
  • Stronger Collaboration: When direct reports feel like they are working with you rather than for you, the dynamic shifts. Conversations become more open, ideas flow more freely, and trust deepens. Autonomy signals respect, and respect strengthens teams. This kind of environment naturally supports horizontal mentorship, where peers learn from one another and leadership development happens across the team.
  • Reduced Bottlenecks: When every decision must pass through the manager, progress slows. Giving ownership distributes decision‑making across the team, allowing work to move faster and more efficiently.


How Managers Can Create Real Ownership
Some managers may think that creating ownership is simply assigning a project and stepping back, but this is not the case. Giving more autonomy to your direct reports does not mean handing over the entire project and saying, “figure it out!” It requires clarity, communication, and support throughout the process. Managers must define the scope of responsibility, this includes what decisions the employee owns, what success looks like, and where the boundaries are. This prevents confusion and will help the employee to act confidently, while still keeping a good eye on the situation. Instead of simply giving a step by step on how to do something, managers should explain the context of the situation and allow their people to exercise the skills that got them hired in the first place. Explain the “why” behind the work, the constraints, and the priorities, then allow the employee to determine how the work should get done. This should be done in combination with regular check‑ins that focus on guidance and alignment.  Here you can ask questions like “What decisions have you made so far?” or “What obstacles are you anticipating?” These questions encourage critical thinking without taking control. Ultimately, creating ownership is less about delegation and more about development. Ownership over projects helps employees build the skills, confidence, and judgment they need to succeed.


Giving your team something meaningful to own is essential for leadership that aims to grow and develop rather than just manage. Managers who hold too tightly limit their team’s growth and unintentionally create dependency. But managers who intentionally give away ownership build stronger, more capable teams who take pride in their work and contribute at a higher level. By trusting your direct reports with real responsibility, you reduce bottlenecks, strengthen collaboration, and create a culture where people feel empowered to lead. Ownership is the foundation of intrinsic motivation, accountability, and long‑term success for both the team and the organization.


 
Wed 6 May 2026
What makes a change initiative successful? Is it the vision of grandeur around all the possibilities of what could happen if every domino falls into place? Or is it the ability to get the entire organization to permanently change the way they behave at a small, day-to-day level? Is it even possible to enact big changes within an organization?

These questions will be addressed in this article.

Let’s start with the root cause of change. Change occurs because the business has identified that the current way it has been operating can be improved.

Change becomes painful when not everyone agrees that the current way of operating can be improved or when they are unclear about why it isn’t cutting it anymore.

Executives, typically, are reticent to share details on why a change needs to occur for fear that by sharing these details, it might cause panic. Oftentimes they compound this issue by doubling down with toxic optimism - sharing things like “We have never had a layoff and never will!” or “Everything is going amazing and we are crushing it in the market!”

This compounding of toxic optimism hurts change initiatives because if “nobody is in fear of getting fired” or if “everything is going amazing and we are crushing it in the market” it lacks the honesty of the hard truth that comes with implementing a change initiative - that the overtly optimistic message shared in the past was in fact wrong and that there are opportunities for improvement.

For those of you who are fans of the TV show The Office - it is reminiscent of the episode where Michael has money problems and as opposed to confronting his girlfriend Jan about her spending, he gets a second job and tries to convince everyone else he is fine and that he doesn’t have money problems - crumpling up a dollar bill and pretending to toss it away while secretly putting it back into his pocket. 

This sounds like a silly analogy but it is the truth. Most executives would prefer to meet with their executive team/board, determine a new direction or change, and pass that message on to the middle managers with the hope that they can turn that message around and implement the change in the exact vision in which the executive team drew it up isolated. 

And if the change initiative doesn’t work, whose fault is it? You can probably surmise that it is not the executive team’s fault until the board loses patience and fires the CEO. 

In place of large change initiatives, many companies are finding “success” in driving efficiencies by making cuts. “Success” is in quotations because it doesn’t address the root cause of the issue with why change initiatives fail. The way these cuts work is a company, in an effort to reduce expenses while maintaining output, decides to let go of a certain percentage of the workforce and then ask the remaining team to accomplish the same amount of work they did with a larger staff.

This technically achieves the outcome the company identified because:
  1. The standard of excellence was set (it is much easier to hit a standard of excellence that is established with fewer people than it is to get a group of people to raise their standard of excellence).
  2. They are paying less in salaries.

The unintended consequences are:
  1. Burnout
  2. A disgruntled workforce that doesn’t feel trusted

The issue: In all of these scenarios, no one is having honest conversations about the problem to be solved, the expectations that need to be set, and what the priority order is.

To successfully implement change, everyone in the company needs to be aligned on the problem to be solved. To get alignment, executives need to be vulnerable, honest, and open-minded.

Below is an example of what this looks like in a practical sense:

Memo from the CEO to the entire company:

“Hello team, I have met with our board and leadership team and we have identified a challenge as our business transitions into the future. Our competitors are currently offering a similar service for 30% less than we are currently offering our services. Obviously, we believe we have better service and overall outcomes than our competitors and our clients are locked into annual agreements, but we believe that there is a chance that our competitor might challenge our market share. We can take a wait-and-see approach to this issue, but if we do, we run the risk of losing significant business and being put in “catch-up” mode versus proactively reinforcing to our customers why they should continue working with us. We believe it would be prudent for us as a business to proactively identify additional value we can provide to our clients and/or cost savings that we can implement and pass along to the client. We are currently putting this plan in place and would like to involve everyone in the company to share their thoughts and ideas on how we might be able to add value and reduce costs. We likely won’t be able to implement every idea but by taking pieces of all of these ideas, we can create a solution that sets us up to thrive into the future. Therefore, over the span of the next 2 weeks, if you could please share with our colleague Jane Doe your ideas for how we can improve the business, she will compile them and we might follow up if we have future questions or need clarification.”

This message is powerful because it is honest, collaborative, and aligns everyone on the problem to be solved. As opposed to mysteriously letting go of 10% of the workforce and asking the rest to make up for the work or asking the team to implement a large change initiative without explaining why implementing this change initiative is important, this method creates understanding, receptivity, and collaboration.

And once there is alignment on the problem to be solved across the company, and a change initiative is implemented, showcasing the early wins is critical to building support of the cause. 

Similar to Paul Revere sharing word of good news across the American Revolutionary War, your team wants to know any and all good news supporting the cause of change - because by inviting their collaboration, they now want to see its success. 

If you are a leader and want to join this conversation or surround yourself with others discussing these issues, consider joining an executive mastermind group.

 
Fri 10 April 2026
In most organizations, middle managers are the essential link between big ideas and practical execution. Senior leaders set ambitious goals, and frontline teams bring those goals to life, but it’s the middle managers who must interpret and translate both sides. They have to have an understanding of the exact expectations, but also the limitations. This role as liaison between executives and frontline teams comes with an immense amount of pressure. You’re evaluated on your output, yet responsible for protecting your team. In this position, saying “no” feels like too much of a risk. There’s often a level of ambiguity about exactly what authority you have as a middle manager, making it feel like boundaries are a luxury reserved for those who run the organization, when in reality, setting boundaries is one of the most essential functions of a middle manager. Setting boundaries helps to not only protect your own peace but also to prevent team burnout, protect the quality of your work, and make you a better leader.
When middle managers fail to set boundaries, the consequences are felt by both the team and the organization. Without clear limits, teams become overwhelmed, and burnout begins to affect morale and performance. A middle manager who always says yes to taking on more than what is reasonable signals to others that their capacity is endless, causing the issue to worsen. Over time, saying yes to everything will lead to diminishing work quality, leading senior leadership to lose trust. This loss of trust is not due to a lack of effort from the manager's end, but rather because the workload was never sustainable to begin with. Never saying no or setting boundaries will lead people to start to expect constant availability and unquestioned compliance, making it even harder to push back in the future. In this way, saying yes to everything becomes far riskier than learning to say no.

When You Should be Putting your Foot Down
Because middle managers sit at the intersection of competing demands, one of the most critical leadership skills they must develop is the ability to set boundaries. These boundaries are not about resistance; they are about creating the conditions for sustainable performance. Some of the most essential include:
  1. Unrealistic Expectations: You know the limitations of your team, and accepting projects that are beyond those limitations doesn’t make you look better; it just sets you up to underperform. To drive performance, you have to be honest about what is and isn’t realistic. When an executive gives you a deadline that you know your team will struggle to meet, say that when you hear it the first time, not the day before it’s due. Communicating the limitations of your team and working to set clear expectations of the work you can deliver from the very start puts you and your team in the best position for success.
  2. “Not my Job”: Everyone knows the struggle of receiving a task that seems out of their job scope entirely. While it might seem like an inconvenience that you accept to please upper management, doing so is just as bad for the organization as it is for you. When middle managers take on responsibilities that aren’t their own, it blurs the lines of accountability and tracking who is responsible for what. Before you know it, you’ll be taking on the work of another team, and management will be giving away the work of your team because you can’t do both at one time. Creating a clear boundary of only accepting work under your jurisdiction will maintain order in your organization by reinforcing the structure that allows teams to function effectively.
  3. Availability and Work Hours: Middle managers frequently feel obligated to be “always on,” responding to messages late at night, joining early‑morning calls, or working through weekends to keep up. While flexibility is part of leadership, constant availability is not. When you fail to set boundaries around your work hours, you set an expectation of unsustainable behavior for your team that will, in the long run, be very difficult to maintain. It’s important to establish clear limits, such as defined offline hours or protected focus time, to help preserve your energy and reinforce a healthier culture for your team. Without this boundary, burnout becomes inevitable.

Setting Boundaries as a Middle Manager
Setting boundaries is about more than just knowing where the limits are; it’s about knowing how to communicate them. Middle managers can only do this effectively when they have a firm understanding of their team’s true capacity, which requires tracking workload patterns, noticing when performance dips or improves, and identifying the conditions under which the team does its best work. Using tools such as AIM insights can give you a better, more in-depth understanding of exactly how your team is performing and under what conditions. With that insight, boundaries become easier to articulate because they are grounded in evidence rather than emotion. Good communication from the start is essential; waiting until a deadline is slipping or a project is already off track makes boundary‑setting feel reactive instead of responsible. A good practice is framing conversations around trade‑offs rather than refusals. Be clear about your reservations, what can be done, and what support is needed. This will help to avoid the perception of refusal while still protecting your team. Practicing these conversations in low‑stakes environments builds confidence for the moments when the stakes are higher. Ultimately, setting boundaries is less about saying “no” outright and more about creating clarity, aligning expectations, and ensuring that the work you commit to is work you can deliver well.
 Boundary setting is a leadership requirement, not just a luxury for the higher-ups. The pressures of middle management make it easy to fall into patterns of overcommitment, blurred responsibilities, and constant availability, but these habits ultimately undermine both performance and credibility. By recognizing where limits must be drawn and communicating those limits frequently, middle managers protect their teams, strengthen organizational structure, and ensure that the work they take on is work they can deliver well.


Fri 27 March 2026
When a team falls behind, it’s often tempting to blame individual members. Leaders often point to reasons like frequent dentist appointments or poor time management. However, slipping output usually doesn’t always stem from the people's lack of effort. It’s often due to a lack of standardized procedures that guide execution. Before you decide that the people on your team aren’t a good fit because you aren’t getting the results you want, you should make sure that the issue isn’t the system they’re operating under.

Effective leaders may have the same number of team members taking time off or stepping out of the office for appointments, but still manage to achieve better results. The key difference is not fewer interruptions. It’s a stronger focus on output and a clear plan for handling the predictable challenges. When teams know how to respond to obstacles, progress remains steady. Having standard operating procedures is a surefire way to protect the performance of your team and keep you on track. A clear procedure supports daily work and helps identify issues before they escalate into bigger problems.

Undefined Expectations Create Avoidable Failure

Without standard procedures, it’s harder to measure progress and expectations are assumed rather than defined. Leaders lose visibility on where work struggles occur and often don’t realize there’s an issue until output has already dropped. At that point, individuals are blamed for failing within a poorly designed system, instead of examining the system that set them up to fail.

A strong team and its leaders should always have a standard process guided by these key questions to keep the team on track:

  • When output dips, what do we review?
  • When timelines slip, when do we step in?
  • If someone deviates from SOPs, how do we correct it early?

These questions keep the focus on output rather than individual behavior. They allow leaders to address performance without nitpicking and prevent distractions from diverting attention away from the goal. Instead of coaching individuals, leaders refine processes. 

What Happens When Expectations Aren’t Properly Defined

A benefit of standard operating procedures is the clarity they provide to leaders. When SOPs are in place, leaders no longer guess whether someone is underperforming. They can see exactly where execution differs from the standard. This makes feedback factual instead of personal.

Without that clarity, feedback often comes too late. Leaders wait, hoping performance will improve on its own. This leads to the build up of frustration and resentment in a team, so by the time the issue is tackled, emotions are already involved. Even accurate feedback can feel unfair when the standard was never clearly set beforehand. SOPs prevent this by establishing expectations before problems arise. This way, it becomes easier for people to take accountability, because there is no excuse for not knowing the standards.

This delay in addressing issues is where many teams unknowingly create avoidable conflict. A team member falls slightly behind. Leadership notices but takes no action. As time passes, output will only continue to decline. Eventually, the conversation occurs under pressure. By then, the leader is frustrated, the employee feels blindsided, and both leave feeling dissatisfied. The problem wasn’t effort or intent. It was the absence of an early, objective standard to refer to.

Removing Emotion from Accountability

Many leaders hesitate to implement more procedures fearing micromanagement. But micromanagement doesn’t come from added structure. It comes from emotion. It’s a reaction to missed deadlines, unexpected outcomes, and unclear expectations that leads to leaders becoming overly involved.

Well-implemented standard operating procedures do the opposite. They define standards early on, which reduces the need for reactive oversight. When leadership trusts the process, they’re less likely to micromanage. Issues can be identified sooner, addressed calmly, and corrected before they develop into larger problems that require significant intervention.

Strong SOPs also shift accountability from individuals to processes. Instead of asking why someone is always behind, leaders can investigate where execution diverged and whether the system supported the desired outcome. This doesn’t lower standards; it strengthens them. High standards become consistent rather than situational.

Teams without SOPs rely heavily on individual judgment. While that might work in low-pressure settings or with highly experienced contributors, when complexity rises, communication issues arise, people don’t get the guidance they need, and everyone is blaming someone else for the lack of output.

In contrast, teams with solid SOPs work with a shared understanding. Everyone knows what being “on track” looks like. Progress is visible. Deviations get caught early and adjusted smoothly. Work advances because expectations are clear, not because individuals are working harder or sacrificing more personal time.

Promoting Alignment

In the end, standard operating procedures aren’t about control. They are about alignment. They align effort with results, expectations with execution, and accountability with fairness. When systems are clear, leaders spend less time reacting and more time leading. Teams work faster, frustration decreases, and performance becomes consistent rather than accidental.


Fri 27 March 2026
Maya had finally built a company fueled by strong revenue growth and high performing teams. As a result, investors were becoming increasingly optimistic about the company’s future. With this momentum, pressure to expand and bring in new clients began to rise. Maya knew she needed to scale faster. She directed her teams to increase outreach, pursue referrals, and bring in as much new business as possible.


However, Maya also recognized a major risk. Most of the company’s growth was driven by just five enterprise clients. While these relationships were stable and highly profitable, they were also extremely concentrated. 


As the team pushed for growth, coordination began to break down. Within a single week, one key client received three separate touchpoints: a marketing team contacted the vice president of operations, a new sales representative made a cold introduction, and the existing account manager sent a routine quarterly review invitation.


From the client’s perspective, the experience was confusing. They received multiple messages, each with a different tone and no clear coordination. Internally, both sales representatives believed they were doing the right thing. One was focused on expansion, while the other was trying to protect a strategic relationship. But, it felt like chaos.


What Happens When Sales and Marketing Do Not Communicate and How it Starts


These scenarios are not rare.  As companies start to scale their business from small to mid-sized, or mid-sized to enterprise, they often attempt to grow faster than their internal structure can support. These problems are rooted in miscommunication between different teams within the company. There are three structural gaps between teams which fuel client confusion: 


  1. There is no client ownership
    . With no client ownership, the teams do not know who the point of contact is, and multiple teams feel entitled to engage and help out the same client. A lot of the relationship building and work being done becomes very repetitive. 
  2. Teams are incentivized to the reward revenue of helping a client. Usually, within companies, compensation plans are rewarded to teams for closing deals, especially those without clarifying ownership. As a result, teams look more towards their own personal returns. Sometimes, having a client without a direct point of contact, there are times that people create territorial behavior, internal competition, and even client poaching.
  3. The last way this can be rooted is through the need for growth. Teams start to just expand, outpacing the resources they have. Headcounts expand, yet customer relationship management controls, segmentation strategy, and cross-team alignment lag behind. Effort increases, but coordination does not.

From these root causes, clients get bombarded, slowly internal trust erodes, and major accounts begin to feel like targets instead of partners.


How to Solve and Mitigate It


To fuel long-term growth, there needs to be specific guidelines that define lanes, ownerships, and aligned incentives. Organizations that address these gaps typically implement three core corrective actions.


1. Establish Clear Account Segmentation


Clients should be divided into defined tiers, such as:

  • Strategic accounts with high revenue concentration or long-term value
  • Growth accounts with expansion potential
  • Net new prospects


Each tier should have a designated ownership model. Strategic accounts are typically assigned to dedicated account managers who have been with the client for a while and have built trust and relationship. Growth accounts may require shared planning with clearly defined roles, and utilizing different teams in the office to foster long-term growth. Net new prospects belong to new business sales, and they are still starting up and learning more about the company.  


Segmentation allows for clarity and teams to operate within lanes instead of overlapping territory.


2. Formalize Account Ownership Rules


Ownership should not rely on informal understanding or historical precedent. A written policy should establish:


  • One primary owner per account
  • Defined rules for expansion engagement


When ownership is transparent and documented, conflict decreases. Decisions move from politics to process. As a result, the primary owner becomes a trustworthy manager towards the client who understands everything and is able to establish long-term success. With having the document written, no other teams can infer if it is their team, and it completely eliminates the ambiguity of ownership. 


3. Implement Regular Sales and Marketing Alignment Meetings


Even though establishing a point of contact for our contact is important, it is also imperative to foster a cross-functional forum to ensure:


  • Visibility into upcoming campaigns
  • Updates on strategic accounts
  • Shared pipeline reviews


Consistent communication prevents duplication and protects the client experience. In addition, teams are more involved with the clients, having the company more in the loop of where clients are, but at the same time fostering a holistic environment full of trust for clients. 


The Outcome


Within months, internal friction will decrease and the client experience should stabilize. The previously frustrated top five clients renewed and expanded. Growth does not slow, but becomes sustainable.


The lesson for business leaders is clear. Misalignment between sales and marketing is rarely a people problem, but most likely a structural one. And structure, when designed intentionally, turns internal competition into coordinated growth.



Recent Contributors


Blog for Mentors and Mentees by Ritika Vijay
Ritika Vijay 17 articles

Blog for Mentors and Mentees by Julia Gonzalez
Julia Gonzalez 16 articles

Blog for Mentors and Mentees by Snehal Mantri
Snehal Mantri 3 articles

Blog for Mentors and Mentees by Kayla Ambrose
Kayla Ambrose 44 articles

Blog for Mentors and Mentees by Kendall Barndollar
Kendall Barndollar 35 articles

Blog for Mentors and Mentees by Grace Tripathy
Grace Tripathy 84 articles

Blog for Mentors and Mentees by Malhar Lakshman
Malhar Lakshman 42 articles

Blog for Mentors and Mentees by Mindy Honcoop
Mindy Honcoop 3 articles

Blog for Mentors and Mentees by Dolores Wuepper
Dolores Wuepper 1 article

Blog for Mentors and Mentees by Brad Finkeldei
Brad Finkeldei 1 article

Blog for Mentors and Mentees by Andrea Butcher
Andrea Butcher 1 article

Blog for Mentors and Mentees by Susan Lindner
Susan Lindner 1 article

Blog for Mentors and Mentees by Annie Meehan
Annie Meehan 1 article

Blog for Mentors and Mentees by Shane Matthews
Shane Matthews 2 articles

Blog for Mentors and Mentees by Nick Van Horn
Nick Van Horn 2 articles

Blog for Mentors and Mentees by Megan King
Megan King 1 article

Blog for Mentors and Mentees by Mike Johnson
Mike Johnson 3 articles

Blog for Mentors and Mentees by Chip Stapleton
Chip Stapleton 2 articles

Blog for Mentors and Mentees by Geoff McCuen
Geoff McCuen 3 articles

Blog for Mentors and Mentees by Aaron Grady
Aaron Grady 3 articles

Blog for Mentors and Mentees by Chaundra Covington-Rousseau
Chaundra Covington-Rousseau 1 article

Blog for Mentors and Mentees by Vishal Kinkhabwala
Vishal Kinkhabwala 1 article

Blog for Mentors and Mentees by Shontal Linder
Shontal Linder 1 article

Blog for Mentors and Mentees by Bob Torstrick
Bob Torstrick 1 article

Blog for Mentors and Mentees by Brandon Gaydorus
Brandon Gaydorus 1 article

Blog for Mentors and Mentees by Dr. Colonel Solis
Dr. Colonel Solis 1 article

Blog for Mentors and Mentees by Hallie Crawford
Hallie Crawford 1 article

Blog for Mentors and Mentees by Evony Caldwell
Evony Caldwell 1 article

Blog for Mentors and Mentees by Aseba Green
Aseba Green 1 article

Blog for Mentors and Mentees by Rob Studivan
Rob Studivan 1 article

Blog for Mentors and Mentees by Christy Wolfe
Christy Wolfe 1 article

Blog for Mentors and Mentees by Dr. Toscha Dickerson
Dr. Toscha Dickerson 1 article

Blog for Mentors and Mentees by Frank Mengert
Frank Mengert 1 article

Blog for Mentors and Mentees by Janice Porter
Janice Porter 1 article

Blog for Mentors and Mentees by Yvonne Heath
Yvonne Heath 1 article

Blog for Mentors and Mentees by Andrea Constantine
Andrea Constantine 1 article

Blog for Mentors and Mentees by Emma Kerr
Emma Kerr 1 article

Blog for Mentors and Mentees by Wanda Thibodeaux
Wanda Thibodeaux 1 article

Blog for Mentors and Mentees by Ashley Fontaine
Ashley Fontaine 1 article

Blog for Mentors and Mentees by Mac Prichard
Mac Prichard 1 article

Blog for Mentors and Mentees by JT McCormick
JT McCormick 1 article

Blog for Mentors and Mentees by Adam Posner
Adam Posner 1 article

Blog for Mentors and Mentees by Lou Adler
Lou Adler 1 article

Blog for Mentors and Mentees by Nick Smarrelli
Nick Smarrelli 1 article

Blog for Mentors and Mentees by Jayne Fouché
Jayne Fouché 1 article

Blog for Mentors and Mentees by Nicole Martin
Nicole Martin 1 article

Blog for Mentors and Mentees by David Elfman
David Elfman 1 article

Blog for Mentors and Mentees by Joanna Severino
Joanna Severino 1 article

Blog for Mentors and Mentees by Bree Deforest
Bree Deforest 1 article

Blog for Mentors and Mentees by John Boitnott
John Boitnott 1 article

Blog for Mentors and Mentees by Andy Pham
Andy Pham 1 article

Blog for Mentors and Mentees by Garrett Mintz
Garrett Mintz 101 articles

Blog for Mentors and Mentees by Nicole Martin
Nicole Martin 1 article

Blog for Mentors and Mentees by Ashira Prossack
Ashira Prossack 1 article

Blog for Mentors and Mentees by Emilio Lorenzo
Emilio Lorenzo 1 article

Blog for Mentors and Mentees by Caroline Ceniza-Levine
Caroline Ceniza-Levine 1 article

Blog for Mentors and Mentees by Lexi Herrick
Lexi Herrick 1 article

Blog for Mentors and Mentees by David Meltzer
David Meltzer 1 article

Blog for Mentors and Mentees by Lauren Schieffer
Lauren Schieffer 1 article

Blog for Mentors and Mentees by Evangelia Leclaire
Evangelia Leclaire 1 article

Blog for Mentors and Mentees by Heather Wilde
Heather Wilde 1 article

Blog for Mentors and Mentees by Judith Humphrey
Judith Humphrey 1 article

Blog for Mentors and Mentees by Dr. Ai Addyson-Zhang
Dr. Ai Addyson-Zhang 1 article

Blog for Mentors and Mentees by Charmaine Hammond
Charmaine Hammond 1 article

Blog for Mentors and Mentees by Kathy Caprino
Kathy Caprino 2 articles

Blog for Mentors and Mentees by Erica Ballard
Erica Ballard 1 article

Blog for Mentors and Mentees by Jordan Paris
Jordan Paris 1 article

Blog for Mentors and Mentees by Marcus Wermuth
Marcus Wermuth 1 article

Blog for Mentors and Mentees by Vinay Singh
Vinay Singh 1 article