In two past blogs, we addressed modeling space, costs, and return on investment at the project and national or regional levels. This blog will address three challenges to designing a successful office space reduction model. If done correctly, a model can generate excitement for an office space reduction program and help decision-makers visualize outcomes.
For Fentress, modeling has become an extension of our architectural and analytical services to streamline business processes and predict the impact of program changes. Our latest space reduction model, the Space Utilization Model (SUM), has been used successfully at both the program and project levels. The model is web-based and was developed using PHP and Javascript. This post will feature some lessons we learned to create a successful model.
The first challenge is the data. This will come as no surprise to those who engage in modeling efforts. Office space reduction requires accurate data on current space, personnel, rent/security costs, design standards, and project costs.
These data often come from disparate sources and must be mined and compiled to form a working database. This is a challenging task, and however, once it is accomplished, so much can be done with the data that the undertaking is well worth the effort.
The second challenge is designing a model that matches the process. For our Space Utilization Model, we knew that we wanted to present the return on investment (ROI), which is the point when rent savings offset the cost of funding a project to reduce space. With ROI, we mapped a process backward to develop a flow for the model.
For example, you need to calculate the project costs and savings before calculating ROI. Before calculating costs, you must calculate the required space and saved space. Before figuring out space, you need to align personnel to space standards. This mapping process was very helpful in developing a model with a clean, logical flow.
The final challenge, and perhaps the most important, is to take the logic described above and design the model as user-friendly. I have seen many models so densely detailed that it is hard for anyone to understand except for the model developers and the people who use them daily. Designing an overly detailed model is a missed opportunity.
Try to think of the model as a selling point for the program. If the model is user-friendly, logical, and visually appealing, it can generate excitement over the benefits of office space reduction and lend credibility to the overall program.
Through this white paper, you will learn how a space reduction model can calculate:
The white paper also comes with a case study that presents how the model has been used to generate excitement for the mission of space reduction.
[mc4wp_form id="1479"]
Here are some suggestions to enhance the modeling effort. The suggestions apply whether you are developing a model in Excel, programming a desktop version, or designing an application for the Internet:
If done correctly, a model can be demonstrated to decision-makers to help them understand the benefits of the space reduction program. Such understanding can generate support for project funding. The model can also be shown to personnel considering a project to reduce their office space.
Seeing and even manipulating the model results can help generate a comfort level with space reduction, and these benefits are worth the effort. Following the suggestions above, it will be easier for your organization to overcome the challenges of developing a successful office space reduction model.