Navigating Leadership Challenges: Insights and Lessons Learned

A few years ago I had to walk my leadership team through a change none of us saw coming and none of us were ready for. Before that meeting, I wanted to do what I’d always been taught a leader does: walk in with a plan, sound certain, project control.

I could feel the room’s worry before anyone said a word. People were watching my face for a signal about how bad this actually was. If I’d walked in and faked confidence, they would have felt it, even if they couldn’t have named what was off. People can tell when a leader’s words and a leader’s knowledge don’t match. And once they can tell, they stop listening to the words.

So I resisted the instinct to perform certainty. I named what was true instead. We didn’t have every answer yet, and pretending otherwise would cost us more than admitting it. I said plainly what we knew, what we didn’t, and what our next step for finding out would be, nothing more. I remember the silence after I said it, a couple seconds where nobody moved. Then someone asked a real question, the kind you only ask once you believe you’re actually going to get a real answer. That one decision changed how the room responded. People stopped bracing and started actually thinking with me instead of watching me for reassurance.

The lesson I carried forward wasn’t really about that specific change. It was about sequencing. Clarity has to come before confidence. Skip straight to reassurance and people feel the gap even when they can’t name it, and that gap does more damage to trust than the uncertainty ever could have.

Confidence built on clarity holds. Confidence built to cover for its absence doesn’t, and it usually cracks at the worst possible moment.

I still return to that meeting when I’m tempted to sound more certain than I am. The team doesn’t need a leader who has it all figured out. They need one who’s honest about what’s still being figured out, and steady enough to keep working the problem with them.

The change: our team’s job stopped being production and became evaluation, over about two quarters, and I handled the first half of it badly.

What happened underneath is simple to state and was hard to see at the time. Making things stopped being the scarce input. Deciding what was worth making, and whether it was true, became the constraint. That sounds like a workflow adjustment. It was a change in what people were actually good for.

My mistake was announcing it as a tooling change and a process update. It was neither. One of our strongest people was excellent at production and mediocre at judgment, and I let them discover that in a performance conversation rather than telling them early that the ground was moving. That was avoidable and it was mine.

The approach that eventually worked, once I stopped pretending it was small:

I said out loud that the role had changed and that some people would be better at the new version than the old one, and that this was about the work rather than about anyone’s worth. Naming it removed a lot of quiet anxiety that had been showing up as resistance to the tooling — people were not arguing about software, they were arguing about their standing.

We rebuilt what we measured. Output per person had become an actively misleading number, so we moved to whether senior time was freed and whether a specific class of error disappeared.

And we protected the thing the change threatened: juniors now deliberately draft unassisted on some work, because judgment is built by producing errors and having them named. Automate the reps away and you get throughput now and no senior bench in five years.

The lesson I took: when the nature of the work changes, say so early and explicitly. People handle “the job is different now” far better than they handle discovering it themselves six months later in a review. The resistance you get to a change is usually about status, not about the change.

The hardest stretch my small leadership group has been through was deciding to step away from a payer contract that made up a meaningful share of our volume. The economics no longer worked and the administrative burden was pulling clinical time away from patients, but leaving meant telling people who had been coming to us for years that we would no longer be in network for them.

My instinct was to decide it quickly and quietly, then announce it. My office manager pushed back and said the staff would be having this conversation at the front desk hundreds of times and needed to believe in the answer they were giving. She was right. We spent two weeks working through the decision together, wrote the reasoning out in plain language, and gave every person the same words to use.

What I learned is that the decision and the explanation are one piece of work, not two. I had treated the explanation as an afterthought to be handled once the hard thinking was done. Doing it properly took longer at the front and saved months of confusion afterward.

We kept about 70% of the affected patients through a self-pay arrangement, which was better than I had allowed myself to expect, and the front desk conversations stayed calm because nobody was improvising an answer under pressure.

The challenge that tested our leadership team most significantly was not a single moment. It was a sustained period of enrollment decline that forced us to make decisions none of us wanted to make, while holding together a culture that took 30 years to build.

Miami families began pulling their children out of preschool earlier than they should, driven by fear around elementary school seat availability. The thinking was: if we leave early, we improve our chances of getting in somewhere. What that meant for us was losing children mid-journey, before the work was complete, before the families had experienced what the full arc of these years can give a child.

The financial pressure was real. There were periods when we had to let teachers go temporarily. Not because the work wasn’t extraordinary. Because we couldn’t meet payroll. These were people we had invested in deeply, emergent teachers who were learning to build this culture alongside veterans who had been with us for decades. Letting them go, even temporarily, felt like interrupting something essential.

My approach in those moments was to keep the leadership team tightly connected to purpose. Not to the problem. To the purpose. We asked ourselves, again and again: what does L’Atelier need to survive without becoming something it isn’t? That question kept us from making decisions that would have solved the financial problem by eroding the culture.

The practical answer was to turn our deepest strength into a revenue stream. We invested in professional development, conferences, workshops, and enrichments as a way to carry the school through the difficult months. The teachers came back when we could pay them again.

What I learned is that a leadership team navigates change well when it has spent years in genuine dialogue before the crisis arrives. You cannot build trust under pressure. You build it in the Wednesday meetings, in the daily planning hours, in the years of shared research and documentation. When the difficulty came, we already knew how to think together. That made all the difference.

Make Every Change Visible Beyond The Room

A significant leadership challenge is changing direction without making the team pay for information they never received. I learned that after two team members spent a full week building something that had already been deprioritized in a conversation they were not part of.

Their execution was not the problem. The leadership process was. A decision had been made, but the people whose work it affected still had the old instruction. More meetings would have treated the symptom while adding more interruption.

I introduced a single daily log we called the record. By 4pm, anyone who made a decision, changed a plan, learned something important, or hit a blocker added a one or two sentence entry. It captured what changed and what another person might need to know. It was not a diary, a meeting transcript, or a list of completed tasks.

The format stayed intentionally plain: date, name, and one short entry. Someone returning after time away could scan the changes. A person focused on delivery could review the decision trail before continuing. Leadership context stopped depending on meeting attendance.

Within a couple of months, duplicated work dropped almost entirely. People stopped beginning conversations with long recaps because the shared context already existed. New hires could read the previous month’s entries and understand both what the company was doing and how decisions were made.

The lesson was that alignment is not created by repeating a message more loudly. It comes from making material changes easy to find and difficult to misinterpret. Leaders still need direct conversations when a decision is sensitive, contested, or personally consequential. The record supports those conversations; it does not replace them.

There is a failure mode. If every minor update enters the log, the important decisions disappear inside noise. If leaders write vague entries, the team still has to guess. The standard must stay narrow: record decisions, changed assumptions, blockers, and information that alters someone else’s work.

My leadership rule is now simple. The people affected by a decision should not need proximity to the decision-maker to understand it. Context should follow the work.

The one that taught me most was shifting the business away from depending on marketplace sales and towards our own site. Commercially it was obvious. Internally it was the hardest thing I have done.

The people around me were not being difficult. They could see the orders arriving from the marketplace and could not see the ones that might come from a site we had not finished building. My mistake was announcing the decision and expecting the reasoning to be inferred from it.

What worked was the opposite order. I over-explained the why repeatedly, in more detail than felt necessary, showing the margin difference and the risk of depending on a channel we did not control. Then I left the how properly open and let it be argued about. People who had disagreed with the plan designed large parts of how it happened, and defended it afterwards.

Own-site sales went from a small fraction of revenue to around 70%, and most of the operational work behind that was not my idea.

The lesson is that a leadership team absorbs change at the pace it understands the reasoning, not at the pace you announce it. If you want speed, spend the time on the why. Arguing about the how is not resistance, it is people taking ownership.

The closest thing I have to a leadership team is a handful of senior people, so this played out in a room small enough that everybody’s opinion carried real weight.

The challenge was AI arriving inside search. Our client work was built around ranking pages and earning visits, and it became clear that a growing share of the answers people wanted were being served inside AI results without anyone clicking through to anything. Two of my senior people thought it was overstated and would settle down. I thought it was the start of a structural change in what we sell.

What I did badly at first was try to win that argument. What worked was agreeing on what evidence would settle it. We picked a set of client sites, tracked how often their pages were cited in AI answers against how much traffic the same queries were sending, and agreed to reconvene in a quarter with whatever the numbers said. Across that group, clicks from queries where an AI answer appeared fell by around 30%, and the disagreement dissolved without anybody having to lose.

The lesson was that senior disagreement is almost never about the facts. It is about different exposure to risk and different amounts of unlearning required. Arguing harder entrenches it. Defining the measurement in advance, before anyone knows which way it will fall, gets you a decision the whole room can live with, and the person who turned out to be wrong is not the one who has to say so.

Three months into building Nika Finance, we hit a structural decision that exposed how fast a three-person team has to move when the market shifts underneath you. Hyperliquid had just launched their builder codes program, and the question on the table was whether to rebuild our entire perpetuals backend to route through them or stick with what we’d already built in-house.

The in-house version worked. It settled trades. But it was slow to iterate on, and the matching engine quality wasn’t close to what specialized infrastructure could deliver. The honest assessment was that we’d built something functional that would never be best-in-class, and that gap was only going to widen.

Here’s what made the decision hard. Ripping out the backend and rerouting meant throwing away three months of engineering work. For a three-person team, that’s not a trivial cost. But the alternative was worse. We’d keep iterating on something we knew had a ceiling, burning time on infrastructure when the real product surface was the consumer interface sitting on top.

We made the call in one conversation. No committee. No phased rollout. We rerouted perpetuals through Hyperliquid via builder codes, and the matching engine quality went from functional to best-in-class overnight. The internal engineering surface got narrower. The user-facing product got stronger.

That decision became the template for how we route everything now. Prediction markets go through Polymarket. We don’t build oracles. We build the interface, the wallet, the cross-chain plumbing, and the AI layer that ties it all together. The rest routes to teams that specialize in those primitives.

The lesson wasn’t about flexibility or pivoting. It was structural. You cannot build a world-class product with a slow organization. The teams that win are the ones that stay closest to users and ship faster than everyone else. A three-person team has exactly one advantage over larger organizations: the decision-making layer and the execution layer are the same layer. When we see a better path, we take it that week, not that quarter.

The challenge for any lean team navigating change is knowing what to protect and what to replace. We protect the consumer surface. We replace everything underneath it the moment something better exists. That’s not agility as a virtue. It’s the only way to keep shipping when you’re three people competing against teams ten times your size.

The hardest one was cutting products we had launched with. The range had grown because each addition felt reasonable on its own, and the team, me included, was attached to the things we had made rather than the things people were buying.

My first attempt was to build consensus, which sounds like leadership and was avoidance. We discussed it across three consecutive sessions and left each one with everybody agreeing something should change and nobody agreeing what. Meanwhile, stock sat there and attention stayed spread across too many lines.

What broke it was separating two things I had allowed to blur. Input is open, the decision is not, and both need a date. I told the team I wanted every argument they had by the end of that week, that I would decide on the Monday, and that once decided we would stop relitigating it. We cut two lines.

The lesson was about what a team is asking for when it resists a change. They are usually not asking to vote. They are asking to be sure their objection has been heard and weighed by someone who could have been persuaded, and once that is visibly true most people move quickly.

Consensus is a lovely outcome and a terrible process. I confused the two for longer than I should have.

I should say up front that our leadership team is a handful of people, not a boardroom. There is no board and no investors, so when something big changes, it is a few of us in a room deciding, and the failure modes are different from a large company.

The hardest one was deciding to stay small on purpose. We had growth, and the obvious path was to hire ahead of it, add layers, and turn the company into something I did not want to run. Two of the people closest to me disagreed, and their case was good. Turning down revenue to protect a way of working is easy to say and hard to defend when somebody puts the math in front of you.

What I did badly at first was argue about tactics when the disagreement was about what the company is for. Once we put that on the table directly, the conversation got shorter and a lot less personal. We wrote down what we wanted the business to look like in terms of headcount and hours rather than revenue, and then judged every hire against it. We are still under 15 people serving well over a thousand brokerages.

The lesson is that an unresolved disagreement at the top is almost never about the decision in front of you. Find the thing nobody has said out loud, or you will keep having the same argument in new costumes.

During one product-development project, our leadership team had committed to a launch date before the formulation had been fully tested at manufacturing scale. The laboratory results looked good, but the first scale-up work exposed problems with consistency and stability. Sales wanted to protect the customer commitment, operations needed more time, and R&D was being pushed to find a quick fix.

I brought the group together and laid out three choices: launch on time with known technical risks, delay the entire program, or narrow the initial scope and finish the remaining work properly. I included the likely cost and risk of each choice. We agreed to focus on one version of the product and postpone the secondary versions. That gave the technical team enough room to solve the scale-up issues without losing the entire commercial opportunity.

I learned to bring difficult information to leadership early, even when everyone wants a different answer. I also learned that people handle bad news better when they are given clear choices. A problem becomes much harder to manage when it stays hidden until only one bad option remains.

A couple years ago I appointed a Vice CEO thinking it was my turning point. Excited about becoming a mother and focusing on our strategic vision, I breathed a sigh of relief as I granted her a new title. Then reality hit: despite years in leadership roles within our company, she was struggling with finding her own voice as a leader.

“My signature says ‘Vice CEO,’ but I feel like I still don’t know things I’m supposed to know,” she admitted to me once. To help her internalize that new authority, I decided to step in differently. Instead of retreating completely or taking over at the first sign of hesitation, I chose to coach her through it.

I stopped managing department heads directly so she had the room to lead. During a trip to London, we sat in a hotel room with my open inbox, walking through how I filtered requests, set priorities, and made executive calls in real time. We also changed how we ran leadership meetings. She began giving executive feedback first, while I shifted into a coaching role. Slowly, her reflex to ask for my advice transformed into confident judgment.

Navigating this change taught me that stepping back had two important parts to it: operational and psychological. Delegating responsibilities is one thing; transferring real authority is another. Handing over a title was merely the starting line; patience and mentorship brought us across the finish.

Today, my Vice CEO leads the company’s present so I can build its future. As a mother and a CEO, I finally have the space to thrive in both roles.

When we moved the Testlify core product from a general assessment play into a specialized skill-verification platform, my leadership team was divided on execution timelines. Sales wanted to continue selling the old, broad version (because the pipeline was built around it). Product wanted an immediate cutover (because maintaining both slowed down the roadmap). Neither was exactly “wrong,” which made it trickier than an average disagreement (where someone’s usually just missing information).

Approach: I didn’t play arbitrator during the meeting. I sent both sides home to write, independently, what they thought would happen to revenue and morale if the other team had their way. Basically, I forced them to clearly state the best-case scenario for the opposing position (not just defense for their own).

From there, it became clear that sales’ core fear wasn’t a change in the product, but losing their compensation on deals that were already in the pipeline.

Once that was named explicitly, the conflict went from a stalemate (“who is right?”) to an actionable one (“how can we achieve both ends?”): grandfather in existing pipeline on old terms and implement a clean cutover on everything new.

Lesson: Most leadership-team arguments that seem like strategic differences are rooted in an unexpressed, very specific fear. If you can draw that out, the “major” disagreement will typically disintegrate into a more manageable negotiation.

“Leadership conflicts don’t need arbitrators. They need people to elicit what the leadership teams are truly afraid of losing.”

A very recent example for me was taking Zeva outside Hong Kong. We opened our first Mainland China location at Upper House Chengdu this summer, and I think that was one of those moments where I realized that growth changes the way you have to lead.

When Zeva was smaller, I could be very close to almost everything. I’m naturally quite particular about details, so my instinct is often to notice something and fix it myself. That becomes much harder, and probably not very healthy, once you are working across different locations and teams.

With Chengdu, one of the things I kept coming back to with the team was: what absolutely has to remain Zeva, and where should we allow people on the ground to make their own decisions?

For me, the nonnegotiables are things like how seriously we take scalp and hair health, the professional standard behind our treatments, and how we care for someone who comes to us with a concern. But I also learned that maintaining those standards does not mean every location has to operate in the same way.

That distinction was important for me personally. As a founder, it is very easy to confuse consistency with control.

I’m still learning this as we grow, but the experience has made me more conscious of explaining the “why” behind our standards rather than simply telling people how I would do something. If your leadership team understands what you are trying to protect, they can make good decisions even when you are not in the room.

One of the bigger changes we had to navigate was building a model that could handle both traditional agency work and on-demand fractional talent without turning the whole operation into spaghetti. The leadership challenge was making sure everyone understood what was changing, what wasn’t, and who actually owned each decision. We got much more explicit about roles, processes, and priorities, and we surfaced disagreements early instead of letting them ferment into Slack archaeology. The biggest lesson was that change usually breaks down because of ambiguity, not resistance. People can handle a hard pivot; what fries them is not knowing who’s driving or where the car is going. Now, when something significant shifts, I’d rather over-communicate the why and the ownership than assume everyone magically downloaded the same memo.

One significant challenge I faced was managing the shift from a traditional language-services model toward a more technology-driven, AI-assisted localization model. It required the leadership team to rethink not only our processes but also how we positioned the business and how our teams worked.

My approach was to involve the leadership team in the decision rather than making it a top-down change. We looked at what was working, identified where AI could improve speed and scalability, and were equally clear about where human expertise remained essential. We tested the new approach on smaller projects, learned from the results, and then gradually expanded it.

The biggest lesson I learned was that change becomes much easier when people understand the “why” behind it and feel that they have a role in shaping the solution. I also learned that you don’t need to have every answer before taking the first step. Sometimes the best strategy is to start small, measure, learn, and adapt together.

– Sudeepthi Garlapati

Founder & CEO

Naarg Data Media Services

I had to manage a leadership challenge when early customer feedback suggested two different paths. One path leaned into stronger emotional positioning, the other leaned into careful technical education. Both had merit, but the category carries scientific gray areas, and exaggeration can create short-term lift while undermining retention and brand trust later.

The solution was not choosing one camp over the other. Instead, I separated inspiration from substantiation. Emotional language could open attention, but any statement touching sleep, recovery, inflammation, or environmental exposure had to reflect the actual quality of evidence. That reduced internal tension because each function understood its lane. The lesson was that leadership maturity often means designing constraints that let teams move quickly without borrowing confidence from uncertain science.

There are a handful of us, so the room I had to win over was three people sitting close enough to hear each other type.

The change was a cap. We carry 28 hand-picked products, and I decided that number would stop moving, so a new line only comes in when an existing one leaves. Everybody else wanted the opposite, and they had the better stories. They field the questions, they know how often somebody asks for a brand we do not stock, and every one of those sounds like a sale walking out.

What shifted it was putting the other half of the line on the same page: cash sitting in stock that turns twice a year; the support load of a product nobody on the team has used on their own hair; the refunds that arrive once a range is wide enough for a customer to pick wrong. Once the cost of a product sat next to the demand for it, the disagreement stopped being about whether I trusted their judgement.

We still argue about which one leaves. That part I would keep.

A challenge came when demand surged and our leaders had to decide whether to grow through volume or depth. In tax law, that choice carries ethical weight because taking on too many matters without screening can hurt taxpayers. I led the team toward a slower path by tightening acceptance standards and making matter fit clearer. We invested time training leaders to turn down cases that were not right.

That experience reinforced a principle that guides how we lead. Sustainable growth often comes from restraint rather than expansion. Teams build confidence when standards are clear and applied fairly under pressure. The strongest culture develops when leaders show that revenue never comes before professional judgment.

At my previous company, we reached a point where expanding into a new business segment would make us significantly more competitive in RFPs. Our core strength was a leadership team with deep tenure and institutional knowledge. The new segment fell outside their areas of expertise.

Pursuing it meant bringing in new leadership and revising established reporting structures. Understandably, the existing team was concerned that these changes could erode the culture we had spent years building.

The approach:

1. Conducted a SWOT analysis with the leadership team. We jointly identified our strengths, weaknesses, opportunities, and threats, which gave everyone a shared, honest starting point.

2. Strengthened the hiring process. We introduced a behavioral and personality assessment to better understand candidates, paired with multiple interviews involving key members of the leadership team.

3. Involved the team in redesigning the organizational chart. Existing leaders had a direct hand in shaping the new structure, including how the new segment would fit in.

4. Launched an internal and external marketing campaign that gain-framed the expansion. This positioned existing leaders as visible voices in communicating the change across the company.

5. Opened new-segment roles to internal candidates first. Existing leaders had the opportunity to interview for positions they felt qualified to pursue.

Lessons learned:

1. Patience, patience, patience. Giving everyone a voice requires patience and genuine respect for the feedback you receive.

2. Set the example. Uphold the integrity of the process you all agreed to.

3. Follow up in writing. Clear written communication ensures decisions are documented and accurately reflect their intent.

4. Be ready for pushback. When tensions rise, steer the conversation away from the personal and back to the process.

One recurring challenge at Mills Shelving has been balancing growth with the service standards customers already expect from us. More enquiries and larger projects are positive, but growth can quickly expose weaknesses in quoting, stock planning, delivery and communication.

Our approach has been to break the customer journey into stages and identify where additional volume creates pressure. Instead of simply asking people to work faster, we look at the underlying process and decide what needs to be standardised, delegated or improved.

The biggest lesson for me is that leadership during growth is often about removing bottlenecks. If every important decision still has to pass through one or two people, the business hasn’t really scaled.

One leadership challenge was moving from years in food and CPG into EVKII after selling Julian Bakery. My first two agency clients were a cybersecurity company and an online auto dealership, industries far removed from product formulation. I had to separate what was truly industry-specific from what was a transferable growth principle.

The lesson was that reliable measurement travels well. Every business needs to know where leads originate, how they convert, and which activities produce a return. Leadership became less about having every answer on day one and more about asking the right operating questions, then learning the client’s business quickly.

One of the most significant leadership challenges I faced was navigating a period where our leadership team had different views on the direction of the business. We all agreed on the ultimate goal, but there were strong disagreements about priorities, resource allocation, and the pace of growth. The difficult part was that there was no obvious right answer, and delaying a decision would have created even more uncertainty for the team.

My approach was to focus first on alignment before action. Rather than debating individual tactics, I worked to ensure everyone agreed on the primary business objective we were trying to achieve. Once we had clarity on that, it became much easier to evaluate competing ideas based on how well they supported the goal.

During a busy season, we were dealing with supply chain issues while also rolling out a new drone-based property inspection system.

We don’t just send company memos or emails. I worked closely with our team, walked them through the new system, and gave them a chance to raise concerns and see how it would help them. We also set up a group chat between locations so teams could quickly share information about materials and help each other keep jobs moving.

From that experience, we handled change better. It wasn’t enough to say the new technology would make the company more efficient. We had to show the team how it could help them turn inspections faster, close more jobs, and ultimately improve their own results.

I came up inside big, structured companies, where the senior person in the room is expected to decide and everyone else executes. That instinct followed me into founding my own thing. Early on, when something got hard, I’d step in and make the call myself — fast, decisive, and quietly corrosive. I thought I was leading. I was actually teaching a sharp team to stop thinking, because whatever they brought me, I’d override it anyway.

The approach I took was uncomfortable and simple: I made myself the last person to speak, not the first. In the meetings that mattered, I’d put the problem on the table and then shut up until everyone else had committed to a view. Sometimes they landed somewhere I wouldn’t have. I let it ride anyway, unless it was truly going to hurt us.

What I learned is that a leadership team is only as strong as the room’s willingness to disagree with you. If you’re always right, you’ve built a team of narrators. The change wasn’t a strategy. It was me talking less.