Basics of Design 1: Objective Needs

Thankfully, the majority of the project design process is basic common sense. The first and foremost need is simply, what will it do? This question is foundational to all of our starting points: what, who and how.

What function(s) does the project need to fulfil?

The more details you are able to provide in each question, the easier your final assessment will be. Don't stop at "My computer desk needs to hold my computer." Think through each specific function that your desk will require. Sure, it needs to hold your computer. Is it a laptop, or a desktop with a tower? If it is a tower, will your desk need a side cabinet in order to hold it? Will your desk need a drawer for the keyboard or writing tools? You get the idea. Listing each and every need, and keeping them organized if the list gets long, will go a long way towards helping you to narrow down the function of your project.

Who will use your project?

The "who" question helps to refine and round out your "what" section. If you are making a computer desk for yourself, then your requirements are fairly easy to track and accomplish. However, if you are making something which others will use, such as a table or chair, then it becomes important to keep the other persons' needs in mind. For instance, even though a typical dining table is about 30" tall, I chose to make mine at 31.5" because I hate sitting at short tables and knocking my legs against the aprons. You must consider your end user. There is a significant chance that in considering your customers needs, your function list may need to be altered.

How does it need to fulfill its function? Are there any restrictions?

This last question is the more interpretive of the three - the first two questions address the direct, literal needs of the project. The third question asks how those needs must be accomplished. Ignore appearance for now; simply consider the functional, mechanical needs. A simple dining room table can be deceiving in its functions. A table can still have leaves to insert or remove, or company boards to add to each end. Leaves require table slides, and company boards require removable supports. Even our computer desk example would have great examples. If we know that the computer desk needs to work with a robust desktop style computer setup, then it makes sense that the desk needs to have cable management built in. Style, appearance and other flavors will come later. The critical part is taking the known need, and taking it to the next step of necessary components.

If I were to take these three questions and actually engage with them for a project, it might look something like this:

Built-In Humidor Cabinet

1. What does it need to do?

   1. Primary: securely store cigars in a moisture and temperature controlled environment

      1. Secure: locking doors

      2. Store: shelves, drawers

      3. Moisture: electric plugs for interior humidifier unit, access to unit

      4. Temperature: circulation fans to move air; negative space to allow air movement

      5. Control: gasketed opening seams, to limit environment loss

   2. Secondary: allow ease of maintenance and ease of access to all storage

   3. Tertiary: electrical features - interior LED lighting and circulation fans

2. Who will use it?

   1. Homeowner - requests pull out drawer or shelf to hold humidification unit, for easy refill

      1. Dimmable LED lighting on separate wall switch

   2. Guests - no current considerations beyond homeowner

3. How

   1. Locks: half-mortise

   2. Shelves / Drawers: adjustable, rollout shelves. Soft close glides

   3. Moisture / Temp: held by humidification unit

   4. Electrical:

      1. Interior LEDs - wiring through cabinet to wall switch; low voltage to standard 110 conversion

      2. GFCI Outlet - powers fan, humidification unit; run to ground plug, engage plug into wall outlet

In the next post, we will begin to decide the form of the project - the subjective appearance, based on preference.