QUESTION Has anyone ever designed an enterprise application's first release to have only a wizard for creating complex 'objects'; then, offered a more hands on solution for a hot fix or subsequent releases?
EXPERIENCE The above question occurred to me during a presentation of an enterprise application that took months to design. Moreover, it was only after the project had been developed could the design fully be realized in all of its complexity.
Fortunately, before the release, the designer was able to test the application and update the experience before the release.
Looking back on the process, they now realize that the complexity that became second nature to them over the months where mind boggling to the first time highly technical user. Moreover, per these types of presentations / critiques, internal team members who had not worked on the problem where equally amazed.
From my perspective, part of the design's catch is that the designer must consider that these user 'pride' themselves on knowing and understanding these complex task and tools.
After the presentation, I had a discussion with the designer and had a thought / question, again, has anyone ever design the first release of an enterprise application where a wizard was the only way to create 'objects' for the first release, then, offered a more hands on solution for a hot fix or subsequent releases?