))
XRM Can Help
Archived series ("Inactive feed" status)
When?
This feed was archived on November 30, 2017 16:14 (
Why? Inactive feed status. Our servers were unable to retrieve a valid podcast feed for a sustained period.
What now? You might be able to find a more up-to-date version using the search function. This series will no longer be checked for updates. If you believe this to be in error, please check if the publisher's feed link below is valid and contact support to request the feed be restored or if you have any other concerns about this.
Manage episode 169015162 series 1323125
Content provided by Jon Doctor. All podcast content including episodes, graphics, and podcast descriptions are uploaded and provided directly by Jon Doctor or their podcast platform partner. If you believe someone is using your copyrighted work without your permission, you can follow the process outlined here https://player.fm/legal.
Here are three quick points for December 27, 2016.
Today's cast looks at the benefits of providing functional experts and information workers with low or no-code development capabilities for ad-hoc business tools and applications. Typically missed as part of the technical footprint because they are created on the desktop and hard to track, ad-hoc tools are often used for decision support or give structure to rules which make business operations possible. There are system gaps everywhere which is how these tools are realized but it also positions xRM as an ideal option for deploying and managing these important assets.
- An xRM development approach integrates common organizational data and can be secured on centrally managed repositories. This means there are no more form fields to keep updated, stored credentials, or password protected worksheets. An additional benefit is that local copies will give way to mobile, eliminating version problems altogether.
- xRM applications can be rapidly iterated, replaced, or retired with greater control. The QA cycle is immediate, these were never formal applications, and the users were the makers. Owing minimal tech debt, these small but important tools did not need to be pretty, only to work as designed.
- xRM formalizes work, ideally within a larger process, making it possible to measure activity that was previously invisible or attributed to overhead.
In the absence of a standard, or in this case a platform, departments will create calculators, templates, and forms. Furthermore they will rely tools that are already familiar, generally desktop applications like Word, Excel, and Access. This is not to say that every pricing calculator needs to go through formal development, it would likely be too slow given how quickly they change. Locally developed tools have value, usually they are a direct response to real inefficiency, but are inherently difficult to control. Every company has a complex relationship with these types of artifacts because they are easy to create, aid decision making, and help enforce common practices; all of which are important. However they also tend to be a frequent source of risk when unmanaged, unmeasurable, and lacking proper security.
8 episodes
Share
