That is kind of funny but I suspect we are most likely going through the same process at the same time.
I am kind of looking at this in three modes at the same time. Developer - Implementor - User As an implementor, I need to know how things work so that i can install, customize and configure it. Users don't really need to know the internal workings... As a user, I am thinking more along the lines of how a user would use the system. Editing pages, formatting, searching, access to help/ formatting, ease of use things etc... As a developer, I am thinking about how I am going to integrate, support, develop the tool across mutiple platforms, and company types that I deal with. I live in both a large Corp and small business world at the same time. Even on the user level there are sublevels... Passive: Just looks for content, searching etc... Never going to edit or contribute... just looking for info. Active: Does the same as a Passive user, but if they can't find something and they figure it out, they then come back and add that tidbit of information. There are few of these. These types of users are gold. Knowledge User: This is the people who actually know how whole niches of things work. How Deliverys work, credit card processing, network configuration etc... These people are always busy and rarely have time to contribute. But these are the people with the answers, so getting them able to easily use the system to offload their information in the various areas is vital. If they can't easily figure it out, they won't bother. If they find it easy to use, some will take advantage of that and dump lots of useful info into the system. For those that can't, I need to make sure that they at least dump the data on me so that I can get it into the system. Without this info, the system is empty and lacking the knowlege need for it to exist. The fact is that most users when confronted with something they don't know how to do will rarely ask for help and just won't use it. Even the Help Desk which is where all problems and questions should be routed will ignore and stop using tools if they either never have the answer they need, or they can't figure out how to use it. I know that it is hard sometimes for a creator of a product to step back and think like a newbie looking at the project for the first time. Once you understand how something works, it is not longer a mystery. The obvious is not so obvious when you are missing pieces of what is going on. My best method of learning is documentation. As I write the document (s) that will allow users to use the system, I learn how things work better, remember it better, and end up with documents to help myself and others in the process. On Sep 3, 4:36 am, "Dustin Gooding" <[email protected]> wrote: > Kevin, > > You're freakin me out. I did extremely similar things last night... Even > editting action.edit to adjust the HxW of the edit window... To the same HxW > of yours.... Get out of my head!! :) --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "BoltWire" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/boltwire?hl=en -~----------~----~----~----~------~----~------~--~---
