0
1
Emotional intelligence has an image problem among analytically-minded leaders. Not because they lack it, but because the concept is almost always packaged in language that repels them.
Strip away the motivational packaging and it's a system with four components: self-awareness, self-regulation, social awareness, and relationship management. Each one is observable, practicable, and improvable.
The diagnostic question that actually works: which of those four is the weakest link in your leadership right now?
Name the specific component, and it becomes solvable. Leave it vague, and it stays a personality critique that nobody knows how to act on.
0
0
Always wonderful to recieve 5-star feedback!
0
1
Sustainable leadership isn't about working less. It's about working on different things.
The leaders who maintain their effectiveness over a decade aren't doing it through stamina. They built decision-making capability into their team, created information systems that move context without them being the conduit, and designed a culture where initiative is the default.
That shift feels slower than doing it yourself. Until the compounding kicks in and the business stops breaking every time you step away.
What would your week look like if you only worked on things that genuinely need you?
0
1
The most expensive input in most organisations is the input that never arrives.
Not because people are not speaking. Because the system was never designed to receive what they were saying.
In Victor's business, the information needed to identify a significant strategic problem had existed within the team for months. It hadn't reached the decision-makers who needed it, not through dishonesty, but through accumulated experience of what happened when difficult things were raised.
The fix was not a new feedback channel. It was changing what happened the first few times someone brought a problem before it was urgent. Two or three instances of honest input being received with curiosity rather than scrutiny reset what the team believed was possible.
The information was there. The design work was building the conditions for it to move.
Swipe for the pattern and what changed.
1
1
Most leaders who design hybrid working for their teams apply a completely different standard to themselves.
Flexible on location. Rarely flexible on hours, rhythm, or the expectation of constant availability.
The leaders who have made the actual shift describe it the same way: not working less, but working differently. Protected time for strategic thinking. Async by default for anything that doesn't require a live decision. A calendar that reflects priorities rather than reactive demand.
That shift doesn't come from better time management. It comes from building an organisation that doesn't require the leader's presence to keep moving.
The flexibility is evidence the architecture is working. Not the reward for finishing it.
What would a well-designed week look like for you right now?
1
1
Most organisations have strategic objectives. Very few of them reliably influence how decisions get made on a Tuesday afternoon.
The gap is not about the quality of the strategy. It's about translation: the work of connecting a strategic objective to the specific decisions, trade-offs, and priorities that teams actually face.
Without that translation, the objective sits in a document while the real work is driven by what's urgent, visible, and loudly expressed. The strategy is technically in place. It's practically invisible.
Translation is the step most strategic planning processes skip.
What would it mean for your strategy to actually change what your team does this week?
2
1
When communication breaks down in a team, the instinct is to look at the people.
Someone wasn't responsive enough. Someone didn't flag it clearly. Someone dropped the ball.
That framing is almost always wrong, and the interventions it produces almost never hold.
The more useful question is: what did the system make easy, and what did it make hard? Communication gaps that keep appearing in the same place, in the same form, are structural signals. They point to unclear ownership, a cadence that doesn't match the decision rhythm, or an escalation path that quietly punishes people for using it.
Each of those has a specific fix. None of them require anyone to become a different person.
Swipe for the three structural causes and what to do about each.
1
1
Most leaders who value transparency express it as a personal quality. They share what they know, communicate openly, and try not to withhold things that would help their team.
That's a good start. It is not a system.
Personal transparency depends on the leader's attention, energy, and presence. Designed transparency moves information because the structure delivers it, not because the leader decided to share it today.
The difference shows up most clearly when the leader is stretched or absent. In a personally transparent organisation, information stops. In a structurally transparent one, it keeps moving.
Which kind are you building?
1
2
Strategic clarity isn't about how often you communicate.
It's about predictability.
The team that always knows the current priorities, understands what changes and why when something shifts, and knows which direction to face when things are ambiguous: that team doesn't need constant reassurance. They've learned that the information they need will be there when they need it.
The leader who produces that experience isn't necessarily communicating more than anyone else. They're communicating in a way that eliminates the need to guess.
Guessing is expensive. It produces decisions made on assumptions rather than information, work completed in the wrong direction, and the kind of misalignment that only surfaces once it's cost something.
Consistency in strategic communication isn't a style choice. It's architecture.
What would the people in your team say they're currently having to guess?
0
1
This week we've been exploring what it takes for an organisation to function well without the leader as the central information hub.
Which surfaces a specific paradox.
The leaders who hold strategy close, translating it downward in the form of instructions, don't produce tighter execution. They produce dependency. The team executes instructions without understanding the reasoning, which means every variation, every unexpected situation, every trade-off requires a trip back to the top.
The leaders who invest in strategic clarity produce something different. A team that can reason about the work, not just execute it. A team that knows which priority wins when two things conflict. A team that handles the variations without asking.
The deeper the team's understanding of the strategy, the less the strategy requires managing.
Tomorrow on LinkedIn I'll explore what it looks like to build strategic clarity as a structural practice, not a communication exercise.
Where in your business is strategy operating as instruction rather than as shared understanding?
0
1
There are two versions of Friday afternoon in most organisations.
In the first, you're finding out about things. Problems that have been sitting quietly for a week. Decisions made on incomplete context. Misalignments between what the team was working on and what actually mattered.
In the second, you're working with information that's been flowing all week because the system was designed to move it. Nothing is a surprise. The relevant things surfaced early enough to do something about them. The afternoon is for thinking, not repair.
The difference between the two versions isn't culture, communication style, or team quality. It's architecture.
One organisation has designed how information moves. The other is relying on people to remember to share it.
Architecture is fixable. Culture takes much longer.
What does your Friday afternoon usually tell you about how information is flowing during the week?
0
1
When team members stop raising issues, most organisations read it as a positive signal.
It usually isn't.
The team has made a rational calculation: the cost of speaking up relative to the expected benefit, based on what experience has taught them. When that calculation tips against raising things, the filter goes up without anyone deciding to close it.
The standard response is to ask for more feedback: surveys, open-door policies, all-hands questions. These signal intent. They don't revise the underlying calculation.
The only thing that revises it is a specific, visible instance where input led to a different outcome. One conversation where something was raised, something changed, and the connection was made explicit. That single instance, if it's genuine, shifts the expected benefit of raising things.
The organisations that sustain open feedback loops don't do it by being more open. They do it by being consistently and specifically responsive to a small number of inputs.
Swipe for how the loop closes, and what actually reopens it.
0
0
Always wonderful to recieve 5-star feedback!
2
2
Most organisations have a strategy. Fewer have strategic clarity.
The difference: strategic clarity is when the people making daily decisions know how their work connects to what the business is actually trying to do.
It doesn't travel by announcement. A clear all-hands presentation, a well-written strategy document, a well-run quarterly review: none of those reliably close the gap. Understanding strategy in the abstract and using it to inform daily trade-offs are different skills, and the second one doesn't follow automatically from the first.
The diagnostic is specific. Ask three people in your team, at different levels, to explain in their own words why the project they're working on matters to the business. No prompts. No reference to the strategy document. Just the connection, in their own words.
The gap between what you expect to hear and what you actually hear is a direct measure of how far your strategy has travelled.
1
1
Many technically-minded leaders restrict information flow without realising it.
Not from secrecy. From a protective instinct: the concern that information travelling without the right judgment attached to it will produce bad decisions.
The instinct isn't irrational. The problem is structural. One person cannot scale as the translator between raw information and actionable context. The bottleneck grows with the organisation.
The team doesn't stop deciding. They decide on less reliable data. They stop raising the gaps, because asking for context that never arrives is demoralising. The organisation ends up with the same number of poor decisions, plus a leader who's trying to review all of them.
Information, in an organisational context, isn't depleted by sharing. It multiplies.
Swipe for the pattern and the reframe.