Notes from 8/6–15/6

Not much this week, wasn’t much interesting

[ Ray Dalio ] Why and How Capitalism Needs to Be Reformed

Interesting set of notes here, capitalism needs to have the base of an eduaction populace with sufficient opportunity

Blockchain

Someone just made a $2.6 million mistake on Ethereum

Some mistakes are just hilarious

Career

The Open Feedback Circle (OFC)

Tim Ferris / Josh Waitzikin Interview: Josh Waitzikin talks about his latest pursuit of mastering foiling through repetition.

Principles: Every challenge is an opportunity to learn.

Radical Candor: Criticize the action or the work, not the person.

Nonviolent Communication: Covers a framework that helps with difficult conversations. I have used this framework at work and at home.

Development

Hone your JavaScript skills by building these 15 projects

8H video, if there’s a spare weekend this will be handy.

Product

Decision making for product managers

In this article, we will cover the following:

• How to judge different types of decision and decide what is important
• How to be confident with incomplete information
• How to use probabilistic thinking in decision making
• How groups increase your chances of making successful decisions

Failing properly has two major components:

1. First, never take a risk that will ‘do you in’ completely (never get fully taken out of the game)
2. Second, develop the personal resilience to learn from your failures and start again

Forget NPS, meet CES

CustomerEffortScore

Top Heuristics to follow for a good CES

1. Visibility of system status: The system should keep customers informed of what is going on with the system, where they are within a process, and what actions are available, and provide feedback on status appropriate to interactions.
2. Match between system and the real world: The system should use language, wording, & concepts familiar to the customer, rather than system-oriented language. Information should follow real-world conventions and appear in a natural and logical order.
3. User control and freedom (undo, redo, exit): Customers should be able to back out of unwanted or mistaken interactions through a marked “emergency exit”, without requiring unnecessary steps. The system should support undo and redo.
4. Consistency and standards: Text, situations, and actions should be consistent throughout a system and should follow system conventions. Customers should not have to wonder whether different words or actions mean the same thing.
5. Error prevention: Careful design should prevent problems from occurring. Eliminate error-prone conditions, or be aware of them and present customers with confirmation options before committing to an action.