Explain the trade-off

The project and case-study features can support a comparison between approaches considered during an engagement. Present the relevant constraints and explain why one option was selected. Avoid making the rejected option deliberately absurd just to flatter the final design. A useful comparison shows the cost or limitation accepted alongside the benefit. Readers can then understand your judgement rather than only see a polished conclusion.

Keep the evidence status clear

Label preliminary concepts, simulations and completed outcomes separately. Obtain appropriate permission before sharing internal alternatives. If you recreate the comparison for explanation, identify it as a reconstruction. Do not imply that both options were delivered or tested when they were only discussed. A compact comparison can enrich a profile without becoming a full technical report, provided the reader understands what actually happened.

Imagine this

Hypothetical scenario

A hypothetical project story compares a single shared resource page with separate audience pages. The team selected the shared page because maintenance capacity was limited, while acknowledging reduced customisation. The portfolio makes the trade-off visible rather than declaring one approach universally superior.

Make it practical.

Use this checklist as you read. Checks are not stored.

Published by Tap Tap Go. Product availability and eligibility vary by programme and market. About our stories.