Independent business simulation
Project Order Readiness System
Lakemont Building Supply · Operations and systems analysis
Nobody can say which project orders are ready to schedule without opening four systems first.
Read the case studySelected work
Four projects built around one fictional company, Lakemont Building Supply. Each shows the reasoning behind the deliverable: what I would investigate first, who the stakeholders are, the root cause underneath the symptom, the tradeoffs each group would have to accept, and what I would measure to know it worked.
Lakemont Building Supply · Operations and systems analysis
Nobody can say which project orders are ready to schedule without opening four systems first.
Read the case studyLakemont Building Supply · Customer operations
A growing case backlog requires employees to manually research every record before they can determine the next action.
Read the case studyLakemont Building Supply · Project and implementation management
Eleven teams share one launch date, but no shared view shows ownership, dependencies, and risks.
Read the case studyLakemont Building Supply · Organizational enablement
Lakemont acquired two branches, but processes stayed inconsistent. Knowledge lived in individual memory, leaving new hires to guess and branch managers without current procedures.
Read the case studyThe company
A fictional regional commercial building supply company with three branches, a central warehouse, and roughly 120 employees. It supplies architectural finishes, commercial doors and hardware, flooring, lighting, acoustic materials, and prefabricated interior components to general contractors, property managers, developers, schools, healthcare facilities, and municipal buildings.
Lakemont grew through an acquisition and an expansion into project based interior packages. Its systems did not grow with it. Order information, vendor dates, customer approvals, and delivery schedules live across an ERP, a CRM, shared spreadsheets, and email. Leadership knows work falls through the cracks but cannot see where.
One environment, four different operational problems. That is deliberate: it keeps this a connected body of work rather than four unrelated exercises.
Portfolio confidentiality statement. All business scenarios, organizations, names, data, processes, and supporting materials shown in this portfolio are fictional and were created independently to demonstrate my approach to operations, systems improvement, project execution, organizational enablement, and cross-functional problem solving. No confidential, proprietary, or internal materials from current or former employers are included.