Clear
Written Expression auf Compose-Beats
O*NET Written Expression kommuniziert Ideen schriftlich verständlich. GIS bewertet written_expression nur auf Composition-getaggten Beats wie E-Mail und Slack-Compose.
Written craft ist Klarheit unter Druck auf Compose-Beats, keine Grammatikübungen.
Was es ist
Written expression uses library ID written_expression with compositionOnly flag in the library. It scores separately from spoken rubrics on the same episode.
Warum es im Enablement zählt
Async miswrites cause spill and buyer stalls. Enablement needs written situational fit, not generic writing courses.
Wie wir messen
Deterministic compose rubrics score clarity, appropriate tone, and situational fit on written_expression tagged beats only.
Deal-Craft-Szene
Deal IQ compose beats score buyer facing email when qualification facts and next steps must be clear.
Team-Craft-Szene
Team IQ Slack compose beats score loop-in early, ownership, and repair tone to peers and managers.
Üben in der Simulation
Activate written_expression on compose episodes. Spoken dialogue on the same arc uses spoken IDs.
Wrong-Tool-Momente
Sinkt die situative Passung, markieren Rubriken Mismatch-Risiko. Das sind typische Beats, in denen diese Kompetenz das falsche Werkzeug für die Szene ist.
- 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.