---
name: kwark-prioritise
description: Prioritise a creative-tool backlog using the effect on real work, recovery risk and implementation cost.
---

# Prioritise the film’s work

## Context

- https://kwark.space/designSystem/method/product-skills.md
- https://kwark.space/designSystem/method/ux-before-build.md
- https://kwark.space/designSystem/patterns/saving-and-sync.md

## Work

Read the backlog in terms of whose work is blocked. For a screenplay app, a change that can destroy words takes priority over convenience or polish. For an issued call sheet, ambiguous time or location can outweigh a dense toolbar.

State the chosen criteria and use the available evidence. Keep uncertain reach and impact estimates visible. If a score is useful, show the formula and assumptions so it can be checked. Apply the score to product work, never to the writer’s creative output.

Identify dependencies and the smallest independently useful slice. Include implementation, migration and verification effort. Keep a fixed time or cost constraint if the user supplies one. Avoid treating a competitor’s feature list as evidence of a user need.

## Deliverable

An ordered backlog, the reason for each decision, dependencies, an explicit release slice and its verification cost.
