how many instances of "d" are there in:
justifying an lso implementation
01/09/2012
- faster time to answer
- click reduction
- increased user acceptance
- shorter time to custom solution
faster time to answermost lawson users spend a large portion of their day dealing with interruptions. things come up that are not part of their normal daily grind. re-engineering their standard processes only drives out some of the inefficiency. the hidden gem here is the time savings associated with lowering an employee’s time to answer. basically, how long it takes them to answer a question or track down a discrepancy or variance and take corrective action. though each interruption may be unique, what they have in common, at a most basic level is: a question is raised (work is initiated)
- verbally in a meeting or on the phone
- im
- or it could be self-initiated (worker notices an anomaly or discrepancy)
- queries are run
- reports are printed
- records are adjusted
- calls are made
- paper is passed
there are many opportunities here:it shouldn’t write complicated queries or reports and print them out, users can use list-driven forms and infobrowsers to quickly find all of the records that meet a specific criterion then edit them inline or launch them in a work list. the results can then be emailed to relevant parties and the process is done. now, take it a step further and work on prevention.
- use conditional styles to make problem records quickly identifiable.
- users can set up alerts or watches to notify them when issues arise.
- create infobrowsers that show exception records only. (out of balance invoices, error suspense transactions, vendors on hold, pos that are partially received, past due reviews, employees without benefits or on leave or…)
user
The passage contains 47 "d"s.
assistant