Afterthought in Architectural Designs

When something is thought of or implemented just after the general plan is already concluded with, it is an seen as an Afterthought.

Afterthought means you didn't include it in your thought and planning process only to include it when the project is partly or fully done with.

Have you ever prepared a meal before and forgot to add salt only to realize it when the meal is already served? 

If you then start adding salt (which is needed but was forgotten) in an already served meal, the result of your action is then said to be an afterthought. 

This simply means that afterthought is encountered most times when a planner/designer or whosoever forgot what is needed (or what he thinks should be in a place) only to attach it when the design has gone pass that stage.

Here is a Google search of "afterthought in architecture"; though most on the list might just be a call to action of what shouldn’t be an afterthought. 

And since architects do more of critical thinking well solving problems; in fact they create from their imagination. 

So if he creates in his mind and transfers it to the paper only to remember he forgot to add something or maybe adding a particular thing will make the design even better that's already an afterthought and might be visible in the design.

Architects do encounter this mostly during the sketch period. At this stage it won't cause much problem.

But when the design moves from just a sketch to a working drawing, the effect causes more problem.

In a nutshell afterthought can go more badly for an architect if we consider the below stages in an ascending order.

Starting Sketch - working drawing - construction period - after construction. 

The hardest stages to implement an afterthought is during and after construction work is done.

Just as in other fields, afterthought can be seen in various planning and application processes within architectural practices. 

 Implementing afterthoughts in your design, during and after construction presence serious difficulties mostly.

One of these is that it presents a greater level of difficulty than should if considered and implemented earlier enough. 

An example is when you are designing a residential building and you finally realized that you didn't add the visitors convenience which you are supposed to make provisions for and then you strategically finds a place to attach it.

Such spaces usually look odd when an experience architect or designer reads the plan. It doesn't flow with the other spaces. 

You will encounter afterthought and afterthought look-alike much in architectural schools. Where unexperienced students still learning to design produce funny floor plans and other drawings.

Is afterthought bad?

We won't  say generally that afterthoughts are bad, but we can classify it into two presenting the good and the bad side.

In fact most times things that suffer within the afterthought sphere are vital part of the design needed for better flow, functionality, aesthetic, etc.

The reason afterthought around be greatly avoided is that it pops ups this vital things late.

So we will say that the things thought of are most time good but when it was thought of can have a very big negative effect on the project making it bad.

Who encounters afterthought?

Everybody, even outside the building industry, if what should make a design, model, production, etc. better is thought of late, it is an afterthought.

How do one avoid afterthoughts?

You can avoid being forced to attach features to your next project that will make it look less professional by observing the below. 

But don't get the whole concept wrong, it's not totally out of it to realize afterward one or two ideas that would have been great in your project.

What we are trying to achieve here is the satisfaction that what you already have should to a great extent serve the purpose irrespective of any new idea. 

Isn't that great? Let's look at the list below:

1. Be acquainted
2. Understand the project
3. Patience 
4. Cross-check 
5. Ask a junior or senior colleague

1. Be acquainted 

You must be knowledgeably enough in your profession to avoid encountering afterthought often.

You should know, understand and have handy things you need to make a project work when putting down your ideas in a drawing/written form. This will help you avoid getting a reminder afterwards. 

2. Understand the project

How else do you intend on starting a project if you don't first understand the requirements. The deeper you understand the project itself the better you are likely to deliver. 

If you are already good in your profession that's good, but to apply what you have within, you must first understand the problem. 

The problem for architects can come as the clients brief, site details (location, wind and sun directions, soil type, etc.), local building codes, and so many others. 

The more you know, the more you can consider during the design process and the more likely it is to avoid afterthoughts.

3. Patience 

You must be Patient enough to put things in place during the design period before you jump into construction or production. 

Make sure you don't rush processes especially as a beginner. 

Some problem might not be resolved after the last result; so why rush? The more you dive deeper in your profession the easier it will be to add greater speed and complete more projects faster.

3. Cross-check 

Crosschecking is simply going through what you have already done so far to see is there are mistakes, things missing, unnecessary things added, new ideas to implement, etc. 

Crosschecking requires patients. You may not find it easy revisiting what you are already done with, but it's worth it.

4. Ask a junior or senior colleague 

Oh yes! ask colleagues questions irrespective of their level, lower or higher than you, just ask.

The benefits of asking questions and getting befitting answers can not be over emphasized. Asking the right persons the rights questions per time will be of great help to stay out of afterthoughts.