Business is king. Customers rule. Service is everything. Yet every organization I go into has an engineering group that can't see outside their bubble. Perhaps they can, but they certainly choose not to.
I'm an engineer, I write code. I've written approaching 100k lines of C code in my life time, I've administered tens of thousands of systems in my career and I've help plan some of the largest customer-facing infrastructure ever built. I've learned a tremendous amount about technology and the hubristic nature of engineering teams. The most important take away from all of this? The technology doesn't mean anything unless it enables business by providing better service to customers.
Now, I realize that when I rant about this to technology folk, they emphatically agree. But, I'm tired of the lip service. People today in architecture, engineering and operations say again and again that their focus on enabling better customer experience. It's a nice sentiment, but every time I dive into someone's instrumentation and monitoring, I see an absolute vacuum when it comes to non-IT data.
The obvious things like financial and customer service metrics are missing, but so are all the more subtle things. Hiring is hard; finding and retaining talent is challenging; providing good benefits that add value and increase job appeal is a competitive task. All of these things are critically important to the organization as a whole (and specifically engineering and IT) and yet they are completely absent from the "monitoring" within the organization.
The truth is that there is absolutely critical telemetry coming from every facet of your organization. All of this telemetry is either directly related to providing better service to customers or directly related to providing better service to your organization itself which, in turn, stabilizes the platform on which you deliver products and services. Of this, I shouldn't have to convince you and I find that no convincing of the general population is required. Yet, here we are with almost every organization I see standing blind to this vital information.
Don't get me wrong, I don't think technology isn't a first-class component of today's (and tomorrow's) organizations. In fact, I think the technology group has been applying radically advanced techniques to telemetry data for years. It's high time that these techniques and tools were applied to the organization unabridged.
There is a profound shift in data transparency and accountability coming to the organization to tomorrow. If you don't buy in, you'll simply fail to achieve the agility and efficiencies of your competition. I'm here, with Circonus, to make that happen.
Business is king, not engineering. The difficult (but exceptionally simple) shift of engineering's focus from serving itself to serving the business as a whole will remake IT as the engine of the organization. As soon as you embrace this shift, technology will be the most powerful tool your organization has at its disposal.
Monday, August 27. 2012 at 12:11 (Reply)
I would say resistance often does not just come from engineering but also other departments. So even if IT started to focus on the business they would be blocked in their attempts.
Monday, August 27. 2012 at 12:48 (Link) (Reply)
The biggest impediment, particularly in the Fortune X00 crowd is users/business analysts insisting that any new or ported application look and act just like the character mode/terminal system being replaced. After all, today's user learned it from their predecessor, who learned it from their predecessor, and so on.
The result for those in the RDBMS venue, is that 1960s data structures persist, even among folks who self-identify as database gurus. The lapping up of NoSql stuff as innovated (even by some of those self-same self-identified gurus) is proof that IT has walked through the door into a Dark Age or Twilight Zone. We get yet more siloed applications using language centric (and constrained) "integration" with other siloed applications. It is a wonderment.
Monday, August 27. 2012 at 15:57 (Reply)
Business people seem to lack understanding that software development costs money. Currently I am tasked with writing software that interfaces to another businesses API. Due to our recent acquisition what service provider we are with is in question. However no one seems to think the money currently spent on me doing this with a web service we may drop is important. Even though in the past we blew $$$ on a service that would have cost millions for us to start using. Business also forgets that IT needs to be part of their decisions. In other words completely ignoring engineering is a bad idea, and vice versa.
Monday, August 27. 2012 at 18:53 (Link) (Reply)
Business forgets this because IT doesn't stay engaged with them in a business-level conversation. When business spends big $$$, it is because the person selling it can communicate with them. Just imagine if you could deliver *and* communicate!
Friday, August 31. 2012 at 14:56 (Link) (Reply)
I just like the valuable information you supply in your articles.
I'll bookmark your blog and test again right here regularly. I am reasonably sure I will be informed a lot of new stuff proper here! Good luck for the next!
Tuesday, August 28. 2012 at 13:18 (Link) (Reply)
Excellent thoughts.
One of the things I have seen all too often is actually a very simple issue: the engineers don't understand the problems they are trying to solve. If you put a programmer with no accounting experience in charge of writing accounting software you will get an unusable stinking pile of crap. Yet we respond to this problem not by ensuring proper cross-training of engineers but rather by lowering our expectations of the engineering.
This has to stop. Engineers aren't just paying you lip service. They are tired of this too. They just can't see the solution because they never get a chance to really operate outside of their bubble.
The simplest solution would be to require that the engineers and developers actually do the work they are trying to enable for at least a few weeks before starting to build their solutions. On the other hand cost accountants don't see the value there....