MoneyRead the article
Visibility = danger
Avoiding posting
Open Code← All Code lists28 Codes
Visibility and Success Codes
When people start to notice, and the opportunity feels harder to take
Wanting success and feeling safe inside success are different questions. These Codes focus on the hidden costs attention and growth may seem to carry.
Read the statements below to find a starting point. Some have an article you can read here; others open in Explorer, where you can test Codes from packs you own.
01
Being seen
Codes that connect attention with exposure rather than opportunity.
MoneyCheck your access in Explorer
Visibility = risk
You remove the result from a case study because it reveals too much success.
Open in ExplorerMapRead the article
Wealth = separation
I hide gains, reduce ambition or keep income similar to my group so difference cannot threaten connection.
Open CodeSafetyCheck your access in Explorer
Safety = invisibility
Avoids situations that would test this pattern directly.
Open in ExplorerChangeCheck your access in Explorer
Visibility = dangerous
Avoids situations that would test this pattern directly.
Open in ExplorerConfidenceCheck your access in Explorer
Confidence = exposure
Avoids situations that would test this pattern directly.
Open in ExplorerMediaRead the article
Attention = value
Chasing visibility, overexplaining, performing for response, or feeling flat when nobody notices.
Open Code02
Success brings a cost
Codes that attach loss, guilt or pressure to a positive result.
ImportanceRead the article
Success = pressure
Sabotage.
Open CodeSuccessCheck your access in Explorer
Success = outgrowing others
Avoids situations that would test this pattern directly.
Open in ExplorerSuccessCheck your access in Explorer
Success = endless effort
Avoids situations that would test this pattern directly.
Open in ExplorerFamily LoyaltyCheck your access in Explorer
Success = disloyal
Avoids situations that would test this pattern directly.
Open in ExplorersuccessCheck your access in Explorer
Success = for other people
Minimising genuine wins as flukes or luck
Open in ExplorerearningRead the article
Earning = guilt
Giving work away for free or significantly below value
Open CodeworthRead the article
Visible success = worth
Worth fluctuating with income metrics
Open Code03
Growth changes the rules
Codes that make a larger role or reach feel destabilising.
MapRead the article
Growth = loss of control
I interrupt momentum, avoid demand or reduce capacity as soon as growth brings new systems and responsibility.
Open CodeMoneyCheck your access in Explorer
Leadership = obligation
Avoiding growth.
Open in ExplorerbelongingCheck your access in Explorer
Ambition = disloyalty
Downplaying financial goals in community or political contexts
Open in ExplorersufficiencyCheck your access in Explorer
More = better
I chase higher income, reach or client numbers and feel restless even after meaningful achievement.
Open in ExplorerChangeCheck your access in Explorer
Growth = loneliness
Avoids situations that would test this pattern directly.
Open in ExplorerMoneyCheck your access in Explorer
Comfort = complacency
You create a new urgent target as soon as the current one is reached.
Open in ExplorerCommunityCheck your access in Explorer
Leadership = attack
Avoids situations that would test this pattern directly.
Open in Explorer04
Retreat after momentum
Codes that explain why progress can trigger a protective step back.
MoneyRead the article
Money = pressure
I avoid earning more, expanding, or looking closely at my finances.
Open CodeMoneyCheck your access in Explorer
Money = authority threat
Minimizes visibility or growth to avoid scrutiny, envy, or perceived backlash.
Open in ExplorerWork & AuthorityCheck your access in Explorer
Feedback = attack
Avoids situations that would test this pattern directly.
Open in ExplorerMoneyCheck your access in Explorer
Price = judgement
Underprices, delays asks, or overdelivers to secure safety through approval.
Open in ExplorerSuccessCheck your access in Explorer
Success = being controlled
Avoids situations that would test this pattern directly.
Open in ExplorerAskingCheck your access in Explorer
Receiving help = loss of control
Avoids situations that would test this pattern directly.
Open in ExplorerReceiving CriticismCheck your access in Explorer
Criticism = rejection
Avoids situations that would test this pattern directly.
Open in ExplorerA next question