Technical Documentation Is an Information-Design Problem
Why the consequential decisions begin with product understanding, task logic, structure and representation.
I work with technical and information-rich products — organising source material and shaping clearer manuals, product content, websites, diagrams and other visual explanations.
Features, configurations or processes make sense to the people who know the product, but not necessarily to someone seeing or using it for the first time.
Specifications, existing documents and other source material contain the facts, but they are scattered, repetitive or difficult to navigate.
Assembly, operation or technical relationships may be clearer through diagrams, 3D-based illustrations, motion or other visual explanation than through more text.
For technical or information-heavy offers, the problem may be product hierarchy, content order or missing detail — not simply the visual design of the page.
Different outputs, same starting point: understand the product and make the information easier to use.
A small control product needed to communicate installation, connection logic, operating states and display behaviour across a tightly constrained multilingual instruction.


Product content can be technically complete and still leave buyers unsure what fits, how variants differ or where to find the detail they need. This working slot will be replaced by real digital or system proof.
Digital / system / ownership proof
The final visual should demonstrate product hierarchy, information structure or a buyer-facing digital decision — not simply another deliverable format.
When a product relationship is spatial, sequential or difficult to describe, the value lies in deciding what to show, what to remove and how to sequence the explanation. Real proof still needs to be selected.
Product, footage, CAD, specifications or other source material.
Selection, simplification, sequence and the communication decision.
Final visual, motion or product-facing communication asset.
Needs proof decision · candidate should diversify medium and ownership evidence.
A manual, product page, diagram or video can solve different parts of the same problem. My background lets me work across technical communication, information design, web and visual media without treating the format as the starting point.
Explore expertiseIf you have a technical product that is difficult to explain, organise or present clearly, send me a short description of the problem. I can usually tell whether my background is a good fit.
Discuss a projectPractical analyses, experiments and decision frameworks around product communication, content structure, technical visuals and product-focused websites.
Why the consequential decisions begin with product understanding, task logic, structure and representation.
My background began in graphic and visual design, expanded into web and 3D, and later moved deeper into technical products, documentation and information design. Running a business added broader responsibility for projects, clients and how the work gets delivered.
Technical communication, documentation, information design and business ownership.
Graphic design, product communication, motion and video in an international technical organisation.
Visual, web and 3D communication for technical products and a growing company.
Graphic design, print production and web work across commercial client projects.
Send me a short description of the product, the audience and what currently is not working. You do not need a finished brief.
Career opportunities, partnerships and referrals can use the same contact route.