By
El Copeland
October 28, 2024
•
20 min read
Fundamental Skills

The article you've stumbled across is the first in a collection of five blog posts meant to be an extension of The Care and Feeding of Meat Computers series which I’m releasing on the Rising Tide YouTube channel, born from a talk I shared at MSPGeekCon 2023. These companion guides are intended to help provide links to resources, research, and books that informed parts of this collection. The goal is to give you enough information and connections so you can dig into these concepts, including things that I cut from the talks for time or other organizational, boring reasons. I am also going to include some questions at the end of each guide to help you facilitate conversation with your team or to further deepen it!
Before we go much further, it's important to me to also extend my gratitude to the people who helped me make sure this talk happened in the first place. Heather and Brian at Gozynta encouraged me as I wrote and honed this concept the first time and generously sponsored me to attend MSPGeekCon and give this talk. Matt Fox, for the reliable perspective, fresh jokes, and tots. Alicia Gregory for academic and psychological insight, a cache of useful journal articles, and listening to me cry basically bi-weekly for nearly a decade.
Of course, last but not least, my business partner, Mendy Green, for believing in me and that this concept needed to see the light of day at all instead of just our five-minute-long WhatsApp voice notes.
If you’re here, there’s a good chance you’re involved in technology, whether you follow Rising Tide, are a part of the MSPGeek community, or otherwise found this series while searching the depths of the internet. Regardless of who you are or where you’re from, come on in, make a cup of something warm, and have a seat. I hope that you will find each word expressing my sincere love to the tech community, specifically to those often-unsung heroes, the nerds whose daily, Sisyphean job is to balance the science behind tech with the increasingly important art of human understanding.
This series is for those of you who may feel (or those of you who manage and collaborate with those who feel) more at home with your hard skills compared to soft skills. It’s completely understandable: in our society, and especially in tech, we tend to believe hard skills are the “real” skills, while soft skills are secondary or nice-to-have. But don’t let your imposter syndrome about the places you feel weak dictate what is real or true! Just because something can easily be expressed through certifications doesn’t mean they are more valuable or will help you live a more fulfilling life. In fact, you may have even been called “gifted” when it comes to technology, and as such, choose to feed that part of you, first. If we consider some of the theories about giftedness, specifically Renzulli’s three-ring conception of it, giftedness for any skill comes from ability, creativity, and commitment.

My goal with this series is to challenge the view that hard skills are respected and most prized; and to encourage us to reframe “soft skills” not as something separate or less-than, but as essential, accessible, and attainable, intertwined with our technical expertise. We may not come by it naturally, as in an above-average-ability, but with creativity and commitment, we can develop these skills as well!
I specifically want us to look at soft skills in a way that outright refuses the notion that as you are, you are bad, undesirable, or unacceptable. While there are certain social standards that you may have been trained to adhere to, I want you to put those rules aside for these conversations. If you’ve ever felt like you’re expected to fit a mold to be successful—whether to be more charismatic, more structured, or even more proper—this series is for you.
I’ve held a ton of jobs in a wide variety of industries and tiers of responsibilities. Despite my breadth and depth of experience and knowledge, I’m not interested in being revered as an expert. Experts tell you what you’re supposed to do and exactly how you’re supposed to do it to guarantee success. I’m sure my disdain for this snake-oily social power dynamic shows consistently in things I say and my approach in this series. Why the sass regarding experts? I want you to know and truly embrace the fact that your value as a tech professional goes beyond fitting into the boxes people want to put you in. Your value as a tech professional goes beyond fitting into the boxes you want to put yourself in! I’m not an expert, experts want you to be like them. I want you to be like you.
You have these skills: you have social skills, you have people skills, you have soft skills. Regardless of if they fit into what some expert tells you is “correct,” if you’re a little bit weird, I want you to embrace it.
You’re here because you’re passionate about technical solutions, and you’re here because you’re looking for ways to develop further yourself and your community. I propose to you that your passion for technology is actually a powerful tool, if not the most powerful tool, in developing your soft skills. You can use your technical intelligence to boost your Emotional Intelligence.
It’s time to stop kidding ourselves that hard skills are technical and measurable while that soft skills are just a “personality trait” exemplified by gentle people like women and mothers. This belief implies two terrible, not-true things:
This is a disservice to you and those who you work with. You have soft skills, and developing and enhancing them is vital to your personal and professional growth. Here’s the thing: soft skills are hard. But that doesn’t mean they aren’t worth shaping or that they’re out of your reach as a technical, linear-minded person. Soft skills are hard-won through life experiences, loss, pain, and PRACTICE.
These concepts fold neatly into coding ideologies like Human-Centered Design and Human-Computer Interaction. You are technical, you are practical. Humans are hard. Let’s reframe this to help ourselves be more successful. I propose that soft skills aren’t the opposite of hard skills, but an evolution of them, and if you find them hard, perhaps you just need to look at humans as what they are: complex meat computers that really just want to do what they can to survive and thrive in the world they’ve inherited, just like you.
So together, let’s flip the script and let’s start with reframing a questions we often ask, to see how we can better harness our natural penchant for hard skills and alchemize them into above average soft skills.
Join me as we elevate the question, “Why aren’t people more like computers?” to “Why might people be too much like computers?” Instead of following a set of rules, I want you to ask yourself, “what if I treat people with just as much care and curiosity as I treat computers? What would my life, my job, and my relationships look like, instead?”
To deepen the concepts discussed in this series, here are several resources for further exploration:
Questions for Team Reflection
If you’re watching this series with a team, here are some questions to guide your discussion and help you make the most of these ideas:
That’s it for Episode 1! Tune in for our next Episode: The most expensive piece of technology you’ll ever see.

Episode 20 of By the [run]Book dives into HaloPSA v2.214 with a mix of practical improvements and some quirky additions. Connor and Mendy walk through everything from new dollar variables and asset controls to Avalara fixes and portal enhancements—highlighting what actually matters for day-to-day MSP operations. This episode is especially useful for MSPs refining workflows, automation, and reporting accuracy in Halo.
Watch Now: By the [run]Book: Episode 20
For easier tracking, check out haloreleases.remmy.dev to filter and search HaloPSA updates by ID, version, and keyword.
Mendy and Connor noted this was very useful.
Highlighted during the user action demo as a practical workflow improvement.
Called out as a genuinely useful UI improvement.
Allows more flexibility in how incoming emails are matched to tickets.
Enables automation of asset configuration through API usage.
Introduces a new variable to output custom fields in Q&A format.
Improves visibility into asset changes over time.
Returns the email address of the user associated with a purchase order.
Enhances usability and visibility of search results in the portal.
Provides control over configuration synchronization.
Ensures correct popup behavior when multiple rules trigger.
Makes ticket source available for reporting and filtering.
Adds safeguards when configuring email matching tags.
Allows distribution lists to target all email addresses tied to a user.
Improves clarity in Avalara transaction records.
Adds control over visibility of user actions in the portal.
Improves flexibility when using Accounts and Prospects.
Enables dynamic fields based on asset lifecycle status.
Ensures asset tagging consistency during stock processes.
Adds control over Avalara synchronization scope.
Allows a predefined score for surveys.
Improves visibility when prorating billing items.
Automatically generates a ticket alongside sales orders.
Allows column width customization in list views.
Changes ordering of lists in the team view.
Adds asset status as a usable variable in buttons.
Improves flexibility when viewing lists.
Allows visual customization of buttons.
Enables distribution lists based on ticket criteria.
Adds control over forecast data ranges.
Enhances performance of Azure/Entra sync.
Improves visibility of ticket closure information.
Optimizes webhook performance and payload handling.
Refines permissions for asset management.

Episode 19 walks through HaloPSA v2.212 and v2.214, covering a wide range of quality-of-life improvements, admin controls, and workflow enhancements. Connor and Robbie highlight updates around ticket forms, invoicing, templates, and automation, making this especially useful for MSPs looking to tighten processes and improve day-to-day efficiency.
Watch Now: By the [run]Book: Episode 19
For easier tracking, check out haloreleases.remmy.dev to filter and search HaloPSA updates by ID, version, and keyword.
Allows assets to be linked directly to a client instead of only via a site.
Improves tracking of report usage across dashboards.
Adds control over end-user assignment in templates.
Prevents actions on tickets for stopped clients or sites.
Allows updating custom fields directly via actions.
Prevents approval of expired quotes.
Adds variables for original customer addresses.
Ensures hidden fields do not retain values.
Adds advanced relative date filtering.
Adds preview functionality for templates.
Allows editing of existing meter readings.
Improves grouping of invoice items.
Enables merging duplicate assets.
Displays number of related tickets.
Enhances monitoring integration mapping.
Adds more control to purchase order lifecycle.
Enables workflows triggered by agent emails.
Adds mapping and geolocation features.
Introduces guided project setup.
Allows updating ticket fields post-creation in chat.
Prevents deletion of populated top-level structures.
Improves timesheet usability.
Fixes inconsistent quote PDF behavior.
Aligns quote email behavior with configuration.
Adds access to billing profiles from invoice screen.
Allows use of quote data in actions.
Adds new automation trigger.
Adds rich text support for asset fields.
Prevents closure when tasks remain open.
Adds approvals to activity feed.
Removes agent login option from portal.
Adds ordering control to lookup codes.
Adds planning field to releases.
Enables guided onboarding tools.
Adds note field to consignment lines.
Expands team visibility.
Extends accessibility tools to main app.
Displays previous invoice values.
Exposes billing data to API.
Adds search to selection fields.
Aligns call screen logic with ticket settings.
Links credit lines to original sales orders.
Improves invoice ID handling.
Introduces role-based API identity.

In this episode of By the Runbook, the team continues through the HaloPSA 2.212 release notes and spends time unpacking what several of these changes actually mean in practice. The conversation covers workflow design, mail campaigns, ticket views, reporting, and automation behavior, with especially useful commentary for MSPs trying to decide what to enable, what to ignore, and what to be careful with.
Watch Now: By the [run]Book: Episode 18
For easier tracking, check out haloreleases.remmy.dev to filter and search HaloPSA updates by ID, version, and keyword.
Check out MSP Blueprint for info on runbooks: MSPBlueprint
This allows the ticket screen to automatically refresh when a background automation completes.
Expands qualification matching to include custom field criteria.
Adds delayed and retry-based webhook processing options.
This change limits the available “From” addresses on a ticket action to mailboxes the assigned team can actually access.
Adds Email Address as another attribute option for follower behavior on the portal.
Allows changes to Mail Campaigns after they have started.
Restricts pipeline stages based on opportunity type.
Adds webhook processing options including delayed and retry handling.
Adds the ability to hide tickets from the change calendar.
Adds Service Users as a selectable option in distribution and user lists.
Allows campaigns to be sent from sales mailboxes.
Adds a warning when an action email will fail.
Adds asset relationship mapping during SQL imports.
Adds an isRunning field to asset discovery.
Expands qualification matching with custom field rules.
Allows ticket view to auto-refresh after automation runs.
Adds ability to update currency values on quotes.
Requires comments for negative KB feedback.
Adds control for showing nested tickets.
Enhances AI reporting capabilities.
Restricts KB edits to owners only.
Adds translation support in the portal.
Adds secondary MAC address support.
Adds character limits to text fields.
Adds more fields for OLA and rule reporting.
Prevents approvals from email replies.
Extends field copying to deeper ticket levels.
Adds primary asset as a runbook condition.
Adds AgentID variable for lookups.
Adds reporting changes to config tracking.
Adds filter profiles to child ticket views.
Adds more configuration options to other open tickets view.