my prioritization answers sound soft — feature lists with no real sequencing or trade-offs. a cynical veteran offered to run a drill where they throw in constraints and keep interrupting until i pick the one thing I’d ship. the drill exposed weak reasoning and vague trade-offs. i’d like a reproducible, no-fluff drill that forces clean trade-off articulation and sequencing within c.i.r.c.l.e.s. what exact prompts, constraints, and debrief questions would you use to run this drill on myself or peers?
do this: give yourself 3 minutes, one constraint (e.g., 30% headcount cut or $0 budget), and pick one metric to move. list three options, then immediately eliminate two with a single sentence each. the drill is brutal: you must justify the keeper with expected impact and one risk. repeat with a different constraint. if you hesitate more than 20s, you lose. forces clarity and sequencing, and the pain is the point.
another version: have a partner play execs with conflicting KPIs. you get 90s to align them. if your answer contains more than one vague promise, the partner interrupts and asks you to choose. this is how you stop being evasive and start prioritizing.
i tried the 3-minute constraint and it changed everything. quick, painful but effective. do it with a friend!
also time the 20s decision part. makes u faster. write down one sentence reasons only.
this is brutal but doable — start small and build speed, you’ll improve fast!
run a data-informed prioritization drill: pick a primary KPI, estimate effect sizes for three initiatives using past feature data or industry benchmarks, and compute expected impact per engineering week. the ranking should be impact/week. present the math in one sentence per initiative. This forces concrete trade-offs and avoids fuzzy reasoning — the interviewer can immediately see the cost-benefit logic.
if you don’t have historical data, use conservative proxies (e.g., 0.5–1% lift benchmarks) and be explicit about assumptions. interviewers respect transparent assumptions.