crm-program-design
crm-program-design
The other skills in this library each describe a mechanic or a construct. None of them says which one this business needs now, what its position in the queue follows from, or who is answerable when the number does not move.
That gap is expensive in a specific way. Every individual scenario can be built correctly, read correctly and reported on, while the program moves nothing the business cares about. Nobody is lying and nothing is broken. The place where this becomes visible is a review, and the review lives here.
This skill covers three decisions in a fixed order: what the program is for, who answers for each part of it, and what gets built first. The order is not a preference. You cannot hand out ownership before there is a goal to own, and you cannot cut a queue before you know who reads what comes out of it.