Reflection — An Honest Take 8 min

Honest Take — Before You Begin

Honest Take — Module 5: Coalitions, Sponsors, and Allies #

This is the module where the curriculum gets uncomfortably operational. The previous modules asked you to think differently about political dynamics; this one asks you to act differently in your professional relationships, and the action will be visible to the people you are acting toward. That visibility is the new texture of difficulty. You can read Pfeffer privately and update your worldview without anyone noticing; you cannot rebuild your sponsor inventory privately.

The Sponsor Inventory will be the most uncomfortable checkpoint of the curriculum so far, and I want to name why before you encounter it. The discomfort is not that the inventory is morally tainted; it is that the inventory will be small. For most engineers — and almost certainly for you, if you contract, work remotely across a cultural or organizational boundary, or have spent your career believing good work speaks for itself — the count of current active sponsors, people who advocate for you in rooms you are not in, is between zero and two. This is not a personal failure. It is a structural observation about configurations that systematically suppress sponsor-building: the contractor's manager has weaker advocacy capacity than an FTE's; the remote engineer's relationship-formation surface is thinner; cross-cultural distance adds friction at every step; the good-work-speaks-for-itself belief actively prevents the deliberate work. The implication is not despair; it is deliberate compensation. The engineers who do well in suppressed configurations are the ones who recognize the structural deficit and do the sponsor-building work the configuration would otherwise prevent. This module's exercises are that work, formalized.

A prediction about Grant's giver framework, and a warning about its wrong distillation. The giver frame will resonate strongly — possibly too strongly — if your professional identity is built around helping, teaching, unblocking, and shipping things as gifts to a community. Grant's data is that givers can be extraordinarily successful when they have protections against exploitation, and career-endingly unsuccessful when they don't. The protection chapter will land with mild resentment, because the protections (time-budgeting, five-minute favors instead of unlimited generosity, distinguishing reciprocators from extractors) will feel like a betrayal of the giving orientation. Deploy them anyway; the alternative is not generosity but unmaintained generosity, which depletes its source and disappears. And refuse the engineer-rationalist's wrong distillation, which is "I should be more strategic about who I help." That conclusion converts you into a matcher — the worst-performing orientation in Grant's data. The actual finding: the most successful givers are unselectively generous within explicit protective limits. Stay a giver; build the limits.

The most uncomfortable single move I will ask of you in this module is the legibility move: after the inventory is written, initiate one conversation in which you explicitly name the sponsor dynamic. The simple version is, "When X comes up, would you be willing to advocate for me?" This conversation feels excruciating to most engineers, and it is, by Hogan's writing and Hewlett's research, the single highest-leverage relationship move available at your career stage — it converts an implicit relationship into an explicit one, which is the difference between hoping for advocacy and having it. Make the move at least once during this module. The first time is the worst.

Two widening observations before you start. First, if you have recently changed roles — a promotion, a new company, a shift from IC to lead — Ibarra's Working Identity will land harder than you expect, because your relationship infrastructure was built around the old identity and is not yet sufficient for the new one; reading her mid-transition is uncannily well-timed, and the inventory will show you exactly where the old structure no longer fits. Second, sponsorship is not confined to employment. If you maintain an open-source project, write publicly, or sell a product, the users and readers who mention you favorably in forums, bring your work up in hiring conversations, and recommend your tools to their team leads are doing advocacy in rooms you are not in — which is, by the operational definition, sponsorship. Some of your most consequential sponsors over the next decade may never share an employer with you. The thank-you notes, the testimonial asks, the occasional what's-coming-next updates — work you may currently underweight because it feels promotional — is, at the right cadence and tone, literal sponsor-cultivation.

Conclusion #

This is where the reading-to-action ratio inverts. Reading without acting produces a person who can name sponsorship dynamics but does not have any; acting without reading produces relationship-building that is undisciplined and often counterproductive. Do the inventory honestly even though it will be small. Make the legibility move at least once. Stay a giver and build the protections. The structural deficit of your configuration is real, and the deliberate work is the only known compensation.

Predictions #

  • Your current-active-sponsors section will contain zero to two people. Structurally normal; not a failure.
  • You will discover at least one relationship you had filed as "professional friendship" that was actually inactive sponsorship, and the realization will be slightly bittersweet.
  • The gaps section will identify at least one room where decisions about you get made with nobody present who would advocate for you. Seeing it written down is the module's sharpest moment.
  • You will resist the legibility-move conversation for at least a week before doing it. The resistance is normal. Do it anyway.
  • Grant's giver-protection material will produce mild resentment before it produces compliance. The resentment is data about how deep the can't-say-no pattern runs.
  • If you have any public surface — code, writing, products — you will realize mid-module that several strangers have been functioning as distributed sponsors, and that you have under-invested in those relationships relative to their political weight.
  • Within three months, you will sponsor someone else — explicitly, with a specific advocacy event — and it will feel performative the first time and native by the third. Sponsoring others is the marker that the module actually installed.
  • If you are mid-transition, Ibarra will land harder than any other reading in the module, and you will quote her to yourself for years.