How do you get your departments to quantify what they actually need for their jobs
-
@scottalanmiller said in How do you get your departments to quantify what they actually need for their jobs:
@DustinB3403 said in How do you get your departments to quantify what they actually need for their jobs:
@scottalanmiller said in How do you get your departments to quantify what they actually need for their jobs:
@DustinB3403 said in How do you get your departments to quantify what they actually need for their jobs:
Looking for some general advice on how you might address this so you can formulate a real business plan
Bill backs.... if a department pays for what they request, you don't care if they use it or not.
How do you bill back a department who doesn't have a budget? (honestly asking)
By not billing based on projects, base on orders.
Example:
Dept A demands 100TB of storage. IT has a TB cost for storage (maybe by performance tier.) Let's say 1TB of storage costs $1/mo. So if a department orders 100TB of storage, they have to pay $100/mo whether they use it or not.
THis is a standard model that pushes real costs to departments, and puts the onus on the departments to justify their expenditures. It also provides the CFO a look into profits and losses that they lack otherwise.
How does this work with the ultra conservative managers? I'd imagine it would translate into overhead for IT. Reverse the scenario.
Say in a 3 year period you calculate the need for 750 TB worth of expansion. The manger is unwilling to purchase 750 TB and instead purchases 250 TB because they don't want to pay the full amount until they will use it. Now you have three installs instead of one. I'd imagine this would be a problem with bigger companies.
-
@DustinB3403 said in How do you get your departments to quantify what they actually need for their jobs:
@Dashrender said in How do you get your departments to quantify what they actually need for their jobs:
@scottalanmiller said in How do you get your departments to quantify what they actually need for their jobs:
@DustinB3403 said in How do you get your departments to quantify what they actually need for their jobs:
Looking for some general advice on how you might address this so you can formulate a real business plan
Bill backs.... if a department pays for what they request, you don't care if they use it or not.
How is this not done on the norm anyway to verify that departments are in fact getting value for their purchases?
Because of dysfunction? I'm not the CFO and thus can't possibly answer that.
The question was for Scott - not you.. and well - it is in use according to his recent post...
If you do this for every department, it makes all your buying decisions so much less about IT, and so much more about the departments truly being involved in the financial levels of the company... which should make the better - hell, if the department shows it's really producing.. they might find that they can get even more things/stuff/money., etc.
-
@wirestyle22 said in How do you get your departments to quantify what they actually need for their jobs:
@scottalanmiller said in How do you get your departments to quantify what they actually need for their jobs:
@DustinB3403 said in How do you get your departments to quantify what they actually need for their jobs:
@scottalanmiller said in How do you get your departments to quantify what they actually need for their jobs:
@DustinB3403 said in How do you get your departments to quantify what they actually need for their jobs:
Looking for some general advice on how you might address this so you can formulate a real business plan
Bill backs.... if a department pays for what they request, you don't care if they use it or not.
How do you bill back a department who doesn't have a budget? (honestly asking)
By not billing based on projects, base on orders.
Example:
Dept A demands 100TB of storage. IT has a TB cost for storage (maybe by performance tier.) Let's say 1TB of storage costs $1/mo. So if a department orders 100TB of storage, they have to pay $100/mo whether they use it or not.
THis is a standard model that pushes real costs to departments, and puts the onus on the departments to justify their expenditures. It also provides the CFO a look into profits and losses that they lack otherwise.
How does this work with the ultra conservative managers? I'd imagine it would translate into overhead for IT. Reverse the scenario.
Say in a 3 year period you calculate the need for 750 TB worth of expansion. The manger is unwilling to purchase 750 TB and instead purchases 250 TB because they don't want to pay the full amount until they will use it. Now you have three installs instead of one. I'd imagine this would be a problem with bigger companies.
I'm pretty sure Scott is going to tell you that you don't buy for the future, because you really don't know what tomorrow brings. So likely you're going to do just that - buy 250 TB as needed, you might need if faster, you might need it slower. Sure it's possibly more work for IT, three installs - but theses are storage growths, you shouldn't require nearly as much work as the initial setup - design the system for growth, so IT has less using performing that growth.
-
@Dashrender said in How do you get your departments to quantify what they actually need for their jobs:
@wirestyle22 said in How do you get your departments to quantify what they actually need for their jobs:
@scottalanmiller said in How do you get your departments to quantify what they actually need for their jobs:
@DustinB3403 said in How do you get your departments to quantify what they actually need for their jobs:
@scottalanmiller said in How do you get your departments to quantify what they actually need for their jobs:
@DustinB3403 said in How do you get your departments to quantify what they actually need for their jobs:
Looking for some general advice on how you might address this so you can formulate a real business plan
Bill backs.... if a department pays for what they request, you don't care if they use it or not.
How do you bill back a department who doesn't have a budget? (honestly asking)
By not billing based on projects, base on orders.
Example:
Dept A demands 100TB of storage. IT has a TB cost for storage (maybe by performance tier.) Let's say 1TB of storage costs $1/mo. So if a department orders 100TB of storage, they have to pay $100/mo whether they use it or not.
THis is a standard model that pushes real costs to departments, and puts the onus on the departments to justify their expenditures. It also provides the CFO a look into profits and losses that they lack otherwise.
How does this work with the ultra conservative managers? I'd imagine it would translate into overhead for IT. Reverse the scenario.
Say in a 3 year period you calculate the need for 750 TB worth of expansion. The manger is unwilling to purchase 750 TB and instead purchases 250 TB because they don't want to pay the full amount until they will use it. Now you have three installs instead of one. I'd imagine this would be a problem with bigger companies.
I'm pretty sure Scott is going to tell you that you don't buy for the future, because you really don't know what tomorrow brings. So likely you're going to do just that - buy 250 TB as needed, you might need if faster, you might need it slower. Sure it's possibly more work for IT, three installs - but theses are storage growths, you shouldn't require nearly as much work as the initial setup - design the system for growth, so IT has less using performing that growth.
So if you're buying new servers you don't try to account for growth? You just buy exactly what you had?
-
@wirestyle22 said in How do you get your departments to quantify what they actually need for their jobs:
@Dashrender said in How do you get your departments to quantify what they actually need for their jobs:
@wirestyle22 said in How do you get your departments to quantify what they actually need for their jobs:
@scottalanmiller said in How do you get your departments to quantify what they actually need for their jobs:
@DustinB3403 said in How do you get your departments to quantify what they actually need for their jobs:
@scottalanmiller said in How do you get your departments to quantify what they actually need for their jobs:
@DustinB3403 said in How do you get your departments to quantify what they actually need for their jobs:
Looking for some general advice on how you might address this so you can formulate a real business plan
Bill backs.... if a department pays for what they request, you don't care if they use it or not.
How do you bill back a department who doesn't have a budget? (honestly asking)
By not billing based on projects, base on orders.
Example:
Dept A demands 100TB of storage. IT has a TB cost for storage (maybe by performance tier.) Let's say 1TB of storage costs $1/mo. So if a department orders 100TB of storage, they have to pay $100/mo whether they use it or not.
THis is a standard model that pushes real costs to departments, and puts the onus on the departments to justify their expenditures. It also provides the CFO a look into profits and losses that they lack otherwise.
How does this work with the ultra conservative managers? I'd imagine it would translate into overhead for IT. Reverse the scenario.
Say in a 3 year period you calculate the need for 750 TB worth of expansion. The manger is unwilling to purchase 750 TB and instead purchases 250 TB because they don't want to pay the full amount until they will use it. Now you have three installs instead of one. I'd imagine this would be a problem with bigger companies.
I'm pretty sure Scott is going to tell you that you don't buy for the future, because you really don't know what tomorrow brings. So likely you're going to do just that - buy 250 TB as needed, you might need if faster, you might need it slower. Sure it's possibly more work for IT, three installs - but theses are storage growths, you shouldn't require nearly as much work as the initial setup - design the system for growth, so IT has less using performing that growth.
So if you're buying new servers you don't try to account for growth?
you can, but you don't have to spend all the money today.
example - you buy a server, you buy a dual socket machine, but only populate 1 socket (assuming the job can get done with that) and you populate the second when it's actually needed, same goes for storage and RAM.
-
@wirestyle22 said in How do you get your departments to quantify what they actually need for their jobs:
@Dashrender said in How do you get your departments to quantify what they actually need for their jobs:
@wirestyle22 said in How do you get your departments to quantify what they actually need for their jobs:
@scottalanmiller said in How do you get your departments to quantify what they actually need for their jobs:
@DustinB3403 said in How do you get your departments to quantify what they actually need for their jobs:
@scottalanmiller said in How do you get your departments to quantify what they actually need for their jobs:
@DustinB3403 said in How do you get your departments to quantify what they actually need for their jobs:
Looking for some general advice on how you might address this so you can formulate a real business plan
Bill backs.... if a department pays for what they request, you don't care if they use it or not.
How do you bill back a department who doesn't have a budget? (honestly asking)
By not billing based on projects, base on orders.
Example:
Dept A demands 100TB of storage. IT has a TB cost for storage (maybe by performance tier.) Let's say 1TB of storage costs $1/mo. So if a department orders 100TB of storage, they have to pay $100/mo whether they use it or not.
THis is a standard model that pushes real costs to departments, and puts the onus on the departments to justify their expenditures. It also provides the CFO a look into profits and losses that they lack otherwise.
How does this work with the ultra conservative managers? I'd imagine it would translate into overhead for IT. Reverse the scenario.
Say in a 3 year period you calculate the need for 750 TB worth of expansion. The manger is unwilling to purchase 750 TB and instead purchases 250 TB because they don't want to pay the full amount until they will use it. Now you have three installs instead of one. I'd imagine this would be a problem with bigger companies.
I'm pretty sure Scott is going to tell you that you don't buy for the future, because you really don't know what tomorrow brings. So likely you're going to do just that - buy 250 TB as needed, you might need if faster, you might need it slower. Sure it's possibly more work for IT, three installs - but theses are storage growths, you shouldn't require nearly as much work as the initial setup - design the system for growth, so IT has less using performing that growth.
So if you're buying new servers you don't try to account for growth? You just buy exactly what you had?
Why would you ever buy exactly what you had? The reality here is that you're replacing for one of two reasons - aged out equipment or growth. Obviously in the case of growth, you're not buying the same thing - you clearly need more. But aged out equipment - do you really need more? heck your equipment aged out, meaning it's at least 5 years old, and could easily be 8+. Any server you buy today will crush that 5+ year old server and if necessary, should have plenty of room for expansion (in RAM and CPU) assuming you built it somewhere near the performance level of the old one.
As for storage - you might start with all internal storage - then you might move to DAS for additional storage, don't need another server (necessarily)
-
@Dashrender said in How do you get your departments to quantify what they actually need for their jobs:
@wirestyle22 said in How do you get your departments to quantify what they actually need for their jobs:
@Dashrender said in How do you get your departments to quantify what they actually need for their jobs:
@wirestyle22 said in How do you get your departments to quantify what they actually need for their jobs:
@scottalanmiller said in How do you get your departments to quantify what they actually need for their jobs:
@DustinB3403 said in How do you get your departments to quantify what they actually need for their jobs:
@scottalanmiller said in How do you get your departments to quantify what they actually need for their jobs:
@DustinB3403 said in How do you get your departments to quantify what they actually need for their jobs:
Looking for some general advice on how you might address this so you can formulate a real business plan
Bill backs.... if a department pays for what they request, you don't care if they use it or not.
How do you bill back a department who doesn't have a budget? (honestly asking)
By not billing based on projects, base on orders.
Example:
Dept A demands 100TB of storage. IT has a TB cost for storage (maybe by performance tier.) Let's say 1TB of storage costs $1/mo. So if a department orders 100TB of storage, they have to pay $100/mo whether they use it or not.
THis is a standard model that pushes real costs to departments, and puts the onus on the departments to justify their expenditures. It also provides the CFO a look into profits and losses that they lack otherwise.
How does this work with the ultra conservative managers? I'd imagine it would translate into overhead for IT. Reverse the scenario.
Say in a 3 year period you calculate the need for 750 TB worth of expansion. The manger is unwilling to purchase 750 TB and instead purchases 250 TB because they don't want to pay the full amount until they will use it. Now you have three installs instead of one. I'd imagine this would be a problem with bigger companies.
I'm pretty sure Scott is going to tell you that you don't buy for the future, because you really don't know what tomorrow brings. So likely you're going to do just that - buy 250 TB as needed, you might need if faster, you might need it slower. Sure it's possibly more work for IT, three installs - but theses are storage growths, you shouldn't require nearly as much work as the initial setup - design the system for growth, so IT has less using performing that growth.
So if you're buying new servers you don't try to account for growth?
you can, but you don't have to spend all the money today.
example - you buy a server, you buy a dual socket machine, but only populate 1 socket (assuming the job can get done with that) and you populate the second when it's actually needed, same goes for storage and RAM.
What I've seen is overbuying specifically for the calculated expansion needed for whatever the refresh plan is but yeah, I guess that is too much of an upfront investment.
-
@wirestyle22 said in How do you get your departments to quantify what they actually need for their jobs:
@Dashrender said in How do you get your departments to quantify what they actually need for their jobs:
@wirestyle22 said in How do you get your departments to quantify what they actually need for their jobs:
@Dashrender said in How do you get your departments to quantify what they actually need for their jobs:
@wirestyle22 said in How do you get your departments to quantify what they actually need for their jobs:
@scottalanmiller said in How do you get your departments to quantify what they actually need for their jobs:
@DustinB3403 said in How do you get your departments to quantify what they actually need for their jobs:
@scottalanmiller said in How do you get your departments to quantify what they actually need for their jobs:
@DustinB3403 said in How do you get your departments to quantify what they actually need for their jobs:
Looking for some general advice on how you might address this so you can formulate a real business plan
Bill backs.... if a department pays for what they request, you don't care if they use it or not.
How do you bill back a department who doesn't have a budget? (honestly asking)
By not billing based on projects, base on orders.
Example:
Dept A demands 100TB of storage. IT has a TB cost for storage (maybe by performance tier.) Let's say 1TB of storage costs $1/mo. So if a department orders 100TB of storage, they have to pay $100/mo whether they use it or not.
THis is a standard model that pushes real costs to departments, and puts the onus on the departments to justify their expenditures. It also provides the CFO a look into profits and losses that they lack otherwise.
How does this work with the ultra conservative managers? I'd imagine it would translate into overhead for IT. Reverse the scenario.
Say in a 3 year period you calculate the need for 750 TB worth of expansion. The manger is unwilling to purchase 750 TB and instead purchases 250 TB because they don't want to pay the full amount until they will use it. Now you have three installs instead of one. I'd imagine this would be a problem with bigger companies.
I'm pretty sure Scott is going to tell you that you don't buy for the future, because you really don't know what tomorrow brings. So likely you're going to do just that - buy 250 TB as needed, you might need if faster, you might need it slower. Sure it's possibly more work for IT, three installs - but theses are storage growths, you shouldn't require nearly as much work as the initial setup - design the system for growth, so IT has less using performing that growth.
So if you're buying new servers you don't try to account for growth?
you can, but you don't have to spend all the money today.
example - you buy a server, you buy a dual socket machine, but only populate 1 socket (assuming the job can get done with that) and you populate the second when it's actually needed, same goes for storage and RAM.
What I've seen is overbuying specifically for the calculated expansion needed for whatever the refresh plan is but yeah, I guess that is too much of an upfront investment.
Right - and how often do those growth projections fail? Far more than most want to admit. So save the money.
-
@Dashrender said in How do you get your departments to quantify what they actually need for their jobs:
@wirestyle22 said in How do you get your departments to quantify what they actually need for their jobs:
@Dashrender said in How do you get your departments to quantify what they actually need for their jobs:
@wirestyle22 said in How do you get your departments to quantify what they actually need for their jobs:
@scottalanmiller said in How do you get your departments to quantify what they actually need for their jobs:
@DustinB3403 said in How do you get your departments to quantify what they actually need for their jobs:
@scottalanmiller said in How do you get your departments to quantify what they actually need for their jobs:
@DustinB3403 said in How do you get your departments to quantify what they actually need for their jobs:
Looking for some general advice on how you might address this so you can formulate a real business plan
Bill backs.... if a department pays for what they request, you don't care if they use it or not.
How do you bill back a department who doesn't have a budget? (honestly asking)
By not billing based on projects, base on orders.
Example:
Dept A demands 100TB of storage. IT has a TB cost for storage (maybe by performance tier.) Let's say 1TB of storage costs $1/mo. So if a department orders 100TB of storage, they have to pay $100/mo whether they use it or not.
THis is a standard model that pushes real costs to departments, and puts the onus on the departments to justify their expenditures. It also provides the CFO a look into profits and losses that they lack otherwise.
How does this work with the ultra conservative managers? I'd imagine it would translate into overhead for IT. Reverse the scenario.
Say in a 3 year period you calculate the need for 750 TB worth of expansion. The manger is unwilling to purchase 750 TB and instead purchases 250 TB because they don't want to pay the full amount until they will use it. Now you have three installs instead of one. I'd imagine this would be a problem with bigger companies.
I'm pretty sure Scott is going to tell you that you don't buy for the future, because you really don't know what tomorrow brings. So likely you're going to do just that - buy 250 TB as needed, you might need if faster, you might need it slower. Sure it's possibly more work for IT, three installs - but theses are storage growths, you shouldn't require nearly as much work as the initial setup - design the system for growth, so IT has less using performing that growth.
So if you're buying new servers you don't try to account for growth? You just buy exactly what you had?
Why would you ever buy exactly what you had? The reality here is that you're replacing for one of two reasons - aged out equipment or growth. Obviously in the case of growth, you're not buying the same thing - you clearly need more. But aged out equipment - do you really need more? heck your equipment aged out, meaning it's at least 5 years old, and could easily be 8+. Any server you buy today will crush that 5+ year old server and if necessary, should have plenty of room for expansion (in RAM and CPU) assuming you built it somewhere near the performance level of the old one.
As for storage - you might start with all internal storage - then you might move to DAS for additional storage, don't need another server (necessarily)
They were widely viewed as successful but that is only because they stopped analyzing after implementation
-
@DustinB3403 said in How do you get your departments to quantify what they actually need for their jobs:
@Dashrender said in How do you get your departments to quantify what they actually need for their jobs:
@scottalanmiller said in How do you get your departments to quantify what they actually need for their jobs:
@DustinB3403 said in How do you get your departments to quantify what they actually need for their jobs:
Looking for some general advice on how you might address this so you can formulate a real business plan
Bill backs.... if a department pays for what they request, you don't care if they use it or not.
How is this not done on the norm anyway to verify that departments are in fact getting value for their purchases?
Because of dysfunction? I'm not the CFO and thus can't possibly answer that.
@DustinB3403 said in How do you get your departments to quantify what they actually need for their jobs:
@Dashrender said in How do you get your departments to quantify what they actually need for their jobs:
@scottalanmiller said in How do you get your departments to quantify what they actually need for their jobs:
@DustinB3403 said in How do you get your departments to quantify what they actually need for their jobs:
Looking for some general advice on how you might address this so you can formulate a real business plan
Bill backs.... if a department pays for what they request, you don't care if they use it or not.
How is this not done on the norm anyway to verify that departments are in fact getting value for their purchases?
Because of dysfunction? I'm not the CFO and thus can't possibly answer that.
Dysfunction may come about because the company only has so much money and if the charge back is a fixed cost, you can bet all departments will work VERY hard to be first in line to use up all of their fee first.
Add to that, you now have all department heads stating, "Hey, I paid my monthly fee, now give me what I want NOW! My department is more important than any other department" Thus more dysfunction within the company.
If you would like a good example of how charge backs can mess things up but have a slight potential of working, give "Keep the Joint Running: A Manifesto for 21st Century Information Technology" by Bob Lewis a read.
-
@pmoncho said in How do you get your departments to quantify what they actually need for their jobs:
@DustinB3403 said in How do you get your departments to quantify what they actually need for their jobs:
@Dashrender said in How do you get your departments to quantify what they actually need for their jobs:
@scottalanmiller said in How do you get your departments to quantify what they actually need for their jobs:
@DustinB3403 said in How do you get your departments to quantify what they actually need for their jobs:
Looking for some general advice on how you might address this so you can formulate a real business plan
Bill backs.... if a department pays for what they request, you don't care if they use it or not.
How is this not done on the norm anyway to verify that departments are in fact getting value for their purchases?
Because of dysfunction? I'm not the CFO and thus can't possibly answer that.
@DustinB3403 said in How do you get your departments to quantify what they actually need for their jobs:
@Dashrender said in How do you get your departments to quantify what they actually need for their jobs:
@scottalanmiller said in How do you get your departments to quantify what they actually need for their jobs:
@DustinB3403 said in How do you get your departments to quantify what they actually need for their jobs:
Looking for some general advice on how you might address this so you can formulate a real business plan
Bill backs.... if a department pays for what they request, you don't care if they use it or not.
How is this not done on the norm anyway to verify that departments are in fact getting value for their purchases?
Because of dysfunction? I'm not the CFO and thus can't possibly answer that.
Dysfunction may come about because the company only has so much money and if the charge back is a fixed cost, you can bet all departments will work VERY hard to be first in line to use up all of their fee first.
Add to that, you now have all department heads stating, "Hey, I paid my monthly fee, now give me what I want NOW! My department is more important than any other department" Thus more dysfunction within the company.
If you would like a good example of how charge backs can mess things up but have a slight potential of working, give "Keep the Joint Running: A Manifesto for 21st Century Information Technology" by Bob Lewis a read.
I don't think it needs to be super hard and fast to live and die by charge backs, that could be a CFO/exec level only thing... but then the CFO could look at a department who's asking for 750 TB of storage, and look at the history of that department and might come back and say - uh, yeah.. ya know.. we're going to get you that 750, but it will be staged over years - etc...
I also want to find a way to work in Dustin's - the departments don't cleanup their old shit - so storage just keeps growing - into this as well, but I'm not sure how.
-
@Dashrender said in How do you get your departments to quantify what they actually need for their jobs:
@pmoncho said in How do you get your departments to quantify what they actually need for their jobs:
@DustinB3403 said in How do you get your departments to quantify what they actually need for their jobs:
@Dashrender said in How do you get your departments to quantify what they actually need for their jobs:
@scottalanmiller said in How do you get your departments to quantify what they actually need for their jobs:
@DustinB3403 said in How do you get your departments to quantify what they actually need for their jobs:
Looking for some general advice on how you might address this so you can formulate a real business plan
Bill backs.... if a department pays for what they request, you don't care if they use it or not.
How is this not done on the norm anyway to verify that departments are in fact getting value for their purchases?
Because of dysfunction? I'm not the CFO and thus can't possibly answer that.
@DustinB3403 said in How do you get your departments to quantify what they actually need for their jobs:
@Dashrender said in How do you get your departments to quantify what they actually need for their jobs:
@scottalanmiller said in How do you get your departments to quantify what they actually need for their jobs:
@DustinB3403 said in How do you get your departments to quantify what they actually need for their jobs:
Looking for some general advice on how you might address this so you can formulate a real business plan
Bill backs.... if a department pays for what they request, you don't care if they use it or not.
How is this not done on the norm anyway to verify that departments are in fact getting value for their purchases?
Because of dysfunction? I'm not the CFO and thus can't possibly answer that.
Dysfunction may come about because the company only has so much money and if the charge back is a fixed cost, you can bet all departments will work VERY hard to be first in line to use up all of their fee first.
Add to that, you now have all department heads stating, "Hey, I paid my monthly fee, now give me what I want NOW! My department is more important than any other department" Thus more dysfunction within the company.
If you would like a good example of how charge backs can mess things up but have a slight potential of working, give "Keep the Joint Running: A Manifesto for 21st Century Information Technology" by Bob Lewis a read.
I don't think it needs to be super hard and fast to live and die by charge backs, that could be a CFO/exec level only thing... but then the CFO could look at a department who's asking for 750 TB of storage, and look at the history of that department and might come back and say - uh, yeah.. ya know.. we're going to get you that 750, but it will be staged over years - etc...
I agree that in Dustin's situation, it may not be so dire. Just in general, that is the possible dysfunction of charge backs. I've only been in a SMB area but I have seen CIO/CFO/CEO's (and their SMB equivalents) fight over money constantly. Yes, the C-levels will make the choice but only to the determent of the overall business.
I also want to find a way to work in Dustin's - the departments don't cleanup their old shit - so storage just keeps growing - into this as well, but I'm not sure how.
I have yet to find a way to do it here and will be watching this post for others who come up with an idea. FU*&#%@ PDF's for Credentialing bloat my file server. Worse than email attachments (grrhhhh).
-
@pmoncho said in How do you get your departments to quantify what they actually need for their jobs:
@Dashrender said in How do you get your departments to quantify what they actually need for their jobs:
@pmoncho said in How do you get your departments to quantify what they actually need for their jobs:
@DustinB3403 said in How do you get your departments to quantify what they actually need for their jobs:
@Dashrender said in How do you get your departments to quantify what they actually need for their jobs:
@scottalanmiller said in How do you get your departments to quantify what they actually need for their jobs:
@DustinB3403 said in How do you get your departments to quantify what they actually need for their jobs:
Looking for some general advice on how you might address this so you can formulate a real business plan
Bill backs.... if a department pays for what they request, you don't care if they use it or not.
How is this not done on the norm anyway to verify that departments are in fact getting value for their purchases?
Because of dysfunction? I'm not the CFO and thus can't possibly answer that.
@DustinB3403 said in How do you get your departments to quantify what they actually need for their jobs:
@Dashrender said in How do you get your departments to quantify what they actually need for their jobs:
@scottalanmiller said in How do you get your departments to quantify what they actually need for their jobs:
@DustinB3403 said in How do you get your departments to quantify what they actually need for their jobs:
Looking for some general advice on how you might address this so you can formulate a real business plan
Bill backs.... if a department pays for what they request, you don't care if they use it or not.
How is this not done on the norm anyway to verify that departments are in fact getting value for their purchases?
Because of dysfunction? I'm not the CFO and thus can't possibly answer that.
Dysfunction may come about because the company only has so much money and if the charge back is a fixed cost, you can bet all departments will work VERY hard to be first in line to use up all of their fee first.
Add to that, you now have all department heads stating, "Hey, I paid my monthly fee, now give me what I want NOW! My department is more important than any other department" Thus more dysfunction within the company.
If you would like a good example of how charge backs can mess things up but have a slight potential of working, give "Keep the Joint Running: A Manifesto for 21st Century Information Technology" by Bob Lewis a read.
I don't think it needs to be super hard and fast to live and die by charge backs, that could be a CFO/exec level only thing... but then the CFO could look at a department who's asking for 750 TB of storage, and look at the history of that department and might come back and say - uh, yeah.. ya know.. we're going to get you that 750, but it will be staged over years - etc...
I agree that in Dustin's situation, it may not be so dire. Just in general, that is the possible dysfunction of charge backs. I've only been in a SMB area but I have seen CIO/CFO/CEO's (and their SMB equivalents) fight over money constantly. Yes, the C-levels will make the choice but only to the determent of the overall business.
If the CIO/CFO is the one making the final OK - then there should be no determent to the business
-
@pmoncho said in How do you get your departments to quantify what they actually need for their jobs:
@Dashrender said in How do you get your departments to quantify what they actually need for their jobs:
I also want to find a way to work in Dustin's - the departments don't cleanup their old shit - so storage just keeps growing - into this as well, but I'm not sure how.
I have yet to find a way to do it here and will be watching this post for others who come up with an idea.FU*&#%@ PDF's for Credentialing bloat my file server. Worse than email attachments (grrhhhh).
Better than being in email in my mind. are you in medical?
-
@Dashrender said in How do you get your departments to quantify what they actually need for their jobs:
@pmoncho said in How do you get your departments to quantify what they actually need for their jobs:
@Dashrender said in How do you get your departments to quantify what they actually need for their jobs:
I also want to find a way to work in Dustin's - the departments don't cleanup their old shit - so storage just keeps growing - into this as well, but I'm not sure how.
I have yet to find a way to do it here and will be watching this post for others who come up with an idea.FU*&#%@ PDF's for Credentialing bloat my file server. Worse than email attachments (grrhhhh).
Better than being in email in my mind. are you in medical?
Yeah a Medical SMB. The issue is they come in email, the email is then forwarded (with attachement) to a few other internal individuals and then save to the file server. Then they make one change to the document and the process starts over and no one bothers to remove the previous PDF's that no longer matter.
-
@pmoncho said in How do you get your departments to quantify what they actually need for their jobs:
@Dashrender said in How do you get your departments to quantify what they actually need for their jobs:
@pmoncho said in How do you get your departments to quantify what they actually need for their jobs:
@Dashrender said in How do you get your departments to quantify what they actually need for their jobs:
I also want to find a way to work in Dustin's - the departments don't cleanup their old shit - so storage just keeps growing - into this as well, but I'm not sure how.
I have yet to find a way to do it here and will be watching this post for others who come up with an idea.FU*&#%@ PDF's for Credentialing bloat my file server. Worse than email attachments (grrhhhh).
Better than being in email in my mind. are you in medical?
Yeah a Medical SMB. The issue is they come in email, the email is then forwarded (with attachement) to a few other internal individuals and then save to the file server. Then they make one change to the document and the process starts over and no one bothers to remove the previous PDF's that no longer matter.
yeah - I have those same types of issues, but the PDFs are generally so small it's not an issue.
But to really fix it - you have to get management involved - look, we are storing a TB of dupe not valid forms - can we delete them?
how do you know they are dupe non valid? - hopefully you have some sort of naming that makes them identifiable as the same, yet updated. -
@Dashrender said in How do you get your departments to quantify what they actually need for their jobs:
@pmoncho said in How do you get your departments to quantify what they actually need for their jobs:
@Dashrender said in How do you get your departments to quantify what they actually need for their jobs:
@pmoncho said in How do you get your departments to quantify what they actually need for their jobs:
@Dashrender said in How do you get your departments to quantify what they actually need for their jobs:
I also want to find a way to work in Dustin's - the departments don't cleanup their old shit - so storage just keeps growing - into this as well, but I'm not sure how.
I have yet to find a way to do it here and will be watching this post for others who come up with an idea.FU*&#%@ PDF's for Credentialing bloat my file server. Worse than email attachments (grrhhhh).
Better than being in email in my mind. are you in medical?
Yeah a Medical SMB. The issue is they come in email, the email is then forwarded (with attachement) to a few other internal individuals and then save to the file server. Then they make one change to the document and the process starts over and no one bothers to remove the previous PDF's that no longer matter.
yeah - I have those same types of issues, but the PDFs are generally so small it's not an issue.
But to really fix it - you have to get management involved - look, we are storing a TB of dupe not valid forms - can we delete them?
how do you know they are dupe non valid? - hopefully you have some sort of naming that makes them identifiable as the same, yet updated.A hash checker could quickly produce an easily readable report for that.
-
@Dashrender said in How do you get your departments to quantify what they actually need for their jobs:
@pmoncho said in How do you get your departments to quantify what they actually need for their jobs:
@Dashrender said in How do you get your departments to quantify what they actually need for their jobs:
@pmoncho said in How do you get your departments to quantify what they actually need for their jobs:
@Dashrender said in How do you get your departments to quantify what they actually need for their jobs:
I also want to find a way to work in Dustin's - the departments don't cleanup their old shit - so storage just keeps growing - into this as well, but I'm not sure how.
I have yet to find a way to do it here and will be watching this post for others who come up with an idea.FU*&#%@ PDF's for Credentialing bloat my file server. Worse than email attachments (grrhhhh).
Better than being in email in my mind. are you in medical?
Yeah a Medical SMB. The issue is they come in email, the email is then forwarded (with attachement) to a few other internal individuals and then save to the file server. Then they make one change to the document and the process starts over and no one bothers to remove the previous PDF's that no longer matter.
yeah - I have those same types of issues, but the PDFs are generally so small it's not an issue.
But to really fix it - you have to get management involved - look, we are storing a TB of dupe not valid forms - can we delete them?
how do you know they are dupe non valid? - hopefully you have some sort of naming that makes them identifiable as the same, yet updated.It is not that they are dups per se' but the the contract needed to be signed or missing initials, no one ever gets rid of "clientMedicare (1).pdf" or the previous 15 versions of the file.
It is almost the same as dealing with the email chains. Why keep the last 15 messages if the final message contains all the replies (aka entire conversation)??? Just one of those things guess....
-
@DustinB3403 said in How do you get your departments to quantify what they actually need for their jobs:
@Dashrender said in How do you get your departments to quantify what they actually need for their jobs:
@pmoncho said in How do you get your departments to quantify what they actually need for their jobs:
@Dashrender said in How do you get your departments to quantify what they actually need for their jobs:
@pmoncho said in How do you get your departments to quantify what they actually need for their jobs:
@Dashrender said in How do you get your departments to quantify what they actually need for their jobs:
I also want to find a way to work in Dustin's - the departments don't cleanup their old shit - so storage just keeps growing - into this as well, but I'm not sure how.
I have yet to find a way to do it here and will be watching this post for others who come up with an idea.FU*&#%@ PDF's for Credentialing bloat my file server. Worse than email attachments (grrhhhh).
Better than being in email in my mind. are you in medical?
Yeah a Medical SMB. The issue is they come in email, the email is then forwarded (with attachement) to a few other internal individuals and then save to the file server. Then they make one change to the document and the process starts over and no one bothers to remove the previous PDF's that no longer matter.
yeah - I have those same types of issues, but the PDFs are generally so small it's not an issue.
But to really fix it - you have to get management involved - look, we are storing a TB of dupe not valid forms - can we delete them?
how do you know they are dupe non valid? - hopefully you have some sort of naming that makes them identifiable as the same, yet updated.A hash checker could quickly produce an easily readable report for that.
only if they are 100% identical - which he already said was not the case, a small update.
So if these were text, you could do a comparison of said text and say if something like 90% the same - flag for review, then choose which to keep, etc.
-
@wirestyle22 said in How do you get your departments to quantify what they actually need for their jobs:
How does this work with the ultra conservative managers? I'd imagine it would translate into overhead for IT. Reverse the scenario.
How? It can't. Since IT has no budget. How conservative a manager is affects only his department, not IT.
Basically it is treating the IT department like an MSP. An MSP never cares if a customer orders too much, because it's up to the customer to decide, and up to the customer to pay. MSP / IT should never care or control a budget because logically it makes no business sense.
