I was recently introduced to someone by a mutual contact who suggested that we meet at the new contact’s office because of the quality of his pour over.
I admit that although I love coffee and drink it daily, the pour over jargon was new to me. Luckily, Google was able to rescue me from my ignorance, and I realized that I not only hadn’t been left behind by coffee aficionados and some awesome coffee brewing technology, but that this is in fact how I make my coffee all of the time.
Now, for those who don’t know, the pour over is basically a manual coffee brewing process in which you “pour” your perfectly heated water carefully “over” your perfectly measured grind to create the perfect cup of coffee. Research into this method will quickly reveal a myriad of options of varying prices, styles, and complexities. Some will swear by a certain type of kettle or a certain type of filter, or state that you need to use a thermometer to get the perfect water temperature or a gram scale to perfectly measure your coffee. (Here’s a great blog on some of the options out there: https://prima-coffee.com/blog/a-beginners-guide-to-pour-over-coffee-brewing)
I use my everyday electric kettle and a plastic single cup coffee cone that I picked up years ago. I switched to the single serve cone, because I felt unsatisfied by the lackluster coffee created by my original electric coffee maker, and the French press was too much cleanup. Hating the idea of generating so much trash with paper filters, I explored metal filters as well before settling back on the paper filters because using them got me the tasty cup of coffee that I wanted and the time/energy expenditure that worked for my daily schedule.
That’s a lot about my coffee conundrum, but what does this have to do with software choices?
I think my experience with the “pour over” jargon is reminiscent of the emotional and other phases we go through when faced with (real or perceived) changes in technology.
When we hear about a “new” thing that “everyone” is using, it’s easy to slip into a panic about being left behind by technology, and to feel an urge to catch up as soon as possible.
You ask yourself things like: How have I not heard of this before? Is everyone else already doing this? Is there something “wrong” with the way I do things? How soon can I get on board with this new way myself? Is it going to cost a lot? What’s going to happen to my old stuff?
Take a deep breath. And then do a little research to see what the “new” thing is.
With my coffee conundrum, all this entailed was a simple Google search. More than likely, a Google search of the new terminology will yield all the results you need at this point. If you’ve just seen a presentation or demo, then you probably know all you need to know at this point.
Next, step back and assess what you really want and need.
This is something you have to assess in terms of your business processes (a.k.a. your business flow). It’s good to take stock every once in a while. Needs change over time, and it’s good to reassess where you’re at against where you want to be.
I needed a robust means of making a tasty cup of coffee with minimal cleanup. I wanted a means of doing so that entailed minimal trash waste. My needs were determined by a morning ritual that I’ve come to rely on as a start to my day, and the amount of time I could afford to spend on this ritual without sacrificing something else. My needs had not changed over time, so my original process remained as-is.
Once you’ve determined your ideal business flow (including who does what, how information needs to flow between people, any compliance regulations that you might be under, and performance/productivity metrics), it’s time to turn your attention to those things that are supposed to be supporting that business flow, like your software.
It’s important to assess if your software is already doing the job. It’s also important to assess if you’re doing a lot of work to convince yourself that your software is doing the job.
What does it even mean for software to “do its job”? Basically, you need to perform something called a gap analysis. Based on that business flow you just nailed down and the requirements you expect your software to help you meet, investigate for places where the software does or does not help you meet those requirements. For instance, you might need an audit trail of preventive maintenance on your equipment to meet certain compliance regulations for that equipment. Does your software record this information in a way that you can use? If so, then the software is doing this job. If not, and you expect or need the software to be doing this, then you’ve identified a gap between your business flow and your software.
Going back to my coffee conundrum, the French press could have given me the flavor I was looking for, but it was also introducing a lot more “busy work” into my process versus the single serve cone. I had been left behind by jargon, not technology. In this case, even switching to the “new” thing wasn’t going to change my situation, because I was already doing that thing and just not calling it that thing. Lesson learned. I now had the words everyone else was using to talk about this thing, and I could better target my research to search out possible alternatives. For me, this entailed exploring other pour over methods. I didn’t want to add more tools (i.e., cleanup), and I had already tweaked my process by trying other filters. I was left with an outstanding want but not an outstanding need, and even that want was pretty negligible in my grand scheme of things.
To return again to software, if you have to spend a lot of time getting your software to save data the way you want it to or give you those reports you need, or you have to pass data between a lot of different software packages to get what you need, or people spend days or weeks compiling information “by hand”, then you likely have a gap between your ideal work flow and your actual work flow in terms of efficiency. However, just like I live with my paper coffee filters, maybe this is something you can live with. Only you can decide if this is enough of a pain point to warrant change.
If there’s a real, painful gap between your needs/wants and what you have, now it’s time to search out new solutions.
If you’re at the point where you have an actual gap that needs to be addressed, and not just one you perceive based on new jargon, then there are two basic options for you:
a. It could be the case that your existing software solutions can be tweaked or extended to close your gaps.
b. It could be the case that you need to start putting aside some of your budget for that new software purchase.
It’s okay to not know or not be sure. Don’t be afraid to ask for help.
You can’t be an expert in everything. Expertise takes time and resources, and at some point we each have to choose to pursue some areas of expertise wholeheartedly, learn a little about others, and completely forego the rest. Reach out to others in your industry to see what they’re using, and talk to folks in IT to see if they have recommendations.
Let’s have a conversation!
If new jargon has ever sent you into a panic, I’d love to hear about in the comments! What was it and how did you deal with it? (If you have a favorite pour over method, feel free to share that, too!)
Want help assessing whether there are gaps between your business processes and your software? Want to discuss whether what you have can be tailored to better serve your needs? Let’s Connect and talk about it.