About this block

Decision Log Case lays out four ruled rows, each naming a call made on the project: navigation model, comparison view, density default, and ship scope. Every row carries a small meta line for when the call was made and who was in the room, then two columns side by side, what I chose and what I rejected, with the reason the losing option lost. It is the show-your-reasoning block.

The decisions are a single array, so a row is a title, a meta line, a chosen paragraph, and a rejected paragraph. Naming the rejected option and why it failed is the distinctive move here, it reads as judgment rather than a tidy list of things that happened to work out.

When to use

Reach for this block in the middle of a case study, after the process or challenge section and before the results, when a reader would fairly ask why you went the way you did. The installer swaps the four titles, meta lines, and both column bodies for the real calls on their project.

A natural flow around it on a Portfolio Pro page:

Before

• Process walkthrough
• Challenge solution

After

• Metrics grid case
• Results band

What you can display

One strong use is the product design project where a few key calls shaped everything. Other decision-log shapes:

• Engineering tradeoffs. The architecture you picked beside the approach you benchmarked and dropped.
• Brand project. The direction the client approved next to the route that tested well but felt wrong.
• Research-led calls. Each decision paired with the finding that settled it, the alternative below.

Tip: keep the rejected column honest, a fake alternative you were never going to choose reads as a straw man and costs you the credibility the whole block is buying.