The questions leaders ask before they reach out
For CEOs and Founders
I feel something in my organization isn't working the way it should. What are the signs that it's time to bring in outside help?
The clearest sign is this: you keep having the same conversations, making the same decisions, and the same problems keep coming back.
Other signs include a leadership team that is capable on paper but not delivering as a group, strategies that get agreed on but never fully executed, and a CEO who is in the middle of everything because nothing moves without them.
Most leaders feel this before they can name it.
That feeling is not noise - it is a signal, and it has a price tag.
Every month it goes unaddressed costs you in slow decisions, missed opportunities, and leadership energy spent managing friction instead of driving growth.
We're growing fast but it feels like firefighting - everything is urgent, nothing is moving forward. Is that just part of scaling or is something actually broken?
When firefighting becomes your operating mode - when every week looks like the last one and the problems that were supposed to be temporary have become permanent - something is broken, not just busy. Fast revenue growth almost always moves faster than the organization's ability to absorb it.
A team that worked at $1M ARR cannot automatically run a $3M company. A team that worked at $5M ARR cannot automatically run a $10M company. A team that worked at $20M ARR cannot automatically run a $50M company.
The way decisions get made, who owns what, how the leadership team communicates - all of it has to evolve at every stage, and it rarely does on its own.
Companies that mistake structural breakdown for growing pains spend years paying for it in turnover, missed targets, and a CEO who cannot get out of the weeds.
My leadership team is smart and experienced but we keep having the same conversations without getting anywhere. What is actually happening?
When a capable team keeps circling the same issues without resolution, it is almost never a problem because you chose wrong people.
Something else is making it necessary to keep circling back - and it will keep doing so until that something is named and addressed.
Something is making the real conversation impossible - an unspoken disagreement about direction, a tension nobody will name directly, or a pattern where people agree in the room and don't follow through outside it.
Every hour your leadership team spends in a repeat conversation is an hour not spent executing.
In a six-person leadership team at average senior compensation, one wasted meeting per week costs over $150,000 a year in leadership time alone - before you count what did not get decided or built, and that should be unacceptable.
As the CEO, I find myself at the epicenter of almost every decision. My team is capable but nothing moves without me. What is actually happening and how do I fix it?
When everything routes back to the CEO, it is rarely because the team is incapable.
It is because something in the organization makes coming to you "the right answer" instead of deciding independently.
That could be unclear ownership, a culture where mistakes are not safe, leaders who have learned that you will reverse their decisions anyway, or a structure that was never designed for distributed decision-making.
This pattern has a hard ceiling: the company can only grow as fast as you can personally process.
And the longer it runs, the more entrenched it becomes.
Leaders who break this pattern early scale. Those who do not become the single most expensive bottleneck in their own company.
We have a clear strategy but it's not translating into good enough results. Why does that happen and what can be done about it?
McKinsey research shows that roughly 70% of strategic transformations fail to meet their objectives - not because the strategy was wrong, but because the organization was not built to execute it.
Most companies do not fail at strategy.
They fail at the conditions that make execution possible: who owns what, how fast decisions get made, whether the leadership team is pulling in the same direction, and whether the people two levels down understand what they are supposed to be doing and why.
If your strategy is clear but results are not good enough, the gap is organizational.
That gap has a direct cost - every quarter of underperformance against a strategy you already invested in building is money you spent twice.
A key leader on my team is not performing as well as expected. I want to figure out what to do about it and how long I can afford to wait.
Most leaders wait longer than they should on this - and the cost of waiting is almost always higher than they expect.
Underperformance at the senior level does not usually resolve on its own. It spreads.
It affects the people who report to that leader, the decisions that do not get made well, and the message it sends to everyone watching how you handle it.
Before deciding what to do, it is worth understanding what is actually driving the underperformance - whether it is a capability issue, a role fit problem, or something the organization itself is creating.
Getting that diagnosis right changes the right action.
But the longer the situation stays unresolved, the more it costs in business outcomes, team morale, and the time you spend managing around it.
How is this different from sending someone to an executive education program, a psychometric assessment like a behavioral or personality profile, or an online leadership course?
Assessments and programs give you insight about a person. They do not change the organization that person operates in.
A leader can complete a behavioral profile or spend two weeks at an executive program and return to the same team, the same pressures, and the same unresolved issues waiting for them.
The insight does not automatically transfer into different results at work.
Organizational development work happens inside the actual company - with the real team, on real decisions, in the real context.
It changes the conditions that shape how people lead and decide, not just how they think about themselves in isolation.
That is a different intervention, and it produces results that classroom learning and self-assessment cannot.
I've worked with consultants before who gave great recommendations that nobody implemented. How is this different?
A recommendation that does not get implemented costs twice - the fee and the continued cost of the problem it was supposed to solve.
Most consulting engagements fail at implementation not because the diagnosis was wrong, but because the work stopped at the slide deck.
This practice does not deliver reports and exit.
It works inside the organization - in the room with the leadership team, on real decisions, through the resistance - until something is actually different in how the company operates.
The test is not the quality of the output. It is whether the business performs differently six months later.
How do I calculate the cost of NOT solving this problem?
Start with this: a leadership team of six senior people, at average fully-loaded compensation, that spends four extra weeks on a single strategic decision costs roughly $90,000 in leadership time alone - before opportunity cost.
A senior leader who leaves because the organization did not address what was driving their dissatisfaction costs 1.5 to 2 times their annual salary to replace.
A strategic initiative that stays stuck for six months in a 50-person company can consume $500,000 or more in leadership attention.
​
These numbers are not hypothetical - they are the math behind situations that happen in scaling companies every quarter.
​
The question is not whether organizational problems have a price. They do.
The question is whether you have done the calculation before deciding whether to act.
In almost every engagement, the fee is smaller than the monthly cost of the problem it solves.
That is not a sales claim - it is the math most leaders have not done yet.
Things are actually going pretty well right now. Why would I invest in organizational work when there's no crisis?
Because the patterns that create crises are present long before the crisis arrives - they are just not visible yet.
The leadership team that is not quite aligned, the ownership gaps that have not caused a failure yet, the culture that is working at 40 people but will not survive at 120 - these are not invisible.
They are just tolerable right now.
Organizational work done proactively costs a fraction of what it costs after a breaking point.
The companies that scale without major disruption are almost always the ones that built organizational health deliberately, before they needed to.
Waiting for the crisis is a choice. It is just a more expensive one.
I know we need this but I'm not sure I have the bandwidth to take this on right now. What does engagement actually ask of me?
Here is the honest version: the reason you do not have bandwidth is often the exact problem the engagement addresses.
CEOs who are at the center of every decision, managing a leadership team that is not fully functional, and absorbing organizational friction that has never been resolved - they are the ones with the least time.
And they are the ones who gain the most.
The engagement is designed to be lean on your schedule. It does not ask for workshops or offsites. It works with you in the context of your actual work.
The cost of not having bandwidth to fix what is consuming your bandwidth is that it keeps consuming it - and the problem that is costing you time now will cost you more time next quarter than it does today.
For VCs and Portfolio Companies
One of my portfolio companies is scaling fast but the leadership team is not keeping up with the growth. What does that cost me if I don't address it?
A leadership team that cannot keep up with growth is a valuation risk, a round risk, and a retention risk - often at the same time.
The research on startup underperformance consistently points to team and leadership problems as a primary driver, ahead of market and product issues.
When the leadership team is not functioning at the level the business requires, execution slows, key people leave, and the gap between what the company could be doing and what it is actually doing grows every quarter.
That gap has a direct impact on the metrics that matter at the next round.
And the longer it runs unaddressed, the harder it is to close before the next milestone becomes a conversation with investors.
We just completed an acquisition. How quickly do culture and leadership problems show up post-merger and what happens if we don't address them in the first year?
Culture and leadership problems in a post-merger environment typically surface within the first 90 days and compound through the first year.
Most M&A value destruction does not happen because the deal was wrong. It happens because the cultural and leadership integration was underinvested relative to the financial and operational integration. The window for getting it right is narrow - and it does not stay open.
Organizations that address leadership alignment and cultural integration in the first year retain more talent, make better decisions faster, and reach operational effectiveness significantly sooner.
Those that do not spend years managing the consequences in turnover, performance gaps, and a combined entity that never fully functions as one.
I need my portfolio company to be Series B ready - operationally, culturally, and from a leadership perspective. What does that actually require and how long does it take?
Series B readiness from an organizational perspective means the company can operate at the next level of scale without the founder being the primary glue holding everything together.
It means a leadership team that makes decisions well together without constant intervention, a culture that can attract and retain the talent the next stage requires, and execution that works without everything routing back to the top.
Most companies are further from this than they realize - and the gap is not about headcount. It is about how the organization operates.
The work required is almost always clearer and more tractable than it looks from the outside, and the earlier it starts, the less it costs relative to the round it is protecting.
Can you point to specific business outcomes from this work - not just qualitative feedback but actual numbers?
Yes. An AI hardware startup that had been stuck at the same revenue and headcount for two years tripled ARR and more than doubled headcount within 18 months of resolving its leadership situation - Series A closed, Series B in progress.
A company with 10 strategic initiatives that had not moved in over five years completed 4 of them and has 4 more in active progress, including an AI transformation of its core operations.
A leadership team that completed a full international expansion within 24 months of resolving an internal conflict that had made expansion impossible for years.
And Israel Aerospace Industries' aviation division, which improved net profitability from $1M to $46M on comparable revenue over four years during a period of organizational and leadership alignment work - public financial data, NDA-protected engagement.
Organizational development does not close deals or build products. It removes what slows down the people who do. These are the numbers that have come from that.
For HR Leaders and People Teams
As an HR leader and Business Partner, how do I make the case internally for this kind of external OD work, and how does it complement what my team already does?
The strongest internal case is not about what HR cannot do. It is about what an external practitioner can do that internal teams are structurally not positioned to do.
An HR leader or business partner is part of the organization they are trying to diagnose.
They carry relationships, reporting lines, and political realities that shape what they can say, to whom, and in what room.
An external OD consultant operates outside that structure - which means they can surface the conversations, name the tensions, and work with the leadership team in ways that would be impossible or career-limiting from the inside.
The work is designed to run alongside your team and strengthen what you are already doing - not to replace it or compete with it.
What is organizational constellations and why does it surface things that conventional OD approaches and HR interventions often miss?
Organizational constellations is a certified methodology that maps the hidden patterns driving behavior in an organization - the loyalties, exclusions, and structural tensions that shape how people act before they consciously decide how to act.
Most HR and OD interventions work on what people report - in surveys, assessments, and conversations. Constellations works on what is actually operating underneath those reports.
It is particularly effective for persistent problems that have not responded to conventional approaches: leadership conflicts that keep regenerating, cultural patterns that survive personnel changes, and organizational structures that produce the same problems regardless of who fills the roles.
It consistently surfaces material that standard diagnostic tools miss - and it does so in a way that creates movement rather than just insight.
We have engagement scores, performance reviews, and 360 feedback. Why isn't that enough to diagnose what's really happening in the organization?
Engagement scores, performance reviews, and 360 feedback measure what people are willing to say in a structured format to an audience they know is receiving the data.
The most important things happening in an organization are almost never the ones that show up clearly in those instruments.
They show up in what does not get said, in patterns that persist across personnel changes, and in the gap between what the data reports and what leaders actually experience day to day.
These tools tell you where the symptoms are. They rarely tell you what is generating them - which is usually something people were not positioned to report and the instruments were not designed to capture.
We work with Israeli and American teams across different cultures and time zones. Do you have experience with that specific context?
Yes - this is a specific area of practice.
Eitan Nussbaum is a native bilingual in English and Hebrew, has worked extensively with organizations in both Israel and the United States, and has direct experience with the specific friction points that arise in Israeli-American leadership teams - including differences in communication style, hierarchy, directness, decision-making, and how conflict gets handled or avoided across the two cultures.
The Israeli tech ecosystem and the Boston innovation community are both familiar territory.
If your organization is navigating that bridge, the context does not need to be explained from the beginning - it is already understood.
For Leaders Stepping Up
I just stepped into a new leadership role or was promoted into a bigger position. Is this the right time to bring in support or should I wait until I've established myself?
The instinct to wait until you have established yourself before bringing in support is understandable - and it is usually the wrong call.
The patterns a new leader sets in the first 90 days are the hardest to change later.
The relationships, the decision-making habits, the dynamic with the team - these get established early, often before the leader has enough information to set them intentionally.
Support at the start of a transition is not a sign of weakness. It is how the transition gets designed rather than just survived. Waiting until you feel established often means waiting until the patterns you needed to avoid are already in place - and changing them later costs more than getting them right from the start.
​
This transition is so close to my practice that I wrote a book about it.
My third book - currently available in Hebrew and forthcoming in English as "Step Up" - is specifically about what surprises leaders as they move into bigger roles: from team lead to organizational leader, from junior management to senior and executive levels.
The gap between what they expected and what the role actually required is one of the most consistent patterns I have seen across hundreds of leadership transitions. It is a specialty, not a side note.
I want to invest in a manager or leader on my team who just stepped up into a bigger role. Can this work be used as a development investment for someone on my team, not just for me as the CEO?
Yes - and this is one of the highest-return investments a leader can make in their organization.
Research shows that leaders who step up without structured support take six to twelve months longer to reach full effectiveness than those who get it.
At VP or senior director level, that delay costs $35,000 to $70,000 in salary alone - before you count the decisions that did not get made well, the team that did not get led well, and the strategic work that did not get done.
The engagement can be scoped specifically for a leader in transition - helping them understand what the new role actually requires, letting go of the habits that worked at the previous level, and building the capacity to lead at the level they have been asked to reach.
What made me successful at my previous level seems to be working against me now. Why does that happen and what do I do about it?
This is one of the most common and least discussed leadership problems - and it is almost never a capability issue.
The behaviors that made you effective at one level were selected for by that level.
Speed of execution, hands-on problem solving, direct control, doing things yourself because you do it best - these are assets at one stage and liabilities at the next.
The step up is not about working harder at what worked before.
It requires letting go of the identity and methods that produced your previous success and building something genuinely new.
Most leaders try to solve it by doing more of what worked before - which is the natural instinct and the wrong move. The work is to understand what the new level actually requires and close that gap deliberately, before the cost of not doing so shows up in your results or your relationships.
We're a 30-person company. Are we too small for this kind of work, or is earlier actually better?
Earlier is almost always better.
The patterns that cause the most damage at 150 people - the communication gaps, the decision-making bottlenecks, the cultural defaults that become invisible because they have always been there - are established at 30.
At 30 people, they are visible, malleable, and inexpensive to change.
At 150, they are structural and expensive to undo.
The companies that scale most smoothly are the ones that built organizational health deliberately from early on - not as a reaction to a crisis, but as a foundation for the growth they knew was coming.
If you are at 30 people and you can already feel friction, that friction does not disappear with more headcount. It scales with it.
Still have a question that isn't answered here?
Every organization is different.
If what you are dealing with does not fit neatly into any of the questions above, that is not a problem - it is usually a sign that the situation has more complexity than a standard answer can address.
That is exactly what the exploratory call is for.
Learn more about Eitan Nussbaum's background, credentials, and approach - read the full About page.