In short
- Definition: The ease with which a system can be administered, configured, monitored and controlled by its operators.
- Goal: Let a small team run the system efficiently and safely.
- Example S.M.A.R.T. requirement: Routine administration taking under 2 hours per week, with 100% of settings managed from a central console.
1. Definition
As a non-functional requirement, management (or manageability) describes how easily a system can be administered, configured, monitored and controlled by the people who run it [1], [2].
If routine administration needs an expert, the system is not manageable. It is merely managed, for now.Key takeaway
It covers administration consoles, user and role management, configuration screens, monitoring dashboards, scheduled jobs, bulk operations and the ability to manage many instances or tenants consistently.
Good manageability means routine tasks are simple, safe and repeatable, ideally automated, and that administrators can see the state of the system at a glance.
2. Goal
The goal is to let a small team run the system efficiently and safely, without depending on a few experts.
Poor manageability leads to manual, error-prone procedures, long onboarding for administrators and configuration mistakes that cause incidents.
3. How to Measure It (S.M.A.R.T.)
| Metric | Unit | Typical target | How to measure |
|---|---|---|---|
| Routine administration effort | Hours per week | < 2 h | Time tracking of the admin team |
| Settings managed centrally | % of settings | 100% from a central console or configuration as code | Configuration review |
| Admin errors causing incidents | Count per quarter | 0 | Incident root causes |
| Time to onboard a new administrator | Days | < 3 | Onboarding records |
4. Example Requirements
Each requirement below is ready to copy into a specification: specific, measurable, achievable, relevant and time-bound.
- Administration: “Routine administration (user management, job monitoring, configuration) shall take less than 2 hours per week for a system with 5,000 users.”
- Central control: “All settings shall be managed from the central administration console or as code; no setting shall require direct database access.”
- Delegation: “Department managers shall be able to manage their own team’s access without contacting IT.”
5. Questions to Ask Stakeholders
- Who will administer the system day to day?
- Which tasks are routine, and how often do they occur?
- Which tasks should be delegated to business users?
- How many environments, instances or tenants must be managed?
- What must administrators see on a dashboard?
- Which actions must be restricted or approved?
6. Common Pitfalls
- Admin tasks requiring database scripts. They are risky and need experts. Provide proper tools.
- No bulk operations. Changing 500 users one by one invites mistakes.
- Unaudited admin actions. Record who changed what in the console.
7. Related NFRs
- Operability — day-to-day running in production.
- Configuration Management — settings should be versioned and traceable.
- Auditability and Control — admin actions must be recorded.
- Usability — admin interfaces need good usability too.
8. FAQ
They overlap. Manageability focuses on administering and configuring; operability on keeping the system running in production.
User and role management, configuration, job and health monitoring, and audit of admin actions.
Automate routine tasks, delegate safe ones to business users and manage settings as code.
9. Acronyms, Initialisms & Terms
Acronyms are abbreviations pronounced as words (like NASA); initialisms are spelled out letter by letter (like FBI). The classification below follows common pronunciation.
Acronyms
| Abbreviation | Stands for | Definition | Ref. |
|---|---|---|---|
| SMART | Specific, Measurable, Achievable, Relevant, Time-bound | Criteria for writing a goal or requirement so that anyone can check whether it has been met. | [3] |
Initialisms
| Abbreviation | Stands for | Definition | Ref. |
|---|---|---|---|
| FAQ | Frequently asked questions | List of common questions with their answers. | [4] |
| IT | Information technology | Use of computers, software and networks to store, process and exchange information; also the department that runs them. | [5] |
| NFR | Non-functional requirement | Requirement that describes how well a system must work (its qualities, such as speed or security) rather than what it does. | [2] |
Terms
Plain-language definitions of technical and project-management terms used in this article.
| Term | Plain-language definition | Ref. |
|---|---|---|
| Dashboard | Screen that summarizes key measures at a glance. | [6] |
| Database | Organized store of data that software can query and update. | [7] |
| Incident | Unplanned interruption or degradation of a service. | [8] |
| Production environment | The live system that real users use, as opposed to test environments. | [9] |
| Stakeholder | Person or group with an interest in the system: users, sponsors, operators, regulators. | [10] |
10. Sources and Further Reading
- [1] “Systems management.” Wikipedia. https://en.wikipedia.org/wiki/Systems_management (accessed Nov. 18, 2026).
- [2] “Non-functional requirement.” Wikipedia. https://en.wikipedia.org/wiki/Non-functional_requirement (accessed Nov. 18, 2026).
- [3] “SMART criteria.” Wikipedia. https://en.wikipedia.org/wiki/SMART_criteria (accessed Nov. 19, 2026).
- [4] “FAQ.” Wikipedia. https://en.wikipedia.org/wiki/FAQ (accessed Nov. 19, 2026).
- [5] “Information technology.” Wikipedia. https://en.wikipedia.org/wiki/Information_technology (accessed Nov. 19, 2026).
- [6] “Dashboard (computing).” Wikipedia. https://en.wikipedia.org/wiki/Dashboard_(computing) (accessed Nov. 19, 2026).
- [7] “Database.” Wikipedia. https://en.wikipedia.org/wiki/Database (accessed Nov. 19, 2026).
- [8] “Incident management.” Wikipedia. https://en.wikipedia.org/wiki/Incident_management (accessed Nov. 19, 2026).
- [9] “Deployment environment.” Wikipedia. https://en.wikipedia.org/wiki/Deployment_environment (accessed Nov. 19, 2026).
- [10] “Project stakeholder.” Wikipedia. https://en.wikipedia.org/wiki/Project_stakeholder (accessed Nov. 19, 2026).
Written by Philippe Huard · LinkedIn · Last updated: November 18, 2026 · Header photo by @silverkblack; inline photo by @hannahbusing, both on Unsplash.




