Page 153 - IMDR JOURNAL 2023-24
P. 153

IMDR’s Journal of Management Development & Research 2023-24

               Employee perspective:
                    1.  Difficulty  navigating  the  software:  Clients  frequently  encounter  difficulties  navigating

                        complex interfaces and functionalities. They struggle to locate specific features or complete

                        tasks efficiently.
                    2.  Limited understanding of the software capabilities:  Clients may not fully grasp the full

                        potential of the ERP solutions due to inadequate training or unclear documentation. This can
                        lead to underutilization of valuable features.

                    3.  Inadequate  support:  Clients  may  feel  their  concerns  are  not  addressed  promptly  or
                        satisfactorily by the support team. This can lead to negative experiences and a sense of being

                        unsupported.


         By combining these diverse data collection methods, we can create a richer and more nice understanding of

         user  experiences  with  educational  ERP  solutions.  The  combined  approach  strengthens  the  research
         methodology  and  provides  valuable  insights  for  various  stakeholders,  including  software  developers,

         educational institutions and ultimately all those involved in the educational ecosystem.


             5.  Data Analysis
         We crunched numbers and analysed words to understand what users really think.

               Number magic: We used stats to summarize key trends (like how many people are happy/unhappy).
               Word  detective:  We  grouped  similar  comments  to  uncover  recurring  themes  (like  "difficult

                 interface").
               Combining forces: This double-pronged approach gave us a complete picture of user experiences.

         Here's what we found:

               Numbers told us how many users faced challenges, but not why.
               Words explained their frustrations (confusing interface, no support).

               Together, they painted a vivid picture of user needs (training, user-friendliness).
         This analysis is like having a superpower:

               Understanding user needs helps developers make better software.

               Schools can choose systems that work for everyone, not just the tech-savvy.
               Ultimately, it's about improving the educational experience for all.


         The  words  used  to  describe  their  frustrations,  such  as  "confusing  interface"  and  "lack  of  support,"  were

         common themes among the users. These issues were not isolated incidents, but rather widespread challenges

         that many faced when using the software. However, when combined, they formed a clear and detailed picture
         of the user's needs. The users expressed a desire for more training and a user-friendly system that would make
   148   149   150   151   152   153   154   155   156   157   158