Field notes

articles

A tour explains where controls live. A story explains why a person would use them. Both can be useful, but they answer different questions.

articles

Responsive layouts change the path as well as the shape of the screen. Menus, cards and stacked controls can alter what needs to be shown.

articles

When only the final teaser survives, every new request becomes a new production job. Source preservation makes creative iteration less dependent on recapture.

articles

Questions should resolve decisions the agent cannot infer reliably. Repeatedly asking for information already supplied is a state-management failure.

articles

Authentication is a prerequisite for product access, not usually a reason to buy. It can also reveal information that does not belong in a public asset.

articles

An empty dashboard can accurately show a fresh account but cannot prove a data-driven benefit. The narrative must match the state that exists.

articles

An automated workflow can execute a brief, but choosing what deserves attention is an editorial decision. Review remains part of the product experience.

articles

Creative variation should explore different reasons to care. Changing colours and a few adjectives rarely changes the underlying proposition.

articles

A presenter can explain an idea, but product proof comes from the interface and demonstrated behaviour. Decide which element is carrying the claim.

articles

The first export reveals issues that are invisible in a plan: timing, reading distance, transitions and unexpected overlays. Build a review step into the schedule.

articles

Re-edit when the source still proves the intended claim. Re-record when the product state, viewport or available evidence has changed.