Project Management in Interior Design

The management course that turns a design into a delivered project. It teaches how an interior project is planned, scheduled and controlled from concept to commissioning so that it comes in on time, on budget and to the quality the client was promised, and it treats project management honestly, as continuous control rather than a one-time plan, with the interior designer often the coordinator of contractor, vendors and consultants. It begins with the fundamentals of planning, scheduling and controlling a project, the role of decision-making, the human side of managing people, the work breakdown structure that divides the whole job into manageable work packages, and the project life cycle, and it is clear from the start that a plan is a hypothesis and management is what you do when reality disagrees, so the triple constraint of scope, time and cost with quality means you cannot fix all three independently. It builds the language of the network diagram, distinguishing activities that consume time from events that mark instants, explaining the dummy that carries logic but no work, and the rules for drawing and numbering a valid network, so that a schedule respects the real dependencies of the job. It then teaches the Critical Path Method and PERT, showing how a forward and backward pass find the earliest and latest times, the float, and the critical path whose length is the shortest possible project duration, and it draws the honest line between CPM, which is deterministic and suits known work, and PERT, which uses three time estimates to give a probabilistic answer for uncertain work, so a single confident date is false precision. It moves into time and cost optimization, separating direct cost that rises as you crash from indirect cost that rises with duration, finding the least-cost optimum duration on the total-cost curve, and using the cost slope to decide which critical activities to crash first, making plain that faster is not automatically cheaper. And it ends with updating the plan as reality diverges from it and with allocating resources through histograms, resource smoothing that uses float without moving the deadline and resource levelling that respects a resource limit even at the price of a longer programme, alongside the computer applications that compute all of this but do not manage the project. Throughout, it insists that adding people to a late project can make it later, that the critical path is about time and not importance, that float is flexibility to be spent deliberately, and that the software and the technique serve a manager whose judgement, communication and control remain the real work.