Evolve: How to Keep Learning Solutions Aligned With Change
Updated: Aug 18
The purpose of Evolve is to recognize that a learning solution is never truly finished. The performance, environment, technology, workforce, customer expectations, and business requirements that shaped the original solution will inevitably change. Evolve establishes the mechanisms for monitoring those changes and determining when the solution or the underlying performance requirements needs to be reconsidered.
Evolve answers the question: What has changed, and does that change require us to revisit the solution?
Learning Solutions Are Not One-Time Projects
Traditional learning development often follows a linear model:
Analyze → Design → Develop → Deliver → Done
Once the course is launched, the project is considered complete.
But organizations don't operate in static environments. New technologies are introduced. Processes change. Regulations evolve. Customer expectations shift. Employees discover better ways of working. Business strategies change. Even the desired behaviors themselves may become obsolete.
A solution that was highly effective when it was created can gradually become less relevant—or actively reinforce outdated practices.
The Solution Architect therefore needs to treat the learning solution as a living system, not a finished product.
Monitor the Conditions That Matter
Evolve requires monitoring three broad areas:
Performance
Is the desired performance actually occurring?
The organization may monitor:
Business results
Quality
Productivity
Customer outcomes
Employee performance
Behavioral data
Assessment results
Compliance indicators
Performance data can reveal that the solution is no longer producing the expected outcome—or that a new opportunity for improvement has emerged.
Environment
What has changed in the context in which employees perform?
Examples include:
New technology
New systems
New products
New regulations
New customers
Changes in organizational structure
Changes in workforce composition
Changes in competitive conditions
Changes in processes or policies
A capability that was appropriate in one environment may no longer be sufficient in another.
Solution
Is the learning and performance-support ecosystem itself still effective?
The Solution Architect should monitor:
Learner engagement
Assessment results
Practice performance
Transfer data
Usage of performance support
Manager feedback
Learner feedback
Content relevance
Technology effectiveness
This helps distinguish between a performance problem and a solution problem.
Change Triggers the Cycle
The most important concept in Evolve is that change should trigger a return to the beginning of the Solution Architect process.
For example:
A new technology changes how employees perform their jobs.
That change may alter the desired state.
The organization therefore needs to:
Redefine the desired state → Re-engage employees → Re-diagnose capability gaps → Upskill → Consolidate → Assess → Transfer
The process does not start over because the original solution failed. It restarts because the conditions have changed.
This makes Evolve fundamentally different from simply updating course content.
Not Every Change Requires a New Learning Solution
An important responsibility of the Solution Architect is determining whether a change actually requires intervention.
A change may require:
No action
A content update
A new performance support resource
Refresher learning
Additional practice
A new assessment
A change to manager reinforcement
A redesigned learning journey
A completely new solution
For example, a minor policy change might require updating a job aid. A major technology implementation might require returning to Engage and redesigning the entire learning journey.
The Solution Architect should avoid treating every change as a reason to build more training.
Experiences and Activities for Evolve
Experience | Example Media | Purpose |
Performance Monitoring | Dashboards, analytics, reports | Identify changes in performance |
Environmental Scanning | Research, stakeholder interviews, trend monitoring | Identify changes that may affect performance |
Learner Feedback | Surveys, interviews, focus groups, AI analysis | Identify changing learner needs |
Manager Feedback | Interviews, forums, performance reviews | Identify emerging performance issues |
Content Review | Content audits, expert reviews | Identify outdated or inaccurate content |
Assessment Analysis | Assessment analytics, certification data | Identify capability changes |
Behavioral Analytics | System data, workflow data, interaction data | Monitor whether desired behaviors persist |
Customer Feedback | Surveys, interviews, support data | Identify changes in customer expectations |
Change Reviews | Project reviews, business planning sessions | Identify organizational changes requiring capability development |
Solution Retrospectives | Workshops, analytics reviews | Evaluate whether the solution remains effective |
Trigger-Based Reviews | Automated alerts, dashboards | Initiate the EDUCAT cycle when predefined conditions change |
Establishing Evolve Triggers
The Solution Architect should identify what changes would be significant enough to trigger a review.
These might include:
Performance falls below an established threshold.
A critical behavior declines.
A new system or technology is introduced.
A regulation changes.
A product or service changes.
Customer expectations shift.
A significant business strategy changes.
Assessment results indicate declining competence.
Employees report that learning no longer reflects their work.
Managers identify recurring performance problems.
New risks emerge.
These triggers turn Evolve from a vague commitment to "continuous improvement" into an actionable operating mechanism.
The Solution Architect as Steward
Evolve changes the role of the Solution Architect.
The Solution Architect is not simply responsible for delivering the original solution. They become the steward of the capability system, monitoring whether the relationship between business objectives, employee capabilities, workplace conditions, and learning interventions remains effective.
This creates a continuous feedback loop:
Business & Environment → Performance → Capability → Solution → Performance
When something changes, the Solution Architect determines where the change enters the system and whether the EDUCAT cycle needs to be restarted.
Evolve is therefore more than updating content or refreshing a course. It is a mechanism for maintaining the alignment between the organization, its people, and its performance requirements.
The original solution architecture represents a set of assumptions:
This is the desired performance.
These are the behaviors required.
These are the capabilities employees need.
These are the barriers they face.
These are the experiences that will develop those capabilities.
These are the conditions required to sustain performance.
Over time, those assumptions may no longer be true.
Evolve tests those assumptions.
Key Questions the Evolve Phase Answers
Is the desired performance still the right performance?
Are employees still demonstrating the required behaviors?
What has changed in the business or work environment?
Have new capability gaps emerged?
Is the existing solution still effective?
What elements of the solution need to change?
Does the change require a minor update or a new solution architecture?
What should trigger another cycle of EDUCAT?
The purpose of Evolve is to ensure that learning solutions remain aligned with changing performance requirements, environments, and business outcomes. When meaningful change occurs, Evolve triggers the Solution Architect process to begin again.
The complete EDUCATE cycle
Engage — I understand why change matters.
Diagnose — I understand where I need to improve.
Upskill — I develop the capabilities I need.
Consolidate — I can integrate those capabilities in realistic situations.
Assess — We have evidence that I can perform to the required standard.
Transfer — I apply and sustain those capabilities in my work.
Evolve — We monitor whether the performance and environment have changed—and restart the cycle when they have.
Comments