My colleagues tease me sometimes over the words I choose. I used the phrase, “…of that ilk” (meaning other matters that are similar) and my co-worker nearly lost his cool, telling me that it makes us sound old. I remember another project meeting, where I said, “A watched pot never boils,” then tried over the next ten minutes to explain the idiom. Shoot-probably the word “idiom” is forbidden too. Oh well. I can be flexible. But on some matters, we do not flex. These matters are the Basics that Build Trust. With Hedgerow Software I joined my tribe, a high-performing technical team focused on Environmental Health. I was welcomed and put directly to work. I’ve been on the job close to 90 days. 

basics that build trust within environmental health

In the first thirty days, I watched for the Basics that Build Trust. Among these, honesty, hard work, a willingness to really learn. And, as you know, there is so much to learn. No two environmental health departments are the same, even close neighbors. 

In the next thirty days, I launched my own projects (with assistance). From this vantage point, I got to apply some of my favorite basics. For example, we don’t fuss with inefficient meetings. Project communication is universal (everybody gets all emails, facilitated by an email group). We value action over handwringing, because seeing your facility data in the Hedgehog Platform for the first time is akin to feeling “halfway there.” It’s true. 

Other matters coming down the line that we can predict? Prioritize report design. For so many environmental health professionals, the “piece of paper” is the work product, whether that is an inspection, permit, invoice, or letter. Your system is nowhere near complete if it doesn’t produce the artifacts that memorialize the work. 

Also, empower the staff to define and execute their own tests. Why not let the vendor do it? Two reasons: (1) only your staff knows the whole truth about your services and expectations; and (2) sweat equity. This is why I wholeheartedly recommend that staff do, test, and train others on the core configuration of a technology application.

Finally, there’s always something cooler right around the corner. To hold up your project in favor of waiting for the “next version” is foolhardy, because there will always be a “next version.” As with before, we value action over handwringing. Action means “getting to done.” Perfect can come later.

So, this is what it means to join my tribe. We’re aligned, customers and staff, and that’s rare enough that I think about it a lot. What else have you seen that works well to build trust and project success? Connect with me on LinkedIn and send us your ideas.