By
Mendy Green
July 5, 2024
•
20 min read
Fundamental Skills
Professional Development
Laws for the Practical Technician
Over the years of training and assisting various technicians, I've formed a set of guidelines that I've been known to drill constantly. The other day while talking to a newer technician and working with them I realized that I now have the time I didn't have before to actually write down what I've been ranting about for 14 years. I've dubbed them as the Laws for the Practical Technician.
- Keep an open mind when approaching the problem and avoid falling back into the "End User" mindset
- Read and explore everything on the screen! Pay attention to what's being done and what its telling you
- Understand the problem at least as well as the person asking you for help
- Be intentional in your troubleshooting, closing your eyes and throwing darts at the wall is not helpful
- Question everything you think you know and are being told
- Always have a way out, make sure you can undo anything you do
There's a lot of nuance in each "law" so now that we got the TLDR version out of the way let's dive into the specifics. Note for the purposes of this post, each law has been given a title.
1. The "Technician" Mindset
Keep an open mind when approaching the problem and avoid falling back into the "End User" mindset
If you run around with your eyes closed expecting nothing to get in your way, you're bound to smack into a wall (or something) and fall down. If you keep your eyes open and aware of your surroundings you can navigate the obstacles and overcome them.
End users typically expect systems to work seamlessly and view issues as problems needing external help. Technicians, on the other hand, approach systems with the expectation that things might not work and are prepared to "figure it out" each time.
Key Points:
- Expect Issues: Approach every situation with the mindset that things might not work as expected. This keeps it fresh in your mind and allows you to figure out what should or should not be happening each time, and usually during that process you'll identify the disconnect that's causing the issue.
- Problem-Solving Approach: View issues as challenges to be solved rather than insurmountable problems. This proactive mindset helps in finding creative solutions.
- Context Matters: The difference in mindset is less about the person and more about the context! Everyone (for the most part) handles their own problems for their personal lives daily. The moment it becomes a work or tech issue suddenly its hands-off. Be aware of the context you're in, this affects Clients escalating to IT and IT escalating to a higher tier! Don't fall into the trap.
Example: When dealing with a software bug, an end user might see it as "broken" and wait for a fix. A technician, however, will explore various angles—checking logs, considering recent changes, and testing different scenarios to identify the root cause, or find a viable workaround
2. Read the Entire Screen
Read and explore everything on the screen! Pay attention to what's being done and what its telling you
Computers and software are designed to be used, (it's actually the only way they make money!). Therefore, the information needed to operate or troubleshoot them is generally available on the screen or in logs, (although the language can be context-specific for the industry). To effectively identify and solve issues, it's crucial to explore the interface and ask questions. Thoroughly reading on-screen messages and prompts can provide insights into what might be wrong and how to address it.
When encountering an error message or unexpected behavior, don’t rush to conclusions, AND DO NOT SKIP IT!
Instead, read all the details provided. Error codes, system messages, and even seemingly minor details can offer significant clues. For instance, a message that seems obscure at first glance might make sense when considered within the context of the application or system you're working on. Even comparing against a computer that is working, looking for differences in behavior, or order of operations, screen activity, and so on, can provide clues (for example an error that takes a while to appear is likely caused by a timeout, vs an error that appears immediately is likely caused by an immediate rejection).
Example: If a user reports an issue with a software application crashing, instead of just noting "application crashes," you should read any error messages, logs, or system prompts that appear when the crash occurs. These details can guide you towards understanding the root cause and potential fixes.
3. Understand the Problem
Understand the problem at least as well as the person asking you for help
To effectively troubleshoot, ensure you can recreate the problem and understand its significance. Start by asking the person reporting the issue why it's a problem and why it's important to solve it. Gather as much information as possible to understand all sides of the issue. You should be able to understand the problem at least as well as the person reporting it to you, otherwise how do you expect to fix it? Or even explain it to the next escalation point if you have to reach out for help?
Here are some ways you can work to understand the problem.
- Recreate the Problem: Attempt to replicate the issue in your environment. This step is the best option because it allows you to see the problem firsthand and understand its nuances, at the same time as testing to see if its a problem with their computer only or a wider issue. You can also choose to recreate the problem on a different system, if it requires specific applications or files you don't have on your computer directly.
- Understand the Impact: Determine why the issue is significant. Is it causing data loss, preventing critical operations, or just a minor inconvenience? Understanding the impact helps prioritize the issue and communicate its importance to others.
- Gather Detailed Information: Ask the user detailed questions about the problem. When did it start? What were they doing when it occurred? Has anything changed recently (e.g., new software, updates, hardware changes)? What's normally supposed to happen?
- Prepare for Escalation: If you cannot resolve the issue, you might need to escalate it to a vendor or higher-level support. Having detailed information and a clear understanding of the problem will make this process smoother and more effective.
Example: If a user cannot access a shared network drive, ask them about any recent changes to their system, any specific error messages they receive, and how critical this access is to their work. Look at what the shared drive is mapped to, and if other people have access to it that are working. Identify the network the user who is complaining about is on and if it has connectivity to the shared drive host. This comprehensive understanding allows you to troubleshoot more effectively and escalate if needed.
4. Be Intentional
Be intentional in your troubleshooting, closing your eyes and throwing darts at the wall is not helpful
Being intentional in your actions means making deliberate, thoughtful decisions rather than taking random stabs at fixing an issue. This approach prevents exacerbating the problem and leads to more efficient troubleshooting. Most technicians below Tier 3 will perform troubleshooting by way of "trying different thing to see what works", this is essentially closing your eyes and trying to pin the tail on the donkey, make sure you understand what is going on, and the logical reason why what you're attempting will affect (either negatively or positively) the current outcome so that you can make progress with every step.
Expand on This:
- Map out the "Attack" Chain: Before diving into fixing an issue, outline the Chain that exists to allow the system you're troubleshooting to work during normal behavior. What are the potential areas for disconnect? What steps will you take to test that the chain is working throughout?
- Progress is Progress (both good and bad): Any change in outcome is desired, as it'll help provide information about the underlying behavior that we don't have visibility into. Look for error messages, success messages, timers, lags and so on. No detail is too small.
- Evaluate and Adjust: After each step, evaluate whether it has brought you closer to resolving the issue. Adjust your approach based on these evaluations.
Example: If a printer isn’t working, don’t randomly try different fixes like restarting the printer, reinstalling drivers, or changing settings. Instead, follow a logical sequence—check for error messages to help point you towards a connection issue or a driver issue.
5. Question Assumptions
Question everything you think you know and are being told.
Always be prepared to reassess what you know. Technology and systems evolve, and what was true yesterday might not hold today. Keeping an open mind and questioning assumptions can lead to discovering the true cause of an issue.
Expand on This:
- Expect to be wrong all the time: When you're right about something there's no reason to go back and check because you know you're right. If you're wrong about something then you'll be looking to validate that you are wrong, or what the right answer is. This mindset helps keep your knowledge fresh and reminds you to double check everything you think you know or are being told.
- Seek Out Information: Be proactive in seeking out new information and learning from others. Forums, user groups, and official documentation can offer insights you might not have considered. Often times all it takes to help find the answer is asking the question, not to the person next to you, but even to yourself! Use the Rubber Duck method if you need to.
Example: If a network issue arises, don’t assume it’s due to the same cause as last time. Reevaluate the situation - start the troubleshooting process from scratch everytime until you've identified the root cause to the be the same as last time.
6. Never Do Something You Can't Undo
Always have a way out, make sure you can undo anything you do
Always have a contingency plan before making changes. Ensure that any action you take can be reversed if it doesn’t resolve the issue or causes new problems.
Expand on This:
- Backup First: Before making destructive changes, find a way to keep a good copy of what you're changing. This ensures that you can revert back if needed.
- Test Changes: Where possible, test changes in a controlled environment before applying them to the live system.
- Document Reversible Steps: Ensure that every action you take can be undone. Document the steps if necessary so you can revert configurations and settings.
Example: Before modifying a system registry, backup the registry or export the key in question. Rename something instead of deleting it, or cut/paste it somewhere else. This way, if the change has unintended consequences, you can easily revert to the previous state.
----
Edit 2024/11/13 | This article has been presented and recorded at The IT Nation Connect 2024 in Orlando, Florida! You can watch it here: https://youtu.be/ZJqhT48pnLU
I'm passionate about IT, driven by a dual love for solving complex problems and a commitment to transforming the stereotype of technical support into a positive and enjoyable user experience. For over 13 years, I've been deeply involved in the MSPGeek community, lending my expertise to various Managed Service Providers (MSPs), while also serving as the CTO at IntelliComp Technologies.
My journey in the tech world is fueled by a passion for teaching others. I find great satisfaction in imparting problem-solving and critical thinking skills, and offering practical guidance during the troubleshooting process. It's this enthusiasm for mentorship and improvement that led me to my current venture.
Today, as the founder of Rising Tide, I'm focusing on the MSP industry, dedicating my time to coaching and assisting both individuals and businesses. At Rising Tide, we're not just about providing solutions; we're about nurturing growth, fostering innovation, and building a community where everyone can rise together. Whether it's through hands-on problem solving or strategic planning, my goal is to make the IT experience not just efficient, but also empowering and enjoyable
See some more of our most recent posts...
By the [run]Book: Episode 4
By the Run Book dives into HaloPSA v2.192 — from holiday approval tweaks and smarter contract scheduling to AI suggestions, new security controls, and Robbie’s Quick Ticket app for lightning-fast ticket logging.
Read post
In Episode 4 of By the Run Book, the team digs into HaloPSA v2.192 with a mix of technical deep-dives and practical tips for MSPs. Robbie and Mendy walk through improvements in holiday approvals, contract schedule plans, and important security updates like webhook authentication. They also explore quality-of-life changes in ticket type restrictions, AI suggestions without an AI license, and new admin mode controls. To wrap up, Robbie demos his “Quick Ticket” browser extension for lightning-fast ticket creation without breaking your workflow. Whether you’re streamlining internal processes, tightening security, or speeding up ticket logging, this release has something to improve your day-to-day.
Watch Now: By the [run]Book: Episode 4
Robbie's Quick Tickets: Halo Quick Ticket - Microsoft Edge Addons
Multiple minor improvements to Holiday Approvals | v2.192 #948186 | 3:55
- Shows balance in days/hours instead of decimals
- Approval screen now displays holiday details
- Fix for approval from holiday record failing
Multiple minor changes to improve Contract Schedule Plan functionality | v2.192 #947953 | 7:01
- Easier setup for scheduled contract work
- Tracks allocated vs. remaining hours
- Still manual for recurring hour replenishment
Federated credentials update endpoint | v2.192 #937555 | 13:40
- API endpoint to update federated credentials more easily
Quotation Config: remove whitespace from signature image | v2.192 #937347 | 14:30
- Option to trim white background from customer signature images
Ready for Invoicing filter applies to other billable entities | v2.192 #937175 | 17:17
- Top-level Customer criteria now carry over to other billable entities
- Ignores other non-applicable filter criteria
Integration and webhook improvements | v2.192 #936110, #936402, #936998, #936862, #936739 | 19:34
- Various integration updates including webhook authentication
Charge Rate restrictions at Ticket Type | v2.192 #933938 | 22:17
- Restrict allowed charge rates for specific ticket types
AI Suggestions without AI integration | v2.192 #923472 | 24:48
- Use AI Suggestions feature without enabling AI integration
Admin Mode security improvement | v2.192 #909530 | 31:55
- Requires 2FA to enable Admin Mode
- Adds audit logging of activations
Load Balance limits by Team | v2.192 #898859 | 35:52
- Limit tickets assigned via load balancing per team
Forecasting Module improvements | v2.192 #883797 | 36:00
- Enhancements to AI-based forecasting for tickets, hours, and reports
Enabled for Instances option | v2.192 #882671 | 39:05
- Limit notifications, webhooks, and runbooks to specific instances
Disable editing of config-tracked entities | v2.192 #882664 | 39:32
- Prevent editing config-tracked entities directly in production
Sprints for config tracking | v2.192 #882648 | 40:26
- Group config changes into deployable sprints
Filter ticket types on New Ticket screen by group | v2.192 #858227 | 41:40
- New ticket screen can be filtered by Ticket Type Group
Show/hide more User system fields in Screen Layout Profiles | v2.192 #856243 | 47:20
- Added more User fields to show/hide controls
Add new Contacts on Opportunities | v2.192 #840296 | 47:46
- Add contacts directly from existing opportunities
Owners and Assets in article query builder | v2.192 #836009 | 48:06
- Owners and Assets now reportable in article queries
Added $-LOGGEDINAGENTSIGNATURE variable | v2.192 #831158 | 48:15
- Variable for logged-in agent’s signature
Unit prices in Product Bundles on Quotes | v2.192 #823474 | 48:53
- Show per-unit price when group quantifier enabled
Restrict creation of new article tags | v2.192 #822558 | 49:48
- Only allow selecting from existing article tags
Primary agent, secondary agent, and account manager as additional agents | v2.192 #821136 | 49:57
- Option to add these roles as additional agents when logging a ticket
Countersign Quotations | v2.192 #820956 | 53:04
- Allow countersigning of quotations before finalizing
Prefix for $ variables with data | v2.192 #793305 | 53:55
- Prefix only appears if variable contains data
Halo Quick Ticket extension demo | 55:21
- Robbie’s Edge/Chrome extension for quick ticket creation
- OAuth setup with Halo, select fields, and complete on creation
By the [run]Book: Episode 2
HaloPSA 2.188 introduced runbook triggers via chat, smarter billing rules, and cleaner settings layouts. In this recap, Mendy and Connor unpack key updates, link to demo timestamps, and flag risks like the still-unruly HubSpot sync. This is your practical guide to deploying the new features with confidence (and a few extra guardrails).
Read post
HaloPSA version 2.188 brought a variety of usability and backend enhancements—from runbook triggers in chat to finer-grain billing logic and cleaner settings layouts. In Episode 2, Mendy and Connor walk through these updates, troubleshoot common gotchas, and share the kind of real-world implementation advice you can only get from people deep in the trenches. They also made a point to mention a few times to add feature requests at ideas.halopsa.com
Watch now: https://youtube.com/live/6tjM4SGOcB4
Busy MSP? This guide recaps the episode’s major updates, links you to key moments in the video, and flags anything that might deserve extra caution in deployment.
Join us July 22, 2025 for Episode 3, where we'll start to cover v2.190!
Trigger Runbooks from Chat | v2.188 #838526 | 3:14
Chat flows can now kick off integration commands—including runbooks. Embed chat on your website or in Teams, and let Halo handle the routing. You could:
- Run diagnostics
- Route to support teams
- Automatically open categorized tickets
⚠️ Be careful what runbooks you expose publicly—especially if they modify data.
Notification Sound Customization | v2.188 #820304 | 6:58
You can now toggle the notification sound on or off—but the visual popup still appears. You still can’t upload custom sounds, and notifications can get out of hand across tabs.
💡 Bonus tip: You can suppress sound notifications per rule, but they may still clutter the alert pane.
WebSocket Notifications (Beta) | v2.188 #839402 | 8:02
Enable WebSockets for faster, real-time alerts instead of using the default polling (heartbeat). This reduces delay in receiving internal or backend alerts.
Backend Service Monitoring Logs | v2.188 #840002 | 9:13
Debug runbooks, automations, email failures, and integration issues using the new service monitoring pane. It logs each backend action so you can pinpoint where workflows failed.
🔍 You no longer need to email Halo support for log digging—huge time-saver.
Travel Charge Rate Flexibility | v2.188 #843591 | 15:25
You can now set separate rates for time and distance in a single travel charge entry. Perfect for billing both mileage and technician transit time in a single step.
Email & Settings UI Reorganization | v2.188 #839711 | 21:22
Settings like mailboxes, templates, and rules have been reorganized into distinct tabs instead of being buried under “General.” More logical, but prepare for some retraining of your internal muscle memory.
Auto-Expire Contract Logic | v2.188 #842066 | 25:50
Set a contract status to auto-expire when the end date passes. A scheduled task now flips expired contracts to “inactive” if configured.
⚠️ Hidden contracts can cause trouble—pair this with automated tickets or alerts to track renewal conversations.
Item Group Accounting & Billing Defaults | v2.188 #844350 | 33:00
You can now:
- Prevent PO receiving or invoice creation at group level
- Exclude groups from accounting sync (useful for test/staging items)
Connor and Mendy share tips for keeping messy product catalogs from polluting QuickBooks/Xero.
Client-Specific To-Do Groups | v2.188 #847221 | 51:57
To-do groups can now be restricted to specific customers. Use this to tailor onboarding checklists, project tasks, or compliance processes.
⚠️ Only one customer per group for now. Feels clunky, but it’s a start.
Clone Billing Templates | v2.188 #849112 | 52:32
Quickly duplicate complex billing logic with a new “Clone” button. Ideal for MSPs using multiple templates per client or those needing custom combinations for each contract type.
Advanced Billing Rule Matching | v2.188 #850203 | 54:23
Billing plan rules can now reference:
- Ticket custom fields
- Action fields
- Agent properties
Use this to get laser-precise about when a contract or billing model should apply.
New Custom Field Storage Options | v2.188 #853900 | 1:04:20
Choose between traditional storage (custom fields added to core tables) or a new “separate table” method. The latter avoids bloating system tables—but still stores multi-selects as comma-separated strings (ugh).
Quote XLS Import Profiles | v2.188 #855612 | 1:18:27
You can now import vendor quote spreadsheets directly into Halo quotes. Set up mappings for Cisco, Dell, or distributor quote templates and save serious time.
OAuth via Custom Developer Apps | v2.188 #856711 | 1:21:52
You’re no longer stuck using Halo’s shared apps. Bring your own app registration to limit scopes, improve auditing, and align with internal security policy.
Recurring Invoice Proration Simplification | v2.188 #857744 | 1:24:33
A new setting condenses prorated adjustments into a single invoice line (instead of two). Easier to read—but harder to debug.
🔍 Consider leaving this disabled unless your team fully understands the logic.
HubSpot Integration Tweaks (and Pain) | v2.188 #859011 | 1:31:35
The HubSpot sync continues to be... challenging:
- Doesn’t respect new “Accounts & Prospects” model
- Overwrites domains and duplicates clients
- Inconsistent inbound behavior
Proceed with extreme caution or disable it entirely.
By the [run]Book: Episode 3
This HaloPSA release may not grab headlines, but it delivers smart backend fixes for billing, approvals, and project automation. From delegate ticket approvals to proration-ready invoices and improved QuickBooks syncing, it's a solid batch of quality-of-life upgrades for fast-moving teams and structured orgs alike.
Read post
This release didn’t come with any headline grabbers—but for those deep in Halo, it delivered a handful of quality-of-life improvements and some thoughtful backend fixes. Below are the features worth your attention, especially if you're in billing, approvals, or building project automation.
Watch here now: https://youtube.com/live/WGnJXYeSxN4
Features Reviewed
Delegate Approvals for Tickets | v2.190 #830512 | 2:28
Ticket approvers can now assign delegates directly from the agent app ticket detail screen. Great for ITSM or structured orgs, but less relevant for fast-moving MSPs unless you're running approvals regularly.
Manual Proration Made Invoice-Ready | v2.190 #823611 | 4:18
A new checkbox on manual proration entries lets them show up in the invoicing screen immediately. Particularly useful for mid-cycle adjustments to annual billing, like licensing or domains.
Zero Draft Invoice Handling | v2.190 #819999 | 6:41
Halo will now ignore draft invoices created in Xero, preventing clutter and accidental syncing. You'll need to enable this in the Xero integration webhook settings.
Receive Stock Before PO Approval | v2.190 #829771 | 9:04
You can now receive items before a purchase order is approved. Risky for strict workflows but may fit fast-paced environments where hardware urgency overrides red tape.
Auto-Issue Items from Actions | v2.190 #837101 | 10:21
Set up actions to issue specific inventory items without user selection. Makes fixed-fee tickets more maintainable. Bug alert: doesn't yet work with quick actions—still requires a workaround.
Ticket ID in PDF Template Item Tables | v2.190 #837112 | 12:39
PDF templates can now pull the associated ticket ID into item tables—helpful for clarity in documentation, reporting, or client-facing PDFs.
Read-Only Appointment Subjects | v2.190 #829744 | 17:43
Admins can lock appointment subjects to match the ticket/project. It’s a small control that helps standardize records across large teams.
Editable Invoice Line Contract Links | v2.190 #823492 | 20:41
You can now edit the contract tied to a specific invoice line—especially valuable if you're tracking profitability across services with multiple contracts.
Prevent RMM from Changing Device Types | v2.190 #821917 | 24:58
ConnectWise RMM imports won't overwrite an existing device type anymore, assuming you check the new box.
QuickBooks Name Collision Workaround | v2.190 #829321 | 26:05
Halo now checks for matching item names before syncing, and links them rather than creating duplicates. A clever patch for a QuickBooks API issue.
Ticket Type as Rule Outcome | v2.190 #831422 | 27:28
You can now set ticket type via rule outcomes. Great for automating triage flows or conversions between types during lifecycle changes.
Team Custom Fields in Details Tab | v2.190 #831994 | 31:13
You can finally surface custom fields tied to teams directly in ticket details. Limited use cases for now, but it’s a step toward richer internal data visibility.
Granular Attachment Permissions | v2.190 #829812 | 32:36
Admins can now control who can view, edit, upload, and download attachments—down to the ticket type and role level.
Track Completion of Sales Lines | v2.190 #832113 | 33:58
Sales order lines can be manually or automatically marked as “Complete.” Adds helpful clarity, especially when you're tracking partial progress across installs or shipments.
Runbook Execution Modes (Parallel/Sequential) | v2.190 #830301 | 35:27
Control how runbooks trigger: run steps in parallel for speed or in series to avoid conflicts and ensure data accuracy.
Column Profiles for Invoices & Quotes | v2.190 #834755 | 44:01
Column profiles now work on sales orders, quotes, and invoices. You can personalize the data you see—and what you hide—for cleaner views.
Runbook Stats Tab | v2.190 #830996 | 35:27
Basic run metrics are now visible in a tab. Not yet robust for reporting, but a decent glance for usage and debugging.
For easier tracking, check out haloreleases.remmy.dev to filter and search HaloPSA updates by ID, version, and keyword. And join us on August 5th for a show with Robbie and Mendy: https://youtube.com/live/ApiYEmWJsPU!