Factors Influencing Implementation of a Management Information System

Imagine you are trying to build a massive, high-tech castle in a world where the ground is still settling after a long earthquake. This is the story of how universities in places like Somaliland are trying to swap their dusty paper files for shiny, digital Management Information Systems (MIS). Think of an MIS not as a boring computer program, but as the central nervous system of a university—a digital brain that connects students, teachers, and administrators so everyone knows what's happening, from grading exams to signing up for classes.

To understand why these digital castles sometimes crumble while others stand tall, scientists often use two special maps. The first is the "Design-Reality Gap" map. It warns us that a computer system designed in a fancy office might fail if it doesn't fit the messy, real-life reality of the people using it. The second map is called UTAUT, which is like a guidebook for understanding why people decide to use (or ignore) new technology. Usually, we assume that if you give people a cool new tool, they will use it if they are trained well, have enough money, and feel happy about it. But this paper asks a tricky question: In a place rebuilding from conflict, is it really about the users' feelings or the money, or is there something else pulling the strings?

The Digital Castle Experiment

A team of researchers from the University of Hargeisa decided to test these maps on their own campus. They wanted to know what actually makes a digital system work in a university that is still recovering from tough times. They gathered 214 people—mostly teachers and some office staff—to fill out surveys. They looked at five big buckets of factors:

1. IT Staff: The tech wizards who fix the computers.
2. Administration: The bosses and leaders who make the rules.
3. Users: The teachers and staff actually using the system.
4. Organization: How the university is structured and its culture.
5. Money: The budget for buying and running the system.

The Big Surprise: It's All About the Bosses and the Tech Wizards

When the researchers looked at the data, they found something that might make you do a double-take. At first glance, it looked like everything mattered. The teachers' attitudes, the organization's culture, and the money all seemed to be linked to success. It was like a recipe where every ingredient tasted good on its own.

But when they mixed all the ingredients together in a big statistical pot (using a method called multiple regression), the recipe changed. The study found that only two ingredients were truly essential for the cake to rise: University Administration and IT Staff.

The "Administration" factor was the heavyweight champion. The data showed that when university leaders are truly committed, push for the system, and enforce its use, the system works. It's like a captain steering a ship; if the captain is focused, the crew follows. The "IT Staff" factor was the second most important. Having skilled, responsive tech people who can fix problems quickly was crucial. It's the difference between having a broken car and a mechanic who can fix it in five minutes versus a mechanic who is nowhere to be found.

Together, these two factors explained about 45% of why the system succeeded or failed. That's a huge chunk of the puzzle.

What Didn't Matter (As Much as You'd Think)

Here is where the story gets interesting. The study explicitly ruled out some ideas that many people assume are the most important.

• User Attitudes: Surprisingly, how much the teachers liked the system or felt ready to use it didn't predict success once the leaders and tech support were in place. In a university, using the system is often mandatory (you have to submit grades!), so personal feelings matter less than the rules set by the bosses.
• Money: While you obviously need money to buy the computers, the study found that just throwing cash at the problem doesn't guarantee success. If the leaders aren't driving the change and the tech team isn't skilled, the money alone won't fix the "Design-Reality Gap."
• Organization and Culture: The general way the university was run or its culture didn't independently drive success when the leaders and tech staff were doing their jobs.

The "Middle-Age" Glitch

The researchers also noticed a funny pattern in the people using the system. They found that teachers aged 35 to 44 and those with 2 to 5 years of experience were actually less likely to adapt well compared to younger teachers or older, more senior professors.

Think of it like this: Younger teachers are digital natives who grew up with tablets. Older professors have been around so long that they have assistants to handle the paperwork, or they have enough authority to ignore the new rules. But the teachers in the middle? They are the ones doing all the heavy lifting of grading and managing classes, but they might feel stuck between old habits and new demands. They are the ones feeling the most friction, like a runner trying to change shoes while still sprinting.

The Takeaway

So, what is the lesson for the University of Hargeisa and other universities in similar situations? The study suggests that if you want your digital system to work, don't just buy expensive software or hope everyone will "get excited" about it. Instead, focus on two things:

1. Get the Bosses on Board: Make sure the leaders are actively driving the change, not just signing a check.
2. Hire and Train the Tech Team: Make sure you have skilled IT people ready to catch the ball when things go wrong.

The study concludes that in places rebuilding from conflict, leadership and technical skill are the "load-bearing pillars" of the digital castle. If those two are strong, the rest of the building (the money, the culture, the user feelings) tends to fall into place. But if those pillars are weak, no amount of money or good intentions will stop the castle from crumbling. The researchers admit this is based on a snapshot in time from one university, so more studies are needed, but for now, the message is clear: Fix the leadership and the tech support, and the rest will follow.