By
El Copeland
March 2, 2025
•
20 min read
Professional Development
Tutorials
This article is a companion to my article on how to get the most out of Conference and Industry events. While most of the concepts here will not require external explanation, some things will be linked to subsections in my article, “Ripe for the Picking: Maximize your Conference ROI” and you may benefit from skimming that piece for context or discussion.
This article is about the importance of good notetaking including a demonstration of one of the methods I personally use. I have a lightweight template in OneNote that I’ve scrubbed for your use and you can download that here. We will also use a fair amount of genAI through ChatGPT.
As with most things from Rising Tide, this document is not dictatorial. We feel everything evolves and the goal for this was to be an easy tool that can be implemented with little effort. If you have feedback or questions or just want to argue, feel free to find me on LinkedIn or the MSPGeek Discord community (@cinakur) and I’ll be glad to chat!
I was a poor student in school, ironically driven but unmotivated. I knew I wanted to make a difference in the world, and that was it. I didn’t even plan on getting an Engineering degree. My family was lower-middle class in a rural town in the southeast United States that sprung up around an Air Force Base 80 years ago. I was the first on both sides of the family to go straight from high school to college, so I had no context or support about what it would take to be a Doctor, Lawyer, or even Engineer. I thought maybe I’d just get some vague Liberal Arts degree and become a teacher or get married and be a mom. Nothing bad about being a teacher or a mother, I still could see myself being both one day: it’s just that I had no dreams of my own, no direction or understanding. I thank all that is good in this world that college counselor looked at my SAT scores and was surprised I wasn't already pursuing something explicitly science and math focused!
While I say I was a poor student, I did receive good grades in basic classes and hands-on labs as I am a generally curious person, so talking about theory, tangible experience, and writing about it carried me a long way. However, as classes advanced from practical to theoretical, I rarely operated well under pressure and had poor time management so I would often fail homework and mid-term exams. When my Master’s Thesis was due, an advisor of mine chided me, noting I should be much further along in my research and analysis and questioning if I’d even make the deadline to defend it that year. (His talking-to was the motivation I needed to complete, even if I was doing it out of spite.)
School was miserable, sitting at a desk for hours a day was miserable: there were a million other things I could be doing and were already thinking about as I am half listening to a tenured professor drone on about whatever heady topic the syllabus offered.
Did my notes in those classes carry me through? I think back to them and I can clearly see in my mind’s eye: a doodle I made of my water chemistry professor as a lobster from 17 years ago. So, I guess you can say, yes, they carried me, but probably not for the right reason.
So why am I, an admittedly poor student, writing a blog post about note-taking? How did I even get out of college with two degrees? And why a lobster!?
Well, here’s the thing: with each exam I took, and with each hands-on lab, I finally understood the concept. Something about the adrenaline and skills that I needed to perform helped the concepts solidify in my mind, and eventually I even had enough confidence to tutor others in those courses!
The key was, and is, action.
It’s easy to freeze after a conference. You’ve taken in so much information: new names, new faces, new products, new settings, new experiences. Hopefully, most are good, but maybe some are bad. How do you KNOW what action to take, how do you even remember?
In this article, we’re going to talk about one way to create meaningful plans of action through note-taking at conferences, using the template that I created as a guide. We’ll look at our notes according to the lifecycle of your conference attendance: choosing the event, attending, and after. For this article, I’m going to use the two examples, one of planning to attend CodeMash, Home - CodeMash., following their 2025 event, and the other with my actual notes from Right of Boom 2025.
Let’s start at the beginning.
Before getting into how I use the template, let’s go over what is in it and my thought process behind it.
Did you download it yet? You can get that OneNote file here: Conference Note Template. (Contact me if you want a different type of export!)
The key thing about building with action in mind is that I bookend my trip with intentional processing and preparation so I can enjoy the event with confidence, knowing I am being responsible with my time, skill, and relationships. There are three main parts to the thought process that governed my template:
I personally do this by bookending my trip with 1-hour on each side: the hour before I plan my goals, and the hour after I summarize and make an action plan. Considering a conference with travel is easily a 40-60 hour week (and longer for vendors!), 2-hours is a small investment on the success of my conference attendance from a content perspective.
If we’re looking for direction on action at the end of this, we need to know where to find certain things we talked about, and that is all this OneNote template is. So, let's take a look! If you'd like to follow along, I have screenshots that follow as well as a video I recorded, available here: A Conference Note Survival Guide.
I like to have a Conferences Notebook shared between the team, and for each conference I add a Section Group, with the given year as a Section. So I copy parts of my template to the given location as needed.
Within the template, you will find four main sections:
Let’s talk about each section and how they’re used.
The point of this page is to visualize what success looks like for this conference, personally and as a team. You’ll find there are a lot of questions on this first page. You don’t have to answer all of them, but asking them ahead of time will give you some clarity on the type of questions you could be asking to get the most out of this event.
Session Notes are broken up into two parts: Agenda and Session Notes.
Make an Agenda page for each team member attending so you can compare sessions, notes, and ask questions!
Session Notes are for the actual Session Notes. Even if you don't take notes or even attend the session, you can fill in things you hear other people mention about it down the road!
Yes, more questions for you to ask. These are helpful when you do some AI analysis at the end.
Networking should be lightweight! You're going to meet a ton of people, quickly. Keep it at a high level as much as possible.
Vendors should generally be separate from your Networking so can have a place for notes about their product that aren't related to them personally.
Now that we have the lay of the land for the template, let's set up our example of attending Codemash 2025 (CodeMash).
We create the new Section for this event and copy in the template pages.
Now, the work starts. For me, I like to give myself one-hour to work this through. It’s enough time to do research and not too much time that I feel like I’m getting in the weeds.
If you read the article this is a companion to, you know I think setting your intentions for a conference is the foremost important thing to accomplish once you decide you’re going.
So, tell me, why do you want to attend CodeMash?
Do you have clear reasons you want to attend? Take a look at the Agenda from a high level or ask around. Maybe it’s worth asking a generative AI to help frame this. Perhaps ask, “Why should I, as an MSP (or individual, or business, depending on the data you’ve fed your AI!), want to attend Codemash?”
It’ll likely give you a bunch of reason, and while these are all probably valid to some degree, limit it to 1-2 main reasons and let the rest be a bonus. Review the website for vendors and key speakers that are meaningful to you. Fill out this section on the Conference Overview page.
Now, it's time to review the conference agenda a little more thoroughly. Which sessions do you want to attend? Here is their 2025 Agenda for context: 2025 CodeMash Conference
Fill those in on the Agenda page. Each team-member attending can have their own Agenda page so you can see what courses everyone else is taking and divide and conquer the session topics, or take joint notes on the same document and fill in each others’ blanks.
And add the Description and key notes to a new page in that section. Read the questions in the Session Notes section and write out your OWN questions of what you'd like to learn in this session based on your understanding of the Summary.
Rinse and Repeat until you have a full schedule. Be sure to put breaks in there occasionally for client calls or for serendipitous hallway meetings!
Some of these sessions, I won’t be taking active notes in (like the soldering course) but may want to have somewhere to dump resources or other notes afterwards! There may be a few different days that I jump into lightning talks, so I group them all together, they don’t need separate pages!
The main things to remember here echo the blog post on conferences.
One more thing I pre-prep to help keep my focus: I travel with my work laptop but I do not take it to the sessions. Instead, I take a lightweight tablet. This allows me to focus on what I’m here for: networking and learning and not answering emails or surreptitiously working on projects.
Time to actually take notes. At this point, we'll transition from planning the CodeMash trip to looking at my actual experience at Right of Boom this past year. Depending on your situation, you may or may not have the time or space to take “good” notes. I generally find myself in one of two situations:
In general, focus on the main things and let noise drift to the side. Here is some advice I have for handling each of these situations, and examples of how I handled them while at Right of Boom this past February.
In general, any live note-taking completed by you should be about action, not mindless transcription. There are AI transcribers like Otter.ai or Plaud.ai for that. Your goal should be three-fold:
Keep your notes high-level; focus on engaging in the sessions and ask questions. Write just enough to help jog your memory or find the source information later. If you wrote out your own questions in the planning phase, those can help guide your notes as well, or give you questions to ask when they open up the mic.
Here is a snippet from my notes I took in Brent Adamson’s session on the Framemaking Sale.
As you see in my notes here, yes, take photos, but where do those go when you’re done? Do you review them? Really?
Put that information somewhere useful, friend. Here are few things you can do to help shape your notes:
Taking notes on conversations is a lot harder. Who did you talk to and what did you talk about? Where were you? What actionable things can you remember, jokes, or meaningful things about that situation?
The Networking and Vendor sections are a lot lighter because they should be. Hopefully, you are living in the moment and connecting with these thoughts and ideas you discussed over a meal and worrying less about getting notes from these experiences. The point of these notes are to remind yourself of the important stories or experiences you had with someone, to build camaraderie and sometimes wise insight that these strangers-turned-friends-and-colleagues shared with you.
For conversation notes, I would encourage you to take notes you can, by texting or sending yourself a brief message through Teams/Slack, or recording a voice memo. Sometimes, I also just message my business partner if it’s a particularly lovely exchange.
Also, make sure you connect with that person, by social media, email, or business card. As with the Session Notes, triage throughout the day, or at the very least at the end of the day/beginning of the next to make sure all of your notes end up in one place.
These are my notes from a recent conference, with enough redacted so you can see what I do, but enough showing so you can see I am not perfect or 100%. I didn't fill in some of the blanks as I've mentioned in later segments, I’m not building dossiers, I’m only writing out just enough information to jog my memory. Some of the experiences were highly memorable, so the names were enough.
In the end, the most important thing for your notes is that they are here for you to return to at any time during the conference. If you’ve done the pre-work of laying it out, you don’t have to expend energy to get back on track. You just find the next session or meal and pick it back up again.
It’s the last day of the conference. You are exhausted and it’s time to pack up and hit the road.
I’d argue that THIS is the most important time in this entire document, this liminal space between education and action that will determine if you actually learn anything from this event!
Before things get “Back to Normal,” it is vital that you take the time to review your notes, whether alone or as a team. Here’s how I do it:
Here is what I distilled the Business Track at Right of Boom into.
I fed genAI each session with a few questions, and then fed the outputs together into genAI for the "Big Ideas" and then I edited them down and removed 2-3 points and subpoints I felt were unneccesary.
There it is, you have your nice, neat notes reflecting what you learned at a Conference! Now...what...what do you do with them?
Debrief with your friends who also attended. What did they get out of the event that you missed? Be ruthless about which product you’re going to try from which vendor following this event and stick with it. Go ahead and write up a short “sorry not interested, do not contact" template email to send to vendors, or email rules to send them to another folder/trash. (You can always come back to them, give them a clear templated no and move on!)
I mean, my notes from Right of Boom literally led to two (maybe three) blog posts on getting the most out of conferences, a video, and probably a webinar reviewing content as well. There is a depth of knowledge that comes from diverse conversations on topics, don’t be scared to have opinions or speak your mind, you never know how that can help our entire industry in the long run! Make videos, blogposts, or LinkedIn Articles. Share the wealth with others who couldn’t make it. Who knows, it may be helpful to you, to help you sort out your ideas better.
My goal in sharing with you how I take conferences notes, is to encourage YOU to get the most out of your conference attendance. However you do that is up to you, but hopefully this framework helps you practically implement how you can best ideate, execute, and close out your event experiences with Action in mind. Remember:
If you take nothing else, I hope you consider that a conference isn’t just about showing up. Instead, it’s about capturing insights, making connections, and turning those ideas into action. Take notes that matter, review them before they fade into oblivion, and for the love of all things good, do something with them!
In By the [run]Book Episode 9, Connor and Robbie power through the rest of HaloPSA v2.2 — unpacking dozens of quality-of-life updates, automation improvements, and admin refinements that make daily operations smoother. From new calendar defaults and contract history tabs to long-requested rule enhancements and KB management upgrades, the pair keeps the banter light and the insights practical.
Perfect for MSPs, admins, and implementation teams who want to understand not just what’s new, but why it matters in real-world use.
Watch Now: By the [run]Book: Episode 9
For easier tracking, check out haloreleases.remmy.dev to filter and search HaloPSA updates by ID, version, and keyword.
This new Other Uses tab shows every place an email template is used — from rules to mailboxes to notifications.
A new system action logs each time qualification matching runs on a ticket.
CAB selection in approval processes can now reference a custom field.
Portal users can start a ticket and save progress as a draft.
A new trigger fires whenever a quote is revised.
Runbooks can authenticate via Halo API Bearer Token.
Simplifies calendar management for agents.
Administrators can update review dates for multiple KBs at once.
Add KB fields to approval forms for better context when reviewing changes.
Improves data visibility for developers working with email template records.
Sales emails can be attached as CRM notes to keep records complete.
Introduces SKU validation during stock receipt.
New tabs track every edit made to contracts.
Calls no longer end automatically when linked or logged to a ticket.
Quick Time entries now respect ticket-type charge rate rules.
Canned Text can include file attachments.
Control Quick Close visibility per ticket type.
PDF Templates now respect access controls.
The team demonstrates Renada’s custom “Log Site Visit” action as a cleaner alternative to Halo’s arrive/leave process.
Show the Main Contact directly in Site views.
The Team label is clickable and opens the team configuration.
A new system use allows receiving all POs from a ticket in one action.
Event management can map incoming data to the ticket Source field.
The Add Note to Parent option can now be combined with other system uses.
Custom SQL single select fields can now auto-populate with their first value.
A new User field is available for actions.
Rules can evaluate total time logged to trigger pop-ups or actions.
Backend optimizations enhance ServiceNow sync reliability and speed.
Mail campaigns can leverage dynamic distribution lists.
Large reports now load page-by-page to avoid browser timeouts.
Adds criteria-based indexing controls for AI and search.
Different holiday types can have their own allowances and carry-over rules.
Rules can now check if a checkbox is not selected.
You can insert dynamic values into recurring invoice notes and references.
Charge rate controls can now be applied at the top-level entity.
Lookup profiles can now trigger based on checkbox fields.
Choose which mailbox sends automated reports.
Dashboard filters support multiple selections at once.
Like many MSPs, Rising Tide invests in our people through access to books, trainings, conferences, and certifications. At its core, this is not education for education’s sake: rather, we believe the best technical work starts with curiosity, and we consistently seek ways to foster curiosity as a skill. You see, we think the best solutions come not just from curiosity about technology, but curiosity about each other, about our clients, and about our community. We want to be known as people who ask better questions, understand others' perspectives with clarity, and are always hungry for more. We believe that personal growth will always drive technical and professional success for our team, and as a result, our clients.
So how does a business foster curiosity? Curiosity is not something you learn from an SOP, a certification, or a conference. It’s something you develop by creating the time and space for yourself and your people to feel safe to speak up, to ideate, to build, and to iterate.
We are doing our best to build a culture of curiosity and progress in as many ways as possible, not just through structured education, but in choosing tools, conversations, and activities where we can intentionally seek to learn from and about each other and the world around us. The last part is very important at a core level: we believe every person brings a different background, toolkit, and perspective that strengthens and deepens our own, even — or especially! — when we disagree.
As a fully remote team of 6, this can be pretty difficult to do since we can’t go out for lunch or have regular physical touchpoints other brick-and-mortar businesses may enjoy. So, one of the standard ways we cultivate this is through scheduled daily and weekly team conversations where we review customer issues, books or videos, conferences attended, or other interesting things we’ve seen that we want to share.
Most recently, we chose to essentially start a book club where we would read The Go-Giver by Bob Burg, together, and to invite clients and friends to review it with us on a weekly call. It was important to us that as a team expectation, we should make sure no one felt the demand too great on top of weekly work expectations. Thus, we decided on reading one chapter (7-10 pages) a week, to make sure that it felt accessible to everyone. (Reading ahead is absolutely allowed and encouraged, but we will only discuss one chapter a week!)
The next question for a book club is: how do you facilitate conversation in a way that allows for people to share what was meaningful to them, or to join in the conversation even if they didn’t get a chance to read? In preparing for our book meetings, I sought out online resources with simple chapter-by-chapter discussion questions. However, as a very easy read, it seemed that most questions online covered concepts that spanned multiple chapters, which encouraged reading ahead and missing perhaps some smaller ideas worth savoring in each chapter.
Honestly, we figure we’re not alone in this desire to have simple questions and to walk carefully through conversations, so we've decided to share our own discussion questions, chapter-by-chapter! These questions are written without consideration for future chapters of the book and are meant to help bring in conversation about the topics and themes specifically covered in the given chapter. These questions are open-ended and if you’re facilitating, we encourage you to take the stance of no-wrong-answers, just as an impartial listener. You never know what perspectives or fresh ideas may come out of conversation.
Check out The Go-Getter Chapter One Discussion Questions here.
We’ll continue to add discussion questions and commentary on the book club as we move forward. Next things I’d like to try is to offer facilitation to a team member who has read ahead, to help them stretch their muscles of asking questions and building conversations. What other ideas should we tie in?
Want to hang out in these conversations with the Rising Tide team? We meet Fridays at 9:30 AM ET to talk through important business, technological, and communal developments, and for the next 14ish weeks, The Go-Giver! If you’re an MSP owner, consultant, or service professional who wants to grow your team’s emotional intelligence alongside your technical skill, you’re welcome here.
Reach out to partners@risingtidegroup.net for the Rising Tide Fridays Teams link. Bring your coffee and curiosity: no prep required.
If you’ve already read Book Clubs, Conversations, and Curiosity, you know that at Rising Tide, we don’t host book clubs for the sake of reading. We use them as an excuse to talk, to listen, and to practice curiosity together.
The Go-Giver by Bob Burg and John David Mann is the first book that we've chosen to explore together in this way. Each week, we’re reading one short chapter together and using a few open-ended questions to spark real conversation: no lectures, no wrong answers, just reflection.
Below are our discussion prompts for Chapter One: “The Go-Getter.”
They’re written for teams like ours: busy, service-minded, sometimes too practical for their own good...who want to slow down long enough to notice what these stories have to teach.
How this guide is different from others you'll find online: We keep it chapter-focused. Every set of questions focuses only on the current chapter so there is no foreshadowing, no jumping ahead, no “we’ll get to that in Chapter 7.” The goal is to slow down and savor the smaller ideas that get lost when you rush to the big themes, and we're going to make sure that team members that are "behind" have enough data points to connect the dots and contribute even if they're not caught up to the current reading.
Use them however you like. Whether you’re reading along with us or just looking for a fresh team conversation starter, we hope these questions help you stretch a little, think differently, and see something new in yourself or your work.
If you tweak or add questions, tell us at partners@risingtidegroup.net. We’ll keep improving this tool for other MSP teams.
Creatures of a day! What is anyone?
What is anyone not? A dream of a shadow
Is our mortal being. But when there comes to men
A gleam of splendour given of heaven,
Then rests on them a light of glory
And blessed are their days. (Pythian 8)
Want to hang out in these conversations with the Rising Tide team? We meet Fridays at 9:30 AM ET to talk through important business, technological, and communal developments, and for the next 14ish weeks, The Go-Giver! If you’re an MSP owner, consultant, or service professional who wants to grow your team’s emotional intelligence alongside your technical skill, you’re welcome here.
Reach out to partners@risingtidegroup.net for the Rising Tide Fridays Teams link. Bring your coffee and curiosity: no prep required.