Roles in Information Systems Practice: Users, Developers, Managers and Vendors

Roles in Information Systems Practice: Users, Developers, Managers and Vendors

📘 Overview An organizational information system is planned, built, run and improved by several groups of people: its users, the developers and technical specialists who build and support it, the managers who sponsor and decide about it, and external vendors who may supply parts of it. Each group knows and is responsible for different things, so a system serves the organization best when these roles communicate and work together rather than separately.

🧠 Key Idea The roles around an information system depend on one another. Users know the work, technical specialists know the technology, managers set priorities and provide resources, and vendors supply products or services. The system fits the organization when each role understands what the others need and says clearly what it needs itself.

⚔️ Core Details: - End users are the people who use the system in their daily work. Because they know how the work is really done, they describe their needs, test whether the system fits their tasks, report problems and follow the agreed procedures. - Developers and technical specialists design, build, configure, test and support the system. They turn the organization's needs into working technology and keep it running, and they depend on users to explain what the work requires. - Managers and decision makers sponsor the system, set priorities, approve budgets and decisions, and make sure the right people take part. They remain responsible for the organization's goals, not only for the technology. - External vendors and service providers supply software, equipment or services such as hosting, installation or support. The organization still decides what it needs and stays accountable for its own data and procedures. - Job titles and team structures differ between organizations. In a small office one person may combine several roles, while in a large organization one role may be shared by a team; what matters is that every responsibility is covered. - Consider a fictional city library replacing its book-loan system. The librarians, who handle loans, returns and fines, are the users: they explain how the work is done, test the new screens and report problems. A small technical team configures the system, transfers the existing records and trains staff. The library director, as manager and sponsor, sets the priority, approves the budget and decides the start date. An outside vendor supplies the loan software and corrects defects, and the library team checks that each correction works for its procedures. - In that project the roles collaborate through clear communication. Users describe needs in terms of their work, specialists explain options and limits without unnecessary jargon, managers explain priorities and decisions, and the vendor states what it will deliver. Misunderstandings are caught early, for example by showing librarians a sample screen before the system goes live. - Professional responsibility applies across these roles: being honest about what the system can and cannot do, keeping organizational and personal data confidential, communicating clearly and on time, and following the organization's rules and professional codes.