Contribute
Share something that would help other PLM teams.
Field Notes publishes practitioner writing — the kind of specific, honest material that is hard to find because the people who know it are busy doing the work. If that is you, we would like to publish you, with your byline and a link back to your profile or site.
What we publish
Specific beats general. Real beats polished.
A process that worked
A change process, release workflow, migration approach or governance model your team actually runs — and what made it stick.
A lesson that cost something
A migration that went sideways, an integration that broke, an assumption that turned out wrong. The write-ups people quietly bookmark.
Something new worth trying
A technique, a tool, a way of using AI in engineering — anything that could move PLM practice forward.
A clear-eyed comparison
Platforms, approaches or methods weighed honestly, from real use rather than a vendor deck.
How it works
Pitch first. Write once we agree it fits.
- 1.Send the idea using the form — a paragraph is plenty. No need to write the whole piece first.
- 2.We reply with a yes, a no or a suggestion for a sharper angle. Usually within a few days.
- 3.You write it (800–2,000 words is the sweet spot). We edit lightly for clarity, never for message.
- 4.It publishes with your byline, your role and a link back to you.
Two ground rules
- It has to be yours to share. Nothing under NDA, and no client name or data without written permission. Anonymise freely — “a European aerospace supplier” is fine.
- No vendor pitches. Write about the practice, not the product. You keep the byline; the piece stays useful.