What Does General management practice Mean?

Think of a general management practice as the playbook for running any organized group, like a sports team or a restaurant kitchen. In a restaurant, the head chef plans the menu (planning), makes sure the ingredients are ordered (organizing), tells the cooks what to do (directing), and checks the quality of every dish (controlling). These are all management activities. Now, apply that to an IT department. Instead of a menu, the IT team plans what software projects to work on. Instead of ordering ingredients, they buy new servers or cloud subscriptions. Instead of directing cooks, a project manager tells developers what features to build next. And instead of tasting the food, they monitor the network to ensure everything runs smoothly.

General management practice in ITIL includes a wide range of activities such as risk management, financial management, human resource management, and communication management. These are not technical skills like writing code or configuring routers, but they are essential for making sure the technical work actually achieves the organization's goals. For example, without good financial management, an IT team might run out of budget for critical security updates. Without good communication management, a team might build a new feature that nobody asked for. So, while IT professionals often focus on the technical details, general management practices provide the structure that keeps the whole machine running. These practices are the "soft" skills and business processes that turn raw technical ability into valuable, reliable services for customers.

In the context of ITIL 4, general management practices are a category of 14 practices that have been adapted from generic business management and are applied to service management. They are not unique to ITIL or IT, but are considered essential for managing an IT organization effectively. These practices include: Architecture Management, Continual Improvement, Information Security Management, Knowledge Management, Measurement and Reporting, Organizational Change Management, Portfolio Management, Project Management, Relationship Management, Risk Management, Service Financial Management, Strategy Management, Supplier Management, and Workforce and Talent Management.

These practices are defined in the ITIL 4 framework as part of the Service Value System (SVS). The SVS is a model that shows how all components and activities of an organization work together to facilitate value creation. Each general management practice provides a set of resources, capabilities, and activities that are used to manage a specific aspect of the organization. For example, Organizational Change Management (OCM) provides structured approaches to manage the people side of change, ensuring that changes in services, processes, or technologies are adopted successfully. Service Financial Management provides methods for budgeting, accounting, and charging for IT services, aligning IT costs with business value.

The implementation of general management practices in IT is not optional; they are required to move from a purely technical operations team to a true service provider. For instance, a help desk that only fixes tickets without any portfolio management or continual improvement will likely stagnate and fail to meet evolving business needs. In a real IT organization, these practices are often integrated into formal roles. A Service Delivery Manager may use Relationship Management to understand customer needs, Risk Management to assess service continuity threats, and Measurement and Reporting to track SLAs. The practices are interconnected; a change in Portfolio Management (e.g., retiring a service) will trigger activities in Organizational Change Management, Risk Management, and Supplier Management.

The ITIL 4 framework explicitly separates these from service management practices (like Service Desk, Incident Management) and technical management practices (like Deployment Management, Infrastructure Management). This classification helps learners and professionals understand that effective IT service management requires a blend of business management skills, service-specific processes, and technical expertise. Exam questions often require candidates to identify which general management practice is most appropriate for a given scenario, such as using Risk Management to evaluate a proposed vendor change or using Workforce and Talent Management to address a staffing shortage.

General management practices matter because they transform a chaotic group of technical experts into an organized, value-driven IT department. Without them, IT teams often fall into what is called the "silo trap" where each team works independently without considering the bigger picture. For example, a network team might upgrade all switches to a new model without consulting the security team (missing Risk Management) or without informing the business that there will be a weekend outage (missing Communication/Organizational Change Management). This leads to wasted money, security vulnerabilities, and angry users.

In practical terms, these practices help IT professionals make better decisions. Service Financial Management ensures that IT costs are visible and controlled, so you can justify a cloud migration or explain why a project went over budget. Organizational Change Management helps you roll out a new software tool without having employees revolt against it because they weren't trained or told why the change was happening. Risk Management helps you identify that single point of failure in your network before it causes a major outage.

These practices are also critical for career growth. An IT professional who only knows technical skills will always be a technician. But someone who understands how to budget, manage risk, communicate with stakeholders, and continuously improve services is well on their way to becoming a manager, director, or CIO. In ITIL exams, these practices are not just theoretical; they appear in scenario-based questions that test your ability to choose the right management approach. For example, a question might describe a situation where an IT team is struggling to prioritize work, and the correct answer is to implement Portfolio Management to evaluate and prioritize projects based on business value.

Finally, they matter because IT is no longer just about keeping systems running. It is about delivering business value. General management practices provide the framework to prove that value, measure it, and improve it over time. Without them, IT becomes a cost center that is always under budget pressure; with them, IT becomes a strategic partner that drives innovation.

General management practice questions in ITIL exams typically fall into three patterns: scenario selection, definition matching, and best practice application.

Scenario selection questions present a short description of an IT management problem and ask which general management practice is most appropriate. For example: "A company is launching a new mobile app. The project team needs to ensure that the required developers, testers, and operations staff are available at the right times. Which general management practice should they use?" The correct answer is Workforce and Talent Management. Another example: "An IT manager needs to decide which of four potential projects will deliver the most value to the business with limited resources. Which practice should guide this decision?" The answer is Portfolio Management.

Definition matching questions are more straightforward. They might give a list of definitions and a list of practice names, and you must match them. For instance, "The practice of identifying, analyzing, and controlling potential events that could negatively affect the organization" matches Risk Management. Or "The practice of aligning the organization's activities with its vision and objectives" matches Strategy Management.

Best practice application questions are more complex. They describe a situation where an organization is failing in some area, and you must identify not just the correct practice, but also the correct activity within that practice. For example: "An IT support team receives the same types of repetitive requests daily. They want to reduce these requests over time. Which activity of which practice should they use?" The answer is Continual Improvement, specifically, the step of identifying and implementing improvements to reduce the volume of repetitive work.

Troubleshooting-oriented questions appear in higher-level exams like ITIL 4 DPI. A typical question: "A new software rollout failed because employees resisted using it. Which general management practice was most likely overlooked?" The answer is Organizational Change Management, which would have included stakeholder engagement, training, and communication to ensure adoption.

In all cases, exam writers use the specific wording from the ITIL 4 official publication for the practice definitions. So, memorizing the precise purpose of each practice is helpful. The most commonly tested general management practices on the Foundation exam are: Risk Management, Continual Improvement, Relationship Management, Service Financial Management, and Organizational Change Management. Be prepared to distinguish between Continual Improvement and Organizational Change Management, the former focuses on improving processes and services, the latter on managing the people side of those changes.

In a real IT workplace, general management practices are not just theoretical concepts; they are the daily activities of managers, team leads, and even senior technicians. Let us focus on three commonly used practices: Risk Management (RM), Service Financial Management (SFM), and Relationship Management (RelM). Understanding how these work together is crucial.

Risk Management in IT involves identifying what could go wrong, a server failure, a data breach, losing a key employee, and then deciding what to do. It is not about being afraid of risks; it is about being prepared. A practical approach is to use a risk register, which is a simple table listing each risk, its likelihood, its impact, and the planned response (avoid, mitigate, transfer, or accept). For example, a risk might be 'Cloud provider outage' with a mitigation of 'multi-region deployment.' In a small IT team, risk management might be as simple as ensuring daily backups are tested.

Service Financial Management is often the least favorite practice among technical people, but it is vital. It covers budgeting (planning IT spending for the next year), accounting (tracking where money is actually spent), and charging (billing internal departments for their IT usage). A common mistake is to ignore this practice until the budget runs out. A professional approach is to track cloud usage costs in real-time, set alerts for unexpected spikes, and perform a monthly cost review with the finance team.

Relationship Management is about understanding what your stakeholders (business users) actually need, not just what they say they want. This involves regular meetings, surveys, and service reviews. A classic failure is when IT builds a solution that works technically but no one uses it because it didn't solve the user's real problem. Relationship Management prevents that by ensuring ongoing dialogue.

What can go wrong? The most common issue is that these practices are treated as optional paperwork. Risk Management becomes a one-time risk assessment that sits in a drawer. Service Financial Management is reduced to one annual budget request. Relationship Management becomes a monthly email that no one reads. To avoid this, integrate these practices into existing workflows. For instance, before any major change, include a mandatory risk assessment step. When discussing new projects, always link them to the budget. And when planning a new feature, automatically involve a relationship manager to talk to users.

For certification, focus on the purpose and key activities of each practice. For the workplace, focus on making these practices practical and lightweight. A good rule of thumb: if you are making a decision that involves money, people, or the future direction of IT, one of these general management practices should be guiding you.