Performance Matters - Learning and Performance - 15

PERFORMANCE MATTERS / PG 15
1. COLLABORATIVE
WORKFLOWS
2. QUALITY
ASSURANCE
When managers need to meet with associates to
assign specific tasks, it creates downtime, more
meetings for visibility, and other productivity drainers.
Imagine instead if teams could see the work available,
the actions required, and simply pick up a task or action
item and see it through. Everyone has visibility into what
work needs to happen and when, and the team can stay
aligned as they leverage the right skills when needed.
This is possible using a team collaboration site with
documented workflows because everyone-instructional
designers, UI/UX designers, subject-matter experts,
course owners, business owners, etc.-is empowered
to manage individual deliverables. There's no idle time
spent waiting for someone to assign work. Associates
can pull work forward, allowing things to be addressed
quicker than traditional waterfall-style approaches.
For workflow management, we're big fans of JIRA and
Kanban boards, although other tools work too. A good
workflow accounts for all the steps and stakeholders; is
customized to the work; and provides pathways to cycle
content through the team whenever issues are found.
Start with a process map that details all the steps
(such as role, timing, and other dependencies) as
well as necessary stakeholders. Then, build out that
process in your team collaboration site to ensure all
team members have visibility into the steps it takes to
develop and iterate on an individual deliverable. To add
clarity to tasks and ensure no step in the process gets
overlooked, assign a specific number of days to each
step in the process.
To ensure your training deliverables meet quality
assurance standards, integrate your quality control
process into your workflow. This includes:
* Maintaining a corrective action log
* Identifying content reviewers
* Mapping the workflow of when quality control
will occur
* Determining the amount of time or effort for
each quality control step
The corrective action log will help your team manage
for a quality product that meets the standards when it
comes out of production. Managing quality through a
corrective action log will help your team catch potential
risks and failure points before they happen. The work
becomes " mistake proof. "
Your corrective action log should:
* Identify all quality issues when they happen,
regardless of whatever phase or workflow step the
product is currently in.
* Identify the root cause of the issue. (Is there a
standard in place to effectively manage for quality?
Is the issue caused by human error, process error,
or technical issues?)
* Determine corrective action to prevent similar
issues going forward.
3. DOCUMENTED
STANDARDS
Before any development work begins, document
standards for all team members. Consider:
* Incorporating brand standards, including use
of visuals and known writing standards.
* Outlining different asset types and templates
based on anticipated content.
* Establishing ways to drive consistency through
design features such as icon themes, wayfinding,
or learning patterns.
* Determining targeted device(s) and design to the
proper screen size(s).
These standards should be continuously updated as
the design and content for digital learning assets is
iterated over time. Also, update standards regularly
as a result of flagged items in the corrective action log.
By making regular updates, your team will develop an
efficient rhythm for reviewing standards.
CONTINUED on next page
Performance Matters - Learning and Performance

Table of Contents for the Digital Edition of Performance Matters - Learning and Performance
