Aisha Hassan Algren. Contact
Independent business simulation

Branch Knowledge and Continuity System

Lakemont acquired two branches, but processes stayed inconsistent. Knowledge lived in individual memory, leaving new hires to guess and branch managers without current procedures.

Organization
Lakemont Building Supply (fictional)
Project type
Organizational enablement
My role
Analyst and designer
Timeline assumption
Ten to twelve weeks, assumed
These are simulations for a fictional company. No outcome shown here is presented as an achieved result. Impact appears as something I would propose to measure.

Placeholder case study. Full narrative, knowledge architecture, and training artifacts are still being written.

01

Business context

Lakemont acquired two branches over eighteen months. Each arrived with its own way of quoting, staging, handling returns, and communicating with contractors. None of it was written down.

02

The challenge

Procedures live in individual memory. New hires learn by asking whoever is nearby, which means they learn one person's version. Branch managers cannot confirm whether their team is following a current procedure because there is no current procedure to point to. Several long tenured employees are within a few years of retirement, and their knowledge has no home outside their heads.

03

My assignment

Design a knowledge and continuity system that captures how the work is actually done, assigns ownership to each procedure, and gives new hires a role based path instead of a guessing game.

04

Discovery questions

  • Which procedures actually differ between branches, and which only appear to?
  • Where a procedure differs, which version is better, and who decides?
  • What does a new hire need in week one versus month three?
  • Who owns each procedure, and do they have time to maintain it?
  • What knowledge exists only in one person's head right now?
  • How will anyone know when a procedure has gone out of date?

05

Stakeholders

GroupWhat they need
New hiresA path that does not depend on who is available to ask
Branch managersConfidence that their team follows a current procedure
Long tenured employeesRecognition, and a way to hand off without it feeling like erasure
Operations leadershipConsistency across branches without flattening what works locally
Customer facing teamsOne answer to give a contractor regardless of branch

06

Root cause

  • Acquisition integrated systems but not practices.
  • No owner assigned to documentation, so it was nobody's job.
  • Tribal knowledge was faster in the short term, so it was never challenged.
  • No review cycle, so what documentation existed went stale and lost trust.
  • Onboarding treated as introduction rather than as capability building.

07

Tradeoffs

TradeoffWhat it costs
Standardize procedures across branchesBranches lose local practices that may genuinely work better
Assign documentation ownersReal time commitment from people who are already busy
Capture knowledge from retiring staff firstPrioritizes continuity over immediate operational fixes
Role based paths rather than one manualMore structure to build and maintain upfront

08

Design principles

Placeholder section. The full narrative, diagrams, and artifact previews for this case study are still being written.

09

The proposed solution

  • Knowledge architecture organized by role rather than by department
  • Documentation ownership map with named owners
  • Review cycle with clear triggers for updating
  • Role based new hire learning paths
  • Searchable procedure library
  • Capture plan prioritizing knowledge at risk of leaving
Placeholder section. The full narrative, diagrams, and artifact previews for this case study are still being written.

10

Implementation considerations

Placeholder section. The full narrative, diagrams, and artifact previews for this case study are still being written.

11

What I would measure

Placeholder section. The full narrative, diagrams, and artifact previews for this case study are still being written.

12

Reflection

Placeholder section. The full narrative, diagrams, and artifact previews for this case study are still being written.
Previous: Cross-Functional Branch LaunchSee the toolkit

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.