Skip to content

Instantly share code, notes, and snippets.

@gmcerveny
Last active December 22, 2015 07:28
Show Gist options
  • Star 0 You must be signed in to star a gist
  • Fork 0 You must be signed in to fork a gist
  • Save gmcerveny/6437897 to your computer and use it in GitHub Desktop.
Save gmcerveny/6437897 to your computer and use it in GitHub Desktop.

How to Win at Mentoring

Mentors are Volunteers

  • Mentors give up their time to help you with your business.
  • They are busy individuals, many with businesses of their own to run.
  • Use their time wisely and with respect.

Come Prepared

  • Research mentors and understand their backgrounds.
  • Come prepared with asks, knowing what you want to get out to of your meetings.
  • Each mentor has a different background, understand the unique value they can provide.
  • Know where you are in your business, and what you need to move forward.

Your Goals

  • Get the mentor to do most of the talking. You are there for advice. If you are spending most of the time talking and selling your company, you are doing it wrong.

    • How to do this? Have a well crafted elevator speech, one that succinctly explains your business and starts the conversation. Do your research before hand and know what mentors skills you want to leverage (see above.)
  • Start a relationship

    • A long term relationship can benefit both parties.
    • Ask for permission to follow up via e-mail.
    • Choose wisely as neither mentor nor team have time to engage everyone.

Things Not to Do

  • Come in unprepared: "I just wanted to tell you about my business and see what you say."
  • Send unsolicited emails outside the catalyst.
  • Ask to follow up and then don't.
  • If a mentor is willing to spend more time with you, do not dump every question on them.

No One Has All the Answers

  • Mentors have a lot of experience, but you should never follow advice blindly.
  • If you receive advice, and disagree, it is your business.
  • It you choose not to follow advice, share why you chose a different path.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment