Wednesday, August 01, 2012

Over Complicating

I've had another wide-ish gap in posting. I don't think I've had anything to say. I think I should change the name of my blog to "The Grumpy Old Man" because the only urge I get to blog now is when something annoys me.

So, today's annoyance is at work. We get new sets of codes used for medical billing once a quarter. The process involves 4 people. Person #1 gets the data from 3M and puts it out on an FTP. Person #2 (me) validates the integrity of the data, and then loads it into the database which exists only to do this process. Person #3 builds the patch, and Person #4 is SQA, which reviews everything and makes sure we didn't miss any of the details. Person #1 coordinates the testing of the patch at a few of our test sites, which are hospitals. Once that's done, the patch is released to all hospitals.

I got an email from a new manager that is involved with our group. I had sent her an over view of how this process is done. It contains 10 steps. She turned it into a "mind map" and wants an hour of my time to discuss it. A "mind map" is... oh fuck it, I'll just show you what she sent me.

First, this was my 10 step process list.

With all quarterly update we have the following process:

1. Validate the data that we receive from the SDO
2. Load the data into the Lexicon and coding systems files
3. Validate the Lexicon content and relationships
4. Internal test by STS analysts
5. Build patch
6. Load patch into second account (different to where patch was developed)
7. Internal tests by STS analysts in second account
8. Send patch to SQA
9. Once given the OK by SQA send the patch to the test sites
10. At the same time as the patch is sent to the test site send the quarterly update reports to Austin

This is the mind map. You can click it if you really want to see what it looks like, but it's not that important.

This is an example of what happens when you put somebody who recently got an MBA into the mix. They over think a straight forward process, the steps of which can easily be documented. You end up with diagrams of things which are useless.

Essentially, we assembly line the patch, and worker bees on the assembly line don't need bubbles to describe what we do. The least important person in the entire process is the one that gets paid the most.. that is.. the person that makes bubbles.

There has probably been 500 Dilbert comics done about this sort of thing.


Kor said...

Bet that was done with mind manager software :D

On a completely unrelated notes, I think I just came up with the answer to your "invent something that will sell hotcakes to morons" problem.

You need to develop a mobile phone OS and market it as the only pro-traditional marriage phone on the market. All those Chic-Fil-A supporting fuck wits will line up in droves to ditch their pro-homo iPhones.

Steve said...

That mind map seems to make it a lot easier to understand to me.

I mean steps... that's so 2005.

Also, I love the part where it says "to the Austin"