| M | T | W | T | F | S | S |
|---|---|---|---|---|---|---|
| « Jul | Sep » | |||||
| 1 | 2 | |||||
| 3 | 4 | 5 | 6 | 7 | 8 | 9 |
| 10 | 11 | 12 | 13 | 14 | 15 | 16 |
| 17 | 18 | 19 | 20 | 21 | 22 | 23 |
| 24 | 25 | 26 | 27 | 28 | 29 | 30 |
| 31 | ||||||
- product manager (7)
- projects (40)
- resourcing (4)
- software selection (1)
- tax billing software (32)
- vendors (49)
- water billing software (38)
- 19. April 2011: User groups
- 19. April 2011: Detecting theft
- 13. February 2011: Automated water meter reads
- 27. January 2011: What German utility billing software would that be?
- 5. November 2010: Seven myths of billing implementations
- 24. October 2010: Comparing utility billing software
- 1. October 2010: Failing in the public sector
- 29. September 2010: Project failures
- 27. September 2010: Not the product manager
- 25. September 2010: Not the product roadmap
projects
Listen to the skeptics
In a recent article on implementing software solutions in Supply Chain Management, one of the five main points made for a successful project was “Listen to the skeptics”. Here’s what was said “Where there’s enthusiasm, it’s natural to downplay anyone who wants to throw cold water on the project. That can be a mistake because the naysayers who appear once a design is on the table are most often the people who are presently running your operation. Like Mickey Rourke’s advice to William Hurt, they’re going to see the 25 things you overlooked. “Most of us design for the routine, but the operations people have to handle the exceptions to the routine,” says Apple. “When they raise questions, you need to be able to answer them or you don’t have a good solution.” If the exceptions happen infrequently, a simple, manual workaround may address the issue. What’s important is that the objections are acknowledged and addressed since the naysayers will be running the new system.”
Leave a Reply
You must be logged in to post a comment.