Turn objectives written at "list" and "describe" into ones that measure what a person can actually do, rewritten at the right Bloom's level with a stronger action verb.
Rewrite these [onboarding learning objectives] at a higher Bloom's level so they measure real capability.
An illustrative example. Your output will reflect your own sources, data, and prompts.
I pulled the five objectives from your onboarding outline in the Knowledge Center. Four of them sit at the bottom two rungs of Bloom's taxonomy, so they test whether a new hire can recall a policy, not whether they can act on it. Here's each one rewritten at the level the job actually asks for.
Most of these objectives use verbs like list, describe, name, and recall, which live at the Remember and Understand levels. Those measure whether someone can restate information, not whether they can use it. A new hire can list the company values and still freeze when a real dilemma lands on their desk. Below, each objective is rewritten at the level that matches what the job actually asks the person to do, with the stronger action verb marked.
| Original objective | Current Bloom's level | Rewritten at target level (stronger action verb) |
|---|---|---|
| List the company values | Remember | Apply a company value to resolve a described workplace dilemma (Apply) |
| Describe the expense policy | Understand | Determine whether sample expenses are reimbursable and justify each one (Evaluate) |
| Name the security tools | Remember | Configure the security tools on a new device following the checklist (Apply) |
| Explain the org chart | Understand | Identify the right contact for three realistic requests (Apply) |
| Recall the code of conduct | Remember | Analyze a scenario and flag any code-of-conduct concerns (Analyze) |
Bloom's taxonomy runs from lower-order to higher-order thinking: Remember (recall facts), Understand (explain an idea in your own words), Apply (use what you know in a new situation), Analyze (break something down and see how the parts relate), Evaluate (judge it against criteria), and Create (produce something new). Higher is not automatically better. The right level is the one that matches what the person will actually need to do on the job.
For onboarding, most objectives belong at Apply or Analyze. A new hire rarely needs to create a new code of conduct, but they do need to notice when one is being crossed, so Analyze is the honest target for that one. Where recall really is the goal, such as knowing which tool logs a security incident, Remember is the right level and there's no gain in inflating it. The aim is to match each verb to the need, not to march every objective to the top of the pyramid.
Want me to draft a quick assessment idea for each objective, or down-level any that feel too ambitious for a first-week audience?
Low-level verbs like list, name, and describe are easy to write and easy to test, which is exactly why so many objectives stall there. But recall doesn't predict performance. Joy reads your existing objectives, spots which rung of Bloom's taxonomy each one sits on, and rewrites it at the level the job actually needs, swapping in an action verb you can build an honest assessment around.
Paste the list you already have, or point Joy at the objectives in the course outline in your Knowledge Center. Rough notes are fine.
Say who the training is for and what they need to be able to do afterward, then ask Joy to /review each objective and lift it to the level that matches the job.
Joy returns a table pairing each original objective with the Bloom's level it currently sits at and a rewrite at the target level, with the stronger action verb marked.
Copy the rewritten objectives into your LMS, authoring tool, or design doc. Ask for a different level on any single objective if the fit isn't right yet.
Save this ask as a custom command on the assistant your team already uses, so anyone can run it in one step.
Joy picks the level the work actually demands rather than pushing every objective to Create. Where recall is genuinely the goal, it stays at Remember.
Each rewrite swaps a vague verb for a measurable action, apply, configure, determine, analyze, so a later assessment has something concrete to check.
Every objective comes back tagged with the level it started at, so you can see why it was low and what changed, not just the new wording.
Think a rewrite reached too high for a first-week audience? Ask Joy to bring that one objective down a level and leave the rest.
Lift objectives from recalling a policy to judging whether a scenario complies with it, where the whole point is applied judgment.
Move from naming tools and systems to configuring and troubleshooting them, so the objective mirrors the actual first task.
Rewrite objectives so each one maps to a test question at the same level, and flag any quiz that only checks recall.
Raise objectives toward Analyze and Evaluate, where managers weigh trade-offs and justify decisions rather than repeat frameworks.
Bloom's taxonomy is a six-level ladder of thinking skills, from Remember and Understand at the bottom through Apply, Analyze, and Evaluate up to Create. It matters because the verb in an objective sets the ceiling for what your training can measure. An objective that asks someone to list or describe can only ever test recall, so if the job needs judgment, the objective has to be written at a higher level.
Joy looks at what the person actually needs to be able to do on the job, which you describe when you share the objectives. It matches the level to that need rather than pushing everything to the top. Where recall is genuinely the goal, it leaves the objective at Remember instead of inflating it.
No. Higher is not automatically better. Some facts genuinely need to be recalled, and forcing every objective up to Create produces goals that don't fit the work. The point is to match each objective to what the role demands, which sometimes means raising it and sometimes means leaving it where it is.
Yes. After it rewrites the objectives, you can ask Joy to suggest an assessment idea for each one at the same level, so an Apply objective gets a scenario question rather than a recall quiz. Joy drafts the ideas as text in chat for you to copy into your authoring tool.
Tell Joy which objective and it will bring that one down a level while leaving the rest alone. This is common for first-week onboarding, where an Evaluate-level objective may be more than a brand-new hire can reach before they've done the work.
Join the waitlist and be first to try this workflow when JoySuite launches.