Organizations have a mission statement. Departments can have mission statements. They hang on walls, appears in strategic plans, and are referenced during meetings and orientation sessions.
How do organizations translate a mission statement into everyday work?
This has been an area of focus for our operations leadership team over the past year. We have spent considerable time discussing not only what each department does, but why it exists within the larger organization. Rather than beginning with procedures or performance metrics, we began with something much more fundamental: the mission of each department.
Each director was asked to develop a mission statement for their department, but with one important condition. That mission could not stand on its own. It had to exist in support of the mission of the Operations Division, which itself exists to support the mission of the school. This creates alignment throughout the organization. Instead of the departments operating independently, each with its own priorities, every department understands how its work contributes to a common purpose.
Once that foundation was established, the next question naturally followed. If this is our mission, what must we excel at in order to fulfill it?
Those answers became the department's key areas. Every department has a handful of responsibilities that are essential to its success. For Facilities and Grounds, those areas may include preventive maintenance, work management, capital planning, regulatory compliance, and customer service. Dining, Technology, Campus Store, Human Resources, Finance, and Housekeeping each have their own critical functions. The key areas are not individual tasks, but broad areas of responsibility that collectively define the department's contribution to the organization. They are essential to the success of the mission.
From there, we moved into what I believe is one of the most important conversations an organization can have: establishing standards.
Standards define what good looks like. They are the link between key areas and the work that delivers the result.
Simply put, they are the expectations a department holds for itself before anyone else imposes expectations upon it. Without a baseline against which performance is measured and improvement is evaluated, you can wander aimlessly fulfilling work for the sake of work. Metrics are only meaningful if they are measuring something that has first been defined. Without standards, performance data simply tells us what happened. It does not tell us whether the outcome met our expectations.
Many organizations attempt to begin with metrics asking what they should measure and end up with a dashboard full of data points that may or may not connect to the mission. I believe that approach reverses the process. Metrics are how you know a standard was met and are embedded in the standard itself. When standards are well understood, meaningful measurements become much easier to develop because everyone agrees on what success should look like.
At this point, the framework begins to move from philosophy to execution.
The mission provides purpose. The key areas identify where the department must perform. The standards define the level of performance expected. The next step is determining how those standards will be achieved.
This is where Standard Operating Procedures become valuable.
An SOP describes the broad process required to consistently achieve a particular standard. It identifies the sequence of activities and establishes consistency across the department and ensures that two employees approaching the same responsibility will generally follow the same process.
However, an SOP is not always the final level of detail.
Many procedures are made up of multiple individual activities, each requiring its own work instruction. A housekeeping department provides a simple example. A standard may establish the level of cleanliness expected for every residence hall bathroom and the SOP outlines the overall cleaning process. To achieve all components of the SOP, work instructions provide the detailed guidance for each component of the work: cleaning mirrors, sanitizing fixtures, mopping floors, disinfecting showers, servicing ventilation grilles, replenishing supplies, and completing final inspections.
By separating the procedure from the individual work instructions, organizations gain both consistency and flexibility. Employees can move between buildings, shifts, or assignments while following the same established process. New employees have a clear reference for learning their responsibilities and supervisors have an objective standard for coaching performance. Most importantly, the people using those facilities experience a consistent level of service regardless of who completed the work.
What is created from this structure is an operating system for the organization.
Although housekeeping provides an easy illustration, the same structure applies across every operational department. The principle remains the same regardless of the discipline.
When departments understand every component of how to achieve the mission, they benefit from an environment where expectations are understood rather than assumed. Teams spend less time wondering how work should be completed and more time focusing on the quality of the work itself.
Ultimately, consistency is about creating a dependable experience for the people we serve, not simply reducing work to a checklist. Consistency builds trust because it allows the professional community, students, parents, patients, customers, or guests to know what they can expect every time they interact with the organization.
For me, operational excellence goes beyond performing work efficiently. It is creating systems that consistently deliver the mission the organization has promised to fulfill. When every department understands its purpose and executes its work with consistency, excellence is no longer dependent upon individual effort alone. It has become embedded within the organization itself.
More soon,
Kurt