Skip to main content

Why Information Technology is Like Exercise

I must confess that I don't like to exercise, especially when it's purely for health reasons. I haven't run far and long enough to become addicted to the runner's high. I feel better after I run for the rest of the day, but it still takes effort to get up early and get out there. For me, exercise is best in retrospect.

On the other hand, I am a huge gearhead. I like researching the latest camping equipment, golf clubs, fishing lures, backpacks and even running shoes and socks. It feels great to gear up to be ready for fitness. Sports Authority can testify to my optimism for fitness.

At the end of the day, though, the gear doesn't make you fit. You have to get out there and run, bike, swim, hike, or hit that ball or puck to stay in shape.

Information technology is similar, in that it takes more than gear and software to improve business processes. The most important ingredient is the will to change and openness to assess the way an organization works and find better processes, then automate them if necessary. Buying the latest and greatest technology does little for an organization not willing to invest the time to use the new tool.

When the will to change is absent, no amount of money, hardware or software can make up for it. The examples of failed software projects are legion, and many can be traced back to a lack of leadership or a failure to make tough decisions and tradeoffs. In other cases, the failure is in the last mile of the project: failing to train users and encourage adoption of the new system.

Over the years, we have had the good fortune to work with a large number of IT leaders who were not afraid to shake things up, take chances, and make tough decisions in order to reach their goals. We usually know at the beginning of a project whether the client has this requisite toughness, and its presence is a reliable predictor of project success.

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