Last post I described a system that was stuck by its own commitment to user-driven development. They're really stuck. So what are possible ways out? Particularly for a government system?
I really don't know and particularly for a government system but that doesn't mean I can't think about it.
One thought was that maybe they need to make their case more clearly. How could they describe the projects better to make them more attractive in the rankings? This is probably impossible and maybe even insulting as they probably tried very hard to get their point across in the past. They seemed frustrated. Of course, they could hire a consultant to tell them exactly what they already knew - some people will listen to consultants.
I was wondering if acquisition rules would allow them to set aside like 20% or something to do their projects - ones that they thought were best but not necessarily voted on by the users. This would work for things that were less expensive to do or could be piloted.
Part of the problem is that the system may need to be re-architected and might need major redesign. Some of the pieces can be kept, but need to be integrated. That would have to wait for the next major version. Maybe if their key software underneath has to be upgraded, they could use that as a reason to do some things?
Sigh. I don't know. It sure is easier just to dream of a cool system.