Difference between revisions of "User talk:Martin"
| Line 1: | Line 1: | ||
| + | [[FabLab.co.za]] | ||
| + | |||
{{RightTOC}} | {{RightTOC}} | ||
Revision as of 18:01, 18 June 2007
In general I am a student of “process”. I try to observe and understand what really makes things tick. This has relevance to transparency, democracy, and empowerment issues. Sometimes the most important things for the populace to know, are things that some relatively “few” people within the populace don’t want others to know. When students of process are observing and trying to understand your process, they risk being viewed as a pain in the neck – it’s not an activity where one should expect to get lots of “high fives”.
Some subjects that catch my interest are listed below:
Contents
Topsoil
Process Transparency
RiskParticipation
BetterAutomation
talk page etiquette
DesignerSearchScott
Solar Energy Investment Fund
Six messaging areas
Corporate Positioning
Thoughts On Vision
SuggestionBox
User Interface - edit box
Currently at a Wiki page one clicks “edit”, then waits for the edit page to pop up. The fact is the edit page does not look like the prior page. One makes the edit, then clicks “save”. Then one waits, and often reads the final page to see if it “looks right” – and sometimes notices a minor typo – then goes back to repeat the process. This is really not an efficient process. A more efficient process is to be looking at the page, and never have its format change (as when the edit page pops up), and be able to start typing, and “what you see is what stays on this page”. Why can’t the systems assume that the typed content will be saved – for if that was not the intend, why would one begin typing in the first place? If one makes a mistake and does not want their text saved, then should come the command mode to erase the just typed contents, or perhaps to then highlight the content one does not want saved, and click “delete”. For my brain type the process described above is more intuitive and faster.