You earned the result. Did you understand the conditions?
Success creates a powerful story. We connect effort to outcome, identify the decisions that worked and turn them into a theory of ourselves. The theory may be partly right. The danger begins when it becomes the whole explanation.
A leader can be highly capable and benefit from an exceptional platform. A business can execute well and enjoy an expanding market. A promotion can reflect hard-earned credibility and the advocacy of someone who opened a door. These explanations can reinforce one another.
The purpose of my Earned, Not Given framework is to make that wider picture visible. It asks four questions: what did you bring, who enabled you, what amplified you, and when did the world make your contribution especially valuable?
The more accurately you understand your success, the more deliberately you can repeat it.
This is an exercise in strategic self-awareness. Recognising the ecosystem does not diminish achievement. It helps distinguish what you can carry into the next challenge from what you will need to rebuild.
Four forces. One outcome. No single-hero explanation.
The original framework expresses the relationship as Success = f(You × Leadership × System × Timing). Read the multiplication sign as a reminder that the forces interact. It is a conceptual model, not an equation fitted to data. Multiplying four self-ratings would not produce a defensible probability of success.
- Individual capability: skill, judgement, adaptability and the discipline to deliver repeatedly. The test is whether the behaviour that created value can travel beyond one familiar setting.
- Leadership & sponsorship: the coaching, feedback, advocacy and access that make capability usable. A strong sponsor may accelerate progress; a single sponsor can also become a point of dependence.
- System & environment: the brand, colleagues, infrastructure, customer relationships and operating model surrounding the individual. These assets can amplify excellent work or conceal a weakness until the platform changes.
- Timing & market: demand, scarcity, capital, technology shifts and chance. Good execution matters, but the same execution can meet very different conditions at different moments.
The boundaries overlap. A leader may create a better system; an expanding market may fund the training that builds individual capability. That is precisely why a neat pie chart of ‘credit’ would be misleading. The task is to identify mechanisms and dependencies, not divide an outcome into imaginary causal percentages.
Explore the conditions behind your result.
Choose one outcome and one time period before you begin: a practice built over twelve months, a transformation delivered, or a move into leadership. Keep that reference point constant as you examine the four forces.
The observatory starts with an illustrative scenario. Switch to ‘Your reflection’ for a blank assessment. Rate each force’s perceived influence, then consider the disruption if it weakened. Those are different judgements: something can have helped greatly without being a dependency you still need.
Explore the examples, change the assumptions and watch the pattern respond. Record a concrete observation against each force. A low rating is not a judgement of somebody’s worth, and a high dependency is a question to investigate rather than a verdict.
Illustrative example · fictional inputs you can change. Switching scenarios resets the notes below.
Ring size = perceived influence.
Each force stands on its own scale.
What value could you create in a different setting?
Skill, judgement, execution, learning and consistency.
Make the next move deliberate.
Explore timing first. This force has your highest expected disruption.
- Timing & marketTest the proposition under a plausible weaker-demand scenario. Define an early signal that would trigger a review.
Notes recorded for all four forces. Ask someone who saw the work to challenge your interpretation.
An explanation needs evidence that could challenge it.
‘I worked hard’ describes effort. It does not isolate its effect. ‘The market was strong’ describes context. It does not establish that execution made no difference. A useful account connects an action to an observable mechanism, then asks what else could explain the outcome.
For capability, look for repeated delivery across different mandates. For sponsorship, identify access or decisions that changed because someone intervened. For the system, examine what the brand, installed customer base or delivery team supplied. For timing, compare the period with relevant demand, pricing or competitive conditions.
Comparisons need care. A different company may have a different product, market, scale or risk appetite. A before-and-after comparison may include several changes at once. Treat these observations as evidence to triangulate, not a controlled experiment.
- State the outcome precisely, including quality, durability and the resources used.
- Write the strongest observation supporting each explanation—and one observation that would weaken it.
- Ask a colleague who saw the work to challenge the account, including contributions you may have overlooked.
- Separate what you know, what you infer and what you still need to test.
Intellectual honesty begins when your explanation can survive a serious alternative.
Change one condition. Then examine the chain reaction.
A counterfactual is a disciplined ‘what if’. If your sponsor moved on, which opportunities would still reach you? If the brand disappeared from the pitch, what would earn the client’s trust? If market demand softened, what would protect the value you create?
Change one condition first so you can explain your reasoning. Then recognise that the forces are connected: a leadership change might also affect resources, team confidence and customer access. The first pass clarifies a dependency; a second pass explores the consequences around it.
Do not read the removal test literally as a prediction of a world with no leadership, no system or no market. The useful question is what happens if an important support weakens substantially, within a realistic horizon. The observatory therefore records expected disruption rather than inventing a percentage of success that remains.
Suppose a fictional practice grows during an AI hiring surge. Strong delivery, a trusted brand and a supportive leader all contribute. If growth slows when demand cools, that does not prove the team lacked talent. It does reveal the need to test whether the proposition is valuable outside the surge. One bounded experiment might be to validate an adjacent client need before committing more capacity.
Portability is the ability to rebuild the conditions.
Complete independence is an unrealistic ambition. Leadership is relational; execution requires systems; every strategy operates in a market. A more useful objective is the ability to recognise the conditions you need and help create them in a new setting.
For the individual, that means retaining the underlying judgement when the familiar playbook no longer fits. For leadership, it means building several credible relationships while acknowledging the people who helped. For the system, it means understanding which practices create value rather than mistaking brand recognition for personal influence. For timing, it means noticing when the assumptions behind a strategy change.
A high-dependency result is not automatically fragile. A complex business should depend on capable people and useful infrastructure. The practical distinction is between an understood, maintained dependency and an invisible dependency with no alternative.
- Preserve: identify a support that works and make its contribution explicit.
- Strengthen: choose one capability that would improve your response to changing conditions.
- Diversify: reduce an avoidable single point of dependence without discarding a valuable relationship.
- Test: run a small, reversible experiment that could expose a mistaken assumption.
For an executive appointment, this changes the conversation. Go beyond the size of the candidate’s previous result. Ask what they inherited, what they personally changed, who enabled delivery and what they would need in the next organisation. A past achievement is evidence to examine, not a guarantee of transfer.
Turn a clearer story into one better decision.
The value of reflection is what changes afterwards. Pick one uncertainty or material dependency from the observatory. Write a test that is small enough to run, meaningful enough to teach you something, and safe enough to reverse.
For example: ‘Over the next thirty days, I will test whether a new client conversation progresses without my usual sponsor’s introduction. I will record the objections, ask for feedback and review what actually created trust.’ The result may confirm capability, reveal the value of an introduction, or show that both matter in different ways.
Before starting, define the observation that would change your view. Afterwards, revisit the original account rather than quietly rewriting it to fit the result. Keep what worked, credit the people and conditions that enabled it, and adjust the next experiment.
Be proud of what you earned. Be precise about what enabled it. Build what makes it repeatable.
Sources & context
The original four-pillar framework, reflection questions and removal stress test. This article expands the reasoning and adapts the exercise; the ratings are subjective, not a validated measure of causal contribution.
Edited and expanded from Qasim MB’s original work ↗.