A Path suggests a lock-step trip down Learning Lane.
I have been labeling one of the key deliverables of my Curriculum Architecture Design efforts as a Blueprint and then later as a Path. I have always seen both the Blueprint and the Path – as being, as appropriate: As Flexible As Feasible and As Rigid As Required.
As Flexible As Feasible
Here is an example Path that was flexible – as required by the client given their situation.
As Rigid As Required
Here is an example Path that was rigid – as required by the client given their situation.
Two Short Videos
Here is a short video produced by AT&T back in the day (1980) about the flexible Curriculum (more Menu than Path) developed for Product Managers.
And here is a short video produced by General Motors – back in the day (1998) – about the approach they embraced for developing Paths and Menus – because their was a predictable Process – predictable in terms of time burden (touch time) for all involved, schedule (cycle time) and costs of labor, materials, travel, etc.
What Does Your Situation call For: Rigid or Flexible?
For your most critical job titles in your most critical business processes, what is required?
What’s at stake?
What’s the R in ROI?
Is it Revenues to be achieved – or – Risks to be avoided? Or both?
# # #