The original is one click away. Open original ↗
How to ask for what you want and stop holding yourself back
Executive overview
Most people fail to get what they want not because they lack skill or ambition, but because they never clearly articulate their desires — even to themselves. The cost compounds: stuckness, interpersonal conflict, and a quiet erosion of integrity.
The framework is three steps: articulate what you want, ask for it intentionally, and accept the response. Each step has predictable failure modes rooted in fear, people-pleasing, or entitlement — not in the steps themselves.
Not asking for what you want is a form of living out of integrity with yourself.
Signs you need to work on this
- You feel stuck in the same place week after week despite effort
- You experience recurring interpersonal conflict at work
- The stakes feel existentially high, narrowing your focus to fear rather than goals
- You're running from what you don't want rather than toward what you do
Finding out what you want: the dream behind the complaint
- Most people struggle to articulate desires but excel at complaining
- Every complaint implies a dream — a better world where that problem is resolved
- Start with the complaint, then surface the vision it points toward
- Check whether that vision is genuinely inspiring, not just relief from irritation
- If the dream is too embarrassing to say out loud, it probably isn't the real one
- For people-pleasers: tune into subtle signals — mild frustration, low-grade nervousness, quiet preference
- For control-oriented people: peel back the surface demand to find the underlying social or emotional need (e.g. "team alignment" rather than "everyone obeys me")
Integrity as a practical tool
- Integrity here means full self-expression, not just honesty with others
- Ask: is there something I keep thinking about but won't say?
- Suppressed feelings — frustration, boredom, nervousness — are data pointing to unexpressed wants
- Saying it out loud often dissolves the inflated sense of risk
- Holding it in is usually what creates suffering, not the act of asking
Asking intentionally: avoiding the two failure modes
- People-pleaser mode: hoping others read your mind; never asking at all
- Control-freak mode: ordering rather than requesting; demanding compliance
- Neither works — both avoid genuine dialogue and undermine relationships
- Asking effectively means: clear about the ask, humble about the outcome
- "I really disagree with this decision. I know it's not my call and others see it differently — but it's important to me you know that. Would you be willing to reconsider?" is often enough
- Personal opinion, stated plainly, carries more weight than most people expect
- Data is a crutch when what's actually needed is a stated preference or gut call
- People care about your opinion because they're in a relationship with you
The disagree-and-commit gap
- Nice founders often articulate a concern but stop short of making the expectation explicit
- The missing step: "This is the call, and I need you to follow through on it"
- Part of respecting people is holding them to consequences for their choices
- Giving feedback without naming a desired outcome is just venting
Asking for what you want as a PM or IC
- Positional power is not required to influence outcomes
- State clearly what you want and why, then acknowledge the limits of your authority
- The combination of directness and humility is disarming and often persuasive
- Not having data is not a valid reason to stay silent — gut opinions from subject matter experts are real information
The hell-yes standard
- Anything short of a whole-body yes is a no
- Lukewarm agreement leads to missed deadlines, low commitment, and later resentment
- When you hear a weak yes, ask: "What would it take to get to a hell yes?"
- This respects the other person's right to decline while moving toward genuine alignment
- Settling for half-hearted consent is a form of wishful thinking
Step three: accepting the response
- The hardest step for most people is not asking — it's hearing the answer
- Over-accepting a no: treating one rejection as permanent, universal, final
- Under-accepting a no: dismissing it because of power or certainty ("they have to do what I say")
- A no is data — it tells you what to try next, not that the game is over
- A no from this person, in this way, at this time says nothing about the next ask
- Accepting a no visibly often increases your influence: when people see their no is taken seriously, they sometimes reconsider voluntarily
- 99% of the difficulty in this step is emotional regulation — not logic
Kenneth's firing story: all three steps failing at once
- Joined Slack as first PM in 2014; confident, didn't ask for expectations or alignment
- Fired after 6 weeks; re-hired after apologizing
- Second phase: people-pleaser mode, never voiced what he wanted across a full year of 1-on-1s with the CEO
- Briefly articulated his want when product management was dissolved — wrote a proposal, got his role back
- Third phase: fear-driven, unable to hear critical feedback, externalized blame onto the CEO
- Final firing: HR involved, permanent
- The pattern across all three phases: no articulation, no asking, no listening to the nos
- Insight in retrospect: he wasn't a victim and the CEO wasn't a villain — it was just ineffective asking
On fear as motivation
- Many high achievers believe fear of inadequacy is what drives their performance
- Fear works in the short term; it is not a sustainable engine for years of hard work
- Discipline follows the same pattern — it gets you to the gym for a week, not a year
- The alternative: motivation rooted in vision and genuine desire
- Reframe: fear is for tigers; there is no tiger in the room
- When fear arises, name it, note there's no actual threat, then redirect to what you want
Being the first PM at a startup
- The core relationship is with the CEO or founders — everything flows from there
- Founders are often terrified; their seemingly difficult behavior usually makes sense through that lens
- Come in without assumptions about how you'll operate; your range and fit emerge from the people and context
- Have an explicit relationship design conversation early: what does success look like, how do we work together
- Don't assume the job description captures what they actually need from a human being
On the ask-for-what-you-want framework
- The three steps are simple to state: articulate, ask, accept
- What's hard is resistance — the internal narratives that block each step
- Asking isn't about guaranteeing an outcome; it's about staying in integrity regardless of outcome
- The goal is not to have everything work out — it's to avoid living in fear and regret
- Try pursuing an inspiring vision instead of running from fear; notice the difference
More like this — when you're ready for early access.
Join the waitlist for a personal account and content recommendations based on what you're working on.
No spam. Unsubscribe at any time.
You're on the list. We'll be in touch before launch.