Tag: software development

  • Year-end Technology Assessment

    Year-end Technology Assessment

    We are approaching the end of another year, the perfect time for a technology assesment. Yes, it has flown by, and now we are in the 4th quarter of every year, when we should be looking ahead to the year ahead. That makes this a great time for review and planning. However, we are starting into a new wave, and it is more important than in recent years to assess where you are and where you should plan to go. 

    We call that plan a technology roadmap. Every business should have one. Even more, that roadmap needs an annual review at least. Technology and the related solutions move too fast not to. However, this does not need to be a scary or even an expensive process. You need to spend some time reviewing where you are, what is causing the biggest headaches, and where your business is aiming in the year ahead. You might notice that none of those steps require any knowledge of technology. Therein lies the greatest value of a technology assessment, a review of how your business operates.

    Business Over Technology

    Too many businesses and technology advocates push a solution or “the latest hot tech” rather than starting with your business processes. A technology assessment views those processes through a specific lens. However, the strengths and weaknesses of those processes should be the focus (or the “why”) of any assessment. That is where even a technology-focused assessment can provide value before getting to the assessment recommendations. 

    Most, if not all, of us benefit from talking through problems and challenges. That is why counseling is such a beneficial activity. We might pay a counselor for exactly that service, or we gain counseling by sharing our time with friends, family, and confidantes. A proper technology assessment provides that opportunity to talk through our daily and weekly routines in a way that helps us identify more details. Our focus allows us to identify and document some of those “muscle memory” tasks that we otherwise overlook. 

    A Technology Assessment That Serves Your Needs

    Once we have those steps outlined on paper, we can use them as a guide for leveraging the latest technology advances, upgrading our systems, and adapting to changes from previous years. Thus, the assessment is not pushing the latest offering from a vendor, nor the hottest new thing. Instead, the assessment should be technology agnostic and business needs-focused. The recommendation and plans should conform to your specific needs and situation rather than vice versa. That is a common mistake I see in small and mid-sized businesses. They followed recommendations over the years, but the recommendations were not based on what is best for the business. The recommendations were driven by a narrow view of the world limited by experience, vendor agreements, and the needs of those making the recommendation.

    This mindset has led us to create a short (roughly a week of elapsed time) and tightly defined assessment that can provide you with the first steps for your technology roadmap. We wanted something that we could offer that has no strings attached and allows you the freedom to make decisions based on an unbiased assessment. We can assist you with the nextsteps, or you can proceed with the roadmap on your own. If any of this has moved you to consider an assessment, then reach out to us for a call or check out our offer at https://rb-sns.com/product.php.

  • Leveraging AI Technology

    Leveraging AI Technology

    It is hard to find any article about artificial technology that does not talk about it as a game-changer. Thus, leveraging AI technology is going to be a big part of business as we step into the years ahead. I have to admit I was a bit slow to really examine how it will impact us. That is because my career has seen countless times that AI under-delivered. Even now, it is roughly the next advancement in search technology. The results are rarely novel. However, how often is that our experience with human interaction as well? How many times has a common topic suddenly sparked innovation due to a slightly different perspective or even phrasing of a problem?

    Leveraging AI Technology as a Worker

    The simplest (and potentially most powerful) case for AI is to use it to scale ourselves. The virtual assistant industry has become what it is (almost $20 billion in 2025) because high achievers can do more when they draw on others to do the things that slow them down. The cost-effectiveness of VAs has been one factor in growing that industry. While AI is being adopted to keep those companies relevant, I think AI will end up killing that industry. We now have a VA at our fingertips via tools like ChatGPT and the integration of AI into tools like “Hey Google”, Siri, and Alexa. 

    The low-hanging fruit aspect of using AI as a VA makes it the perfect place to take your first steps into using it. There are skills that are required to leverage tools like this properly, but they can be learned. Skills like delegation, clear command and communication, reviewing results, and adjusting to the audience are not magical. They just require practice.Fortunately, trial and error is not a bad way to delve into finding out how to command AI in a productive way.

    Leveraging AI Technology as a Sounding Board

    While there is a danger of creating your own personal echo chamber, AI makes an excellent sounding board. This is where I am seeing many thought leaders take it. We learn more by discussing our thoughts with others. We can use AI tools to increase the velocity of discussions and even create an environment to test out our ideas. However, that is far easier said than done. I see that challenge in the rise of project requests that boil down to, “Create the environment where I can learn from AI.” This opportunity takes practice and developing skills that some of us (yes, particularly the younger ones among us) have been working on for years via searches and interacting with technology via natural language rather than code. 

    I see that experience in “talking” to computers as the most valuable asset we will have moving forward. It is a new kind of leadership that ignores EQ but requires us to build EQ into the results. A computer doesn’t really care emotionally how you ask a question. On the other hand, the details are critical. The output of a request is going to be lifeless, as we see in content that is purely AI-generated. Those who will find the greatest success in the future are the ones who can breathe life into what AI builds. While science and technology will create faster, the need for the “artists” that can turn it into something “human” will grow exponentially. 

    Start Today

    There are many conversations I have had where people talk about learning AI as something they plan on doing in the future. It may be next month, quarter, or year. This is not a case where you can spend a weekend and be ready to embrace the next wave. It is going to take time, and for many of us, will require a retraining of how we think. Start today, start small, if needed. The “youngsters” among us have switched from search engines to AI tools for their search engine. Try that out. Then start to ask follow-up questions in your searches. Practice refining your request. Build that habit. See where it takes you because the next wave is upon us.

  • Runaway Technical Debt

    Runaway Technical Debt


    I was recently listening to advice from Financial Guru Dave Ramsey about financial debt and how it can control us. The thought occurred to me that this is very much a factor in software development when we have technical debt. We need to avoid letting our pile of debt get out of control or something we simply accept.

    Technical Debt Seems To Always Grow


    The problem with technical debt is that many of us simply accept it. We toss it into a bucket without considering the cost. This applies to missing or incorrect documentation, slow-running queries, clunky interfaces, and so much more. Yes, we can get away with that for a bit here and there when we have to hit a deadline. However, those little things can add up.

    The worst part about those “little things” is that they are small thieves of time and quality. Moreso, they can be hard to measure. Thus, we allow them to be a part of the experience with that codebase or application. For example, how often do you hear a user complain about a solution but then brush it off like that is just how things are?

    Address The List

    The idea behind technical debt is that we have a task we should do, but we kick it down the road instead. If this was not a task we should be ding it would not be technical debt. That is no different from getting an oil change for your car or cleaning air filters. We have a period of time where we can push those tasks off, but eventually they can grow to an emergency situation that must be immediately addressed.

    Just like we need to keep track of debt in general, technical debt should be reviewed regularly and even avoided where we can.