Clear
Written expression on compose beats
O*NET Written Expression communicates ideas in writing so others understand. GIS scores written_expression only on composition-tagged beats such as email and Slack compose.
Written craft is clarity under pressure on compose beats, not grammar exercises.
What it is
Written expression uses library ID written_expression with compositionOnly flag in the library. It scores separately from spoken rubrics on the same episode.
Why it matters in enablement
Async miswrites cause spill and buyer stalls. Enablement needs written situational fit, not generic writing courses.
How we measure
Deterministic compose rubrics score clarity, appropriate tone, and situational fit on written_expression tagged beats only.
Deal craft scene
Deal IQ compose beats score buyer facing email when qualification facts and next steps must be clear.
Team craft scene
Team IQ Slack compose beats score loop-in early, ownership, and repair tone to peers and managers.
Practice in simulation
Activate written_expression on compose episodes. Spoken dialogue on the same arc uses spoken IDs.
Wrong-tool moments
When situational fit drops, rubrics flag mismatch risk. These are common beats where this skill is the wrong tool for the scene.
- Polished prose that hides a required early loop-in
- Long email when the beat tagged brief accountability
- Tone that sounds defensive on blame-response compose
- Copy paste champion email without thread specific facts
- Written persuasion when the beat tagged repair only
FAQ
- Why composition only?
- The library flag ensures written_expression scores only where writing is the observable beat deliverable.
- Do spoken skills score on compose beats?
- Other IDs may co-tag when rubrics require ownership or repair, but written_expression owns writing quality.
- Can managers assign it as focus?
- Yes when async craft is the quarter gap.