A useful explanation may belong in more than one place. The product detail on a page can also help a brochure, a quote or an installation guide. We start by understanding the information and the person using it, then choose the format and tools around that job.
Give the design something real to organise.
Existing documents, customer questions, product knowledge and a conversation provide useful raw material. We investigate what needs explaining, draft the content and ask the business to check the detail and nuance.
The KD framework helps keep that understanding connected to the deliverables. Figma can provide a shared design canvas when the project needs one. Creative tools support the illustrations, image preparation and document assets around the website.
Carry the foundations between formats.
The FX thinking is about shared rules that can be used with care: colour, type, spacing, components and interaction. A consistent system helps the next asset feel connected, while each format still needs to work for its own reader.
We use AI assistance where it helps organise material, draft or check the work, with human review and business approval still central. A fluent draft is not evidence that a product detail is correct. The source knowledge and the review are part of the job.
Leave a reference someone can use.
A dated screenshot can make a change or a review point clear. Snagit is part of that capture toolkit. GitHub keeps a record of source changes in our development workflow.
Handover also needs to explain the files, account access, editable assets and responsibilities. We agree those details around the way the client or partner will use the work, including what requires ongoing support.
