Anyone Can Claim Experience. STAR Cases Prove It.

What STAR stands for and why the format matters

STAR stands for Situation, Action, and Result. The format was originally developed for structured interview evaluation and has become the standard for documenting outcome-accountable professional experience across a range of high-stakes fields.

In the expert operator context, the STAR format serves a specific purpose: it forces documentation at the level of individual accountability rather than team contribution. The critical distinction is the Action component. A resume documents what a person did at a company – the role, the scope, the tenure. A STAR case documents what a specific person decided and built, and what happened as a result of those specific decisions. The format makes it difficult to obscure the difference between an operator who made the decisions and an operator who was present while others made them.

The Situation component sets the context: what was the company, what stage, what specific challenge or gap existed, and what was the state of the function when the operator engaged. A strong Situation description is specific enough that a reader can evaluate whether the situation is comparable to their own. A weak Situation description is vague enough to apply to any company at any stage.

The Result component documents what changed: specific percentages, timelines, revenue figures, or operational metrics that demonstrate the outcome of the operator's work. A strong Result is specific and attributable – it connects directly to what the Action describes. A weak Result is a general claim ("improved team performance," "accelerated growth") that cannot be verified or compared.

What makes a strong STAR case versus a weak one

Strong STAR cases are specific at three levels: situation specificity (exact company stage, ARR, team size, and the precise problem the operator was brought in to address), action specificity (what the operator personally decided or built, not what the team accomplished while they were present), and result specificity (measurable outcomes with a timeline and a clear line of attribution from the action to the result).

Weak STAR cases fail on one or more of these dimensions. The most common weakness is vague action description: the case says the operator "led GTM strategy" or "advised on organizational design" without specifying what exactly they decided, what they built, and what the alternative options were. Vague action descriptions cannot be verified and do not allow a reader to assess the difficulty or quality of the operator's work.

The second most common weakness is result inflation: results described in relative rather than absolute terms ("increased conversion significantly," "dramatically improved team performance"), or results attributed to the team's performance during the engagement without clear attribution to the operator's specific interventions. Strong result documentation specifies the baseline metric before the engagement, the metric after, the timeline, and the specific action the operator believes drove the change.

A useful heuristic: a strong STAR case is specific enough that a skeptic could dispute it. If the case is so vague that no one could argue with it, it is also not useful as evidence of operator capability.

How Forward Share Ventures collects and verifies STAR cases

Every expert operator who applies to the Forward Share Ventures network submits a minimum of three STAR cases as part of the vetting process. Cases are submitted using a structured template that requires specific responses to each STAR component – the template makes it difficult to submit vague descriptions because each field has explicit specificity requirements.

Verification occurs through reference conversations with the CEOs, founders, or executives who can confirm the outcomes described. The verification conversation focuses on three questions: Was the situation described accurately? Did the operator take the specific actions described? Do the results match what the reference observed? References are not character witnesses – they are outcome verifiers. The conversation is focused on the facts of the STAR case rather than on general endorsement of the operator's capability.

Cases that cannot be verified are not accepted into the network. Cases where verification reveals a material discrepancy between the documented STAR case and the reference's account are investigated, and the operator's application is reviewed based on the corrected case documentation. The verification standard is strict because the STAR Portfolio™ is the primary matching tool – a case that looks strong on paper but cannot be verified is worse than no case at all, because it misleads the matching process.

What buyers should ask for and look for in STAR cases

When evaluating any operator – whether through Forward Share Ventures or independently – the STAR case questions to ask are: "Tell me about a specific engagement where you solved a problem similar to mine. What was the company, what stage, what exactly was wrong? What did you personally decide and build? What happened, with specific numbers?" If the operator cannot answer these questions with specificity, that is a data point about the quality of their operator experience, not a gap in their storytelling ability.

The follow-up question is equally important: "What did not work in that engagement? What would you do differently?" Operators who have genuine STAR cases will have clear and specific answers to this question. Operators who are recounting involvement in others' work rather than their own will struggle to answer it, because the failures belong to someone else's memory.

Look for cases at comparable stage and situation to your own. A strong STAR case at Series C does not predict operator performance at Series A – the decisions that matter, the constraints that bind, and the stakeholder dynamics are fundamentally different. The best predictor of an operator's performance in your situation is their documented performance in a situation as close to yours as possible.

The difference between a STAR portfolio and a list of references

A reference list tells you that people who worked with an operator are willing to speak positively about them. A STAR portfolio tells you what that operator specifically did and what specifically resulted from it. The two are measuring different things.

References are valuable for assessing working style, communication, and character – qualities that matter in an operator relationship but that do not predict performance on the specific technical and operational challenges you are facing. STAR cases are valuable for assessing whether the operator has made the specific type of decision, in the specific context, that your situation requires.

The Forward Share Ventures vetting process uses both, in that order: STAR cases establish the evidence of operator capability, and reference verification confirms the accuracy of the cases. Operators who have strong references but weak STAR cases are often strong colleagues and capable executives who have not yet operated in the specific situations the expert operator role requires. Operators who have strong STAR cases and strong references are the target profile for the network.