Convert vague role language into a structured job profile that supports architecture decisions.
The request is vague: "We need a strategic ops person who can fix messy cross-functional things." Purpose -> Outcomes -> Duties -> Requirements -> Interfaces The common trap is polishing adjectives instead of extracting job evidence. "Strategic," "hands-on," and "cross-functional" sound useful but do not tell a recruiter, compensation partner, or calibration panel what the job owns. Purpose Ask why the job exists in one sentence: "Reduce revenue-process friction so sellers can forecast and close with fewer operational blockers." Purpose gives the role a reason to exist and prevents a miscellaneous-task job from forming. Outcomes Name 3 outcomes: shorter quote-to-contract…
Sign up free — one personalized lesson every day, matched to your role and goals.
Already have an account? Sign in