A note from Daniel

You need to start thinking in terms of outcomes rather than outputs. That means rather than defining your success by the code that you ship (your output), you define success as the value that code creates for your customers and for your business (the outcomes).

Daniel Continuous Discovery Habits, page 20 · July 22, 2023 Save to shelf
Notes like this take four seconds in Booksense. Scan the paragraph, it lands on the right page, and comes back for review later. Take your first note

More from readers of Continuous Discovery Habits

Daniel p. 58

To shift your outcome from less of an output to more of an outcome, question the impact it will have. In addition to your primary outcome, a team needs to monitor health metrics to ensure they aren't causing detrimental effects elsewhere. For example, customer-acquisition goals are often paired with customer-satisfaction metrics to ensure that we aren't acquiring unhappy customers. To be clear, this doesn't mean one team is focused on both acquisition and satisfaction at the same time. It means their goal is to increase acquisition without negatively impacting satisfaction.
Daniel

More from Daniel

See their profile
Ultra Successful p. 60

The False Constraints That Limit Your Potential: - How Quickly You Can Scale Whether it's your business or your career, there are unspoken timelines that people accept as gospel.They are all untrue: "You can only really grow at 10% a year." "You need to pay your dues for a decade before getting promoted." These artificial limits keep people moving at a crawl when they could be sprinting or pushing for more. The most successful people I know refuse to accept conventional wisdom about timelines, and oddly enough, they break them all the time.
Daniel

Stop losing the best parts of what you read.

Booksense pushes your highlights back to you for review, so a note from page 174 is still yours a year later. Free on iOS.

Get Booksense free
Daniel on Booksense 5,999 notes 387 hours of reading