I have just joined with a company. As I am a fresh passout from graduate college, I had a habit of writing every important point that I hear.

As I am in IT industry, every single point that we hear about technology is useful for long run to us. We usually have presentation and some training sessions also, where our seniors provide us with some presentation over what we are going to work upon. During that session, I think I am the only one who keeps on writing the whole matter, that is being presented.

The fellow colleagues advised me, not to write everything as it shows up a bad habit.

I dont think it as much embarrassing, as I had a habit of remembering details by writing briefly about them.

I would appreciate to have suggestions on whether or not to write everything that I hear at office.

  • 2
    Fine answers have already been given here, but perhaps it would also be helpful to read some Q&A that have come up on other SE sites. Although these are different situations (specific to meetings), they're similar in that people have questioned whether they should or should not, and how, to take notes throughout their workday: "How to Take Minutes of Meeting Effectively" and "Not okay to take notes at meetings?"
    – jcmeloni
    Commented Oct 20, 2012 at 14:35
  • 1
    Well...if the person talking has to wait for you to write down you notes then that would become really annoying. But I guess less annoying that assigning work to a junior developer and they do something completely different than asked because they didn't write it down. Is your note taking affecting the flow of the conversation, if so then learn to take notes without affecting the flow.
    – Dunk
    Commented Oct 22, 2012 at 15:41
  • I read jcmeloni's links and I definately agree that it is really annoying and distracting to listen to someone typing in the notes while the meeting is going on. So once again, notes are fine, unless you are being annoying about it.
    – Dunk
    Commented Oct 22, 2012 at 15:44
  • I have decided to just note down the highlighting points and summarize it later on. Thus it will prevent me from distracting anyone. Commented Oct 23, 2012 at 5:10
  • 2
    When I'm in a meeting I want us to make eye contact, because then I am sure you understand what I'm talking about. If you don't remember things, you can ask me to send you follow-up documentation. I want meetings to be an engaging back-and-forth, rather than at school were lectures are one-way transfers of information. If all I see when I look at you is you robotically jotting down everything then I might as well just save time and send you links to documentation.
    – MrFox
    Commented Oct 23, 2012 at 17:21

7 Answers 7


If you write down every single point, it can create the impression that you do not understand the subject under discussion enough to identify the key points. It can also simply be irritating or perturbing, as colleagues wonder what you are writing.

If your work is of good quality, it shouldn't matter. Even so, it can take a long time to correct any first impressions made on your colleagues.

Can you still remember by just writing down single keywords and then reading through them afterwards and reflecting on you just heard? If so, it might be something to try.

  • 1
    +1, its really a valuable suggestion, though i just write the key points and write the details on it later by having some research on it. Commented Oct 20, 2012 at 12:03
  • 3
    An interesting idea, but as a fresh graduate he probably doesn't understand the subject under discussion. However if he keeps writing things down he probably will pretty soon. Maybe more so than the people who object. Commented Oct 20, 2012 at 15:47
  • 1
    @DJClayworth Not only is it an interesting idea, if you read the comment above yours, it seems to be what he actually does.
    – itsbruce
    Commented Oct 20, 2012 at 19:06
  • @SahilMahajanMj - But do keep some notes atleast. You'll thank yourself when you'll have the necessary information for work and when the others will be asking you for info or knowledge transfer. Commented Jul 31, 2014 at 5:04

If writing down things is something that helps you remember important details, you should keep doing so. Having a written record is valuable later on if you do forget things and need to review.

I don't know why your colleagues are saying this is unprofessional, one possibility being that it makes them look bad (as they are not writing things down and it may seem, in comparison to yourself, that they are not paying attention), so they don't want you to continue.

In short - keep doing what you are doing. If it helps you and hurts no one, I don't see the harm in it.

  • 8
    As a senior person, I am far more worried about the new graduates who don't take notes.
    – HLGEM
    Commented Oct 22, 2012 at 15:22
  • @HLGEM look at their output first. If they don't take notes, maybe they have good memories. If their results are poor, maybe then the lack of note-taking is significant.
    – itsbruce
    Commented Oct 23, 2012 at 9:13
  • @itsbruce - HLGEM did not say this is the one and only yard stick, only that it can be a warning sign.
    – Oded
    Commented Oct 23, 2012 at 9:21
  • Then consider my comment and yours clarifications for those who might take his comment too literally ;) All for the greater good of the greatest answer etc.
    – itsbruce
    Commented Oct 23, 2012 at 9:31
  • I have to disagree, bruce. As the new developer begins to take on more difficult projects, it gets tougher and tougher to remember all the details. If they aren't in the habit of writing things down early, they won't do it when it's too late. And worse than more difficult projects is more simultaneous projects. You don't give a fresh college grad five simultaneous projects. But once you've been in the industry a few years, you're expected to juggle them. If you're not writing things down, you're forgetting them.
    – corsiKa
    Commented Jun 14, 2014 at 3:14

I also have the habit of writing many things down, at least much more than my fellow colleagues. In particular when I started at the job I am right now, I wrote a lot of information down. And guess what, from time to time I needed to look back at it. As a technical person involved in many systems this was in fact the only way to get around for me.

Now I am already there since some time, I need to write down less. For two simple reasons:

  • the most important stuff is already written down; the most frequently used stuff usually organized in (shared) Corporate Google Docs or Wiki (or I just have it in may head)
  • it is now more easy for me to see what I probably need in the future and what not

However, one reason why it is good to limit the stuff you write down: eventhough already the writing helps memorizing, you lose some of your attention to writing. Sometimes you can be more productive by concentrating on listening and writing only the most important points when you have more time.

And yes, from time to time people will address your writing habit. Having frequently external Sales persons at our office, one of them once told me he did the same when he was a programmer. ;)


Do you write down everything that is important or just everything? Many graduate programs expose you to a lot of information which you're required to synthesis into something meaningful. And like a job, no one is going to spoon feed you what is on the test like undergraduate work. My guess is you know what is important, but may be a little anxious with your new job and are writing things down just in case.

Make sure you let others know you are paying attention. If you're constantly making people slow down so you can keep up, you may be writing too much information.

Review you notes and work on condensing them. If you have to trim it down too much, it could be another indicator of writing too much.


Many people write to learn, don't be ashamed of that. If you find it helpful, keep it up, but realize that:

  • It's worth asking about documentation. Trying to write down, for example, every step in a technical process may be less useful than listening to the talk about the process, when you know the actual steps are written down in a how-to document. In that case, knowing where to find the documentation is many times more useful than having a written record.

  • Certainly you'll learn as you go and after a while you won't need all the detailed notes since you'll know the basic information. If many of your coworkers are deeply familiar with the system they work in, they may have forgotten what it's like to be new.

  • Be aware that some discussions are not set in stone. A conversation about how to design or approach a given problem may mean that nothing is all that certain - not every opportunity is a training session, and it may be less useful to take notes and more useful to simply listen, ask questions and offer thoughts when the final out come is uncertain.

One particular note is that sometimes eye contact is more important than perfect recall. Particularly in cases (in a Western office... anyway) where a boss or customer is giving instructions to a subordinate, it can be as important to show that you are actively engaged in listening by looking at the speaker. To slow down the conversation and clear up any confusion, reframe their statements, ask for clarification and take notes only when you know you have an action to take or a particularly crucial shared understanding to jot down. At times where you are trying to please a superior, very intense note taking can be perceived as a listener who is not actively engaged in the conversation. A good rule of thumb on this is to watch the body language of any speaker with more power than you have - if they seem jumpy or tense, they may feel they are not being listened to, and you may want to give more eye contact at the risk of less note-taking.

Probably the biggest transition from school to work is to realize that in many situations, you are expected to question, consider, and provide comment to the technical information being discussed. When you are very new, it is likely that your questions will outweigh your comments, but people at your work are likely to expect that to change over time. The mindset of wrote learning and relay that works well in many school settings may work poorly in an office that expects a lot of conversation and commentary... but don't worry too much over it, as you learn, you'll be able to provide mroe thoughts and less questions!


I don't know if it's a bad habit, but you may want to write down stuff that pertains to you, or what you could do is what I do, which is bring in an audio recording device (iTouch in my case) and record the conversation, then go back and take notes to what you deem is important at your own convince later that day, or week if need be.

What I do though is if someone has schematics or concepts that are written down on the whiteboard, I record those so that the audio makes more sense later on.


No, it is a GREAT habit that I wish I did more of. Of course, within the limits of relevance. And a great tool for organizing your notes is Evernote, unless your company, like mine, blocks access to it (I understand why they block FB and such but Evernote is a slam dunk organizational enhancement for everyone).

  • At first, the question here is about taking notes during the meeting not about how to take and preserve notes. By the way, thanx for suggesting Evernote. I have looked upon it and its a good site to preserve notes. Commented Oct 23, 2012 at 5:14
  • 1
    I think taking notes anywhere, if you can get in the habit of doing it and doing it well, is a good practice. Evernote is an incredibly helpful tool to me. I am not too good at taking live notes (never been, including school) but I do record various info items and categorize them in Evernote and it helps me oragize my life and not forget things I learned. I <3 E.N.
    – amphibient
    Commented Oct 23, 2012 at 14:01

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .