Skip to main content

The 10X Rule: The Only Difference Between Success and Failure by Grant Cardone - (Notes)


Claims to teach:

  1. How to define correct goals and estimate efforts.
  2. Why most people never achieve success.
Chapter 1:
  Says did 10x more effort compare to others in everything (sales presentation, phone calls, property searches)

  2 Rules of 10x
  1.   10X more thought/thinking
  2.   Set 10 times high target and work 10 times harder to achieve it.

  4 Mistakes people make when setting goals:
  • Mistargeting by setting objectives too low
  • Severely underestimating what it takes in terms of actions, resources, money, and energy to accomplish the target.
  • Spending too much time competing and not enough time dominating their sector.
  • Underestimating challenges to attain target.

Chapter 2:
  What reactions manager have when not hitting their targets - Reduce the targets.
  When you start excuses for not hitting your target what that should indicate to you? - Getting off the track.
  The 10x Rule assumes the target is never ___. Any target attacked with the right __ in the right __ with persistence is ___?

Chapter 3: Success
  
Chapter 6: Assume control of everything
 Successful people accept very high levels of accountability for creating and having success for themselves. They hate blame game, better to make it happen - good or bad.

Chapter 7: Massive action - creates new problems. 
Chapter 8: Average is failing formula.
Chapter 9: 10X Goals
Chapter 10: Competition is for sissies
  Competition limits ability to think creatively
  Dominate your sector
  Stay ahead of the pack.
  Study others and take it to the next level.
  Do something others can't do - because of their size, commitment to other projects and then exploit it.
Competition is healthy then domination is immunity

Chapter 14: Expand - Never contract
Some ways you can expand that only requires energy and creativity and not money 
When have you ever benefitted from contraction

Chapter 17: Customer Satisfaction

Increasing customer is the right target, not customer satisfaction.
If your service doesn't satisfy customers then you're a criminal - Always over deliver.
First, dominate space and get all the attention before other things.
Customer first, customer satisfaction next.

Clients how didn't buy your product survey
Did 

Have you ever been surveyed by a company that you didn't buy from?
What is more important than customer satisfaction?
Why do most business fail?
What might be some survey questions you could see when you don't acquire a customer?







 
  

Comments

Post a Comment

Popular posts from this blog

Access multiple Databases in JPA

According to JPA specification we can define multiple "persistence-unit" elements (i.e. like below) in persistence.xml file and can easily refer them inside Dao layers as this. public class PolarDaoImpl {     @PersistenceContext(unitName="PolarPU")     protected EntityManager entityManager; -- } public class BearDaoImpl {     @PersistenceContext(unitName="BearPU")     protected EntityManager entityManager; -- } Checkout sample persistence.xml <?xml version="1.0" encoding="UTF-8"?> <persistence version="2.0" xmlns="http://java.sun.com/xml/ns/persistence" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://java.sun.com/xml/ns/persistence http://java.sun.com/xml/ns/persistence/persistence_2_0.xsd">     <!-- Database 1 -->     <persistence-unit name="PolarPU" transaction-type="RESOURCE_LOCAL">         <
3 comments
Read more

JPA 2 new feature @ElementCollection explained

@ElementCollection is new annotation introduced in JPA 2.0, This will help us get rid of One-Many and Many-One shitty syntax. Example 1: Stores list of Strings in an Entity @Entity public class Users implements Serializable {     private static final long serialVersionUID = 1L;     @Id     @GeneratedValue(strategy = GenerationType.AUTO)     private Long id;     @ElementCollection     private List<String> certifications = new ArrayList <String> ();     public Long getId() {         return id;     }     public void setId(Long id) {         this.id = id;     }     public List <String> getCertifications() {         return certifications;     }     public void setCertifications(List <String> certifications) {         this.certifications = certifications;     } .. }         Users u = new Users();         u.getCertifications().add("Sun Certified Java Programmer");         em.persist(u); Generated Tables    Users    Co
21 comments
Read more

Reuse JPA Entities as DTO

Note : Major design advantages of JPA Entities are they can detached and used across tiers and networks and later can by merged. Checkout this new way of querying entities in JPA 2.0 String ql = " SELECT new prepclass2.Employee (e.firstname, e.lastname) FROM Employee e "; List<Employee> dtos = em.createQuery(ql).getResultList(); The above query loads all Employee entities but with subset of data i.e. firstname, lastname. Employee entity looks like this. @Entity @Table(name="emp") public class Employee implements Serializable {     private static final long serialVersionUID = 1L;     @Id     @GeneratedValue(strategy = GenerationType.AUTO)     private Long id;     @Column     private String firstname;     @Column     private String lastname;     @Column     private String username;     @Column     private String street;     @Column     private String city;     @Column     private String state;     @Column     private String zipc
11 comments
Read more