portfolio

Score an opportunity, proposal, vendor, or investment candidate against explicit criteria and produce a comparable, defensible read. Use whenever the user needs to evaluate or prioritize options, has a backlog to rank, is doing build/buy/partner analysis, or asks whether something is worth pursuing relative to other things. Trigger on "should we pursue," "how does this compare," "help me prioritize these," or any assessment against a bar.

Produce a whole-portfolio read — where the money and people actually are, what has stalled, what should be killed, and whether the mix matches the stated strategy. Use whenever the user is preparing a portfolio or quarterly review, is running multiple initiatives and has lost the aggregate picture, needs to justify a portfolio to leadership, or asks what should be stopped. Trigger on "portfolio review," "how are our initiatives doing," "what should we kill," or any request spanning several efforts at once.

Design or run the front door for a portfolio — how opportunities enter, what information is required before anything is evaluated, and what happens to things that don't qualify. Use whenever ideas arrive through side channels, the user needs an intake process or request form, a team is drowning in unsorted requests, or someone asks how work should get proposed. Trigger on "intake," "request process," "how do ideas get in," or a backlog that arrived without structure.

Match a portfolio's demands against a team's real capacity and show where it is oversubscribed, including the person-level constraints that determine dates. Use whenever the user is staffing initiatives, asks whether the team can absorb something new, is building a resourcing plan, or wonders why everything is late. Trigger on "do we have bandwidth," "can we take this on," "how should I staff this," or any allocation conversation.