Every building teaches us something.
A failed seal. Deteriorating caulking. An unexpected access challenge. A repair that lasted. One that didn't. A condition that changed between visits. A question from a property manager that made us look at something differently.
Over time, those experiences become knowledge.
But we don't believe that knowledge should end with the project.
It should be remembered.
It should be questioned.
It should be refined.
And when it's useful, it should be shared.
Throughout our careers, we've learned from technicians, supervisors, trainers, property managers, engineers, tradespeople, manufacturers, and others who were willing to share what they knew.
Sometimes that happened through formal training.
Sometimes it was a conversation on a rooftop.
Sometimes someone showed us a better technique, pointed out something we'd missed, explained why a material behaved the way it did, or shared a lesson they learned the hard way.
Those moments shorten learning curves.
We believe there's a responsibility to create more of them.
People can spend decades learning how to do this work.
They learn how buildings behave, how equipment performs, which warning signs matter, which questions to ask, and how to recognize when something doesn't quite look right.
When an experienced person leaves a company or eventually retires, someone else can fill the position.
But everything that person learned isn't automatically replaced.
That's why we believe experience should be discussed, documented, taught, and passed on.
Not everything can be captured in a procedure.
But valuable lessons shouldn't disappear simply because nobody took the time to share them.
Experience shouldn't be used to establish hierarchy.
It should shorten someone else's learning curve.
We want experienced technicians to teach what they know and newer technicians to feel comfortable asking questions.
And knowledge doesn't only travel from the most experienced person to the least experienced one.
Equipment changes. Techniques improve. Standards evolve. New people ask questions experienced people may have stopped asking.
Sometimes the person with less experience brings the better idea.
The goal is to preserve what we've learned without becoming convinced that we've finished learning.
Knowledge isn't only valuable to technicians.
Property managers, condominium boards, building owners, facility operators, engineers, and contractors all make decisions about buildings.
The more useful information available to those decisions, the better the conversation becomes.
That's one reason we created Building Insights: to share practical observations, maintenance knowledge, lessons from the field, and the thinking behind how we approach exterior building work.
We don't expect everyone who reads it to become a Vertex client.
That's not the point.
If an article helps someone understand a building better, ask a better question, recognize a developing condition, or make a more informed maintenance decision, it has done something useful.
Procedures, checklists, inspection records, training materials, and safe work practices help preserve information and create consistency.
But creating documents isn't the goal.
Using them is.
A procedure should help someone understand the work.
A checklist should help prevent something important from being missed.
An inspection record should preserve information that may matter later.
A training resource should help someone become more capable.
If documentation isn't useful to the people expected to use it, then the documentation needs to become better.
As our own systems and resources develop, there may be things worth sharing beyond the company.
That could include:
These resources aren't substitutes for formal training, engineering, manufacturer requirements, regulatory requirements, or competent professional judgment.
They're simply another way to contribute useful information.
We hope Vertex is eventually known for more than the buildings we've worked on.
We'd like the company to leave behind better technicians, useful resources, shared experience, better questions, and knowledge that continues to help people long after a particular project is finished.
That's a long-term goal.
We're still building toward it.
But if years from now the industry is a little better because Vertex existed because something we taught, documented, shared, or learned helped somebody else do better work — we'll consider that something worth being proud of.
Someone taught us.
We'll keep learning.
And we'll pass on what we can.
Good information leads to better decisions.
We use cookies to analyze website traffic and optimize your website experience. By accepting our use of cookies, your data will be aggregated with all other user data.