Leading at scale: how to make the shift from hub to network
Last week we established that the hub model breaks down at scale. When you are the central node for every decision and piece of information in a large organisation, you quickly become the bottleneck. Instead, you will need to shift from being the single hub to the architect of a system with multiple, autonomous nodes. But how? Here’s a few thoughts...
Design decision rights. Map the main recurring decisions and assign ownership explicitly. If a decision is reversible and can be made with confidence, push it to the nearest node. Your role is to define the boundaries within which those nodes operate, not to process every transaction yourself. Then hold those boundaries - so people learn not to depend on you for all the things.
Build feedback loops. You used to know the mood of the organisation because you were the central receiver. You could walk the floor and pick up the vibe. At scale, you need deliberate mechanisms. Some possibilities:
· Make sure your leadership team can speak freely with you, and take care to ensure they are creating a culture where their teams can speak freely with them. If challengers are silenced or punished, you’re never going to know what’s really happening
· Have regular, structured skip-level conversations where you listen rather than solve. Notice the patterns that emerge over time.
· Read the attrition data properly... not just who is leaving, but from which teams, under which managers, and how long they stayed. Turnover patterns are a feedback loop that is already running
· Build your own network of trusted people at various levels who will tell you the truth (this is personal influence, but used deliberately as a diagnostic tool rather than a leadership crutch)Practise strategic silence. In a hub model, your voice dominates but in a network your voice can drown out the signal. Wait, ask questions, let the nodes struggle with the problem before you intervene. Your silence allows the network to think for itself.
Measure your success by your absence. Not from the system as a whole – you definitely still need to be visible – but from the day to day mechanics of the machine. If the network collapses when you disconnect, you have built a dependency, not a system. True scale is when the nodes communicate and resolve issues without routing everything through you.
None of this means you become redundant. There are decisions and tensions that belong only to the most senior leader: setting the strategic direction, resolving conflicts between nodes that cannot reconcile on their own, and holding the standard on values when the system is tempted to compromise.
This shift in operating style can also mean a change in how you find satisfaction: from the reward of personally fixing a crisis (immediate) to the reward of designing a system where crises are prevented (delayed and abstract). It takes time to value the invisible architecture over the visible fix.
Stepping up means letting go. If you are navigating the transition to leading at scale and need support reshaping your leadership approach for a larger system, let's connect.
Until next week,
Madeleine
I help accomplished professionals untangle difficult career questions so they can thrive in work and life.
1. Want to find out more? Send me a note and let me know.
2. Feeling unfulfilled, overworked or unclear about what next? Work with me to identify what is holding you back and make a plan for more powerfully and enjoyably pursuing goals that matter to you. Contact me to find out more.
3. Join my list to receive regular articles and insights, early news about programs and offers, and respect for your inbox.
4. Follow me on LinkedIn to stay connected.
5. Prefer to talk? Choose a time and it will drop right into my schedule.
Click below to share this on your socials…