korrents
Ian McAllister

Ian McAllister

@ian-mcallister · 7 positions · On ppll ↗

Product leader; senior director of product at Uber in 2022, earlier more than a decade at Amazon, where he created AmazonSmile; founder of the small-business AI service OkayWinston.

Ian McAllister did not write this page.

We collected these quotes from things they published elsewhere, and every quote links to where it was said. They have no account here and have not endorsed this site. Quotes are word for word; the short line under each one is our own restatement, not their wording. Their own site. Is this you? Claim it or ask us to remove it. Or tell us what is wrong here.

Filter All topics · Newest first
  1. I applaud the drive in my PMs who choose to escalate (appropriately) because escalation is forward progress. It’s far better to escalate and risk ruffling some feathers than letting a project stall out.

    ↗Leveraging Your Leader - The Polite Escalationianmcallister.substack.com 1st of 2 in this piece

  2. Don’t make your leader figure out what needs to happen. Tell them EXACTLY what you want them to do. That takes work off their plate.

    ↗Leveraging Your Leader - The Polite Escalationianmcallister.substack.com 2nd of 2 in this piece

  3. 13 months earlier
  4. In bad times or when you’re out of a job, you need to build a large upper funnel of target companies. A large upper funnel means 30 companies, not 3.

    ↗How to Go Get Your Next Job in Techianmcallister.substack.com

  5. 2 months earlier
  6. Co-authoring a doc is painful, and the Frankendocs that result are usually painful to read as well. Collaborate on the outline, perhaps, but either write it yourself or have your prospective co-author write it. Don't tag-team.

    ↗16 Tips for Writing Upwardsianmcallister.substack.com 1st of 3 in this piece

  7. Boil the entire doc down into a few bullets or a paragraph. Spill it. Your temptation will be to save the good stuff for the end of the doc to build suspense or get your excuses in ahead of time. Resist!

    ↗16 Tips for Writing Upwardsianmcallister.substack.com 2nd of 3 in this piece

  8. Just like it is quicker to fix a software bug during unit testing than in production, it is much more efficient to iterate on the outline of a document than to rework a fully written doc.

    ↗16 Tips for Writing Upwardsianmcallister.substack.com 3rd of 3 in this piece

  9. 5 months earlier
  10. You shouldn’t claim success launching a feature by a certain date. Set a metric-based goal on the impact the feature is supposed to achieve. Metric-based goals are durable and give you the flexibility to meet a goal in different ways including launching a different feature or simply fixing something that is broken.

    ↗The Goal Postianmcallister.substack.com