Well, It Worked For Me
-
It Worked for Me on SMB IT Journal
Latest article is up, obviously inspired by many conversations that were had today elsewhere. This is one that I have needed to have written for a while but I have finally gotten around to it. Criticism is good, of course, I'm posting here first so that there is a chance to proof it a bit more. Has not been through an editor since it is so late at night so I am anticipating stuff to be found tomorrow
-
I'm not a writer by any stretch, but this phrase seems 'odd'
That’s not proof, but anecdotally it suggests that the risk figures are unlikely correct.
I think 'likely incorrect' sounds better - but I'm not entire sure it has the same meaning you are going for.
-
Third paragraph there case should be their.
-
Is is based on logic or irrational amygdala emotions? in the last paragraph should be 'Is it'
-
Thanks guys. I'll try to fix tonight.
Any feedback on the content?
-
I really like it. And you're right, we have all at least thought this in the past. I think I've grown enough to the point where I rarely if ever actually say it.
The biggest retort that I might have is that some employers, perhaps many, do judge harshly upon bad decisions not caring that it's reality. This judgement lead people to extreme fear/stress about their job status, and the desire for over the top ass covering. I definitely agree that we can't really grow as well in that situation.
-
@Dashrender said:
I really like it. And you're right, we have all at least thought this in the past. I think I've grown enough to the point where I rarely if ever actually say it.
The biggest retort that I might have is that some employers, perhaps many, do judge harshly upon bad decisions not caring that it's reality. This judgement lead people to extreme fear/stress about their job status, and the desire for over the top ass covering. I definitely agree that we can't really grow as well in that situation.
@scottalanmiller great read! I thought there was a little fat, but it was very well written in your own style and sucked me in. The entire thing fit well into a good understandable concept that was easy to read. Edit: and insightful/informative for sure
@Dashrender I think a lot of that comes from solely metric-driven institutions that don't have a good grasp on the people in them. I agree; I'm all for "CYA" but only to a point, i would much rather employ a person that says a lot of "I" instead of "He/she/they". Now, where'd that article go I read about this....
-
I, personally believe that most SMBs operate this way - people fear for their jobs - Bigger companies tend to understand better that mistakes happen, understand them, grow, and move on. It's only after you fail continually that they generally wonder if you should be there or not....but smaller companies allow themselves to be run more by emotion.
-
@Dashrender SMBs rules by emotion. I totally agree but never thought about it in those terms.
-
SMBs might rule by emotion but I don't have ALL the details or insight to give an answer. Let me make some calls first before I reply back. Hold on guys.
-
Read the article, saw the posts. Emotions tend to trump logic too often when trying to have technical discussions. Emotions often trump logical decisions in the workplace and you see this happen a lot in smaller IT shops / SMB's. While something may work, it doesn't mean that it's correct but at the same time, every situation is different and sometimes doing it 100% right isn't always possible due to the emotions and politicking that has to go on. I fight it everyday myself. It's taken me over a year to finally get buy in that a firewall appliance was actually causing most if not all of some network issues I would have with a VPN. Same excuse, "well, it works for me, must be your config." when no, it's the overall throughput for the VPN, the firewall, and for the LAN / WAN. Did I continue to work? Yes. Was it working properly? No, not at maximum efficiency but that's the card I was dealt.
I've seen this a lot myself in many environments I've been in over the years. The best any IT pro can do when faced with these challenges is to document the requests to do it the "correct" way, and then be prepared to have a fallback or two or three. You gotta know how to make things work when given a box of tools and a problem to solve, you have to know what the tools are, what their purposes is, how to use them and when to use them as well as when not to use them.
Sorry if this contains too much anecdotal language, I'm tired and was just typing what came off the top of my head.
-
@scottalanmiller said:
obviously inspired by many conversations that were had today elsewhere.
What conversations were these?
I think what you call “Anecdotal Dismissal of Risk.” is generally referred to as the outcome bias
-
@Carnival-Boy said:
@scottalanmiller said:
obviously inspired by many conversations that were had today elsewhere.
What conversations were these?
I think what you call “Anecdotal Dismissal of Risk.” is generally referred to as the outcome bias
You are correct.
