The Solo Capability Question
Every dependency you build is a choice to leave a capability undeveloped.
If your external partners were unavailable today, could your internal lead independently produce content, code the platform, and manage logistics to ensure a successful launch? This is not a budget issue. It is a question of whether you chose dependency deliberately — and what risks follow when that choice fails.
The Question Nobody Asks Until It's Too Late
Every complex global project faces moments when support structures fail. The agency misses a deadline. The vendor becomes unresponsive. The freelancer accepts another client. The partner responsible for managing the content shoot is unreachable the night before the launch.[3]
In those moments, the question shifts from whether partners are performing to whether anyone within the organisation can complete the necessary tasks.[4]
Often, the answer is no — not because of a lack of internal talent, but because the organisation was designed on the assumption that partners would always be available.[1]
Dependency as a Design Choice
We rarely discuss dependency as a design choice. Instead, we frame it as collaboration, efficiency, or focusing on core strengths. Sometimes, it is all of these — but it is still dependency.[2]
Dependency is also a risk — a belief that the external party will perform, be available, and share your priorities. This risk has a cost that becomes clear only when the launch fails.[3]
The solo capability question does not oppose collaboration. It asks you to understand the risks involved and prepare for scenarios where external support is unavailable, so the launch can still happen.
What Solo Capability Actually Means
Solo capability does not require one person to handle all tasks routinely. It means having at least one person in the organisation who can manage all critical functions if needed — so the organisation can continue when support is absent.[5]
This person can produce content, code platform updates, manage logistics, oversee vendor relationships, and prepare briefs. They are the final safeguard — and they understand that role.[7]
In high-stakes global growth environments, this individual is essential. Their presence determines whether a launch recovers from a crisis or fails — and that is what makes the role decisive.[4]
How to Assess Your Organisation's Solo Capability
One approach is to run a scenario test: remove all external support from a planned launch on paper, and map out which internal team members can cover each critical function. Another method is capability mapping — list every essential task required for success, then identify who, if anyone, can execute each one independently.[5]
These exercises reveal strengths, highlight gaps, and prompt conversations about where to build internal resilience. They are not about creating anxiety — they are about creating clarity before the moment of crisis, not during it.[6]
The organisations that do this work in advance are the ones that recover fastest when the scaffolding fails. The ones that skip it discover their gaps at the worst possible time.[4]
The Human Version of This Question
There is a version of this question that has nothing to do with business. In astrology, the Saturn placement in a birth chart often reveals where we have built the most elaborate scaffolding — the structures, routines, and external authorities we rely on to feel capable. Saturn asks: what would you do if the scaffolding were removed?
Not as a threat — as a diagnostic. The person who has never tested their own capability without the structure around them does not know what they are actually capable of. The structure may be necessary. But it should be chosen, not inherited by default.
The solo capability question, in its personal form, is not about isolation. It is about knowing — with clarity — what you can do when no one is watching and no one is coming. That knowledge changes how you build your dependencies. It makes every collaboration a choice rather than a necessity.
Three Questions Worth Sitting With
If your external partners disappeared today, who inside your organisation could close the loop on the launch?
When did you last test your internal capability — not as a backup plan, but as the primary one?
What would you do differently if you knew no one was coming to save it?
The Fool's Wisdom
In tarot, The Fool ventures forward alone — without agency, partner, or safety net. While many see this as reckless, The Fool understands something that most organisations don't: you cannot know what you are capable of until the scaffolding is gone. The card is not about recklessness. It is about the clarity that only comes from standing at the edge without a net.
This is the same lens I bring to the healing side of this work — the question of what you are carrying that was never really yours, and what you are capable of when you stop outsourcing your own authority. If that question resonates beyond the boardroom, the Healing section of this site explores it in depth.
Organisations that succeed in complex global launches are not those with the most partners. They are those with at least one individual who can manage the launch independently if required. Establish internal capability first. Then build collaboration around it.[8]
References
- 1.Kaiser, J. & Buxmann, P. (2012). Organizational Design of IT Supplier Relationship Management. Journal of Information Technology 27(1).
- 2.Raveendran, M., Silvestri, L. & Gulati, R. (2020). The Role of Interdependence in the Micro-Foundations of Organization Design. Academy of Management Annals.
- 3.Palomo, J., Rios, D. & Ruggeri, F. (2007). Modeling External Risks in Project Management. Risk Analysis 27(4), pp. 961–978.
- 4.Nesse, S. (2024). Collective response capacity: Developing crisis leadership in organisations. Journal of Contingencies and Crisis Management 32(3).
- 5.González, A., Sandoval, A. & Heredia, B. (2018). Development of cross-training plans for key personnel in projects. Revista Ingeniería de Construcción.
- 6.Oroszi, T. (2018). A preliminary analysis of high-stakes decision-making for crisis leadership. Journal of Business Continuity & Emergency Planning 11(4), pp. 335–359.
- 7.Cooke-Davies, T. (2002). The 'Real' Success Factors on Projects. International Journal of Project Management 20(3), pp. 185–190.
- 8.Kenda, R., Meslec, N. & Oerlemans, L. (2024). Single versus multiple project teams and individual performance. International Journal of Project Management 42(2).
Also on this platform
The solo capability question has a personal counterpart — the Saturn placement in a birth chart, and what it reveals about the structures we rely on without ever testing them. That territory lives in the Healing section of this site.
Explore the Healing pathProfessional Opinion & IP Notice
This article is original intellectual property drawn from direct professional experience, independent field observation, and proprietary analysis. The views expressed are solely my own and do not represent any employer, client, or affiliated organisation. No part of this work — including its frameworks, arguments, or structure — may be reproduced, forwarded, quoted at length, or used in any form without explicit written authorisation. If you are interested in referencing or republishing this content, please get in touch.