Um, you're kind of making my point. Those orgs which don't use (utilize?) IT correctly will suffer relative to their competitors. It's just that 'correctly' hasn't been well defined yet.
I do think that DBAs are part of IT. Don't confuse sysadmins with IT - sysadmins are a subset of IT, as are DBAs and programmers who support internal functionality, as opposed to those who fulfill other, usually customer-facing, roles. I grok his distinction between CPAs who handle the customers and CPAs who handle, for instance, the firms tax returns. On Tue, Dec 1, 2009 at 19:40, Jon Harris <[email protected]> wrote: > Sorry I hit the send button to soon. > > Your biggest mistake and one he is counting on in my opinion is use of > intelligent and executives to define a person that will make the decisions. > How many of us have had to deal with executives that only use one metric to > make decisions? How many of us have wondered how these executives got to > their positions with so little evidence of intelligence seen in their > decisions? I have been lucky to work with truly intelligent executives. > Most of the ones I have had to deal with though are not all that > intelligent. Kurt is right though the definition of who is actually an IT > person needs to be better defined. I would argue that a DBA is not a true > IT person. Any more than the person who enters the data into the database. > > Jon > > On Tue, Dec 1, 2009 at 10:30 PM, Jon Harris <[email protected]> wrote: >> >> Your biggest mistake and one he is counting on in my opinion is use of >> intellegent and executives to define a person that will make the decisions. >> How many of us have had to deal with executives that only use one metric to >> make decisions? How many of us have wondered how these executives got to >> their positions with so little evidence of intellegence seen in their >> decisions? >> >> On Tue, Dec 1, 2009 at 9:53 PM, Kurt Buff <[email protected]> wrote: >>> >>> Well, it's a little more complicated than just Ya, or +1. >>> >>> I think he needs to refine his thoughts a bit more. The definition he >>> comes up with is a bit vague, and needs more discussion, as do some of >>> the examples he uses. In particular, some will wonder *why* it's not >>> an IT job for a DBA to "pull financial reports" - he needs to clarify >>> and defend that and other examples, to sharpen the discussion for >>> those who aren't particularly IT-competent. >>> >>> Also, he needs to highlight that the responsibility of producing >>> corporate IT policy works in both directions. The policies need to >>> server the mission of the organization, but they also need to be >>> informed by the best judgment of IT, both about security and about >>> technical possibilities. >>> >>> Plus, he needs a better copy editor. Some of his locutions are >>> cringe-inducing - for instance, he uses 'hedge' when he probably means >>> 'hinge' >>> >>> Like I said - no answers, just the beginning of a discussion, and >>> worthy of handing off to clueful execs. >>> >>> Kurt >>> >>> On Tue, Dec 1, 2009 at 17:53, Steven Peck <[email protected]> wrote: >>> > It's hard to have a conversation when everyone agrees. You have a >>> > mutual 'Ya!' fest instead. So... >>> > >>> > >>> > Ya! >>> > >>> > On Tue, Dec 1, 2009 at 5:05 PM, Kurt Buff <[email protected]> wrote: >>> >> I think this might prove an interesting conversation... >>> >> >>> >> >>> >> http://www.computerworld.com/s/article/9141609/Opinion_The_unspoken_truth_about_why_your_IT_sucks?taxonomyId=14&pageNumber=1 >>> >>> ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ >>> ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~ >>> >> > > > > ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~
