Paths · 11 reading journeys
Read with a purpose.
One question, a deliberate reading order, and something to put into practice. Choose by the time you have; longer paths can be read across sessions.
Find a reading path ↓
One question. A few good reads.
4 pieces · About 41 min
Build growth that lasts
Are you building a growth loop—or just replacing users who leave?
Founders and product teams with acquisition activity but an uncertain growth mechanism.
Take away: A growth-loop sketch, a retention check and an owned experiment aimed at a specific friction.
Open reading path →4 pieces · About 28 min
Make the decision you keep avoiding
Is the decision unclear, unowned, or simply uncomfortable?
Product managers, founders and team leads with a consequential decision stuck in another round of discussion.
Take away: A decision note that separates the question, the owner, the reason for waiting and the reasoning to review after the result.
Open reading path →3 pieces · About 22 min
Disagree without breaking trust
Can your team challenge an idea without turning on the person?
Managers and team leads facing disagreement that has become personal or unproductive.
Take away: A question, a boundary and a clearer role for the next difficult conversation.
Open reading path →3 pieces · About 26 min
Think beyond the first-order effect
If your prediction comes true, what changes next?
Founders, product managers and curious readers examining the consequences of a long-term bet.
Take away: A consequence map and a reversible experiment for one assumption you cannot yet resolve.
Open reading path →3 pieces · About 34 min
Choose what to build
Is your roadmap solving the right problem?
Product managers and founders facing a roadmap debate where a ranked backlog has not produced agreement. This is a diagnostic reading route, not a scoring-template collection.
Take away: A roadmap choice with a customer rationale, strategic fit and an explicit change in commitment.
Open reading path →4 pieces · About 29 min
Lead without becoming the bottleneck
Where does your attention actually help the team?
New engineering managers, team leads and founders who keep taking work back because explaining it seems slower than doing it. The examples lean toward software teams.
Take away: A handoff with clear authority, useful support and a signal for adjusting your involvement.
Open reading path →3 pieces · About 23 min
Stress-test your strategy
What would make you change a strategy you believe in?
Product managers, founders and engineering leaders with a strategic bet to defend—or reconsider.
Take away: A testable assumption, a disconfirming check and a review point.
Open reading path →3 pieces · About 36 min
Discover the problem before the feature
Are you learning what customers need—or collecting requests?
Product teams whose backlog grows faster than their understanding of customers.
Take away: A customer question and a small opportunity to investigate before choosing a solution.
Open reading path →3 pieces · About 33 min
Design boundaries that can evolve
Which early modeling choice will become expensive to change?
Technical product managers, founders and engineers who can follow a data model and an API example.
Take away: A boundary sketch with one coupling risk and one promise to downstream users.
Open reading path →2 pieces · About 17 min
Make feedback useful
Will this feedback change the work—or just express your frustration?
Managers and technical leads improving feedback conversations and reviews of unfinished work.
Take away: A specific request for change and a review format that invites useful input.
Open reading path →3 pieces · About 21 min
Turn reading into understanding
Can you explain the idea when the article is closed?
Knowledge workers building a learning habit; the later examples focus on software development.
Take away: A gap you can name, a practice task and a plan to revisit it.
Open reading path →