Business Tag

Two computers from the 1980s are standing on an office desk.   We see it all the time: a company has a long-established software system that's either fully custom or has been customized to fit just right. It's perfect, or as nearly perfect as software can be. And then the company grows. It evolves with the changing marketplace. Little by little, that perfect fit starts to pinch here and sag there. You know you'll need to do something about that legacy software eventually, but not now. When does "eventually" become "now"? How can you tell when it's time to overhaul your legacy system?

Salesforce User Adoption, Part II: Improving Salesforce User Adoption

team all hands together Creating a great Salesforce app for your team is only part of the solution; the other part is getting your team to use the app. The best tool in the world is useless if it's not used! You've seen plenty of tips about signs your team has bought into using Salesforce. Your next step is improving Salesforce user adoption, and communication, training, and continuous refinement are the keys.

sorting and organizing Many companies use Salesforce not only for sales-related CRM but also for managing disparate business processes. Salesforce record types can help administrators fine-tune their orgs and manage business processes for different users effectively. Sometimes, administrators go a little overboard with custom record types. Even after reading the documentation, it can help to see how other admins utilize Salesforce record types. Here are some tips to help get you started.

Monolith; Monolithic Rollout of Legacy System Conversion Legacy system conversion projects are always challenging. Rollout strategy can make a huge difference in successful user adoption and overall project success. Only when I began writing them down did I realize that I had recurring dreams.  I had believed that my dreams were largely random and varied, but instead I learned that I had many frequently recurring themes.  Similarly, the process of writing down my thoughts on software development has shown me that there are also recurring themes. One of these themes is the impact of rollout methodology on a project's success.  More specifically, rollouts of legacy system conversion projects.  Rollouts of brand new systems into an organization are typically less painful, as you are often automating a paper process, or inventing a new process that improves productivity.  However, legacy system conversions are almost always painful, as there are many processes that have emerged around this system.  People have developed a form of muscle-memory with the old system that even they themselves scarcely understand. We have successfully replaced dozens of legacy systems where everyone was happy and all was good with the world.  But it's not those projects I want to talk about.  I am going to talk about the projects where things went awry, because I don't want to make the same mistakes again.  Hopefully, these words will also help the reader to avoid similar problems in their projects.

Now that your company has rolled out its shiny new CRM system, you’ll want to make sure your team is fully on board. How can you track Salesforce user adoption? What are the signs you don’t have full buy-in from your organization on using Salesforce?Silhouette of many thumbs up Of course, there are many useful reports available in the Salesforce Adoption Dashboards. To get the most benefit from those dashboards and reports, you'll need to quantify your expectations. How should your team use the system?

3D stick man jump over crack floor, business concept, avoid pitfalls.Working with Salesforce relationships is a little different from traditional relational database structures, but Salesforce has great tools for building custom data relationships and most people can adapt quickly to the SOQL model. As with any other system, though, there are a few "gotchas" to watch for when designing Salesforce relationships. I ran into one of these gotchas just recently. I needed a lookup relationship from our custom object to the standard Product table, Product2. No problem, right? Create the lookup field in the custom table, and there it is. Not so fast!  

When your business requires a software solution, you have several directions which you can go. A credible custom programming firm can help you device by completing a detailed needs analysis so that they can provide you with the information needed for you to make the best business decision for your company. It's not always easy to device which application is right for your business. Below are a few pros and cons that may help you device.

80% of small businesses utilize QuickBooks to handle their accounting needs. This includes accounts payable, accounts receivables, time tracking, vendor databases, and client databases. QuickBooks is a revolutionary program that has one big flaw; it does not allow for native importing of other systems data. Most businesses and their accounting firms have no idea that they can import anything into QuickBooks with a little help from a custom-programming firm. By integrating disparate systems with QuickBooks, businesses can increase their productivity and run more efficiently by eliminating redundant data entry.