Thoughts

Welcome to The Care and Feeding of Meat Computers

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.

Who this talk is for? You.

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.  

Being you is a good thing to be.

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:  

1. some people just “have it” and are naturally good team players while there are others who are destined to never expand beyond their personal hangups.  

2. people with only hard skills and no soft skills are the only ones who make good business people and leaders.  

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?”

Video Chapters

• Soft Skills are Hard It’s ok to admit that soft skills are harder to you than hard skills. It’s not ok to never develop them further. Know your limits. And then dare to go further.  

• Nuance rules over Rules Life is complicated. You don’t need a list of rules to know what right looks like. What is the heart of the laws you’ve been given? Mindlessly following rules will rarely get you the results you dream of.  

• People over Tech Services work is rarely about the technical part and more about being curious and care-full about the people in our care!

• People over Stack Success comes from bringing your entire self to the table. No two people, no two MSPs are alike.

• People are Puzzles worth solving How do we, as technical people who love to solve puzzles, look as humans as solvable puzzles instead of pain points?

• People are Tech It’s not that humans are not like computers, it’s perhaps that they are too much like them.

Additional Resources and Recommended Reading

To deepen the concepts discussed in this series, here are several resources for further exploration:

Terms and Concepts

• MSP (Managed Service Provider) - Companies that remotely manage a customer’s IT infrastructure and systems

• Sisyphean - A task that feels endless and difficult, based on the Greek myth of Sisyphus, who had to roll a boulder up a hill forever

• Hard skills - Skills that involve specific knowledge or abilities, often technical, that can be measured or certified

• Soft skills - Personal skills like communication, empathy, and teamwork that help you work well with others

• Imposter syndrome - A feeling that you’re not as capable or skilled as others believe, even if you are

• Snake-oil - Something that is falsely advertised or exaggerated, originally referring to fake medicine

• Social power dynamic - How power and influence are distributed in social interactions or society

• Human-Centered Design - An approach to creating products that considers people’s needs, wants, and limitations.

• Human-Computer Interaction - The study of how people interact with computers and design technology that is easy and enjoyable to use.

• Emotional Intelligence (EQ) - The ability to recognize, understand, and manage emotions in yourself and others.

Books and Research

• Emotional Intelligence ‍
  • How to Improve Your Emotional Intelligence - Professional & Executive Development | Harvard DCE

• Human Centered Design ‍
  • What Is Human-Centered Design? | HBS Online  ‍
  • Full article: Knowledge is not everything

• Giftedness
  • The Renzulli Model: Three-Ring Conception of Giftedness | Renzulli Center for Creativity, Gifted Education, and Talent Development
  • Giftedness + ADHD + Autism - Tending Paths

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:

1. Favorite Tech: What is your favorite piece of tech? What is the best device or tool you’ve used or owned? Why is it your favorite? How much time did you spend configuring its settings and developing your own abilities to use it?  

2. Self-Assessment: Which soft skills come naturally to you, and which feel more challenging to develop? How do these impact your day-to-day work with clients or teammates?

3. Curiosity as a Tool: Have there been times when a “difficult” user or teammate surprised you with their insights or perspective? How might approaching people with curiosity change your interactions?

4. Rule Reflection: Are there any industry “rules” you follow that don’t serve you or your team well? Where did they come from? How can you find the “why” behind those rules and adapt them to fit your context? If there isn’t a good “why”...why are you still doing it?  

5. Growth Areas: What soft skill do you most want to develop? Consider using the resources linked above as a starting point to dive deeper into that area.

That’s it for Episode 1! Tune in for our next Episode: The most expensive piece of technology you’ll ever see.  

‍

Have you implemented unique colors for your Ticket Statuses in HaloPSA?  

Coloring these Statuses adds a great Quality of Life to your Agents working tickets. Often, it is treated as a nice-to-have or “let’s just make it look pretty,” which are fine if it works for you. However, we invite you to imagine instead with us: what if you could leverage symbolic colors that guide an Agent through your defined ticket process. What if you could implement that in a reasonable way?

So, to help lessen that decision fatigue for you since we know you’re busy customizing every other setting in HaloPSA as well, here is the framework that Rising Tide uses to approach customizing these settings to help you quickly and sensibly label your Ticket Statuses. In a future article, we’ll tackle Ticket Action color codes; however, the concepts will generally remain the same.  

Laying out the Ticket Status Colors Framework

Before we jump into coloring statuses, let’s start by defining a ticket’s lifecycle according to how your Agents need to allocate their attention to those tickets, whether that is dictated by standard professionalism or ensuring SLAs are kept. For the sake of this conversation, we are going to address these ticket attention phases with the segments: Normal Attention, Elevated Attention, or Inert Attention.

Normal Attention

Ideally, your Agents receive a ticket and all things are “Go,” they have everything they need to start working, and then Close the ticket when they've successfully completed the task and can rest on their laurels (or move on to the next ticket!).

We recommend all Normal Attention tickets to be assigned “cool colors” like greens, blues, and purples. (And not cool because we think they’re rad, cool as opposed to warm colors, more information here on color theory) Statuses like New and In Progress generally belong here. We have the ticket, everything is going as planned. What a perfect, serene world. Peaceful, isn’t it?  

Unfortunately, that’s not the reality in most of our businesses! What happens when tickets require extra attention or action to ensure their timely completion?

Elevated Attention

‍Here in Elevated Attention is where we see statuses like Escalated, Pending Approval, or Reopened: tickets that we need to be actively thinking about and revisiting, especially ones that are keeping our SLA clock running. To inspire action and increase visibility, we’re using warm, fiery colors like Orange, Red, and Yellow.

What if there is a ticket where we cannot take immediate action, or it doesn’t warrant it? That’s our last category: Inert Attention.  

Inert Attention

‍There will be times when our tickets are active but there is literally nothing we can do but wait. The SLA clock isn’t running, so we don’t need to worry about taking action on these just yet: statuses like Waiting on Client or Waiting on Vendor. We recommend using greys to signify these statuses’ inactive character.  

In general, we recommend you set up HaloPSA to do most of the status setting and remembering to move tasks in and out of statuses, especially Inert-type statuses. Specifically, when setting up these Inert Attention statuses in HaloPSA, be sure to build those Ticket Statuses, Ticket Type Settings, and your related Workflows so when a ticket enters or exits an Inert status, it automatically puts the ticket on or removes it from SLA hold. You can see examples of these settings in the screen captures below.

Some examples of this recommendation in action could be:

• Setting a Waiting on Client ticket to Attention Required when a customer replies to an email
• Setting a Waiting on Vendor ticket to Attention Required when a Supplier updates
• Setting a ticket to Scheduled upon creating an Appointment (Ticket Type Settings: Status after user appointment booking (resource booking), or Status after Agent creates appointment)
• Automatically setting Waiting on Client tickets to Closed after a certain number of hours with no reply according to SLA rules you set.

Ticket Status Colors Framework in Action

With all of these ideas in mind, we suggest as you approach customizing each ticket status, you ask:  

What type of Attention do I expect of my team at this status: Normal, Elevated, or Inert?

When you have that answer, choose a color from the suggested family. Remember that color for other statuses you may have for other Ticket Types so it stays consistent regardless of what Area your Agent is operating from!

Here are some examples for what we specifically recommend to Rising Tide Customers. You will likely not need all of them, depending on your MSP’s needs:  

Normal Attention

• Brand New/Assigned (Waiting on You): Green — Ticket is newly created and waiting for initial action. Green indicates readiness to start and clear action needed.

• Claimed/Work in Progress: Blue — Ticket is actively being addressed towards resolution. Blue symbolizes confidence in ongoing work and progress.  
  • We’d be remiss if we didn’t specifically call out that at Rising Tide we recommend that your Agents should not be "Claiming" tickets until they're ready to work on them.  

• Closed: Black — The ticket has been fully resolved and all necessary actions are completed. Black signifies completion and closure of the ticket.

‍Elevated Attention

• Pending Approval: Yellow — Awaiting authorization or approval to proceed. Yellow is high-visibility and unique to call attention to follow up that may be necessary.  

• Escalated: Orange — Moved to a higher level of support due to complexity or urgency. Orange highlights urgency and attention required.

• Customer Updated/Vendor Updated/Approver Updated: Orange— Orange is used to indicate recent release from a paused status like Waiting on Customer or Waiting on Vendor and subsequent re-instating of the current SLA timer, if applicable.  

• Attention Required: Orange — Elevated attention needed following removal from an SLA hold.  

• Reopened: Red — Previously closed/resolved ticket is active again due to additional issues or dissatisfaction. Red indicates a critical reactivation that needs immediate reassessment.

Inert Attention

• Waiting on Client: Grey — Progress on the ticket is paused because it requires input or action from the client. Grey suggests inactivity from the MSP’s side, waiting on external action.  

• Waiting on Vendor/Waiting on Parts: Grey — Progress on the ticket is halted while waiting for action or information from an external vendor. Similar to waiting on client but specific to external vendors.

• Scheduled: Purple — Scheduled could also technically be included in the Normal category, hence the cool purple. Denotes a paused status where work is planned, but no active work is required.  

• Resolved: Teal — Similar to Scheduled, Resolved straddles the Normal category as well. The issue within the ticket has been addressed, awaiting final closure or verification from the requester. Teal is a calm yet upbeat color indicating resolution but awaiting final closure.

As with most rules, there are going to be times when items cross between phases, or you may operate differently and not define a ticket status the same way we did here.

Maybe you have some color-blind technicians on staff and decide to use completely different colors completely or none at all. (If you do want to create a color-blind friendly palette, here’s a great resource.)  

Maybe you want to choose different values (light or dark) within a certain family than what Halo provides.

Good! Break our rules. They're just here to help you decide what you do or don't actually want.

Our main recommendation is that you use your best judgement on what is right for your team and just be consistent which sometimes means keeping it simple. And let us know what you ended up doing, you may help someone else. Happy customizing!

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.

‍

1. Keep an open mind when approaching the problem and avoid falling back into the "End User" mindset
2. Read and explore everything on the screen! Pay attention to what's being done and what its telling you
3. Understand the problem at least as well as the person asking you for help
4. Be intentional in your troubleshooting, closing your eyes and throwing darts at the wall is not helpful
5. Question everything you think you know and are being told
6. 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

‍

“Should my business be going to Cloud?”

This is one of the most popular questions that comes up in my conversations with clients, and like every other question I get, I like to answer it with “It depends”.

Before we can address this, we need to address the ongoing struggle between IT Professionals and Marketing Professionals. This was cleverly outlined in the classic Project Management meme

We won’t get too far into the specifics of this as Marketing can be a post all by itself, but suffice to say, the…let’s call it exuberance to sell something new, tends to make for overly aggressive messaging targeting the Stakeholders which does not generate tingly-friendly feelings on the people who actually have to implement, support, or answer questions about the technical specifics. This is true no matter if the “Expert” person is at your company or the company the marketing person is sitting at. If you need a further demonstration of what this looks like you can watch the skit on YouTube called “The Expert” which should give you an idea of what frame of mind to approach this question with

Keeping this in mind we need to immediately increase our level of skepticism when we hear about Cloud Computing (or really any new technology).

Let’s switch tracks for a moment. One of the things I always talk about is how there’s at least two sides to everything. Literally you can take a specific item, scenario, concept, etc. examine it and you’ll see two or more sides that reflect or are directly opposite to each other. In business finances for example we have Operating costs and Cost of Goods Sold (COGS). Traditionally Operating costs were made up of things like Rent for the office, Utilities, supplies and things like that. Supplies would include the cost of equipment (such as computers) Utilities would include cost of the internet and so on. COGS would be made up of how much money the business would need to spend, in order to provide the service that they offer. This is essentially two sides to the same thing (money being spent), but you track them separately because they help you break down the cost of running the business vs the cost of providing services.

In other words, Operating Expenses can be broken down to the point where you would assign a Per Dollar amount for each Employee that you have, and COGS would be broken down and assigned a Per Dollar amount for each Customer

Now let’s get back to the point of this. Cloud, like everything else, has 2 or more (way more actually) sides. There’s Infrastructure as a Service offerings, Platform as a Service, Software as a Service, and so on and so forth and all of these items get mixed up and placed into the “Cloud” category. If you dig into what Cloud actually is, you’ll find that it’s just…rented computers. Really. If you’re skeptical, you can read more on this here from one of the bigger software platforms on their reasons why they’re leaving the cloud.

The questions we’d want to answer so that we can determine if you should be moving to the cloud are as follows.

Would you be moving your Operating Expenses to the cloud or your COGS. Specifically, are you providing an online service to your clients that requires you to rapidly scale up if you were to grow, or that allows you to measure out the cost of running in the cloud against the number of users you’re servicing?

Running in almost any cloud has pricing that is broken down to the minute, generally speaking. This is one of the big things marketing likes to tout “Scale up or down as needed, so it’s very cost effective”. Cost effective compared to running them 24/7 sure, but not cost effective compared to buying hardware. Marketing is selling you on the idea that if you needed to turn down services, you can do rapidly and save money with it off, but if you never need to turn down services, and your scaling doesn’t happen rapidly, then you’re actually spending way more over the same period of time of hardware life. Up to 4 or 5 times the amount potentially.

Do you have a need either from a compliance standard or your own security policy for enhanced security, physical auditing, a requirement to be highly available or a guaranteed uptime of 4 or more 9s (99.99%)?

Here is where it starts making sense to consider, although the question of finding a datacenter that will rent you hardware or allow you to place hardware vs running in something like Google Cloud, Azure, or AWS is still debatable. In the end the level of redundancies that exist in the cloud or datacenter are harder to build (read, more costly) than using an infrastructure that is already built and essentially being shared. This isn’t a new phenomenon, if you’ve read my article on the MSP Business Fallacy, or even just paid attention in the world the idea of pooling resources to save on costs is a well-established and very successful pattern. This is something that can range on a spectrum from sharing power costs, to sharing full on hardware and running your services on segregated containerized workloads.

Are you concerned about control of your data. Specifically, does it matter to you if your data is physically on equipment that you solely own and control, or is your business okay with the data being placed onto equipment owned and controlled by a trusted Third Party

Data sovereignty is an important part of the equation, even if you do trust it to a third party, the question of which region and where it is physically located is still an issue. In the end the agreements you sign with vendors and clients state that the data you hold for them is your responsibility to protect and keep safe and you do not have the right to assign that responsibility to anyone else. These are all concerns that should be evaluated and addressed in your assessment of moving to cloud.

In the end there’s no real good right answer, as most of these questions are ones you’ll need to decide for your business. I’ve outlined a table below to help with the decision matrix, but it is still only just a suggestion.

As a business owner, it’s important to have a good understanding of your business goals, and its operations. There are several key questions that every business owner should be able to answer in order to ensure the success and growth of their company.

1. What is your why? If you know me personally, by now you know I am a follower of Simon Sinek. Simon’s consistent chasing the why is something I’ve come to admire and strive for. The reason you get out of bed every day, the reason you go to work, if you know it, it’ll sustain you and become the building block for your Company Culture and Core Values.
2. Who are your customers? It’s important to have a clear understanding of who your target customers are and what their needs and preferences are. This will help you tailor your products and services to meet their specific requirements and create a more personalized customer experience. More importantly, staying in touch with them will help you adjust to their changing needs, so you stay relevant.
3. What is your revenue model? How do you generate revenue and make a profit? This could be through the sale of products or services, subscriptions, advertising, or a combination of these methods. Understanding your revenue model will help you identify growth opportunities and make strategic business decisions.
4. What are your expenses? It’s crucial to have a good understanding of your business’s expenses, including fixed costs like rent and salaries, as well as variable costs like materials and marketing expenses. This will help you manage your cash flow and make sure your business is profitable.

As a business owner, it’s essential to have a strong and focused culture and a set of core values that guide your company’s actions and decisions.

Business culture refers to the values, beliefs, and behaviors that make up a company’s identity. It’s the “personality” of the organization and the way it operates. A strong culture is one that aligns with the company’s goals and mission, and that supports the growth and success of the business.

These values should reflect your company’s mission and goals and should be integrated into every aspect of your business operations. Once your values are established, it’s important to communicate them to your team in to help make sure they are integrated into the company’s operations and decision-making processes. While all the other points are critical for owning and operating a business, they are also all areas that can be delegated (and usually are for larger businesses). The first point, regarding company culture is something that can only come from the top.

There are several reasons why this can have a major impact on the success and growth of your business.

First, a strong and focused culture can help attract and retain top talent. Employees who share your company’s values and beliefs are more likely to be motivated and engaged in their work and are more likely to stay with the company long-term. This can improve morale and productivity and can help drive the success of your business. This can include offering opportunities for professional development and growth, providing a healthy and supportive work environment, and recognizing and rewarding outstanding performance.

Second, a consistent and focused culture can improve customer satisfaction. Customers want to do business with companies that share their values and beliefs. Simon Sinek uses the one wearing the Red Hat as an example. People gravitate to those they connect with and by having a clearly defined culture you can articulate it allows others to see what you stand for and more easily connect with you, which can help increase loyalty and repeat business, as well as establish a greater level of trust.

Third, a focused culture and set of core values can provide guidance and direction for your employees. By having a clear set of values that everyone understands and adheres to, you can create a cohesive and consistent brand and customer experience. This can help improve collaboration and communication within your team and can make it easier to make strategic business decisions.

Finally, having that strong culture and core values established gives you guiding principles when it comes time to pick which companies you start a vendor/client relationship with, being able to articulate what you stand for allows you to recognize easily those that align with you or those that do not. You can quickly identify business practices and test them against your core value. “Is this company being honest”, “Do they care about customer experience” are questions you can easily answer based on the start of the relationship and your interaction throughout.

While having a unique selling proposition (USP) is often considered an essential part of a successful business, there is some debate over whether it is still relevant in today’s competitive market. With so many businesses offering similar products and services, it can be difficult to differentiate yourself and stand out from the crowd.

Additionally, many prospects may not have the time or inclination to thoroughly research and compare different vendors before making a purchasing decision. They may rely on marketing messages and other external factors to make their decision, rather than taking the time to evaluate the validity of a company’s USP.

In some cases, a company’s USP may be seen as simply a marketing tactic, rather than a genuine differentiator. This can lead prospects to view all USPs as equally valid, or to disregard them altogether.

Overall, while having a unique selling proposition is still important, it may not be as effective as it once was as a marketing strategy in a crowded and competitive market. It’s important for businesses to carefully consider their USP and whether it is a genuine differentiator, or if it is simply a generic marketing message, and in reality, aligning this with your Culture will help give you a true differentiator.

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:

1. Practice asking questions: Critical thinking involves questioning assumptions and looking at situations from different perspectives. Practice asking questions about the information you encounter, such as “Why is this true?” or “What evidence supports this claim?”. Feel free to start with this one right here 😉
2. Seek out diverse perspectives: To think critically, it’s important to consider multiple viewpoints and perspectives. Seek out diverse sources of information and listen to others with different backgrounds and experiences.
3. Evaluate sources of information: In today’s information-rich world, it’s important to be able to evaluate the credibility and reliability of sources. Consider factors such as the author’s expertise and credentials, the date and source of the information, and any potential biases or conflicts of interest.
4. Take your time: Critical thinking takes time and effort. Don’t be afraid to take a step back and reflect on a situation before making a decision. Consider the potential consequences of your actions and be open to changing your mind based on new information.
5. Practice regularly: Like any skill, critical thinking improves with practice. Take opportunities to apply critical thinking in your everyday life, and in some cases, you’ll find that you’ve already been doing it subconsciously!

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.

The butterfly effect is a term used to reference a scenario where, if you were to go back in time 1000 years and step on a butterfly and then return to your current time, you would find that everything has been changed. Potentially even you would no longer exist. This is explained as being caused by the fact that everything in the world is connected (as being part of the same ecosystem) and therefore given enough time the effects of a tiny butterfly being squashed can exponentially grow into an event where the Germans won World War II, or your parents never met.

In a world today where we are too busy to look beyond the face value, the lesson is pretty clear. If you go back in time, make sure you don’t step on any butterflies. If we were to stop and look beyond the face value, the lesson hits far closer to home. Scientists use this to explain that even a small change in a complex system can have a huge impact, but even they distill the true lesson down to its practical use for themselves.

Have you ever watched a Wave roll through the stadium audience, proud to join the hundreds raising their hands but jealous you weren’t the one who started it? What did the other person have that you don’t? Why couldn’t you be the source of this impressive movement visible throughout the entire stadium? The answer is honestly, nothing. Just the courage to go first, and be the leader, influencing others around you and creating an impact that spreads.

You have been created in order that you might make a difference. You have within you the power to change the world. – Andy Anderson

The Rising Tide Consulting Group is movement looking to start the waves, creating the tide, that will subsequently create larger waves, and larger waves, eventually rising higher and elevating everyone within the ecosystem. Let’s go back to the Wave in the stadium, can you imagine if the first person lifted their hands to create the Wave and the person next to them watched, acknowledged it was cool, and did nothing? The only reason why the Wave works is because the second person who follows, then the third, and the fourth and so-on. This is why at Rising Tide we are hyper-focused not on your business, but on your people. If we do your work for you, there is no impact, and we are left deciding if we should keep raising our hands to make up for the effort of those who aren’t joining or give up! If we can influence you doing your work, we can be the start of a massive wave that will spread not only throughout your entire business, but to your clients, and your vendors, raising the level of partnerships and quality of service being delivered to you, and by you.

The Rising Tide LevelUp Challenge is our ‘Audience in the Stadium Wave’. A movement started by our mentor Mendy Green on LinkedIn, where you take three stories, or analogies, and you pull out a lesson learned from each one (similar to how we did it with The Butterfly Effect mentioned above). After your three lessons you call out three new people to partake in the challenge and post their own. The lessons can be repeated, but the analogies or stories must be different.

In every situation, scenario, or story, there’s always a lesson to be learned. The scientists knew that when they framed the Butterfly Effect to teach their lesson, but each person will look at these stories and lessons through a colored lens filtered for their specific use case! It’s up to each individual as they hear these to take a lesson that relates to them. In fact, it is with Elizabeth Copeland’s lesson from the challenge (“Sometimes you need to stop and take in the view”) that we can examine analogies and situations and pull out a lesson from each one relevant to us to help us grow; the difference between taking something at face value or looking for that deeper meaning.

You can find her lesson and more by looking for the tags #RisingTideChallenge or #RisingTide on LinkedIn.

In any business where you’re not billing Time and Materials, the amount of time you spend on a project directly correlates to how profitable you are. In an MSP, this applies even more. MSP Businesses were designed years ahead of their time, bringing into practice concepts such as recurring revenue, outsourcing, efficient resources, and more; before people even realized the value. It’s the reason that today the MSP Businesses are blowing up with everyone you meet starting their own. Unfortunately, there’s a complex side to the framework of an MSP that is very often overlooked, especially by those just starting out.

Let’s discuss how the MSP business model is built. MSPs pitch to their prospective clients that they can provide the same level (or often times better) IT Services to their organization than they themselves can find if they go with someone internally. They ask for less money, and offer a bigger team with greater experience. These same MSPs then have to turn around and hire the same people that would have been hired directly, and not just one, but two or three or more depending on the size of the MSP.

MSPs have to pay the same salary with a smaller budget. How can these numbers possibly work?

This is where efficient resources come in; an MSP needs to stack multiple clients reusing the same resources for each client so that together all the clients combined pay enough money for the MSP to pay the technicians salary and make a profit. The income also needs to cover all base expenses of the MSP which includes infrastructure such as an RMM, PSA, Email, Phones, over-night team for emergencies and so on.

With an internal IT resource, that resource would be solely focused on the business they were working for and getting paid a full salary of say $52k/year, now the same resource at an MSP is getting paid $52k/year and needs to  stay on top of not one company IT needs, but actually 3 or 4 (or more depending on the contract size of each). This kind of expectation is unreasonable and when maintained results in high-stress work environments and eventual burn out for the technician. The saying “trial by fire” is very applicable to the technicians who work at an MSP. They are under constant barrage of tickets and stress, jumping from company to company each ticket wildly different from the next. This makes them unusually skilled and also rapidly exposes them to a wide range of experience they may not have received working for just one company. A good MSP technician of the lowest tier can easily go head to head in ability (if not knowledge) to a mid-tier internal IT resource.

Now keep in mind that when MSPs started we were a new phenomenon. There was no standard to follow, no existing business to copy, except for the existing internal IT department within a Company. We didn’t know what kind of pay structure was fair to offer a Tier 1 or Tier 2 technician because there was no “average pay” metric. The only thing we did know is that we are building a business with a stress on smaller dollar amounts per client, and more total clients. This means what we paid our technicians had to be less too, or that we keep the MSP as lean as possible with only the amount of technicians truly needed. Following the 80/20 rule we determined that 80% of the time with our clients running smoothly we would be fine and only 20% of the time when some kind “perfect storm” would occur we would need to motivate our technicians to put in more effort (or what was generally called “figure something out”).

What’s being described is not a sustainable long term plan. Simon Sinek likes to stress that business is an Infinite Game and that those who are not playing by those rules are doomed to failure eventually. The only way to stay in the game is by having resources, and the will to keep playing. We’ve already established that MSPs do not have the same pockets as a normal business, not without drastically imposing upon “will”, our employees, making them work in stressful environments and constantly being battered by the next broken issue.

The fix for this is easy, and its an iteration of what we already started. Efficient use of resources. Efficiency can help us spend less time per ticket, less time per client, and improve our technicians stress in the environment. There are two side to the efficient use of resources, one of which we already started (Sharing resources among companies) but the other is often overlooked “Work load management”. If we can make our work load efficient we can easily improve upon all the issues we just brought up. Here are some ideas that can be used to help facilitate the efficient workload.

Efficient resources is way more than just sharing resources. Making your workload efficient is just as important. Remember how profitable you are directly correlates to how efficient you can be

• Proactively addressing age of client equipment
• Proactively addressing ticket trends over time to help improve underlying issues
• End User technology training for better understanding of the tools they use
• Breaking Client’s business vertical into separate teams to allow for familiarity of Line of Business applications and setup
• Building an MSP supported technical standard as your “stack” to ensure familiarity with technical infrastructure
• Establishing formalized business processes for your MSP Teams so they know where to find information and how to proceed
• Building an Automation First environment allowing you to offload work from your team to your technology decreasing the amount of time spent on tickets.

Remember, in the MSP business time isn’t a loss of potential profit, its actual profit lost as your contracted rate is the same every month. Automation and bulk actions are extremely important as the less time you spend doing something the more your Per Hour amount goes up.

Have you implemented unique colors for your Ticket Statuses in HaloPSA?  

Coloring these Statuses adds a great Quality of Life to your Agents working tickets. Often, it is treated as a nice-to-have or “let’s just make it look pretty,” which are fine if it works for you. However, we invite you to imagine instead with us: what if you could leverage symbolic colors that guide an Agent through your defined ticket process. What if you could implement that in a reasonable way?

So, to help lessen that decision fatigue for you since we know you’re busy customizing every other setting in HaloPSA as well, here is the framework that Rising Tide uses to approach customizing these settings to help you quickly and sensibly label your Ticket Statuses. In a future article, we’ll tackle Ticket Action color codes; however, the concepts will generally remain the same.  

Laying out the Ticket Status Colors Framework

Before we jump into coloring statuses, let’s start by defining a ticket’s lifecycle according to how your Agents need to allocate their attention to those tickets, whether that is dictated by standard professionalism or ensuring SLAs are kept. For the sake of this conversation, we are going to address these ticket attention phases with the segments: Normal Attention, Elevated Attention, or Inert Attention.

Normal Attention

Ideally, your Agents receive a ticket and all things are “Go,” they have everything they need to start working, and then Close the ticket when they've successfully completed the task and can rest on their laurels (or move on to the next ticket!).

We recommend all Normal Attention tickets to be assigned “cool colors” like greens, blues, and purples. (And not cool because we think they’re rad, cool as opposed to warm colors, more information here on color theory) Statuses like New and In Progress generally belong here. We have the ticket, everything is going as planned. What a perfect, serene world. Peaceful, isn’t it?  

Unfortunately, that’s not the reality in most of our businesses! What happens when tickets require extra attention or action to ensure their timely completion?

Elevated Attention

‍Here in Elevated Attention is where we see statuses like Escalated, Pending Approval, or Reopened: tickets that we need to be actively thinking about and revisiting, especially ones that are keeping our SLA clock running. To inspire action and increase visibility, we’re using warm, fiery colors like Orange, Red, and Yellow.

What if there is a ticket where we cannot take immediate action, or it doesn’t warrant it? That’s our last category: Inert Attention.  

Inert Attention

‍There will be times when our tickets are active but there is literally nothing we can do but wait. The SLA clock isn’t running, so we don’t need to worry about taking action on these just yet: statuses like Waiting on Client or Waiting on Vendor. We recommend using greys to signify these statuses’ inactive character.  

In general, we recommend you set up HaloPSA to do most of the status setting and remembering to move tasks in and out of statuses, especially Inert-type statuses. Specifically, when setting up these Inert Attention statuses in HaloPSA, be sure to build those Ticket Statuses, Ticket Type Settings, and your related Workflows so when a ticket enters or exits an Inert status, it automatically puts the ticket on or removes it from SLA hold. You can see examples of these settings in the screen captures below.

Some examples of this recommendation in action could be:

• Setting a Waiting on Client ticket to Attention Required when a customer replies to an email
• Setting a Waiting on Vendor ticket to Attention Required when a Supplier updates
• Setting a ticket to Scheduled upon creating an Appointment (Ticket Type Settings: Status after user appointment booking (resource booking), or Status after Agent creates appointment)
• Automatically setting Waiting on Client tickets to Closed after a certain number of hours with no reply according to SLA rules you set.

Ticket Status Colors Framework in Action

With all of these ideas in mind, we suggest as you approach customizing each ticket status, you ask:  

What type of Attention do I expect of my team at this status: Normal, Elevated, or Inert?

When you have that answer, choose a color from the suggested family. Remember that color for other statuses you may have for other Ticket Types so it stays consistent regardless of what Area your Agent is operating from!

Here are some examples for what we specifically recommend to Rising Tide Customers. You will likely not need all of them, depending on your MSP’s needs:  

Normal Attention

• Brand New/Assigned (Waiting on You): Green — Ticket is newly created and waiting for initial action. Green indicates readiness to start and clear action needed.

• Claimed/Work in Progress: Blue — Ticket is actively being addressed towards resolution. Blue symbolizes confidence in ongoing work and progress.  
  • We’d be remiss if we didn’t specifically call out that at Rising Tide we recommend that your Agents should not be "Claiming" tickets until they're ready to work on them.  

• Closed: Black — The ticket has been fully resolved and all necessary actions are completed. Black signifies completion and closure of the ticket.

‍Elevated Attention

• Pending Approval: Yellow — Awaiting authorization or approval to proceed. Yellow is high-visibility and unique to call attention to follow up that may be necessary.  

• Escalated: Orange — Moved to a higher level of support due to complexity or urgency. Orange highlights urgency and attention required.

• Customer Updated/Vendor Updated/Approver Updated: Orange— Orange is used to indicate recent release from a paused status like Waiting on Customer or Waiting on Vendor and subsequent re-instating of the current SLA timer, if applicable.  

• Attention Required: Orange — Elevated attention needed following removal from an SLA hold.  

• Reopened: Red — Previously closed/resolved ticket is active again due to additional issues or dissatisfaction. Red indicates a critical reactivation that needs immediate reassessment.

Inert Attention

• Waiting on Client: Grey — Progress on the ticket is paused because it requires input or action from the client. Grey suggests inactivity from the MSP’s side, waiting on external action.  

• Waiting on Vendor/Waiting on Parts: Grey — Progress on the ticket is halted while waiting for action or information from an external vendor. Similar to waiting on client but specific to external vendors.

• Scheduled: Purple — Scheduled could also technically be included in the Normal category, hence the cool purple. Denotes a paused status where work is planned, but no active work is required.  

• Resolved: Teal — Similar to Scheduled, Resolved straddles the Normal category as well. The issue within the ticket has been addressed, awaiting final closure or verification from the requester. Teal is a calm yet upbeat color indicating resolution but awaiting final closure.

As with most rules, there are going to be times when items cross between phases, or you may operate differently and not define a ticket status the same way we did here.

Maybe you have some color-blind technicians on staff and decide to use completely different colors completely or none at all. (If you do want to create a color-blind friendly palette, here’s a great resource.)  

Maybe you want to choose different values (light or dark) within a certain family than what Halo provides.

Good! Break our rules. They're just here to help you decide what you do or don't actually want.

Our main recommendation is that you use your best judgement on what is right for your team and just be consistent which sometimes means keeping it simple. And let us know what you ended up doing, you may help someone else. Happy customizing!

In any business where you’re not billing Time and Materials, the amount of time you spend on a project directly correlates to how profitable you are. In an MSP, this applies even more. MSP Businesses were designed years ahead of their time, bringing into practice concepts such as recurring revenue, outsourcing, efficient resources, and more; before people even realized the value. It’s the reason that today the MSP Businesses are blowing up with everyone you meet starting their own. Unfortunately, there’s a complex side to the framework of an MSP that is very often overlooked, especially by those just starting out.

Let’s discuss how the MSP business model is built. MSPs pitch to their prospective clients that they can provide the same level (or often times better) IT Services to their organization than they themselves can find if they go with someone internally. They ask for less money, and offer a bigger team with greater experience. These same MSPs then have to turn around and hire the same people that would have been hired directly, and not just one, but two or three or more depending on the size of the MSP.

MSPs have to pay the same salary with a smaller budget. How can these numbers possibly work?

This is where efficient resources come in; an MSP needs to stack multiple clients reusing the same resources for each client so that together all the clients combined pay enough money for the MSP to pay the technicians salary and make a profit. The income also needs to cover all base expenses of the MSP which includes infrastructure such as an RMM, PSA, Email, Phones, over-night team for emergencies and so on.

With an internal IT resource, that resource would be solely focused on the business they were working for and getting paid a full salary of say $52k/year, now the same resource at an MSP is getting paid $52k/year and needs to  stay on top of not one company IT needs, but actually 3 or 4 (or more depending on the contract size of each). This kind of expectation is unreasonable and when maintained results in high-stress work environments and eventual burn out for the technician. The saying “trial by fire” is very applicable to the technicians who work at an MSP. They are under constant barrage of tickets and stress, jumping from company to company each ticket wildly different from the next. This makes them unusually skilled and also rapidly exposes them to a wide range of experience they may not have received working for just one company. A good MSP technician of the lowest tier can easily go head to head in ability (if not knowledge) to a mid-tier internal IT resource.

Now keep in mind that when MSPs started we were a new phenomenon. There was no standard to follow, no existing business to copy, except for the existing internal IT department within a Company. We didn’t know what kind of pay structure was fair to offer a Tier 1 or Tier 2 technician because there was no “average pay” metric. The only thing we did know is that we are building a business with a stress on smaller dollar amounts per client, and more total clients. This means what we paid our technicians had to be less too, or that we keep the MSP as lean as possible with only the amount of technicians truly needed. Following the 80/20 rule we determined that 80% of the time with our clients running smoothly we would be fine and only 20% of the time when some kind “perfect storm” would occur we would need to motivate our technicians to put in more effort (or what was generally called “figure something out”).

What’s being described is not a sustainable long term plan. Simon Sinek likes to stress that business is an Infinite Game and that those who are not playing by those rules are doomed to failure eventually. The only way to stay in the game is by having resources, and the will to keep playing. We’ve already established that MSPs do not have the same pockets as a normal business, not without drastically imposing upon “will”, our employees, making them work in stressful environments and constantly being battered by the next broken issue.

The fix for this is easy, and its an iteration of what we already started. Efficient use of resources. Efficiency can help us spend less time per ticket, less time per client, and improve our technicians stress in the environment. There are two side to the efficient use of resources, one of which we already started (Sharing resources among companies) but the other is often overlooked “Work load management”. If we can make our work load efficient we can easily improve upon all the issues we just brought up. Here are some ideas that can be used to help facilitate the efficient workload.

Efficient resources is way more than just sharing resources. Making your workload efficient is just as important. Remember how profitable you are directly correlates to how efficient you can be

• Proactively addressing age of client equipment
• Proactively addressing ticket trends over time to help improve underlying issues
• End User technology training for better understanding of the tools they use
• Breaking Client’s business vertical into separate teams to allow for familiarity of Line of Business applications and setup
• Building an MSP supported technical standard as your “stack” to ensure familiarity with technical infrastructure
• Establishing formalized business processes for your MSP Teams so they know where to find information and how to proceed
• Building an Automation First environment allowing you to offload work from your team to your technology decreasing the amount of time spent on tickets.

Remember, in the MSP business time isn’t a loss of potential profit, its actual profit lost as your contracted rate is the same every month. Automation and bulk actions are extremely important as the less time you spend doing something the more your Per Hour amount goes up.

As a business owner, it’s important to have a good understanding of your business goals, and its operations. There are several key questions that every business owner should be able to answer in order to ensure the success and growth of their company.

1. What is your why? If you know me personally, by now you know I am a follower of Simon Sinek. Simon’s consistent chasing the why is something I’ve come to admire and strive for. The reason you get out of bed every day, the reason you go to work, if you know it, it’ll sustain you and become the building block for your Company Culture and Core Values.
2. Who are your customers? It’s important to have a clear understanding of who your target customers are and what their needs and preferences are. This will help you tailor your products and services to meet their specific requirements and create a more personalized customer experience. More importantly, staying in touch with them will help you adjust to their changing needs, so you stay relevant.
3. What is your revenue model? How do you generate revenue and make a profit? This could be through the sale of products or services, subscriptions, advertising, or a combination of these methods. Understanding your revenue model will help you identify growth opportunities and make strategic business decisions.
4. What are your expenses? It’s crucial to have a good understanding of your business’s expenses, including fixed costs like rent and salaries, as well as variable costs like materials and marketing expenses. This will help you manage your cash flow and make sure your business is profitable.

As a business owner, it’s essential to have a strong and focused culture and a set of core values that guide your company’s actions and decisions.

Business culture refers to the values, beliefs, and behaviors that make up a company’s identity. It’s the “personality” of the organization and the way it operates. A strong culture is one that aligns with the company’s goals and mission, and that supports the growth and success of the business.

These values should reflect your company’s mission and goals and should be integrated into every aspect of your business operations. Once your values are established, it’s important to communicate them to your team in to help make sure they are integrated into the company’s operations and decision-making processes. While all the other points are critical for owning and operating a business, they are also all areas that can be delegated (and usually are for larger businesses). The first point, regarding company culture is something that can only come from the top.

There are several reasons why this can have a major impact on the success and growth of your business.

First, a strong and focused culture can help attract and retain top talent. Employees who share your company’s values and beliefs are more likely to be motivated and engaged in their work and are more likely to stay with the company long-term. This can improve morale and productivity and can help drive the success of your business. This can include offering opportunities for professional development and growth, providing a healthy and supportive work environment, and recognizing and rewarding outstanding performance.

Second, a consistent and focused culture can improve customer satisfaction. Customers want to do business with companies that share their values and beliefs. Simon Sinek uses the one wearing the Red Hat as an example. People gravitate to those they connect with and by having a clearly defined culture you can articulate it allows others to see what you stand for and more easily connect with you, which can help increase loyalty and repeat business, as well as establish a greater level of trust.

Third, a focused culture and set of core values can provide guidance and direction for your employees. By having a clear set of values that everyone understands and adheres to, you can create a cohesive and consistent brand and customer experience. This can help improve collaboration and communication within your team and can make it easier to make strategic business decisions.

Finally, having that strong culture and core values established gives you guiding principles when it comes time to pick which companies you start a vendor/client relationship with, being able to articulate what you stand for allows you to recognize easily those that align with you or those that do not. You can quickly identify business practices and test them against your core value. “Is this company being honest”, “Do they care about customer experience” are questions you can easily answer based on the start of the relationship and your interaction throughout.

While having a unique selling proposition (USP) is often considered an essential part of a successful business, there is some debate over whether it is still relevant in today’s competitive market. With so many businesses offering similar products and services, it can be difficult to differentiate yourself and stand out from the crowd.

Additionally, many prospects may not have the time or inclination to thoroughly research and compare different vendors before making a purchasing decision. They may rely on marketing messages and other external factors to make their decision, rather than taking the time to evaluate the validity of a company’s USP.

In some cases, a company’s USP may be seen as simply a marketing tactic, rather than a genuine differentiator. This can lead prospects to view all USPs as equally valid, or to disregard them altogether.

Overall, while having a unique selling proposition is still important, it may not be as effective as it once was as a marketing strategy in a crowded and competitive market. It’s important for businesses to carefully consider their USP and whether it is a genuine differentiator, or if it is simply a generic marketing message, and in reality, aligning this with your Culture will help give you a true differentiator.

“Should my business be going to Cloud?”

This is one of the most popular questions that comes up in my conversations with clients, and like every other question I get, I like to answer it with “It depends”.

Before we can address this, we need to address the ongoing struggle between IT Professionals and Marketing Professionals. This was cleverly outlined in the classic Project Management meme

We won’t get too far into the specifics of this as Marketing can be a post all by itself, but suffice to say, the…let’s call it exuberance to sell something new, tends to make for overly aggressive messaging targeting the Stakeholders which does not generate tingly-friendly feelings on the people who actually have to implement, support, or answer questions about the technical specifics. This is true no matter if the “Expert” person is at your company or the company the marketing person is sitting at. If you need a further demonstration of what this looks like you can watch the skit on YouTube called “The Expert” which should give you an idea of what frame of mind to approach this question with

Keeping this in mind we need to immediately increase our level of skepticism when we hear about Cloud Computing (or really any new technology).

Let’s switch tracks for a moment. One of the things I always talk about is how there’s at least two sides to everything. Literally you can take a specific item, scenario, concept, etc. examine it and you’ll see two or more sides that reflect or are directly opposite to each other. In business finances for example we have Operating costs and Cost of Goods Sold (COGS). Traditionally Operating costs were made up of things like Rent for the office, Utilities, supplies and things like that. Supplies would include the cost of equipment (such as computers) Utilities would include cost of the internet and so on. COGS would be made up of how much money the business would need to spend, in order to provide the service that they offer. This is essentially two sides to the same thing (money being spent), but you track them separately because they help you break down the cost of running the business vs the cost of providing services.

In other words, Operating Expenses can be broken down to the point where you would assign a Per Dollar amount for each Employee that you have, and COGS would be broken down and assigned a Per Dollar amount for each Customer

Now let’s get back to the point of this. Cloud, like everything else, has 2 or more (way more actually) sides. There’s Infrastructure as a Service offerings, Platform as a Service, Software as a Service, and so on and so forth and all of these items get mixed up and placed into the “Cloud” category. If you dig into what Cloud actually is, you’ll find that it’s just…rented computers. Really. If you’re skeptical, you can read more on this here from one of the bigger software platforms on their reasons why they’re leaving the cloud.

The questions we’d want to answer so that we can determine if you should be moving to the cloud are as follows.

Would you be moving your Operating Expenses to the cloud or your COGS. Specifically, are you providing an online service to your clients that requires you to rapidly scale up if you were to grow, or that allows you to measure out the cost of running in the cloud against the number of users you’re servicing?

Running in almost any cloud has pricing that is broken down to the minute, generally speaking. This is one of the big things marketing likes to tout “Scale up or down as needed, so it’s very cost effective”. Cost effective compared to running them 24/7 sure, but not cost effective compared to buying hardware. Marketing is selling you on the idea that if you needed to turn down services, you can do rapidly and save money with it off, but if you never need to turn down services, and your scaling doesn’t happen rapidly, then you’re actually spending way more over the same period of time of hardware life. Up to 4 or 5 times the amount potentially.

Do you have a need either from a compliance standard or your own security policy for enhanced security, physical auditing, a requirement to be highly available or a guaranteed uptime of 4 or more 9s (99.99%)?

Here is where it starts making sense to consider, although the question of finding a datacenter that will rent you hardware or allow you to place hardware vs running in something like Google Cloud, Azure, or AWS is still debatable. In the end the level of redundancies that exist in the cloud or datacenter are harder to build (read, more costly) than using an infrastructure that is already built and essentially being shared. This isn’t a new phenomenon, if you’ve read my article on the MSP Business Fallacy, or even just paid attention in the world the idea of pooling resources to save on costs is a well-established and very successful pattern. This is something that can range on a spectrum from sharing power costs, to sharing full on hardware and running your services on segregated containerized workloads.

Are you concerned about control of your data. Specifically, does it matter to you if your data is physically on equipment that you solely own and control, or is your business okay with the data being placed onto equipment owned and controlled by a trusted Third Party

Data sovereignty is an important part of the equation, even if you do trust it to a third party, the question of which region and where it is physically located is still an issue. In the end the agreements you sign with vendors and clients state that the data you hold for them is your responsibility to protect and keep safe and you do not have the right to assign that responsibility to anyone else. These are all concerns that should be evaluated and addressed in your assessment of moving to cloud.

In the end there’s no real good right answer, as most of these questions are ones you’ll need to decide for your business. I’ve outlined a table below to help with the decision matrix, but it is still only just a suggestion.

The butterfly effect is a term used to reference a scenario where, if you were to go back in time 1000 years and step on a butterfly and then return to your current time, you would find that everything has been changed. Potentially even you would no longer exist. This is explained as being caused by the fact that everything in the world is connected (as being part of the same ecosystem) and therefore given enough time the effects of a tiny butterfly being squashed can exponentially grow into an event where the Germans won World War II, or your parents never met.

In a world today where we are too busy to look beyond the face value, the lesson is pretty clear. If you go back in time, make sure you don’t step on any butterflies. If we were to stop and look beyond the face value, the lesson hits far closer to home. Scientists use this to explain that even a small change in a complex system can have a huge impact, but even they distill the true lesson down to its practical use for themselves.

Have you ever watched a Wave roll through the stadium audience, proud to join the hundreds raising their hands but jealous you weren’t the one who started it? What did the other person have that you don’t? Why couldn’t you be the source of this impressive movement visible throughout the entire stadium? The answer is honestly, nothing. Just the courage to go first, and be the leader, influencing others around you and creating an impact that spreads.

You have been created in order that you might make a difference. You have within you the power to change the world. – Andy Anderson

The Rising Tide Consulting Group is movement looking to start the waves, creating the tide, that will subsequently create larger waves, and larger waves, eventually rising higher and elevating everyone within the ecosystem. Let’s go back to the Wave in the stadium, can you imagine if the first person lifted their hands to create the Wave and the person next to them watched, acknowledged it was cool, and did nothing? The only reason why the Wave works is because the second person who follows, then the third, and the fourth and so-on. This is why at Rising Tide we are hyper-focused not on your business, but on your people. If we do your work for you, there is no impact, and we are left deciding if we should keep raising our hands to make up for the effort of those who aren’t joining or give up! If we can influence you doing your work, we can be the start of a massive wave that will spread not only throughout your entire business, but to your clients, and your vendors, raising the level of partnerships and quality of service being delivered to you, and by you.

The Rising Tide LevelUp Challenge is our ‘Audience in the Stadium Wave’. A movement started by our mentor Mendy Green on LinkedIn, where you take three stories, or analogies, and you pull out a lesson learned from each one (similar to how we did it with The Butterfly Effect mentioned above). After your three lessons you call out three new people to partake in the challenge and post their own. The lessons can be repeated, but the analogies or stories must be different.

In every situation, scenario, or story, there’s always a lesson to be learned. The scientists knew that when they framed the Butterfly Effect to teach their lesson, but each person will look at these stories and lessons through a colored lens filtered for their specific use case! It’s up to each individual as they hear these to take a lesson that relates to them. In fact, it is with Elizabeth Copeland’s lesson from the challenge (“Sometimes you need to stop and take in the view”) that we can examine analogies and situations and pull out a lesson from each one relevant to us to help us grow; the difference between taking something at face value or looking for that deeper meaning.

You can find her lesson and more by looking for the tags #RisingTideChallenge or #RisingTide on LinkedIn.