RULES MATTER (NOV 2016)

I believe it was around year '99 or may be it was 2000 when I was commuting daily from Manhattan to New Jersey; reverse commute is generally OK. Everyday on my way back towards the Holland tunnel, I would take I-280 East, continue on to a spur that connected to the Pulaski Skyway and enter one of the tributary to the river that becomes daily grind to the entrance to Holland Tunnel. Right around when joining the Pulaski Skyway, there were generally three roads merging and that would in turn fork into three outbound roadways. While that is not unusually in and around NY-NJ area, except for the lack of lane markings. When there were lot of cars, the traffic generally would crawl and it was generally safe intersection; if you call it an intersection. However, things were pretty bad when there was not much in a way of traffic and cars at that time would be speeding way above the speed limit that was marked. Again, not unusual for the time and place.

Problem was this. Cars entering the intersection area would have one of the three or four possible outbound paths. Now this was not a usual intersection, it was more like three paths which were more or less 10 degree angle to each other, forming entry / exit cones. Since there was no need to turn, the cars would not actually slow down. And that did cause problem; I always had to stay ultra alert when in that area. And every time I would tell myself that this could be dangerous.

And that is exactly what happened. On a single day there was an accident involving multiple fatalities and that tripped someone's alarm. The story got repeated in every news cycles in local media (for me that was on local AM news station). Soon (although not soon enough) the keepers of the road safety got involved and they came up with the solution and that made the intersection dramatically safe. If you guessed lane markings, you would be correct! Such simple solution and it avoided huge cost.

Lane markings and road signs are everywhere. They are easy to follow when well designed. And that keeps avoidable disasters from taking the toll.

Same is true for Applications. Implementing proper validations can help you maximize your returns on the automation that you have placed.



LS/R -- LENDING SYSTEM RULES (SEP 2016)

Increasingly the necessity of automating loan data-entry, onboarding and servicing is widely recognized and its no longer regarded as a luxury. Unfortunately, a less well regarded is the reality that automation alone is not sufficient. Realistic servicing scenarios will involve managing the constantly shifting boundary between activities that are automated and the activities that are left to carry out manually. With the tasks at the lower end of complexity spectrum getting evermore automated, what remains to be executed manually, as a consequence, tend to be complicated; needing constant attention and diligence, requiring sharp analytical eye, and ever-present investigative hunches to accomplish manually at requisite quality and speed.

Catching or avoiding costly mistakes not only save time and improve your bottom line, even more importantly, it greatly protects the credibility and reputation of your lending platform. Now more than ever, there is need for harmony between automated and manual execution of activities. This requires that users are armed with proper tools to do their jobs effectively and have loans serviced through the system free of friction and with optimum quality. Raw SDK approaches go a long way towards this goal, however, leveraging SDK effectively places a premium on technical skills, experience, and the knowhow that are needed before any benefits are realized.

LS/R unlocks the power of SDK to help attain Quality Data Entry, make Loan Servicing Tasks conform to desired business processes, and comply to internal and external regulatory and monitoring requirements.


Advocating End-User Programming for Business Applications of all kinds


Email | Copyright © 2016 ASSET, Inc.