Using Screenshots and Images Print

  • 0

When pictures help.

WHEN AN IMAGE HELPS

Locating something in an interface Showing what the correct result looks like Illustrating physical assembly or connection Showing relationships a description cannot convey

WHEN IT DOES NOT

Illustrating what the text already states clearly Decorating the document

WHY UNNECESSARY IMAGES HARM

They must be maintained, and they date faster than text.

WHAT TO ESTABLISH BEFORE ADDING ANY

Whether it does something the words cannot.

WHAT MAKES A USEFUL SCREENSHOT

It shows only the relevant area The relevant element is marked It is legible at the size it will be viewed

WHY CROPPING MATTERS

Full-screen images at reduced size are unreadable.

WHAT TO MARK

The specific element the reader must find.

WHAT TO AVOID IN SCREENSHOTS

Personal or customer data Internal information Anything identifying a specific account

WHY

They are published and they persist.

WHAT TO ESTABLISH

That screenshots use sample data.

WHAT PHOTOGRAPHS SUIT

Physical equipment, connections and results.

WHY THEY MATTER FOR PHYSICAL WORK

They remove ambiguity that words cannot.

WHAT MAKES A USEFUL PHOTOGRAPH

Adequate lighting The relevant part clearly visible Scale apparent The correct result shown

WHAT DIAGRAMS SUIT

Relationships, flows and structures.

WHAT TO ESTABLISH ABOUT MAINTENANCE

That images are updated when the thing changes.

WHY IT IS A PROBLEM

Interfaces change frequently and images are forgotten.

WHAT TO CONSIDER

Minimising images in areas that change often.

WHAT TO RECORD

Where images came from and how to recreate them.


Was this answer helpful?
Back

Are you happy with your experience? Leave us a review on Trustpilot.


Trustpilot