The job is the reporting cycle
Raw exports arrive messy. They have to be cleaned the same way every month.
Figures have to agree with another system. A pack has to reach a manager by a
date, and it has to be right.
Everything an MIS executive does is somewhere in that loop. It is not glamorous
and it is genuinely important — a company that cannot see its own numbers makes
decisions blind, and the person who makes those numbers appear on time is
noticed.
There is a specific moment when an MIS executive becomes twice as useful, and it
is the day they learn enough SQL to pull their own data.
Before that, every question routes through somebody in IT and takes two days.
After, it takes ten minutes. Nothing else in this role produces that size of
change, which is why the SQL is worth the few weeks it takes even though the job
advertisement may not insist on it.
Automate the second time, not the first
Do a report by hand once and you understand it. Automate it before you understand
it and you have built something you cannot debug.
The right order is to produce the pack manually, note which steps are identical
every month and which need a judgement call, and automate only the first kind.
People who skip that step end up maintaining a fragile macro nobody trusts.
What protects you
The part of this job that a script can do will eventually be done by a script.
What it cannot do is work out why two systems disagree, notice that a figure is
implausible before it reaches a board pack, or explain a variance to a manager
who is annoyed about it. Build those and the automation is your tool rather than
your replacement.