Build a STAR, not a superhero

A capability story becomes credible when the reader can identify the situation, assigned task, specific action and measured result. The STAR framework can provide that order, but its letters do not guarantee an honest answer. A speaker may still exaggerate the result, hide team support or use a long sentence to blur who did what. Sentence types should make responsibility clearer. A simple sentence can state the task directly: ‘I revised the entrance sign.’ A compound sentence can connect two equal events or show a consequence: ‘The first version was unclear, so I tested a shorter one.’ A complex sentence can explain reason, time, condition or contrast: ‘Because visitors repeated one question, I changed the wording.’ Complexity is useful only when the relationship is true. Two complete clauses cannot normally be joined by a comma alone, and double markers such as although...but can make the structure faulty in standard edited English. Content matters even more. If teammates designed role cards and recorded responses, the speaker should say so. ‘I led the revision, while two teammates collected the evidence’ demonstrates coordination rather than weakness. Results also require boundaries. Five successful role cards support a conclusion about one simulation; they do not prove that every future user will understand the sign. A strong reflection names what the speaker has learned and what should be tested next. It may use present perfect for the current learning and past simple for the dated example. Students should practise with fictional tasks or approved school activities, not invent achievements or disclose private records. The purpose of an interview response is not to sound superhuman. It is to help a listener understand a real contribution, its evidence, its shared context and its limit.