Organizing Data: Part 1 ![[Registration never required for free content]](/images/free.gif)
By: Joel Martinez on Monday, June 20, 2005
Reader Level: 
Ever since I began my career as a programmer, I have been asked time and time again to create applications to organize data, provide workflows, execute business processes. Only through the magic of time have I come to realize that I implement the same code over and over. Approximately 99% of business applications written are variations on the same structure and navigation. Once you realize this, several things are accomplished.
- Less time deciding "how the app is going to look". After collecting and analyzing the requirements, you already have a template of sorts you can use for the various screens.
- The ability to more easily estimate how long a screen will take.
- Usability ... once users have been trained on how a certain screen works, they will be able to intuitively figure out the next app if it looks and feels the same.
Now, I'm not talking about visual design here ... I'm referring to things such as navigation, workflow, instructions. Effectively organizing data and information is an important skill which will give you a lot of bang for your development buck. I will touch on a few of these topics in detail and give some examples of what you can do to build up a repertoire of "app design templates" in this, the first of a series on organizing data and information.
The Information Architecture Series:
Organizing Data: Part 1
Information Architecture: Part 2 Coming Soon
