This document is posted to help you gain knowledge. Please leave a comment to let me know what you think about it! Share it to your friends and learn new things together.
Quick WinsNorth Dakota SOS OfficeBusiness registration turnaround improvements madeOctober 09, 2015 4:45 pm • By Nick Smith
“… reduced the backlog of business registrations from four weeks for completion to one week.”“…process business registrations has recently dropped to its lowest level since 2010.”“…lowered the turnaround time for business registrations to the one-week range, the lowest it’s been since 2010-11.”
Jaeger said, “[Major Oak Consulting] worked over the summer months on a modeling study for the department’s long-delayed technology project that will create an online filing system for business registrations. As a result of that work, Jaeger said the department was given pointers to improve office efficiency.”
Quick WinsIowa SOS OfficeIdentified 24 “Quick Wins” being non-system improvement projects and presented to entire leadership team at the commencement of the engagement. Secretary Pate immediately looked at his staff as asked, “When will these improvements be completed?”
His team immediately started working on implementing the identified improvement and moved toward the future state, eliminated non-value add processes, and improved workflow efficiencies.
Process Mapping Best Practices1. The people doing the work are the best source of realistic data
– They are the ‘factual’ authorities on that work – treat them with respect – To get the ‘real story’, remove “bosses” from room during process mapping
2. Generalities are the enemy of good process maps - push for specifics
3. Gather data with multiple approaches - explanation and demonstration
4. Quantify as much as possible – quantification = relevance
5. Validate the process map – multiple times if necessary
6. Swim lanes make the map much more relevant
7. Capture process exceptions, but don’t map them
8. Real test is if the process map is vouched for by those doing the work
9. Break the process down into sub-processes wherever possible
10.The timeline tells a whole story in itself
11.Use flags, notes, colors and other visuals in your process maps