4 Replies Latest reply on Oct 1, 2017 1:41 PM by Grace Brebner

    Naming & Organisational Conventions - how do you do it?

    Grace Brebner

      Hey community

       

      I'm curious to hear about how other people manage organisation and naming conventions in their instances!

       

      I don't know about anyone else, but I'm really particular about them. It's definitely in my top 3 of most critical elements to successfully scaling an instance, and since it's one of the things I find myself discussing at length with every client of mine, I'm now writing a little guide to naming convention best practice.

       

      My general preference for program naming is to preface the program with a unique Job Number, then a short description. I'll tweak the Job Number structure slightly for each client, but typically lean towards something like this: Region-ProgramShortcode-YYMMDD-Short Description, e.g. UK-LE-170929-Monthly Seminar. Because the Job Number is always unique to every program, I also like to use it as a reference for anything tied to it inside or outside of Marketo, like images or in documentation.

       

      In my experience it's a convention that's proven to be scaleable, scannable, and incredibly effective.

       

      I'd love to hear what you've done that's worked well in your instance(s)! Whether it's your preferred top level folder structure, program naming, asset organisation within folders, or document naming within Design Studio - what horror or success stories do you have when it comes to naming and organisation in Marketo?