By
Mendy Green
December 12, 2022
•
20 min read
Fundamental Skills
Professional Development

Critical thinking is an essential skill for success in both personal and professional life. It involves the ability to think independently and objectively, to analyze and evaluate information and arguments, and to make sound and logical decisions.
Learning critical thinking is not always easy, but it is a skill that can be developed and improved with practice. Here are some tips for how to learn critical thinking:
Assumptions are an important part of the critical thinking process, as they help us make sense of the world and make predictions about future events. However, assumptions can also be dangerous, as they can lead us to make false or misguided conclusions.
One of the dangers of assumptions is that they can be based on incomplete or incorrect information. For example, if we make an assumption about someone’s intentions based on limited information, we may be mistaken and draw the wrong conclusion. This can lead to misunderstandings and conflicts with otherwise could have been avoided, whereas when we properly assess a situation, it keeps us agile and allows us to adjust to meet the new circumstances (both in personal and professional lives).
Another danger of assumptions is that they can lead us to become overconfident in our beliefs and conclusions. When we make an assumption, we may be more likely to ignore or dismiss something that we see or that someone tells us that contradicts our assumption. This can lead to confirmation bias, where we only consider evidence that supports our assumption, and can prevent us from seeing the whole picture, or alternative perspectives.
Despite these dangers, assumptions are still necessary in the critical thinking process. Without assumptions, we wouldn’t have a way to continue moving forward through the process Instead, we would have to rely on raw data and facts, and we’d be stuck without being able to collect new raw data. Making an assumption is necessary for us to test the raw data and allow us to collect more (such as if the assumption is right or wrong). It’s kind of like shaking the wrapped present to see if we can guess what’s inside…we just need to be prepared for the possibility that we might break it.
With assumptions being so crucial to the Critical Thinking process, it’s important to be aware of the dangers of assumptions and to approach them cautiously. We should be open to revising or rejecting our assumptions based on new evidence, and we should strive to be as objective and unbiased as possible. By doing so, we have a greater change of avoiding the dangers of assumptions and successfully use them to our advantage.
It’s important to update and revise the things we know when presented with evidence that contradicts it, sometime even when they’re not assumptions. This is because our understanding of the world is always evolving, and new information and evidence can challenge and expand our current beliefs and knowledge.
Updating and revising our beliefs and knowledge based on new evidence is an essential part of the critical thinking process. It allows us to be more objective and unbiased, and to avoid making false or misguided conclusions. By being open to new information and evidence, we can gain a more accurate and complete understanding of the world around us.
In a rapidly changing world, it’s important to be able to adjust and update our understanding of the world in order to make informed and effective decisions. By updating and revising our beliefs and knowledge, we can remain open to new ideas and opportunities, and can continue to learn and grow.

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.