As engineers, we have a love-hate relationship with cost.
On the one hand, we like to start with a clean sheet of paper and dream. What if cost didn’t matter at all? What could we build? But also, cost is one of those existential variables that helps bound the problem.
Sometimes, boundaries are just limitations that must be engineered around — The river flow has this range of characteristics.
But many times, the boundaries on the problem are what push creativity and technology in a direction that leads to a better overall solution. Even better than without boundaries — Screen real estate limitations lead to better user interfaces.
Cost can be either. Sometimes, we know the budget, and then that budget is just a limitation to engineer around. Engineering effort stops when we meet the budget. Sometimes, however, the cost becomes the main thing. Minimization without expense to function, performance, and perception is worth the effort.
When designing, we often trade cost for time, responsibility, and perception, if even subconsciously. We look around at what already exists and start there.
However, what if we throw those assumptions out the window and return to the first principles of what we’re trying to make and for whom?
We can use this service to get us started quicker. OK, but could we do it better ourselves?
If we use this provider for this part, they will take responsibility if it breaks. OK, but do we care?
We want to put “ISO certified” on our website. Do we? Does it actually matter?
Questioning every cost can be exhausting, but it can also be liberating.
