Tag: solutions

  • How To Leverage Technology

    How To Leverage Technology

    The modern world of business is flooded with technology. Whether it is the basics like an email client or complex ERP systems, every company out there is going to have to leverage technology. That is a good thing. We can use technology to spend more time on our business instead of in it. That means better customer service, improved response times, and happier employees. Better yet, those returns do not require an investment that is equivalent to betting the farm on it.

    Not all of us are “tech gurus,” and often we do not know where to begin. I am going to give you a crash course in improving your business and steps that can get you going today. These are steps you can take even if you do not know the first thing about technology. They start where you do, your business and what you do best.

    Technology gives us ways to do more faster and at a lower cost. However, that is not beneficial if we make mistakes faster, produce more errors, or do any of that at the expense of our customers. Thus, we start with what we are currently doing. Before you can leverage technology, you need to be able to describe what you do in a way that your technical solution will understand. Computers understand black and white, well-defined steps that include all the details you can provide. That is where we begin. There is no cost to taking this first step. You can do it with technology that is no more advanced than a pencil and sheet of paper. 

    Getting Started

    The most important thing a business does is where we will find the biggest “bang for our buck.” Start by describing your most crucial business task in a sentence or two. This is your primary product and what it provides to your customer. Think of it as why your business is in business and why it generates revenue. As an example, my company would start with, “Help companies assess where they can leverage technology best and build a plan to do so.” Your answer doesn’t need to be flashy or polished. The goal is to start with the process that means the most to your business.

    Now you need to go down a level and create a list of steps that takes you through the customer’s journey. This list will likely be several steps and may be dozens. Here is an example that can help you get started. Your steps will look different, but maybe the thought process will help you build out yours.

    1. Identify potential customers
    2. Contact customers
    3. Send/provide a pitch that tells a prospect how we will provide them value
    4. Confirm a sale
    5. Schedule product/service delivery
    6. Fulfill order
    7. Follow up with the customer to confirm successful delivery.

    Those steps may seem a bit vague and general. That is ok. We want to keep this at a higher level for now. The next steps are to take one of those identified above and make it our focus. When you list out the steps for your business process, there will likely be one or two that give you the most trouble or cost the most to execute (or both). That is where you want to begin. Take another step down in detail with that step. I will use step 3 above to provide an example. These are the steps we take to send a pitch to a customer.

    1. Research the customer industry/background and find where the most likely needs are.
    2. Build out a custom pitch from our core offering.
    3. Add details to the pitch that personalize it and let them know this is not some inhuman automation.
    4. Add a proposal and call to action.
    5. Send the pitch
    6. Follow up

    We are now at a point where we can start leveraging technology. While each of the above steps will have another layer or more of detail, we can take some steps with minimal technology cost. The easiest way to begin is to turn the above into a checklist. You can create a list of prospects. Then, for each one have a checkbox for each of the above steps. You can do this in a spreadsheet or similar tool. Check out Asana or Trello for free options that can help you.

    Now you have something that can leverage technology. There are plenty of ways to set up your list so that you have a dashboard of where prospects are, what is the next step, and reminders to ensure no one falls through the cracks. There are plenty of tools available that can provide those features. They can save you time, help avoid mistakes, and get you on a track to an easily reproducible process. That is where you can further automate a process or scale it by handing it off to another employee. 

  • Selecting A Software Partner

    Selecting A Software Partner

    The success or failure of a project often rides on how good a company is at selecting a software partner. Software development has become almost a commodity in many areas. However, the team you choose or build is a critical factor in project success. No two providers are the same, and minor differences can have a substantial impact. There is far more than price, experience, or even portfolios that go into selecting the best team.

    Selecting A Software Partner Is Like A Marriage

    Few, if any, people choose to marry the first potential partner they meet. Likewise, they rarely leave the decision up to first impressions. Yes, we sometimes can quickly see a bad option and reject it. However, making a selection takes time, investment, and getting to know the partner. This approach should be the same in selecting a software partner. The “home page” view of them (experience, portfolio, and pricing) should be just the beginning.

    Explore The Portfolio and Experience

    We can often start the selection process by discussing past performance. You likely want to avoid someone brand new at solving your problems (or similar ones) as well as those who have tried and failed. A good track record is not insignificant. It is just the beginning. Think of it as an icebreaker of sorts. The prospect’s history and experience are a gold mine for leading as well as open-ended questions. Get them talking about the problems they solved, the challenges they faced, and how they got through it all. These sorts of answers provide you with a wealth of information to judge whether they will be a good fit or belong on the rejection pile.

    The Goal Is A Solution

    One should always start the search for a software partner with a clear idea of the problem or problems the partner will be asked to solve. A good partner will be able to offer solutions that suit the problem. Watch out for those who talk in generalities but seem unable to provide a path to a true solution. They will give you names of frameworks or processes and technical jargon. Yet, they will not be able to phrase your problem and a proposed solution in a way that makes sense. It can be tempting to hire a partner who talks above your head because they must really know their stuff. Yes, they might know their business inside and out, but you need a partner who knows and understands your business and pain points.

    Common Mistakes and Incorrect Assumptions

    There are a few areas where a software partner selection tends to go wrong. Avoid these mistakes, and you will be more likely to find the best partner for your needs.

    • Unclear requirements – The customer should drive requirements discussions and avoid being led by what the software partner wants or their area of expertise.
    • Budget Constraints – Time, cost, and quality are the factors that combine to determine price. Your goals, budget, or schedule may need to adjust to solve the problem. A hard deadline or budget can severely limit options and what a partner can provide.
    • Due Diligence – Determining the best partner can take some time and research. Make sure it is clear what is needed and what will be provided.
    • What happens next? – A partner will likely be needed beyond deployment to enhance or maintain the solution. Be clear on that extended relationship and license or contractual agreements.
    • A Simple Solution – It may be surprising, but I have seen both the customer and the software partner guilty of underestimating the project. Critical details can often be hidden in the initial phases of a discussion.
    • Accountability – Both sides of the partnership must agree on who will do what and how to hold each other accountable. Things happen, dates slip, and scope changes. These common challenges need to be understood and an agreement reached for how to work through them.
    • Service Level Agreement (SLA) – The SLA is something that too often is left until a product is complete. Ensure the partner can step up to any desired SLA. It should be realistic. However, some partners are not staffed or built to support ongoing SLAs, such as a 24/7 support line.

    Date Around

    There are software partners of all shapes and sizes. Take the time to get to know enough that you can judge a good partner. This process is an investment of time and a critical factor in your success. Do not rush into a partnership, nor take it lightly. The time you spend finding the best software partner for you will pay off many times over.

    Next Steps

    Feel free to schedule a time to discuss your next project with us and see if we might be the perfect partner for you. We take these relationships seriously and are happy to point you in the right direction if we are not a good fit. Years of being on both sides of these relationships have taught us a lot. That initial call is free, and there are no obligations. You have nothing to lose. 

    Our experience has taught us a lot about the pitfalls and challenges of custom software. Likewise, we have an e-book that can help you explore all the steps in building software, including a few templates. However, we ask that you share an e-mail address so we can send you a copy. We will add you to our monthly newsletter, but you can unsubscribe anytime. Your data is not shared with anyone else. Learn more about our book here.

  • Investing In Requirements

    Investing In Requirements

    Custom software can be very expensive and scary, but investing in requirements can help you improve the likelihood of success. However, we often want to see things being built rather than simply think about them. That creates two things that fight against each other (get it done or think it through) in many projects. Thus, we must consider early work on requirements and design as an investment. We pay for it in patience, but it saves us in almost every way down the road.

    Investing In Requirements Is An Easy Choice

    There is so much value in thorough requirements gathering that it seems impossible for anyone to pass over this crucial step. Unfortunately, it is a common problem and one of the reasons many software projects fail. Yes, we want to see “work getting done,” but the only reason that is a problem is because we are not yet seeing the end product. I like to use the analogy of going on a road trip. You are not getting closer to the destination until you start driving. However, if you do not know where you are going or the obstacles on the way, it can be extremely costly. Those that use modern GPS maps or apps like Wayz often are redirected around problem areas and potentially save hours of drive time. That is the same with software development. We are not writing code but investing in requirements, so we have a better idea of the path ahead. That allows for proper estimates and planning.

    We Can Adjust As We go

    One argument we fall prey to is that we can start building the software and easily adjust as we go. While there is truth in that, and we do not need to know the whole journey in detail, we do need to plan for each stretch. That is what the Agile approach embraces. It takes a bit from both worlds and gets us on the road faster while still ensuring we are planning enough to avoid major issues. When we use the road trip analogy, it is like planning the trip but then being open to adjusting due to construction or traffic delays. However, the key is that we need to know at least some of our path before we start. In a software project, this can be done via high-level requirements and core feature definition. Be warned that is a possible approach, but it can still suffer from wrong turns and proceeding down dead ends.

    Back On The Main Road

    The discussion of Agile and its strengths and weaknesses is for another article. Let us return to a focus on requirements that applies to any software project. Modern software systems are highly complex. There are tools that can help us to create or generate thousands of lines of code quickly. However, that speed can be just a faster way to create a big mess. I have seen many projects stumble and fall due to this issue. The problem may seem simple, but the details are highly complex.

    For example, let’s consider the simplest of problems to solve: keeping contact information for your customers so you can serve them. How hard can it be? There is a name and address and maybe a phone number or email. Oh wait, what if the customer needs a title, or is a company with multiple contacts? What if the billing contact is different from the key decision maker? Do we care if they have bought from us before, or do we track leads? Should we keep notes each time we talk to them? The list goes on and on. A simple problem can quickly become a complex maze of decisions. These can be very costly to make if we have already made a lot of progress on our software journey. Changes can require updates to code the database, the user interface, and even the partners or libraries utilized. Backing up is far more than that BEEP, BEEP, BEEP a large vehicle makes.

    How Do We Get The Requirements We Need?

    Custom software development is just a way to solve problems on a big scale. Thus, we can use basic problem-solving techniques to guide us in creating a list of requirements that we can be confident in. Here is a short list of questions that you can use to take your requirements definition up to another level.

    • What does this need to do?
    • What does success look like?
    • Who needs to know about task completion?
    • Where can it fail?
    • Who needs to know about a failure, or how do they need to be told?
    • Is there anything else it needs to do?
    • Can any user do it?
    • Does every user experience it the same way?
    • What did we forget?
    • No, really, what else did we forget is a part of this process. Walk through each step as thoroughly as possible.

    The above question may not seem like much. However, they are easy to overlook. I have worked on dozens (probably hundreds) of software projects and still need to step back and review these questions each time. We can easily get lost down a rabbit trail and skip a step. A thorough review before building out requirements is a huge step in the right direction.

    Play It Back To Me

    A good way to ensure clear communication is to have someone repeat back to you what you said in their words. Do the same thing with your requirements. Walk through your problem and the proposed solution using only what is listed in the requirements. This action often brings up more requirements and details than even the last two questions listed above.

    Next Steps

    Feel free to schedule a time to discuss your next project with us. We are happy to help you with investing in requirements and improving the overall success rate of software projects. Our experience has taught us a lot about the pitfalls and challenges of custom software. Likewise, we have an e-book that can help you explore all the steps in building software, including a few templates. However, we ask that you share an e-mail address so we can send you a copy. We will add you to our monthly newsletter, but you can unsubscribe anytime. Your data is not shared with anyone else. Learn more about our book here.