Skip to main content

Listen - How to Learn to Learn

Good listening skills, in particular Active Listening is essential to learning- and success.

Listening- you think you know it- most of us think we're good listeners. It's very hard to know and acknowledge that you are not good at listening. You may never become a good listener because so many personal emotions and prejudices get in the way of listening.

A good listener tries to understand thoroughly what the other person is saying. In the end he may disagree sharply, but before he disagrees, he wants to know exactly what it is...
- Kenneth A. Wells, American

Active listening is about focusing on the person who is speaking. An active listener needs to focus full attention on the person who is speaking.

Here are a few good links to learn more about listening:

What is listening?
  • Poor Listening Habits, Poor Listeners, and Good Listeners.
Active Listening

You'll find here the four characteristics of empathetic listeners.

Attributes of Good Listening

Have you ever stopped to think that we require courses and training in our education in speaking and writing, but not in listening? Why not?

Active Listening: A Communication Tool
  • ask good questions,
  • listen non-judgmentally,
  • paraphrase, and
  • empathize with the speaker.
Finally, would you have believed someone who came up to you and said he was a member of the International Listening Association?

Comments

Popular posts from this blog

Splitting User Stories vs. Rally's "split" feature (that has nothing to do with it!)

Agile tool Rally has a "split" feature it recommends to handle "unfinished work" in a Scrum Sprint: Manage Unfinished Work - Split user stories ( new link ) Below are my observations on the "Split" feature in Rally (followed by a few excellent articles on Splitting User Stories):   This "split" feature in Rally has numerous problems: 1. Nothing to do with Splitting User Stories It has nothing to do with "Splitting a User Story" which is an advanced but fairly well-understood field in Agile, and a tool for Product Managers to use in one of the two scenarios: The Product Manager does it before an Iteration commences (i.e. during backlog creation or release planning) to create User Stories by business value that are right-sized, i.e. they can be comfortably implemented inside an iteration; The Product Manager does it in Iteration Planning or in the middle of an Iteration to reduce scope by removing/simplifying accept

Entrepreneur Committee - Advisory Board of SVASE

For whatever it is worth, I would like to announce to my millions of would-be readers that I have been invited to join the Entrepreneur Committee on the Board of Advisors to the Silicon Valley Association of Startup Entrepreneurs . And I have accepted. If you're a hi-tech entrepreneur, I would love to hear your suggestions on what I can do in my "official" capacity to make SVASE a better organization for startups.

Agile Entrepreneurs Manifesto

The  Agile Manifesto  defines the 4 core Values that define "Agile":  " Individuals and interactions",  " Working software",  " Customer collaboration", and  " Responding to change" As I applied Agile requirements (user stories), engineering (XP), and process & project management (Scrum & Kanban) to my startups  (RideStation, and Agile Entrepreneurs)  starting from 2005 to now in 2018, I learned numerous lessons and shared them with my fellow entrepreneurs for the next dozen years. These lessons I have incorporated by "extending" the Agile Manifesto with two additional values pertaining to  Product (5th) and Startup/Business (6th)  -  that the services consultants who wrote it in 2001 probably didn't have to contend with as most (all?) of them were not founders of product startups:  "User Validation, Customer Traction, and Business Milestones" Agile Entrepreneurs Manifesto Us