Why YourHero Uses Success, Failed, and Idea Cases

When we started designing YourHero, the obvious model was the portfolio: a list of projects, each with a title and a description of what went well. It is the format everyone knows. We rejected it fairly early, and the reason says most of what there is to say about the product.

Real professional experience is not a list of wins. It is a mix of work that landed, attempts that did not, and things you saw clearly but could not pursue. A format that only has room for the first category forces people to either leave most of their experience out, or quietly rewrite it as success. Both make the record less true and, as it turns out, less persuasive.

So YourHero has three Story Types, and every Case Study is one of them.

Success Case: what worked

The Success Case is the familiar one, with a structure that keeps it honest: Problem, Action, Result. The problem has to be real and evidenced. The action is what you actually did, in your actual role. The result is what happened, with its time frame and its attribution stated like an adult, including the other things that shipped at the same time.

The structure exists because "we redesigned onboarding and it went great" is not a case; it is a caption. The Problem → Action → Result shape forces the reasoning into view, which is the part that makes a success credible rather than merely pleasant.

Failed Case: what did not work, and what was learned

This is the type most portfolio tools do not have, and its absence is why so little failed work ever gets written up. The structure is deliberately different from a success: Problem, Attempted action, Why it failed, Learning or next approach.

The point is not to celebrate failure. It is that a serious attempt that did not work is often the clearest evidence of judgment a professional can offer, because the outcome no longer hides the reasoning. A reader can see what you believed, whether it was reasonable, where it broke, and what you changed. We make the case for this at length in Why Failure Belongs in a Professional Portfolio.

Two design decisions follow from taking failure seriously. First, a Failed Case is presented with exactly the same weight and design as a Success Case, marked clearly as what it is, never visually diminished. Second, it is never disguised: the Story Type is explicit, so a failed project cannot be quietly relabelled as a learning success. Honesty about the outcome is the whole value.

Idea: what someone sees, proposes, or would improve

The third type covers something that is usually invisible in professional records: the proposal that was right but not pursued, the improvement you saw but could not prioritise, the opportunity you framed before anyone acted on it. Its structure is Problem or opportunity, Proposed approach, Expected impact, and Assumptions or validation needed.

The last element matters most. An Idea is explicitly untested. YourHero will not let it be presented as an achieved result, and the format asks the author to state what would have to be true for the proposal to work. That discipline is what separates a credible idea from a wish. Product managers in particular have a lot of this material, as we discuss in How Product Managers Can Build a Portfolio Without Being Designers.

Why the type is explicit and never inferred

A person could, in principle, write any of these as free text and let the reader work out which it is. We chose not to, for three reasons.

Honesty by construction. When the type is a first-class choice, the author decides up front whether this is a win, a failure, or a proposal, and the structure holds them to it. The "it failed but really it was a success" story becomes hard to write.

Legibility for the reader. A visitor to a profile can see at a glance that this person has documented successes, failures, and ideas, and can read each with the right expectations. A Success Case is judged on its result; a Failed Case on its analysis; an Idea on its reasoning and assumptions.

A more truthful record. The three types together describe a career the way it actually happens. A profile with all three is more believable than a highlight reel, and, we think, more interesting.

What stays independent

One thing the Story Type deliberately does not control is how a case looks. Cover colour and cover treatment are the author's choice, made separately, and a Failed Case is never automatically red or a Success automatically green. Story Type communicates meaning through an explicit marker and label, not through decoration, so a profile can have a consistent visual identity regardless of how its cases turned out.

The optional layer underneath

Every case carries its core narrative for its type. When the work warrants more, an author can add optional modules, Context, Constraints, Decisions, Alternatives, Outcomes, and Reflection, so that a small case stays small and a large one has room for the reasoning that makes it credible. The optional layer is the same for all three types; only the core narrative changes with the type.

What we are not claiming

YourHero today is a place to document and publish structured professional experience on a public profile. That is the product. We have ideas about where a well-structured body of professional experience could go, but they are ideas, and this post is about what exists.

If you want to see the three types in practice, Discover has real examples. The practical guide to writing any of them is How to Write a Professional Case Study That Shows How You Think.