Putting user docs as part of a marketing role is not lining things up for a good result. :(
How about putting it under engineering instead?
Thank you. This is exactly my point.
The only way making them a function of "marketing" makes sense, is if the leadership of Ghost view user docs as something primarily to bring in (new) sales.
As a person who has often done implementation roles in their career, having to rely on docs written by "marketing" people rather than engineers is generally a lousy experience. :(
The primary function of the role is to do writing, not engineering - and the success of the role will be measured in terms of marketing, not engineering - so to me the title we went with makes the most sense. I can definitely understand the discussion here though :)
Err... trying to grok that, and failing. Are you ok to flesh out what you mean? :)
The skills overlap much better there: user research, usability testing, copywriting, information design... these are all things UX teams think about and are part of making good docs.
The only similarity between engineering projects and documentation projects is... there are engineers around.
Of all the places to put user docs, marketing is not the right one. :)
It's fairly easy to see that a Marketing manager will view the desired end result quite differently than an Engineering manager would.
With a corresponding difference in the focus and priorities then set accordingly.