tag:blogger.com,1999:blog-852028730356570772.post3599152760745739798..comments2023-04-14T08:01:31.630-05:00Comments on Catherine's Corner: Please keep the user in mind....Please.....Catherine R.http://www.blogger.com/profile/12294447414092276386noreply@blogger.comBlogger2125tag:blogger.com,1999:blog-852028730356570772.post-51499677552662822082007-05-21T13:54:00.000-05:002007-05-21T13:54:00.000-05:00bean - I hear ya. It's pretty hard to convince pe...bean - I hear ya. It's pretty hard to convince people who are "in charge" that there is more to manage in a technical implementation than just the technical aspects....I feel like I'm the only one who "drank the kool-aid" in the room when I talk about building in time in the project plan for documentation and training development. Instead, the people who actually have to use the system are an afterthought and "success" is measured by whether or not they got the system "working."Catherine R.https://www.blogger.com/profile/12294447414092276386noreply@blogger.comtag:blogger.com,1999:blog-852028730356570772.post-76528632898723199442007-05-14T09:42:00.000-05:002007-05-14T09:42:00.000-05:00We're at the end of the dev cycle, too. Before the...We're at the end of the dev cycle, too. Before they are ready to ship, our engineers are very secretive about the workings of our products. They question us thoroughly and 9 out of 10 times, they won't let us see a product ahead of time. Then they send a version over to us to look at for one day before it ships and expect us to produce a fully developed service and parts manual.The problem is that engineers don't seem to care if any documentation goes with the product at all. Once it gets out the door, it's our problem, not theirs. No sense of user-centered design, either. Product if finished and you have customers going, "How do you turn this on?" Turns out the switch is in a hidden panel that is not apparent from the front of the product. While that's neat, it does new users no good whatsoever.Anonymousnoreply@blogger.com