What FAANG executives read this week: Ethan Evans on the selection problem behind overwork (2026)

One fully date-verified recommendation anchors the August 2–9 scan: former Amazon VP Ethan Evans points readers to his new article, How to Actually Work Smarter. Its argument is less about squeezing more out of a day than refusing work that does not serve the outcome.

The public record is thin this week, so this issue carries one strong signal rather than padding the list with recommendations whose dates or executive provenance cannot be verified. The window is August 2–9, 2026, in the channel’s display timezone. This is a scan of public posts and public-facing pages, not a record of what any executive reads privately.

At a glance

Signal	Recommender	Item	Type	What it helps you examine
Strong direct share	Ethan Evans, former Amazon VP	How to Actually Work Smarter, by Ethan Evans and Jason P. Yoong 1	Article	Whether your workload problem is really a prioritization problem

The recommendation: choose the work before you optimize it

On August 6, Evans posted a direct invitation to read his latest newsletter: “If you want to learn to prioritize, to say ‘no’, and to have a more successful career because of it, read my latest newsletter.” He describes the piece as a guide to starting work smarter and iterating toward more impact. 2

Evans’s public X bio identifies him as a former Amazon VP who led global teams and now trains leaders to become executives. That makes this a career-practice recommendation from a former operator, not an outside book review. 2

Loading content card…

The article, written by Evans and Jason P. Yoong and published on August 6, is aimed at overworked individual contributors and managers. Its central claim is blunt: many people who feel overloaded have a selection problem, not an effort problem. The fix starts with accepting that you cannot do everything, then choosing which work deserves the risk of saying no to something else. 1

The practical questions are:

What outcome are we trying to create?
What decision will this work help us make?
Is the requested deliverable the goal, or merely one way to reach it?

That last question is the useful one for managers. A request often arrives disguised as a document, dashboard, meeting, or feature. Evans’s test asks you to recover the business problem underneath it before spending the team’s time on the requested form.

Why this is useful at manager level

The article is not a time-management trick. It is a filter for competing commitments.

A manager can apply it before accepting a new request:

Name the outcome in one sentence.
Name the decision the work should improve.
Separate the required result from the requested artifact.
Say what will move later, get smaller, or stop.

The fourth step is where “work smarter” becomes real. If nothing moves, the team has not prioritized; it has merely added another priority.

This framing also puts a limit on the advice. Evans’s article can help a reader inspect selection, scope, and trade-offs. It cannot decide which stakeholder risk is acceptable in a particular organization. That depends on the reader’s role, commitments, and room to push back.

Should you read it?

Read it first if your week is full of legitimate requests, your team keeps polishing low-consequence work, or you are being praised for reliability while losing control of your calendar. The article is short, direct, and built around questions you can use in the next intake meeting.

Skip it if you are looking for a research survey or a book-length theory of productivity. This is a coaching piece, and its value is the prompt it gives you: before asking how to complete more work, decide which work should exist.

No second executive endorsement is counted for this item. It is a single-source recommendation, but a clear one: Evans is telling readers that advancement does not come from accepting every task. It comes from choosing work that changes the outcome.