If he can do it faster in excel, isn't that a good enough reason?
If the problem is that the spreadsheet later becomes an unworkable mess, isn't that an argument you can use to convince him to use other tools? And if he remains unconvinced... maybe excel was right for him after all?
That's a very good reason. I perfectly understand not willing to learn yet another fancy tool that looks nice, but is unfinished, buggy and will probably be gone next year. Some people are too busy doing actual business to waste time on that.
The biggest benefit of Excel is its flexibility - you can do what you need, how you need, and you can adjust and readjust your sheets on the fly to match the changing and messy needs of doing business. That database you're trying to force those workers to use? It's probably designed wrong the moment you save the schema, because the needs changed.
So Excel is unsecure and people keep losing their spreadsheets by moving them between each other on flash drives? Solve that. Maybe with a Dropbox-like solution for syncing documents (no shiny webapp bullshit, no logging in to domain NAT Samba Kerberos Windows Briefcase Sharepoint nonsense, just "a folder that syncs" and enforces some security).
I have the feeling that a lot of problems between IT and non-tech workers stems from the former treating latter like morons instead of trying to help them to do their jobs efficiently.
>I have the feeling that a lot of problems between IT and non-tech workers stems from the former treating latter like morons instead of trying to help them to do their jobs efficiently.
No. I know this sounds bad, but they really are morons.
OK, maybe that's too much. They're not morons. But neither are babies (could you learn a language as quickly as they do?). Like babies, they just don't know stuff. And they never have an incentive to learn it. Programmer is always there to save the day.
When the ability to code is seen as essential to be in a C-level position, I predict that many frustrations with IT will just magically disappear.
>I predict that many frustrations with IT would magically disappear if IT stopped calling everyone who doesn't know how to program morons or babies.
That's already happened. Have projects magically aligned to budgets and schedules? Have we been able to fire all the programmers and replace them with business analysts yet? Have Excel sheets become maintainable?
Certainly it's a good thing if IT doesn't hold itself as superior; but that does not mean that it's not a bad thing that most business people don't have what is becoming a more and more essential skill.
1. People have to read this calendar.
2. People have to edit this calendar.
3. Other people in the office don't know Excel as well as him.
4. Other stuff is designed to work with our calendar software, but not excel.
A hammer can drive a nail into wood. With a little help, it can also remove nails, smash glass, and pry things open. But if you're using a hammer to stretch pizza dough, get help.
Those are pretty good arguments you can use to convince your boss to start using your calendar software! So why hasn't he switched? I see some possibilities:
- No-one has pointed out these shortcomings to your boss.
- You have, but he is stubborn and refuses to see the downsides even though they are obvious to everyone else.
- You have, but you're overstating the downsides and the current setup actually works well enough as it is.
Even though he may be able to start working faster, there's no guarantee that the time-to-completion is faster. Also, in a calendar program it's going to be orders of magnitude faster to change stuff like the design in hindsight. And you're likely able to achieve designs that are physically impossible to do in Excel.
If the problem is that the spreadsheet later becomes an unworkable mess, isn't that an argument you can use to convince him to use other tools? And if he remains unconvinced... maybe excel was right for him after all?