We're always looking for ways to build stronger design habits into the Epiphany workflow. This release, we’re bringing a stronger performance focus to the Brief.
The performance level — what people actually need to do differently on the job — has always been part of the brief's thinking, but it sat implicitly inside the business problem and goal. Now it's called out explicitly in the Why section of the design brief.
The Performance Gap and Goal split into two levels:
Impact Evaluation reads across three levels: in-training, on-the-job performance, and business impact.
To draw this out, the brief-creation chat now asks you what you know about the learners’ performance today and what they need to do differently.
As before, where training is not the only solution to closing the performance gap, the brief flags this in the attention points.
Epiphany builds good design practice into your workflow. This update is part of that ongoing work: naming the performance gap and giving it a visible place means the connection between learning objectives and business needs stays top of mind, instead of a nuance you have to infer.