Physician turned product manager writing about all things medicine, business and technology.
Today, we consume more information per person than at any other time in human history. We are continually reading, observing, monitoring, conversing and mentally trying to build a knowledge of the world we can use in our daily work and lives. The problem? The disparity between the total quantity of human knowledge and our ability to assimilate and filter it grows, unremittingly, by the day.
Imagine being able to recall any interesting thing you have read, seen or done. How amazing would that be? Any problem, any piece of creative work or project, boosted by a library of your historical insights, accessible any time. That’s a transformative way of solving problems.
One of the stepping stones to building such a solution is note-taking. However, it’s likely the way you currently take notes is wrong. It’s probably not changed since your school days. In the knowledge workplace, nobody can tell us what’s essential and when or how the information will be needed. Unlike school, the “tests” in our working lives can come at any time.
The failing of taking good notes is invisible in the short term, but in my daily role as a product manager I now regularly find myself referring to notes for everything from feature development, meeting preparation, providing colleague feedback and user research.
Knowledge is hard to come by, and as humans, it’s better to use our energies to focus on solving problems rather than recalling all the information. The following is a guide to understanding what a note is and how to you can use them in a system to help boost your thought process and productivity.
“A good Note says what is wrong, what is missing, what isn’t clear, what makes no sense. A good Note is offered at a timely moment, not too late to fix the problem. A good Note doesn’t make demands; it doesn’t even have to include a proposed fix.” — Ed Catmull, Creativity, Inc.
It’s not so much that there is a “right” way to create a note.
What’s more important is making sure a note does the job you need it to. This is somewhat challenging, because you are trying to predict what your future self is going to find useful.
And that’s the point — that effort is how you start thinking differently about information.
There are some good practices for note-taking like Zettelkasten, which would be worth reading if you are not used to note-taking. What is working for me is a system of small or “atomic” notes which focus on a single idea or article/book. Within each note will be a list of highlights, annotations and a personally written summary or reflection. The more critical the note, the more time I will spend summarising, reflecting and adding value to its content.
As you read things in books, blogs, or come up with ideas, you want to be building a catalogue of your most treasured insights and literature quips, which in turn can be organised, searched and shared.
The idea being that over time you start seeing the relationships between ideas and combining them to create unique insights. The system should help facilitate you in creating these connections.
Underpinning each example below is the idea that my workload is gradually residing less and less in my mind. It now lives in my notes. Sometimes the more straightforward you want your daily work to be, the more sophisticated the underlying system must be.
If I had to name the biggest impact note-taking has had on me, its the time saved searching for stuff. The volume of new information we are exposed to any given day can be overwhelming, and there is no good way to tell what will be important later on.
“Good product managers know the market, the product, the product line and the competition extremely well and operate from a strong basis of knowledge and confidence” — Ben Horowitz
I used to rely on a frantic keyword search journey consisting of emails, slack, cloud drives and apple notes just to find that one name or URL. Now, whenever a nugget of potentially valuable information comes my way, be it a link to a prototype, a piece of colleague feedback or excerpt from a design document, it goes straight into my note database for easy recall later.
This different approach to storing information has a surprising knock-on effect. I’m no longer reading passively. In every sentence, I’m now scanning for the value and future benefit. It completely changes the way I consume information or process events.
Note-taking in meetings is probably one of the most thankless jobs at work. Nobody wants to do it, but everyone is thankful when those notes are available. If you are already taking notes on everything by default, what’s the harm in sharing them afterwards? Not only does this make you a savour in the eyes of your colleagues, but there is another strange indirect benefit of doing this — you define the narrative.
Why is this useful? Language massively influences the limitations of how we think, and by developing the language used to describe or summarise a problem, you are teaching your team how to think about and communicate ideas during collaboration.
At the time of writing, we have just passed the middle of the year, and that means a flood of colleagues asking for performance reviews. Giving this feedback can usually be tedious as you typically need to cite specific examples of things they did or did not do well. But this time it was a breeze.
One of the things I started doing is spending 5–10 minutes a day jotting down in a work diary any successes, grievances, issues, thoughts and events. Not only is this a good process for reflection, but also served as an index for events. I typed in my colleague’s name and watched the associated notes pop up. Having nothing appear was sometimes equally as telling.
In short, my time spent providing feedback was halved. I was able to give the managers of my colleagues the information they needed to ensure and sponsor their career progress.
The act of writing notes itself serves as an excellent tool for reflection. Writing is thinking, and you can’t think clearly until you can write clearly. That’s why it’s so hard.
The act of summarising a lengthy report or trying to solve a hard problem requires a process of consolidation, description and communication before you be impactful in your actions. Note-taking can be a great tool to help you with this.
When I start researching a new product feature or thinking through a strategy, having a system of standardised, searchable notes enables me to work faster by pulling together thoughts and perspectives from across my knowledge domain. It gives me the space to explore an idea further, from a zoomed-out perspective and hopefully develop some hard-earned wisdom.
As I mentioned before, there is no single “right” solution for note-taking. It’s likely the first system you build will need to gradually replaced once you get a feel for what’s useful. The following is how I run my note-taking system, and it starts with some principles:
I’m an avid reader, and I wanted a solution that would fit into my current workflows. Here is the tech-stack I’m using, so to speak:
Searching on Google is no longer enough to make sure you have access to the best ideas. You need something more reliable and personalised — a system designed around your needs and interests.
It may be useful to end this post with a recent example of the system in action.
What can a product manager learn from a medieval farmer? Recently, when musing about a product strategy, the answer turns out to be more than I realised. Medieval farmers, in case you didn’t know, actively chose not to plant crops they knew would produce more food. Seems strange. Surely more food, means more sellable produce and hence, more profits in return?
Back to my example. I was debating a risk/reward scenario. Should I put all my resources into developing one significant feature that would likely have major user impact, or, should I focus on developing multiple smaller features which collectively, may have a major impact? I can’t do both.
Back to the farmers. Why not just plant the best crops? It turns out these farmers were masters of risk management. By choosing instead to plant a variety of lower-yielding but hardier crops, they protected themselves from the unknowns of bad weather and disease. The average food yield would always be lower, but they always had enough to eat and sometimes a surplus. They hedged their bets and sacrificed short term gains for long term returns.
Perhaps there is a lesson in there for my product strategy. By making smaller, multiple feature bets I may increase the chances for long term success. More importantly, I have created an opportunity for reflection and an analogy that can now be shared with others. This is the promised value of a note-taking system.
In a similar way that teams of people are more likely to be successful than individuals, spotting the connections between ideas will help liberate you to do what humans do best — think creatively and create new wisdom.
“To understand is to perceive patterns.” — Isaiah Berlin
Level up your reading game by joining Hacker Noon now!