Skip to main content

You Gain by Using Software, Not Just Owning It

January is the time for New Years resolutions and for planning new initiatives.  The gym is getting crowded with new members who have vowed to exercise more.  Others are trying out new treadmills, stationary bikes, and elliptical trainers at home. Unfortunately, many of them will not stick with their plans more than a few weeks, as they become bored or other priorities take over.

This reminds me that business software requires long term commitment, and hard work to drive adoption in order to gain the benefits of automation.  Here are five tips from my company's clients who are most successful in using the software that they buy:

  1. Start at the top. Executive sponsorship and use by the appropriate leadership goes a long way toward driving software adoption.
  2. Keep training after your system goes live. It is hard to absorb too much training at one time, and users can hone their skills if provided training weeks and months after initial training sessions. New employees will also need training, so plan for how you can help them become proficient.
  3. Adapt based on user feedback. Users are likely to find new ways to make the system more effective after they have a chance to use it in production.  Help these suggestions make their way into the product so it can improve over time. 
  4. Learn from your best users. Every organization has users that go further and learn tricks and shortcuts that make them more productive.  Find a way for these users to share their techniques with others.  Lunch and learn sessions can be helpful.
  5. Establish governance over the system and your data. You need processes and people who can maintain the quality of your data and allow your system to improve over time.  A change control board or similar group should be created before you go live.
Business software often brings new approaches and workflows which can make your organization more efficient and effective.  Mindfulness is essential in order to make the most of these benefits, to avoid making your software end up like the treadmill in the basement which is used to hang laundry. 


Popular posts from this blog

Key Concepts for Microsoft Dynamics 365: Tenant, Instance, App and Solution

To understand Microsoft Dynamics 365 (formerly Dynamics CRM), you need to learn some new terms and concepts that may be a bit different from what you know from databases and solutions that are hosted on premises. This post introduces some of the key terms and how these concepts are important for planning your implementation. While Dynamics 365 is available on premises, it is most commonly deployed on the Microsoft cloud.  This blog post discusses only cloud implementations. Microsoft has multiple clouds such as commercial and government community clouds. We start with a Microsoft tenant .  A tenant is the account you create in the Microsoft Online Services environment (such as Office 365) when you sign up for a subscription. A tenant contains uniquely identified domains, users, security groups, and subscriptions.  Your tenant has a domain name of .onmicrosoft.com such as acme.onmicrosoft.com.  User accounts belong to a tenant, and subscriptions are assigned to user accoun

Understanding Dynamics 365 and Office 365 Admin Roles

Managing Dynamics 365 instances If you run Microsoft Dynamics 365 (formerly Dynamics CRM) in the Microsoft cloud, you need to understand how your Dynamics instances relate to Office 365 and choose which of your administrators receives which roles and permissions to manage Dynamics 365. In on premises deployments, your network administrator would create and delete user accounts.  The Dynamics 365 admin would then assign permissions to users in Dynamics 365. This post explains three administrator roles: Office 365 Global Administrator Dynamics 365 System Administrator Dynamics 365 Service Administrator You may think that the Dynamics 365 system administrator would have power to do all the actions needed to manage Dynamics 365, but this is not the case. What's different in Microsoft cloud deployments is that licenses and user accounts are managed in Office 365 by an Office 365 Global Administrator.  This role is analogous to a network administrator for an on premises

Replacing Microsoft InfoPath with Power Apps

Source:  https://powerapps.microsoft.com/en-us/infopath/ Microsoft has offered a number of forms automation products over the years, and the most long running was InfoPath which was released as part of Office 2003.  InfoPath is a powerful and flexible product that stores user data in XML while offering form features such as rules, data validation, scripting, and integration with SharePoint.  The popularity of SharePoint resulted in many organizations standardizing on InfoPath for forms, especially internal forms which are hosted on an intranet such as employee reviews, leave and payment requests, and human resources forms. Microsoft has discontinued InfoPath, with mainstream support ending July 13th, 2021, and extended support ending July 14th, 2026. Microsoft has named Power Apps as the successor to InfoPath .  Power Apps has much in common with InfoPath.  Both products include integration with SharePoint.  Both are geared toward the citizen developer and do not require advan