By
El Copeland
May 2, 2025
•
20 min read
Professional Development

Productivity. It's one of my most beloved and yet most hated concepts. At its core, productivity is just output over time: a metric that first rose to prominence during the Industrial Revolution as we looked for a way to measure how efficiently machines (and then people) produced goods.
But, dear reader, I propose to you that we aren't machines whose only value in what we produce, and we should be intentional about evading that trap.
It's tempting to equate productivity with worth. In a tech-driven world where the average worker is already exponentially more productive than generations before, chasing productivity for its own sake can leave us burnt out and disoriented.
Chasing productivity alone can reduce our identities to more emails, more code, more content. An endless and meaningless attempt to bend the boundaries of finite resources.
Instead, I want to reframe the conversation around efficiency: meaningful output over time. Efficiency asks better questions which will lead us to better answers. No longer are we asking, "How much did you do today?" but rather, "Was it worth doing?" It is very important to me that we can reclaim this quality as something every worker can own and take pride in, and that it isn't merely a metric for middle management to squeeze as much out of you as they possibly can.

It's called Triple D not just because I'm a Guy Fieri fan (Diners, Drive-ins, and Dives is peak American reality TV in my humble opinion), but because I believe every great day at work should have that same heart: a little execution, a little learning, and a little dreaming about what’s next.
Triple D in light of our conversation on meaningful, modern productivity and efficiency in the workplace is: Do, Discover, Dream.
These three feed into each other, creating a loop of sustainable, intentional work. It honors both execution and imagination.
SInce we've defined efficiency as something every worker is in command of in their own lives, it's worth noting that attaining better efficiency isn't about having expensive software or corporate resources. It's about using what you already have as well as finding new tools. Many aspects of productivity can be inexpensive, or free. With that said, I break tools into three categories:
In order to accomplish all of the Doing, Discovering, and Dreaming you are capable of, it's vital that you establish a Flow to create structure, sense, and accountability.
Your body and brain are your most important tools. Building a rhythm that supports rest, clarity, and momentum matters more than any productivity app. Ways that you can establish Flow:
Start with what you already have. You might be surprised by what your existing tools can do.
And if your organization already uses Microsoft or Google, explore Copilot or Gemini before paying for new AI tools.

Space is more than just free time. It’s about creating breathing room to connect the dots.
Most importantly, focus on how you can build in downtime to let your mind wander. That’s where big ideas and problem-solving happen.
At the end of the day, productivity was a metric that was created for machines, and you're not a machine. You’re a human in a finite, soft body, in a world that is often very hard. Your value is not your output.
Efficiency, in contrast, helps you:
When we focus on efficiency, we create room for autonomy, insight, and innovation. That’s what helps teams thrive and businesses grow.
So: Do. Discover. Dream. And build a system that works for your actual life—not just your to-do list.
Author's Note: I also recorded a video on this with a few anecdotes and visuals. You can view it here: Rethinking Productivity: Tools and Mindsets That Actually Work.

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.