From zero to one, then handed over.
Every engagement, whether a Knowledge Station, a learning program or a community, moves through the same five stages. The aim is a first working version your own people can run.
- Expertise stays with its owners. Experts approve what is taught in their name, and their reasoning stays visible.
- Practice before launch. People rehearse the real task, including what goes wrong, before it counts.
- Honest limits. Product gaps, policy constraints and staffing limits are named and given owners, not hidden.
- Hand over, do not lock in. Your team learns to run, maintain and improve what we build together.
- 01
Understand
Whose expertise matters, who needs to learn from it, what they do today and what is getting in the way.
- 02
Scope
The station, program or community to build, the people involved, responsibilities, exclusions and acceptance checks, agreed in writing.
- 03
Build
Recordings, lessons, practice tasks and community spaces, made from approved source material in the tools you already use where they fit.
- 04
Practice and launch
Operators, facilitators and reviewers rehearse their roles, then a first group uses it with DBX alongside.
- 05
Review and hand over
We review what happened with your owners, record open actions and hand over guides, templates and trained roles.
How we agree it is done
Before handover we check only what is in your scope, against criteria agreed in writing:
- Staff can make a recording and find it again without DBX present.
- The initial learning has been delivered to participants and reviewed with the expert.
- People know where to get help and how to contribute what they learn.
- Reviewers have rehearsed responding to a real contribution.
- Owners are named for maintenance and for each open action.
Expertise, made teachable.
At DBX Expert Lab, our mission is to turn expert knowledge into practical capability. We bring learning design and technical implementation together so organizations can help their people learn, exercise judgment, and put new skills to work.
Expertise often lives in the decisions experienced people make every day. They recognize when a process needs to change. They know which question to ask, which detail matters, and when someone needs help. We work to make that knowledge teachable and build the systems that help others apply it.
The people who teach are central to this work. They may be educators, facilitators, managers, or specialists helping colleagues master something difficult. Their time is valuable. Their tools should make it easier to explain an idea, see where someone is struggling, and offer guidance that moves learning forward.
A connected working environment.
Our vision is a teacher OS: a connected working environment for the people who create and guide learning. This idea shapes how we design and implement systems that bring authoring, practice, feedback, and learner progress into a coherent workflow.
An educator should be able to adapt an activity for a particular group, understand a learner's response, and decide what comes next. A program leader should be able to maintain shared curriculum while giving facilitators room to respond to local needs. Everyone involved should understand who is responsible for feedback and follow-through.
Our Cohort Engine expertise brings this thinking into native authoring and learning systems. We help organizations connect reusable learning activities with cohort delivery and practical support. We begin with the tools and workflows already in place, then identify what needs to change.
Learning principles, made practical.
We begin with the work a learner needs to do and the evidence that would show they can do it. Then we design the explanations, practice, and support that lead there. Adults bring different experience, goals, constraints, and confidence. Our approach makes room for those differences while keeping the purpose clear.
Learning blocks are reusable pieces of an experience: an explanation, demonstration, question, reflection, or task. We choose them for the thinking they invite and the work they help someone accomplish. These block and workflow examples depend on each engagement's tools and delivery model.
1. Begin with purpose and prior experience.
Connect learning to a real responsibility or problem. Invite people to bring what they know, describe where they need help, and set a useful goal. Use that starting point to choose examples and support.
In practice: An orientation, open-response goal prompt, survey, or baseline task makes the learner's context visible.
2. Create a clear, manageable progression.
Connect each new idea to what came before. Give each step a clear job, show the expected effort, and build in stopping points. Leave room for different paces and additional support.
In practice: Brief text and media blocks, task lists, and short checks organize explanation, practice, and reflection.
3. Make expert thinking visible.
Show how an experienced person approaches the work. Explain what they notice, why they choose an action, and how they respond when something goes wrong.
In practice: A narrated demonstration, annotated image, or worked example reveals decisions that a finished answer leaves hidden.
4. Ask learners to use what they learn.
Give people a meaningful decision to make or something to produce. Connect practice to their work and ask them to explain their choices. A completed interaction is one signal; the quality of the response tells us more.
In practice: Scenario questions with explanation prompts, image annotation, practice tasks, and project submissions make understanding available for review.
5. Make room for reflection and agency.
Invite learners to examine assumptions, compare an attempt with its result, and decide what they need next. Offer relevant choices and support while keeping expectations clear. Give people time to think and ask for help.
In practice: Open-response reflections, self-assessments, personal action plans, and optional reference material help learners direct their progress.
6. Revisit important ideas over time.
Plan opportunities to recall and use earlier learning after an interval. Retrieval and spaced practice can support retention. Later application tasks help reveal whether people can use that knowledge in context.
In practice: Recall questions, flashcards, and cumulative checks, paired with a planned review schedule, bring earlier ideas back into use.
7. Build community around the work.
Give people a shared problem and a reason to exchange perspectives. Keep conversation close to the task it concerns. Ask learners to explain their reasoning and respond thoughtfully to another person's contribution.
In practice: A case or question block can lead into contextual discussion, peer critique, a shared project, or a facilitated meeting.
8. Make feedback useful for the next attempt.
Give learners clear criteria, respond to their actual work, and identify a manageable next improvement. Build in a chance to revise or try again. Feedback becomes useful when someone can act on it.
In practice: A submitted task, review criteria, a private feedback conversation, and a revision activity connect assessment with improvement.
Clear language, readable layouts, captions, transcripts, image descriptions, and accessible interactions belong in the design from the start. Consistent navigation and a welcoming visual identity help people focus.
Teaching is an ongoing relationship.
Teachers connect the learning to the person. They notice uncertainty, ask questions that reveal assumptions, and help learners see a possibility they have missed. We design for that continuing presence, with personal introductions, check-ins, and conversations around the work.
Good guidance makes room for questions, mistakes, and another attempt. We encourage educators to model their reasoning, acknowledge uncertainty, and explain the purpose of a demanding task. Practice should give people a safe place to develop judgment before the consequences become real.
Educators need room to adapt. Shared materials should support local examples, different pacing, and additional practice. Clear responsibility for review and follow-up helps a teaching team respond consistently. Learner feedback should also inform how the curriculum improves.
We use scheduling, reminders, and organized review to reduce coordination work and protect time for teaching. We work with educators to plan outcomes and activities, try an early version with learners, and refine it from what their responses reveal.
How the pieces work together.
Consider a team learning to handle a difficult customer request. An illustrative learning sequence could look like this:
- 1.
Establish the context. A case and goal prompt connect the task to the learner's experience.
- 2.
Examine an example. A narrated demonstration explains how an experienced colleague weighs the options.
- 3.
Make a decision. A scenario question asks the learner to choose a response and explain why.
- 4.
Apply it. A task list guides a draft response that the learner submits for review.
- 5.
Discuss and improve. A facilitator reviews the work against clear criteria, then the learner revises it.
- 6.
Return to it. A later recall prompt and a new case check what the learner remembers and can apply.
Illustrative design pattern. Activities and review arrangements are selected for the learning goal and delivery environment.
Participation, completion, understanding, and successful application tell us different things. We use those distinctions to decide what evidence to collect and where someone needs more practice or support.
What informs our work.
Research informs our design choices. We apply it alongside educators' experience and evidence from the work learners produce, adapting the approach to the people, task, and context.
Built to keep getting better.
This commitment extends into our AI and workflow implementation work. We help teams connect new tools to specific responsibilities and learn how to evaluate the results. A successful rollout requires people who understand how to use the system, where their judgment is needed, and how to keep it working.
That is why our work continues through implementation, adoption, and handover. We want the people responsible for a system to understand it well enough to use it, maintain it, and improve it as their needs change.
If your organization has knowledge that more people need to put into practice, we would welcome a conversation about the work ahead.
Discuss your initiative