We hope to announce by the end of this month the release of iHRIS Manage and iHRIS Qualify version 3.0. Most of the changes in version 3.0 are to the structure of the software, which will make it easier for developers to customize the software and for system administrators to manage it without our technical assistance.
One big change is the addition of configurable modules to each system. This enables system administrators to install new modules written by us or other developers, or to write their own modules. Modules can be disabled and configured to customize the way each system works and the features that are available without requiring programming expertise.
Another big change is that reports can now be exported in a variety of formats. This will enable one-button porting of report data to Microsoft Excel or to other systems. Reports may also be formatted as PDFs for easier printing.
We hope to release a Windows version of iHRIS Manage 3.0 in the next month. This desktop version will not require an Internet connection, but data can be exported and imported for synchronization with other instances of the system.
In preparation for the release of version 3.0, all the documentation has been updated on this website, including the use case reports, user’s manuals, features lists and development calendars. Please see the iHRIS Manage and iHRIS Qualify software pages for all documentation.
When we design information systems, particularly working with stakeholders who have had difficulties accessing data in the past, it can be very tempting to collect every piece of data we can think of, just because we now have a tool that can capture and store the data. But we have to resist such temptations, or we’ll end up with systems that are too bloated to maintain and unwieldy amounts of data that are impossible to analyze meaningfully.
We’ve all seen forms that ask for so much information it’s exhausting to even think about filling them out. What incentives do we have to complete such forms, or to not rush through them as quickly as possible? The data entry person who fires up a bloated information system has the exact same reaction. When faced with a seemingly endless number of fields to complete, she might be tempted to skip some or fake data if all fields are required. She typically doesn’t know what is critical to the analyst. So bad data goes in, and bad analysis comes out. The system runs the risk of being abandoned, either by the people trying to maintain it or the people trying to get information out of it — or by everyone.
It’s better, when first designing the system, to ask “why” about each data field that is proposed. Why is it necessary to collect this? What report will require that data item to be complete? How will you use this piece of data to make better decisions? That’s why we typically ask stakeholders to come up with their most critical policy and management questions that they have been unable to answer because they couldn’t access the pertinent data. This process narrows the types of data that the system needs to collect to only the most critical pieces of information and helps us avoid “data smog” that can actually keep analysts from making good data-driven decisions.
Even with this process, it’s difficult to control the kid-in-a-candy-store mentality. Sitting down with stakeholders and brainstorming requirements for a new module often results in calls for everything but the kitchen sink. Just because we can collect a lot of data doesn’t mean we should.
I think it’s better to take a minimalist approach, especially when first introducing an information system to an organization that hasn’t used one before. Real-world use of the system will reveal which critical pieces of data may still be missing, and those fields can be added in a later version, or by the organization with a customized need. It is better, I think, to risk the system being too small than being too large.
What do you think? How much data is too much?
We have completed the process of uploading all of the documentation for iHRIS Manage and iHRIS Qualify. You can find the vision statements, full use case models and supporting documentation on the software pages. If you are very interested in how we developed this software and how it works, the use cases should prove enlightening. The use case model documents all functions already implemented in each system, as well as future development paths, such as an in-service training management module for iHRIS Manage. The use cases will be updated regularly on this site as they are expanded and revised.
In addition, we have added a page with information of particular interest to any developers who would like to customize the systems for their own use or contribute to our core development project for iHRIS. Check out the new For Developers page to find links to the code repository, bug-tracking and knowledge base systems, mailing list and wiki where we are documenting current development efforts and future plans.
As always, we welcome suggestions and feedbacks via the comments or the Contact form on this site. Happy reading!
What is happening with HRIS Strengthening? Get news about our ongoing work in the field, find out when new features and releases of the software are available, learn more about human resource information systems, and join the conversation. Your comments and questions are welcome.