Skip to main content

Don't Fight the User Interface - It Usually Wins



Businesses and government have adopted off-the-shelf software, especially cloud software products, to avoid the cost and technical risk which have often accompanied custom software development.  This means that software vendors control the user experience such as navigation, menus, colors, fonts, and all other aspects of the products. Faced with rapid innovation and competition, cloud software vendors are introducing updates at an increasingly rapid pace, forcing users to relearn on the fly.  Browser-based solutions also embody the behavior of the specific browser each user chooses, such as Chrome or Microsoft Edge.

In some cases, you may not like the most recent version, or an update may be disruptive to your user community. Should you write code to recreate the previous interface? Or circumvent the default behavior of the browser or the app?

My experience is that resistance to the user interface of a commercial product is largely futile. Accepting changes introduced by the vendor is part of the trade-off of COTS v. custom software.  Even if you can temporarily fend off an upgrade, in the long run you are likely to want the latest and supported version of every software product.

The solution is continuous training to help your users achieve greater productivity and take advantage of new features and options as they are introduced.  Too often training is an afterthought, and users do not know where to turn for learning resources.  Without training and support, adoption will suffer along with your business goals.

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