I have the privilege of working closely with several of our software vendors to help them improve their products, both for our use and for their entire client base. Through this collaboration, I’ve discovered some fascinating correlations between software development processes and business development processes. These similarities have significantly influenced my perspective on development across various areas.

When we sat down to define our core values, we started with a long list. As we worked to refine it, we realized that many values were actually distillates of others. For example, we see honesty as a distillate of integrity. This led us to focus on identifying root values that drive all the others. That’s how we arrived at the concept of Impact.

Growth is a fascinating concept. On one hand, it’s an obvious value for any organization. On the other, it’s often overlooked, with many companies spending significant time figuring out how to achieve it.

For us, growth isn’t just a goal—it’s an outcome. We believe that by doing the right things for the right people and for the right reasons, we help our clients grow, which in turn drives our own growth. Thus, growth is a necessary outcome of our actions.

Thinking Outside of the Box is a phrase we often hear, but truly embracing this mindset can be challenging. The very notion of a “box” suggests limitations, yet the practice of thinking beyond these constraints is essential for the growth and innovation of both individuals and organizations. Without mastering this skill, how can we achieve breakthrough ideas and advancements?

In the fast-paced world of IT, it’s easy to lose sight of what’s truly important. We all have core values, but the daily hustle can lead us to forget them or make small compromises that steer us off course. I face this challenge too.

There are countless resources on setting priorities, defining values, and maintaining focus. The key is to distill our focus down to specific, core elements and ensure everything aligns with these values. We must clearly define what is valuable to us and ensure every action ties back to that focus.

In the world of IT, we often think of integrity as a trait of character and integration as a feature of systems and processes. However, these two concepts are deeply intertwined.

When we say someone has “integrity,” we mean there’s a consistency between their words and actions. If they commit to being somewhere at 5 PM, they will be there at 5 PM. If they promise to complete a project by Thursday, it will be done by Thursday. Achieving this level of integrity requires intentional planning and execution. You need to account for variables and engineer situations to ensure consistent outcomes.

Back in July, I wrote a 2 part series on Demystifying the Cloud. You can find Part 1 HERE and Part 2 HERE. In parts 1 and 2, I talked through the different kinds of clouds, pros and cons and considerations for evaluating the cloud. While I definitely posted some opinion, I intentionally didn’t present a lot of opinion or speculation there. I have had some people asking for my take on the cloud, if it is right for them and where I see things going. So, back by popular demand, this is Part 3 of Demystifying the Cloud, where I’ll walk through my thoughts on the cloud.

One of the many areas where IT concepts dovetail well with the rest of the world is a conversation about whether you should use Best-of-Breed products or use a suite of products that optimally integrate with each other. This is similar to decisions we make in the rest of our life where we decide if we want the best possible individual product or if we want to pick the best collection of products that will work together optimally.

Back in June, I talked about how we celebrate failure in Here’s to the Crazy Ones. But, is changing our perspective on failure enough? Can we survive, emotionally or practically, in a state of constant failure?

In the last blog, we defined the cloud and talked about what it was and wasn’t, various types of the cloud and so on. In this blog, let’s build on that and talk about the kinds of metrics and considerations you should make when considering whether or not to go into the cloud.